Bug 175264
| Summary: | kernel lockup without "noapic acpi=off" parameters | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Minesh Patel <minesh> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | acpi-bugzilla, jonstanley, pfrields, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | MassClosed | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-20 04:39:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Minesh Patel
2005-12-08 11:43:30 UTC
can you remove the 'quiet' from the boot command line, and find out where exactly it hangs ? The last line or two before the hang may give clues as to where the problem is. It locks up after
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
After that there are acpi lines surrounded by < > if just the "noapic"
kernel parameter is used. if just "acpi=off" is used then there are
thread_helper lines surrounded by < >.
I will try to get more details in a few weeks
there's a bunch of acpi fixes in the test kernel at http://people.redhat.com/davej/kernels/Fedora/FC4 too. It'd be good to know if that fixes this problem. I've tested the 2.6.15-1.1781_FC4smp test kernel and it still crashes during
startup
grub entry
title Fedora Core (2.6.15-1.1781_FC4smp) REDHAT TEST
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-1.1781_FC4smp ro root=LABEL=/1 rhgb
initrd /boot/initrd-2.6.15-1.1781_FC4smp.img
last line shown during boot up is
<c01347a2> call_usermode_helper+0x2e-0x38
I need the whole dump, not just the last line. (Preferably after booting with vga=791 to get more lines on the screen). Even a photo (if you have a digital camera) would be acceptable. Created attachment 123241 [details]
error during kernel 2.6.15-1.1781_FC4smp startup
error displayed during kernel 2.6.15-1.1781_FC4smp
Created attachment 123242 [details]
error during kernel 2.6.15-1.1781_FC4smp startup
error displayed during kernel 2.6.15-1.1781_FC4smp boot up
I've added a photo of the error during boot up with the 2.6.15-1.1781_FC4smp test kernel. The vga=791 option caused a blank screen during boot up when I added it. Please attach the dmesg -s64000 output from the latest kernel that booted properly without any cmdline workarounds. Shooting in the dark.... Does it boot with only "acpi=noirq" or "pci=noacpi", or "maxcpus=1" or "noapic"? (In reply to comment #9) > Please attach the dmesg -s64000 output from the latest kernel that > booted properly without any cmdline workarounds. > > Shooting in the dark.... > Does it boot with only "acpi=noirq" or "pci=noacpi", or "maxcpus=1" > or "noapic"? > Hello, I currently cannot find a kernel that boots with no command line workarounds. I've tried the ones listed in initial comment and the 2.6.15-1.1781_FC4smp test kernel. I will try those parameters out and add the results soon. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. testing different parameters with kernel-smp-2.6.15-1.1830_FC4.i686 "acpi=noirq" = crashes, last lines are simple boot flag at 0x7d set to 0x1 apf bios not found "pci=noacpi" = crashes "maxcpus=1" = booted,dmesg attached "noapic" = crashes,memory dump booting with no parameters = crashed, last line is acpi:using ioapic interrupt routing Created attachment 124385 [details]
dmesg output from kernel-smp-2.6.15-1.1830_FC4.i686 with "maxcpus=1" parameter
*** Bug 181769 has been marked as a duplicate of this bug. *** [This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. (this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug. |