All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dylan <dylan1473@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Severe issue with ath9k_htc driver - consistent full system crash since 3.8 kernels
Date: Tue, 23 Apr 2013 21:04:46 -0400	[thread overview]
Message-ID: <51772FAE.5020400@gmail.com> (raw)

The ath9k_htc driver causes my computer to completely lock up, forcing
me to restart. This occurs after anything between a few minutes to a few
hours - generally less than an hour - of having the device using the
driver connected to the computer and communicating with a network (I
haven't tested having the device connected to the computer but not
communicating with any network).

The network adapter in question is a TP-Link TL-WN822N V3 (lsusb
indicates it is TP-Link TL-WN821N v3). The only unusual thing that jumps
to mind about it is that it was initially listed as a Realtek driver
here <http://wikidevi.com/wiki/TP-LINK_TL-WN821N_v1> and TP-Link's tech
support informed me of the same. Now version 4 is listed as the Realtek
one and this is listed as an Atheros one. Not sure whether that's worth
pointing out but it was something that bugged me when I first got it.

The issue has existed since the 3.8 kernels at least partway through the
release candidates. I had the compat-wireless drivers installed for
unrelated reasons which was how I first noticed it. I sent a message
when the stable release of 3.8 came out shortly after and the issue
still existed but received no response. I've tested the device with the
new 3.9 kernel and the issue still occurs. I've also noted some signal
loss while it functions at all but it's much less severe with the later
3.8s and 3.9 so I'm not confident that bit is even still a problem. I
had no issues whatsoever with the driver in the 3.7 kernels and in fact
I'm using it with 3.7.9 right now. Though I will comment that the 3.9
drivers reconnect to networks when disconnected much more smoothly.

I'd be happy to provide any additional necessary information. I'm not
sure where to get logs of whatever it is that's happening as the only
ones I found that seemed relevant appeared to be erased on each boot.
Since the only way to recover from the issue was a hard reboot I haven't
got any logs of when it occurs. I might just be looking in the wrong
places though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130423/6a2d67bc/attachment.htm 

             reply	other threads:[~2013-04-24  1:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  1:04 Dylan [this message]
2013-04-25  9:30 ` [ath9k-devel] Severe issue with ath9k_htc driver - consistent full system crash since 3.8 kernels Oleksij Rempel

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=51772FAE.5020400@gmail.com \
    --to=dylan1473@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 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.