All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Let ath10k_err take 'ar' argument?
Date: Thu, 06 Mar 2014 09:02:31 -0800	[thread overview]
Message-ID: <5318AA27.4090609@candelatech.com> (raw)

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
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5
ath10k: target stalled
ath10k: failed to wait for target to init: -5


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?

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

             reply	other threads:[~2014-03-06 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 17:02 Ben Greear [this message]
2014-03-07  7:49 ` Let ath10k_err take 'ar' argument? Kalle Valo
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=5318AA27.4090609@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    /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.