From: Alexander Hoogerhuis <alexh@boxed.no>
To: "Kamil Srot" <kamil.srot@nlogy.com>
Cc: "Jeff Garzik" <jgarzik@pobox.com>,
"Felix von Leitner" <felix-kernel@fefe.de>,
<linux-kernel@vger.kernel.org>, <davem@redhat.com>
Subject: Re: tg3 error
Date: Sat, 03 Apr 2004 20:56:39 +0200 [thread overview]
Message-ID: <87smfkao0o.fsf@dorker.boxed.no> (raw)
In-Reply-To: <005401c4195b$ede2f950$4100a8c0@rigel> (Kamil Srot's message of "Sat, 3 Apr 2004 11:13:28 +0200")
"Kamil Srot" <kamil.srot@nlogy.com> writes:
>> Felix von Leitner wrote:
>> > A machine at a customer's site (running kernel 2.4.21) has stopped
>> > answering over Ethernet today. The machine itself was still there and
>> > the customer could log in at the console. A reboot fixed the problem.
>> >
>> > The machine has had these error messages in the syslog about once per
>> > hour for about 24 hours:
>> >
>> > Mar 9 16:17:38 mail2 kernel: tg3: eth0: transmit timed out, resetting
>> > Mar 9 16:17:38 mail2 kernel: tg3: tg3_stop_block timed out, ofs=3400
> enable_bit=2
>> > Mar 9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=2400
> enable_bit=2
>> > Mar 9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=1400
> enable_bit=2
>> > Mar 9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=c00
> enable_bit=2
>>
>>
>> AFAIK this is fixed in the latest upstream tg3...
>
> I have exactly the same problems in 2.4.25 - the log says exactly the same
> as for Felix.
> I'm running two identical HP ProLiant servers but have this problem only on
> one of them.
> It's happening approximately twice a week.
>
> Any ideas?
>
Just to pipe in; I have a machine (HP 530cmt) running RHEL3 no the
latest kernel, running with the tg3-driver for the onboard eth, and if
requires the i/f to be taken down and up again to start speaking, or
even negotiating an eth-link. Hardware at the other end is a cisco switch.
mvh,
A
--
Alexander Hoogerhuis | alexh@boxed.no
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
next prev parent reply other threads:[~2004-04-03 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 17:09 Felix von Leitner
2004-03-09 17:13 ` Jeff Garzik
2004-04-03 9:13 ` Kamil Srot
2004-04-03 18:56 ` Alexander Hoogerhuis [this message]
[not found] <fa.e6ruhov.1l3ejrn@ifi.uio.no>
[not found] ` <fa.ilm5rgj.bl2ljb@ifi.uio.no>
2004-04-04 21:14 ` walt
2004-04-04 21:19 ` Alexander Hoogerhuis
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=87smfkao0o.fsf@dorker.boxed.no \
--to=alexh@boxed.no \
--cc=davem@redhat.com \
--cc=felix-kernel@fefe.de \
--cc=jgarzik@pobox.com \
--cc=kamil.srot@nlogy.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®