All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saurabh Chakrabarti <saurabh.chakrabarti@amideeptech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] atheros chipset does not recover after going into unresponsive state
Date: Tue, 20 May 2014 20:01:43 +0530	[thread overview]
Message-ID: <537B674F.70208@amideeptech.com> (raw)

I am using TP-link WN721n usb wifi adapter with atheros 9271 chipset on 
raspberry pi. There are times when the wifi interface goes into an 
unresponsive state in which it does not send or receive any packets.

Here's the error log I get as soon as this occurs,

May 16 15:55:13 raspberry kernel: [  240.974619] ath: phy0: Timeout 
waiting for WMI command: WMI_REG_WRITE_CMDID
May 16 15:55:13 raspberry kernel: [  241.053067] ath: phy0: REGISTER 
WRITE FAILED:(0x4048, -110)
May 16 15:55:14 raspberry kernel: [  241.737670] ath: phy0: Dropping a 
packet due to TX timeout

When this state is hit, I reboot the system, but after reboot the wifi 
interface(wlan0) does not come back up. Here's the error I get on 
startup in the kernel log,

usb 1-1.2: device descriptor read/64, error -110

Interestingly, it works like a charm when I turn off the power and turn 
it back on(or if I pull the wifi adapter out and insert it back). But 
obviously I cannot do this all the time as the system is at a remote 
location.

Although I would want to know why the interface goes into this state, is 
there anything I can do so that I can atleast reset the interface once 
it goes into this state?

Regards,
Saurabh Chakrabarti

             reply	other threads:[~2014-05-20 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 14:31 Saurabh Chakrabarti [this message]
2014-05-21 13:51 ` [ath9k-devel] atheros chipset does not recover after going into unresponsive state Saurabh Chakrabarti

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=537B674F.70208@amideeptech.com \
    --to=saurabh.chakrabarti@amideeptech.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.