On Sat, 22 Sep 2007 21:56:04 -0400
ben soo <lnx-kern@soo.com> wrote:

quoted text
> i spoke too soon.  The Gbit interface still dies.  Lasted around 
> 19hrs. or so.  i can't tell if there are hardware issues: yesterday 
> a Gbit NIC on the firewall died.  Different chip (Realtek), 
> different driver, different machine, same segment.  Segment is a 
> mix of 100Mbit and 1Gbit machines.
> 
> Symptoms of the failure are it just stops functioning with no error 
> messages.  ifconfig says there are packets being TX'd and none 
> being RX'd.  Interface can't be brought up again.
> 
> i use this box as the secondary DNS for our Internet domains 
> (unblocked by firewall), as well as the database server for our 
> developmental web CMS and the LAN ntp server (both services 
> invisible outside the LAN).
> 
> 
> dmesg says this on bootup:
> 
> > ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 16
> > PCI: Setting latency timer of device 0000:01:00.0 to 64
> > sky2 0000:01:00.0: v1.17 addr 0xdfefc000 irq 16 Yukon-EC (0xb6) rev 2
> > sky2 eth0: addr 00:01:29:d6:35:f4
> > ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 17
> > PCI: Setting latency timer of device 0000:02:00.0 to 64
> > sky2 0000:02:00.0: v1.17 addr 0xdfcfc000 irq 17 Yukon-EC (0xb6) rev 2
> > sky2 eth1: addr 00:01:29:d6:36:26

Does your network switch support flowcontrol?  The Yukon-EC may have
a hardware problem that happens if FIFO gets full. If flow control is enabled,
that shouldn't happen. 

The newest version of the driver has a watchdog to try
and detect and do an automatic reset, but it still means there would be about
2 seconds of downtime.

-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/