From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mike Galbraith <umgwanakikbuti@gmail.com>
Subject: Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO)
Date: Mon, 07 Sep 2015 08:16:38 +0200
Message-ID: <1441606598.3529.15.camel@gmail.com>
References: <CAK-9PRC3HhM5cfWuByv5bWvzaV7w3e6Djwv_WfXK2mvs=9V6JQ@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:subject:from:to:cc:date:in-reply-to:references
         :content-type:mime-version:content-transfer-encoding;
        bh=jk79unHneNl7lL4Y7sgRL5EOEdL8q6MCk6u0CRE0dic=;
        b=YqwqGqCNpDVNzJxaK57fc5N7uCstPx05zOEkPlJs0F3xGTlwOdD9kJEx4vTqyu4UWa
         HeopHW8aTkoGDJnBzFn6F9I5ajesf0GqGDdDWN9RKIhUhHszmPYHklbKdENx9auloVTG
         9+Xp6Miy8PlNt6K/KCLZDa5Rbjimg+kH0TxNDVOGstOZdCkvrY18kd5vcdd3mviXz3xC
         RFdvfKPp2x/5CcACuRZpt+E6uBVqUoSmElXW3b5IxBI2Toe8Yp3Pld79veHaB+bNTzqG
         3IWOFTUdfIWytU/TUreQo24jAWB8qzqIqOH/BHfxg8jJ8uIxopAZ5T3F8EXLpXfpv3c0
         ueng==
In-Reply-To: <CAK-9PRC3HhM5cfWuByv5bWvzaV7w3e6Djwv_WfXK2mvs=9V6JQ@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-smp.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
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

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