From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4 Description of problem: the computer starts up to the message 'setting computer name' and freeze complete. Motherboard: MS-6758 dmidecode: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=103925 acpidmp: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=103926 Version-Release number of selected component (if applicable): kernel-2.6.12-1.1387_FC4.i686.rpm How reproducible: Always Steps to Reproduce: 1. Problem occurs every time 2. 3. Actual Results: computer boots with 2.6.11-1.1369_FC4 fine Additional info:
I also noticed strange stuff with 1387, as opposed to 1385 (the one from testing). It appears that something if very wrong with 1387... The symptoms on my notebook (full hardware spec here: http://www.rexursive.com/articles/linuxonhpze4201.html) are that when I see the line "Initializing: storage network audio" it takes ages to get to "done". This wasn't a problem with any of the previous kernels. Unfortunately there is nothing in the logs or dmesg that points to any meaningful error that would be causing this.
This bug is also a duplicate of bug #162320.
*** Bug 162320 has been marked as a duplicate of this bug. ***
To me, this happened just before setting up LVM modules.
This happens to me as well. It can happen at virtually any stage, but most usually at the mentioned. I once managed to boot the whole system up before the lockup and even login. I can't find any useful log entry or alike. I tried the non-smp kernel with acpi=off and it did't fix the issue for me and can't think of anything else useful. Reverted back to .11 kernel
Created attachment 116324 [details] Sample dmesg from problematic computer In case it helps to see some basic information about platform.. My board is Asus P4P800-VM http://www.asus.com/prog/spec.asp?m=P4P800-VM&langs=01
I agree with comment #5 - it happens kind of at random - completely unpredictable. Actually, I just booted up and the "Initializing hardware..." thing went on really fast. And I had slowdowns at other boot stages. No idea what's happening there...
Just to preserve sanity, I booted 1385 again (the one based on 2.6.12.1) and it is quite fine. My bet is on that ACPI patch in 2.6.12.2, which changed IRQ routing via ACPI. These strange "hangs" have all the hallmarks of undelivered IRQs...
Re Comment #8 : This sounds like a reasonable explanation for what I'm seeing so I'll add my comments here instead of opening a new report. My computer consistently hangs on boot with kernel-2.6.12-1.1387 with the default boot command line; it works when I add "pci=noacpi". Hardware is a notebook with ATI IGP320M northbridge (Athlon XP-M processor) and ALi southbridge. The last boot messages before the hang are: ---- Warning: ATI Radeon IGP Northbridge is not yet fully tested. ALI15X3: IDE controller at PCI slot 0000:00:0f.0 ACPI: PCI Interrupt 0000:0f.0[A]: no GSI - using IRQ 0 PCI: Setting IRQ 0 as level-triggered ALI15X3: chipset revision 196 ALI15X3: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x1800-0x1807, BIOS settings: hda:DMA, hdb:PIO ide1: BM-DMA at 0x1808-0x180f, BIOS settings: hdc:DMA, hdd:PIO ---- (Hand-copied, sorry for any typos, but I think I got it right.) The "IRQ 0" sounds fishy to me; the IDE controller is normally on IRQs 14 and 15 I believe, although I'm not sure about what that message actually means. My /proc/interrupts now kernel 1387, booting with pci=noacpi, and I think this is what it usually looks like) looks like this: ---- CPU0 0: 564758 XT-PIC timer 1: 1578 XT-PIC i8042 2: 0 XT-PIC cascade 7: 2 XT-PIC parport0 8: 1 XT-PIC rtc 9: 1 XT-PIC acpi 11: 135957 XT-PIC ath0, ALI 5451, ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3, yenta, yenta, eth0, radeon@pci:0000:01:05.0 12: 113 XT-PIC i8042 14: 25132 XT-PIC ide0 15: 4431 XT-PIC ide1 NMI: 0 ERR: 0 ---- I think that this means that itlooks like something has gone fishy with the interrupt routing? And the patch in 2.6.12.2 has the comment --- Linus Torvalds: ACPI: Make sure we call acpi_register_gsi() even for default PCI interrupt assignment --- Sounds related to "no GSI" in my boot messages above?
I am seeing the same symptoms on an ASUS P5A as described in comment #9. Differences in my case is the ALI15X3 is chipset revision 193 (instead of 196) and my ide1 shows hdd:DMA (instead of hdd:PIO). Modifying the boot parameters to add "pci=noacpi" also gets me past the problem and allows the kernel to boot and run.
Re comment #10: I strongly suspect that the reason that I'm seeing "hdd:PIO" is that this is a notebook with one hard disk (hda) and one CDRW/DVD (hdc), so there's no hdd drive connected. Just for clarity, the section corresponding to what I posted above, but grabbed from my dmesg when booted with pci=noacpi are ---- Warning: ATI Radeon IGP Northbridge is not yet fully tested. ALI15X3: IDE controller at PCI slot 0000:00:0f.0 ALI15X3: chipset revision 196 ALI15X3: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x1800-0x1807, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x1808-0x180f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: TOSHIBA MK6021GAS, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: TOSHIBA DVD-ROM SD-R2412, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 ---- (...boot continues...)
Most likely related to this kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=4824 BTW, there is already a fix for PCI IRQ issue, just scroll down to the end of that bug report.
*** This bug has been marked as a duplicate of 162269 ***
Problem was fixed for me with kernel-2.6.12-1.1390_FC4 but after update BIOS to V2.4 booting isn't longer possible. Now kernel-2.6.11-1.1369_FC4 is the only working kernel for me :(((
Created attachment 116565 [details] dmidecode.out
Created attachment 116566 [details] acpidmp.out
with the last FC5 kernel-2.6.12-1.1425_FC5 or a vanilla linux-2.6.13-rc2 kernel, the computer is booting, why not with 2.6.12-1.1387_FC4 and 2.6.12-1.1390_FC4 ? I get no message in dmesg or messages.
Although comment 13 says this bug is a duplicate of 162269, the use of 'pci=noacpi' or 'acpi=off' does not solve the problem (despite 162269 saying it does). I too can only run kernel-2.6.11-1.1369_FC4 as the latest working kernel, all others fail at setting hostname.
booting works now again with kernel-2.6.12-1.1394_FC4
Yes, 1394 works for me too. Must have been the PIIX change. Many thanks.