Date: Wed, 29 Jun 2011 09:50:08 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Stefan Esser <st_esser@t-online.de> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic in ieee80211 tx mgmt timeout Message-ID: <BANLkTiknrezs%2BsxC4x9KcM0LJSs_fU_mdg@mail.gmail.com> In-Reply-To: <4E099EB2.7050902@freebsd.org> References: <4E099EB2.7050902@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is kinda strange; that symbol doesn't exist in the net80211 or ath sou= rce. What the heck? adrian On 28 June 2011 17:28, Stefan Esser <st_esser@t-online.de> wrote: > 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 =3D 0; apic id =3D 0 > fault virtual address =A0 =3D 0xffffff807f502000 > fault code =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D supervisor data read, page not = present > ... > processor eflags =A0 =A0 =A0 =A0=3D interrupt enabled, resume, IOPL =3D 0 > current process =A0 =A0 =A0 =A0 =3D 11 (swi4: clock) > [ thread pid 11 tid 1000012 ] > Stopped at =A0 =A0 =A0ieee80211_tx_mgmt_timeout+0x1: =A0movq =A0 =A0 (%rd= i),%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 =3D 0, rsp =3D 0xffffff8000288d00, rbp =3D 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTiknrezs%2BsxC4x9KcM0LJSs_fU_mdg>