Issue created by Sebastian Huber: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5745
The POSIX sporadic server takes the real priority node of a thread out of the priority aggregation while the thread runs at the low priority. `_Scheduler_Set()` extracts that node without a check. It skips the extract where a scheduler change inhibitor is present, and only an SMP build has one. A uniprocessor build with the POSIX API therefore extracts a node which sits in no tree. A debug build ends `psx09` with a failed assertion in `_RBTree_Extract()` and a release build breaks the priority aggregation of the thread. `psx09` itself asks for the scheduler of processor 1. A uniprocessor configuration owns processor 0 alone, so `rtems_scheduler_ident_by_processor()` returns `RTEMS_INVALID_NAME` and the test ends with a failed assertion before it reaches the defect above. Found while running the test suite of the uniprocessor BSPs. This description was created with Claude Code assistance. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5745 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-9irx3og5oj9pzcfcisz3wy3wl-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
