From owner-freebsd-current@FreeBSD.ORG Tue Aug 25 21:17:20 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 1A7411065690 for ; Tue, 25 Aug 2009 21:17:20 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id C54D58FC18 for ; Tue, 25 Aug 2009 21:17:19 +0000 (UTC) Received: by an-out-0708.google.com with SMTP id d14so1201865and.13 for ; Tue, 25 Aug 2009 14:17:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=wQm6sskpHzOxc7JMEWer2Km+Q/ZUiTew1ZEZDjIY85Y=; b=r/ziBXODXOxbZNO14z9yyDc5X93F+m+AGeKf8L93rSYAyHoVGs+rpTUA2VgHJw2s5R V7c2A9HcwK+/e+ty7rSUar0oUjhKT3PGiwrBsM5aUXR71lCAvPMndficl5O7ssA2cYA/ sjOuvF3EYp5UkfPC9IT+VSqGMq57Imo2W6bP8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JLuH8k4Aw+BBOSAzkiqycb91UWhvhBvSXcDDlI5USdE+klta8HYMFTobMrkKTvvAGj jiWeBqbLdCi816OS7kXf4K/mL9SgJEG+zSSPZLimvCv+7Ilp1+oNVDpFOSltF/HfgLIJ yeoiY9vWEoJmA94Smmqea9s5TUFol9XR7B58I= MIME-Version: 1.0 Received: by 10.101.33.5 with SMTP id l5mr6619352anj.44.1251235039198; Tue, 25 Aug 2009 14:17:19 -0700 (PDT) In-Reply-To: References: <2a41acea0908251408q1004fbc7sae2a79b469a3a3a4@mail.gmail.com> Date: Tue, 25 Aug 2009 14:17:19 -0700 Message-ID: <2a41acea0908251417jabfc132xd6dd3c25f70664f6@mail.gmail.com> From: Jack Vogel To: Scott Ullrich Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Tue, 25 Aug 2009 21:17:20 -0000 Hmm, I do not know what this hardware looks like, but its a wired interface, not wireless, so if it has link (and I'm guessing it does) it will have informed the stack its running, and thus will get traffic. Sounds like this is something the Wimax box should handle, at least that's my first take on the matter. This is the first I've encountered a setup like this however. Jack On Tue, Aug 25, 2009 at 2:12 PM, Scott Ullrich wrote: > On Tue, Aug 25, 2009 at 5:08 PM, Jack Vogel 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 >