From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Chinmay V S <cvs268@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-smp@vger.kernel.org, stable-rt@vger.kernel.org
Subject: Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)
Date: Mon, 07 Sep 2015 08:16:38 +0200 [thread overview]
Message-ID: <1441606598.3529.15.camel@gmail.com> (raw)
In-Reply-To: <CAK-9PRC3HhM5cfWuByv5bWvzaV7w3e6Djwv_WfXK2mvs=9V6JQ@mail.gmail.com>
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
next prev parent reply other threads:[~2015-09-07 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 5:30 RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO) Chinmay V S
2015-09-07 6:16 ` Mike Galbraith [this message]
2015-09-07 6:58 ` Chinmay V S
2015-09-07 7:17 ` Mike Galbraith
2015-09-07 9:37 ` Sujit K M
2015-09-07 9:38 ` Sujit K M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1441606598.3529.15.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=cvs268@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.org \
--cc=stable-rt@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox