Bug 379651
Summary: | toshiba laptop: Timer interrupt error on reboot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Derkjan de Haan <haanjdj> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | andrew.jarcho, chris.brown, moneta.mace |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.23.14-115.fc8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-02-08 00:33:27 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: |
Description
Derkjan de Haan
2007-11-13 10:29:36 UTC
I'm seeing the same thing on two Toshiba 5105-s607. They used to run FC6 with no error on reboot. With F8, this error appears requiring a power cycle for a successful boot. I just ran some reboot testing, and found that I can prevent the error by booting with kernel parameter: clocksource=pit Of course, wakeups per second went from about 200 to 1000. I tried hpet with hires=off, and that had no effect on the timer error. Nor did acpi_pm. Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. This should now be resolved - can you verify with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Yes, for me it's solved with the latest kernel. I kind of noticed it by accident though, because nothing in the kernel changelog indicated there had been fixes in this area. Confirming; booting 2.6.23.14-115.fc8 without clocksource=pit no longer causes a problem. I'd like to second that it would be nice if the changelog referenced bugs that were thought to be fixed, as I also missed that this was the case in the current kernel. There was no package announcement for this kernel either - I had to check koji for the changelog. I'm getting the same behavior on reboot ("timer interrupt error" message, then a hang after the message "Uncompressing Linux... Ok, booting the kernel"). After a cold boot, though, the system behaves normally. The kernel is 2.6.25.11-60 fc8 running on a Toshiba A45-S250 with a brand new hard drive. fc8 is the only OS on this machine. |