Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

random reset and complete lock #173

Open
varoudis opened this issue Feb 3, 2022 · 8 comments
Open

random reset and complete lock #173

varoudis opened this issue Feb 3, 2022 · 8 comments

Comments

@varoudis
Copy link

varoudis commented Feb 3, 2022

Hi,

At random times and tested with two different Linux distro running 5.10 and 5.15 the usb device goes dead until is physically removed from the system.
Everything seems ok after USB in re-inserted until a random interval later same thing happens again.

Any ideas?
USB card is ALFA AWUS036NHA

		[    5.171311] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
		[    5.173528] usbcore: registered new interface driver ath9k_htc
		[    5.175441] kmodloader: done loading kernel modules from /etc/modules.d/*
		[    5.469340] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
		[    5.751851] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
		[    6.555202] 8021q: adding VLAN 0 to HW filter on device eth0
		[    6.557432] br-lan: port 1(eth0) entered blocking state
		[    6.559144] br-lan: port 1(eth0) entered disabled state
		[    6.561547] device eth0 entered promiscuous mode
		[    6.564435] br-lan: port 1(eth0) entered blocking state
		[    6.566314] br-lan: port 1(eth0) entered forwarding state
		[    6.934851] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
		[    6.936906] ath9k_htc 1-1:1.0: FW RMW support: On
		[    6.938809] ath: EEPROM regdomain: 0x833a
		[    6.940534] ath: EEPROM indicates we should expect a country code
		[    6.943417] ath: doing EEPROM country->regdmn map search
		[    6.945221] ath: country maps to regdmn code: 0x37
		[    6.946591] ath: Country alpha2 being used: GB
		[    6.947894] ath: Regpair used: 0x37
		[    6.980456] ieee80211 phy0: Atheros AR9271 Rev:1
		[    8.452273] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
		[    8.496708] device br-lan entered promiscuous mode
		[  127.581219] wlan0: authenticate with 00:2a:10:cf
		[  129.527475] wlan0: send auth to 00:2a:10:cf (try 1/3)
		[  129.533347] wlan0: authenticated
		[  129.539989] wlan0: associate with 00:2a:10:cf (try 1/3)
		[  129.545750] wlan0: RX AssocResp from 00:2a:10:cf (capab=0x431 status=0 aid=12)
		[  129.615347] wlan0: associated
		[  129.723574] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
		[ 2571.637692] ath: phy0: Unable to remove station entry for: 00:2a:10:cf
		[ 3038.032661] usb 1-1: USB disconnect, device number 2
		[ 3038.125724] ath: phy0: Chip reset failed
		[ 3038.126858] ath: phy0: Unable to reset channel (2447 Mhz) reset status -22
		[ 3038.128678] ath: phy0: Unable to set channel
		[ 3038.230731] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0783b01
		[ 3038.434341] ath: phy0: RX failed to go idle in 10 ms RXSM=0x0
		[ 3038.446391] ath: phy0: Failed to wakeup in 500us
		[ 3038.548547] ath: phy0: RX failed to go idle in 10 ms RXSM=0x4016cf01
		[ 3038.752421] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0683b01
		[ 3038.764229] ath: phy0: Failed to wakeup in 500us
		[ 3038.995863] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0683b01
@olerem
Copy link
Contributor

olerem commented Feb 3, 2022

Hi,

please take a look here:
https://github.com/qca/open-ath9k-htc-firmware/wiki/usb-related-issues

@varoudis
Copy link
Author

varoudis commented Feb 3, 2022

@olerem Thanks for the quick reply. I did check and for about an hour Im running a test with:

options "nohwcrypt=1 ps_enable=0 blink=0"

I think blink=0 is the same as the "sudo bash -c "echo none > /sys/class/leds/ath9k_htc-phy*/trigger"" ?
LED isnt blinking anymore

@olerem
Copy link
Contributor

olerem commented Feb 3, 2022

yes. Will be interesting to know results.

@varoudis
Copy link
Author

varoudis commented Feb 3, 2022 •
edited
Loading

The above test wasnt a success...

[    5.411515] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[    5.414339] usbcore: registered new interface driver ath9k_htc
[    5.418440] kmodloader: done loading kernel modules from /etc/modules.d/*
[    5.715760] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[    5.997918] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[    6.751271] 8021q: adding VLAN 0 to HW filter on device eth0
[    6.756850] br-lan: port 1(eth0) entered blocking state
[    6.759396] br-lan: port 1(eth0) entered disabled state
[    6.763735] device eth0 entered promiscuous mode
[    6.770477] br-lan: port 1(eth0) entered blocking state
[    6.775707] br-lan: port 1(eth0) entered forwarding state
[    7.273586] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
[    7.278242] ath9k_htc 1-1:1.0: FW RMW support: On
[    7.282485] ath: EEPROM regdomain: 0x833a
[    7.285871] ath: EEPROM indicates we should expect a country code
[    7.290866] ath: doing EEPROM country->regdmn map search
[    7.295167] ath: country maps to regdmn code: 0x37
[    7.299110] ath: Country alpha2 being used: GB
[    7.302916] ath: Regpair used: 0x37
[    7.343320] ieee80211 phy0: Atheros AR9271 Rev:1
[    7.347709] device br-lan entered promiscuous mode
[    8.838294] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[  128.107954] wlan0: authenticate with 00:2a:10
[  130.168660] wlan0: send auth to 00:2a:10: (try 1/3)
[  130.177460] wlan0: authenticated
[  130.189552] wlan0: associate with 00:2a:10: (try 1/3)
[  130.210526] wlan0: RX AssocResp from 00:2a:10:cf (capab=0x431 status=0 aid=12)
[  130.292239] wlan0: associated
[  130.373981] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 6383.518119] ath: phy0: Unable to remove station entry for: 00:2a:10:c
[ 9807.054930] ath: phy0: Chip reset failed
[ 9807.057151] ath: phy0: Unable to reset channel (2447 Mhz) reset status -22
[ 9807.059751] ath: phy0: Unable to set channel
[ 9807.162394] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0b8b103
[ 9807.176010] ath: phy0: Failed to wakeup in 500us
[ 9807.279149] ath: phy0: RX failed to go idle in 10 ms RXSM=0x4056da01
[ 9807.484249] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0a8b103
[ 9807.496733] ath: phy0: Failed to wakeup in 500us
[ 9807.804791] ath: phy0: RX failed to go idle in 10 ms RXSM=0xc0a8b103

Do you think sending "none" in your command does something different?

This is what I had:

cat /sys/class/leds/ath9k_htc-phy0/trigger 
		none timer heartbeat default-on netdev phy0rx phy0tx phy0assoc [phy0radio] phy0tpt

@varoudis
Copy link
Author

varoudis commented Feb 7, 2022

Same error with LED totally off.

@olerem
Copy link
Contributor

olerem commented Feb 8, 2022

Sorry, Currently I have no idea. To get more information, you will need to get access to the UART pins (TXD1, RXD1) on the board of this adapter (baudrate 19200) and log this error on the firmware side.

@varoudis
Copy link
Author

varoudis commented Feb 8, 2022 •
edited
Loading

ok thanks! Ill try to find some time to do it. (and find my ftdi adapter first :) )

@ZerBea ZerBea mentioned this issue Apr 1, 2022
Closed
@ZerBea
Copy link

ZerBea commented Apr 1, 2022

I got some issue reports possible regarding this issue, too, and it looks like they don't appear on kernel 5.17.1 any longer.
But that need some more investigations. The last test over a period of nearly 9h is looking good, so far:
ZerBea/hcxdumptool#209 (comment)

@turbodat turbodat mentioned this issue Feb 4, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@varoudis @olerem @ZerBea