Bug 205090
| Summary: | FC5 2.6.17-1.2174 Hangs on Boot on ASUS M2NPV-VM Motherboard | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Khoa Ton <khoa> | ||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5 | CC: | cochranb, jimmollmann, khoa, pfrields, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-11-20 19:09:41 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
Khoa Ton
2006-09-04 01:46:17 UTC
Oops, I made a mistake in the problem kernel version throughout this report. It should be 2.6.17-1.2471 and NOT 2.6.17-1.7124 due to mental transposition and subsequent cut-and-paste! Is it possible to change this bug report to reflect the correct kernel revision, or should I resubmit? Sorry again, that's kernel version 2.6.17-1.2174. The hang was due to some ACPI related interaction and the new 2.6.17-1.2174 kernel. I ran with: pci=noacpi and the system booted! Based on Stanton Finley's writeup at: http://stanton-finley.net/kernel-parameters.txt the above option instructs the kernel not to use ACPI for IRQ routing or for PCI scanning. I don't know what the ramifications of setting this kernel parameter are, aside from bypassing the hang... I'd like to mention that the motherboard being used is a Socket AM2 board. Hopefully, Khoa will create an attachment of his dmesg output here so more information is available. Bob Thanks Bob. Here are the last lines on the console at the hang (typed in manually): Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API Loading keyring - Added public key D4AD441F6DB3F282 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) _ The last "_" represents the blinking cursor There are no dmesg output available in the case that the kernel hangs. Created attachment 135523 [details]
Here is the dmesg output for successful boot with pci=noacpi boot parm.
Here is the dmesg output for successful boot with pci=noacpi boot parm.
Changing to proper owner, kernel-maint. I see the same failure. But "pci=noacpi" does not let my system boot. I have a SATA HD. The last kernel that boots is kernel-2.6.16-1.2133_FC5.x86_64.rpm. The first that does not is kernel-2.6.17-1.2139_FC5.x86_64.rpm. I notice that this: ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE000 irq 16 ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE008 irq 16 changes to "irq 153" when I boot 2174 with "pci=noacpi". Also see Andy Chittenden's thread on linux-kernel - http://www.uwsg.iu.edu/hypermail/linux/kernel/0608.3/0225.html 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. I can confirm the 2200.fc5 kernel solves at least one problem I didn't list in this bug but did in a separate bug: the kernel no longer seems to "time out" on each unused SATA2 connection on my Asrock 939SLI32-eSATA2 motherboard. I don't know if this solves Khoa's problem, but it does solve mine. Thanks, Dave! 2.6.18-1.2200.fc5 does boot. 2.6.18-1 does not. I had encountered the same problem during installation of FC-6-x86_64-DVD.iso on my PC with the same motherboard. During loading from DVD boot process stops at line "io scheduler cfq registered (default)". But I don't know exactly what kernel is used there. they're different enough that it deserves a separate bug. as the original reporter hasn't responded here, but Jim mentioned that 2.6.18-1.2200.fc5 boots for him, I'll close this out. |