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.

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

FS#3765 - RT5592 initializes but does not function when enabled #8780

Open
openwrt-bot opened this issue Apr 29, 2021 · 26 comments
Open

FS#3765 - RT5592 initializes but does not function when enabled #8780

openwrt-bot opened this issue Apr 29, 2021 · 26 comments
Labels
flyspray kernel pull request/issue with Linux kernel related changes release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release

Comments

@openwrt-bot
Copy link

openwrt-bot commented Apr 29, 2021

mcpratt:

this issue is also present on master branch

board is EPG600 (not added yet)
this probably also affects ESR600 which is the same hardware
and other boards with RT5592

5 GHz wireless initializes and SSID can be seen on scan
however, clients cannot connect and traffic fails

init:

...
...
[   12.654377] rt2800pci 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4
[   12.668538] rt2800pci 0000:01:00.0: loaded eeprom from mtd device "factory"
[   12.675676] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[   12.683626] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 000f detected
[   12.711360] urngd: jent-rng init failed, err: 2
[   12.737471] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "rf"
[   12.744489] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 6352, rev 0500 detected
[   12.752435] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 7620 detected
...
...

iw list (phy0):

Wiphy phy0
        wiphy index: 0
        max # scan SSIDs: 4
        max scan IEs length: 2261 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short long limit: 2
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 2:
                Capabilities: 0x2fe
                        HT20/HT40
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 2-streams
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 2 usec (0x04)
                HT TX/RX MCS rate indexes supported: 0-15, 32
                Frequencies:
                        * 5180 MHz [36] (20.0 dBm)
                        * 5190 MHz [38] (20.0 dBm)
                        * 5200 MHz [40] (20.0 dBm)
                        * 5210 MHz [42] (20.0 dBm)
                        * 5220 MHz [44] (20.0 dBm)
                        * 5230 MHz [46] (20.0 dBm)
                        * 5240 MHz [48] (20.0 dBm)
                        * 5250 MHz [50] (20.0 dBm) (no IR, radar detection)
                        * 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
                        * 5270 MHz [54] (20.0 dBm) (no IR, radar detection)
                        * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
                        * 5290 MHz [58] (20.0 dBm) (no IR, radar detection)
                        * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
                        * 5310 MHz [62] (20.0 dBm) (no IR, radar detection)
                        * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
                        * 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
                        * 5510 MHz [102] (20.0 dBm) (no IR, radar detection)
                        * 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
                        * 5530 MHz [106] (20.0 dBm) (no IR, radar detection)
                        * 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
                        * 5550 MHz [110] (20.0 dBm) (no IR, radar detection)
                        * 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
                        * 5570 MHz [114] (20.0 dBm) (no IR, radar detection)
                        * 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
                        * 5590 MHz [118] (20.0 dBm) (no IR, radar detection)
                        * 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
                        * 5610 MHz [122] (20.0 dBm) (no IR, radar detection)
                        * 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
                        * 5630 MHz [126] (20.0 dBm) (no IR, radar detection)
                        * 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
                        * 5650 MHz [130] (20.0 dBm) (no IR, radar detection)
                        * 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
                        * 5670 MHz [134] (20.0 dBm) (no IR, radar detection)
                        * 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
                        * 5690 MHz [138] (20.0 dBm) (no IR, radar detection)
                        * 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
                        * 5745 MHz [149] (20.0 dBm) (no IR)
                        * 5755 MHz [151] (20.0 dBm) (no IR)
                        * 5765 MHz [153] (20.0 dBm) (no IR)
                        * 5775 MHz [155] (20.0 dBm) (no IR)
                        * 5785 MHz [157] (20.0 dBm) (no IR)
                        * 5795 MHz [159] (20.0 dBm) (no IR)
                        * 5805 MHz [161] (20.0 dBm) (no IR)
                        * 5825 MHz [165] (20.0 dBm) (no IR)
                        * 4920 MHz [184] (disabled)
                        * 4940 MHz [188] (disabled)
                        * 4960 MHz [192] (disabled)
                        * 4980 MHz [196] (disabled)
        valid interface combinations:
                 * #{ managed, AP, mesh point } <= 8,
                   total <= 8, #channels <= 1
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Supported extended features:
                * [ RRM ]: RRM
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
                * [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
                * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
                * [ DEL_IBSS_STA ]: deletion of IBSS station support
                * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
                * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support

errors:

[  248.431432] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[  248.452925] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.40
[  248.515819] br-lan: port 2(wlan0) entered blocking state
[  248.521308] br-lan: port 2(wlan0) entered disabled state
[  248.526882] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0024, type=4
[  248.540458] device wlan0 entered promiscuous mode
[  248.545362] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  248.563127] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0024, type=4
[  248.580316] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  248.587159] br-lan: port 2(wlan0) entered blocking state
[  248.592642] br-lan: port 2(wlan0) entered forwarding state
[  248.603260] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0055, type=4
[  248.623801] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0024, type=4
[  248.644220] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  248.664762] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0024, type=4
[  248.705661] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0055, type=4
[  248.726199] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0024, type=4
[  248.746620] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  249.076237] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4003 max 3840
[  249.893479] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  250.648599] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  250.661836] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  250.681991] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  251.065181] rt2x00lib_rxdone_read_signal: 94 callbacks suppressed
[  251.065206] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0016, type=4
[  251.084627] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[  251.097831] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0001, signal=0x0120, type=4
[  251.131983] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  251.151566] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  251.199122] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  251.349860] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0077, type=4
[  251.522683] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 3904 max 3840
[  251.549260] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  251.561657] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  251.581250] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  251.783651] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  251.795947] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0001, signal=0x0120, type=4
[  251.833765] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  251.846411] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[  251.862441] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  251.960289] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0022, type=4
[  251.973491] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[  252.013308] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  252.032827] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  252.080332] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  252.393129] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 3904 max 3840
[  252.977643] rt2x00lib_rxdone_read_signal: 5 callbacks suppressed
[  252.977668] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0077, type=4
[  253.367744] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0040, type=4
[  253.383966] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0001, type=4
[  253.399972] rt2x00lib_rxdone: 17 callbacks suppressed
[  253.399994] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  253.423120] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  253.435617] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[  253.451641] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  253.478082] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  253.490376] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0001, signal=0x0120, type=4
[  253.527646] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  253.540122] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0027, type=4
[  253.556142] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  253.582589] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  253.602113] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  253.651031] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  253.688334] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4074 max 3840
[  253.700828] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[  253.716857] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  253.785936] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0077, type=4
[  253.851589] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0001, signal=0x0120, type=4
[  254.864343] rt2x00lib_rxdone_read_signal: 27 callbacks suppressed
[  254.864369] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0072, type=4
[  254.913025] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0002, signal=0x006b, type=4
[  254.929122] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0010, type=4
[  255.079618] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0024, type=4
[  255.102729] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[  255.132881] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0010, type=4
[  255.220453] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0002, signal=0x0078, type=4
[  255.236459] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0001, signal=0x0120, type=4
[  255.252539] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0002, signal=0x0078, type=4
[  255.268678] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0077, type=4
[  255.362987] rt2x00lib_rxdone: 75 callbacks suppressed
[  255.363009] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  255.386251] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  255.412947] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  255.432490] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  255.508218] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4074 max 3840
[  255.520688] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  255.540132] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 3890 max 3840
[  255.580842] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  255.588533] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 4095 max 3840
[  255.605518] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[  256.759235] rt2x00lib_rxdone_read_signal: 87 callbacks suppressed
...
...
...

@openwrt-bot
Copy link
Author

mcpratt:

hexdump of eeprom:

00000000 92 55 07 01 88 dc 96 aa bb cc 92 55 14 18 01 80 |.U.....#...U....| 00000010 00 00 92 55 14 18 00 00 01 00 6a ff 13 02 ff ff |...U......j.....| 00000020 ff ff c1 ff 01 92 ff ff ff ff ff ff ff ff ff ff |................| 00000030 8e 75 01 43 22 ff 27 00 ff ff 17 01 ff ff d9 aa |.u.C".'.........| 00000040 cc 88 ff ff 08 07 00 00 00 07 00 00 00 07 ff ff |................| 00000050 ff 00 05 05 05 05 05 05 05 05 05 05 05 05 05 05 |................| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 42 73 |..............Bs| 00000070 f7 00 86 0f 00 00 72 fc 0c 0c 0c 0c 0c 0c 0c 0c |......r.........| 00000080 0c 0c 0d 0d 0e 0e 0e 0e 0e 0e 0e 0e 0e 0e 0e 0e |................| 00000090 0e 0e 0f 0f 0d 0d 0d 0e 0e 0f 0f ff ff ff ff ff |................| 000000a0 ff ff ff ff ff ff 0c 0c 0d 0d 0e 0f 0f 0f 0f 0f |................| 000000b0 10 10 10 10 10 0f 0f 0e 0e 0d 0d 0d 0e 0e 0f 0f |................| 000000c0 10 0e 0f 0f 0f 0f 0f 0f 10 ff ff ff ff ff ff ff |................| 000000d0 ff ff ff ff 43 43 f3 00 21 fa 00 00 72 e1 66 66 |....CC..!...r.ff| 000000e0 aa aa 88 66 aa aa 88 44 aa aa 88 44 aa aa 88 44 |...f...D...D...D| 000000f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 00000100 ff ff ff ff ff ff ff ff ff ff ff ff 00 00 ff ff |................| 00000110 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| 00000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00010000

@openwrt-bot
Copy link
Author

nbriggs:

I can confirm that this issue is present on the ESR600.

@aparcar aparcar added release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release kernel pull request/issue with Linux kernel related changes labels Feb 22, 2022
@sobukus
Copy link

sobukus commented Feb 23, 2022

I confirm the issue on a mikrotik MIPS device with a CSL 27395 USB device with an RT5592 chip connected via USB.

[25188.965262] usb 1-1: reset high-speed USB device number 4 using xhci-mtk
[25189.130442] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[25189.152403] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 000f detected
[25189.159595] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
[25196.196868] usb 1-1: USB disconnect, device number 4
[25196.640926] usb 1-1: new high-speed USB device number 5 using xhci-mtk
[25196.945265] usb 1-1: reset high-speed USB device number 5 using xhci-mtk
[25197.080987] xhci-mtk 1e1c0000.xhci: ERROR: unexpected setup address command completion code 0x11.
[25197.296940] xhci-mtk 1e1c0000.xhci: ERROR: unexpected setup address command completion code 0x11.
[25197.512930] usb 1-1: device not accepting address 5, error -22
[25198.129142] ieee80211 phy3: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1000 with error -19
[25198.140108] ieee80211 phy3: rt2800_probe_rt: Error - Invalid RT chipset 0x0000, rev 0000 detected
[25198.148986] ieee80211 phy3: rt2x00lib_probe_dev: Error - Failed to allocate device
[25198.157341] usb 1-1: USB disconnect, device number 5
[25198.288944] usb 1-1: new full-speed USB device number 6 using xhci-mtk
[25198.421009] usb 1-1: device descriptor read/64, error -71
[25199.896940] usb 1-1: new high-speed USB device number 7 using xhci-mtk
[25200.197364] usb 1-1: reset high-speed USB device number 7 using xhci-mtk
[25200.362447] ieee80211 phy4: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[25200.384463] ieee80211 phy4: rt2x00_set_rf: Info - RF chipset 000f detected
[25200.391665] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
[25210.664985] usb 1-1: USB disconnect, device number 7
[25211.092943] usb 1-1: new full-speed USB device number 8 using xhci-mtk
[25211.224954] usb 1-1: device descriptor read/64, error -71
[25212.700953] usb 1-1: new high-speed USB device number 9 using xhci-mtk
[25213.001291] usb 1-1: reset high-speed USB device number 9 using xhci-mtk
[25213.166422] ieee80211 phy5: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[25213.188404] ieee80211 phy5: rt2x00_set_rf: Info - RF chipset 000f detected
[25213.195601] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
[25216.504865] usb 1-1: USB disconnect, device number 9
[25216.912952] usb 1-1: new high-speed USB device number 10 using xhci-mtk
[25217.213301] usb 1-1: reset high-speed USB device number 10 using xhci-mtk
[25217.378427] ieee80211 phy6: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[25217.400405] ieee80211 phy6: rt2x00_set_rf: Info - RF chipset 000f detected
[25217.407603] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht'
[25642.641949] ieee80211 phy6: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[25642.651079] ieee80211 phy6: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[25645.023145] IPv6: ADDRCONF(NETDEV_CHANGE): wlan6: link becomes ready
[25786.697516] IPv6: ADDRCONF(NETDEV_CHANGE): wlan6: link becomes ready

It looks fine initially. I also manage to get a bit of connection (a client connect showing up in LuCI), but things break after that.

Dmesg suggests that the USB connection or the device itself die … maybe there's not enough power. Maybe totally unrelated, but maybe not. An Atheros USB device works nicely (but only 1x1 setup with 72 MBit/s, not 144).

@sobukus
Copy link

sobukus commented Feb 24, 2022

Red herring. I tested with a USB switch with external power supply, ruling out flaky contacts/not enough power. Also without device resets, there is no real communication going on. The activity LED on the device doesn't light up once, apparently, while it does flash all the time when used on a client laptop.

So is there something that just broke AP operation of RT5592? Are other rt2800-style devices working fine?

@kbios
Copy link

kbios commented Mar 17, 2022

This bug also affects the Asus RP-N53 Repeater/Access Point:

Thu Mar 17 16:42:00 2022 kern.warn kernel: [  568.462070] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0002, signal=0x005b, type=4
Thu Mar 17 16:42:00 2022 kern.err kernel: [  568.487819] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:00 2022 kern.err kernel: [  568.502778] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:00 2022 kern.err kernel: [  568.517720] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:00 2022 kern.err kernel: [  568.532660] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:01 2022 kern.warn kernel: [  568.775742] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0002, type=4
Thu Mar 17 16:42:01 2022 kern.warn kernel: [  568.801449] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0002, type=4
Thu Mar 17 16:42:02 2022 kern.err kernel: [  569.388861] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:02 2022 kern.err kernel: [  569.461007] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:04 2022 kern.warn kernel: [  570.602981] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0002, signal=0x0074, type=4
Thu Mar 17 16:42:04 2022 kern.err kernel: [  570.628690] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
Thu Mar 17 16:42:07 2022 kern.err kernel: [  572.428319] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840

@Lorilandly
Copy link
Contributor

This bug also affects Buffalo WSR-600DHP. It makes the 5Ghz wifi completely unusable, i.e., the 5Ghz ssid is visible, but does not connect.

[32582.109222] ieee80211 phy1: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[32582.134956] ieee80211 phy1: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[32582.162806] ieee80211 phy1: rt2x00lib_rxdone_read_signal: Warning - Frame received with unrecognized signal, mode=0x0000, signal=0x0023, type=4
[32582.188919] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[32582.214341] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 3863 max 3840
[32582.229851] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[32582.244830] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[32582.260004] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[32582.274983] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840

@mpratt14
Copy link
Contributor

@sobukus to be clear, you do not see any kernel messages like Wrong frame size or Frame received with unrecognized signal correct?

@sobukus
Copy link

sobukus commented Feb 17, 2023

@sobukus to be clear, you do not see any kernel messages like Wrong frame size or Frame received with unrecognized signal correct?

Yes. I just tried again. All I get (if the USB connection is not loose) is

[12704489.237136] usb 1-1: USB disconnect, device number 9
[12704491.401643] usb 1-1: new high-speed USB device number 10 using xhci-mtk
[12704491.705977] usb 1-1: reset high-speed USB device number 10 using xhci-mtk
[12704491.871140] ieee80211 phy4: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[12704491.893387] ieee80211 phy4: rt2x00_set_rf: Info - RF chipset 000f detected
[12704491.900925] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
[12704491.923340] ieee80211 phy4: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[12704491.932728] ieee80211 phy4: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[12704545.859784] do_page_fault(): sending SIGSEGV to hostapd for invalid write access to 00000004
[12704545.868559] epc = 5565cc75 in hostapd[55653000+9d000]
[12704545.873995] ra  = 5569d98f in hostapd[55653000+9d000]
[12704577.271860] IPv6: ADDRCONF(NETDEV_CHANGE): wlan4: link becomes ready
[12704577.764579] IPv6: ADDRCONF(NETDEV_CHANGE): wlan4-1: link becomes ready
[12704598.200271] IPv6: ADDRCONF(NETDEV_CHANGE): wlan4: link becomes ready
[12704598.814792] IPv6: ADDRCONF(NETDEV_CHANGE): wlan4-1: link becomes ready

This was swtiching from one USB wifi device to another (stopping wifi and then
starting in in luci) … hostapd didn't like this in one instance, but eventually I got
an instance running. But this only amounts to this on the client side:

[81842.003021] wlp2s0: associate with 24:05:0f:xx:xx:xx (try 1/3)
[81842.008269] wlp2s0: RX AssocResp from 24:05:0f:xx:xx:xx (capab=0x431 status=0 aid=1)
[81842.010909] wlp2s0: associated
[81852.012139] wlp2s0: deauthenticating from 24:05:0f:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[81862.239971] wlp2s0: authenticate with 24:05:0f:xx:xx:xx
[81862.242117] wlp2s0: send auth to 24:05:0f:xx:xx:xx (try 1/3)
[81862.248700] wlp2s0: authenticated
[81862.252063] wlp2s0: associate with 24:05:0f:xx:xx:xx (try 1/3)
[81862.257420] wlp2s0: RX AssocResp from 24:05:0f:xx:xx:xx (capab=0x431 status=0 aid=1)
[81862.260321] wlp2s0: associated
[81867.167303] wlp2s0: deauthenticating from 24:05:0f:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[81867.203237] wlp2s0: authenticate with 24:05:0f:xx:xx:xx
[81867.205366] wlp2s0: send auth to 24:05:0f:xx:xx:xx (try 1/3)
[81867.207671] wlp2s0: authenticated
[81867.208305] wlp2s0: associate with 24:05:0f:xx:xx:xx (try 1/3)
[81867.212997] wlp2s0: RX AssocResp from 24:05:0f:xx:xx:xx (capab=0x431 status=0 aid=1)
[81867.215695] wlp2s0: associated
[81877.217179] wlp2s0: deauthenticating from 24:05:0f:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)

No proper connection establishing …

@mpratt14
Copy link
Contributor

what is the model of the usb device? or is there a similar one I can get?

the mikrotik is an mt7620 or ath79?

@sobukus
Copy link

sobukus commented Feb 17, 2023

The Mikrotik is an RB750Gr3, with the wifi connected to the USB port.

[    0.000000] Linux version 5.4.154 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16325-88151b8303)) #0 SMP Sun Oct 24 09:01:35 2021
[    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
[    0.000000] MIPS: machine is MikroTik RouterBOARD 750Gr3

The USB wifi is a CSL 27395. It's a 300 MBit/s dual-antenna wifi not needing USB 3 that I hoped would work well, based on the Ralink chip. Wondering now … the product page of $store says RT5572, dmesg says RT5592. The label on the chip says RT5572. The board carries the name MT-WN813N-D-V2.0. That may help to identify an identical product. Having said that … there's not much more besides the two antenna ports and the chip on it, so I'd expect any RT5572 device behaving the same.

@mpratt14
Copy link
Contributor

can you install usbutils and run lsusb and show it

@sobukus
Copy link

sobukus commented Feb 18, 2023

Sure.

# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux 5.4.154 xhci-hcd xHCI Host Controller
Bus 001 Device 014: ID 148f:5572 Ralink 802.11 n WLAN
Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.154 xhci-hcd xHCI Host Controller
# lsusb -v
[…]
Bus 001 Device 014: ID 148f:5572 Ralink 802.11 n WLAN
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x148f 
  idProduct          0x5572 
  bcdDevice            1.01
  iManufacturer           1 Ralink
  iProduct                2 802.11 n WLAN
  iSerial                 3 1.0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0035
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              450mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           5
      bInterfaceClass       255 
      bInterfaceSubClass    255 
      bInterfaceProtocol    255 
      iInterface              5 1.0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)

[…]

For good measure, the working USB wifi:

Bus 001 Device 011: ID 0cf3:9271 ATHEROS USB2.0 WLAN
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 
  bDeviceSubClass       255 
  bDeviceProtocol       255 
  bMaxPacketSize0        64
  idVendor           0x0cf3 
  idProduct          0x9271 
  bcdDevice            1.08
  iManufacturer          16 ATHEROS
  iProduct               32 USB2.0 WLAN
  iSerial                48 12345
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x003c
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           6
      bInterfaceClass       255 
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0

Edit: With 'working', I mean that it normally works, but has occasional interruptions in the connection. During video conferences, this is rather annoying, but it's mostly OK, for a year now. I had hoped for better performance using the dual-antenna device with another chip (it's just a few meters, so it is not really about the antennas, I guess).

@mpratt14
Copy link
Contributor

it might be missing kernel config symbol

config RT2800USB_RT55XX
	bool "rt2800usb - Include support for rt55xx devices (EXPERIMENTAL)"
	help
	  This adds support for rt55xx wireless chipset family to the
	  rt2800usb driver.
	  Supported chips: RT5572

@mpratt14
Copy link
Contributor

@mpratt14
Copy link
Contributor

@sobukus I got my hands on a RT5572 usb and it's misidentified as a RT5592 in kernel log like you said,
but I have it working, did a speed test and watched videos and everything

However, I plugged it into an ath79 device (specifically QCA9558), not an mt762x device. going to try an mt7620 device next.

have you made sure to install the right driver and reboot?

https://openwrt.org/packages/pkgdata/kmod-rt2800-usb

If you still have trouble, I would suspect the USB driver as the problem

relevant log output

[   20.195928] usb 1-1: reset high-speed USB device number 2 using ehci-platform
[   20.402054] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[   20.472977] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 000f detected
[   20.487600] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   20.489535] usbcore: registered new interface driver rt2800usb
...
[   44.885567] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   44.927126] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
...
[   45.491024] br-lan: port 2(phy1-ap0) entered blocking state
[   45.496755] br-lan: port 2(phy1-ap0) entered disabled state
[   45.502686] device phy1-ap0 entered promiscuous mode
[   45.507923] br-lan: port 2(phy1-ap0) entered blocking state
[   45.513592] br-lan: port 2(phy1-ap0) entered forwarding state
[   45.524310] br-lan: port 2(phy1-ap0) entered disabled state
[   45.639918] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
[   45.646894] br-lan: port 2(phy1-ap0) entered blocking state
[   45.652569] br-lan: port 2(phy1-ap0) entered forwarding state

@sobukus
Copy link

sobukus commented Mar 4, 2023

I am pretty sure we got the same driver being active, loading the same firmware file, etc. If you could try a mt7620 and verify yourself (or find a setup that actually works;-), that would be great!

A somewhat flaky USB would explain that the other device also does not work perfectly stable. And sure, routers with onboard wifi do exist and are known to work better, as would a separate access point. But putting that USB port to some use would be more fun, and in my case conserve resources (power and device production).

@mpratt14
Copy link
Contributor

mpratt14 commented Mar 4, 2023

in the meantime would you happen to have an ath79 device to test it with?

@sobukus
Copy link

sobukus commented Mar 5, 2023

Nope, I only played with openwrt on this one mikrotik device. Maybe I can ask around.

@kbios
Copy link

kbios commented Mar 21, 2023

With the latest OpenWRT (2023-03-20 snapshot, firmware 0.40) there are no more "unrecognized signal" or "wrong frame size" errors in dmesg (on the RP-N53), but the behaviour is the same (clients cannot connect)

@neheb
Copy link
Contributor

neheb commented Nov 30, 2023

@mpratt14 since you added this, care to comment on the following changes?

--- a/target/linux/ramips/dts/mt7620a_engenius_epg600.dts
+++ b/target/linux/ramips/dts/mt7620a_engenius_epg600.dts
@@ -215,9 +215,9 @@
 };
 
 &pcie0 {
-       wifi@0,1,0 {
-               compatible = "pci1814,3091";
-               reg = <0x0 1 0 0 0>;
+       wifi@0,0 {
+               compatible = "pci1814,5592";
+               reg = <0x0000 0 0 0 0>;
                nvmem-cells = <&eeprom_factory_0>;
                nvmem-cell-names = "eeprom";
        };

seems to be copy/paste from the other engenius device where the pci reg values are a bit different:

@@ -161,9 +161,9 @@
 &pci1 {
        status = "okay";
 
-       wifi@0,1,0 {
+       wifi@0,0 {
                compatible = "pci1814,3091";
-               reg = <0x0 1 0 0 0>;
+               reg = <0x10000 0 0 0 0>;
                ralink,5ghz = <0>;
                nvmem-cells = <&eeprom_factory_8000>;
                nvmem-cell-names = "eeprom";

@mpratt14
Copy link
Contributor

if you're trying to solve this issue, that won't make a difference

I believe there's something wrong with the PCI driver that makes it incompatible with the rt5592

@neheb
Copy link
Contributor

neheb commented Nov 30, 2023

eh no I'm trying to fix dtc warnings. Addresses are wrong here. The pci id is as well.

@mpratt14
Copy link
Contributor

what's the warning? seems really strict...I don't see anything wrong with the way it is...

@neheb
Copy link
Contributor

neheb commented Nov 30, 2023

full commit: neheb@af1d5d3

the reg values are wrong. that's it. I copied what other dts files do to fix.

@mpratt14
Copy link
Contributor

mpratt14 commented Dec 1, 2023

What I put in DTS is just from what I saw in dmesg. I don't know that much about PCI so maybe the driver problems are causing a nonsense configuration to be displayed... I can't tell what's wrong here...

I use the class value 0x28000 to identify what's the actual wireless card/chip, it's the same across other devices and other subtargets that I have seen.

Side note on naming the "wifi" node: I've been told that the numbers after @ should be all the address cells, and that PCI has 3 address cells, not 2. I would imagine that changing the node name to 2 number values would either cause a warning or do nothing.

[    0.681420] PCI host bridge to bus 0000:00
[    0.685415] pci_bus 0000:00: root bus resource [mem 0x20000000-0x2fffffff]
[    0.692041] pci_bus 0000:00: root bus resource [io  0x10160000-0x1016ffff]
[    0.698729] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.706461] pci 0000:00:00.0: [1814:0801] type 01 class 0x060400
[    0.712270] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
[    0.718331] pci 0000:00:00.0: reg 0x14: [mem 0x00000000-0x0000ffff]
[    0.724510] pci 0000:00:00.0: supports D1
[    0.728335] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.736308] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.744245] pci 0000:01:00.0: [1814:3091] type 00 class 0x028000
[    0.750088] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x0000ffff]
[    0.756256] pci 0000:01:00.0: PME# supported from D0 D3hot
[    0.763813] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.770202] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01
[    0.776685] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
[    0.783055] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
[    0.789833] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x200fffff]
[    0.796411] pci 0000:00:00.0: BAR 1: assigned [mem 0x20100000-0x2010ffff]
[    0.803024] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x2000ffff]
[    0.809601] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.814429] pci 0000:00:00.0:   bridge window [mem 0x20000000-0x200fffff]
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0# cat vendor
0x1814
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0# cat device
0x3091
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0# cat irq
4
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0# cat class
0x028000
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0# cd of_node
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0/of_node# ls
compatible         name               ralink,mtd-eeprom  reg
root@OpenWrt:/sys/class/pci_bus/0000:01/device/0000:01:00.0/of_node# hexdump -C name
00000000  77 69 66 69 00                                    |wifi.|
00000005

@mpratt14
Copy link
Contributor

mpratt14 commented Dec 1, 2023

Another very old issue also reports the PCI ID discrepancy

#5692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray kernel pull request/issue with Linux kernel related changes release/21.02 pull request/issue targeted (also) for OpenWrt 21.02 release
Projects
None yet
Development

No branches or pull requests

7 participants