On Thu, Nov 20, 2003 at 02:02:12PM -0800, Feldman, Scott wrote: > Christian, moving this issue over from lkml to linux-net to increase > chances for a response. thanks, wasn't aware of this list > Are those other three interfaces with e100 as well? Yes, they were working fine. > -scott bye, -christian- > -----Original Message----- > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Christian Hammers > Sent: Thursday, November 20, 2003 11:40 AM > To: linux-kernel@vger.kernel.org > Subject: e100.c network driver suddenly stops working > > > Hello > > This is the second time now that I've experienced a e100.c network driver to suddenly stop forwarding packets over an interface without giving further warnings in the syslog until I did a "ifconfig down", "ifconfig up". The running kernel was 2.4.22 with 802.1q VLAN enabled on the interface. There were 3 additional interfaces and normal load. > > Last time this happens while using the version shipped with kernel 2.4.22, this time it was version 2.3.27 from the intel homepage. > > Does anybody else had this bug? I don't like switching to the eepro100.c > driver as it had MTU problems when using 802.1q VLANs. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
