DriveSetup causes syslog spamming

[vidrep]

hrev53541 x86_64

Launching DriveSetup takes a very long time to detect drives. This is followed by spamming of the syslog with XHCI errors and stuttering mouse and keyboard function. The keyboard/mouse are connected to USB 2 ports and no devices are connected to any USB 3 ports. This same behavior is observed during the process of installing Haiku and using DriveSetup to partition and format drives.

[vidrep]

From syslog:

KERN: usb_disk: receiving the command status wrapper failed: Operation timed out

KERN: usb xhci 0: cancel queued transfers (5) for pipe 0xffffffff82beb648 (2)

KERN: usb error xhci 0: unsuccessful command 15, error Context state (19)

KERN: usb error xhci 0: KERN: cancel queued transfers: could not stop endpoint: I/O error!

KERN: usb_disk: acquire_sem failed while waiting for data transfer: Operation timed out

[vidrep]

I have attached listdev.txt and listusb.txt for device information.

[vidrep]

I noticed that when running listusb from the terminal, device detection took much longer than usual compared to other PC's I own which run Haiku.

[waddlesplash]

Please post a syslog; copy it out as soon after the app stalls start occuring as you can.

[waddlesplash]

Please retest after hrev53855.

[waddlesplash]

(And post a full syslog.)

[vidrep]

Tested with hrev53867 x86_64 Attached: syslog

[waddlesplash]

KERN: usb xhci 0: transfer error on slot 2 endpoint 5: Stall
KERN: usb xhci 0: KERN: cancel queued transfers (1) for pipe 0xffffffff82bea648 (2)
KERN: usb error xhci 0: unsuccessful command 15, error Context state (19)

I don't think we handle stalls properly yet, so that would explain the subsequent errors. I'm not sure what causes the stall though, that's odd. Either way, there's probably things I can do here.

[waddlesplash]

Please retest after hrev56123. Even if the problem is not resolved, please post a new syslog.