em0 watchdog timeouts

[Jack Vogel]

Hmmm, I did have one of the drivers print more info at watchdog time, but I
just looked
and that's not em, time to add that I guess.

Since you're in the driver there isn't a huge amount of info that you can
print, it still
may not be enough to help.

BTW, I've always been somewhat dissatisfied with the watchdog design and
think
its kinda flawed, I could try and make you an experimental with debug and
some
changes that you can try if you'd like.

Jack


On Mon, Oct 5, 2009 at 1:54 PM, Rudy <crapsh at monkeybrains.net> wrote:

> Finally, while doing some comparisons, I realized that the motherboard
>> having the problem was _not_ the same as the others; it was similar, but
>> not identical.
>>
>
> This is a good piece of info.  I can try swapping out the MB and see what
> happens.
>
> I do want to add: thank you Jack for all your help and if does turn out to
> be the MB, then double thanks.  Viva Monday!   :)
>
> What would be nice would be MORE info for a watchdog timeout... maybe a
> sysctl dev.watchdog.debug=1 or something where when a watchdog event
> happened --- for whatever driver --- a bunch of stats were dumped relating
> to the event.
>
> Rudy
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>