FreeBSD 9.1-RELEASE + bge0 == watchdog timeout

[YongHyeon PYUN]

On Thu, Mar 07, 2013 at 05:15:48PM +0900, YongHyeon PYUN wrote:
> On Thu, Mar 07, 2013 at 01:14:03PM +0600, Eugene M. Zheganin wrote:
> > Hi.
> > 
> > On 07.03.2013 12:23, YongHyeon PYUN wrote:
> > > On Thu, Mar 07, 2013 at 11:08:50AM +0600, Eugene M. Zheganin wrote:
> > >> It was definitely older than "months". It was running something similar 
> > >> to  "FreeBSD 8.2-STABLE #0: Mon Sep 19 08:10:00 YEKST 2011", this is the 
> > >> uname from a neighbor machine.
> > >>
> > >> I have, as I said, identical servers running FreeBSD. Here are some of 
> > >> the unames that I don't see timeouts on:
> > >>
> > >> 8.3-STABLE #2: Wed Aug 29 13:00:02 YEKT 2012 (up 187 days)
> > >> 8.3-PRERELEASE #1: Thu Mar 29 16:14:11 MSK 2012 (up 15 days, previous 
> > >> uptime around 180 days)
> > > These servers do not have 5718/5719/5720 changes.
> > >
> > >> 8.2-STABLE #0: Wed Dec 14 16:56:11 YEKT 2011 (up 99 days)
> > > This server has the bge(4) change but it didn't trigger watchdog
> > > timeouts.  Does this server use the same controller? If yes, the
> > > issue didn't come from bge(4) change.
> > >
> > How's that ? It's running even older version than previous two. I guess
> > you misread the year.
> 
> Oops, you're right. 

If your controller supports ASF/IPMI access please apply r248226
to stable/8 and let me know whether that makes any difference.
I believe ignoring ASF/IPMI firmware is not good idea since the
ASF/IPMI firmware will run regardless of hw.bge.allow_asf loader
tunable configuration.  You may have to set hw.bge.allow_asf=1
since it's off by default on stable/8.