Date: Sun, 31 Oct 2004 18:19:24 -0500 From: "Simson L. Garfinkel" <simsong@csail.mit.edu> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/73360: sk0: watchdog timeout Message-ID: <4D9834F9-2B93-11D9-B7B6-000A95DA91E2@csail.mit.edu> In-Reply-To: <Pine.BSF.4.53.0410312137500.73542@e0-0.zab2.int.zabbadoz.net> References: <200410312115.i9VLFisD013971@www.freebsd.org> <Pine.BSF.4.53.0410312137500.73542@e0-0.zab2.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-2-698480383 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Oct 31, 2004, at 4:42 PM, Bjoern A. Zeeb wrote: >> I have an AMD64 machine with an ASUS motherboard and an on-board >> syskonect gigabit ethernet. The syskonect is periodically going mute. >> It still receives packets but will not transmit. This happens in both >> gigabit and 100BaseT modes. > > how do you know that it still receives packets ? > > - can you see counters increasing ? I ran tcpdump and saw that the packets were still arriving > - can you see packets coming in using tcpdump or such ? > > PS: > see also kern/73052, kern/73038, kern/71858, kern/71229, i386/67818, > and closed: kern/69879 Okay. ... I'm not sure what to do about those. ... I think that this is a syskonnect problem, rather than an AMD64 problem. I'm happy to assist the debugging. I seem to be able to make this happen pretty easily. > --Apple-Mail-2-698480383--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D9834F9-2B93-11D9-B7B6-000A95DA91E2>