On Saturday 16 February 2008, Kok, Auke wrote:
> Bernd Schubert wrote:
> > Hello,
> >
> > I can't login to one of our servers and just got this in an ipmi sol
> > session:
> >
> > [18169.209181] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Hello,
I can't login to one of our servers and just got this in an ipmi sol
session:
[18169.209181] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
[18169.209183] Tx Queue <0>
[18169.209184] TDH
[18169.209185] TDT
[18169.209186] next_
On Tuesday 08 August 2006 01:46, Michael Chan wrote:
> On Tue, 2006-08-08 at 01:24 +0200, Bernd Schubert wrote:
> > tg3.c:v3.49 (Feb 2, 2006)
> > acpi_bus-0201 [01] bus_set_power : Device is not power manageable
> > eth1: Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)
rupts: 64bit+ Queue=0/3
Enable-
The driver is compiled into the kernel (its a nfs-root booted system and
NIC modules are presently not supported by our initrd).
So the default option for tso is set. Is there any way to determine the
present tso setting? With ethtool I only find the opti
Hi,
I have seen a few reports like this, but now broadcom seems to actively
support tg3, so I decided to send this.
... [many hamilton not responding messages]
4554928.798000] nfs: server hamilton not responding, still trying
[4554935.319000] nfs: server hamilton not responding, still trying
[455
