Date: Wed, 15 Jul 2015 12:21:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200221] em0 watchdog timeout under load Message-ID: <bug-200221-2472-apatVEn20C@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200221-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-200221-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200221 --- Comment #10 from anthony@ury.org.uk --- Now using sys/dev/e1000@283959 from 10-STABLE (rest of the kernel 10.1-RELEASE as before), I'm seeing watchdog timeouts again, with tso4 enabled. Again, this only seems to happen at a point of high network load (nightly backup over NFS). I'll try disabling tso4 on this revision but failing that, will go back to e1000@269196. There is slightly more detail in messages now, though: Jul 8 07:31:58 urybsod kernel: em0: Watchdog timeout Queue[0]-- resetting Jul 8 07:31:58 urybsod kernel: Interface is RUNNING and ACTIVE Jul 8 07:31:58 urybsod kernel: em0: TX Queue 0 ------ Jul 8 07:31:58 urybsod kernel: em0: hw tdh = 909, hw tdt = 1015 Jul 8 07:31:58 urybsod kernel: em0: Tx Queue Status = -2147483648 Jul 8 07:31:58 urybsod kernel: em0: TX descriptors avail = 914 Jul 8 07:31:58 urybsod kernel: em0: Tx Descriptors avail failure = 114 Jul 8 07:31:58 urybsod kernel: em0: RX Queue 0 ------ Jul 8 07:31:58 urybsod kernel: em0: hw rdh = 959, hw rdt = 958 Jul 8 07:31:58 urybsod kernel: em0: RX discarded packets = 0 Jul 8 07:31:58 urybsod kernel: em0: RX Next to Check = 959 Jul 8 07:31:58 urybsod kernel: em0: RX Next to Refresh = 958 Jul 8 07:31:58 urybsod kernel: em0: Link is Down Jul 8 07:31:58 urybsod kernel: em0: link state changed to DOWN Jul 8 07:32:01 urybsod kernel: em0: Link is up 1000 Mbps Full Duplex Jul 8 07:32:01 urybsod kernel: em0: link state changed to UP Jul 8 07:32:01 urybsod devd: Executing '/etc/rc.d/dhclient quietstart em0' -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200221-2472-apatVEn20C>