From owner-freebsd-current@FreeBSD.ORG Wed Aug 26 15:19:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B946E106568E for ; Wed, 26 Aug 2009 15:19:01 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from n4a.bullet.mail.ac4.yahoo.com (n4a.bullet.mail.ac4.yahoo.com [76.13.13.67]) by mx1.freebsd.org (Postfix) with SMTP id 6F7DE8FC30 for ; Wed, 26 Aug 2009 15:19:01 +0000 (UTC) Received: from [76.13.13.26] by n4.bullet.mail.ac4.yahoo.com with NNFMP; 26 Aug 2009 15:06:14 -0000 Received: from [76.13.10.176] by t3.bullet.mail.ac4.yahoo.com with NNFMP; 26 Aug 2009 15:06:14 -0000 Received: from [127.0.0.1] by omp117.mail.ac4.yahoo.com with NNFMP; 26 Aug 2009 15:06:14 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 644980.2463.bm@omp117.mail.ac4.yahoo.com Received: (qmail 79717 invoked by uid 60001); 26 Aug 2009 15:03:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1251299024; bh=lZgMoGnHS6OauSvw/VPmS8PBskLBIDsWIQImJRQcIAs=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=t5T14E8TeGDm80mvYp0/4lmku6IcaFk3SxIElNcVyLUk8c+M6cHoVIpu/I6zUU2GnGn2xt68fdVV0jXuAOQzY8fI4ApjhZh8/3WMJET5wgoYC5uUuYnBbRUm6KYWuUQaYp1CyL8wmeNoIj6m0o/MloJlAeUN0pg9sILdUf2nkVw= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=pZGo+DMq9hqVLPX1NFg41pi17D4Z+KjY+LA2obBLQUK2Jy/j15u5qIWCVFyTZs4Mw2J24Cqw+CW6M1fvQI1xtqo9T0BVzDbWO+QrTKmeZqyY8yWZphRk9Wgh2eeQ7xCGepRUZKOLA5cjACsFxeca6QBeoVMIyCI8yS4EdHPIwEc=; Message-ID: <494547.79702.qm@web63907.mail.re1.yahoo.com> X-YMail-OSG: EB2GkvQVM1mBKkb.Vfjr_eK0pYCNKEv9IbznWushM03CjC91xqWS4Ye0cx1a.BnH9HLZ7Z0BUD2o68oM1ASuYPyHdRjTT9623goaitiAPWpyS34J3l0GH2vtWDMAauSUieuXVzNFJALX_iWrym3CZ4ceVeXgfqJsKHo0reyC0jzWUR2mnMScLJUW9km7ipaxioKPB02qPkamQ3oik8dYOdBFv2nB61pJKUMco6pG5XkfGkYcw.78PwKuACEMwAKaiE4W1cibJgxEnVIhfvGPHk.cn_6ilkRV_lJWCwyOQ4jy1J.EVgUWtXrNMhk.emrbCn5S251V9UCJ Received: from [66.176.162.245] by web63907.mail.re1.yahoo.com via HTTP; Wed, 26 Aug 2009 08:03:44 PDT X-Mailer: YahooMailClassic/6.1.2 YahooMailWebService/0.7.338.2 Date: Wed, 26 Aug 2009 08:03:44 -0700 (PDT) From: Barney Cordoba To: Scott Ullrich , Jack Vogel In-Reply-To: <2a41acea0908251417jabfc132xd6dd3c25f70664f6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current Subject: Re: kernel: em2: watchdog timeout -- resetting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 15:19:01 -0000 =0A=0A--- On Tue, 8/25/09, Jack Vogel wrote:=0A=0A> Fro= m: Jack Vogel =0A> Subject: Re: kernel: em2: watchdog ti= meout -- resetting=0A> To: "Scott Ullrich" =0A> Cc: "Fr= eeBSD Current" =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 =0A> wrote:=0A> =0A> > On Tue, Aug 25, 2009 at 5:08 PM, Jack Vogel=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