Bug 5221
| Summary: | Regression: 2.6.13 boot hang unless acpi=noirq -- 2.6.12.6 worked - Compaq nx8220 | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Pavel Alexeev (al_pavel) |
| Component: | Config-Interrupts | Assignee: | Len Brown (lenb) |
| Status: | REJECTED INVALID | ||
| Severity: | normal | CC: | acpi-bugzilla, kernel, kernelbugs, me, rudolph, xoen |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.13.1, 2.6.14-rc1 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
acpidump, 2.6.12.6
dmesg -s64000 output, 2.6.12.6 dmesg -s64000 output, 2.6.14-rc2-git3 lspci -vv output, 2.6.12.6 lspci -vv output, 2.6.14-rc2-git3 /proc/interrupts, 2.6.12.6 /proc/interrupts, 2.6.14-rc2-git3 dmesg through serial console of failed boot dmesg on 2.6.14-rc4 copy of DMESG file lspci.txt from same machine |
||
|
Description
Pavel Alexeev
2005-09-10 16:18:39 UTC
Notebook: nx 8220, model PY518ET. The kernel 2.6.13.1 boots successfully if ACPI is not compiled in. if you boot the CONFIG_ACPI=y kernel with "acpi=off" then it works? if yes, how about with just "pci=noacpi"? if yes, how about with just "acpi=noirq"? how about with "pnpacpi=off"? When you build the 2.6.13 kernel, you first run "make oldconfig" on the working 2.6.12 .config? > if you boot the CONFIG_ACPI=y kernel with "acpi=off" then it works? Yes, it works > if yes, how about with just "pci=noacpi"? Yes, it works (but hangs while rebooting: Remounting rootfilesystem read-only. Rebooting. Restarting system. . ) > if yes, how about with just "acpi=noirq"? Yes, it works, but hangs while rebooting. > how about with "pnpacpi=off"? It hangs. > When you build the 2.6.13 kernel, you first run "make oldconfig" on the working 2.6.12 .config? make oldconfig on the working 2.6.12 ".config". P.S. I can attach dmesg output and my .config, when you need it (which kernel with which option?). The same problem on 2.6.14-rc1-git1 (14.09.2005, 09:01:00) please attach the dmesg -s64000 output from 2.6.12.working, along with the /proc/interrupts and the output from lspci -vv Please attach the output from acpidump, available in pmtools here: http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/ Please attach the dmesg and /proc/interrupts resulting from the latest kernel with the "acpi=noirq" cmdline workaround. Any chance you can also capture the "debug" console output from the failing 2.6.>12 boot, say with a serial console? Created attachment 6116 [details]
acpidump, 2.6.12.6
Created attachment 6117 [details]
dmesg -s64000 output, 2.6.12.6
Created attachment 6118 [details]
dmesg -s64000 output, 2.6.14-rc2-git3
Created attachment 6119 [details]
lspci -vv output, 2.6.12.6
Created attachment 6120 [details]
lspci -vv output, 2.6.14-rc2-git3
Created attachment 6121 [details]
/proc/interrupts, 2.6.12.6
Created attachment 6122 [details]
/proc/interrupts, 2.6.14-rc2-git3
> Any chance you can also capture the "debug" console output
from the failing 2.6.>12 boot, say with a serial console?
mmm... At first, i must learn what it is and how i can do it :) Where can i
read it? :)
This notebook does not have any COM-ports. *** Bug 5216 has been marked as a duplicate of this bug. *** I am also having the same problem described, on similar hardware. In my case, the laptop is an nc6220 which does have a serial port. What diagnostics can I provide? Could you please capature the dmesg though the serial port in the failure case? This will help us compare the dmesg unser working/unworking cases, so we can find clues. You can find the document about how to use serial console at kernel source/Documentation/serial-console.txt Created attachment 6192 [details]
dmesg through serial console of failed boot
As requested, serial console output of 2.6.14-rc2-git6 on nc6220 that fails to
boot with acpi turned on
This is really quick! Does the system work with lapic with acpi=on? Oops, I mean does the system work with noapic but with acpi=on? booting with noapic made no difference, boot failed in exactly the same place. I've also noticed that I have the kacpid 100% CPU problem when booting with options that do result in a successful boot, that is acpi=off -> ok pci=noacpi -> 100% kacpid acpi=noirq -> 100% kacpid on the above kernel. I've realised that my previous observations about kacpid are not properly a regression - they occur with 2.6.12 as well, so don't really belong in this bug report (more likely, they belong in something like #3686). Sorry. I don't have this kacpid-related problem (100% CPU usage) on my nx8220, under neither 2.6.12.6 nor 2.6.14-rc3-git3. Does the patch at https://bugzilla.novell.com/show_bug.cgi?id=116763 work? Yes, this patch works for me. The kernel 2.6.14-rc4 boots successfully (but hangs when rebooting). Created attachment 6277 [details]
dmesg on 2.6.14-rc4
dmesg on 2.6.14-rc4
patch also works for me. I am also seeing the same issue with reboots (i.e, the system displays "restarting system" and then hangs) as Pavel. looks like the reboot issue is logged as a separate bug, 5396. For me the same. 2.6.14-rc4 with patch applied boots fine on my HP Compaq nx 8220. (I did not try 2.6.14-rc4 without the patch yet.) The reboot problems on my machine are "sometimes", and also with 2.6.12.6. Markus I have never any reboot-related problems with 2.6.12.6. This is the kernel i use every day since at least 03.09.05. The full model number of my laptop is: Compaq nx8220 PY518ET#ABD, BIOS: 68DTV Ver. F.0A, 04/28/2005 So, how do we get this patch into the official kernels now? As I can see from the 2.6.14-rc5 changelog, it is not included yet. The reboot issue can be handled with kernel option reboot=bios. I checked all reboot= options and this one is the only one working. 2.6.15-rc2 also does not include the ACPI fix from https://bugzilla.novell.com/ show_bug.cgi?id=116763 - now I ask again: What shall we do to get this patch into mainstream kernel? Downstream bug: http://bugs.gentoo.org/112601 applied to acpi-test shipped in linux-2.6.15-rc5 -- closing. Created attachment 7785 [details]
copy of DMESG file
Copy of DMESG file
Kernel 2.6.16-1.2080_FC5 showing same symptoms as this bug. IBM Thinkpad A30P with docking station attached. from DMESG (attached) PCI: Cannot allocate resource region 7 of bridge 0000:02:03.0 PCI: Cannot allocate resource region 8 of bridge 0000:02:03.0 PCI: Cannot allocate resource region 9 of bridge 0000:02:03.0 System won't boot properly about 50% of the time (locks during boot) System won't restart properly about 50% of the time (requires power cycle to reset) If you want any other files or for me to try anything please let me know. Paul Created attachment 7787 [details]
lspci.txt from same machine
This is the lspci output from the same machine
Having read extensively on this since posting it looks like a 'sort of' known bug. http://marc.theaimsgroup.com/?l=linux-acpi&m=114073385031547&w=2 I can't yet tell if these patches were included in the version I'm currently using so will read further to see if they have been. The thought occured to me as well that the build was done while the docking station was attached, I'll do another build on the same machine without the docking station is attached and report back. Paul If the problem is still present in 2.6.17-rc4, please reopen. 2.6.18-rc5 works fine on my hardware (hp nc6220 laptop) |