Bug 8061 - mageia3a2,tsc: Fast TSC calibration failed
Summary: mageia3a2,tsc: Fast TSC calibration failed
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Low minor
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-13 11:40 CET by episteme promeneur
Modified: 2013-05-02 19:07 CEST (History)
2 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description episteme promeneur 2012-11-13 11:40:31 CET 
Description of problem:


during pc boot iahve this message :

tsc: Fast TSC calibration failed
Comment 1 episteme promeneur 2012-11-13 12:13:50 CET 
complete group of messages concerning tsc :

...
hpet clockevent registered
[    0.000000] tsc: Fast TSC calibration failed
[    0.000000] tsc: PIT calibration matches HPET. 1 loops
[    0.000000] tsc: Detected 2611.622 MHz processor
[    0.000000] tsc: Marking TSC unstable due to TSCs unsynchronized
[    0.002004] Calibrating delay loop (skipped), value calculated using timer frequency.. 5223.24 BogoMIPS (lpj=2611622)
[    0.002007] pid_max: default: 32768 minimum: 301
...
Comment 2 Thierry Vignaud 2012-11-14 10:40:20 CET 
This is just a warning

Priority: Normal => Low
Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => WONTFIX
Assignee: bugsquad => tmb
Source RPM: (none) => kernel
Severity: normal => minor

Comment 3 Kristoffer Grundström 2013-05-02 18:35:06 CEST 
I don't intend to open this, but I see this as soon as I get a picture when booting the installation of the RC-version.

What are warnings there for?

Just wondering.

CC: (none) => kristoffer.grundstrom1983

Comment 4 Thierry Vignaud 2013-05-02 19:07:41 CEST 
It means that the kernel don't trust the Time Stamp Counter as a reliable "clock".
See http://en.wikipedia.org/wiki/Time_Stamp_Counter
Note You need to log in before you can comment on or make changes to this bug.