From owner-freebsd-hackers@FreeBSD.ORG Fri May 16 18:06:06 2014 Return-Path: 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 C184B70C for ; Fri, 16 May 2014 18:06:06 +0000 (UTC) Received: from mail-ee0-x232.google.com (mail-ee0-x232.google.com [IPv6:2a00:1450:4013:c00::232]) (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 58CC728FB for ; Fri, 16 May 2014 18:06:06 +0000 (UTC) Received: by mail-ee0-f50.google.com with SMTP id e51so1765765eek.37 for ; Fri, 16 May 2014 11:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version; bh=QdVKfzSX29vxD4gaaRVDUwrQH5Au+no63Y9Suu7cEBA=; b=ouHjN4+60REj0QZippkid5FLZFNP62pgJTNS2EcbCzbYEAmH1elSaPiDjLY7fezNGZ tXqwK4TgWnLlTg9ADg0Xxod7UiptDHDxoYsdhyjFux4s99OdaC3dfxiMlDPUkfeBR36H cK2ZvxIFmTaiqgN9Vp4sD0sHg4hYIIm+UBssvNwme+TvTwT6RFEvxSb7+YNsPx3gb/4p PSnJev8zNeRyH2HqLYpCvtyAPCtAv7yzD5+64FJ7wUko1PqbtOcwP9vmJBKarV7IwD2e hgBJvsDlwoh/cPT/Oo54ErWpcA+wUkdEmtuS3E13ICpvUhU3IXak2JYZ/seyXXGBODuc zDrg== X-Received: by 10.14.32.136 with SMTP id o8mr24544793eea.35.1400263564532; Fri, 16 May 2014 11:06:04 -0700 (PDT) Received: from strashydlo.home (adhj161.neoplus.adsl.tpnet.pl. [79.184.165.161]) by mx.google.com with ESMTPSA id b12sm9620404eeh.45.2014.05.16.11.06.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 May 2014 11:06:03 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Workaround for "fatal firmware error" iwn(4) problem. Date: Fri, 16 May 2014 20:06:02 +0200 Message-Id: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org> To: "freebsd-hackers@freebsd.org" Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) 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: Fri, 16 May 2014 18:06:06 -0000 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 May 16 17:11:54 brick kernel: firmware error log: May 16 17:11:54 brick kernel: error type =3D "NMI_INTERRUPT_WDG" = (0x00000004) May 16 17:11:54 brick kernel: program counter =3D 0x0000046C May 16 17:11:54 brick kernel: source line =3D 0x000000D0 May 16 17:11:54 brick kernel: error data =3D 0x0000000207030000 May 16 17:11:54 brick kernel: branch link =3D 0x0000D31A000004C2 May 16 17:11:54 brick kernel: interrupt link =3D 0x000006DE0000D23A May 16 17:11:54 brick kernel: time =3D 2985537 May 16 17:11:54 brick kernel: driver status: May 16 17:11:54 brick kernel: tx ring 0: qid=3D0 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 1: qid=3D1 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 2: qid=3D2 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 3: qid=3D3 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 4: qid=3D4 cur=3D33 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 5: qid=3D5 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 6: qid=3D6 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 7: qid=3D7 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 8: qid=3D8 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 9: qid=3D9 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 10: qid=3D10 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 11: qid=3D11 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 12: qid=3D12 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 13: qid=3D13 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 14: qid=3D14 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: tx ring 15: qid=3D15 cur=3D0 queued=3D0 =20= May 16 17:11:54 brick kernel: rx ring: cur=3D45 ... has been driving me crazy, so I wrote a workaround. The patch can be found here: http://people.freebsd.org/~trasz/iwn.diff 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.