From: Nick Piggin <npiggin@suse.de>
To: David Woodhouse <dwmw2@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Patch "USB: Work around BIOS bugs by quiescing USB controllers earlier" causes MCEs
Date: Fri, 2 Oct 2009 09:34:00 +0200 [thread overview]
Message-ID: <20091002073400.GV6327@wotan.suse.de> (raw)
Hi,
Your patch db8be50c4307dac2b37305fc59c8dc0f978d09ea is causing my
ia64 Altix system to die with an MCE in early boot.
Good dmesg looks like this:
ACPI: PCI Root Bridge [P001] (0001:00)
pci 0001:00:01.0: reg 10 io port: [0x1000-0x10ff]
pci 0001:00:01.0: reg 14 64bit mmio: [0x700000-0x703fff]
pci 0001:00:01.0: reg 1c 64bit mmio: [0x710000-0x71ffff]
pci 0001:00:01.0: reg 30 32bit mmio pref: [0x800000-0x8fffff]
pci 0001:00:01.0: supports D1 D2
pci 0001:00:02.0: reg 10 64bit mmio: [0x720000-0x72ffff]
pci 0001:00:02.0: PME# supported from D3hot
pci 0001:00:02.0: PME# disabled
pci 0001:00:02.1: reg 10 64bit mmio: [0x730000-0x73ffff]
pci 0001:00:02.1: PME# supported from D3hot
pci 0001:00:02.1: PME# disabled
pci 0001:00:03.0: reg 10 64bit mmio pref: [0x900000-0x9fffff]
pci 0001:01:01.0: reg 10 32bit mmio: [0xa00000-0xa00fff]
pci 0001:01:01.0: supports D1 D2
Bad (which is less verbose because it came from a console output):
ACPI: PCI Root Bridge [P001] (0001:00)
pci 0001:00:02.0: PME# supported from D3hot
pci 0001:00:02.0: PME# disabled
pci 0001:00:02.1: PME# supported from D3hot
pci 0001:00:02.1: PME# disabled
Entered OS MCA handler. PSP=20000000fff21120 cpu=2 monarch=1
<6>cpu 2, MCA inconsistent r12 and r13, original stack not modified
<6>Entered OS MCA handler. PSP=20000000fff21120 cpu=1 monarch=0
<6>cpu 1, MCA inconsistent r12 and r13, original stack not modified
<6>Entered OS MCA handler. PSP=20000000fff21120 cpu=0 monarch=0
<6>cpu 0, MCA inconsistent r12 and r13, original stack not modified
<6>Entered OS MCA handler. PSP=20000000fff21120 cpu=3 monarch=0
<6>cpu 3, MCA inconsistent r12 and r13, original stack not modified
<6>All OS MCA slaves have reached rendezvous
mlogbuf_finish: printing switched to urgent mode, MCA/INIT might be dodgy or fail.
Delaying for 5 seconds...
Relevant pci devices:
0001:00:03.0 PCI bridge: IBM PCI-X to PCI-X Bridge (rev 03)
0001:01:01.0 USB Controller: NEC Corporation USB (rev 43)
0001:01:01.1 USB Controller: NEC Corporation USB (rev 43)
0001:01:01.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
Let me know any more info I can provide.
next reply other threads:[~2009-10-02 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 7:34 Nick Piggin [this message]
2009-10-02 10:26 ` Mikael Pettersson
2009-10-02 19:28 ` Mikael Pettersson
2009-10-06 4:44 ` Nick Piggin
2009-10-06 4:53 ` David Woodhouse
2009-10-11 22:51 ` Mikael Pettersson
2009-10-12 17:34 ` Bjorn Helgaas
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=20091002073400.GV6327@wotan.suse.de \
--to=npiggin@suse.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®