From owner-freebsd-hackers@FreeBSD.ORG  Thu May 22 17:40:12 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 11B90367;
 Thu, 22 May 2014 17:40:12 +0000 (UTC)
Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com
 [IPv6:2a00:1450:4013:c00::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 758612915;
 Thu, 22 May 2014 17:40:11 +0000 (UTC)
Received: by mail-ee0-f52.google.com with SMTP id e53so2780464eek.25
 for <multiple recipients>; Thu, 22 May 2014 10:40:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=/GXi6aerB6F7tfH1zqRV6psVZOqkSGwhkusQJzdlQsE=;
 b=0N1VOnr/C/zMcO8Una8Vl1Gimcp0jau0iowDB3FrbhkL7YZEKA6vIrlqlFyAPJgBBX
 72HcrSmm+fiqCBnXanjuForHz5h9DebM0tuPmcnJZD9syonR4SmJ3MzY7oWqvMD1b5Ki
 7Cpxinl5Pwj9KtF7AD3ZNmNwrlrBLqrG4zwqQGwv6eOxavfuM5obpWVokQGN4g/K379d
 O9WfE9Yi8SBLFgwD4hsTceDxkYiLn7WQVySg+SbEU9lAAsVGVLFykidYioqo3HTRDmbi
 G1N0wz7Wxpe4hjDNbVmJMPmc8LbQGaqNJTTQp1J1Z+q/H8D5lADGnI2tZpXhLoPjyF+/
 xOQQ==
X-Received: by 10.15.33.140 with SMTP id c12mr101193eev.41.1400780409704;
 Thu, 22 May 2014 10:40:09 -0700 (PDT)
Received: from strashydlo.home (adhh46.neoplus.adsl.tpnet.pl. [79.184.163.46])
 by mx.google.com with ESMTPSA id
 l45sm1974055eep.25.2014.05.22.10.40.08 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Thu, 22 May 2014 10:40:09 -0700 (PDT)
Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <etnapierala@gmail.com>
Subject: Re: Workaround for "fatal firmware error" iwn(4) problem.
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-2
From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org>
In-Reply-To: <1400779164.1069.4.camel@bruno>
Date: Thu, 22 May 2014 19:40:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1A450D0-7478-41A3-A21E-207BC55CC4D2@FreeBSD.org>
References: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org>
 <1400779164.1069.4.camel@bruno>
To: sbruno@freebsd.org
X-Mailer: Apple Mail (2.1283)
Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@FreeBSD.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 17:40:12 -0000

Wiadomo=B6=E6 napisana przez Sean Bruno w dniu 22 maj 2014, o godz. =
19:19:

> On Fri, 2014-05-16 at 20:06 +0200, Edward Tomasz Napiera=B3a wrote:
>> I've started using FreeBSD laptop and iwn(4) failing at random =
moments
>> like this...
>>=20
>> May 16 17:11:54 brick kernel: iwn0: iwn_intr: fatal firmware error
>=20
>=20
> so, interesting.  iwi(4) seems to do the same thing.  I'm not sure
> what's up, but I've been trying to pin it down.

It seems to already have the required code, iwi_restart().  Doesn't
it work?