Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
"kernel time" is about fifteen minutes in the future
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
curmudgeon
Veteran
Veteran


Joined: 08 Aug 2003
Posts: 1537

PostPosted: Sun Jun 07, 2015 5:54 am    Post subject: "kernel time" is about fifteen minutes in the futu Reply with quote

I have never seen anything like this before.

Basically, everything from the kernel that goes into the syslog (/var/log/messages) is timestamped with a value about fifteen minutes ahead of the system (and actual) time.

Best to show an example (this was taken at about 21:54):

Code:

Jun 6 21:50:55 system kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1050404950)
Jun 6 21:50:55 system kernel: CPU3: Core temperature/speed normal
Jun 6 21:52:09 system kernel: mce: [Hardware Error]: Machine check events logged
Jun 6 21:36:42 system mcelog[23558]: Processor 3 heated above trip temperature. Throttling enabled.
Jun 6 21:36:42 system mcelog[23558]: Please check your system cooling. Performance will be impacted
Jun 6 21:36:42 system mcelog[23558]: Processor 3 below trip temperature. Throttling disabled
Jun 6 21:58:46 system kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1051624272)
Jun 6 21:58:46 system kernel: CPU1: Core temperature/speed normal
Jun 6 21:59:39 system kernel: mce: [Hardware Error]: Machine check events logged
Jun 6 21:44:12 system mcelog[23558]: Processor 1 heated above trip temperature. Throttling enabled.
Jun 6 21:44:12 system mcelog[23558]: Please check your system cooling. Performance will be impacted
Jun 6 21:44:12 system mcelog[23558]: Processor 1 below trip temperature. Throttling disabled
Jun 6 22:03:46 system kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1051658749)
Jun 6 22:03:46 system kernel: CPU1: Core temperature/speed normal
Jun 6 22:04:40 system kernel: mce: [Hardware Error]: Machine check events logged
Jun 6 21:49:13 system mcelog[23558]: Processor 1 heated above trip temperature. Throttling enabled.
Jun 6 21:49:13 system mcelog[23558]: Please check your system cooling. Performance will be impacted
Jun 6 21:49:13 system mcelog[23558]: Processor 1 below trip temperature. Throttling disabled
Jun 6 22:08:46 system kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1051699850)
Jun 6 22:08:46 system kernel: CPU1: Core temperature/speed normal


The machine is a timeserver (the system time is within two milliseconds of its peers according to ntpq), so the system time is spot on. I just don't know where the timestamps from the kernel generated messages are coming from (but whatever the source is, it is quite wrong).
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 42847
Location: 56N 3W

PostPosted: Sat Jun 13, 2015 2:13 pm    Post subject: Reply with quote

curmudgeon,

Check the timezone. Your clock will be running at UTC.
Displayed times will be corrected by the timezone.

If /etc/timezone is correct, try another timezone. Maybe there is a problem just with the timezone file you are actually using.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
haarp
Guru
Guru


Joined: 31 Oct 2007
Posts: 517

PostPosted: Sun Jun 14, 2015 11:45 am    Post subject: Reply with quote

It could also be that syslog-ng is showing wrong timestamps for kernel messages. This seems to be happening a lot lately.
Back to top
View user's profile Send private message
toralf
Developer
Developer


Joined: 01 Feb 2004
Posts: 3652
Location: Hamburg

PostPosted: Sun Jun 14, 2015 4:56 pm    Post subject: Reply with quote

haarp wrote:
It could also be that syslog-ng is showing wrong timestamps for kernel messages. This seems to be happening a lot lately.
with 3.6.2 and if the system was suspened/resumed.
3.6.3 is fine so far.
Back to top
View user's profile Send private message
Buffoon
Veteran
Veteran


Joined: 17 Jun 2015
Posts: 1074
Location: EU or US

PostPosted: Thu Jun 18, 2015 4:31 pm    Post subject: Reply with quote

Can your kernel predict lotto numbers? :P
Back to top
View user's profile Send private message
cal22cal
n00b
n00b


Joined: 19 Jan 2006
Posts: 36

PostPosted: Fri Jun 19, 2015 1:59 am    Post subject: Reply with quote

hwclock ?
http://docs.slackware.com/howtos:hardware:syncing_hardware_clock_and_system_local_time
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 2587

PostPosted: Fri Jun 19, 2015 6:54 am    Post subject: Re: "kernel time" is about fifteen minutes in the Reply with quote

curmudgeon wrote:
The machine is a timeserver (the system time is within two milliseconds of its peers according to ntpq), so the system time is spot on. I just don't know where the timestamps from the kernel generated messages are coming from (but whatever the source is, it is quite wrong).

Did you compare that timestamp to hwclock?
Code:
# /sbin/hwclock && date
Back to top
View user's profile Send private message
mjbjr
Apprentice
Apprentice


Joined: 02 Mar 2003
Posts: 233

PostPosted: Fri Jun 19, 2015 8:58 am    Post subject: Reply with quote

I've been following this thread because I have the same problem,
except that my kernel log message timestamps are four minutes
ahead of all the clocks. All the clocks are accurate.

hw clock (UTC)
linux system clock (UTC)
local (xfce4 desktop) (PDT)

I've never had this problem before, afaicr.
Back to top
View user's profile Send private message
curmudgeon
Veteran
Veteran


Joined: 08 Aug 2003
Posts: 1537

PostPosted: Sun Jul 19, 2015 6:33 pm    Post subject: Reply with quote

I had to reboot a while back (which resynced everything), and the problem has not returned.

Thanks for the suggestions, but all my computers use UTC anyway, and it wasn't the hardware clock (syslog-ng wouldn't be using the hardware clock anyway). Maybe this was just a bad version of syslog-ng (I see some other people have noticed the same problem, so at least I am not imagining things).

I have upgraded to syslog-ng 3.6.4 (which fixed some other problems), and I hope that this one won't return.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum