Date: Sat, 09 Feb 2019 20:22:20 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 235625] Repeated excessive logging about unsuccessful port reset during device enumeration Message-ID: <bug-235625-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235625 Bug ID: 235625 Summary: Repeated excessive logging about unsuccessful port reset during device enumeration Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: usb Assignee: usb@FreeBSD.org Reporter: maxsteciuk@gmail.com Since FreeBSD 12 build around last summer it was noticed the syslog was flo= oded with the following messages >>>Jan 29 20:18:44 kernel: uhub_reattach_port: giving up port reset - devic= e vanished Although the log message is displayed the USB devices and hubs are function= al: successfully connected and working. The following sysctl configuration helps to get rid of excessive logging b= ut the downside that certain USB devices (e.g. Create SoundBlaster) are not ev= en getting recognized by USB hub controller. >>>hw.usb.disable_enumeration=3D1 As a quick solution I decreased log level for the message from 0 to 1 so t= hat at least to reduce log noise.=20 Here is a small proposed patch for decreasing log level: https://github.com/trueos/trueos/pull/283/files As a more elaborate solution I was thinking about possibility to implement = log throttling for this warning so it logs a suficient number of times to brin= g to attention but not inifinitely. Another question is whether this is a symptom of a larger problem: is something broken (e.g. sys/dev/usb/usb_hub.c , /sys/dev/usb_device.c) or n= ot functioning as expected... Thanks, Max --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235625-19105>