# Task blocking in xQueueReceive but not on the xTasksWaitingToReceive list

**URL:** <https://forums.freertos.org/t/task-blocking-in-xqueuereceive-but-not-on-the-xtaskswaitingtoreceive-list/25209>\
**Category:** Kernel\
**Created:** [October 23, 2026, 8:18am UTC](https://forums.freertos.org/t/task-blocking-in-xqueuereceive-but-not-on-the-xtaskswaitingtoreceive-list/25209 "2026-10-23T08:18:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![OliM](https://avatars.discourse-cdn.com/v4/letter/o/f04885/32.png) [@OliM](https://forums.freertos.org/u/OliM)\
**Post date:** [October 23, 2026, 8:18am UTC](https://forums.freertos.org/t/task-blocking-in-xqueuereceive-but-not-on-the-xtaskswaitingtoreceive-list/25209/1 "2026-10-23T08:18:58Z")

</div>

I managed to get one of my tasks hanging in the following situation:

 ![image](https://d2v6vdsk2p900z.cloudfront.net/original/2X/4/4e49c175950c83462e05cab7af9205b4271cf919.png)  
Neither the scheduler ends the wait after xTicksToWait, nor the queue activated because of the waiting message. So somehow the OS has completely missed the fact that xQueueReceive was called, even though it is currently yielding right inside that call.

 ![image](https://d2v6vdsk2p900z.cloudfront.net/original/2X/8/8ce4aa53d3725777b30937f396a8dc9d7c4b5121.png)  
I guess it is a 99% chance this is not a FreeRTOS bug but wrong usage somewhere, but what kind of misuse could trigger such a result?

---

<div class="post-metadata">

**Author:** ![RAc](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rac/32/1389_2.png) [@RAc](https://forums.freertos.org/u/RAc)\
**Post date:** [October 23, 2026, 9:17am UTC](https://forums.freertos.org/t/task-blocking-in-xqueuereceive-but-not-on-the-xtaskswaitingtoreceive-list/25209/2 "2026-10-23T09:17:06Z")

</div>

most probably a misuse of a critical section or a violation of the ISR rules (ISR API call \> MAX\_SYSCALL, mismatch in xxxFromISR call discipline, Syscall isr not lowest priority or something the like). Good luck!

Edit: If this is a custom port, have a very close look at the port implementations of isr mask manipulation, critical section and related.

---

<div class="post-metadata">

**Author:** ![OliM](https://avatars.discourse-cdn.com/v4/letter/o/f04885/32.png) [@OliM](https://forums.freertos.org/u/OliM)\
**Post date:** [October 23, 2026, 11:19am UTC](https://forums.freertos.org/t/task-blocking-in-xqueuereceive-but-not-on-the-xtaskswaitingtoreceive-list/25209/3 "2026-10-23T11:19:24Z")

</div>

Looks like the mismatch in that case was an explicit call to suspend because the power management mistakenly thought that hardware area was already unused. Thank you for the pointers nonetheless.

---

<div class="post-metadata">

**Author:** ![RAc](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rac/32/1389_2.png) [@RAc](https://forums.freertos.org/u/RAc)\
**Post date:** [October 23, 2026, 2:41pm UTC](https://forums.freertos.org/t/task-blocking-in-xqueuereceive-but-not-on-the-xtaskswaitingtoreceive-list/25209/4 "2026-10-23T14:41:34Z")

</div>

Thanks for reporting the solution! 🙂