Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Oct 2007 00:10:44 -0400
From:      Mike Andrews <mandrews@bit0.com>
To:        Philip Murray <pmurray@nevada.net.nz>,  Goran Lowkrantz <goran.lowkrantz@ismobile.com>, freebsd-stable@freebsd.org
Subject:   Re: em 6.6.6 - watchdog timeout
Message-ID:  <471AD144.60404@bit0.com>
In-Reply-To: <20071020040347.GA71660@eos.sc1.parodius.com>
References:  <DF00B541F0F46F5A6BE2414E@viglaf>	<5CCABF9E-80DD-4E46-80AA-6E3E1F156645@nevada.net.nz> <20071020040347.GA71660@eos.sc1.parodius.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick wrote:
> On Sat, Oct 20, 2007 at 11:21:10AM +1300, Philip Murray wrote:
>> "me too" on a Supermicro 5015MT+, although I notice my em0 is also sharing 
>> an interrupt with USB (uhci3)... not sure if that's the culprit.
> 
> I'm not aware of a 5015MT+ model.  Maybe you mean 5015M-MT+ or
> 5015M-T+?

We've got five 5015M-MT+'s in production.  The PDSMI+ motherboard has 
two 82573's, one of which has a known EEPROM issue that Jack Vogel has 
sent a DOS-based utility around to fix up (search the archives for 
dcgdis.exe).  It fixed watchdog timeouts I was having way back in the 
6.2 beta cycle -- in my case they only happened when I had link at 1G 
and went away if I dropped to 100M.  It might be worth ruling that out 
first unless you've already done that. :)

I haven't tried the 6.6.6 driver on mine yet, though, so this could be 
something totally different.  I was going to bump one of them from 
RELENG_6 to RELENG_7 as a test soon.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?471AD144.60404>