Skip to contentSkip to conversation

2.6.25.2 - Jiffies/Time jumping back and forth (Regereesion from 2.6.24)

DISCUSSION Martin Knoblauch 4 participants 4 messages May 7, 2008

lore
Share & tools
lore
#1 lore raw
Quoted 1 line · Martin Knoblauch

any news on the one below? I upgraded to 2.6.25.2 and the problem still persists. Would adding a bugzilla actually help ? :-)

Well, at least a bugzilla entry makes it impossible for the information to be lost, so IMHO unless you get a patch right away, it is a good idea to open one.

As for it helping someone to actually go and FIX the bug, no :-)

Signature · 4 lines
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
#2 lore raw
In reply to Martin Knoblauch
Quoted 4 lines · Martin Knoblauch

any news on the one below? I upgraded to 2.6.25.2 and the problem still persists. Would adding a bugzilla actually help ? :-)

http://www.ussg.iu.edu/hypermail/linux/kernel/0804.2/1144.html

I noticed a similar issue on 2.6.22 and 2.6.24 kernels: with ACPI disabled Linux' clock jumps backward and forward early during boot. See also the kernel messages from the attachment in comment #13 of
http://bugzilla.kernel.org/show_bug.cgi?id=9936.

Bart,

#3 lore raw
In reply to Martin Knoblauch
Quoted 6 lines · Martin Knoblauch

Hi,

any news on the one below? I upgraded to 2.6.25.2 and the problem still persists. Would adding a bugzilla actually help ? :-)

http://www.ussg.iu.edu/hypermail/linux/kernel/0804.2/1144.html

With this issue you're seeing is only the printk timestamps jumping back, correct?

For example, you're not seeing the output from gettimeofday() or the actual jiffies value (as seen from maybe a driver) jump backward? Is that right?

The printk timestamps may jump around a bit at bootup, especially if you have unsynced TSCs, so that is a known issue. However its not known to have any actual negative effect other then maybe causing the dmesg log to be a bit confusing.

thanks
-john