From owner-freebsd-stable@FreeBSD.ORG Thu Apr 8 18:18:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6524A1065672 for ; Thu, 8 Apr 2010 18:18:50 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id E54328FC19 for ; Thu, 8 Apr 2010 18:18:49 +0000 (UTC) Received: by wwb24 with SMTP id 24so454519wwb.13 for ; Thu, 08 Apr 2010 11:18:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=p8aM2q7S9UuApIiQiWRqAL+f2oR3cwtThhwyfg/sED0=; b=WS52aZKIDZbvMvKc3aGr2qRxZmHkQi73Ae/i7pN4CZFaLdeOOyeQ3E4yyNQfgRRdj1 GwRq69yTF4pW/P6gAQpYlCMgaP1beHsfgBz7Wk/9JBmzFKm9XQ5UJwwPomZzxj7h7pDb q80gs0UCQh3ZjdaX+BhBRdXEUvKSsjyxkrZWU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DMJ1krz+9wKXSpZtrlcSJM/QNv0wtBtnvqib83DglwX5Rc0c8HCLraHJDaGpL47y0P 9UlMb3SrgY4sscohphXHwbZXTn2wi/H2oV1niXhaRWKyt6Hk24elt9B70tTpVSDMnSV0 sZZuchVXc0MD/BDI/TQFCdjQexFugscOKx6Y8= MIME-Version: 1.0 Received: by 10.216.11.8 with HTTP; Thu, 8 Apr 2010 11:18:48 -0700 (PDT) In-Reply-To: <201004081746.o38HkhmQ043211@lava.sentex.ca> References: <201004081313.o38DD4JM041821@lava.sentex.ca> <201004081320.o38DKVX7041854@lava.sentex.ca> <201004081746.o38HkhmQ043211@lava.sentex.ca> Date: Thu, 8 Apr 2010 11:18:48 -0700 Received: by 10.216.172.5 with SMTP id s5mr248419wel.30.1270750728638; Thu, 08 Apr 2010 11:18:48 -0700 (PDT) Message-ID: From: Jack Vogel To: Mike Tancsa , Brandon Gooch Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: em driver regression X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2010 18:18:50 -0000 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 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 metric 0 mtu 1500 > > options=399b > ether 00:1c:c0:95:0d:0d > inet 192.168.xx.219 netmask 0xffffff00 broadcast 192.168.xx.255 > media: Ethernet autoselect (1000baseT ) > 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 > >