Date: Mon, 05 Oct 2009 13:54:54 -0700 From: Rudy <crapsh@monkeybrains.net> To: Greg Byshenk <freebsd@byshenk.net> Cc: Daniel Bond <db@danielbond.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: em0 watchdog timeouts Message-ID: <4ACA5D1E.10006@monkeybrains.net> In-Reply-To: <20091005200900.GE15606@core.byshenk.net> References: <2a41acea0909301556g1df7dbafv813f5924553c8bfb@mail.gmail.com> <4AC5198E.7030609@monkeybrains.net> <4AC51B4C.7080905@monkeybrains.net> <2a41acea0910011450v41590f3dn112f367f26faed2d@mail.gmail.com> <4AC64835.3060107@monkeybrains.net> <2a41acea0910021237w415efa2cs4354a0f99aef8f6@mail.gmail.com> <4AC66437.4040704@monkeybrains.net> <6194E9BC-3A3D-4941-A777-88C7411905B0@danielbond.org> <2a41acea0910050957x2d085e90w2ebea7f9eb87c3e4@mail.gmail.com> <57F8F331-E823-4F88-BDD5-A8B95A3B4CB6@danielbond.org> <20091005200900.GE15606@core.byshenk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ACA5D1E.10006>