From owner-freebsd-mobile@FreeBSD.ORG Sat Nov 12 18:37:53 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 D4E821065670 for ; Sat, 12 Nov 2011 18:37:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1578FC08 for ; Sat, 12 Nov 2011 18:37:53 +0000 (UTC) Received: by vcbfo14 with SMTP id fo14so6159074vcb.13 for ; Sat, 12 Nov 2011 10:37:52 -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=TSa4+2SW62G9dDiMSPKUAxoaYVr8qnAP1e3wC4k2xwE=; b=kT3p5tn2vVaeh0HjEmXbRl5rf6VHH2BzOTWQgxgNNAI6V17ROd9Ao/1kqzqlSSqf7s Nq1H13qzSjJRBTEoeKfR7/gjen2FTNNpnZJtsQGBU/PSRtXxAWKnOsmoQQbfw9pmTP3n N8OGflSZiu7qxZg8V2mohika0hRC+vX2qqU3Y= MIME-Version: 1.0 Received: by 10.52.92.84 with SMTP id ck20mr27416159vdb.88.1321123072752; Sat, 12 Nov 2011 10:37:52 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.29.198 with HTTP; Sat, 12 Nov 2011 10:37:52 -0800 (PST) In-Reply-To: <4EBCDAF2.5020605@yandex.ru> References: <4EBBD13C.2010705@yandex.ru> <4EBCDAF2.5020605@yandex.ru> Date: Sat, 12 Nov 2011 10:37:52 -0800 X-Google-Sender-Auth: jqbweUN4X0G_dwM0O2TSouFDC04 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: Sat, 12 Nov 2011 18:37:53 -0000 On 11 November 2011 00:21, Ruslan Mahmatkhanov wrote: > Yes, but i'm not sure what exact version it was. Firmware version is > still the same as it was on 9-CURRENT, but after some recent if_bwn or > wireless stack changes this errors now happens constantly, but this > panic was for the first time. Well, we'll need to know which firmware/driver version last worked right before we have any chance of fixing what's going on. Adrian