All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Let ath10k_err take 'ar' argument?
Date: Fri, 7 Mar 2014 09:49:10 +0200	[thread overview]
Message-ID: <871tyeqwi1.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5318AA27.4090609@candelatech.com> (Ben Greear's message of "Thu,  06 Mar 2014 09:02:31 -0800")

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?

> 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

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-03-07  7:49 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 [this message]
2014-03-07 15:35   ` Ben Greear

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=871tyeqwi1.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.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.