Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759453AbXKLSGW (ORCPT ); Mon, 12 Nov 2007 13:06:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751822AbXKLSGK (ORCPT ); Mon, 12 Nov 2007 13:06:10 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:50164 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751434AbXKLSGJ (ORCPT ); Mon, 12 Nov 2007 13:06:09 -0500 Subject: Re: 2.6.24-rc1-gb4f5550 oops From: Peter Zijlstra To: "Rafael J. Wysocki" Cc: Grant Wilson , Ingo Molnar , lkml , Andrew Morton , netdev , vatsa In-Reply-To: <200711082349.19344.rjw@sisk.pl> References: <20071105061158.3174d24d@worthy.swandive.local> <200711082242.21869.rjw@sisk.pl> <20071108221951.71224bd8@worthy.swandive.local> <200711082349.19344.rjw@sisk.pl> Content-Type: text/plain Date: Mon, 12 Nov 2007 19:05:49 +0100 Message-Id: <1194890749.9713.17.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2673 Lines: 74 On Thu, 2007-11-08 at 23:49 +0100, Rafael J. Wysocki wrote: > On Thursday, 8 of November 2007, Grant Wilson wrote: > > On Thu, 8 Nov 2007 22:42:21 +0100 > > "Rafael J. Wysocki" wrote: > > > > > On Thursday, 8 of November 2007, Grant Wilson wrote: > > > > On Thu, 8 Nov 2007 16:53:10 +0100 > > > > "Rafael J. Wysocki" wrote: > > > > > > > > > On Thursday, 8 of November 2007, Grant Wilson wrote: > > > > > > On Thu, 8 Nov 2007 01:06:21 +0100 > > > > > > "Rafael J. Wysocki" wrote: > > > > > > > > > > > > > On Monday, 5 of November 2007, Grant Wilson wrote: > > > > > > > > Hi, > > > > > > > > I got this oops on 2.6.24-rc1-641-gb4f5550: > > > > > > > > > > > > > > (1) Is this reproducible? > > > > > > > (2) Did it happen previously on your system? > > > > > > > > > > > > > > [18073.371126] Unable to handle kernel NULL pointer dereference at 0000000000000120 RIP: > > > > > > > [18073.371134] [] check_preempt_wakeup+0x6e/0x110 > > > > > > > > > > > > This has now happened twice - the second time was last night when > > > > > > running 2.6.24-rc2. > > > > > > > > > > > > Here's that second occurrence: > > > > > > > > > > [snip] > > > > > > > > > > Hmm. > > > > > > > > > > Please run "gdb vmlinux" and see what code corresponds to > > > > > check_preempt_wakeup+0x6e in your kernel. > > > > > > > > > > > > Dump of assembler code for function check_preempt_wakeup: > > > > > > Well, thanks, but I meant the source code. Please do "gdb vmlinux" and then > > > "l *check_preempt_wakeup+0x6e" in gdb. > > > > Here's the requested output: > > > > (gdb) l *check_preempt_wakeup+0x6e > > 0xffffffff802329ae is in check_preempt_wakeup (kernel/sched_fair.c:668). > > 663 > > 664 /* Do the two (enqueued) entities belong to the same group ? */ > > 665 static inline int > > 666 is_same_group(struct sched_entity *se, struct sched_entity *pse) > > 667 { > > 668 if (se->cfs_rq == pse->cfs_rq) > > 669 return 1; > > 670 > > 671 return 0; > > 672 } > > Well, it looks like either se or pse is NULL. > > Ingo, can you please have a look? Most puzzling this, it should be guaranteed that the top sched_entities are of the same group, therefore avoiding this loop into NULL. Obviously something has gone wrong. Grant, is there anything specific you can tell us about how to reproduce this? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/