From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751670AbbIGGQo (ORCPT ); Mon, 7 Sep 2015 02:16:44 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:37429 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750926AbbIGGQl (ORCPT ); Mon, 7 Sep 2015 02:16:41 -0400 Message-ID: <1441606598.3529.15.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 08:16:38 +0200 In-Reply-To: References: 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 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