[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Jian Li]

hi all:
 
the linux box version is 2.6.35.12. and the compat wireless version is "compat-wireless-2011-11-20". Fireware version is 1.3?
 
wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB wifi.
 
the question is that wifi failed to initialize when i reboot the box. the print message as below :
 
 
ADDRCONF(NETDEV_UP): WAN1: link is not ready
usb 1-1: default language 0x0409
usb 1-1: udev 2, busnum 1, minor = 1
usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: ATHEROS
usb 1-1: SerialNumber: 12345
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
usb usb3: suspend_rh (auto-stop)
usb usb4: suspend_rh (auto-stop)
usb usb5: suspend_rh (auto-stop)
usb usb2: suspend_rh (auto-stop)
r8169 0000:02:00.0: WAN1: link up
ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
Backport based on linux-next.git next-20111118
cfg80211: Calling CRDA to update world regulatory domain
ath9k_htc 1-1:1.0: usb_probe_interface
ath9k_htc 1-1:1.0: usb_probe_interface - got id
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc
g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
 
 
but if i unplug and plug the wifi, it will be initilized ok! could you help me
 
 
ehci_hcd 0000:00:1d.7: port 1 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
usb 1-1: default language 0x0409
usb 1-1: udev 2, busnum 1, minor = 1
usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: ATHEROS
usb 1-1: SerialNumber: 12345
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
ath9k_htc 1-1:1.0: usb_probe_interface
ath9k_htc 1-1:1.0: usb_probe_interface - got id
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
ieee80211 phy0: Atheros AR9271 Rev:1
cfg80211: Pending regulatory request, waiting for it to be processed...
Registered led device: ath9k_htc-phy0
usb 1-1: ath9k_htc: USB layer initialized
drivers/usb/core/inode.c: creating file '002'
physical device wlan0 UP!!!  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111123/cded6f40/attachment.htm 

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Jian Li]

hi all:
 
the linux box version is 2.6.35.12. and the compat wireless version is "compat-wireless-2011-11-20". Fireware version is 1.3?
 
wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB wifi.
 
the question is that wifi failed to initialize when i reboot the box. the print message as below :
 
 
ADDRCONF(NETDEV_UP): WAN1: link is not ready
usb 1-1: default language 0x0409
usb 1-1: udev 2, busnum 1, minor = 1
usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: ATHEROS
usb 1-1: SerialNumber: 12345
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
usb usb3: suspend_rh (auto-stop)
usb usb4: suspend_rh (auto-stop)
usb usb5: suspend_rh (auto-stop)
usb usb2: suspend_rh (auto-stop)
r8169 0000:02:00.0: WAN1: link up
ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
Backport based on linux-next.git next-20111118
cfg80211: Calling CRDA to update world regulatory domain
ath9k_htc 1-1:1.0: usb_probe_interface
ath9k_htc 1-1:1.0: usb_probe_interface - got id
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc
g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
 
 
but if i unplug and plug the wifi, it will be initilized ok! could you help me
 
 
ehci_hcd 0000:00:1d.7: port 1 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
usb 1-1: default language 0x0409
usb 1-1: udev 2, busnum 1, minor = 1
usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: ATHEROS
usb 1-1: SerialNumber: 12345
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
ath9k_htc 1-1:1.0: usb_probe_interface
ath9k_htc 1-1:1.0: usb_probe_interface - got id
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
ieee80211 phy0: Atheros AR9271 Rev:1
cfg80211: Pending regulatory request, waiting for it to be processed...
Registered led device: ath9k_htc-phy0
usb 1-1: ath9k_htc: USB layer initialized
drivers/usb/core/inode.c: creating file '002'
physical device wlan0 UP!!! 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111123/2ad3f296/attachment.htm 

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Jian Li]

hi all?
 
i just want to know about if this is a chip bug or firmware bug. becasue it is ok when i change the wifi to tplink wn821n whose chip is AR7010.
 


From: lijian1976@hotmail.com
To: ath9k-devel at lists.ath9k.org
Subject: ath9k 9271 print "Target is unresponsive" after reboot
Date: Wed, 23 Nov 2011 16:52:48 +0800






hi all:
 
the linux box version is 2.6.35.12. and the compat wireless version is "compat-wireless-2011-11-20". Fireware version is 1.3?
 
wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB wifi.
 
the question is that wifi failed to initialize when i reboot the box. the print message as below :
 
 
ADDRCONF(NETDEV_UP): WAN1: link is not ready
usb 1-1: default language 0x0409
usb 1-1: udev 2, busnum 1, minor = 1
usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: ATHEROS
usb 1-1: SerialNumber: 12345
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
usb usb3: suspend_rh (auto-stop)
usb usb4: suspend_rh (auto-stop)
usb usb5: suspend_rh (auto-stop)
usb usb2: suspend_rh (auto-stop)
r8169 0000:02:00.0: WAN1: link up
ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
Backport based on linux-next.git next-20111118
cfg80211: Calling CRDA to update world regulatory domain
ath9k_htc 1-1:1.0: usb_probe_interface
ath9k_htc 1-1:1.0: usb_probe_interface - got id
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc
g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
 
 
but if i unplug and plug the wifi, it will be initilized ok! could you help me
 
 
ehci_hcd 0000:00:1d.7: port 1 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
usb 1-1: default language 0x0409
usb 1-1: udev 2, busnum 1, minor = 1
usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
usb 1-1: Product: USB2.0 WLAN
usb 1-1: Manufacturer: ATHEROS
usb 1-1: SerialNumber: 12345
usb 1-1: usb_probe_device
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
ath9k_htc 1-1:1.0: usb_probe_interface
ath9k_htc 1-1:1.0: usb_probe_interface - got id
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
ieee80211 phy0: Atheros AR9271 Rev:1
cfg80211: Pending regulatory request, waiting for it to be processed...
Registered led device: ath9k_htc-phy0
usb 1-1: ath9k_htc: USB layer initialized
drivers/usb/core/inode.c: creating file '002'
physical device wlan0 UP!!! 

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111124/fb9bc3b7/attachment.htm 

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Alan]

I have the same problem, have you been able to solve it?

I tried kernel 3.0.4 without compat-wireless. Firmware is version 1.3.
I get these messages at boot time:

cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
Failed to initialize the device
ath9k_htc: probe of 1-1:1.0 failed with error -22
usbcore: registered new interface driver ath9k_htc

This only happens if the machine boots with the dongle plugged in.
If I plug the dongle after booting, I get this:

usb 1-1: new high speed USB device number 2 using ehci_hcd
cfg80211: Calling CRDA to update world regulatory domain
usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
ath: UNDEFINED -> AWAKE
ath: serialize_regmode is 0
ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
ath: EEPROM regdomain: 0x809c
ath: EEPROM indicates we should expect a country code
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x52
ath: Country alpha2 being used: CN
ath: Regpair used: 0x52
ieee80211 phy0: Atheros AR9271 Rev:1
Registered led device: ath9k_htc-phy0
usb 1-1: ath9k_htc: USB layer initialized
usbcore: registered new interface driver ath9k_htc

But then:

# iwconfig wlan0
wlan0     no wireless extensions.



2011/11/23 Jian Li <lijian1976@hotmail.com>:
> hi all:
>
> the linux box version is?2.6.35.12. and the compat wireless version is
> "compat-wireless-2011-11-20". Fireware version is 1.3?
>
> wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB wifi.
>
> the question is that wifi failed to initialize when i reboot the box. the
> print message as below?:
>
>
> ADDRCONF(NETDEV_UP): WAN1: link is not ready
> usb 1-1: default language 0x0409
> usb 1-1: udev 2, busnum 1, minor = 1
> usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
> usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
> usb 1-1: Product: USB2.0 WLAN
> usb 1-1: Manufacturer: ATHEROS
> usb 1-1: SerialNumber: 12345
> usb 1-1: usb_probe_device
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> drivers/usb/core/inode.c: creating file '002'
> hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
> usb usb3: suspend_rh (auto-stop)
> usb usb4: suspend_rh (auto-stop)
> usb usb5: suspend_rh (auto-stop)
> usb usb2: suspend_rh (auto-stop)
> r8169 0000:02:00.0: WAN1: link up
> ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
> Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
> Backport based on linux-next.git next-20111118
> cfg80211: Calling CRDA to update world regulatory domain
> ath9k_htc 1-1:1.0: usb_probe_interface
> ath9k_htc 1-1:1.0: usb_probe_interface - got id
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> Failed to initialize the device
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usbcore: registered new interface driver ath9k_htc
> g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
>
>
> but if i unplug and plug the wifi, it will be initilized ok! could you help
> me
>
>
> ehci_hcd 0000:00:1d.7: port 1 high speed
> ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE
> CONNECT
> usb 1-1: default language 0x0409
> usb 1-1: udev 2, busnum 1, minor = 1
> usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
> usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
> usb 1-1: Product: USB2.0 WLAN
> usb 1-1: Manufacturer: ATHEROS
> usb 1-1: SerialNumber: 12345
> usb 1-1: usb_probe_device
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> ath9k_htc 1-1:1.0: usb_probe_interface
> ath9k_htc 1-1:1.0: usb_probe_interface - got id
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
> ath: EEPROM regdomain: 0x809c
> ath: EEPROM indicates we should expect a country code
> ath: doing EEPROM country->regdmn map search
> ath: country maps to regdmn code: 0x52
> ath: Country alpha2 being used: CN
> ath: Regpair used: 0x52
> cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
> ieee80211 phy0: Atheros AR9271 Rev:1
> cfg80211: Pending regulatory request, waiting for it to be processed...
> Registered led device: ath9k_htc-phy0
> usb 1-1: ath9k_htc: USB layer initialized
> drivers/usb/core/inode.c: creating file '002'
> physical device wlan0 UP!!!

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Jian Li]

not yet  and we are going to change to TP-link WN821N.
 

 

> Date: Fri, 25 Nov 2011 22:37:28 +0900
> Subject: Re: [ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot
> From: lameventanas at gmail.com
> To: lijian1976 at hotmail.com
> CC: ath9k-devel at lists.ath9k.org
> 
> I have the same problem, have you been able to solve it?
> 
> I tried kernel 3.0.4 without compat-wireless. Firmware is version 1.3.
> I get these messages at boot time:
> 
> cfg80211: Calling CRDA to update world regulatory domain
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> Failed to initialize the device
> ath9k_htc: probe of 1-1:1.0 failed with error -22
> usbcore: registered new interface driver ath9k_htc
> 
> This only happens if the machine boots with the dongle plugged in.
> If I plug the dongle after booting, I get this:
> 
> usb 1-1: new high speed USB device number 2 using ehci_hcd
> cfg80211: Calling CRDA to update world regulatory domain
> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
> ath: UNDEFINED -> AWAKE
> ath: serialize_regmode is 0
> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
> ath: EEPROM regdomain: 0x809c
> ath: EEPROM indicates we should expect a country code
> ath: doing EEPROM country->regdmn map search
> ath: country maps to regdmn code: 0x52
> ath: Country alpha2 being used: CN
> ath: Regpair used: 0x52
> ieee80211 phy0: Atheros AR9271 Rev:1
> Registered led device: ath9k_htc-phy0
> usb 1-1: ath9k_htc: USB layer initialized
> usbcore: registered new interface driver ath9k_htc
> 
> But then:
> 
> # iwconfig wlan0
> wlan0 no wireless extensions.
> 
> 
> 
> 2011/11/23 Jian Li <lijian1976@hotmail.com>:
> > hi all:
> >
> > the linux box version is 2.6.35.12. and the compat wireless version is
> > "compat-wireless-2011-11-20". Fireware version is 1.3?
> >
> > wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB wifi.
> >
> > the question is that wifi failed to initialize when i reboot the box. the
> > print message as below :
> >
> >
> > ADDRCONF(NETDEV_UP): WAN1: link is not ready
> > usb 1-1: default language 0x0409
> > usb 1-1: udev 2, busnum 1, minor = 1
> > usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
> > usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
> > usb 1-1: Product: USB2.0 WLAN
> > usb 1-1: Manufacturer: ATHEROS
> > usb 1-1: SerialNumber: 12345
> > usb 1-1: usb_probe_device
> > usb 1-1: configuration #1 chosen from 1 choice
> > usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> > drivers/usb/core/inode.c: creating file '002'
> > hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
> > usb usb3: suspend_rh (auto-stop)
> > usb usb4: suspend_rh (auto-stop)
> > usb usb5: suspend_rh (auto-stop)
> > usb usb2: suspend_rh (auto-stop)
> > r8169 0000:02:00.0: WAN1: link up
> > ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
> > Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
> > Backport based on linux-next.git next-20111118
> > cfg80211: Calling CRDA to update world regulatory domain
> > ath9k_htc 1-1:1.0: usb_probe_interface
> > ath9k_htc 1-1:1.0: usb_probe_interface - got id
> > usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> > ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
> > Failed to initialize the device
> > ath9k_htc: probe of 1-1:1.0 failed with error -22
> > usbcore: registered new interface driver ath9k_htc
> > g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
> >
> >
> > but if i unplug and plug the wifi, it will be initilized ok! could you help
> > me
> >
> >
> > ehci_hcd 0000:00:1d.7: port 1 high speed
> > ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE
> > CONNECT
> > usb 1-1: default language 0x0409
> > usb 1-1: udev 2, busnum 1, minor = 1
> > usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
> > usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
> > usb 1-1: Product: USB2.0 WLAN
> > usb 1-1: Manufacturer: ATHEROS
> > usb 1-1: SerialNumber: 12345
> > usb 1-1: usb_probe_device
> > usb 1-1: configuration #1 chosen from 1 choice
> > usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> > ath9k_htc 1-1:1.0: usb_probe_interface
> > ath9k_htc 1-1:1.0: usb_probe_interface - got id
> > usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> > ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
> > ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
> > ath: EEPROM regdomain: 0x809c
> > ath: EEPROM indicates we should expect a country code
> > ath: doing EEPROM country->regdmn map search
> > ath: country maps to regdmn code: 0x52
> > ath: Country alpha2 being used: CN
> > ath: Regpair used: 0x52
> > cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
> > ieee80211 phy0: Atheros AR9271 Rev:1
> > cfg80211: Pending regulatory request, waiting for it to be processed...
> > Registered led device: ath9k_htc-phy0
> > usb 1-1: ath9k_htc: USB layer initialized
> > drivers/usb/core/inode.c: creating file '002'
> > physical device wlan0 UP!!!
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111128/5c5ee6dd/attachment-0001.htm 

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Adrian Chadd]

Can you please file a bugzilla bug for this? Just so the ath9k htc
developers can chase it up?

Thanks,


Adrian

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Mohammed Shafi]

2011/11/28 Jian Li <lijian1976@hotmail.com>:
> not yet  and we are going to change to TP-link WN821N.
>
I will try this out in my x86 machine

>
>
>> Date: Fri, 25 Nov 2011 22:37:28 +0900
>> Subject: Re: [ath9k-devel] ath9k 9271 print "Target is unresponsive" after
>> reboot
>> From: lameventanas at gmail.com
>> To: lijian1976 at hotmail.com
>> CC: ath9k-devel at lists.ath9k.org
>>
>> I have the same problem, have you been able to solve it?
>>
>> I tried kernel 3.0.4 without compat-wireless. Firmware is version 1.3.
>> I get these messages at boot time:
>>
>> cfg80211: Calling CRDA to update world regulatory domain
>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>> ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>> Failed to initialize the device
>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>> usbcore: registered new interface driver ath9k_htc
>>
>> This only happens if the machine boots with the dongle plugged in.
>> If I plug the dongle after booting, I get this:
>>
>> usb 1-1: new high speed USB device number 2 using ehci_hcd
>> cfg80211: Calling CRDA to update world regulatory domain
>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>> ath: UNDEFINED -> AWAKE
>> ath: serialize_regmode is 0
>> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
>> ath: EEPROM regdomain: 0x809c
>> ath: EEPROM indicates we should expect a country code
>> ath: doing EEPROM country->regdmn map search
>> ath: country maps to regdmn code: 0x52
>> ath: Country alpha2 being used: CN
>> ath: Regpair used: 0x52
>> ieee80211 phy0: Atheros AR9271 Rev:1
>> Registered led device: ath9k_htc-phy0
>> usb 1-1: ath9k_htc: USB layer initialized
>> usbcore: registered new interface driver ath9k_htc
>>
>> But then:
>>
>> # iwconfig wlan0
>> wlan0 no wireless extensions.
>>
>>
>>
>> 2011/11/23 Jian Li <lijian1976@hotmail.com>:
>> > hi all:
>> >
>> > the linux box version is 2.6.35.12. and the compat wireless version is
>> > "compat-wireless-2011-11-20". Fireware version is 1.3?
>> >
>> > wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB
>> > wifi.
>> >
>> > the question is that wifi failed to initialize when i reboot the box.
>> > the
>> > print message as below :
>> >
>> >
>> > ADDRCONF(NETDEV_UP): WAN1: link is not ready
>> > usb 1-1: default language 0x0409
>> > usb 1-1: udev 2, busnum 1, minor = 1
>> > usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
>> > usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
>> > usb 1-1: Product: USB2.0 WLAN
>> > usb 1-1: Manufacturer: ATHEROS
>> > usb 1-1: SerialNumber: 12345
>> > usb 1-1: usb_probe_device
>> > usb 1-1: configuration #1 chosen from 1 choice
>> > usb 1-1: adding 1-1:1.0 (config #1, interface 0)
>> > drivers/usb/core/inode.c: creating file '002'
>> > hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
>> > usb usb3: suspend_rh (auto-stop)
>> > usb usb4: suspend_rh (auto-stop)
>> > usb usb5: suspend_rh (auto-stop)
>> > usb usb2: suspend_rh (auto-stop)
>> > r8169 0000:02:00.0: WAN1: link up
>> > ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
>> > Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
>> > Backport based on linux-next.git next-20111118
>> > cfg80211: Calling CRDA to update world regulatory domain
>> > ath9k_htc 1-1:1.0: usb_probe_interface
>> > ath9k_htc 1-1:1.0: usb_probe_interface - got id
>> > usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>> > ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>> > Failed to initialize the device
>> > ath9k_htc: probe of 1-1:1.0 failed with error -22
>> > usbcore: registered new interface driver ath9k_htc
>> > g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
>> >
>> >
>> > but if i unplug and plug the wifi, it will be initilized ok! could you
>> > help
>> > me
>> >
>> >
>> > ehci_hcd 0000:00:1d.7: port 1 high speed
>> > ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE
>> > CONNECT
>> > usb 1-1: default language 0x0409
>> > usb 1-1: udev 2, busnum 1, minor = 1
>> > usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
>> > usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
>> > usb 1-1: Product: USB2.0 WLAN
>> > usb 1-1: Manufacturer: ATHEROS
>> > usb 1-1: SerialNumber: 12345
>> > usb 1-1: usb_probe_device
>> > usb 1-1: configuration #1 chosen from 1 choice
>> > usb 1-1: adding 1-1:1.0 (config #1, interface 0)
>> > ath9k_htc 1-1:1.0: usb_probe_interface
>> > ath9k_htc 1-1:1.0: usb_probe_interface - got id
>> > usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>> > ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>> > ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
>> > ath: EEPROM regdomain: 0x809c
>> > ath: EEPROM indicates we should expect a country code
>> > ath: doing EEPROM country->regdmn map search
>> > ath: country maps to regdmn code: 0x52
>> > ath: Country alpha2 being used: CN
>> > ath: Regpair used: 0x52
>> > cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
>> > ieee80211 phy0: Atheros AR9271 Rev:1
>> > cfg80211: Pending regulatory request, waiting for it to be processed...
>> > Registered led device: ath9k_htc-phy0
>> > usb 1-1: ath9k_htc: USB layer initialized
>> > drivers/usb/core/inode.c: creating file '002'
>> > physical device wlan0 UP!!!
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>



-- 
shafi

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Mohammed Shafi]

2011/11/28 Mohammed Shafi <shafi.wireless@gmail.com>:
> 2011/11/28 Jian Li <lijian1976@hotmail.com>:
>> not yet  and we are going to change to TP-link WN821N.
>>
> I will try this out in my x86 machine

i can recreate it.

>
>>
>>
>>> Date: Fri, 25 Nov 2011 22:37:28 +0900
>>> Subject: Re: [ath9k-devel] ath9k 9271 print "Target is unresponsive" after
>>> reboot
>>> From: lameventanas at gmail.com
>>> To: lijian1976 at hotmail.com
>>> CC: ath9k-devel at lists.ath9k.org
>>>
>>> I have the same problem, have you been able to solve it?
>>>
>>> I tried kernel 3.0.4 without compat-wireless. Firmware is version 1.3.
>>> I get these messages at boot time:
>>>
>>> cfg80211: Calling CRDA to update world regulatory domain
>>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>>> ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>>> Failed to initialize the device
>>> ath9k_htc: probe of 1-1:1.0 failed with error -22
>>> usbcore: registered new interface driver ath9k_htc
>>>
>>> This only happens if the machine boots with the dongle plugged in.
>>> If I plug the dongle after booting, I get this:
>>>
>>> usb 1-1: new high speed USB device number 2 using ehci_hcd
>>> cfg80211: Calling CRDA to update world regulatory domain
>>> usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>>> ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>>> ath: UNDEFINED -> AWAKE
>>> ath: serialize_regmode is 0
>>> ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
>>> ath: EEPROM regdomain: 0x809c
>>> ath: EEPROM indicates we should expect a country code
>>> ath: doing EEPROM country->regdmn map search
>>> ath: country maps to regdmn code: 0x52
>>> ath: Country alpha2 being used: CN
>>> ath: Regpair used: 0x52
>>> ieee80211 phy0: Atheros AR9271 Rev:1
>>> Registered led device: ath9k_htc-phy0
>>> usb 1-1: ath9k_htc: USB layer initialized
>>> usbcore: registered new interface driver ath9k_htc
>>>
>>> But then:
>>>
>>> # iwconfig wlan0
>>> wlan0 no wireless extensions.
>>>
>>>
>>>
>>> 2011/11/23 Jian Li <lijian1976@hotmail.com>:
>>> > hi all:
>>> >
>>> > the linux box version is 2.6.35.12. and the compat wireless version is
>>> > "compat-wireless-2011-11-20". Fireware version is 1.3?
>>> >
>>> > wifi brand is TPLINK-WN722N, and chip is atheros 9271 which is an USB
>>> > wifi.
>>> >
>>> > the question is that wifi failed to initialize when i reboot the box.
>>> > the
>>> > print message as below :
>>> >
>>> >
>>> > ADDRCONF(NETDEV_UP): WAN1: link is not ready
>>> > usb 1-1: default language 0x0409
>>> > usb 1-1: udev 2, busnum 1, minor = 1
>>> > usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
>>> > usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
>>> > usb 1-1: Product: USB2.0 WLAN
>>> > usb 1-1: Manufacturer: ATHEROS
>>> > usb 1-1: SerialNumber: 12345
>>> > usb 1-1: usb_probe_device
>>> > usb 1-1: configuration #1 chosen from 1 choice
>>> > usb 1-1: adding 1-1:1.0 (config #1, interface 0)
>>> > drivers/usb/core/inode.c: creating file '002'
>>> > hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0000
>>> > usb usb3: suspend_rh (auto-stop)
>>> > usb usb4: suspend_rh (auto-stop)
>>> > usb usb5: suspend_rh (auto-stop)
>>> > usb usb2: suspend_rh (auto-stop)
>>> > r8169 0000:02:00.0: WAN1: link up
>>> > ADDRCONF(NETDEV_CHANGE): WAN1: link becomes ready
>>> > Compat-wireless backport release: compat-wireless-2011-11-08-11-gd32558f
>>> > Backport based on linux-next.git next-20111118
>>> > cfg80211: Calling CRDA to update world regulatory domain
>>> > ath9k_htc 1-1:1.0: usb_probe_interface
>>> > ath9k_htc 1-1:1.0: usb_probe_interface - got id
>>> > usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>>> > ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
>>> > Failed to initialize the device
>>> > ath9k_htc: probe of 1-1:1.0 failed with error -22
>>> > usbcore: registered new interface driver ath9k_htc
>>> > g_lan_port_num(0xc03d1f78): (0, 0x0)--->(2, 0x2)
>>> >
>>> >
>>> > but if i unplug and plug the wifi, it will be initilized ok! could you
>>> > help
>>> > me
>>> >
>>> >
>>> > ehci_hcd 0000:00:1d.7: port 1 high speed
>>> > ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE
>>> > CONNECT
>>> > usb 1-1: default language 0x0409
>>> > usb 1-1: udev 2, busnum 1, minor = 1
>>> > usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
>>> > usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
>>> > usb 1-1: Product: USB2.0 WLAN
>>> > usb 1-1: Manufacturer: ATHEROS
>>> > usb 1-1: SerialNumber: 12345
>>> > usb 1-1: usb_probe_device
>>> > usb 1-1: configuration #1 chosen from 1 choice
>>> > usb 1-1: adding 1-1:1.0 (config #1, interface 0)
>>> > ath9k_htc 1-1:1.0: usb_probe_interface
>>> > ath9k_htc 1-1:1.0: usb_probe_interface - got id
>>> > usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
>>> > ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
>>> > ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
>>> > ath: EEPROM regdomain: 0x809c
>>> > ath: EEPROM indicates we should expect a country code
>>> > ath: doing EEPROM country->regdmn map search
>>> > ath: country maps to regdmn code: 0x52
>>> > ath: Country alpha2 being used: CN
>>> > ath: Regpair used: 0x52
>>> > cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
>>> > ieee80211 phy0: Atheros AR9271 Rev:1
>>> > cfg80211: Pending regulatory request, waiting for it to be processed...
>>> > Registered led device: ath9k_htc-phy0
>>> > usb 1-1: ath9k_htc: USB layer initialized
>>> > drivers/usb/core/inode.c: creating file '002'
>>> > physical device wlan0 UP!!!
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>>
>
>
>
> --
> shafi
>



-- 
shafi

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Alan]

2011/11/28 Mohammed Shafi <shafi.wireless@gmail.com>:
> 2011/11/28 Mohammed Shafi <shafi.wireless@gmail.com>:
>> 2011/11/28 Jian Li <lijian1976@hotmail.com>:
>>> not yet ?and we are going to change to TP-link WN821N.
>>>
>> I will try this out in my x86 machine
>
> i can recreate it.

That's good to know.
Is there any way to avoid recreating it every time we try to use our 9271?

[ath9k-devel] ath9k debug, low bitrates

[gtolon at inti.gob.ar]

Hi. I'm using some D-Link routers with Openwrt Backfire, each one with 
an Acces Point and an ad hoc interface (using virtual interfaces). Using 
the ad hoc interface between routers sometimes i get good bitrates with 
iperf, 70 Mbps for example, with less than 1% of error, but occasionally 
the error increases to larger values, up to 40%. I don't have reasons to 
think that it's a channel problem, because the routers are very close 
and sometimes the transference is good in one direction and not in the 
other, and i know there's not high interferences. I think that maybe 
it's a problem related to tx dma faillures 
(https://dev.openwrt.org/ticket/9693) but i'm not sure, because 
sometimes the low rates appear without that error.

I know that maybe this is a problem related with openwrt and not with 
the driver, but to be sure i'd like to know more about the debug files 
of ath9k. I was searching for usefull data in the debug files like:

/sys/kernel/debug/ieee80211/phy0/ath9k/wiphy
/sys/kernel/debug/ieee80211/phy0/ath9k/xmit
/sys/kernel/debug/ieee80211/phy0/ath9k/interrupt
/sys/kernel/debug/ieee80211/phy0/ath9k/dma

etc, but i found it very difficult to undersand the parameters showed. 
I've been looking in the source code also, in debug.h, and i saw the 
meaning of some abbreviations, but i still don't know how to interpret 
them. I would appreciate some help on this to use the debug files and 
know if the problem is related with the driver or not. Thanks!


Gabriel

[ath9k-devel] ath9k 9271 print "Target is unresponsive" after reboot

[Mohammed Shafi]

On Wed, Nov 30, 2011 at 9:59 PM, Alan <lameventanas@gmail.com> wrote:
> 2011/11/28 Mohammed Shafi <shafi.wireless@gmail.com>:
>> 2011/11/28 Mohammed Shafi <shafi.wireless@gmail.com>:
>>> 2011/11/28 Jian Li <lijian1976@hotmail.com>:
>>>> not yet ?and we are going to change to TP-link WN821N.
>>>>
>>> I will try this out in my x86 machine
>>
>> i can recreate it.
>
> That's good to know.
> Is there any way to avoid recreating it every time we try to use our 9271?

i will try to find it out whether its a regression by the end of this weekend.
if its a firmware issue it will take some more time to debug. thanks!

-- 
shafi