From owner-freebsd-hackers@FreeBSD.ORG Thu May 22 17:19:26 2014 Return-Path: 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 5BF7EB65; Thu, 22 May 2014 17:19:26 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B2FC2748; Thu, 22 May 2014 17:19:25 +0000 (UTC) Received: from [10.12.72.220] (unknown [69.164.56.1]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 11040194138; Thu, 22 May 2014 17:19:25 +0000 (UTC) Subject: Re: Workaround for "fatal firmware error" iwn(4) problem. From: Sean Bruno Reply-To: sbruno@freebsd.org To: Edward Tomasz =?iso-8859-2?Q?Napiera=B3a?= In-Reply-To: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org> References: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org> Content-Type: text/plain; charset="iso-8859-2" Date: Thu, 22 May 2014 10:19:24 -0700 Message-ID: <1400779164.1069.4.camel@bruno> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 17:19:26 -0000 On Fri, 2014-05-16 at 20:06 +0200, Edward Tomasz Napierała wrote: > I've started using FreeBSD laptop and iwn(4) failing at random moments > like this... > > May 16 17:11:54 brick kernel: iwn0: iwn_intr: fatal firmware error 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. I suspect we've aggrivated something in the firmware recently. sean