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)] (PCIX:100MHz:64-bit)
> > 10/100/1000BaseT Ethernet 00:e0:81:2b:aa:28 eth1: RXcsums[1]
> > LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0] eth1:
> > dma_rwctrl[769f4000] dma_mask[64-bit]
> > eth2: Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit)
> > 10/100/1000BaseT Ethernet 00:e0:81:2b:aa:29 eth2: RXcsums[1]
> > LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth2:
> > dma_rwctrl[769f4000] dma_mask[64-bit]
>
> You have ASF enabled on eth1 but not on eth2 so I wonder if ASF is
> causing the problem. Can you run the same traffic on eth2 and see if
> you get the same timeout problem? Thanks.
Currently I have no physical access to the system and eth2 is not connected to
our switch. I will connect it and run a test as soon as possible (sometime
this week). However, I don't think I can easily reproduce it even with eth1.
Its the first time I noticed those error messages in seven months. However,
we are experiencing random crashes of the system and maybe thats the cause of
it, who knows. The system is running its root file system over nfs, so a
network failure will lockup the entire system.
Thanks,
Bernd
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
