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 09:17:33 +0200
Message-ID: <1441610253.3529.22.camel@gmail.com>
References: <CAK-9PRC3HhM5cfWuByv5bWvzaV7w3e6Djwv_WfXK2mvs=9V6JQ@mail.gmail.com>
	 <1441606598.3529.15.camel@gmail.com>
	 <CAK-9PRDGDbPTPK-39Xq=SDiG7bhnDHbTD762i-nAxWTzrbW98w@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-smp-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=cOJW8VNAmoZDzAyR5gEXWu+G7LNRAmg/zPBjgtujcNw=;
        b=JqPiqZ0oVFia9EPLyRI+xuEkWpSAWHF4lwjcsI+DbABKO9GYIO8v2v4af0Y/kKxjgM
         mQsxBedGph4tVddKXsb0fKr/RiXN/KR3XrSuIllh9gVVFxVHGPrzcs/uX17i9kNzIB9l
         4oyphl9cc2qhxNhW6yLRefikZ6UtkDUTxWr1FQVgf501IsNF5dcbVkiwJ49LQXUtNqlh
         H/eA+P2xPWteGQjQcCTe8Rw3u/ue20VVAe9WwBCMC6ELjbU9WSY6UuDfXA5DTXg23vgR
         celklaAeOOWR8EmtdtWD87+VBgAutQ9qBPZM1TYewjGla4o1r/6HKjk5jGj3Fm+tFSg5
         Z9Wg==
In-Reply-To: <CAK-9PRDGDbPTPK-39Xq=SDiG7bhnDHbTD762i-nAxWTzrbW98w@mail.gmail.com>
Sender: linux-smp-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 12:28 +0530, Chinmay V S wrote:

> To catch the "culprit" in the middle of busting the scheduler's
> internal data structures, what would be the recommended debug
> mechanisms (or config options) that i can try?

I'd configure kdump, let it explode, and examine runqueues in the crash
dump first.

	-Mike