From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] 3.17 regression, ath9k: Summarize hw state per channel context
Date: Fri, 24 Oct 2014 11:54:49 -0700 [thread overview]
Message-ID: <544AA079.5050205@candelatech.com> (raw)
In-Reply-To: <544049A8.3030906@candelatech.com>
Has anyone had time to investigate this?
Do I need to write up some scripts to reproduce this
so you can verify it yourself?
Thanks,
Ben
On 10/16/2014 03:41 PM, Ben Greear wrote:
> On 10/04/2014 07:30 AM, Ben Greear wrote:
>>
>>
>> On 10/04/2014 12:46 AM, Sujith Manoharan wrote:
>>> Ben Greear wrote:
>>>> Took a while, but I found the regression that has been bugging me.
>>>>
>>>> This is on stock kernel, with hand-patched fixup from Felix that fixes
>>>> crash related to minstrel (patch made it upstream later, so that isn't
>>>> a current problem).
>>>>
>>>> The test case is easily reproducible on my systems. I'm not sure
>>>> all the details matter, but this happens to be my test case
>>>> at the moment:
>>>>
>>>> 32-bit Fedora OS, latest supplicant, etc. ath9k NIC.
>>>
>>> Does this happen with latest wireless-testing ?
>>
>> It happens with a recent one, but I can test the very latest.
>
> I found time to test it today, and problem still exists in wireless-testing
> (0275925709f044dbcbbef614847d8955ba1a7776).
>
> Thanks,
> Ben
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-10-24 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 21:17 [ath9k-devel] 3.17 regression, ath9k: Summarize hw state per channel context Ben Greear
2014-10-04 7:46 ` Sujith Manoharan
2014-10-04 14:30 ` Ben Greear
2014-10-16 22:41 ` Ben Greear
2014-10-24 18:54 ` Ben Greear [this message]
2014-11-04 21:33 ` 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=544AA079.5050205@candelatech.com \
--to=greearb@candelatech.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