Firmware crash w/ 10.2 diagnosis?

Kalle Valo kvalo at
Tue Sep 9 05:08:21 PDT 2014

Denton Gentry <denton.gentry at> writes:

> The ath10k is operating in AP mode.
> Its using a base ath10k driver from a few months ago:
>        git fetch git:// ath-next
>        git checkout v3.15-rc1-237-gd9bc4b9

What is the kernel version? Do you use backports?

> The data from the firmware shows something about a monitor vdev being
> removed? hostapd does create a monitor interface, though I don't see
> an indication that it was being removed at the time of the crash.
> hostapd had exited and restarted well before though, is it possible
> that removal of a monitor interface some time ago might be
> contributing?

So are you still using the old cooked monitor interface for management
frames? I strongly recommend switching to the new way of transmitting
and receiving management frames through nl80211 as then hostapd will not
a create monitor interface. This is what most people use and is most
extensively tested.

Commit 6e3e939f3b1bf8534b32ad09ff199d88800835a0 ('net: add wireless TX
status socket option') adds this capability to the kernel, first
released in Linux 3.3. There might be some dependencies in case you are
porting it to an older kernel, so be extra careful.

Please note that updating backports is not enough for SO_WIFI_STATUS
status, you need to update the kernel itself.

Kalle Valo

More information about the ath10k mailing list