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: Sat, 04 Oct 2014 07:30:29 -0700 [thread overview]
Message-ID: <54300485.20901@candelatech.com> (raw)
In-Reply-To: <21551.42474.535540.368033@gargle.gargle.HOWL>
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.
Thanks,
Ben
>
> Sujith
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
rmanohar@qti.qualcomm.com
Subject: Re: 3.17 regression, ath9k: Summarize hw state per channel context
Date: Sat, 04 Oct 2014 07:30:29 -0700 [thread overview]
Message-ID: <54300485.20901@candelatech.com> (raw)
In-Reply-To: <21551.42474.535540.368033@gargle.gargle.HOWL>
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.
Thanks,
Ben
>
> Sujith
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-10-04 14:30 UTC|newest]
Thread overview: 11+ 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-03 21:17 ` Ben Greear
2014-10-04 7:46 ` [ath9k-devel] " Sujith Manoharan
2014-10-04 7:46 ` Sujith Manoharan
2014-10-04 14:30 ` Ben Greear [this message]
2014-10-04 14:30 ` Ben Greear
2014-10-16 22:41 ` [ath9k-devel] " Ben Greear
2014-10-16 22:41 ` Ben Greear
2014-10-24 18:54 ` [ath9k-devel] " Ben Greear
2014-11-04 21:33 ` Ben Greear
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=54300485.20901@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 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.