Skip to contentSkip to conversation

tg3 error

DISCUSSION Felix von Leitner 4 participants 4 messages Mar 9, 2004 – Apr 3, 2004

lore
Share & tools
lore
#0 lore raw

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

The hardware is on-board on an IBM eServer pizza box, a dual broadcom gigabit ethernet NIC. Any ideas what might have caused this and what we should do to prevent this from happening again?

Thanks,

Felix

#1 lore raw
Quoted 4 lines · Felix von Leitner

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.

Quoted 8 lines

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...

Jeff

#2 lore raw
Quoted 10 lines
Quoted 9 lines · Felix von Leitner

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

Quoted 1 line
Quoted 1 line
Mar  9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=2400

enable_bit=2

Quoted 1 line
Quoted 1 line
Mar  9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=1400

enable_bit=2

Quoted 1 line
Quoted 1 line
Mar  9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=c00

enable_bit=2

Quoted 3 lines

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.

#3 lore raw
Quoted 21 lines · Kamil Srot
Quoted 10 lines
Quoted 9 lines · Felix von Leitner

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

Quoted 1 line
Quoted 1 line
Mar  9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=2400

enable_bit=2

Quoted 1 line
Quoted 1 line
Mar  9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=1400

enable_bit=2

Quoted 1 line
Quoted 1 line
Mar  9 16:17:39 mail2 kernel: tg3: tg3_stop_block timed out, ofs=c00

enable_bit=2

Quoted 3 lines

AFAIK this is fixed in the latest upstream tg3...

Quoted 8 lines

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

Signature · 3 lines
Alexander Hoogerhuis                               | [email protected]
CCNP - CCDP - MCNE - CCSE                          | +47 908 21 485
"You have zero privacy anyway. Get over it."  --Scott McNealy