[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Hi,

I've USB WiFi stick with VID 0x0cf3 and PID 0x1006, it's TPLink TL-WN422Gv2.
Everything works fine, even the WPA, but until I reset my board (it's ARMv4t
ts7250/mach-ep93xx). Then if the driver is loaded again, it ends with
"ath9k_htc: Target is unresponsive" error. If I replug the device, or power
on/off the board everything starts to work again without any problem, so maybe
the driver is somehow stuck somewhere?

I've tried to rmmod all the modules, but it's still same error, then I've
tried to increase the wait_for_completion_timeout[1] from HZ to HZ*8, but it
didn't helped anyway. Looks like the problem somewhere deeper, like that the
device is left in some undefined state, or maybe some timing/USB problem?

Any hint what could get wrong at this stage? How to debug this? Is it possible
to perform some reset of the device, so I can "emulate" replug of the device?
It's pretty easy to reproduce, happens always, so it shouldn't be that hard to
find the root cause of the problem. Thank you for any hints.

1. line 128 in htc_drv_init.c time_left = wait_for_completion_timeout(&priv->htc->target_wait, HZ);

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Mohammed Shafi]

On Fri, Nov 19, 2010 at 4:35 PM, Petr ?tetiar <ynezz@true.cz> wrote:
> Hi,
Hi
>
> I've USB WiFi stick with VID 0x0cf3 and PID 0x1006, it's TPLink TL-WN422Gv2.
> Everything works fine, even the WPA, but until I reset my board (it's ARMv4t
> ts7250/mach-ep93xx). Then if the driver is loaded again, it ends with
> "ath9k_htc: Target is unresponsive" error. If I replug the device, or power
> on/off the board everything starts to work again without any problem, so maybe
> the driver is somehow stuck somewhere?
>May be the firmware gets loaded/activated only when the device pugged in?
> I've tried to rmmod all the modules, but it's still same error, then I've
> tried to increase the wait_for_completion_timeout[1] from HZ to HZ*8, but it
> didn't helped anyway. Looks like the problem somewhere deeper, like that the
> device is left in some undefined state, or maybe some timing/USB problem?
>
> Any hint what could get wrong at this stage? How to debug this? Is it possible
> to perform some reset of the device, so I can "emulate" replug of the device?
> It's pretty easy to reproduce, happens always, so it shouldn't be that hard to
> find the root cause of the problem. Thank you for any hints.
>We will look into it
> 1. line 128 in htc_drv_init.c time_left = wait_for_completion_timeout(&priv->htc->target_wait, HZ);
>
> -- ynezz
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-19 17:36:27]:

> May be the firmware gets loaded/activated only when the device pugged in?

The firmware seems to be loaded every time, but after the load it fails. I
don't have the device here, so I can't provide the complete log (will do it
later today) but it's always something along these lines:

1. some message about CRDA regulatory domain
2. messge about loaded firmware ~50kB from filename ar9271.fw
3. "Target is unresponsive" error

How could I check if the firmware is activated? Is it possible to do the "hard
reset" from the software somehow? I would try to hard reset the device and
then load the firmware. Strange thing is, that the firmware seems to be loaded
without any error, but than it fails. I've looked at the code really quickly
yesterday and it seems, that the device is always put into some kind of the
deep sleep mode if the module is unloaded, maybe that there's problem with it?

> We will look into it

Thanks. I'll enable debugging and will post hopefully more verbose log soon.

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Petr ?tetiar <ynezz@true.cz> [2010-11-19 13:27:37]:

> Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-19 17:36:27]:
> 
> > May be the firmware gets loaded/activated only when the device pugged in?
> 
> 1. some message about CRDA regulatory domain
> 2. messge about loaded firmware ~50kB from filename ar9271.fw
> 3. "Target is unresponsive" error

after reboot:

	[  469.790000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
	[  470.790000] usb 1-3: ath9k_htc: Target is unresponsive
	[  470.790000] Failed to initialize the device
	[  470.810000] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22
	[  470.820000] usbcore: registered new interface driver ath9k_hif_usb

replug:

	[  477.060000] usb 1-3: USB disconnect, address 2
	[  478.780000] usb 1-3: new full speed USB device using ep93xx-ohci and address 3
	[  478.980000] usb 1-3: New USB device found, idVendor=0cf3, idProduct=1006
	[  478.980000] usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=48
	[  479.010000] usb 1-3: Product: USB2.0 WLAN
	[  479.010000] usb 1-3: Manufacturer: ATHEROS
	[  479.020000] usb 1-3: SerialNumber: 12345
	[  479.470000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
	[  479.760000] usb 1-3: ath9k_htc: HTC initialized with 33 credits
	[  485.670000] cfg80211: Calling CRDA for country: CN
	[  485.700000] usb 1-3: ath9k_htc: USB layer initialized

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Digged into it more, added few printks, after reboot:

	[  521.710000] ath9k_hif_usb_probe
	[  521.720000] ath9k_hif_usb_dev_init
	[  521.770000] ath9k_hif_usb_download_fw - before firmware download
	[  522.210000] ath9k_hif_usb_download_fw - after firmware download
	[  522.210000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
	[  522.220000] ath9k_htc_probe_device
	[  522.230000] ath9k_htc_wait_for_target
	[  522.470000] ath9k_htc_rx_msg - endpoint_id: 0x1 msg_id: 0x18
	[  523.230000] usb 1-3: ath9k_htc: Target is unresponsive
	[  523.230000] Failed to initialize the device
	[  523.250000] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22
	[  523.260000] usbcore: registered new interface driver ath9k_hif_usb

after replug:

	[  624.610000] usb 1-3: USB disconnect, address 2
	[  626.050000] usb 1-3: new full speed USB device using ep93xx-ohci and address 3
	[  626.250000] usb 1-3: New USB device found, idVendor=0cf3, idProduct=1006
	[  626.250000] usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=48
	[  626.270000] usb 1-3: Product: USB2.0 WLAN
	[  626.270000] usb 1-3: Manufacturer: ATHEROS
	[  626.270000] usb 1-3: SerialNumber: 12345
	[  626.290000] ath9k_hif_usb_probe
	[  626.290000] ath9k_hif_usb_dev_init
	[  626.370000] ath9k_hif_usb_download_fw - before firmware download
	[  626.740000] ath9k_hif_usb_download_fw - after firmware download
	[  626.750000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
	[  626.760000] ath9k_htc_probe_device
	[  626.760000] ath9k_htc_wait_for_target
	[  627.010000] ath9k_htc_rx_msg - endpoint_id: 0x0 msg_id: 0x1
	[  627.010000] htc_process_target_rdy
	[..snip..]

So after the reboot, it seems to me, that the device is left in some wrong state:

	[  522.230000] ath9k_htc_wait_for_target
	[  522.470000] ath9k_htc_rx_msg - endpoint_id: 0x1 msg_id: 0x18
	[  523.230000] usb 1-3: ath9k_htc: Target is unresponsive

versus correct behaviour after replug:

	[  626.760000] ath9k_htc_wait_for_target
	[  627.010000] ath9k_htc_rx_msg - endpoint_id: 0x0 msg_id: 0x1
	[  627.010000] htc_process_target_rdy

Endpoint is 1 vs 0 and msg_id is 0x18 and not as expected 0x1 (HTC_MSG_READY_ID).
I'm quite clueless what's going on there, but I hope it helps at least...

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Mohammed Shafi]

On Sat, Nov 20, 2010 at 7:29 PM, Petr ?tetiar <ynezz@true.cz> wrote:
> Digged into it more, added few printks, after reboot:

Sorry for the late reply and thanks for your effort
>
> ? ? ? ?[ ?521.710000] ath9k_hif_usb_probe
> ? ? ? ?[ ?521.720000] ath9k_hif_usb_dev_init
> ? ? ? ?[ ?521.770000] ath9k_hif_usb_download_fw - before firmware download
> ? ? ? ?[ ?522.210000] ath9k_hif_usb_download_fw - after firmware download
> ? ? ? ?[ ?522.210000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
> ? ? ? ?[ ?522.220000] ath9k_htc_probe_device
> ? ? ? ?[ ?522.230000] ath9k_htc_wait_for_target
> ? ? ? ?[ ?522.470000] ath9k_htc_rx_msg - endpoint_id: 0x1 msg_id: 0x18
> ? ? ? ?[ ?523.230000] usb 1-3: ath9k_htc: Target is unresponsive

It is quite clear that the problem is loading the firmware.So can you
please try with the latest firmware available in
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree
I am sure you would have read
http://wireless.kernel.org/en/users/Drivers/ath9k_htc
> ? ? ? ?[ ?523.230000] Failed to initialize the device
> ? ? ? ?[ ?523.250000] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22
> ? ? ? ?[ ?523.260000] usbcore: registered new interface driver ath9k_hif_usb
>
> after replug:
>
> ? ? ? ?[ ?624.610000] usb 1-3: USB disconnect, address 2
> ? ? ? ?[ ?626.050000] usb 1-3: new full speed USB device using ep93xx-ohci and address 3
> ? ? ? ?[ ?626.250000] usb 1-3: New USB device found, idVendor=0cf3, idProduct=1006
> ? ? ? ?[ ?626.250000] usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=48
> ? ? ? ?[ ?626.270000] usb 1-3: Product: USB2.0 WLAN
> ? ? ? ?[ ?626.270000] usb 1-3: Manufacturer: ATHEROS
> ? ? ? ?[ ?626.270000] usb 1-3: SerialNumber: 12345
> ? ? ? ?[ ?626.290000] ath9k_hif_usb_probe
> ? ? ? ?[ ?626.290000] ath9k_hif_usb_dev_init
> ? ? ? ?[ ?626.370000] ath9k_hif_usb_download_fw - before firmware download
> ? ? ? ?[ ?626.740000] ath9k_hif_usb_download_fw - after firmware download
> ? ? ? ?[ ?626.750000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
> ? ? ? ?[ ?626.760000] ath9k_htc_probe_device
> ? ? ? ?[ ?626.760000] ath9k_htc_wait_for_target
> ? ? ? ?[ ?627.010000] ath9k_htc_rx_msg - endpoint_id: 0x0 msg_id: 0x1
> ? ? ? ?[ ?627.010000] htc_process_target_rdy
> ? ? ? ?[..snip..]
>
> So after the reboot, it seems to me, that the device is left in some wrong state:
>
> ? ? ? ?[ ?522.230000] ath9k_htc_wait_for_target
> ? ? ? ?[ ?522.470000] ath9k_htc_rx_msg - endpoint_id: 0x1 msg_id: 0x18
> ? ? ? ?[ ?523.230000] usb 1-3: ath9k_htc: Target is unresponsive
>
I will try to reproduce the issue.
> versus correct behaviour after replug:
>
> ? ? ? ?[ ?626.760000] ath9k_htc_wait_for_target
> ? ? ? ?[ ?627.010000] ath9k_htc_rx_msg - endpoint_id: 0x0 msg_id: 0x1
> ? ? ? ?[ ?627.010000] htc_process_target_rdy
>
> Endpoint is 1 vs 0 and msg_id is 0x18 and not as expected 0x1 (HTC_MSG_READY_ID).
> I'm quite clueless what's going on there, but I hope it helps at least...
>
> -- ynezz
>

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 10:40:16]:

> It is quite clear that the problem is loading the firmware.So can you
> please try with the latest firmware available in
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree

Yes, I use the "latest" (there are only two commits, two versions, so I use
the last one from 2010-05-17). I've tried also the previous version, but it's
the same problem.

> I am sure you would have read
> http://wireless.kernel.org/en/users/Drivers/ath9k_htc

Yes, I did.

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Mohammed Shafi]

On Fri, Nov 19, 2010 at 4:35 PM, Petr ?tetiar <ynezz@true.cz> wrote:
> Hi,
>
> I've USB WiFi stick with VID 0x0cf3 and PID 0x1006, it's TPLink TL-WN422Gv2.
> Everything works fine, even the WPA, but until I reset my board (it's ARMv4t
> ts7250/mach-ep93xx). Then if the driver is loaded again, it ends with
> "ath9k_htc: Target is unresponsive" error. If I replug the device, or power
> on/off the board everything starts to work again without any problem, so maybe
> the driver is somehow stuck somewhere?
>
> I've tried to rmmod all the modules, but it's still same error, then I've
> tried to increase the wait_for_completion_timeout[1] from HZ to HZ*8, but it
> didn't helped anyway. Looks like the problem somewhere deeper, like that the
> device is left in some undefined state, or maybe some timing/USB problem?
>
> Any hint what could get wrong at this stage? How to debug this? Is it possible
> to perform some reset of the device, so I can "emulate" replug of the device?
> It's pretty easy to reproduce, happens always, so it shouldn't be that hard to
> find the root cause of the problem. Thank you for any hints.
>
> 1. line 128 in htc_drv_init.c time_left = wait_for_completion_timeout(&priv->htc->target_wait, HZ);
Can you please try out ..
htc_drv_init.c time_left =
wait_for_completion_timeout(&priv->htc->target_wait, HZ/4); this
should  obviously fail

and

htc_drv_init.c time_left =
wait_for_completion_timeout(&priv->htc->target_wait, 30*HZ);

>
> -- ynezz
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 11:15:17]:

> On Fri, Nov 19, 2010 at 4:35 PM, Petr ?tetiar <ynezz@true.cz> wrote:
> >
> > 1. line 128 in htc_drv_init.c time_left =
> > wait_for_completion_timeout(&priv->htc->target_wait, HZ);
> Can you please try out ..  htc_drv_init.c time_left =
> wait_for_completion_timeout(&priv->htc->target_wait, HZ/4); this should
> obviously fail

I'll try that later today, but it I think, that it will fail also.

> htc_drv_init.c time_left =
> wait_for_completion_timeout(&priv->htc->target_wait, 30*HZ);

I've even tried 100*HZ, but it fails anyway and I think, that the root of the
problem is somewhere else. This point is just the consequence of the failure
in htc_process_target_ready(), so even adding the 1000*HZ wouldn't help it
much :-)

As I understand it, host downloads the firmware to the MCU with
FIRMWARE_DOWNLOAD, then if it's sending of the firmware complete the host
sends FIRMWARE_DOWNLOAD_COMP and then MCU should respond with
HTC_MSG_READY_ID, but it didn't in my case for some reason. It's responding
with msg 0x18 on USB endpoint 0x1, instead of msg 0x1(HTC_MSG_READY_ID) on USB
endpoint 0.

I don't have the sources of the firmware, so I don't know how it works
internally, but maybe it's just wrong timing assumption somewhere or something
similar. That ARM board I'm using is kind of slow, it's like 200MHz(99
Bogomips), so everything takes quite longer time to complete, than on one is
used on desktop PC.

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Mohammed Shafi]

2010/11/22 Petr ?tetiar <ynezz@true.cz>:
> Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 11:15:17]:
>
>> On Fri, Nov 19, 2010 at 4:35 PM, Petr ?tetiar <ynezz@true.cz> wrote:
>> >
>> > 1. line 128 in htc_drv_init.c time_left =
>> > wait_for_completion_timeout(&priv->htc->target_wait, HZ);
>> Can you please try out .. ?htc_drv_init.c time_left =
>> wait_for_completion_timeout(&priv->htc->target_wait, HZ/4); this should
>> obviously fail
>
> I'll try that later today, but it I think, that it will fail also.
>
>> htc_drv_init.c time_left =
>> wait_for_completion_timeout(&priv->htc->target_wait, 30*HZ);
>
> I've even tried 100*HZ, but it fails anyway and I think, that the root of the
> problem is somewhere else. This point is just the consequence of the failure
> in htc_process_target_ready(), so even adding the 1000*HZ wouldn't help it
> much :-)

Yes then the problem is somewhere else.
>
> As I understand it, host downloads the firmware to the MCU with
> FIRMWARE_DOWNLOAD, then if it's sending of the firmware complete the host
> sends FIRMWARE_DOWNLOAD_COMP and then MCU should respond with
> HTC_MSG_READY_ID, but it didn't in my case for some reason. It's responding
> with msg 0x18 on USB endpoint 0x1, instead of msg 0x1(HTC_MSG_READY_ID) on USB
> endpoint 0.
>
> I don't have the sources of the firmware, so I don't know how it works
> internally, but maybe it's just wrong timing assumption somewhere or something
> similar. That ARM board I'm using is kind of slow, it's like 200MHz(99
> Bogomips), so everything takes quite longer time to complete, than on one is
> used on desktop PC.

I am trying to reproduce the same in my PC  but it never got it
reproduced , can you please try with latest wireless testing tree or
compat wireless ?
Can you please disable CONFIG_USB_DEBUG .
Perhaps it because of the board , are you getting the same problem in
your machines or laptop ?
>
> -- ynezz
>

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 15:12:18]:

> I am trying to reproduce the same in my PC  but it never got it reproduced ,
> can you please try with latest wireless testing tree or compat wireless ?
> Can you please disable CONFIG_USB_DEBUG .  Perhaps it because of the board ,
> are you getting the same problem in your machines or laptop ?

Ok, I'll try all the suggested, haven't tried it on desktop/laptop yet, but I
think, that it will work.

I think, that there's no problem with my board at all, USB works fine, other
WiFi USB dongle from Ralink does work fine as is USB hardrive and flash disk,
so no power issue or something like that, it behaves the same on the second
board I've also.

Anyway, If I replug the dongle, it starts working again. So what's wrong, my
board or WiFi dongle with ath9k chipset? :-) I can reset the board 20 times,
all 20 times Ralink works, downloads the firmware always correctly, but the
ath9k doesn't, it fails after first soft reboot.

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Mohammed Shafi]

On Mon, Nov 22, 2010 at 5:00 PM, Petr ?tetiar <ynezz@true.cz> wrote:
> Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 15:12:18]:
>
>> I am trying to reproduce the same in my PC ?but it never got it reproduced ,
>> can you please try with latest wireless testing tree or compat wireless ?
>> Can you please disable CONFIG_USB_DEBUG . ?Perhaps it because of the board ,
>> are you getting the same problem in your machines or laptop ?
>
> Ok, I'll try all the suggested, haven't tried it on desktop/laptop yet, but I
> think, that it will work.
>
> I think, that there's no problem with my board at all, USB works fine, other
> WiFi USB dongle from Ralink does work fine as is USB hardrive and flash disk,
> so no power issue or something like that, it behaves the same on the second
> board I've also.
>
> Anyway, If I replug the dongle, it starts working again. So what's wrong, my
> board or WiFi dongle with ath9k chipset? :-) I can reset the board 20 times,
> all 20 times Ralink works, downloads the firmware always correctly, but the
> ath9k doesn't, it fails after first soft reboot.

Can you just please  look into the status of CONFIG_PM  in
include/generated/autoconf.h, what is its value ?
>
> -- ynezz
>

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 19:11:53]:

> Can you just please  look into the status of CONFIG_PM  in
> include/generated/autoconf.h, what is its value ?

I don't use PM, so it's not in this file.

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Rajkumar Manoharan]

On Mon, Nov 22, 2010 at 09:17:16PM +0530, Petr ?tetiar wrote:
> Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 19:11:53]:
> 
> > Can you just please  look into the status of CONFIG_PM  in
> > include/generated/autoconf.h, what is its value ?
> 
> I don't use PM, so it's not in this file.

Please apply the following patch and try again

https://patchwork.kernel.org/patch/369751/

--
Rajkumar

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Rajkumar Manoharan]

On Fri, Dec 03, 2010 at 04:06:45PM +0530, Rajkumar Manoharan wrote:
> On Mon, Nov 22, 2010 at 09:17:16PM +0530, Petr ?tetiar wrote:
> > Mohammed Shafi <shafi.wireless@gmail.com> [2010-11-22 19:11:53]:
> > 
> > > Can you just please  look into the status of CONFIG_PM  in
> > > include/generated/autoconf.h, what is its value ?
> > 
> > I don't use PM, so it's not in this file.
> 
> Please apply the following patch and try again
> 
> https://patchwork.kernel.org/patch/369751/
> 

Please apply the following firmware patch on linux-firmware git
then use the updated ar9271.fw

http://marc.info/?l=linux-wireless&m=128214177613540&w=3

--
Rajkumar

[ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error

[Petr Štetiar]

Rajkumar Manoharan <rmanoharan@Atheros.com> [2010-12-03 17:03:33]:

> > Please apply the following patch and try again
> > 
> > https://patchwork.kernel.org/patch/369751/
> > 
> 
> Please apply the following firmware patch on linux-firmware git
> then use the updated ar9271.fw
> 
> http://marc.info/?l=linux-wireless&m=128214177613540&w=3

Hi,

thank you for the patches, the issue seems to be gone now, cool :-)

I don't know if it's standard or expected behavior, but it takes about 30
seconds to connect to my WPA/TKIP AP (Asus WL500g):

	root at ts72xx:~# time ifup wlan0 && time ping -c1 www.kernel.org
	WPA: Configuring Interface
	real    0m 8.08s
	user    0m 0.26s
	sys     0m 0.58s
	PING www.kernel.org (199.6.1.164): 56 data bytes
	64 bytes from 199.6.1.164: seq=0 ttl=54 time=50.000 ms

	--- www.kernel.org ping statistics ---
	1 packets transmitted, 1 packets received, 0% packet loss
	round-trip min/avg/max = 50.000/50.000/50.000 ms
	real    0m 26.24s
	user    0m 0.00s
	sys     0m 0.04s

This is from the dmesg:

[   22.730000] usb 1-3: New USB device found, idVendor=0cf3, idProduct=1006
[   22.730000] usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[   22.740000] usb 1-3: Product: USB2.0 WLAN
[   22.750000] usb 1-3: Manufacturer: ATHEROS
[   22.750000] usb 1-3: SerialNumber: 12345
[   23.380000] cfg80211: Calling CRDA to update world regulatory domain
[   25.270000] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51312
[   25.570000] usb 1-3: ath9k_htc: HTC initialized with 33 credits
[   30.890000] ath: EEPROM regdomain: 0x809c
[   30.890000] ath: EEPROM indicates we should expect a country code
[   30.890000] ath: doing EEPROM country->regdmn map search
[   30.890000] ath: country maps to regdmn code: 0x52
[   30.890000] ath: Country alpha2 being used: CN
[   30.890000] ath: Regpair used: 0x52
[   31.830000] cfg80211: Calling CRDA for country: CN
[   31.870000] Registered led device: ath9k-phy0::radio
[   31.870000] Registered led device: ath9k-phy0::assoc
[   31.870000] Registered led device: ath9k-phy0::tx
[   31.880000] Registered led device: ath9k-phy0::rx
[   31.880000] usb 1-3: ath9k_htc: USB layer initialized
[   31.880000] usbcore: registered new interface driver ath9k_hif_usb
[   67.930000] wlan0: deauthenticating from 00:1d:60:9d:a8:e6 by local choice (reason=3)
[   73.740000] wlan0: authenticate with 00:1d:60:9d:a8:e6 (try 1)
[   73.740000] wlan0: authenticated
[   75.080000] wlan0: associate with 00:1d:60:9d:a8:e6 (try 1)
[   76.420000] wlan0: RX AssocResp from 00:1d:60:9d:a8:e6 (capab=0x11 status=0 aid=1)
[   76.420000] wlan0: associated

This is not related to the previous issue or the fix, I think, that it took a
lot more without the firmware patch before. Thanks for any pointers.

-- ynezz

[ath9k-devel] ath9k_htc, 2.6.36 and

[Levi Civita]

Rajkumar Manoharan <rmanoharan <at> atheros.com> writes:

> 
> On Fri, Dec 03, 2010 at 04:06:45PM +0530, Rajkumar Manoharan wrote:
> > On Mon, Nov 22, 2010 at 09:17:16PM +0530, Petr ?tetiar wrote:
> > > Mohammed Shafi <shafi.wireless <at> gmail.com> [2010-11-22 19:11:53]:
> > > 
> > > > Can you just please  look into the status of CONFIG_PM  in
> > > > include/generated/autoconf.h, what is its value ?
> > > 
> > > I don't use PM, so it's not in this file.
> > 
> > Please apply the following patch and try again
> > 
> > https://patchwork.kernel.org/patch/369751/
> > 
> 
> Please apply the following firmware patch on linux-firmware git
> then use the updated ar9271.fw
> 
> http://marc.info/?l=linux-wireless&m=128214177613540&w=3
> 
> --
> Rajkumar
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel <at> lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> 


Hey guys, I have the exact same problem as described in this thread.  

I am not a Linux expert though.  

How do I apply the patch you linked above to the firmware?  

Here is my dmesg log:

$ grep ath9k /var/log/dmesg
[   23.842332] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51312
[   24.841586] usb 1-3: ath9k_htc: Target is unresponsive
[   24.843046] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22
[   24.843087] usbcore: registered new interface driver ath9k_hif_usb

Thanks!

[ath9k-devel] ath9k_htc, 2.6.36 and

[Mohammed Shafi]

On Sat, Jul 30, 2011 at 6:53 PM, Levi Civita
<tullio.levi.civita@gmail.com> wrote:
> Rajkumar Manoharan <rmanoharan <at> atheros.com> writes:
>
>>
>> On Fri, Dec 03, 2010 at 04:06:45PM +0530, Rajkumar Manoharan wrote:
>> > On Mon, Nov 22, 2010 at 09:17:16PM +0530, Petr ?tetiar wrote:
>> > > Mohammed Shafi <shafi.wireless <at> gmail.com> [2010-11-22 19:11:53]:
>> > >
>> > > > Can you just please ?look into the status of CONFIG_PM ?in
>> > > > include/generated/autoconf.h, what is its value ?
>> > >
>> > > I don't use PM, so it's not in this file.
>> >
>> > Please apply the following patch and try again
>> >
>> > https://patchwork.kernel.org/patch/369751/
>> >
>>
>> Please apply the following firmware patch on linux-firmware git
>> then use the updated ar9271.fw
>>
>> http://marc.info/?l=linux-wireless&m=128214177613540&w=3
>>
>> --
>> Rajkumar
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel <at> lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
> Hey guys, I have the exact same problem as described in this thread.
>
> I am not a Linux expert though.
>
> How do I apply the patch you linked above to the firmware?

please jut download the ar9271.fw from (search ar9271.fw  after you
had gone into the link).
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree

interested in trying  latest with compat wireless, read
http://linuxwireless.org/en/users/Drivers/ath9k_htc

>
> Here is my dmesg log:
>
> $ grep ath9k /var/log/dmesg
> [ ? 23.842332] usb 1-3: ath9k_htc: Transferred FW: ar9271.fw, size: 51312
> [ ? 24.841586] usb 1-3: ath9k_htc: Target is unresponsive
> [ ? 24.843046] ath9k_hif_usb: probe of 1-3:1.0 failed with error -22
> [ ? 24.843087] usbcore: registered new interface driver ath9k_hif_usb
>
> Thanks!
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi