I have a Sony Vaio P laptop running F11. It's always had the problem whereby the boot process freezes periodically until you press a key (same at shutdown), and the clock consistently loses time. Matthew Garrett pointed me to the nohz=off kernel parameter, which indeed fixes (or works around) the problem. With nohz=off set, boot is smooth and system clock does not lose time. This has happened with all Fedora 11 kernels, the system is currently on the 2.6.29.6-217.2.3.fc11 . I will attach dmesg and lspci output.
Created attachment 357058 [details] dmesg output on affected system
Created attachment 357059 [details] lspci -nn output on the affected system
See also bug 536721 describing an adversly affected installation with anaconda images using kernel-2.6.31.5-127.fc12.i686.
Someone seems to have fixed this while I wasn't looking - the latest F11 kernel and F13 kernel both seem to boot fine without nohz=off. Closing. I'll re-open if it recurs. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
It blocks here the install process of F13 beta (i686) on a Dell Inspiron 1420 laptop. Passing nohz=off eliminates the problem.
Every instance of this problem on a different piece of hardware is a different bug; fixing this for the Vaio P won't necessarily fix it for your Dell. Please open a new bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I should probably re-open this; it started happening again on my P soon after I thought it was fixed. Dunno why it worked for that short period of time, but I'm back to needing nohz=off.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
still valid with f13, just realized I need to re-open. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Can you get the dmesg output without nohz=off from as recent a kernel as possible? This doesn't look good: Fast TSC calibration failed TSC: Unable to calibrate against PIT TSC: using PMTIMER reference calibration What is in these files? /sys/devices/system/clocksource/clocksource0/{available,current}_clocksource
[adamw@vaio ~]$ cat /sys/devices/system/clocksource/clocksource0/{available,current}_clocksource hpet acpi_pm hpet Booted without nohz=off at present, kernel 2.6.33.6-147.2.4.fc13.i686. I booted a few times and didn't get pauses, but I did get them on shutdown one time. Last time I tried with nohz=off I got no pauses for a few boots and thought it was solved - see above - but then they started coming back a few boots later. dmesg output will be attached shortly.
Created attachment 439454 [details] updated dmesg output with 2.6.33.6-147.2.4.fc13.i686
I added attachment 439524 [details] in https://bugzilla.redhat.com/show_bug.cgi?id=536721#c22 from a boot of 2.6.33.6-147.2.4.fc13.i686 without nohz=off on my laptop. More details in that comment.
Can you try 2.6.36-rc2 from rawhide? Upstream is not interested in anything older than yesterday's kernel...
right, because it will have been magically fixed by pixies in the mean time (rolleyes). i'll try and do that, yeah.
dmesg output is somewhat different in 2.6.36-rc2. Not sure yet if it works any better (would have to try it for a while to see, and I can't because psb doesn't build against 2.6.36, though I guess I should look at fixing that).
Created attachment 441011 [details] dmesg from 2.6.36-rc2
(In reply to comment #12) > [adamw@vaio ~]$ cat > /sys/devices/system/clocksource/clocksource0/{available,current}_clocksource > hpet acpi_pm > hpet > Does booting with "clocksource=acpi_pm" work any better?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.