Date: Thu, 14 Sep 2006 18:25:01 -0500 From: Dan Olson <danolson@visi.com> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) Message-ID: <4509E4CD.8050102@visi.com> In-Reply-To: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> References: <op.tffdo3pj8527sy@laptop.klop.ws> <op.tfud73ep8527sy@guido.klop.ws> <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote:
> On 9/13/06, Ronald Klop <ronald-freebsd8@klop.yi.org> wrote:
> ...
>
>> Them manual page em(4) mentions trying another cable when the watchdog
>> timeout happens, so I tried that. But it didn't help.
>> Is there anything I can test to (help) debug this?
>> It happens a lot when my machine is under load. (100% CPU)
>> Is it possible that it happens since I upgraded the memory from 1GB to 2
>> GB?
>
> watchdogs mean that the transmit ring is not being cleaned, so the
> question is what is your machine doing at 100% cpu, if its that busy
> the network watchdogs may just be a side effect and not the real
> problem?
>
> Jack
I see these too when installing packages over nfs on my Laptop. If I run
with a low level of network traffic, i.e. ssh compile, and peg out the
cpu with a benchmark such as flops, I don't see these timeouts.
6.1-STABLE FreeBSD 6.1-STABLE #0: Sat Aug 26 14:45:40 CDT 2006
em0@pci2:1:0: class=0x020000 card=0x05491014 chip=0x101e8086 rev=0x03
hdr=0x00
vendor = 'Intel Corporation'
device = '82540EP Gigabit Ethernet Controller (Mobile)'
class = network
Any suggestions?
Thanks
Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4509E4CD.8050102>