[RTEMS Project] #1450: Task stuck in READY state

[RTEMS trac]

#1450: Task stuck in READY state
---------------------------+----------------------------
 Reporter:  ascesh.dandey  |       Owner:  joel.sherrill
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:  4.10
Component:  cpukit         |     Version:  4.5
 Severity:  normal         |  Resolution:  wontfix
 Keywords:                 |
---------------------------+----------------------------
Changes (by joel.sherrill):

 * version:  unknown => 4.5


Old description:

> We are using RTEMS (3.2.1) on solaris ,a leagacy code base.
>
> There are 4 timer tasks having max priority (0xFF) , in loaded scenario
> we see one of the timer tasks go to READY state , but never gets
> scheduled againg .i.e not entering RUN state ,
>
> We checked if any wake_after calls are happening in the the timer task
> context , which can explain that the task never gets resheduled , but its
> isnt so .
>
> We are strongly suspecting the issue is with the scheduling algorithm.
>
> I tried searching the bug database , but i am not able to search for the
> 3.2 version of RTEMS being used in my project and i could not see a
> similar bug in the >4.5 versions.

New description:

 We are using RTEMS (3.2.1) on solaris ,a leagacy code base.

 There are 4 timer tasks having max priority (0xFF) , in loaded scenario
 we see one of the timer tasks go to READY state , but never gets scheduled
 againg .i.e not entering RUN state ,

 We checked if any wake_after calls are happening in the the timer task
 context , which can explain that the task never gets resheduled , but its
 isnt so .

 We are strongly suspecting the issue is with the scheduling algorithm.

 I tried searching the bug database , but i am not able to search for the
 3.2 version of RTEMS being used in my project and i could not see a
 similar bug in the >4.5 versions.

--

--
Ticket URL: <http://devel.rtems.org/ticket/1450#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project