From owner-freebsd-hackers@FreeBSD.ORG Sat May 17 21:01:02 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 CBD9FBF9 for ; Sat, 17 May 2014 21:01:02 +0000 (UTC) Received: from mail-ee0-x22d.google.com (mail-ee0-x22d.google.com [IPv6:2a00:1450:4013:c00::22d]) (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 610B426F1 for ; Sat, 17 May 2014 21:01:02 +0000 (UTC) Received: by mail-ee0-f45.google.com with SMTP id d49so2463338eek.32 for ; Sat, 17 May 2014 14:01:00 -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=m1fEma0DovjjvWELwFmEdrUShIM5UIRugRF4VIV/GRo=; b=WI1u0ik6chNH3aYFepxlANfPn1wStpnrLpHlUDLaujNCs6u5r+MSuWvNWDHxD9ZGjM hoA2pI+jB9L8GxKXlHoZPNELUidoS20qy7HD9CNL7DtfTNfjABsdADpknPFaBT+Ikx1f LTEVlrPnmIOpmnqJ/rdlr0mYULKNv/lWTVCBQgTlPh8zTddMuNw3wPTD7fnMunEPIDzu uzgN91k57oNniyRUAg4cWB6Uo80MNj/LjsADR+SQW9YwHn1za7agzPTao3Z6PfXsiF+/ G4RU7YqGEsUzswyX3k95kaeIdGGZx1Sivu30i9gnLSi3W3RvPitOleBSZsn6Qr0csx2i XvBQ== X-Received: by 10.15.33.3 with SMTP id b3mr18960061eev.56.1400360460764; Sat, 17 May 2014 14:01:00 -0700 (PDT) Received: from strashydlo.home (adfh214.neoplus.adsl.tpnet.pl. [79.184.111.214]) by mx.google.com with ESMTPSA id o49sm10996100eep.33.2014.05.17.14.00.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 May 2014 14:00:59 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= 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?= In-Reply-To: <20140517185616.GZ55053@albert.catwhisker.org> Date: Sat, 17 May 2014 23:00:58 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140517185616.GZ55053@albert.catwhisker.org> To: David Wolfskill X-Mailer: Apple Mail (2.1283) 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: Sat, 17 May 2014 21:01:02 -0000 Wiadomo=B6=E6 napisana przez David Wolfskill w dniu 17 maj 2014, o godz. = 20:56: > On Fri, May 16, 2014 at 08:06:02PM +0200, Edward Tomasz Napiera?a = 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 >> May 16 17:11:54 brick kernel: firmware error log: >> May 16 17:11:54 brick kernel: error type =3D "NMI_INTERRUPT_WDG" = (0x00000004) >> ... >>=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 >> I think it's too ugly to commit it as is (I'd never release crap like = this, >> but I know nothing about WiFi and iwn(4) in particular, so I feel = justified), >> but feedback is still welcome. >=20 > On Fri, May 16, 2014 at 08:16:01PM +0200, Edward Tomasz Napiera?a = wrote: >> ... >>> For which branch? >>=20 >> Ah, forgot about that. 11-HEAD. >=20 > So I've been running head/i386 with the above-cited patch for about = 1.75 > hrs. now -- by which time I would normally expect to have seen my > network connection have dropped -- and it's been quite steady, even > through listening to a streaming audio program for about an hour. Thanks! Note that it's easy to verify if the patch helps - just wait = until you see the "fatal firmware error" on the console or in dmesg. If the = network still works afterwards - the patch worked.