From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753549AbbIGHRj (ORCPT ); Mon, 7 Sep 2015 03:17:39 -0400 Received: from mail-wi0-f182.google.com ([209.85.212.182]:33494 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751224AbbIGHRg (ORCPT ); Mon, 7 Sep 2015 03:17:36 -0400 Message-ID: <1441610253.3529.22.camel@gmail.com> Subject: Re: RT Scheduler - BUG_ON (idx >= MAX_RT_PRIO) From: Mike Galbraith To: Chinmay V S Cc: linux-kernel , linux-smp@vger.kernel.org, stable-rt@vger.kernel.org Date: Mon, 07 Sep 2015 09:17:33 +0200 In-Reply-To: References: <1441606598.3529.15.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@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