I've been noticing in recent kernels that the kernel message timestamp has
been inconsistent. It's like something is going backwards sometimes. Here
is a recent example:

[ 26.009143] usb 1-5: new high speed USB device using ehci_hcd and address 3
[ 26.014142] usb 1-5: configuration #1 chosen from 1 choice
[ 26.014142] scsi7 : SCSI emulation for USB Mass Storage devices
[ 20.593219] usb-storage: device found at 3
[ 20.593222] usb-storage: waiting for device to settle before scanning
[ 26.067134] scsi 7:0:0:0: Direct-Access WD 5000AAKB Externa l108 PQ: 0 ANSI: 0
[ 26.067693] sd 7:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
[ 26.068571] sd 7:0:0:0: [sde] Write Protect is off
[ 26.068630] sd 7:0:0:0: [sde] Mode Sense: 03 00 00 00
[ 26.068631] sd 7:0:0:0: [sde] Assuming drive cache: write through
[ 26.069570] sd 7:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
[ 26.070134] sd 7:0:0:0: [sde] Write Protect is off
[ 26.070134] sd 7:0:0:0: [sde] Mode Sense: 03 00 00 00
[ 26.070134] sd 7:0:0:0: [sde] Assuming drive cache: write through
[ 26.070134] sde: sde1
[ 26.070134] sd 7:0:0:0: [sde] Attached SCSI disk
[ 26.070259] sd 7:0:0:0: Attached scsi generic sg4 type 0
[ 26.070580] usb-storage: device scan complete
[ 8.451449] ReiserFS: sde1: found reiserfs format "3.6" with standard journal
[ 8.451522] ReiserFS: sde1: using ordered data mode
[ 8.451730] ReiserFS: sde1: journal params: device sde1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 8.451730] ReiserFS: sde1: checking transaction log (sde1)
[ 8.451730] ReiserFS: sde1: Using r5 hash to sort names
[ 619.636623] usb 1-5: USB disconnect, address 3
[ 1645.779833] device eth0 entered promiscuous mode
[ 548.279391] device eth0 left promiscuous mode
[ 552.069547] device eth0 entered promiscuous mode
[ 1656.171898] device eth0 left promiscuous mode
[ 160.650123] device eth0 entered promiscuous mode
[ 1682.550814] device eth0 left promiscuous mode
[ 1683.534402] device eth0 entered promiscuous mode
[ 930.191046] device eth0 left promiscuous mode
[ 164.117659] device eth0 entered promiscuous mode
[ 932.974722] device eth0 left promiscuous mode
[ 933.473778] device eth0 entered promiscuous mode
[ 585.659182] device eth0 left promiscuous mode
[ 586.368546] device eth0 entered promiscuous mode
[ 940.228072] device eth0 left promiscuous mode
[ 1741.025528] device eth0 entered promiscuous mode
[ 965.505295] device eth0 left promiscuous mode
[ 349.061426] NETDEV WATCHDOG: eth0: transmit timed out
[ 349.061578] eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
[ 349.062194] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

This appears to only be happening on:

root@faraday:/root 69# uname -imprsv
Linux 2.6.25.10 #1 SMP PREEMPT Sun Jul 6 00:57:32 CDT 2008 i686 Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz GenuineIntel

But the problem does not happen on this other machine (which has 2 dual cores):

root@tesla:/root 73# uname -imprsv
Linux 2.6.23.12 #1 SMP PREEMPT Mon Jan 14 04:25:18 CST 2008 i686 Dual-Core AMD Opteron(tm) Processor 2220 AuthenticAMD

A hardware clock issue?

--
|WARNING: Due to extreme spam, googlegroups.com is blocked. Due to ignorance |
| by the abuse department, bellsouth.net is blocked. If you post to |
| Usenet from these places, find another Usenet provider ASAP. |
| Phil Howard KA9WGN (email for humans: first name in lower case at ipal.net) |