Date: Wed, 26 Aug 2009 08:03:44 -0700 (PDT) From: Barney Cordoba <barney_cordoba@yahoo.com> To: Scott Ullrich <sullrich@gmail.com>, Jack Vogel <jfvogel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: kernel: em2: watchdog timeout -- resetting Message-ID: <494547.79702.qm@web63907.mail.re1.yahoo.com> In-Reply-To: <2a41acea0908251417jabfc132xd6dd3c25f70664f6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Tue, 8/25/09, Jack Vogel <jfvogel@gmail.com> wrote:=0A=0A> Fro= m: Jack Vogel <jfvogel@gmail.com>=0A> Subject: Re: kernel: em2: watchdog ti= meout -- resetting=0A> To: "Scott Ullrich" <sullrich@gmail.com>=0A> Cc: "Fr= eeBSD Current" <freebsd-current@freebsd.org>=0A> Date: Tuesday, August 25, = 2009, 5:17 PM=0A> Hmm, I do not know what this hardware=0A> looks like, but= its a wired interface,=0A> not wireless, so if it has link (and I'm guessi= ng it does)=0A> it will have=0A> informed=0A> the stack its running, and th= us will get traffic.=0A> =0A> Sounds like this is something the Wimax box s= hould handle,=0A> at least that's=0A> my first take on the matter. This is = the first I've=0A> encountered a setup like=0A> this however.=0A> =0A> Jack= =0A> =0A> =0A> On Tue, Aug 25, 2009 at 2:12 PM, Scott Ullrich <sullrich@gma= il.com>=0A> wrote:=0A> =0A> > On Tue, Aug 25, 2009 at 5:08 PM, Jack Vogel<j= fvogel@gmail.com>=0A> wrote:=0A> > > Well, there's no magic switch, you cou= ld change=0A> the driver code to remove=0A> > > it,=0A> > > however its rea= lly indicative of some kind of=0A> problem, it shouldn't=0A> > happen,=0A> = > > so=0A> > > perhaps you want to pursue that. Does it only=0A> happen on = em2, what is=0A> > special=0A> > > about that path, etc etc..=0A> > >=0A> >= > You can look at the debug/stats data of the=0A> interface for clues, may= be=0A> > its a=0A> > > mbuf exhaustion, perhaps descriptor.=0A> >=0A> > Aft= er looking at the interface closer it appears the=0A> device it is=0A> > pl= ugged into does not have power.=A0 In this case=0A> it is a Wimax wireless= =0A> > radio.=0A> >=0A> > Should a device with NOCARRIER cause this error= =0A> non-stop in the logs?=0A> >=A0 Can I get you more information that mig= ht help=0A> understand why the=0A> > watchdog is being tripped?=0A> >=0A> >= Thanks for your help!=0A> >=0A> > Scott=0A> >=0AIts amazing that it doesn'= t affect traffic, since the controller is=0Agetting reset each time.=0A=0AA= lthought the watchdog isn't coded very cleanly in the driver, the only=0Ati= me you should get such behavior would be if interrupts weren't working=0Aco= rrectly. Its a pretty unusual part; a special low power device that=0Ais pr= obably rarely used, so its not impossible that there's some required=0Acode= missing. I wonder how much testing Jack has done with an 82541GI?=0A=0ABar= ney=0A=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?494547.79702.qm>