Bug 194996 - ath driver crash leaves card in inconsistent state
Summary: ath driver crash leaves card in inconsistent state
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 10.1-STABLE
Hardware: i386 Any
: --- Affects Only Me
Assignee: freebsd-wireless (Nobody)
Depends on:
Reported: 2014-11-13 19:29 UTC by Menche
Modified: 2015-07-07 16:00 UTC (History)
1 user (show)

See Also:

output of `dmesg | grep ath` and `sysctl -a | grep ath` (17.41 KB, text/plain)
2014-11-13 19:29 UTC, Menche
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Menche 2014-11-13 19:29:27 UTC
Created attachment 149382 [details]
output of `dmesg | grep ath` and `sysctl -a | grep ath`

The driver for my Atheros wireless card crashes after some time of use. A power cycle is needed for it to work properly again; the ath0 interface is not displayed after rebooting after a crash.

Attached are the outputs of dmesg and sysctl -a, grepped for ath.
Comment 1 Adrian Chadd freebsd_committer 2014-11-13 20:56:29 UTC
Hm, try compiling with AH_DEBUG / ATH_DEBUG / ATH_DIAGAPI, then do this:

sysctl dev.ath.0.hal.debug=0x4

then let me know what is printed when this happens.

So, the code '3' is HAL_EIO which in the reset path mostly indicates the hardware isn't coming back from being powered off.

Also, compile the tools in tools/tools/ath and run 'athregs'; it'll give you a register dump. Do it when it's working and when it's not working. It's possible that the NIC has completely lost its mind and the register reads will return error values - I'd like to know what those are.


Comment 2 Menche 2014-11-18 00:53:53 UTC
Unfortunately the power supply for the laptop I was using for FreeBSD died. I am trying to replace it. Thanks for the reply, I will get that debug information when I get it running again.
Comment 3 Menche 2014-11-23 04:17:08 UTC
I rebuilt world with those variables and set dev.ath.0.hal.debug to 4. I did not see any new messages. The athregs command fails, saying "athregs: ath0: invalid argument".
Comment 4 Menche 2014-11-23 04:39:19 UTC
Actually, I see a few different messages: 
/var/log/messages:Nov 22 20:07:21 menche-netbook kernel: ath0: <Atheros 5424/2424> mem 0x55200000-0x5520ffff irq 18 at device 0.0 on pci3
/var/log/messages:Nov 22 20:07:21 menche-netbook kernel: ath0: AR2425 mac 14.2 RF5424 phy 7.0
/var/log/messages:Nov 22 20:07:21 menche-netbook kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00a2
Comment 5 Marcus von Appen freebsd_committer freebsd_triage 2015-02-18 11:54:22 UTC
Updated 10.1-BETA and 10.1-RC versioned bugs to 10.1-STABLE.
Comment 6 Glen Barber freebsd_committer 2015-07-07 16:00:22 UTC
Is this still an issue?