From: Avery Pennarun <apenwarr@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] mac80211: debugfs var for the default aggregation timeout.
Date: Mon, 18 Apr 2016 21:29:42 -0400 [thread overview]
Message-ID: <CAHqTa-1k+QVj2dC3F44fMYMfvh5PpW4QXyVn0NkCcPFrkd5OVg@mail.gmail.com> (raw)
In-Reply-To: <CAArymCnGTj4qv8KWwDfwSN0DQvTTpTwC+-sHSkMfjNVs2Rr_sg@mail.gmail.com>
On Sat, Apr 9, 2016 at 9:59 PM, bruce m beach <brucembeach@gmail.com> wrote:
>> If any people more familiar with ARM are reading this - does the value
>> 0x5b35da40 ring a bell?
>
> It could be anything. It depends on the chip implementation. For instance on an
> exynos that is an undefined region. What device are we talking about?
This is a mindspeed c2k CPU, in case that helps at all. But I'm
guessing it really is just some pointer garbage. The only way to
trigger the crash is to do (something) with an attached station at the
same moment as reading the agg_status file. Some station types
trigger it more than others, but I'm not sure which.
prev parent reply other threads:[~2016-04-19 1:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHqTa-22NpabO6B7nL=O26fnuGQHFOzpagWtsfQz4_BfrO6nTw@mail.gmail.com>
[not found] ` <1455658091-28262-1-git-send-email-apenwarr@gmail.com>
[not found] ` <1455658091-28262-2-git-send-email-apenwarr@gmail.com>
[not found] ` <1456222441.2041.10.camel@sipsolutions.net>
[not found] ` <CAHqTa-1CkJ-Pm6o7-pxcek4h+hmq6EtA0u12zGGraOUjDjeXSQ@mail.gmail.com>
[not found] ` <1456257946.9910.23.camel@sipsolutions.net>
2016-04-05 23:46 ` [ath9k-devel] [PATCH] mac80211: debugfs var for the default aggregation timeout Avery Pennarun
2016-04-06 7:40 ` Johannes Berg
2016-04-08 1:32 ` Avery Pennarun
2016-04-08 6:56 ` Johannes Berg
2016-04-08 7:01 ` Johannes Berg
2016-04-08 7:15 ` Johannes Berg
2016-04-08 8:31 ` Avery Pennarun
2016-04-09 1:27 ` Avery Pennarun
2016-04-09 4:56 ` Johannes Berg
2016-04-10 0:31 ` Adrian Chadd
2016-04-10 2:12 ` bruce m beach
2016-04-19 1:29 ` Avery Pennarun [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=CAHqTa-1k+QVj2dC3F44fMYMfvh5PpW4QXyVn0NkCcPFrkd5OVg@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=ath9k-devel@lists.ath9k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).