Opened 3 years ago

Last modified 2 years ago

#17464 new bug

xhci finding new USB device every second — at Version 5

Reported by: beaglejoe Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Drivers/USB/XHCI Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64

Description (last modified by beaglejoe)

From my syslog (hrev55711):

KERN: usb hub 7: port 0: new device connected
KERN: usb error xhci 1: AllocateDevice: failed to enable slot
Last message repeated 1 time
KERN: usb hub 7: port 0: new device connected
KERN: usb error xhci 1: AllocateDevice: failed to enable slot
Last message repeated 1 time

Running tail on syslog, this repeats approximately once per second.
The only (externally connected) USB device attached is a wireless keyboard/mouse dongle, which works fine, USB thumbdrives also work fine. Maybe duplicate of #16323

Change History (8)

by beaglejoe, 3 years ago

Attachment: syslog added

comment:1 by beaglejoe, 3 years ago

Hardware is an Intel NUC 8

This did not appear in a syslog from hrev55690. It started with hrev55692

comment:2 by waddlesplash, 3 years ago

That ticket was fixed, this is probably the "underlying problem" I mentioned there. I'm not sure why slots would fail to enable, though, this is an area I'm less familiar with.

comment:3 by beaglejoe, 3 years ago

It seems to cause no problems (except for bloated syslog). I didn't know if I should set it to "low" priority or if that was for the dev team to decide. I suspect it has always been there and hvre55691 just enabled the trace for it, but I didn't look at the code for that commit.

comment:4 by waddlesplash, 2 years ago

Looking over the code, it seems there is only one way to get out of this function without an error trace to the syslog, which is that Lock() must be failing. This is extremely strange and should never occur; we should hit some panic asserts in mutex code before that happens; or we have been woken up spuriously with an error condition, which would be strange but I guess is possible.

Can you please upgrade to the latest nightly and re-test this, and see if it still happens, and upload a new syslog if it does?

If it does, can you please show the output of "listimage 1"?

by beaglejoe, 2 years ago

Attachment: syslog-hrev55736 added

by beaglejoe, 2 years ago

Attachment: listimage1.txt added

comment:5 by beaglejoe, 2 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.