From: Andi Kleen <andi@firstfloor.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
Alberto Panizzo <maramaopercheseimorto@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: core i7: hang at Booting processor 5 APIC 0x3 ip 0x6000
Date: Sat, 27 Feb 2010 14:20:34 +0100 [thread overview]
Message-ID: <87k4tyrf19.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4B891621.5070807@wpkg.org> (Tomasz Chmielewski's message of "Sat, 27 Feb 2010 13:54:57 +0100")
Tomasz Chmielewski <mangoo@wpkg.org> writes:
> Justin P. Mattock wrote:
>
>> but what about 2.6.33*(hot off of the press thing).
>
> I found a way to 100% reproduce the kernel "hang" while booting
> 2.6.33. The symptoms will look like here:
>
> http://wpkg.org/files/i7_hang/
>
>
> To hang the kernel while booting, just tap repeatedly on the keyboard
> as soon as the bootloader starts loading the kernel.
>
> The kernel hangs for me every time as I do it.
>
> If it matters, I use a USB keyboard (as a matter of fact, two USB
> keyboards are connected as its a multiseat PC, although I tap the keys
> on only one of them).
Points to USB legacy BIOS code problems. FWIW i've seen the same problem
occasionally too, but I can't reproduce it reliably.
You could add some printks to the USB handoff code (and see if that appears
around the hang (drivers/usb/host/pci-quirks.c:quirk_usb_disable_ehci)
-Andi
prev parent reply other threads:[~2010-02-27 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 19:00 core i7: hang at Booting processor 5 APIC 0x3 ip 0x6000 Tomasz Chmielewski
2010-02-02 19:37 ` Justin P. Mattock
2010-02-02 19:39 ` Tomasz Chmielewski
2010-02-02 20:07 ` Justin P. Mattock
2010-02-12 8:25 ` Alberto Panizzo
2010-02-12 8:50 ` Justin P. Mattock
2010-02-27 12:54 ` Tomasz Chmielewski
2010-02-27 13:20 ` Andi Kleen [this message]
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=87k4tyrf19.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=maramaopercheseimorto@gmail.com \
/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