[Bug 258400] New: No boot with acpi - booting without acpi lets system hang after short while
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 Summary: No boot with acpi - booting without acpi lets system hang after short while Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: karl-heinz_tm@hotmail.de QAContact: qa@suse.de Machine is Sony Z600TEK laptop (P3-700). Boots ok with original 10.2 kernel (2.6.18.2). After update to 2.6.18.8, machine won't boot unless with acpi=off parameter. Once booted, machine will hang after a few minutes. Hangs could be in relation with bcm43xx wireless driver (suspect from related info from bcm43xx development list), but couldn't verify this. Same behaviour experienced also with opensuse 10.1. Have now returned to 2.6.18.2 and everything is fine again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |trenn@novell.com |maintainers@forge.provo.nove| |ll.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from trenn@novell.com 2007-03-29 12:16 MST ------- 10.1 and 10.2 (but only update kernel 2.6.18.8) does not boot? But 10.2 2.6.18.2 is working? Could you try to boot in text mode (you can use installation disk and choose text instead of graphics resolution) And tell us what the last lines are before it hangs. You may want to shoot a photo using your mobile/digicam if you have one... Can you also scroll up a bit and look out for any error/warning message that looks suspicious... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 ------- Comment #2 from karl-heinz_tm@hotmail.de 2007-03-29 13:33 MST ------- Yes, machine only boots properly with 10.2/2.6.18.2. Below's an excerpt from dmesg when the machine boots using 2.6.18.2 (what I am using right now). When it comes as far as talking about the floppy (last line below), it will boot for sure. The hangs in 10.1/10.2(2.6.18.8) occur either at the line "ACPI: Assume root bridge [\_SB_.PCI0] bus is 0" or on one of the two previous or later ACPI statements. When I boot into 10.1 or 10.2/2.6.18.8 with acpi=off, I do a "tail -f /var/log/messages" but there is absolutely nothing there that would provide any hint - often the last log entry is minutes old when the freeze happens. Any other hint where I should look (I'm not an expert)? I suspect there could be a link to the bcm43xx driver because I get lots of activity in the log when the card (4306 pcmcia) is plugged. Then again, I get these log entries in all environments - 10.1, 10.2/2.6.18.2 and 10.2/2.6.18.8 - and there are no freezes in 10.2/2.6.18.2. No clue where the difference is, however, I recall that ACPI is only active in the 10.2/2.6.18.2 situation. From the bcm43xx developers, I got a hint to switch to 2.6.18 when I inquired about these problems when running 10.1. Well, 2.6.18.2 did fix the issues but they apparently came back with 10.2/2.6.18.8. Hope this helps. Let me know what else I can do. Might have some time next weekend if there is any testing to do. -----------------excerpt from dmesg --------------------------------- Linux version 2.6.18.2-34-default (geeko@buildhost) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e8400 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000017ff0000 (usable) BIOS-e820: 0000000017ff0000 - 0000000017fff800 (ACPI data) BIOS-e820: 0000000017fff800 - 0000000018000000 (ACPI NVS) BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 383MB LOWMEM available. On node 0 totalpages: 98288 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 94192 pages, LIFO batch:31 DMI 2.1 present. Using APIC driver default IO/L-APIC allowed because system is MP or new enough ACPI: RSDP (v000 SONY ) @ 0x000f6bb0 ACPI: RSDT (v001 SONY Z3 0x20010512 PTL 0x00000000) @ 0x17ffc1c4 ACPI: FADT (v001 SONY Z3 0x20010512 PTL 0x000f4240) @ 0x17fff764 ACPI: BOOT (v001 SONY Z3 0x20010512 PTL 0x00000001) @ 0x17fff7d8 ACPI: DSDT (v001 SONY Z3 0x20010512 MSFT 0x01000007) @ 0x00000000 ACPI: PM-Timer IO Port: 0x8008 Allocating PCI resources starting at 20000000 (gap: 18000000:e7f80000) Detected 545.964 MHz processor. Built 1 zonelists. Total pages: 98288 Kernel command line: root=/dev/hda4 resume=/dev/hda3 splash=silent bootsplash: silent mode. Local APIC disabled by BIOS -- you can enable it with "lapic" mapped APIC to ffffd000 (0130a000) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 383016k/393152k available (1697k kernel code, 9572k reserved, 968k data, 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 1092.91 BogoMIPS (lpj=2185827) Security Framework v1.0.0 initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000 CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to ffffe000. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed checking if image is initramfs... it is Freeing initrd memory: 2702k freed ACPI: Core revision 20060707 CPU0: Intel Pentium III (Coppermine) stepping 03 SMP motherboard not detected. Local APIC not detected. Using dummy APIC emulation. Brought up 1 CPUs migration_cost=0 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfd9ae, last bus=1 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 8000-803f claimed by PIIX4 ACPI PCI quirk: region 1040-104f claimed by PIIX4 SMB PIIX4 devres I PIO at 0398-0399 PIIX4 devres J PIO at 0398-0399 Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Embedded Controller [EC0] (gpe 9) interrupt mode. ACPI: PCI Interrupt Link [LNKA] (IRQs *9) ACPI: PCI Interrupt Link [LNKB] (IRQs 9) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 9) *0, disabled. ACPI: PCI Interrupt Link [LNKD] (IRQs 9) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 10 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report pnp: 00:01: ioport range 0x398-0x399 has been reserved pnp: 00:01: ioport range 0x4d0-0x4d1 has been reserved pnp: 00:01: ioport range 0x1040-0x104f has been reserved pnp: 00:01: ioport range 0x8000-0x804f could not be reserved PCI: Bridge: 0000:00:01.0 IO window: e000-efff MEM window: fd000000-febfffff PREFETCH window: 24000000-240fffff PCI: Bus 2, cardbus bridge: 0000:00:0c.0 IO window: 00001400-000014ff IO window: 00001800-000018ff PREFETCH window: 20000000-21ffffff MEM window: 22000000-23ffffff ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9 PCI: setting IRQ 9 as level-triggered ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9 PCI: Setting latency timer of device 0000:00:0c.0 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered Simple Boot Flag at 0x35 set to 0x1 Machine check exception polling timer started. BIOS strings suggest APM reports battery life in minutes and wrong byte order. apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) apm: overridden by ACPI. audit: initializing netlink socket (disabled) audit(1175202075.896:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Limiting direct PCI/PCI transfers. isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12ac Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Floppy drive(s): fd0 is 1.44M --------------------------------end-------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |karl-heinz_tm@hotmail.de ------- Comment #3 from trenn@novell.com 2007-03-30 02:27 MST -------
No clue where the difference is, however, I recall that ACPI is only active in the 10.2/2.6.18.2 situation I expect it's this. If other kernels boot without acpi, can you try acpi=force (without the other params above. Possibly also add noapic if it does not work on first attempt).
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 karl-heinz_tm@hotmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|karl-heinz_tm@hotmail.de | ------- Comment #4 from karl-heinz_tm@hotmail.de 2007-04-03 14:40 MST ------- Tested 2.6.18.8 (10.2 update kernel) with acpi=force, and this does the trick - I'm posting this comment running 2.6.18.8-0.1-default. Machine boots without any problems. Does this mean that 2.6.18.2 - using no boot parameters - actually doesn't (fully) use ACPI? I would have thought that ACPI gets used if no boot parameters are supplied, and acpi=force would only aggravate problems on machines that can't boot without acpi-"limiting" parameters (such as acpi=off, as posted in the bug report). Well, (as stated) I'm not a linux expert, I may have learned something new :-) Thanks so far. Will do some more testing during the next several days to see if the machine continues to reliably boot with acpi=force. Will post the results in a few days. P.S.: I did not try noapic, as already acpi=force as only command line parameter was successful. P.S.2: here are the acpi related messages from dmesg from a successful boot with acpi=force: BIOS-e820: 0000000017ff0000 - 0000000017fff800 (ACPI data) BIOS-e820: 0000000017fff800 - 0000000018000000 (ACPI NVS) ACPI: RSDP (v000 SONY ) @ 0x000f6bb0 ACPI: RSDT (v001 SONY Z3 0x20010512 PTL 0x00000000) @ 0x17ffc1c4 ACPI: FADT (v001 SONY Z3 0x20010512 PTL 0x000f4240) @ 0x17fff764 ACPI: BOOT (v001 SONY Z3 0x20010512 PTL 0x00000001) @ 0x17fff7d8 ACPI: DSDT (v001 SONY Z3 0x20010512 MSFT 0x01000007) @ 0x00000000 ACPI: PM-Timer IO Port: 0x8008 ACPI: Core revision 20060707 ACPI: bus type pci registered ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 8000-803f claimed by PIIX4 ACPI ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Embedded Controller [EC0] (gpe 9) interrupt mode. ACPI: PCI Interrupt Link [LNKA] (IRQs *9) ACPI: PCI Interrupt Link [LNKB] (IRQs 9) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 9) *0, disabled. ACPI: PCI Interrupt Link [LNKD] (IRQs 9) *0, disabled. pnp: PnP ACPI init pnp: PnP ACPI: found 10 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9 ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9 apm: overridden by ACPI. ACPI: (supports S0 S1 S3 S4 S5) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: Thermal Zone [ATF0] (46 C) ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9 ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9 ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 9 ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKC] -> GSI 9 (level, low) -> IRQ 9 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9 ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKA] -> GSI 9 (level, low) -> IRQ 9 ACPI: AC Adapter [ACAD] (on-line) ACPI: Battery Slot [BAT1] (battery present) ACPI: Power Button (CM) [PWRB] ibm_acpi: IBM ThinkPad ACPI Extras v0.12a ACPI Sony Notebook Control Driver v0.2 successfully installed ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ak@novell.com Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #5 from trenn@novell.com 2007-04-03 14:58 MST ------- Early ACPI BIOS implementations were very buggy, therefore there is a blacklist by date, to disable ACPI, even if present. The strange thing is: I wonder why this changed from 10.2 GM to 10.2 update kernel? Andi, Karl-Heinz needs acpi=force since last 10.2 update kernel, GM was running fine out of the box. Is this the result of getting the maxcpus=0 noapic bug reports under control? I couldn't find any patch in kernel.changes that points to ACPI blacklisting changes..., really strange. Sorry, but there is not much we can do. Fiddling with blacklisting is a bad idea in general for an update kernel. Some old, broken machines need acpi=off, some even older ones need acpi=force. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 ------- Comment #6 from ak@novell.com 2007-04-03 17:14 MST ------- 10.2 original had the blacklist CONFIG disabled by mistake. I fixed this in the update. If he needs acpi=force his bios year is wrong. If it's a common machine that could be handled with a dmi quirk (please add dmidecode output). If it's not common we probably won't bother to work around this, sorry. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 ------- Comment #7 from karl-heinz_tm@hotmail.de 2007-04-23 20:49 MST ------- With a lot more of experience on this machine with OS 10.2 now, I think it is really a machine (bios?) related problem. Whether it boots or not seems to be accidental and happens on all kernels I tried (10.2 original, 10.2 update, and 2.6.21 ... git6 (sorry don't have exact version as I can't be in linux now)). It also appears to be unrelated to the kernel parameters as - now after many many "test boots" - I couldn't find a reliable parameter set for booting any of the kernels, and I did actually occasionally succeed booting all of them *without any (acpi related) kernel parameter*. Strange that earlier I didn't seem to have the problems with 2.6.18.2 - making me believe that the issue was related to the kernel update - but that has changed now that I did a lot of more "booting tests". I guess it's appropriate to not bother any further. The machine is not a common one, I think - and OS 10.2 runs fine on my newer centrino machine :-). One strange thing - maybe that provides some insight that's useful to know in some respect: 2.6.18.x kernel always have their hangs at the places I described earlier. But 2.6.21...git6 produces another error message "unreliable clock source". Just to mention another piece of information - to those who know the evolution from older suse versions - releases before 10.0 didn't show this behaviour. In case it's still of interest after all this, I can still provide the output of dmidecode (just let me know if you want me to). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=258400 ------- Comment #8 from trenn@novell.com 2007-04-24 04:24 MST ------- Thanks for the detailed info. As this is a PIII-700, I doubt it would be worth debugging this...
Whether it boots or not seems to be accidental and happens on all kernels I tried These kind of bugs are often very hard to find
It possibly might come out to be real HW problem, if so many kernel versions are affected it at least looks like a very machine specific problem... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com