[Bug 1918065] [NEW] Zen 3 (Ryzen 5XXX) temperatures not reported by k10temp
Public bug reported: Current reports from `sensors` for Zen 3 CPUs: ``` PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C ``` This bug is due to the lack of Zen 3 support in Ubuntu's implementation of k10temp. Zen 3 (Ryzen 5XXX) temperature support is now ready as a part of `k10temp`: https://www.kernel.org/doc/html/latest/hwmon/k10temp.html and narrowly missed the window for mainline kernel 5.12. My understanding is it was included in 5.10, removed in 5.11 for documentation/validation reasons, then planned again after updates. With the popularity of these chips increasing, having accurate CPU temp readings is of import in Ubuntu 20.04, as this is an LTS release with support until 2025. Therefore, as we are set at kernel 5.8 at the moment, with 21.04 releasing with kernel 5.11, it may be worth pulling in the latest k10temp to fix this bug as to not delay access to vital CPU information throughout 2020. Thanks. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918065 Title: Zen 3 (Ryzen 5XXX) temperatures not reported by k10temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1918065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908921] Re: No system tray detected by hp-systray
I am also affected with HPLIP and Nextcloud. Icon's do not display as there is no System Tray. Killing the apps and restarting them works, so the "delay" is likely the issue again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I am getting the same issue with a new device. Everything works fine on one BT USB, but the intel one fails. It is a PCIe card with Intel AX200 Wifi+BT, with BT being passed through a USB header. First boot with new card (dmesg): ``` [ 20.708957] Bluetooth: Core ver 2.22 [ 20.708971] Bluetooth: HCI device and connection manager initialized [ 20.708974] Bluetooth: HCI socket layer initialized [ 20.708975] Bluetooth: L2CAP socket layer initialized [ 20.708978] Bluetooth: SCO socket layer initialized [ 20.718527] usbcore: registered new interface driver btusb [ 20.719034] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 [ 20.720327] Bluetooth: hci0: Device revision is 1 [ 20.720328] Bluetooth: hci0: Secure boot is enabled [ 20.720329] Bluetooth: hci0: OTP lock is enabled [ 20.720329] Bluetooth: hci0: API lock is enabled [ 20.720330] Bluetooth: hci0: Debug lock is disabled [ 20.720331] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 20.725091] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [ 21.839173] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 21.839174] Bluetooth: BNEP filters: protocol multicast [ 21.839176] Bluetooth: BNEP socket layer initialized [ 22.274234] Bluetooth: hci0: Waiting for firmware download to complete [ 22.275022] Bluetooth: hci0: Firmware loaded in 1519998 usecs [ 22.275058] Bluetooth: hci0: Waiting for device to boot [ 22.289027] Bluetooth: hci0: Device booted in 13657 usecs [ 22.289187] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc [ 22.290032] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22) [ 35.565521] Bluetooth: RFCOMM TTY layer initialized [ 35.565525] Bluetooth: RFCOMM socket layer initialized [ 35.565527] Bluetooth: RFCOMM ver 1.11 ``` Next boot: ``` [ 19.608303] Bluetooth: Core ver 2.22 [ 19.608315] Bluetooth: HCI device and connection manager initialized [ 19.608318] Bluetooth: HCI socket layer initialized [ 19.608319] Bluetooth: L2CAP socket layer initialized [ 19.608321] Bluetooth: SCO socket layer initialized [ 19.616842] usbcore: registered new interface driver btusb [ 19.617945] Bluetooth: hci0: Firmware revision 0.0 build 128 week 11 2020 [ 20.872710] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.872711] Bluetooth: BNEP filters: protocol multicast [ 20.872714] Bluetooth: BNEP socket layer initialized [ 34.561042] Bluetooth: RFCOMM TTY layer initialized [ 34.561048] Bluetooth: RFCOMM socket layer initialized [ 34.561050] Bluetooth: RFCOMM ver 1.11 ``` `lsusb -v`: ``` Bus 003 Device 003: ID 8087:0029 Intel Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x8087 Intel Corp. idProduct 0x0029 bcdDevice0.01 iManufacturer 0 iProduct0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x00c8 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I should also note, if it helps, that when this BT device is installed on the system, using the hotkeys to adjust volume on my keyboard no longer works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842951] Re: adcli join fails
Just wanted to let others know this impacts me in 19.10 as well, and http://ftp.us.debian.org/debian/pool/main/a/adcli/adcli_0.9.0-1_amd64.deb worked for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842951 Title: adcli join fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1842951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts
Ok, well, no idea what happened, but I did a hard power cycle with that kernel parameter, and it started working. I rebooted again without it, and it still worked. Perhaps the hard power cycle did something different this time with the new BIOS, but I thought I had done that since. In any event, it's unfortunate I can't point to the specific issue, but good that it's working. Thanks for the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824703 Title: Intel 8260 Bluetooth non-functioning, command timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts
Ignore that, typo. Blacklisting correctly didn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824703 Title: Intel 8260 Bluetooth non-functioning, command timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts
Hmm, blacklisting iwlwifi didn't do anything, but I still see this in my lsmod: iwlmvm364544 0 mac80211 778240 1 iwlmvm iwlwifi 286720 1 iwlmvm cfg80211 622592 3 iwlmvm,iwlwifi,mac80211 Should I be blacklisting more? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824703 Title: Intel 8260 Bluetooth non-functioning, command timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts
I was hoping that would be it, but no luck, dmesg with F23f: [ 13.498936] Bluetooth: Core ver 2.22 [ 13.498948] Bluetooth: HCI device and connection manager initialized [ 13.498950] Bluetooth: HCI socket layer initialized [ 13.498951] Bluetooth: L2CAP socket layer initialized [ 13.498955] Bluetooth: SCO socket layer initialized [ 15.548029] Bluetooth: hci0: command 0xfc05 tx timeout [ 15.548030] Bluetooth: hci0: Reading Intel version information failed (-110) [ 15.548196] Bluetooth: hci0: Hardware error 0x08 [ 16.464647] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.464647] Bluetooth: BNEP filters: protocol multicast [ 16.464650] Bluetooth: BNEP socket layer initialized [ 17.564019] Bluetooth: hci0: command 0x0c03 tx timeout [ 25.564094] Bluetooth: hci0: Reset after hardware error failed (-110) [ 27.580108] Bluetooth: hci0: command 0xfc05 tx timeout [ 27.580113] Bluetooth: hci0: Reading Intel version information failed (-110) [ 27.580392] Bluetooth: hci0: Hardware error 0x08 [ 29.596262] Bluetooth: hci0: command 0x0c03 tx timeout [ 37.596249] Bluetooth: hci0: Reset after hardware error failed (-110) [ 39.612268] Bluetooth: hci0: command 0xfc05 tx timeout [ 39.612273] Bluetooth: hci0: Reading Intel version information failed (-110) [ 39.612632] Bluetooth: hci0: Hardware error 0x08 [ 41.628036] Bluetooth: hci0: command 0x0c03 tx timeout [ 49.628278] Bluetooth: hci0: Reset after hardware error failed (-110) [ 51.644041] Bluetooth: hci0: Reading Intel version information failed (-110) [ 51.644042] Bluetooth: hci0: command 0xfc05 tx timeout [ 51.644387] Bluetooth: hci0: Hardware error 0x08 [ 53.660275] Bluetooth: hci0: command 0x0c03 tx timeout [ 61.660277] Bluetooth: hci0: Reset after hardware error failed (-110) [ 63.676041] Bluetooth: hci0: Reading Intel version information failed (-110) [ 63.676195] Bluetooth: hci0: Hardware error 0x08 [ 63.680256] Bluetooth: hci0: command tx timeout [ 65.696082] Bluetooth: hci0: command 0x0c03 tx timeout [ 73.692015] Bluetooth: hci0: Reset after hardware error failed (-110) [ 75.708048] Bluetooth: hci0: command 0xfc05 tx timeout [ 75.708052] Bluetooth: hci0: Reading Intel version information failed (-110) [ 75.708380] Bluetooth: hci0: Hardware error 0x08 [ 77.724262] Bluetooth: hci0: command 0x0c03 tx timeout [ 85.724292] Bluetooth: hci0: Reset after hardware error failed (-110) [ 87.740300] Bluetooth: hci0: Reading Intel version information failed (-110) [ 87.740301] Bluetooth: hci0: command 0xfc05 tx timeout [ 87.740553] Bluetooth: hci0: Hardware error 0x08 [ 89.756583] Bluetooth: hci0: command 0x0c03 tx timeout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824703 Title: Intel 8260 Bluetooth non-functioning, command timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823150] Re: Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version information failed (-110))
I was redirected here as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703 The proposed fix does not work for me as I still receive the same error. Installed deb, updated initrd, rebooted. Still issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823150 Title: Bluetooth cannot be turned on (Bluetooth: hci0: Reading Intel version information failed (-110)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824703] [NEW] Intel 8260 Bluetooth non-functioning, command timeouts
Public bug reported: When trying to use the Gigabyte Z170N-Gaming 5, with Intel 8260 wifi+bluetooth, bluetooth does not function. Dmesg shows: [ 13.051985] Bluetooth: Core ver 2.22 [ 13.051996] Bluetooth: HCI device and connection manager initialized [ 13.051998] Bluetooth: HCI socket layer initialized [ 13.051999] Bluetooth: L2CAP socket layer initialized [ 13.052031] Bluetooth: SCO socket layer initialized [ 15.100035] Bluetooth: hci0: Reading Intel version information failed (-110) [ 15.100036] Bluetooth: hci0: command 0xfc05 tx timeout [ 15.100270] Bluetooth: hci0: Hardware error 0x08 [ 15.978374] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.978375] Bluetooth: BNEP filters: protocol multicast [ 15.978377] Bluetooth: BNEP socket layer initialized [ 17.116013] Bluetooth: hci0: command 0x0c03 tx timeout [ 25.308049] Bluetooth: hci0: Reset after hardware error failed (-110) [ 27.324270] Bluetooth: hci0: Reading Intel version information failed (-110) [ 27.324275] Bluetooth: hci0: command 0xfc05 tx timeout [ 27.324612] Bluetooth: hci0: Hardware error 0x08 [ 29.340020] Bluetooth: hci0: command 0x0c03 tx timeout [ 37.340274] Bluetooth: hci0: Reset after hardware error failed (-110) [ 39.356059] Bluetooth: hci0: Reading Intel version information failed (-110) [ 39.356071] Bluetooth: hci0: command 0xfc05 tx timeout [ 39.356499] Bluetooth: hci0: Hardware error 0x08 I have tried the latest intel firmwares from mainline based on: https://bugzilla.kernel.org/show_bug.cgi?id=197147#c81 and https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ with no luck. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fmstrat2489 F pulseaudio /dev/snd/controlC0: fmstrat2489 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 09:14:54 2019 InstallationDate: Installed on 2019-01-20 (83 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Z170N-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=16462d84-0501-4b74-aeff-7765953b648f ro modprobe.blacklist=nouveau quiet splash intel_iommu=on hugepages=4096 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 04/25/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170N-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/25/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170N-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170N-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170N-Gaming 5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824703 Title: Intel 8260 Bluetooth non-functioning, command timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819389] Re: i2c_hid_get_input: incomplete report in v5.0.0
I will give this a shot today, however after pulling the latest kernel source, it looks like part of that patch made it in, but not all of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819389] Re: i2c_hid_get_input: incomplete report in v5.0.0
NOTE: The pen also reports a 1% battery all of the time. I'm not sure if this is directly related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819389] Re: i2c_hid_get_input: incomplete report in v5.0.0
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+attachment/5245275/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819389] [NEW] i2c_hid_get_input: incomplete report in v5.0.0
Public bug reported: Similar issue to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152, however the fix in 4.18 does not seem to work for this one. When using the pen included with the HP Spectre x360 13" and libinput1.10 or libinput 1.12, dmesg is flooded with: ... [ 87.571189] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.577156] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.586621] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.600126] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.645181] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.647241] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) ... Please see attached details. At first, the pen functions normally, however after approximately 1 minute of use, it will continue to move windows but loses writing and drawing capabilities in applications. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg2.log" https://bugs.launchpad.net/bugs/1819389/+attachment/5245274/+files/dmesg2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819389] Re: i2c_hid_get_input: incomplete report in v5.0.0
Version is 5.0.0+ (only patch applied for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547), so should not have impact here as the error exists with or without that patch. ** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+attachment/5245276/+files/version.log ** Description changed: Similar issue to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152, however the fix in 4.18 does not seem to work for this one. When using the pen included with the HP Spectre x360 13" and libinput1.10 or libinput 1.12, dmesg is flooded with: ... [ 87.571189] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.577156] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.586621] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.600126] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.645181] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) [ 87.647241] i2c_hid i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/65535) ... - Please see attached details. + Please see attached details. At first, the pen functions normally, + however after approximately 1 minute of use, it will continue to move + windows but loses writing and drawing capabilities in applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819389 Title: i2c_hid_get_input: incomplete report in v5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819282] Re: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0
** Attachment added: "dmidecode.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244994/+files/dmidecode.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819282 Title: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819282] [NEW] Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0
Public bug reported: Hardware: HP Spectre x360 13" i7 2018 Gem Cut No s3 support and ACPI errors in dmesg: [0.165087] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.165087] ACPI: bus type PCI registered [0.165087] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.165087] PCI: MMCONFIG for domain [bus 00-ff] at [mem 0xe000-0xefff] (base 0xe000) [0.165087] PCI: MMCONFIG at [mem 0xe000-0xefff] reserved in E820 [0.165087] PCI: Using configuration type 1 for base access [0.165256] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.165256] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.165256] ACPI: Added _OSI(Module Device) [0.165256] ACPI: Added _OSI(Processor Device) [0.165256] ACPI: Added _OSI(3.0 _SCP Extensions) [0.165256] ACPI: Added _OSI(Processor Aggregator Device) [0.165256] ACPI: Added _OSI(Linux-Dell-Video) [0.165256] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.165256] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [0.209836] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.XDCI], AE_NOT_FOUND (20181213/dswload2-160) [0.209841] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [0.209844] ACPI: Skipping parse of AML opcode: Scope (0x0010) [0.210311] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.I2C1.TPL1], AE_NOT_FOUND (20181213/dswload2-160) [0.210315] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20181213/psobject-221) [0.210317] ACPI: Skipping parse of AML opcode: Scope (0x0010) [0.210811] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.210814] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.210816] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.210817] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.210820] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.210822] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.210823] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20181213/dswload2-324) ... Full output of many AE_ALREADY_EXISTS in attached dmesg. I am running v5.0.0+ (only change is the patch for the hid error reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547 ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1819282/+attachment/5244987/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819282 Title: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819282] Re: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244989/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819282 Title: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819282] Re: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244988/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819282 Title: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819282] Re: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0
** Attachment added: "cat-sys-power-mem_sleep.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+attachment/5244991/+files/cat-sys-power-mem_sleep.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819282 Title: Whiskey Lake and HP: ACPI AE_NOT_FOUND and no s3 in kernel v5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
As per Mayur's comments, orientation does work in 4.20, and in 5.0. Mic does not. I'm working on debugging and will submit a ticket for that if I can figure anything out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
That did the trick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I will give that a shot and report back. Should the implement function on line 1347 be changed as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
There are a lot of HID changes in the previous commit of 61c4fc1eaf736344904767d201b0d4f7a2ebaf79, so I guess it's possible there is perhaps something in the previous commit that is causing the 128/256 conflict. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
Hrm, I went looking to see if I could help resolve, but I have to admit,
at first glance I don't get it. The commit diff:
$ git diff 7a324b3f0535ceb0f6676fa20ca2a7b6213008cb
71f6fa90a353605bf25c36417c9ae529ac1a9a8d
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 3da354af7a0a..ef009db512ee 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -406,7 +406,7 @@ static int hid_parser_global(struct hid_parser *parser,
struct hid_item *item)
case HID_GLOBAL_ITEM_TAG_REPORT_SIZE:
parser->global.report_size = item_udata(item);
- if (parser->global.report_size > 128) {
+ if (parser->global.report_size > 256) {
hid_err(parser->device, "invalid report_size %d\n",
parser->global.report_size);
return -1;
The increase from 128 to 256 should not create a scenario where the bug
can exist. If it was originally below 128 and not throwing an error,
then it should be below 256.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818547
Title:
hid-sensor-hub spamming dmesg in 4.20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
71f6fa90a353605bf25c36417c9ae529ac1a9a8d is the first bad commit commit 71f6fa90a353605bf25c36417c9ae529ac1a9a8d Author: Song, Hongyan Date: Fri Aug 3 14:45:59 2018 +0800 HID: increase maximum global item tag report size to 256 The maximum globale report size has changed from 32->...->96->128 in the past years. With the development usage of HID, the report_size max value 128 cannot satisfy all requirements. There are applications need to expose intrinsic metadata to camera stabilizing applications such as 3DFE application. 3DFE intrinsic is designed to express environmental information about sensor that may dynamically change while the sensor is running (such data include noise spectral density, bias standard deviation) A sensor data field is SENSOR_VALUE_PAIR that consists of a PROPERTYKEY and PROPVARIANT pair. It need to report a unique PROPERTYKEY for each data field. Take “Noise Spectral Density” as an example, it report count will be defined as below: "Size of Property key GUID(16 Byte) + property key index(4 Byte) + size of Noise Spectral Density value(4 Byte)" In this case, the data report max is totally 192(24Byte), which is larger than 128, while max size 128 blocked it as illegal length. So increase the report size to satisfy it and more demands in the future. Signed-off-by: Song Hongyan Signed-off-by: Jiri Kosina :04 04 c44ade4341c21e45c653cce63bee3a1411a9cc72 90c14f2502206b9b4884e49cbe1fdef5602a795d M drivers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
My device also has orientation (that works) (HP Spectre x360 13"). I am attempting the bisection without the deb pkg now. Just keeping a log for if it's helpful. 1) 4.19.0+ Erorr displayed, touchpad didn't function 2) 4.19.0-rc8+ Did not show the error, touchpad functioned 3) 4.19.0+ No error, touchpad functioned 4) 4.19.0+ Erorr displayed, touchpad didn't function 5) 4.19.0+ Erorr displayed, touchpad didn't function 6) 4.19.0+ No error, touchpad functioned 7) 4.19.0+ Erorr displayed, touchpad didn't function 8) 4.19.0-rc6+ Erorr displayed, touchpad didn't function 9) 4.19.0-rc3+ Erorr displayed, touchpad functions 10) 4.19.0-rc3+ No error, touchpad functions 11) 4.18.0+ Error displayed, touchpad functions 12) 4.18.0+ Error displayed, touchpad functions 13) 4.18.0+ Error displayed, touchpad functions My next post will contain the commit (need to switch back to that machine to post). Out of curiousity, is there a reason bisection is not supported at the sub-version level? I.E v4.19.27-v4.20-rc1? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I've just tried official 4.19.0, and no issue there. So I'm not sure what's going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
It happens in 4.20-rc1, so should I try to bisect between 4.19 and 4.20-rc1? I gave that a shot, but after labeling the first try "bad", the next make gave me: ... dpkg-source: warning: no source format specified in debian/source/format, see dpkg-source(1) dpkg-source: info: using source format '1.0' dpkg-source: warning: source directory 'linux' is not - 'linux-4.19.0-rc8+-4.19.0-rc8+' dpkg-source: warning: .orig directory name linux.orig is not - (wanted linux-4.19.0-rc8+-4.19.0-rc8+.orig) dpkg-source: info: building linux-4.19.0-rc8+ using existing linux-4.19.0-rc8+_4.19.0-rc8+.orig.tar.gz dpkg-source: info: building linux-4.19.0-rc8+ in linux-4.19.0-rc8+_4.19.0-rc8+-1.diff.gz dpkg-source: error: cannot represent change to vmlinux-gdb.py: dpkg-source: error: new version is symlink to /opt/kernel/linux/scripts/gdb/vmlinux-gdb.py dpkg-source: error: old version is nonexistent dpkg-source: warning: ignoring deletion of file .scmversion, use --include-removal to override dpkg-source: warning: the diff modifies the following upstream files: ... dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1) dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i.git -b linux subprocess returned exit status 1 scripts/package/Makefile:71: recipe for target 'deb-pkg' failed make[1]: *** [deb-pkg] Error 1 Makefile:1357: recipe for target 'deb-pkg' failed make: *** [deb-pkg] Error 2 So I'm not sure where to go from here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
As a note, the issue shows up in the first build attempt which was "linux-image-4.19.0+_4.19.0+-1_amd64.deb". This seems like before the 4.19.27 I did not see the issue in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
It happens in 4.20-rc1, so should I try to bisect between 4.19 and 4.20-rc1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I think I figured it out, I can't use 4.19.27, but have to use 4.19. However: # git bisect good v4.19 # git bisect bad v4.20 Some good revs are not ancestors of the bad rev. git bisect cannot work properly in this case. Maybe you mistook good and bad revs? # Is it safe to continue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
How do I find the commit for the bisect good/bad command? The last good version was 4.19.27, the first bad version was 4.20.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
Just tested in 5.0 kernel, same output. Please see second dmesg.log for 5.0 output. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243448/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243433/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243434/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] [NEW] hid-sensor-hub spamming dmesg in 4.20
Public bug reported: Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+attachment/5243435/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
