Date: Tue, 25 Aug 2009 17:12:02 -0400 From: Scott Ullrich <sullrich@gmail.com> To: Jack Vogel <jfvogel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: kernel: em2: watchdog timeout -- resetting Message-ID: <d5992baf0908251412k6d807d71qacee342ad3edc800@mail.gmail.com> In-Reply-To: <2a41acea0908251408q1004fbc7sae2a79b469a3a3a4@mail.gmail.com> References: <d5992baf0908251257h545b64f5l62c01f5e2ca6c5d4@mail.gmail.com> <2a41acea0908251408q1004fbc7sae2a79b469a3a3a4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 25, 2009 at 5:08 PM, Jack Vogel<jfvogel@gmail.com> wrote: > Well, there's no magic switch, you could change the driver code to remove > it, > however its really indicative of some kind of problem, it shouldn't happen, > so > perhaps you want to pursue that. Does it only happen on em2, what is special > about that path, etc etc.. > > You can look at the debug/stats data of the interface for clues, maybe its a > mbuf exhaustion, perhaps descriptor. After looking at the interface closer it appears the device it is plugged into does not have power. In this case it is a Wimax wireless radio. Should a device with NOCARRIER cause this error non-stop in the logs? Can I get you more information that might help understand why the watchdog is being tripped? Thanks for your help! Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5992baf0908251412k6d807d71qacee342ad3edc800>