From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262686AbTJDSkT (ORCPT ); Sat, 4 Oct 2003 14:40:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262687AbTJDSkT (ORCPT ); Sat, 4 Oct 2003 14:40:19 -0400 Received: from zero.aec.at ([193.170.194.10]:4624 "EHLO zero.aec.at") by vger.kernel.org with ESMTP id S262686AbTJDSkQ (ORCPT ); Sat, 4 Oct 2003 14:40:16 -0400 To: Tony Hoyle Cc: linux-kernel@vger.kernel.org Subject: Re: Oops linux 2.4.23-pre6 on amd64 From: Andi Kleen Date: Sat, 04 Oct 2003 20:39:59 +0200 In-Reply-To: (Tony Hoyle's message of "Sat, 04 Oct 2003 20:00:15 +0200") Message-ID: User-Agent: Gnus/5.090013 (Oort Gnus v0.13) Emacs/21.2 (i586-suse-linux) References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Tony Hoyle writes: > > Trace; ffffffff80202fce It jumped to nirvana, probably because someone passed crap to pci_announce_device. My first guess would be a non matching module. Do a make distclean and recompile/reinstall everything. > Trace; ffffffffa0014560 <[usbcore]hcd_data_lock+4c4c/5f5f06ec> But the decode is useless because the module in question is not loaded. Can you load the module whatever it is manually and then decode the oops while it's still loaded? Or better compile in all USB statically and see if it oopses too. Your legacy USB problems are very likely BIOS bugs. -Andi