---- cut ----
Feb 23 16:30:38 vmw-cube kernel: [ 575.008652] rtc: lost some interrupts at 256Hz.
Feb 23 16:30:43 vmw-cube kernel: [ 580.003457] printk: 249 messages suppressed.
Feb 23 16:30:43 vmw-cube kernel: [ 580.003462] rtc: lost some interrupts at 256Hz.
Feb 23 16:30:48 vmw-cube kernel: [ 584.989692] printk: 248 messages suppressed.
Feb 23 16:30:48 vmw-cube kernel: [ 584.989697] rtc: lost some interrupts at 256Hz.
Feb 23 16:30:53 vmw-cube kernel: [ 589.985667] printk: 249 messages suppressed.
Feb 23 16:30:53 vmw-cube kernel: [ 589.985672] rtc: lost some interrupts at 256Hz.
Feb 23 16:30:57 vmw-cube kernel: [ 593.694190] sky2 eth0: hung mac 124:81 fifo 195 (107:102)
Feb 23 16:30:57 vmw-cube kernel: [ 593.694194] sky2 eth0: receiver hang detected
Feb 23 16:30:57 vmw-cube kernel: [ 593.694231] sky2 eth0: disabling interface
Feb 23 16:30:57 vmw-cube kernel: [ 593.694628] sky2 eth0: enabling interface
Feb 23 16:30:58 vmw-cube kernel: [ 594.964044] printk: 248 messages suppressed.
Feb 23 16:30:58 vmw-cube kernel: [ 594.964049] rtc: lost some interrupts at 256Hz.
Feb 23 16:31:00 vmw-cube kernel: [ 596.409139] sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Feb 23 16:31:03 vmw-cube kernel: [ 599.964007] printk: 249 messages suppressed.
Feb 23 16:31:03 vmw-cube kernel: [ 599.964012] rtc: lost some interrupts at 256Hz.
Feb 23 16:31:08 vmw-cube kernel: [ 604.953725] printk: 249 messages suppressed.
Feb 23 16:31:08 vmw-cube kernel: [ 604.953729] rtc: lost some interrupts at 256Hz.
Feb 23 16:31:13 vmw-cube kernel: [ 609.943330] printk: 249 messages suppressed.
---- cut ----
Then I do a restart of "networking".
---- cut ----
eb 23 16:32:58 vmw-cube kernel: [ 714.714533] rtc: lost some interrupts at 256Hz.
Feb 23 16:33:03 vmw-cube kernel: [ 719.704463] printk: 249 messages suppressed.
Feb 23 16:33:03 vmw-cube kernel: [ 719.704467] rtc: lost some interrupts at 256Hz.
Feb 23 16:33:06 vmw-cube kernel: [ 722.564080] sky2 eth0: disabling interface
Feb 23 16:33:06 vmw-cube kernel: [ 722.579569] bridge-eth0: disabling the bridge
Feb 23 16:33:06 vmw-cube kernel: [ 722.579573] device eth0 left promiscuous mode
Feb 23 16:33:06 vmw-cube kernel: [ 722.579579] audit(1203780786.782:6): dev=eth0 prom=0 old_prom=256 auid=4294967295
Feb 23 16:33:06 vmw-cube kernel: [ 722.579581] bridge-eth0: disabled promiscuous mode
Feb 23 16:33:06 vmw-cube kernel: [ 722.604082] bridge-eth0: down
Feb 23 16:33:06 vmw-cube kernel: [ 722.611129] sky2 eth0: enabling interface
Feb 23 16:33:06 vmw-cube kernel: [ 722.620603] bridge-eth0: enabling the bridge
Feb 23 16:33:06 vmw-cube kernel: [ 722.620617] device eth0 entered promiscuous mode
Feb 23 16:33:06 vmw-cube kernel: [ 722.620624] audit(1203780786.822:7): dev=eth0 prom=256 old_prom=0 auid=4294967295
Feb 23 16:33:06 vmw-cube kernel: [ 722.620627] bridge-eth0: enabled promiscuous mode
Feb 23 16:33:06 vmw-cube kernel: [ 722.620629] bridge-eth0: up
Feb 23 16:33:08 vmw-cube kernel: [ 724.684257] printk: 248 messages suppressed.
Feb 23 16:33:08 vmw-cube kernel: [ 724.684261] rtc: lost some interrupts at 256Hz.
Feb 23 16:33:09 vmw-cube kernel: [ 725.656922] sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Feb 23 16:33:12 vmw-cube ntpdate[6334]: step time server 91.189.94.4 offset 0.002976 sec
Feb 23 16:33:13 vmw-cube kernel: [ 729.676505] printk: 249 messages suppressed.
Feb 23 16:33:13 vmw-cube kernel: [ 729.676510] rtc: lost some interrupts at 256Hz.
Feb 23 16:33:18 vmw-cube kernel: [ 734.659308] printk: 249 messages suppressed.
Feb 23 16:33:18 vmw-cube kernel: [ 734.659313] rtc: lost some interrupts at 256Hz.
Feb 23 16:33:23 vmw-cube kernel: [ 739.663821] printk: 249 messages suppressed.
Feb 23 16:33:23 vmw-cube kernel: [ 739.663825] rtc: lost some interrupts at 256Hz.
---- cut ----
And it works again for a while...