From owner-freebsd-current@FreeBSD.ORG Thu Oct 13 08:15:23 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE41D10656AD for ; Thu, 13 Oct 2011 08:15:23 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 32DCF8FC13 for ; Thu, 13 Oct 2011 08:15:22 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so1365956bkb.13 for ; Thu, 13 Oct 2011 01:15:22 -0700 (PDT) Received: by 10.204.15.194 with SMTP id l2mr1748252bka.83.1318493721766; Thu, 13 Oct 2011 01:15:21 -0700 (PDT) Received: from amy.lab.techwires.net (p54B4B204.dip.t-dialin.net. [84.180.178.4]) by mx.google.com with ESMTPS id d17sm2588243bkq.11.2011.10.13.01.15.19 (version=SSLv3 cipher=OTHER); Thu, 13 Oct 2011 01:15:19 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-current@freebsd.org Date: Thu, 13 Oct 2011 10:17:07 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-BETA3; KDE/4.6.5; amd64; ; ) References: <4E8ED3C8.1020108@freebsd.org> <4E8F0A47.1010408@gmail.com> In-Reply-To: <4E8F0A47.1010408@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201110131017.07154.bschmidt@freebsd.org> Cc: Rene Ladan , Niclas Zeising Subject: Re: iwn panic with 9.0-BETA3-amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2011 08:15:23 -0000 On Friday 07 October 2011 16:18:47 Niclas Zeising wrote: > This might or might not be related, but, I'm having trouble with the iwn > firmware crashing. I also have a clang built kernel (and userland) > buildwith CPUTYPE=core2. My iwn device is > iwn0: mem 0xe4000000-0xe4001fff irq > 17 at device 0.0 on pci16 > and the firmware gives the following output when it dies. > iwn0: iwn_intr: fatal firmware error > firmware error log: > error type = "NMI_INTERRUPT_WDG" (0x00000004) > program counter = 0x0000046C > source line = 0x000000D0 This is a known issue with the 4965's firmware. I have yet to find a reliable solution for that.. As a workaround you can disable background scan with ifconfig wlan0 -bgscan > The only way to restore the firmware is to reboot the computer. No need to reboot, killing the VAP and recreating it should get you going again. -- Bernhard