From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Let ath10k_err take 'ar' argument?
Date: Fri, 07 Mar 2014 07:35:18 -0800 [thread overview]
Message-ID: <5319E736.3080104@candelatech.com> (raw)
In-Reply-To: <871tyeqwi1.fsf@kamboji.qca.qualcomm.com>
On 03/06/2014 11:49 PM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> I have two NICs in a system, and it died overnight (full host lockup).
>> Console shows this:
>>
>> [root@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?
No, nothing useful.
I reproduced this on WLE900VX as well (and posted a week or so about it).
Well, the one above is from system with two different NICs (CUS223, WLE900VX)
so not sure exactly which one had the issue...
>> 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.
I'll take a stab at it today if I can find time.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-03-07 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:02 Let ath10k_err take 'ar' argument? Ben Greear
2014-03-07 7:49 ` Kalle Valo
2014-03-07 15:35 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5319E736.3080104@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.