Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Jul 2020 20:22:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        wireless@FreeBSD.org
Subject:   [Bug 247528] RTL8192EU usb wifi dongle can't connect to AP
Message-ID:  <bug-247528-21060-z5A6viC85s@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-247528-21060@https.bugs.freebsd.org/bugzilla/>
References:  <bug-247528-21060@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247528

Danilo Egea Gondolfo <danilo@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |danilo@FreeBSD.org

--- Comment #3 from Danilo Egea Gondolfo <danilo@FreeBSD.org> ---
Exactly same problem here. I have a tplink wn823n (RTL8192EU).

The issue is easily reproducible. The device will get UP and things like
scanning and adhoc mode will work fine. But if you "ifconfig down" the
interface and "ifconfig up" it again it will stuck and the device will get
disconnected from the USB bus.

This will make wpa_supplicant try to connect using WPA but it will fail:

ifconfig wlan0 create wlandev rtwn0
wpa_supplicant -i wlan0 -c...

Note that the interface is still down before running wpa_supplicant.
wpa_supplicant will put the interface UP and try to connect although it will
fail with authentication timeout.

If you put the interface UP yourself and then run wpa_supplicant it will fa=
il
and the device will be kicked out from the USB bus when it sends a second
ioctl(... IFF_UP) to the interface.

So, the problem is reproducible with:

ifconfig wlan0 create wlandev rtwn0 up
ifconfig wlan0 down
ifconfig wlan0 up

The last command will stuck here:

17899 101638 ifconfig            -                   mi_switch+0xc1
_sleep+0x1cb taskqueue_drain+0xeb ieee80211_waitfor_parent+0x28
ieee80211_ioctl+0x44b ifhwioctl+0xbb2 ifioctl+0x419 kern_ioctl+0x25e
sys_ioctl+0xfa amd64_syscall+0x119 fast_syscall_common+0x101=20


And this is what happens:

ugen0.4: <Realtek 802.11n NIC> at usbus0
rtwn0 on uhub0
rtwn0: <802.11n NIC > on usbus0
rtwn0: MAC/BB RTL8192EU, RF 6052 2T2R
wlan1: Ethernet address: d0:37:45:0a:a3:81
ugen0.4: <Realtek 802.11n NIC> at usbus0 (disconnected)
rtwn0: at uhub0, port 1, addr 13 (disconnected)
rtwn0: r92e_power_off: failed to block Tx queues
rtwn0: detached
usb_alloc_device: set address 4 failed (USB_ERR_IOERROR, ignored)
usbd_setup_device_desc: getting device descriptor at addr 4 failed,
USB_ERR_IOERROR
usbd_req_re_enumerate: addr=3D4, set address failed! (USB_ERR_IOERROR, igno=
red)
usbd_setup_device_desc: getting device descriptor at addr 4 failed,
USB_ERR_IOERROR
usbd_req_re_enumerate: addr=3D4, set address failed! (USB_ERR_IOERROR, igno=
red)
usbd_setup_device_desc: getting device descriptor at addr 4 failed,
USB_ERR_IOERROR
usbd_req_re_enumerate: addr=3D4, set address failed! (USB_ERR_IOERROR, igno=
red)
usbd_setup_device_desc: getting device descriptor at addr 4 failed,
USB_ERR_IOERROR
usbd_req_re_enumerate: addr=3D4, set address failed! (USB_ERR_IOERROR, igno=
red)
usbd_setup_device_desc: getting device descriptor at addr 4 failed,
USB_ERR_IOERROR
ugen0.4: <Unknown > at usbus0 (disconnected)
uhub_reattach_port: could not allocate new device

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247528-21060-z5A6viC85s>