Modify

Opened 5 years ago

Last modified 4 years ago

#13850 new defect

ath9k_htc "target unresponsive"

Reported by: stephan.oelze@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version: Attitude Adjustment 12.09
Keywords: ath9k ath9k_htc target unresponsive Cc:

Description

Hello!

When using devices which uses ath9k_htc compatible devices this error occours from time to time. In my case i can confirm for Alfa AWUS036NHA and Ubiquiti wifi station ext.

When the router reboots with firmware loaded "target unresponsive" occours.
There are several Posts in the past 2 years for documentation.
There is an firmware fix for it :

https://github.com/qca/open-ath9k-htc-firmware/issues/1

Another Ticket in dev.openwrt.org:

/ticket/9486.html

I can confirm that olerems firmware fix works on x86. (warm reboot and pm-suspend)
Is there a way to implement this patch into Openwrt?

Theese devices are a great and cheap option for wifi link over mid distance with awsome throughput. In my case its 70-80mbits tcp througput over ~ 800 meters using directional antenna. (depending on Weather)

Regards!
derdigge

Attachments (1)

876-ath9k-htc-target-unresponsive.patch (629 bytes) - added by anonymous 5 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 follow-ups: Changed 5 years ago by stepahn.oelze@…

I am curently testing the attached patch on attitude adjustment.
In the last 8 hours i was not able to make it unresponsive again.

876-ath9k-htc-target-unresponsive.patch

Index: compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/htc_drv_init.c
===================================================================
--- compat-wireless-2013-02-22.orig/drivers/net/wireless/ath/ath9k/htc_drv_init.c	2013-07-10 22:32:53.443140645 +0200
+++ compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/htc_drv_init.c	2013-07-10 22:43:37.169185154 +0200
@@ -849,6 +849,7 @@
 	if (error != 0)
 		goto err_rx;
 
+	ath9k_hw_disable(priv->ah);
 #ifdef CONFIG_MAC80211_LEDS
 	/* must be initialized before ieee80211_register_hw */
 	priv->led_cdev.default_trigger = ieee80211_create_tpt_led_trigger(priv->hw,

It compiles wit aa final buildroot.
If it continiues wirking, i quilt one for bb trunk.
Maybe someone can test it and give sone feedback?

Changed 5 years ago by anonymous

comment:2 Changed 5 years ago by stephan.oelze@…

This still works on 12.09.
I was not able to bring it in inresponsive state anymore.

HERE IS NO SPAM YOU STUPID DETECTION BOT!!!

In the next week i bring it to up trunk an test it on some routers.

comment:3 Changed 4 years ago by pingo

I have two TL-WR1043ND routers but only one exhibits the "target unresponsive" problem, which is very odd to me. One is v1.8 and the other is v1.2(DE) both run the same precompiled image of Openwrt 12.09, r36088

I tried connecting a TL-WN722N usb wifi to both of them and it's interesting that the results are different.

On v1.2(DE) when the router boots up, the wifi always fails to initialize like so:

Aug 19 22:20:04 OpenWrt kern.info kernel: [   11.330000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
Aug 19 22:20:04 OpenWrt kern.err kernel: [   12.340000] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Aug 19 22:20:04 OpenWrt kern.err kernel: [   12.340000] ath9k_htc: Failed to initialize the device
Aug 19 22:20:04 OpenWrt kern.info kernel: [   12.370000] usb 1-1: ath9k_htc: USB layer deinitialized

But if I unplug and plug the wifi back it, it initializes successfully like so:

Aug 19 22:22:31 OpenWrt kern.info kernel: [  159.480000] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
Aug 19 22:22:31 OpenWrt kern.info kernel: [  159.870000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
Aug 19 22:22:32 OpenWrt kern.info kernel: [  160.100000] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
Aug 19 22:22:32 OpenWrt kern.info kernel: [  160.310000] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
Aug 19 22:22:32 OpenWrt kern.debug kernel: [  160.360000] Registered led device: ath9k_htc-phy2

However the v1.8 router does not have this problem at all and it always succeeds to initialize the same usb wifi on boot up like so:

Aug 21 16:50:04 OpenWrt kern.info kernel: [   10.900000] usbcore: registered new interface driver ath9k_htc
Aug 21 16:50:06 OpenWrt kern.info kernel: [   14.920000] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
Aug 21 16:50:07 OpenWrt kern.info kernel: [   15.550000] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
Aug 21 16:50:07 OpenWrt kern.info kernel: [   15.780000] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
Aug 21 16:50:08 OpenWrt kern.info kernel: [   16.070000] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
Aug 21 16:50:08 OpenWrt kern.debug kernel: [   16.140000] Registered led device: ath9k_htc-phy1

The problem persist with or without a usb hub.

Does anyone know what the difference might be? Should I try compiling the above patch?

Edit: After reading https://github.com/qca/open-ath9k-htc-firmware/issues/1 I just tried to power cycle the problematic router instead of doing a software reboot and the the wifi initialized just fine. This behavior supports the theory in that thread about the wifi device needing a power cycle of the usb port in order to properly initialize and I guess that between v1.8 and v1.2(DE) something changed and the v1.2(DE) board does not power cycle the usb port on reboot while the v1.8 does? Should I try applying the above attached patch or is that unrelated?

Last edited 4 years ago by pingo (previous) (diff)

comment:4 Changed 4 years ago by carlosmf.pt@…

I'm also having problems in connecting the USB TL-WN722N adapter.
With current trunk, the device isn't even detected. There is no output at dmesg when I plugin the adapter and there is no output at lsusb.

comment:5 in reply to: ↑ 1 Changed 4 years ago by anonymous

Replying to stepahn.oelze@…:

I am curently testing the attached patch on attitude adjustment.
In the last 8 hours i was not able to make it unresponsive again.

876-ath9k-htc-target-unresponsive.patch

Index: compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/htc_drv_init.c
===================================================================
--- compat-wireless-2013-02-22.orig/drivers/net/wireless/ath/ath9k/htc_drv_init.c	2013-07-10 22:32:53.443140645 +0200
+++ compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/htc_drv_init.c	2013-07-10 22:43:37.169185154 +0200
@@ -849,6 +849,7 @@
 	if (error != 0)
 		goto err_rx;
 
+	ath9k_hw_disable(priv->ah);
 #ifdef CONFIG_MAC80211_LEDS
 	/* must be initialized before ieee80211_register_hw */
 	priv->led_cdev.default_trigger = ieee80211_create_tpt_led_trigger(priv->hw,

It compiles wit aa final buildroot.
If it continiues wirking, i quilt one for bb trunk.
Maybe someone can test it and give sone feedback?

thanks,I am testing it. it works fine now.Target is unresponsive does not appear again now.I will give my final test result.

comment:6 in reply to: ↑ 1 Changed 4 years ago by anonymous

Replying to stepahn.oelze@…:

I am curently testing the attached patch on attitude adjustment.
In the last 8 hours i was not able to make it unresponsive again.

876-ath9k-htc-target-unresponsive.patch

Index: compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/htc_drv_init.c
===================================================================
--- compat-wireless-2013-02-22.orig/drivers/net/wireless/ath/ath9k/htc_drv_init.c	2013-07-10 22:32:53.443140645 +0200
+++ compat-wireless-2013-02-22/drivers/net/wireless/ath/ath9k/htc_drv_init.c	2013-07-10 22:43:37.169185154 +0200
@@ -849,6 +849,7 @@
 	if (error != 0)
 		goto err_rx;
 
+	ath9k_hw_disable(priv->ah);
 #ifdef CONFIG_MAC80211_LEDS
 	/* must be initialized before ieee80211_register_hw */
 	priv->led_cdev.default_trigger = ieee80211_create_tpt_led_trigger(priv->hw,

It compiles wit aa final buildroot.
If it continiues wirking, i quilt one for bb trunk.
Maybe someone can test it and give sone feedback?

Hi,it works fine after 2000 times reboot.i think this issue has been fixed.thanks a lot!

comment:7 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.