Bug 462156
| Summary: | Kernel 2.6.26.3-14 hangs fairly early in boot | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephen P. Schaefer <sschaefer> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 8 | CC: | danimal, dkovalsk, fredrik, ivo, mjt, sclark46 | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 2.6.26.6-79.fc9 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2008-10-23 16:38:04 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
Stephen P. Schaefer
2008-09-13 02:25:50 UTC
I'm experiencing exactly the same problem on two different laptops. Booting with acpi=off works, but a laptop is pretty broken without acpi. The same laptop has worked with all previous fedora-9 and fedora-8 kernels. Other boot options that make the machine boot are acpi=ht as well noapic I've tried booting with noisapnp which hangs a little later after Synaptics Touchpad, model:1, fw: 6.2, id: 0x1a0b1, caps: 0xa04713/0x200000 input: SynPS/2 Synaptics touchPad as /devices/platform/i8042/serio2/input/input6 The least intrusive boot option that makes the machine boot seems to be clocksource=hpet I have an Asus Laptop - Core 2 Duo and am experiencing the exact same problem - boot hangs right after isapnp: No Plug & Play device found Using clocksource=hpet allowed my laptop to boot I wonder, does it happen with CONFIG_PARAVIRT=y? If so, does the system boot ok with CONFIG_PARAVIRT=n? Well, probably unrelated, but who knows... I've a mysterious problem with several Asus motherboards, their recent BIOSes and 2.6.26.5, but only with CONFIG_PARAVIRT enabled. It hangs at a different place, right before choosing timer source. I don't know - I built a vanilla kernel 2.6.26.5 with the config from fedora and it hung also. I then built a vanilla kernel 2.6.27-rc7 with the fedora config and it booted without having to add clocksource=hpet. I've also been bitten by the no-boot-thingy, Lenovo T60, Core2Duo. I'll add a screenshot tomorrow (hopefully) and gladly any other information you may find useful :-) So using clocksource=hpet does no difference. Adding a screenshot where the kernel actually hangs. Let me know what output do you need from me to better diagnose the problem. Created attachment 318093 [details]
Photo of the display/screen where the boot hangs
I get a hang at boot with both 2.6.26 kernels on fedora 9. See attached screenshot. Both 2.6.25 kernels (fedora 9) and fedora 10 beta kernel boot fine. This is on an IBM Intellistation M Pro (P4-3.2) Created attachment 319284 [details]
Screenshot of kernel hanging at boot (Intellistation M Pro)
(In reply to comment #9) > So using clocksource=hpet does no difference. Adding a screenshot where the > kernel actually hangs. Let me know what output do you need from me to better > diagnose the problem. Did you try 2.6.26.5-45? This kernel has a set of timer fixes that will be in 2.6.26.6. The next kernel, based on 2.6.26.6, will have more timer fixes. (In reply to comment #13) > (In reply to comment #9) > > So using clocksource=hpet does no difference. Adding a screenshot where the > > kernel actually hangs. Let me know what output do you need from me to better > > diagnose the problem. > > Did you try 2.6.26.5-45? This kernel has a set of timer fixes that will be in > 2.6.26.6. The next kernel, based on 2.6.26.6, will have more timer fixes. My rig (screenshot attached) hangs at both 2.6.26 kernels released for fedora 9, including 2.6.26.5-45. The fedora 10 beta kernel boots. Comment on attachment 319284 [details]
Screenshot of kernel hanging at boot (Intellistation M Pro)
Screenshot is from trying to boot
kernel-2.6.26.5-45.fc9
This should be fixed in 2.6.26.6 Actually I'm able to boot with 2.6.26.5-28.fc8. [dkovalsk@kovinek ~]$ uname -a Linux kovinek 2.6.26.5-28.fc8 #1 SMP Sat Sep 20 09:32:58 EDT 2008 i686 i686 i386 GNU/Linux Thanks for the fix! Unfortunately, my ASUSTek Z84J continues to require "clock=hpet" as a kernel argument in order to boot with 2.6.26.5-28.fc8 (Thank you, Ivo, for the suggestion). kernel-2.6.26.6-46.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/kernel-2.6.26.6-46.fc8 kernel-2.6.26.6-71.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/kernel-2.6.26.6-71.fc9 kernel-2.6.26.6-46.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/kernel-2.6.26.6-46.fc8 kernel-2.6.26.6-49.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/kernel-2.6.26.6-49.fc8 kernel-2.6.26.6-79.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-8929 Doesn't make any difference on my rig. It still hangs at the same spot. The fedora 10 kernels all work (2.6.27.x) 2.6.26.6-79 solves the problem for me. Interestingly it chooses hpet as clocksource by default. As far as I recall 2.6.25.x kernel used to choose acpi_pm. However, the new kernel boots without problems using either hpet or acpi_pm. kernel-2.6.26.6-49.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. kernel-2.6.26.6-79.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. As stated in comment #24 it doesn't solve the problems on my rig. See the attached screenshot. How soon should I see the update? [sps@thyrsus-laptop2 ~]$ sudo yum install kernel-2.6.26.6 Setting up Install Process Parsing package install arguments No package kernel-2.6.26.6 available. Nothing to do (In reply to comment #29) > How soon should I see the update? > > [sps@thyrsus-laptop2 ~]$ sudo yum install kernel-2.6.26.6 > Setting up Install Process > Parsing package install arguments > No package kernel-2.6.26.6 available. It's kernel-2.6.26.6-79.fc9 . And erase the one that won't boot first, if you haven't done that already. Since my last comment, the update became visible to me: [sps@thyrsus-laptop2 ~]$ sudo yum install kernel-2.6.26.6 Password: livna | 2.1 kB 00:00 primary.sqlite.bz2 | 499 kB 00:03 http://mirror.cogentco.com/pub/linux/fedora/linux/releases/8/Everything/i386/os/repodata/repomd.xml: [Errno 12] Timeout: <urlopen error timed out> Trying other mirror. fedora | 2.1 kB 00:00 updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 Setting up Install Process Parsing package install arguments Package kernel-2.6.26.6-49.fc8.i686 already installed and latest version Nothing to do ...and I'm happy to report that it boots without any extra clock= options. After being pushed to stable 2.6.26.6-79.fc9.i686 solves the problem for me. The rig boots again. |