Opened 8 months ago

Closed 8 months ago

Last modified 8 months ago

#14959 closed bug (fixed)

USB Ethernet adapter causing KDL

Reported by: mrentropy Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/USB/XHCI Version: R1/Development
Keywords: ethernet, insignia, gigabit Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86-64

Description

Device: Insignia USB 3.0 to Gigabit Ethernet Adapter Model No: NS-PU98635/NS-PU98635-C

Was working plugged into a USB2 port with hrev52947 x86_64

After updating to hrev52992, booting with the device plugged into USB2 or USB3 caused Haiku to enter KDL. Plugging device into a USB2 port when Haiku was fully booted also caused KDL.

Attachments (5)

listusb.txt (882 bytes ) - added by mrentropy 8 months ago.
Contents of listusb when device was working
syslog (160.5 KB ) - added by mrentropy 8 months ago.
Syslog from when device was working hrev52947
IMG_1451.HEIC (1.7 MB ) - added by mrentropy 8 months ago.
KDL when booting with device attached with hrev52992
IMG_1451.jpg (1.5 MB ) - added by waddlesplash 8 months ago.
syslog_TP-Link UE300_hrev53000 (483.9 KB ) - added by fotisk 8 months ago.

Change History (14)

by mrentropy, 8 months ago

Attachment: listusb.txt added

Contents of listusb when device was working

by mrentropy, 8 months ago

Attachment: syslog added

Syslog from when device was working hrev52947

by mrentropy, 8 months ago

Attachment: IMG_1451.HEIC added

KDL when booting with device attached with hrev52992

by waddlesplash, 8 months ago

Attachment: IMG_1451.jpg added

comment:1 by waddlesplash, 8 months ago

Please attach a more commonly readable file format, next time...

At any rate, this has little to do with USB network drivers, it appears I just messed up lock order somehow.

comment:2 by waddlesplash, 8 months ago

So, I really don't understand how I messed this up, the code looks perfectly fine to me. We lock the lock once at the top of the function; there is no way for mutex_lock to fail in KDEBUG mode (that I can tell), and then there is only one way out at the bottom, and we unlock the mutex there. How does this lead to a double-unlock?

comment:3 by waddlesplash, 8 months ago

Please retest after hrev52997.

comment:4 by waddlesplash, 8 months ago

Resolution: fixed
Status: newclosed

Another user reported on the forums that the KDL with USB-ECM devices is now gone.

comment:5 by fotisk, 8 months ago

My usb_to_ethernet adapter doesn't work anymore in hrev53000. Stays in "Configuring.." state. Was fully working on hrev52989. TP-Link UE300 (USB 3.0 to Gigabit). I attach my syslog in case it helps. I hope I am commenting on the right tcket, sorry if not.

Last edited 8 months ago by fotisk (previous) (diff)

by fotisk, 8 months ago

comment:6 by waddlesplash, 8 months ago

Please open a new ticket. It seems that your device is continually resetting. Can you try it on a USB2 port?

comment:7 by mrentropy, 8 months ago

The KDLs have, indeed, stopped. However, the device no longer works. It shows up and has a MAC address, but syslog shows a lot of send/requests to the DHCP server with the occasional "unsupported ioctl 8925" message.'

I'm guessing you'll want a new ticket for that and close this one?

comment:8 by waddlesplash, 8 months ago

Yes. As said before, please try it on a USB2 port also.

comment:9 by fotisk, 8 months ago

My device (TP-Link) is connected to a USB2 port through an external USB2 hub. The exact same configuration that works when I boot to hrev52989. I will try to test it with direct connection also and not through the hub to see if something changes. Will create a new ticket unless mrentropy creates it first.

Note: See TracTickets for help on using tickets.