From: Andi Kleen <ak@muc.de>
To: Tony Hoyle <tmh@nodomain.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops linux 2.4.23-pre6 on amd64
Date: Sat, 04 Oct 2003 20:39:59 +0200 [thread overview]
Message-ID: <m3smm8q22o.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <CYRo.18k.9@gated-at.bofh.it> (Tony Hoyle's message of "Sat, 04 Oct 2003 20:00:15 +0200")
Tony Hoyle <tmh@nodomain.org> writes:
>
> Trace; ffffffff80202fce <pci_announce_device+3e/60>
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
next parent reply other threads:[~2003-10-04 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CYRo.18k.9@gated-at.bofh.it>
2003-10-04 18:39 ` Andi Kleen [this message]
2003-10-04 19:05 ` Oops linux 2.4.23-pre6 on amd64 Tony Hoyle
2003-10-04 19:18 ` Tony Hoyle
2003-10-04 20:55 ` Andi Kleen
2003-10-04 22:34 ` Tony Hoyle
2003-10-05 9:20 ` Andi Kleen
2003-10-05 9:35 ` Tony Hoyle
2003-10-05 14:29 ` Tony Hoyle
2003-10-05 15:37 ` Andi Kleen
2003-10-05 15:42 ` Tony Hoyle
2003-10-05 17:21 ` Marcelo Tosatti
2003-10-05 17:41 ` Tony Hoyle
2003-10-07 20:33 ` calling devinet_ioctl from a kernel module Vishwas Raman
2003-10-04 17:50 Oops linux 2.4.23-pre6 on amd64 Tony Hoyle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3smm8q22o.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tmh@nodomain.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox