From owner-freebsd-current@FreeBSD.ORG Tue Jun 28 09:44:30 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 D330D106566C for ; Tue, 28 Jun 2011 09:44:30 +0000 (UTC) (envelope-from st_esser@t-online.de) Received: from mailout03.t-online.de (mailout03.t-online.de [194.25.134.81]) by mx1.freebsd.org (Postfix) with ESMTP id 9908B8FC0C for ; Tue, 28 Jun 2011 09:44:30 +0000 (UTC) Received: from fwd24.aul.t-online.de (fwd24.aul.t-online.de ) by mailout03.t-online.de with smtp id 1QbUao-0002Gr-Mh; Tue, 28 Jun 2011 11:28:27 +0200 Received: from [192.168.119.20] (rSOVCyZCrhmXcCCQ6vfMfS-2j6QBjmtjsdPBC8noZbmrDaXNP-dlj6vz-1GTT-jZPG@[81.173.158.158]) by fwd24.t-online.de with esmtp id 1QbUag-2KQFZQ0; Tue, 28 Jun 2011 11:28:18 +0200 Message-ID: <4E099EB2.7050902@freebsd.org> Date: Tue, 28 Jun 2011 11:28:18 +0200 From: "Stefan Esser" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110620 Thunderbird/5.0b2 MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-ID: rSOVCyZCrhmXcCCQ6vfMfS-2j6QBjmtjsdPBC8noZbmrDaXNP-dlj6vz-1GTT-jZPG X-TOI-MSGID: 9647439a-9b4e-4f25-944e-3106411223fd X-Mailman-Approved-At: Tue, 28 Jun 2011 11:02:18 +0000 Cc: Subject: Panic in ieee80211 tx mgmt timeout 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: Tue, 28 Jun 2011 09:44:30 -0000 Hi, is this a known issue? My -CURRENT system (r223560M, amd64, 8GB, Atheros WLAN) panics after minutes to hours of uptime with the following message: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 0 fault virtual address = 0xffffff807f502000 fault code = supervisor data read, page not present ... processor eflags = interrupt enabled, resume, IOPL = 0 current process = 11 (swi4: clock) [ thread pid 11 tid 1000012 ] Stopped at ieee80211_tx_mgmt_timeout+0x1: movq (%rdi),%rdi db> bt Tracing pid 11 tid 100012 td 0xfffffe00032e0000 ieee80211_tx_mgmt_timeout() at ieee80211_tx_mgmt_timeout+0x1 intr_event_execute_handlers() at intr_event_execute_handlers+0x66 ithread_loop() at ithread_loop+0x96 fork_exit() at fork_exit+0x11d fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff8000288d00, rbp = 0 --- This panic message is manually transcribed, since the GPT-only partitioning prevents dumping of a kernel core. (Why, BTW?) I could add a swap partition on a MBR disk, if a core dump seems neccessary to diagnose the problem. I'm also willing to wait for that panic to occur again and to gather more debug output. Other information: The Atheros WLAN in this system is unused (not associated) but both ath0 and wlan0 were "UP" at the time of the panic. Initial testing shows the system to be stable with both wlan0 and ath0 set to "down" after boot. But still, the timeout should not panic the kernel, if WLAN is active but not fully configured (e.g. no SSID). Any ideas? Best regards, STefan