From: Ben Greear <greearb@candelatech.com>
To: Corey Richardson <corey@octayn.net>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] ath9k_htc works poorly in 3.9
Date: Wed, 15 May 2013 10:33:16 -0700 [thread overview]
Message-ID: <5193C6DC.40709@candelatech.com> (raw)
In-Reply-To: <CA++BO6TBrzJtD2cnNmUu4j6G2c5tSq228318avuGVF4r1NeW-A@mail.gmail.com>
On 05/15/2013 10:31 AM, Corey Richardson wrote:
> On Wed, May 8, 2013 at 1:31 AM, Oleksij Rempel <linux@rempel-privat.de> wrote:
>> If it is an regression, can you please do "git bisect". If you can locate
>> the patch which introduced this regression, it will be great.
>>
>
> It seems to have been an intermittent problem with my WAP as well; the
> PoE wasn't consistent so it kept dropping out, also taking down the
> adapter with it. It does seem to be a regression, but it's so hard to
> reproduce that I don't think it's worth pursuing.
Sometimes I see the NIC fail to boot up on reboot of the OS.
I've only tested 3.9 kernels with these NICs, as I haven't used
them previously.
The kernel message was something about not being able to upload
firmware to the adapter...I'll grab some logs next
time I see it.
Thanks,
Ben
>
> Thanks!
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-05-15 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 3:52 ath9k_htc works poorly in 3.9 Corey Richardson
2013-05-08 5:31 ` [ath9k-devel] " Oleksij Rempel
2013-05-15 17:31 ` Corey Richardson
2013-05-15 17:33 ` Ben Greear [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=5193C6DC.40709@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=corey@octayn.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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 NNTP newsgroup(s).