New: ACPI under 2.5.50+ (approx) locks system hard during bootup
http://bugme.osdl.org/show_bug.cgi?id=529
Summary: ACPI under 2.5.50+ (approx) locks system hard during
bootup
Kernel Version: 2.5.50 - 2.5.66 at least. Trying to find the last one
that work
Status: NEW
Severity: normal
Owner: [email protected]
Submitter: [email protected]
Distribution: Debian Woody / Sid
Hardware Environment: HP ZT1195 laptop
Software Environment:
Problem Description: Ever since that that update around 2.5.50 of the ACPI system I cannot boot my laptop at all with anything other than acpi=off. I am trying to build the older kernels to determine exactly which version started this problem. I do have a working version of 2.5.48 I'm using right now which produces the following
interrupts:
CPU0
0: 725368 XT-PIC timer 1: 4038 XT-PIC i8042 2: 0 XT-PIC cascade 8: 4 XT-PIC rtc 9: 31 XT-PIC acpi, VIA8233 10: 581 XT-PIC uhci-hcd, eth0 11: 3160 XT-PIC PCI device 1524:1410 (ENE Technology Inc), eth1 12: 14931 XT-PIC i8042 14: 9367 XT-PIC ide0 15: 27 XT-PIC ide1 NMI: 0 LOC: 0 ERR: 0
dmesg sections from 2.5.45:
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 126960
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 122864 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 OID_00 ) @ 0x000e5010
ACPI: RSDT (v001 INSYDE RSDT_000 00000.00001) @ 0x1efffbc0
ACPI: FADT (v003 INSYDE FACP_000 00000.00256) @ 0x1efffac0
ACPI: BOOT (v001 INSYDE SYS_BOOT 00000.00256) @ 0x1efffb50
ACPI: DBGP (v001 INSYDE DBGP_000 00000.00256) @ 0x1efffb80
ACPI: DSDT (v001 INSYDE VT8633 00000.04096) @ 0x00000000
ACPI: BIOS passes blacklist
ACPI: MADT not present
....
ACPI: Subsystem revision 20021022
ACPI-0357: *** Warning: Inconsistent FADT length (0x84) and revision (0x3),
using FADT V1.0 portion of table
ACPI-0508: *** Info: GPE Block0 defined as GPE0 to GPE15
ACPI breakpoint: Executed AML Breakpoint opcode
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: (supports S0 S3 S4 S5)
ACPI: PCI Interrupt Link [LNKA] (IRQs 5 7 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 10, enabled at IRQ 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 *9 10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 *10)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 1)
dmesg from my latest attempt, 2.5.66-bk7 with a fixed DSDT:
On node 0 totalpages: 126960
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 122864 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 OID_00 ) @ 0x000e5010
ACPI: RSDT (v001 INSYDE RSDT_000 00000.00001) @ 0x1efffbc0
ACPI: FADT (v003 INSYDE FACP_000 00000.00256) @ 0x1efffac0
ACPI: BOOT (v001 INSYDE SYS_BOOT 00000.00256) @ 0x1efffb50
ACPI: DBGP (v001 INSYDE DBGP_000 00000.00256) @ 0x1efffb80
ACPI: DSDT (v001 INSYDE VT8633 00000.04096) @ 0x00000000
ACPI: BIOS passes blacklist
ACPI: MADT not present
...
ACPI: Subsystem revision 20030228
tbconvrt-0375: *** Warning: Inconsistent FADT length (0x84) and revision (0x3),
using FADT V1.0 portion of table
tbget-0292: *** Info: Table [DSDT] replaced by host OS
tbxface-0117 [03] acpi_load_tables : ACPI Tables successfully acquired
Parsing all Control Methods:................................................................................................................................................ Table [DSDT] - 664 Objects with 45 Devices 144 Methods 27 Regions
ACPI Namespace successfully loaded at root c0428bbc
evxfevnt-0092 [04] acpi_enable : Transition to ACPI mode successful
evgpe-0416 [06] ev_create_gpe_block : GPE Block: 2 registers at
0000000000001020
evgpe-0421 [06] ev_create_gpe_block : GPE Block defined as GPE0 to GPE15
Executing all Device _STA and_INI methods:........<3>ACPI breakpoint: Executed
AML Breakpoint opcode
.....................................
45 Devices found containing: 45 _STA, 5 _INI methods
Completing Region/Field/Buffer/Package
initialization:............................................................
Initialized 18/27 Regions 0/0 Fields 21/21 Buffers 21/21 Packages (664 nodes)
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 5 7 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 10, enabled at IRQ 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 *9 10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 *10)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 1)
I've downloaded and installed the latest BIOS from HP and that didn't change anything. I also followed the instructions on fixing my dsdt table and put that in the kernel but that didn't change anything either.
Steps to reproduce: Just boot :)
Everything appears fine until it gets to the point around where acpid starts
- at that point the system slows down immensely and then freezes a few minutes later. If I prevent acpid from starting then it freezes on the next program, the alsa setup. If I take that out then it freezes on lircd. When it does freeze the hard drive light stays on solid but the hard drive makes no noise. The system is totally unresponsive and requires a hard reset.
Quoted 7 lines · * Martin J. Bligh ([email protected]) wrote:
http://bugme.osdl.org/show_bug.cgi?id=529
Summary: ACPI under 2.5.50+ (approx) locks system hard during
bootup
Kernel Version: 2.5.50 - 2.5.66 at least. Trying to find the last one
that work
Try >= 2.5.64. It has a derive_pci_id ACPI patch that fixed this problem for me[*].
[email protected], 2003-02-26 13:47:36-08:00, [email protected]
ACPI: Fix derive_pci_id (Ducrot Bruno, Alvaro Lopez)
thanks,
-chris
[*] There is still a case where a warm reboot from a 2.4 kernel will hang, but warm reboot from 2.5 kernel, or cold boot no longer hangs.
Signature · 1 line
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
I've tried every kernel I could get to build up through 2.5.66 and nothing changed. Same behavior every time
Also, I can get them all to boot into single user mode. I'm going to check if the hang is caused by the loading of the alsa modules (which run on the same interrupt) or something else.
: Try >= 2.5.64. It has a derive_pci_id ACPI patch that fixed this problem : for me[*].
:
: [email protected], 2003-02-26 13:47:36-08:00, [email protected]
: ACPI: Fix derive_pci_id (Ducrot Bruno, Alvaro Lopez)
:
: thanks,
: -chris
:
: [*] There is still a case where a warm reboot from a 2.4 kernel will : hang, but warm reboot from 2.5 kernel, or cold boot no longer hangs. : --
: Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
Signature · 3 lines
Matthew Harrell I love defenseless animals, Bit Twiddlers, Inc. especially in a good gravy. [email protected]
Quoted 6 lines · Matthew Harrell
I've tried every kernel I could get to build up through 2.5.66 and nothing changed. Same behavior every time
Also, I can get them all to boot into single user mode. I'm going to check if the hang is caused by the loading of the alsa modules (which run on the same interrupt) or something else.
The only way I can boot recent 2.5 kernels is to make sure my BIOS does nothing that even smells like ACPI. The only response I got so far on the lkml is "disable acpi support" and "disable apic support". The only conclusion I can make is that the ACPI support in 2.5 is buggy enough to prevent 2.5 to emerge into 2.6 for a long time from now, and unfortunately nobody seems to care. I detected big IRQ / ACPI / APIC trouble since about 2.5.44 - 2.5.53, and nothing has changed since.
NFI, I just don't understand that a core problem that prevents me from booting 2.5 kernels, is noticed by so few others that it is able to remain unfixed for so long.
Jos
I sympathize since I've been feeling the same way. When I mentioned it to Andrew in response to another ACPI problem I saw posted he recommended I send it via bugzilla to see if more people will pay attention then.
But, in the ACPI team's defense, I also have about three other computers with ACPI that do work fine and I've seen a number of other people on the ACPI list without problems. In my case it's annoying since it's my laptop which has the problem and that's the only one that I really care about when it comes to ACPI.
I suggest you read through my initial email and see if you find anything unusually different in your setup. I'm not positive since I'm new to bugzilla but if you do have anything different that you notice then go to bugzilla.kernel.org under bug 529 and add on to the bug report. Sounds like the more info the better for this bug
: The only way I can boot recent 2.5 kernels is to make sure my BIOS does : nothing that even smells like ACPI. The only response I got so far on the : lkml is "disable acpi support" and "disable apic support". The only : conclusion I can make is that the ACPI support in 2.5 is buggy enough to : prevent 2.5 to emerge into 2.6 for a long time from now, and unfortunately : nobody seems to care. I detected big IRQ / ACPI / APIC trouble since about : 2.5.44 - 2.5.53, and nothing has changed since.
:
: NFI, I just don't understand that a core problem that prevents me from booting : 2.5 kernels, is noticed by so few others that it is able to remain unfixed : for so long.
Signature · 3 lines
Matthew Harrell The perversity of the universe Bit Twiddlers, Inc. tends to a maximum. [email protected]
Quoted 10 lines · Matthew Harrell
I sympathize since I've been feeling the same way. When I mentioned it to Andrew in response to another ACPI problem I saw posted he recommended I send it via bugzilla to see if more people will pay attention then.
But, in the ACPI team's defense, I also have about three other computers with ACPI that do work fine and I've seen a number of other people on the ACPI list without problems. In my case it's annoying since it's my laptop which has the problem and that's the only one that I really care about when it comes to ACPI.
Quoted 5 lines
I suggest you read through my initial email and see if you find anything unusually different in your setup. I'm not positive since I'm new to bugzilla but if you do have anything different that you notice then go to bugzilla.kernel.org under bug 529 and add on to the bug report. Sounds like the more info the better for this bug
I sure will. My plain Asus P2L97-DS with plain PII 333 SMP, plain Intel 440 LX, plain Soundblaster Live, plain 3Com 3C905C and plain Matrox G400 has no trouble at all with 2.4 kernels, all IRQ lines claimed succesfully. With recent 2.5 kernels it is simply: IDW ! No fancy strange laptop, no "made in antarctica" chipset, only a SMP configuration on one of the most used chipsets in the world, and yes, I enabled MPS 1.4 support for I had trouble with shared IRQs. (FWIW: MPS 1.4 also reroutes interrupts)
Jos
Quoted 11 lines · Jos Hulzink
The only way I can boot recent 2.5 kernels is to make sure my BIOS does nothing that even smells like ACPI. The only response I got so far on the lkml is "disable acpi support" and "disable apic support". The only conclusion I can make is that the ACPI support in 2.5 is buggy enough to prevent 2.5 to emerge into 2.6 for a long time from now, and unfortunately nobody seems to care. I detected big IRQ / ACPI / APIC trouble since about 2.5.44 - 2.5.53, and nothing has changed since.
NFI, I just don't understand that a core problem that prevents me from booting 2.5 kernels, is noticed by so few others that it is able to remain unfixed for so long.
Can you send me a boot log and your config file? Also a bootlog from 2.4 would be nice.
Zwane
Signature · 1 line
function.linuxpower.ca