From: "Kamil Srot" <kamil.srot@nlogy.com>
To: "Jeff Garzik" <jgarzik@pobox.com>,
"Felix von Leitner" <felix-kernel@fefe.de>
Cc: <linux-kernel@vger.kernel.org>, <davem@redhat.com>
Subject: Re: tg3 error
Date: Sat, 3 Apr 2004 11:13:28 +0200 [thread overview]
Message-ID: <005401c4195b$ede2f950$4100a8c0@rigel> (raw)
In-Reply-To: 404DFB4F.1020208@pobox.com
> 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?
Thank you,
--
C.
next prev parent reply other threads:[~2004-04-03 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 17:09 tg3 error Felix von Leitner
2004-03-09 17:13 ` Jeff Garzik
2004-04-03 9:13 ` Kamil Srot [this message]
2004-04-03 18:56 ` Alexander Hoogerhuis
[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='005401c4195b$ede2f950$4100a8c0@rigel' \
--to=kamil.srot@nlogy.com \
--cc=davem@redhat.com \
--cc=felix-kernel@fefe.de \
--cc=jgarzik@pobox.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