Lost clock tick on CPU 0 (now=3b6bca57923, next=3b6b627b32c)!!
Hi,
I am getting regular messages like the one above on my Lion system. I appears to me that these messages are in relation to other errors I am getting like hanging processes NFS IO errors etc.
Can any one comment on this?
Christoph
Re: [Linux-ia64] Lost clock tick on CPU 0 (now=3b6bca57923, next=3b6b627b32c)!!t
Quoted 8 lines
Hi,
I am getting regular messages like the one above on my Lion system. I appears to me that these messages are in relation to other errors I am getting like hanging processes NFS IO errors etc.
Can any one comment on this?
On your Lion are you using the builtin eepro 100 controller ? We have seen things like that with that flaky controller. Ever since we added an extra eepro100 PCI card in the machine I don't recall ever seeing this again.
-Stephane
Re: [Linux-ia64] Lost clock tick on CPU 0 (now=3b6bca57923,
In reply to Christoph RohlandQuoted 7 lines · Stephane Eranian
Quoted 1 line
[Linux-ia64] Lost clock tick on CPU 0 (now;6bca57923, next;6b627b32c)!!t
On your Lion are you using the builtin eepro 100 controller ? We have seen things like that with that flaky controller. Ever since we added an extra eepro100 PCI card in the machine I don't recall ever seeing this again.
Thanks for the info! We've been getting that on our systems too. We haven't seen any other network-related issues, but we haven't pushed that too much.
Signature · 2 lines
David N. Lombard MSC.Software
Re: [Linux-ia64] Lost clock tick on CPU 0 (now=3b6bca57923, next=3b6b627b32c)!!t
In reply to Christoph RohlandQuoted 4 lines · Stephane Eranian
On your Lion are you using the builtin eepro 100 controller ? We have seen things like that with that flaky controller. Ever since we added an extra eepro100 PCI card in the machine I don't recall ever seeing this again.
Adding an extra eepro and disabling the onboard one did not help.
Greetings
Christoph