Date: Thu, 8 Apr 2010 11:18:48 -0700 From: Jack Vogel <jfvogel@gmail.com> To: Mike Tancsa <mike@sentex.net>, Brandon Gooch <jamesbrandongooch@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: em driver regression Message-ID: <w2g2a41acea1004081118jaa99d24bq4438248a5b889f90@mail.gmail.com> In-Reply-To: <201004081746.o38HkhmQ043211@lava.sentex.ca> References: <201004081313.o38DD4JM041821@lava.sentex.ca> <201004081320.o38DKVX7041854@lava.sentex.ca> <l2n2a41acea1004080952u988c0dcci6f0e8b8750ad1fac@mail.gmail.com> <201004081746.o38HkhmQ043211@lava.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Both of you try something for me: Assuming you are using the latest code in HEAD, at line 4042 please make this insert: /* Strip the CRC */ rctl |= E1000_RCTL_SECRC; And try things again, I think this will solve at least the DHCP thing. I hope. Jack On Thu, Apr 8, 2010 at 10:46 AM, Mike Tancsa <mike@sentex.net> wrote: > At 12:52 PM 4/8/2010, Jack Vogel wrote: > >> Mike, I noticed this connection is only 100Mb, that isn't accidental? And, >> is it possible for >> you to check a connection at 1Gb and see if the watchdogs don't happen. >> >> My test engineer is running this code, and we are having trouble repro'ing >> the issue, so any >> clues might help. Is the kernel 64 or 32 bit? >> > > It is a 32 bit kernel (see the attached dmesg from the first email) in a > cisco 10/100 switch. I just tried and the dhclient issue happens at gig > speeds as well. > > Apr 8 13:34:29 ich10 dhclient[1480]: DHCPREQUEST on em0 to 255.255.255.255 > port 67 > Apr 8 13:34:35 ich10 dhclient[1480]: DHCPREQUEST on em0 to 255.255.255.255 > port 67 > Apr 8 13:34:48 ich10 dhclient[1480]: DHCPDISCOVER on em0 to > 255.255.255.255 port 67 interval 5 > Apr 8 13:34:48 ich10 dhclient[1480]: ip length 328 disagrees with bytes > received 332. > Apr 8 13:34:48 ich10 dhclient[1480]: accepting packet with data after udp > payload. > > 0(ich10)# ifconfig em0 > > 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.219 netmask 0xffffff00 broadcast 192.168.xx.255 > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > 0(ich10)# > > > ... As for the watchdog issue, it just seems to show up. I am not able to > reproduce it on demand. However, the dhclient issue happens all the time. I > will give it a whirl on a gigabit for a day and see. > > Its not that frequent > > > Apr 7 02:19:05 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 10:39:40 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 14:01:36 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 22:09:10 ich10 kernel: em0: Watchdog timeout -- resetting > > But it should in theory show up at least once in 24hrs if its not a port > speed issue. > > A potential 3rd issue I also noticed is that this morning I could not login > to the box-- but I could ping it, but no SSH banner. ie no 3way handshake > completing. I was able to 'fix' the issue by logging onto the console, > initiating some outbound tcp traffic (ie. ssh out from the box) and then I > could login again. Perhaps a TSO issue ? I now have a firewire console > hooked up so I can login out of band. If this issue comes up again, how can > I best narrow down what/where this 3rd issue is ? > > ---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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?w2g2a41acea1004081118jaa99d24bq4438248a5b889f90>