Opened 3 years ago
Closed 3 years ago
#17562 closed bug (fixed)
Wacom Graphire tablet spams syslog
Reported by: | humdinger | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta4 |
Component: | Drivers/USB/XHCI | Version: | R1/beta3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev55827, 64bit.
My very old Wacom Graphire (ET-0405-U) tablet works nicely, but spams the syslog with:
KERN: usb hub 2: port 1: new device connected KERN: wacom: add_device() - wacom detected KERN: wacom: ... success! KERN: wacom: device_open() open: 2 USER 'KS': Notify of added/removed/started/stopped device KERN: usb xhci 0: cancel queued transfers (1) for pipe 0xffffffffa2857a50 (1) KERN: usb xhci 0: transfer error on slot 3 endpoint 3: Stopped KERN: usb xhci 0: cancel queued transfers (1) for pipe 0xffffffffa2857a50 (1) KERN: usb xhci 0: transfer error on slot 3 endpoint 3: Stopped KERN: usb xhci 0: cancel queued transfers (1) for pipe 0xffffffffa2857a50 (1) KERN: usb xhci 0: transfer error on slot 3 endpoint 3: Stopped KERN: usb xhci 0: cancel queued transfers (1) for pipe 0xffffffffa2857a50 (1) KERN: usb xhci 0: transfer error on slot 3 endpoint 3: Stopped . . .
I suppose that's a bug in XHCI rather than the Wacom driver?
Change History (5)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
How frequently is the syslog spam?
These are actually harmless, they're more debug prints. They are however extremely useful in a variety of scenarios, so I don't really want to disable them just because they are "spammy" in some instances...
comment:4 by , 3 years ago
These are actually harmless, they're more debug prints. They are however extremely useful in a variety of scenarios, so I don't really want to disable them just because they are "spammy" in some instances...
What about a driver settings file to enable verbose logging for the USB stack at runtime? And/or an option in the boot menu.
I had some instances of verbose USB logs on my machine too. It's annoying to see the hard disk led blink every second because the syslog is being written to (or at least it seems that's what was happening) while the OS is otherwise idle...
comment:5 by , 3 years ago
Milestone: | Unscheduled → R1/beta4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I adjusted the logs in hrev55855 to retain most of their usefulness while also eliminating the spam in this instance and others.
Just found out: The syslog only gets spammed if I don't use the tablet. As soon as the pen is near enough to control the mouse pointer, the syslog entries stop. Maybe a driver or HID issue after all? Feel free to stuff this ticket into the right component...