Bug 319441 - kernel chooses wrong clock source
Summary: kernel chooses wrong clock source
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 321621 322411 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-04 23:56 UTC by Gordon Messmer
Modified: 2008-04-06 18:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-06 18:43:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output after waiting for bad clock source (15.03 KB, text/plain)
2007-10-04 23:56 UTC, Gordon Messmer
no flags Details

Description Gordon Messmer 2007-10-04 23:56:42 UTC
Description of problem:
During boot on my IBM X40 laptop, the installer hangs at "running /sbin/loader",
and goes no further for several minutes.  During this time, console 3 lists a
number of modules loaded, and several inserted, ending with /tmp/loop.ko. 
Console 4 has normal looking kernel messages ending with:

<4>loader used greatest stack depth: 2296 bytes left
<6>loop: module loaded 

After several minutes, the installation process continues.

dmesg reports "Clocksource tsc unstable (delta = -139639622012 ns) " after
"loop: module loaded".  If I boot the system with the kernel option
"clocksource=acpi_pm", I don't have this problem.


Version-Release number of selected component (if applicable):
2.6.23-0.214.rc8.git2.fc8

How reproducible:
Always

Comment 1 Gordon Messmer 2007-10-04 23:56:42 UTC
Created attachment 216831 [details]
dmesg output after waiting for bad clock source

Comment 2 Chuck Ebbert 2007-10-09 21:38:20 UTC
*** Bug 322411 has been marked as a duplicate of this bug. ***

Comment 3 Patrick Mowry 2007-10-12 02:10:35 UTC
*** Bug 321621 has been marked as a duplicate of this bug. ***

Comment 4 Christopher Brown 2008-02-03 22:38:31 UTC
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. Could you tell me if
you are still having problems 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.

Comment 5 Gordon Messmer 2008-02-05 01:30:03 UTC
I *think* this was resolved before the final F8 release.  If it comes up when I
test F9, I'll reopen this bug.

Comment 6 Christopher Brown 2008-02-05 01:42:14 UTC
Please do Gordon. I'm closing WORKSFORME at the moment - you can also test with
a 2.6.24-based kernel from rawhide if you wish.

Comment 7 Daniel Qarras 2008-02-16 20:44:03 UTC
Please, don't shoot the messenger, but I was just hit by this when I booted with
Fedora 9 Alpha 1 DVD. Symptoms are exactly the same as in Comment 1 and in my
earlier report in Bug 322411.

Strangely enough, there has been no such problems with any Fedora 8 kernels
after its installation.

Comment 8 Daniel Qarras 2008-02-16 20:44:56 UTC
Oh, well, I can't reopen this bug. I'll reopen my earlier Bug 322411 instead, then.

Comment 9 Jon Stanley 2008-02-16 21:27:21 UTC
*** Bug 322411 has been marked as a duplicate of this bug. ***

Comment 10 Jon Stanley 2008-02-16 21:28:23 UTC
Re-opening per comment #8, changing version to rawhide

Comment 11 Daniel Qarras 2008-04-06 12:17:35 UTC
I'm happy to inform that this bug is not present in Fedora 9 Beta!

Comment 12 Jon Stanley 2008-04-06 18:43:08 UTC
Awesome!  I'll go ahead and close this bug then.


Note You need to log in before you can comment on or make changes to this bug.