Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757780AbYBPLvT (ORCPT ); Sat, 16 Feb 2008 06:51:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753849AbYBPLvB (ORCPT ); Sat, 16 Feb 2008 06:51:01 -0500 Received: from www.tglx.de ([62.245.132.106]:37218 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753721AbYBPLvA (ORCPT ); Sat, 16 Feb 2008 06:51:00 -0500 Date: Sat, 16 Feb 2008 12:50:37 +0100 (CET) From: Thomas Gleixner To: Jiri Kosina cc: Quel Qun , linux-kernel@vger.kernel.org, Ingo Molnar Subject: Re: Kernel oops with bluetooth usb dongle In-Reply-To: Message-ID: References: <021620080041.476.47B631500001264E000001DC2200761438CE05040A05@comcast.net> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 925 Lines: 30 On Sat, 16 Feb 2008, Jiri Kosina wrote: > [ Ingo and Thomas added to CC, as this is apparently nohz stuff ] Well, it explodes there :) I can not exactly decode the source line, but it's either list corruption or something is fiddling with an enqueued timer. > Quel, does the problem go away when you boot with nohz=off? Quel, can you please compile the kernel with CONFIG_DEBUG_INFO=y ? Then after a crash, pick the address: > > IP: [] get_next_timer_interrupt+0xfe/0x210 ----------^^^^^^^^ and run it through: # addr2line -e vmlinux c0131f3e Please also enable CONFIG_DEBUG_LIST=y, which should catch the place where a list corruption happens. Thanks, tglx -- 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/