Your message dated Thu, 20 Feb 2025 15:23:42 +0100 (CET) with message-id <20250220142342.d4e69be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #1035939, regarding linux-image-6.1.0-8-amd64: dmesg flood xhci_hcd 0000:03:00.0: WARN: bandwidth overrun event for slot 6 ep 4 on endpoint to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: linux-image-6.1.0-8-amd64 Severity: normal X-Debbugs-Cc: cla...@mathr.co.uk Dear Maintainer, * What led up to the situation? I noticed a flood of messages (1000 per second!) in dmesg (mirrored in /var/log) after it filled my drive (16GB of logs total, over a couple of weeks). The message was: xhci_hcd 0000:03:00.0: WARN: bandwidth overrun event for slot 6 ep 4 on endpoint or xhci_hcd 0000:03:00.0: WARN: bandwidth overrun event for slot 11 ep 4 on endpoint (it reoccurred after rebooting, but does not seem predictable). * What exactly did you do (or not do) that was effective (or ineffective)? I unplugged my USB soundcard from my USB hub, and the message flood stopped. When plugging in the USB soundcard, dmesg reports similar to: usb 1-12.1.3: new full-speed USB device number 12 using xhci_hcd usb 1-12.1.3: New USB device found, idVendor=0582, idProduct=0074, bcdDevice= 1.07 usb 1-12.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-12.1.3: Product: EDIROL UA-25 usb 1-12.1.3: Manufacturer: Roland * What outcome did you expect instead? I expect potentially rapidly repeated kernel messages to be rate-limited to a sensible amount. I tried: cd linux-6.1.25/drivers/usb/host sed -i "s/xhci_warn/xhci_warn_ratelimited/g" xhci-ring.c sed -i "s/xhci_warn_ratelimited_ratelimited/xhci_warn_ratelimited/g" xhci-ring.c and rebuilt the kernel. I have not yet rebooted to test if it fixes my problem. Thanks for your work on this package, Claude -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (990, 'testing-security'), (990, 'testing'), (500, 'testing-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-8-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-8-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod 30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-8-amd64 recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-8-amd64 suggests: pn debian-kernel-handbook <none> ii extlinux 3:6.04~git20190206.bf6db5b4+dfsg1-3+b1 ii grub-efi-amd64 2.06-12 pn linux-doc-6.1 <none>
--- End Message ---
--- Begin Message ---Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---
