Date: Sun, 2 Jun 2013 22:06:00 GMT From: Kim Culhan <w8hdkim@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/179232: panic in ath Message-ID: <201306022206.r52M60MW060713@oldred.freebsd.org> Resent-Message-ID: <201306022210.r52MA0R5049496@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 179232 >Category: kern >Synopsis: panic in ath >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jun 02 22:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Kim Culhan >Release: 10.0-CURRENT r251078M >Organization: >Environment: FreeBSD hyster3.kim.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r251078M: Tue May 28 20:02:52 EDT 2013 kimc@hyster3.kim.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: panic in ath driver, after which console is in the debugger. The machine is used a router and wireless access point among other things, panic may happen once in 24 hours of use. Has Intel Core 2 cpu, 4 GB ram, running 10.0-current built with clang. Very reliable otherwise. >How-To-Repeat: ATH wireless running with Atheros 9227 and 4 access points configured and running. 2 wired network interfaces, routing between interfaces, no traffic on wireless. Run the machine for several hours, panic occurs randomly, traffic on the wireless is not necessary. Not necessary to have any of the access points associated with clients. >Fix: Crash dump not attached to this report, 160KB, too large for 100KB limit. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201306022206.r52M60MW060713>