Let ath10k_err take 'ar' argument?

Kalle Valo kvalo at qca.qualcomm.com
Fri Mar 7 02:49:10 EST 2014

Ben Greear <greearb at candelatech.com> writes:

> I have two NICs in a system, and it died overnight (full host lockup).
> Console shows this:
> [root at ct523-9292 ~]# ath10k: target stalled
> ath10k: failed to wait for target to init: -5
> ath10k: target stalled

Damn. Do you have anything before the target stalled message?

> I was thinking of changing ath10k_err to take
> 'ar' as argument and then print out pci-id or some
> other identifier so that we can tell which
> NIC is having issues on systems with multiple NICs?
> Any opinions on this before I get started?

I have been thinking exactly the same. I think we should add struct
ath10k to all of our logging and debugging macros. IIRC iwlwifi does
this already, you might want to check that first.

Kalle Valo

More information about the ath10k mailing list