Bug 198810 - linux boot hangs with intel Q35 chipset
|
Bug#:
198810
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: kernel@gentoo.org
|
Reported By: andreas.eckstein@gmx.net
|
|
Component: Core system
|
|
|
URL:
|
|
Summary: linux boot hangs with intel Q35 chipset
|
|
Keywords: InSVN
|
|
Status Whiteboard: linux-2.6.24
|
|
Opened: 2007-11-11 14:31 0000
|
The linux kernel boot will hang at ACPI initialisation unless acpi=off or
pci=nommconf are used as boot parameters. The kernel devs are aware of the
problem:
http://kerneltrap.org/mailarchive/linux-kernel/2007/8/26/164870
but as of linux-2.6.24_rc2, the patch from the discussion hasn't made it into
mainline. There's talk about BIOS updates fixing the issue for G33 chipsets,
but not so for Q35 (I'm using the latest BIOS for the intel DQ35JO board). I've
tested the patch against vanilla-sources-2.6.24_rc2 and haven't noticed any
negative effects so far.
Reproducible: Always
There seems to still be quite a bit of discussions concerning the validity of
this patch. I think it might be worth it to keep an eye on the upstream thread
until an accepted patch is proposed and committed.
Mike: have you confirmed that upstream has everything under control and doesn't
need our help? Unless upstream tell us to go away, we should pester them and
offer resources -- namely Andreas who would hopefully test candidate patches
should they appear. We shouldn't close this unless there is nothing we can do.
If you have the time, read the thread from the original description. The
discussion seems to have lost some steam and stopped.
If you think after reading there is more that we can do, we can reopen this.
we can at least attempt to breathe some life back into the issue
The problem has been brought to the attention of the master himself, and with
any look above patch will get included soon (preliminarily at least):
http://lkml.org/lkml/2007/12/6/368
Luck, not look, of course.
thanks for the update and your efforts, I just sent an email asking Andrew to
correct that.
Created an attachment (id=143323) [details]
new patch
Rumour has it that this patch solves the issue, and it's already upstream.
Please could you apply it (*instead* of any others) to 2.6.24 and let us know
what happens?
Daniel, the patch works well here.
Great, thanks for testing. Queued this up for next 2.6.24 release.
Not going to backport to 2.6.23 because the code the patch touches on has
changed too much.
Fixed in genpatches-2.6.24-4 (gentoo-sources-2.6.24-r3), thanks for testing