From: David Lombard <david.lombard@mscsoftware.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Lost clock tick on CPU 0 (now=3b6bca57923,
Date: Wed, 26 Apr 2000 17:36:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205052@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205046@msgid-missing>
Stephane Eranian wrote:
>> [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.
--
David N. Lombard
MSC.Software
next prev parent reply other threads:[~2000-04-26 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-26 9:20 [Linux-ia64] Lost clock tick on CPU 0 (now=3b6bca57923, next=3b6b627b32c)!! Christoph Rohland
2000-04-26 16:19 ` [Linux-ia64] Lost clock tick on CPU 0 (now=3b6bca57923, next=3b6b627b32c)!!t Stephane Eranian
2000-04-26 17:36 ` David Lombard [this message]
2000-05-08 11:47 ` Christoph Rohland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590678205052@msgid-missing \
--to=david.lombard@mscsoftware.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox