From owner-freebsd-mobile@FreeBSD.ORG Fri Nov 11 07:34:28 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DAAE106566B for ; Fri, 11 Nov 2011 07:34:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0F3608FC08 for ; Fri, 11 Nov 2011 07:34:27 +0000 (UTC) Received: by vws11 with SMTP id 11so4652794vws.13 for ; Thu, 10 Nov 2011 23:34:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=p8rNDefF8AK9s4q0dps4J3RDDqMb+zdfhNPKrpRcnsg=; b=o4zo/dwMsStdHvRtJ7825SeEWw8gj9oLcFwc8kEdbmZrypyr9qSYGlPrzeE2ld+RgF hmkb4jyxeTePBurLac71Fh5U6sBvw4ybfLtulML5Tr2t58FVpECLQaRHlNEoYVgY8u95 dk3O3tHK2J/dtK/1q1GE79JgSwkUgWsYu+TFs= MIME-Version: 1.0 Received: by 10.52.27.72 with SMTP id r8mr18704222vdg.71.1320996867267; Thu, 10 Nov 2011 23:34:27 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.29.198 with HTTP; Thu, 10 Nov 2011 23:34:27 -0800 (PST) In-Reply-To: <4EBBD13C.2010705@yandex.ru> References: <4EBBD13C.2010705@yandex.ru> Date: Thu, 10 Nov 2011 23:34:27 -0800 X-Google-Sender-Auth: MqdtG61NVUm2flEEM2NPVlZr2-k Message-ID: From: Adrian Chadd To: Ruslan Mahmatkhanov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mobile@freebsd.org Subject: Re: other bwn panic X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2011 07:34:28 -0000 On 10 November 2011 05:27, Ruslan Mahmatkhanov wrote: > Good day! > > I just got yet another panic with bwn driver on fresh -CURRENT. And > still have debugging options turned off, so dunno if this ("unexpected > NULL ni") can help anyhow to understand the problem. Since switching > to 10.0 i constantly get those "HW reset: PHY TX errors", but till > today this wasn't a problem: Was there ever a version where the HW reset issues weren't happening? We'll need a backtrace to figure out why the node is null. Adrian