Hi Jack,
I looks like the latest MFC to RELENG_8 for the em driver
has caused a regression. The box is not doing much as its a
development server in the lab. This is an Intel MB (DX58SO). dmesg
and pciconf -lvc attached.
Apr 6 14:27:13 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 14:27:13 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 15:05:40 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 15:05:40 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 20:31:41 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 20:31:41 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 22:51:04 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 6 22:51:04 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 02:19:05 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 02:19:05 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 03:46:51 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 03:46:51 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 08:04:03 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 08:04:03 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 10:39:40 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 10:39:40 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 11:12:34 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 11:12:34 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 13:25:26 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 13:25:26 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 14:01:36 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 14:01:36 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 17:19:53 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 17:19:53 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 21:16:45 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 21:16:45 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 22:09:10 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 7 22:09:10 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 8 03:11:28 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 8 03:11:28 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 8 07:40:51 ich10 kernel: em0: Watchdog timeout -- resetting
Apr 8 07:40:51 ich10 kernel: em0: Watchdog timeout -- resetting
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.txt
Type: application/octet-stream
Size: 26283 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100408/bf4b864f/dmesg.obj
At 09:12 AM 4/8/2010, Mike Tancsa wrote:>Hi Jack, > I looks like the latest MFC to RELENG_8 for the em driver > has caused a regression. The box is not doing much as its a > development server in the lab. This is an Intel MB (DX58SO). dmesg > and pciconf -lvc attached.Here are the stats from the NIC as well. em0: Excessive collisions = 0 em0: Sequence errors = 0 em0: Defer count = 0 em0: Missed Packets = 0 em0: Receive No Buffers = 0 em0: Receive Length Errors = 0 em0: Receive errors = 0 em0: Crc errors = 0 em0: Alignment errors = 0 em0: Collision/Carrier extension errors = 0 em0: watchdog timeouts = 16 em0: XON Rcvd = 0 em0: XON Xmtd = 0 em0: XOFF Rcvd = 0 em0: XOFF Xmtd = 0 em0: Good Packets Rcvd = 65839 em0: Good Packets Xmtd = 13100 em0: TSO Contexts Xmtd = 203 em0: TSO Contexts Failed = 0 It just grabs the IP via DHCP em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC> ether 00:1c:c0:95:0d:0d inet 192.168.xx.yy netmask 0xffffff00 broadcast 192.168.xx.zz media: Ethernet autoselect (100baseTX <full-duplex>) status: active -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike
OK, some more data... It seems dhclient is getting upset as well
since the updated driver
Apr 8 10:28:37 ich10 dhclient[1383]: DHCPDISCOVER on em0 to
255.255.255.255 port 67 interval 6
Apr 8 10:28:38 ich10 dhclient[1383]: ip length 328 disagrees with
bytes received 332.
Apr 8 10:28:38 ich10 dhclient[1383]: accepting packet with data
after udp payload.
Apr 8 10:28:38 ich10 dhclient[1383]: DHCPOFFER from 192.168.xx.1
Apr 8 10:28:40 ich10 dhclient[1383]: DHCPREQUEST on em0 to
255.255.255.255 port 67
Apr 8 10:28:40 ich10 dhclient[1383]: ip length 328 disagrees with
bytes received 332.
Apr 8 10:28:40 ich10 dhclient[1383]: accepting packet with data
after udp payload.
Apr 8 10:28:40 ich10 dhclient[1383]: DHCPACK from 192.168.xx.1
I also tried manually applying the patch below
<http://lists.freebsd.org/pipermail/svn-src-head/2010-April/016189.html>http://lists.freebsd.org/pipermail/svn-src-head/2010-April/016189.html
but still get the same error on dhclient
Apr 8 10:28:40 ich10 dhclient[1383]: ip length 328 disagrees with
bytes received 332.
which was not there before the 7.0.0 driver update
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
ether 00:1c:c0:95:0d:0d
inet 192.168.43.219 netmask 0xffffff00 broadcast 192.168.43.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
Also, should not
# ifconfig em0 -vlanmtu -vlanhwtag -vlanhwfilter -vlanhwtso
0(ich10)# ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=388b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
ether 00:1c:c0:95:0d:0d
inet 192.168.43.219 netmask 0xffffff00 broadcast 192.168.43.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
0(ich10)# killall dhclient
0(ich10)# dhclient em0
DHCPREQUEST on em0 to 255.255.255.255 port 67
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPACK from 192.168.xx.1
bound to 192.168.xx.219 -- renewal in 22777 seconds.
0(ich10)#
disable all the vlan features on the nic ?
---Mike
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike