Date: Sat, 26 Oct 2002 01:55:31 +0400 (MSD) From: "."@babolo.ru To: Luigi Rizzo <rizzo@icir.org> Cc: Neil McGann <neil@neilmcgann.co.uk>, freebsd-hackers@FreeBSD.ORG Subject: Re: sis NIC problem Message-ID: <200210252155.g9PLtWII041321@aaz.links.ru> In-Reply-To: <20021025012940.A63009@carp.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> known problem with watchdog handling on several network drivers > including the "sis". Can ste be one of that network drivers? I have a problem I sent big description http://docs.freebsd.org/cgi/getmsg.cgi?fetch=126424+0+current/freebsd-net It looks similar (but not equivalent) > This has been fixed in some drivers (including the "sis') > some time ago, surely in 4.7 and probably also in 4.6 > > cheers > luigi > > On Fri, Oct 25, 2002 at 09:26:30AM +0100, Neil McGann wrote: > > I've got a couple of Netgear FA311 NICs (sis driver) in a low-traffic > > server/router/firewall that has been running fbsd4.4-R (with security > > updates) for a year or so. > > > > I occasionally lose all network connectivity on my inside nic (sis1). THis > > usually follows a large data transfer from the server (100Mbit, full > > duplex). What I see is that from the server console I can ping the nic IP > > (192.168.0.1), but everything else on that subnet is unreachable. The > > routing tables are fine and if I do "ifconfig sis1 down" then "ifconfig > > sis1 up" all is well again. (note that when I do ifconfig down I can't > > ping the nic IP) > > > > I get no error messages or clues - The NIC thinks it is "UP" and no > > errors. There are no interrupt conflicts or anything but 2 NICs on the PCI > > bus (it's a micro-atx motherboard with integrated graphics, 1G Celeron and > > 256M ram). -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210252155.g9PLtWII041321>