From owner-freebsd-current@FreeBSD.ORG Tue Aug 25 21:12:24 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 C215F1065694 for ; Tue, 25 Aug 2009 21:12:23 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 3F7A68FC24 for ; Tue, 25 Aug 2009 21:12:22 +0000 (UTC) Received: by ewy5 with SMTP id 5so2226667ewy.36 for ; Tue, 25 Aug 2009 14:12:22 -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 :from:date:message-id:subject:to:cc:content-type; bh=txMSOU20umPc9X6taYocRi8HdfwxvARdEGBY59uwvY0=; b=ljrciDQNcE57hSDM2DasPwdqBZKgdCv02KFQzj6zF3bBWJTwlyk6F32BPUjIPl7Rk4 FaxX22onyv/0s+XWbXuyP0mZ+gyRFeiX8H2hZkEKYBZjC2kSQZOOnNtPnSutsfkbTw96 6XuWrzC5LakHKTMOmTmUdW/Oj3A8hM2ZDo9VE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=YhHvfiEz5r4rahIVJa0vT0xBBAO+UQDDJzEYxrh4gcKXycCVA42gK7EZREfNu1S4EX N0GAcMs7LkufW8uc1otRQ5tL5N+zbfPnL3q/MW5SsCKGmbbxck9BlHXk/7HsBWIFTIwq NKYj4eVpFeLFLpw5CPucgE2dQEa4rcj17oTLs= MIME-Version: 1.0 Received: by 10.210.91.13 with SMTP id o13mr5978419ebb.68.1251234742152; Tue, 25 Aug 2009 14:12:22 -0700 (PDT) In-Reply-To: <2a41acea0908251408q1004fbc7sae2a79b469a3a3a4@mail.gmail.com> References: <2a41acea0908251408q1004fbc7sae2a79b469a3a3a4@mail.gmail.com> From: Scott Ullrich Date: Tue, 25 Aug 2009 17:12:02 -0400 Message-ID: To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 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:12:24 -0000 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