From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 02:45:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D74B16A419 for ; Thu, 1 Nov 2007 02:45:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 14B8113C4B0 for ; Thu, 1 Nov 2007 02:45:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217140407-1834499 for multiple; Wed, 31 Oct 2007 15:51:29 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9VKpFrM095994; Wed, 31 Oct 2007 16:51:20 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 31 Oct 2007 16:21:53 -0400 User-Agent: KMail/1.9.6 References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> In-Reply-To: <200710301328.l9UDSWAK081359@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710311621.53910.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 31 Oct 2007 16:51:21 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4652/Wed Oct 31 14:27:18 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Ihsan Dogan , Mike Tancsa Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 02:45:42 -0000 On Tuesday 30 October 2007 09:29:06 am Mike Tancsa wrote: > At 02:35 PM 10/29/2007, Ihsan Dogan wrote: > >on 11.10.2007 05:02 Jack Vogel said the following: > > > > >> em0@pci5:4:0: class=0x020000 card=0x10018086 chip=0x10268086 > > rev=0x04 hdr=0x00 > > >> vendor = 'Intel Corporation' > > >> device = '82545GM Gigabit Ethernet Controller' > > >> class = network > > >> subclass = ethernet > > >> > > >> And am consistently experiencing: > > >> > > >> em0: watchdog timeout -- resetting > > >> em0: link state changed to DOWN > > >> em0: link state changed to UP > > >> em0: watchdog timeout -- resetting > > >> em0: link state changed to DOWN > > >> em0: link state changed to UP > > >> em0: watchdog timeout -- resetting > > >> em0: link state changed to DOWN > > >> em0: link state changed to UP > > >> > > >> Anything I can do to help debug this ? > > > > > > Well, add more detail for one, like timestamps on these events, > > > do they happen once a minute, hour, day? > > > >I've got exactly the same problem on a machine, running 7.0-BETA1. The > >Problem occurs during the boot, when dhclient is trying to get IP. The > >messages are occuring all the time an it's not possible to use the > >network card at all. > >In my case, the network card and the soundcard are sharing an irq. If I > >don't load the the snd_emu10k1 driver, the network card works perfectly. > > > Mine are shared interrupts as well, however, they are shared among > the nics, so disabling is not an option > > % vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq4: sio0 61332 0 > irq16: em0 1029688695 614 > irq17: em1 em2 em3 775893384 463 > irq19: atapci1 300947 0 > cpu0: timer 3347198272 1997 > cpu1: timer 3347136233 1997 > Total 8500278868 5073 > > > em1 is the one having the problems (and yes, I did check the eeprom issue) > > em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 PT' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit > cap 10[e0] = PCI-Express 1 endpoint > > its also in FastE mode and not gigE. Not sure if that makes a > difference or not. What if you use MSI? -- John Baldwin