Bug 4824
Summary: | Machine will not boot when using 2.6.12.2 | ||
---|---|---|---|
Product: | ACPI | Reporter: | John Doe (skerb1) |
Component: | Config-Interrupts | Assignee: | Len Brown (lenb) |
Status: | CLOSED CODE_FIX | ||
Severity: | blocking | CC: | acpi-bugzilla, bunk |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.12.2 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
Modprobe output for a 2.6.12.1 kernel
al_pavel: dmesg output when using 2.6.12.1 |
Description
John Doe
2005-06-30 09:30:29 UTC
Is this a vanilla ftp.kernel.org kernel or a Gentoo kernel? In the latter case, does a vanilla ftp.kernel.org 2.6.12.2 exhibit this problem? Which gcc version are you using? The 2.6.12.1 -> 2.6.12.2 patch touches only 7 files (excluding the version change in the main Makefile). Can you find the file whose change broke your booting? Please attach dmesg output of a 2.6.12.1 boot. it is a vanilla ftp.kernel.org kernel gcc version 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) I dont have access to the logs right now but I will when I get home. Created attachment 5243 [details]
Modprobe output for a 2.6.12.1 kernel
When trying to boot 2.6.12.2 it hangs at line: 170 of the attached file. 2.6.12.2 does not boot also for me! With the same .config, 2.6.12.1 boots succesfully. HP Omnibook xe4500: P4-1700, chipset ALi M1671, ATI Radeon Mobility M6 LY, ALI15X3 IDE controller. The boot process freezes after the kernel has found my IDE controller. No log entries because the logger is not yet started at this time. This is the vanilla kernel from kernel.org. gcc version 3.3.4, slackware 10.1. Created attachment 5247 [details]
al_pavel: dmesg output when using 2.6.12.1
After i have reverted the patch for drivers/pci/pci-driver.c (',' -> ';'), the kernel 2.6.12.2 boots succesfully (i' using it currently)... 8( More accurately: TWO patches should NOT be applied: drivers/pci/pci-driver.c AND (!!) drivers/acpi/pci_irq.c. The configuration "all patches but drivers/pci/pci-driver.c" DOES NOT boot on my machine! Thanks for this information. I'm reassigning this bug to Greg who is both PCI maintainer and maintainer of the stable 2.6.12.x tree. One more question: Is undoing the drivers/acpi/pci_irq.c patch alone enough for fixing the problem? On a Dell PowerEdge 2850 server with raid controller, a vanilla 2.6.12.2 kernel crashes at startup. Some output from dmesg: ICH5: IDE controller at PCI slot 0000:00:1f.1 PCI: Enabling device 0000:00:1f.1 (0005 -> 0007) ACPI: PCI Interrupt 0000:00:1f.1[A]: no GSI - using IRQ 0 The crash seems to happen a little bit later in the megadriver_mbox module. Removing the acpi_register_gsi(dev->irq, ACPI_LEVEL_SENSITIVE, ACPI_ACTIVE_LOW); in pci_irq.c fixes the problem. Another option is changing the check "dev->irq >= 0" to "dev->irq > 0" Yes, the solution
> changing the check "dev->irq >= 0" to "dev->irq > 0"
works for me (on 2.6.12.2, without any other changes).
Yes this patch fixed the problem for me as well...=) Thank you 2.6.12.2 problem confirmed on presario 2519eu laptop, fortunately linus's patch at http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=44f8e1a20cf3afe10a3744bd9317808a39a242bb apparently solves the problem. Before that, pressing any key eventually unblocked the boot, until another stage got blocked again, etc. Usually it happened right after hotplug was trying to probe usb. This problem should be fixed in both 2.6.12.3 and 2.6.13-rc3. |