On 11/12/14 18:09, Stefan Sperling wrote:
On Wed, Nov 12, 2014 at 05:36:26PM +0000, S wrote:
Synopsis: urtwn(4) is unstable
Category: kernel
Environment:
System : OpenBSD 5.6
Details : OpenBSD 5.6-current (GENERIC.MP) #555: Wed Nov 12
00:58:05 MST 2014
[email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
Machine : amd64
Description:
When using the snapshot from November 2 and 5.5, my ASUS USB-N10 using
the urtwn(4) driver would stop working after a reboot (halt -p then
power on caused no problems).
After upgrading to the November 12 snapshot, I found that it stopped
working after a cold boot during a package upgrade, and again while
browsing the web.
"urtwn0: device timeout" appears in dmesg and the status LED on the
device turns off until netstart is run again.
xhci(4) might factor in here.
See http://undeadly.org/cgi?action=article&sid=20141110153505
xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
urtwn0 at uhub0 port 2 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 3
urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 10:c3:7b:c8:2c:55
Yes, that's quite likely. My bug report may have been a bit early since
I'm now seeing a similar problem with my USB mouse where it stops
working at seemingly random times until it is re-attached.
