[ath9k-devel] Severe issue with ath9k_htc driver - consistent full system crash since 3.8 kernels

[ath9k-devel] Severe issue with ath9k_htc driver - consistent full system crash since 3.8 kernels

[Dylan]

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 

[ath9k-devel] Severe issue with ath9k_htc driver - consistent full system crash since 3.8 kernels

[Oleksij Rempel]

Hi Dylan,

can you please provide some pictures of it?
One pic of the label, and if possible high resolution scans of pcb 
board.  Similar to this:
http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v2
800 or 900dpi in jpg will be ok. Send it directly to me.

Am 24.04.2013 03:04, schrieb Dylan:
> 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.
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>


-- 
Regards,
Oleksij