https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244902
Bug ID: 244902
Summary: rtwn wlan driver failed to associate on USB3, but
succeeds on USB2
Product: Base System
Version: 12.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: usb
Assignee: u...@freebsd.org
Reporter: ruairi.carr...@gmail.com
Created attachment 212519
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=212519&action=edit
gzip'd tarball containing all files
Hey,
I have a TP-WN823N V3 USB Wi-Fi adapter connected via USB3.0. This module
refused to work on bare metal, but worked happily when connected to VM for
local testing. After some investigation, it seems that the USB mode affects the
drivers behaviour - USB3.0 controller and the driver loads, but refuses to
associate with the SSID. However switch to a USB2.0 controller, and the driver
behaves correctly. Specifically, the failure scenario here is that the driver
ends up calling r92e_power_off and the module powers off completely, and needs
to be re-seated.
I setup a test bed, a fresh install of FreeBSD 12.1.
which I've taken with the following enabled:
sysctl hw.usb.ehci.iaadbug=1
sysctl hw.usb.ehci.debug=1
sysctl hw.usb.xhci.debug=1
Attached are two sets of logs;
On successful association:
- freebsd_syslog_success.txt - /var/log/messages syslog taken with
- freebsd_cli_success.txt - loading the driver and calling wpa_supplicant(with
timestamp)
On unsuccessful association:
- freebsd_syslog_failure.txt - /var/log/messages syslog taken with
- freebsd_cli_failure.txt - loading the driver and calling wpa_supplicant(with
timestamp)
I'm not sure how to further debug this issue, so I could use a little help
please.
/Ruairi
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
