Date: Thu, 14 Sep 2006 02:27:29 +0200 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) Message-ID: <op.tfud73ep8527sy@guido.klop.ws> In-Reply-To: <op.tffdo3pj8527sy@laptop.klop.ws> References: <op.tffdo3pj8527sy@laptop.klop.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 05 Sep 2006 23:52:05 +0200, Ronald Klop <ronald-freebsd8@klop.yi.org> wrote: > Hello, > > I get these errors a lot. > > Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting > Sep 5 11:55:12 ronald kernel: em0: link state changed to DOWN > Sep 5 11:55:14 ronald kernel: em0: link state changed to UP > Sep 5 12:00:37 ronald kernel: em0: watchdog timeout -- resetting > Sep 5 12:00:37 ronald kernel: em0: link state changed to DOWN > Sep 5 12:00:39 ronald kernel: em0: link state changed to UP > > I tried turning off rxcsum/txcsum and set these sysctl's. > dev.em.0.rx_int_delay: 0 > dev.em.0.tx_int_delay: 0 (default 66) > But the error is still there. > Searching the internet and the list provides more of the same problems, > but I didn't find an answer. > > My dmesg is attached. > > Is there any info I need to provide to debug this or can I try patches? 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? (dmesg was attached to my previous mail, but I can provide it again.) Ronald. -- Ronald Klop Amsterdam, The Netherlands
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.tfud73ep8527sy>