All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Unable to read firmware registers on crash?
Date: Sun, 01 Feb 2015 09:46:12 -0800	[thread overview]
Message-ID: <54CE6664.9090101@candelatech.com> (raw)

I am trying to debug a case where firmware occasionally crashes and
the driver cannot read any crash dump to debug problem further.

Any idea what might be the problem and how I might could read info
from the firmware (or hack firmware to deliver the crash info in some
other means...maybe though a previously reserved piece of memory on
the host??)

[147334.397148] ath10k: firmware crashed! (uuid ff405224-b2a4-493d-b619-19ad8152d190)
[147334.404808] ath10k: hardware name qca988x hw2.0 version 0x4100016c
[147334.411111] ath10k: firmware version: 10.1.467-ct-community-full-013
[147334.429603] ath10k: failed to read diag value at 0x1300804: -16
[147334.435647] ath10k: failed to read FW dump area address: -16


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:[~2015-02-01 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 17:46 Ben Greear [this message]
2015-02-02 12:11 ` Unable to read firmware registers on crash? Michal Kazior
2015-02-02 17:03   ` Ben Greear
2015-02-03  6:31     ` Michal Kazior
2015-02-03 13:57       ` Ben Greear
2015-02-03 14:26         ` Michal Kazior
2015-02-04  3:45           ` Ben Greear
2015-02-04  4:28             ` Ben Greear
2015-02-06 12:19               ` Michal Kazior

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=54CE6664.9090101@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.