Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423053AbWJVGgr (ORCPT ); Sun, 22 Oct 2006 02:36:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423049AbWJVGgr (ORCPT ); Sun, 22 Oct 2006 02:36:47 -0400 Received: from smtp.osdl.org ([65.172.181.4]:14276 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1423045AbWJVGgq (ORCPT ); Sun, 22 Oct 2006 02:36:46 -0400 Date: Sat, 21 Oct 2006 23:36:10 -0700 From: Andrew Morton To: David Miller Cc: preining@logic.at, linux-kernel@vger.kernel.org, Michael Chan , netdev@vger.kernel.org Subject: Re: tg3 kernel bug in 2.6.18-mm3 and 2.6.19-rc2-mm2 Message-Id: <20061021233610.f190e0a8.akpm@osdl.org> In-Reply-To: <20061021.123814.106436476.davem@davemloft.net> References: <20061021132239.GA29288@gamma.logic.tuwien.ac.at> <20061021.123814.106436476.davem@davemloft.net> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1674 Lines: 49 On Sat, 21 Oct 2006 12:38:14 -0700 (PDT) David Miller wrote: > From: Norbert Preining > Date: Sat, 21 Oct 2006 15:22:39 +0200 > > > [] dump_stack+0x12/0x14 > > [] softlockup_tick+0xaa/0xc1 > > [] update_process_times+0x3b/0x5e > > [] handle_update_profile+0x14/0x1e > > [] smp_apic_timer_interrupt+0x49/0x5b > > [] apic_timer_interrupt+0x28/0x30 > > DWARF2 unwinder stuck at apic_timer_interrupt+0x28/0x30 > > Leftover inexact backtrace: > > [] delay_tsc+0xb/0x13 > > [] __delay+0x6/0x7 > > It's OOPS'ing by softlockup'ing in udelay() and then we get a corrupt > backtrace. The unwinder-based backtrace is screwed up (yet again) but the old-style backtrace is there, in all its messy glory. Weeding out the crap, I think it's this: [] delay_tsc+0xb/0x13 [] __delay+0x6/0x7 [] _tw32_flush+0x3f/0x51 [] tg3_switch_clocks+0x8f/0x93 [] tg3_open+0x250/0x520 [] dev_open+0x2b/0x62 [] dev_change_flags+0x47/0xe4 [] devinet_ioctl+0x252/0x556 [] dev_ifsioc+0x113/0x38d [] dev_load+0x24/0x4b [] sock_ioctl+0x19e/0x1c2 It's strange that the post-2.6.19-rc2 changes triggered this - that code won't have run yet. Norbert, are you really sure? - 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/