kernel-5.2.9-200.fc30.x86_64 Kernel logs are spammed (= tens of messages per second) with : kernel: hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called with n (192) > 32! (kworker/7:0) This is a kernel bug, also reported with several other distributions (e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547) Reported at LKML : https://lkml.org/lkml/2019/3/8/2 Fixed : https://lkml.org/lkml/2019/3/8/2 Reverted : https://lkml.org/lkml/2019/4/25/848 Suggested workaround ("only warn once") : https://lkml.org/lkml/2019/5/21/834 Workaround : https://lkml.org/lkml/2019/8/12/740 Would it be possible to include/backport the workaround in the current 5.2.x releases ?
+1 for implementing the warn_once workaround, this bug is also an issue on my X1 Yoga and makes reading the kernel log almost impossible. I understand the actual fix of increasing the field size requires further work upstream, but it would be great to suppress the (useless IMHO) log spam.
This problem still applies to Fedora's kernel 5.3.0-200.fc30.x86_64.
Problem persists in 5.3.1-300.fc31.x86_64.
Fixed upstream by commit 1ad0bc78948652edc3067b6b49ba31b1598faa4a * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid: (27 commits) HID: core: fix dmesg flooding if report field larger than 32bit HID: core: Add printk_once variants to hid_warn() etc Would be nice if this could be backported to 5.3.
Created attachment 1624728 [details] dmesg output This issue is still present in 5.3.5-200.fc30.x86_64 : dmesg/journald/rsyslog is hit by about 40 superfluous warnings/second.
The problem persists in kernel-5.3.11-200.fc30.x86_64. The issue is resolved in kernel-5.4.0-2.vanilla.knurd.1.fc30.x86_64 (installed from the kernel-vanilla-stable repository, as described at https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories).
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
F30 being rebased to 5.5.x, this bug is resolved.