<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zephyr BTLE in infinite waiting loop</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127842/zephyr-btle-in-infinite-waiting-loop</link><description>When a BTLE Connection is underway, calling bt_disable can result in an infinite hang in the Zephyr BTLE stack. Using ncs v3.0.0 Any ideas? There is some mention of: CONFIG_BT_HCI_ACL_FLOW_CONTROL causing a deadlock, not sure if that is it and also github</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 20 Apr 2026 13:42:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127842/zephyr-btle-in-infinite-waiting-loop" /><item><title>RE: Zephyr BTLE in infinite waiting loop</title><link>https://devzone.nordicsemi.com/thread/565179?ContentTypeID=1</link><pubDate>Mon, 20 Apr 2026 13:42:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03715a99-d529-4240-a970-0f70aee92755</guid><dc:creator>Simon D-M</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The link you sent is for a commit that, I believe, was merged in the NCS v3.1.0. So to see if it fixes your issue you can either try to patch your current SDK or try to migrate to a later version.&lt;/p&gt;
&lt;p&gt;Also, you can check the &amp;quot;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html#bluetooth_le"&gt;known Issues&lt;/a&gt;&amp;quot; page. It looks like&amp;nbsp;NCSDK-31528 or&amp;nbsp;NCSDK-30959 can be relevant. Did you already try the proposed workarounds ?&lt;/p&gt;
&lt;p&gt;If the workarounds don&amp;#39;t work, can you please share a bit more (code snippet, debug logs, ...)&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon D-M&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr BTLE in infinite waiting loop</title><link>https://devzone.nordicsemi.com/thread/565155?ContentTypeID=1</link><pubDate>Mon, 20 Apr 2026 10:30:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a1bf5d3-ef38-4f9e-b136-2ed7d8c5710b</guid><dc:creator>AGeegee</dc:creator><description>&lt;p&gt;I put a breakpoint in the WDT Kick area. Though it could be that most of the device is &amp;#39;sleeping&amp;#39; / WFI as such a 5s WDT timeout might take 100&amp;#39;s of seconds before it times out.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Zephyr BTLE in infinite waiting loop</title><link>https://devzone.nordicsemi.com/thread/565141?ContentTypeID=1</link><pubDate>Mon, 20 Apr 2026 06:54:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a34bcf0d-297c-487a-a14b-d1834ef441e4</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Some of the deadlocks won&amp;#39;t keep any thread in&amp;nbsp;&lt;em&gt;running&lt;/em&gt; state, i.e. all threads are in one of the waiting functions similar to &lt;code&gt;k_sem_take()&lt;/code&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thus its highly likely that your WDT thread was still able to run&lt;em&gt;&amp;nbsp;&lt;/em&gt;even if its at lowest priority. How do you know it did not refresh WDT?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>