bge problems in RELENG_9, bge0: watchdog timeout -- resetting

[Sean Bruno]

On Thu, 2012-07-12 at 12:06 -0700, Sean Bruno wrote:
> On Thu, 2012-07-12 at 14:59 -0700, YongHyeon PYUN wrote:
> > > I grabbed these updates and applied them cleanly to stable/9 on a
> > Dell
> > > R620 with a quad port BCM5720, I still see watchdog timeouts and
> > reset
> > > indications.  I am able to ping out of the box for a short amount of
> > > time before the device hangs and times out.
> > > 
> > 
> > Sean, sorry for late reply.
> > Given that I have no problems on sample 5720 controller I still
> > have no clue yet.
> > 
> 
> No problems ... :-)
> 
> > > 
> > > 
> > > -bash-4.2# ping XXX.XXX.XXX.1
> > > PING XXX.XXX.XXX.1 (XXX.XXX.XXX.XXX): 56 data bytes
> > > ping: sendto: Network is down
> > > ping: sendto: Network is down
> > > ping: sendto: Network is down
> > > ping: sendto: Network is down
> > > ping: sendto: Network is down
> > > Jul  9 17:31:41 <kern.crit> x89 kernel: bge2: watchdog timeout --
> > > resetting
> > > Jul  9 17:31:41 <kern.notice> x89 kernel: bge2: link state changed
> > to
> > > DOWN
> > > Jul  9 17:31:41 <kern.notice> x89 kernel: bge2: link state changed
> > to
> > 
> > Two link state change message indicates there is an issue in state
> > tracking. I'm experimenting a different approach but it seems it
> > takes too long due to lack of time. Any way, I've uploaded updated
> > bge(4)(URL is the same as before).
> 
> I see a bunch of firmware updates for this host along with an update to
> the BCM firmware package for this Dell box.
> 
> I'll update my system's driver first, validate pass/fail, if fail, then
> I'll update the firmware bits and validate some more.
> 
> sean
> 

No real change.  I suspect something else is going on here that I don't
understand.  I note that when the system malfunctions now, the system
cannot boot and requires me to enter the bios to check my settings.

Sean