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

Mike Galbraith <[email protected]> Mon, 07 Sep 2015 08:16:38 +0200
Newsgroups org.kernel.vger.linux-smp,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Mon, 2015-09-07 at 11:00 +0530, Chinmay V S wrote:

> So how could rt_nr_running be non-zero AND active-bitmap NOT have any
> valid bit set?

It can't without being busted.

> Also including the kernel OOPS below.
> Do you see any tell-tale signs in the register-dump/backtrace that can
> point me in the right direction?

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.

	-Mike