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#2992 - USB problem on bcm6318 #7759

Open
openwrt-bot opened this issue Apr 10, 2020 · 1 comment
Open

FS#2992 - USB problem on bcm6318 #7759

openwrt-bot opened this issue Apr 10, 2020 · 1 comment
Labels
flyspray kernel

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Apr 10, 2020

xchetah:

Hi
I'm using openwrt on bcm63xx bcm6318 sagemcom F@ST 2704N V1.
the router is actually V1.1 (16MB flash , 64MB RAM).
trying to connect a usb wifi dongle as AP

root@Openwrt:~# lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

wlan1 Link encap:Ethernet HWaddr 7C:DD:90:48:2A:D2
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::7edd:90ff:fe48:2ad2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:955 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:184246 (179.9 KiB)

the problem is that there's no connectivity at all , I can connect to the AP (only without encryption ) and the ssid doesn't always show on my mobile phone.
the usb port is working fine , I tried mounting a usb flash drive with no problem.
also the adapter is working , I tried it on Orange pi , Raspberrypi , bcm6328 , all with openwrt installed on them and didn't have any problem .
I guess it is something related to bcm6318 or its architecture code .
the onboard broadcom pci wifi is working .
I suspected that its a power problem so I added an external usb power , but with same issues.
also I tried openwrt 19 ,18 ,17 with same problem.
I'm also using two bcm6328 routers as point to point wifi 5ghz link with Ralink RT5572 chipset ( rt2800usb driver ) withouyt any problem.
dmesg is filled with :

[ 1269.191198] rt2800usb_tx_sta_fifo_read_completed: 13054 callbacks suppressed
[ 1269.191239] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.208421] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.218373] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.228285] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.238151] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.248029] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.257902] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.267793] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.278183] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32
[ 1269.287995] ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -32

using rmmod to remove rt2800usb module results in kernel crash /sometimes hang and sometimes panic and reboot.

steps to reproduce:
-boot the router with usb wifi dongle
-configure it as access point and enable it

  • dmesg log starts to fill and adapter is not working
@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Apr 15, 2020

adrianschmutzler:

When googling, the standard explanation for the warning is "insufficient power" indeed, however they have a different error code.

Anyway, this is a kernel issue, so we won't be able to help much.

You can only try to build an image from master with testing kernel enabled (in make menucnonfig -> Global build settings -> Use testing kernel version). This will give you kernel 5.4, maybe there has been a fix there in the meantime.

@aparcar aparcar added the kernel label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray kernel
Projects
None yet
Development

No branches or pull requests

2 participants