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? Ronald. -- Ronald Klop Amsterdam, The Netherlands -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.boot Type: application/octet-stream Size: 5812 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060905/df9afc56/dmesg.obj
On Tuesday 05 September 2006 14:52, Ronald Klop 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 UPSo am I. Especially when I transfer a GB or 2 from Windows XP to 6.1-stable. I use the FreeBSD machine as a backup for digital photos and my ripped mp3 files. A photo session is usually in excess of 1 GB and can hang with the watchdog timeout. Kent> > 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? > > Ronald.-- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html
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
>> Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resettingI got a bazillion of these, and a completely unusable machine, when I upgraded to 6.1-stable sources as of two days ago. The machine would simply freeze for minutes at a time. Going back to my previous kernel (dating from late July) made everything just fine. So something got seriously broken in the em driver in the last few weeks. -David.
At 10:20 PM 9/13/2006, David Myers wrote:>>>Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting > > >I got a bazillion of these, and a completely unusable machine, when >I upgraded to 6.1-stable sources as of two days ago. The machine >would simply freeze for minutes at a time. Going back to my >previous kernel (dating from late July) made everything just fine. > >So something got seriously broken in the em driver in the last few weeks.Which version of the NIC do you have ? (pciconf -lv ) ---Mike