From owner-freebsd-hackers@FreeBSD.ORG  Mon May 19 18:38:10 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0FD30580
 for <freebsd-hackers@freebsd.org>; Mon, 19 May 2014 18:38:09 +0000 (UTC)
Received: from mail-ee0-x22a.google.com (mail-ee0-x22a.google.com
 [IPv6:2a00:1450:4013:c00::22a])
 (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 2046C28D4
 for <freebsd-hackers@freebsd.org>; Mon, 19 May 2014 18:38:08 +0000 (UTC)
Received: by mail-ee0-f42.google.com with SMTP id d49so3949565eek.29
 for <freebsd-hackers@freebsd.org>; Mon, 19 May 2014 11:38:07 -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=jI4eaNdarH7HgpRUGnmuP2TpF2HsSea6Q6SEH/9SSEM=;
 b=W5UEPropHUw6sSxLAEOILT63Rgy4G7FqHXV/Cr4QGPBWgBmREHAVHWvH8al4u1FVoN
 RzQXkNtJeZoPkw560ijvLzaHa9QB/qPIoVJ3wF8xlnEoFjI3wIByzzNPpWSx3/HBE015
 ZKfIOXAo90VwQNfN8rb47gms6wVB+0ovfHs5fy6+ga5XK/KsoVI7LC6csjUFIeEc7kxR
 aFcl2pF1Uf7nYxnLjPEdsNhGJsRlgRpK9hiJgzxKGbLbOzwU0yVCsowxJQbZH5MS74+6
 xM2kpZ41jUOh3BbPaWSPyFRo2ET3ZCj1jH7rlceS5Tkq5R9XUvF1/MKTpcTt8g5CYwf9
 1SDA==
X-Received: by 10.14.5.71 with SMTP id 47mr6507068eek.101.1400524687262;
 Mon, 19 May 2014 11:38:07 -0700 (PDT)
Received: from strashydlo.home (actm36.neoplus.adsl.tpnet.pl. [83.11.66.36])
 by mx.google.com with ESMTPSA id m44sm43690167eep.6.2014.05.19.11.38.06
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Mon, 19 May 2014 11:38:06 -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: <CA+q+TcpHvunOJXucN2j7=PDLrhND1JK7B-QWC-QDTEEZHnJ4PQ@mail.gmail.com>
Date: Mon, 19 May 2014 20:38:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AA5A8C5-F105-4806-AF94-A4D0064DBF9B@freebsd.org>
References: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org>
 <CA+q+TcpHvunOJXucN2j7=PDLrhND1JK7B-QWC-QDTEEZHnJ4PQ@mail.gmail.com>
To: =?iso-8859-2?Q?Olivier_Cochard-Labb=E9?= <olivier@cochard.me>
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: Mon, 19 May 2014 18:38:10 -0000

Wiadomo=B6=E6 napisana przez Olivier Cochard-Labb=E9 w dniu 18 maj 2014, =
o godz. 15:57:
> On Fri, May 16, 2014 at 8:06 PM, Edward Tomasz Napiera=B3a =
<trasz@freebsd.org> wrote:
> I've started using FreeBSD laptop and iwn(4) failing at random moments
> like this...
>=20
> I had the same problem too with iwn(4).=20
>=20
> ... has been driving me crazy, so I wrote a workaround.  The patch
> can be found here:
>=20
> http://people.freebsd.org/~trasz/iwn.diff
>=20
>=20
> I've tested you patch on a r266396, but it generate a panic:

[..]

Thanks!  Can you test with this one:

http://people.freebsd.org/~trasz/iwn3.diff