Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

t; scheduler (sched_rt.c) on 3.1.10 kernel. > [101640.492840] kernel BUG at kernel/sched_rt.c:1126! > > This turns out to be > 1126 BUG_ON(idx >= MAX_RT_PRIO); The reason for the stack trace is given below. http://www.spinics.net/lists/newbies/msg08889.html -- -- Suji

Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

On Mon, Sep 7, 2015 at 12:28 PM, Chinmay V S wrote: > Thanks for your quick response Mike. > >> Try without the proprietary modules. You may also want to audit futex >> fixes if you can't use a maintained stable tree. 3.2 has a bunch that >> 3.1 does not. > > I see that futex.c has 17 patches in

Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

in the realtime > scheduler (sched_rt.c) on 3.1.10 kernel. > [101640.492840] kernel BUG at kernel/sched_rt.c:1126! > > This turns out to be > 1126 BUG_ON(idx >= MAX_RT_PRIO); The reason for the stack trace is given below. http://www.spinics.net/lists/newbies/m

Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)

On Mon, Sep 7, 2015 at 12:28 PM, Chinmay V S wrote: > Thanks for your quick response Mike. > >> Try without the proprietary modules. You may also want to audit futex >> fixes if you can't use a maintained stable tree. 3.2 has a bunch that >> 3.1 does not. > > I see that futex.c