From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Firmware debug messages stopped sometime after 3.18
Date: Thu, 01 Jan 2015 17:17:00 -0800 [thread overview]
Message-ID: <54A5F18C.2050007@candelatech.com> (raw)
While trying to reproduce some bugs on ath10k in 3.19.0-rc2, I could not
get any debuglog messages from the firmware. For instance, in stock kernel
it should print out something like this:
wmi event debug mesg len 28
I got other wmi debug messages, so the debug level appeared correct.
The message shows up as expected in stock 3.18 kernel.
Was this done on purpose?
I've started a bisect...should track it down directly.
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
next reply other threads:[~2015-01-02 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 1:17 Ben Greear [this message]
2015-01-06 1:26 ` Firmware debug messages stopped sometime after 3.18 (bisected) Ben Greear
2015-01-06 20:08 ` Ben Greear
2015-01-06 20:42 ` 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=54A5F18C.2050007@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox