Opened 5 years ago

Last modified 3 years ago

#15416 new bug

DriveSetup causes syslog spamming

Reported by: vidrep Owned by: waddlesplash
Priority: normal Milestone: Unscheduled
Component: Drivers/USB/XHCI Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #15706, #17070
Platform: All

Description

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.

Attachments (3)

listdev.txt​ (2.4 KB ) - added by vidrep 5 years ago.
listusb.txt​ (7.9 KB ) - added by vidrep 5 years ago.
syslog​ (122.6 KB ) - added by vidrep 5 years ago.

Download all attachments as: .zip

Change History (15)

comment:1 by vidrep, 5 years ago

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

comment:2 by waddlesplash, 5 years ago

Component: Applications/DriveSetup → Drivers/USB/XHCI
Owner: changed from stippi to waddlesplash

comment:3 by vidrep, 5 years ago

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

by vidrep, 5 years ago

Attachment: listdev.txt​ added

by vidrep, 5 years ago

Attachment: listusb.txt​ added

comment:4 by vidrep, 5 years ago

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 and the syslog is spammed with something a little different:

KERN: usb error xhci 0: KERN: _LinkDescriptorForPipe max transfers count exceeded

KERN: usb error hub 7: error updating port status

Last edited 5 years ago by vidrep (previous) (diff)

comment:5 by waddlesplash, 5 years ago

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

comment:6 by waddlesplash, 5 years ago

Please retest after hrev53855.

comment:7 by waddlesplash, 5 years ago

Blocking: 15706 added

comment:8 by waddlesplash, 5 years ago

(And post a full syslog.)

comment:9 by vidrep, 5 years ago

Tested with hrev53867 x86_64 Attached: syslog

by vidrep, 5 years ago

Attachment: syslog​ added

comment:10 by waddlesplash, 5 years ago 

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.

comment:11 by diver, 3 years ago

Blocking: 17070 added

comment:12 by waddlesplash, 3 years ago

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

Note: See TracTickets for help on using tickets.