Date: Wed, 31 Oct 2007 16:21:53 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Ihsan Dogan <ihsan@dogan.ch>, Mike Tancsa <mike@sentex.net> Subject: Re: em0: watchdog timeout ... Message-ID: <200710311621.53910.jhb@freebsd.org> In-Reply-To: <200710301328.l9UDSWAK081359@lava.sentex.ca> References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <fg596h$3a5$1@ger.gmane.org> <200710301328.l9UDSWAK081359@lava.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710311621.53910.jhb>