Package: src:linux; Maintainer for src:linux is Debian Kernel Team <debian-kernel@lists.debian.org>;
Reported by: Mattis <e.mail.mattis@googlemail.com>
Date: Mon, 29 Apr 2019 16:33:02 UTC
Severity: important
Tags: confirmed, moreinfo
Merged with 922666
Found in versions linux/4.19.28-2, linux/4.19.16-1, linux/5.10.24-1
Done: carnil@debian.org
Bug is archived. No further changes may be made.
View this report as an mbox folder, status mbox, maintainer mbox
Report forwarded
to debian-bugs-dist@lists.debian.org, e.mail.mattis@googlemail.com, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Mon, 29 Apr 2019 16:33:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Mattis <e.mail.mattis@googlemail.com>:
New Bug report received and forwarded. Copy sent to e.mail.mattis@googlemail.com, Debian Kernel Team <debian-kernel@lists.debian.org>.
(Mon, 29 Apr 2019 16:33:04 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: src:linux Version: 4.19.28-2 Severity: important Dear Maintainer, The trackpad (and -point), both located in the dock, stop working after the laptop is resumed from hibernation, keyboard and touchscreen continue working, redocking does not fix the issue. The missing devices also don't seem to show up in lsusb and xinput. However when booting linux-image-4.19.0-2-amd64 the issue does not come up. It can someties be fixed with modprobing psmouse. ** Package-specific info: ** Version: Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/SparkyHelix--vg-root ro intel_pstate=disable fan_control=1 quiet fan_control=1 ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 17.441163] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 17.443713] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 17.459001] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 17.513389] audit: type=1400 audit(1556554205.788:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=683 comm="apparmor_parser" [ 17.513751] audit: type=1400 audit(1556554205.792:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_firefox" pid=682 comm="apparmor_parser" [ 17.515930] audit: type=1400 audit(1556554205.792:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=681 comm="apparmor_parser" [ 17.518330] audit: type=1400 audit(1556554205.796:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/mysqld-akonadi" pid=684 comm="apparmor_parser" [ 17.518336] audit: type=1400 audit(1556554205.796:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" pid=684 comm="apparmor_parser" [ 17.521576] audit: type=1400 audit(1556554205.796:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=692 comm="apparmor_parser" [ 17.523637] audit: type=1400 audit(1556554205.800:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=699 comm="apparmor_parser" [ 17.523642] audit: type=1400 audit(1556554205.800:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=699 comm="apparmor_parser" [ 17.523645] audit: type=1400 audit(1556554205.800:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=699 comm="apparmor_parser" [ 17.534168] audit: type=1400 audit(1556554205.812:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="system_tor" pid=706 comm="apparmor_parser" [ 18.267554] cdc_wdm 2-4:1.5: cdc-wdm2: USB WDM device [ 18.267896] cdc_wdm 2-4:1.8: cdc-wdm3: USB WDM device [ 18.268341] usbcore: registered new interface driver cdc_wdm [ 18.268787] cdc_acm 2-4:1.1: ttyACM0: USB ACM device [ 18.274092] cdc_acm 2-4:1.3: ttyACM1: USB ACM device [ 18.303299] cdc_ncm 2-4:1.6: MAC-Address: 02:15:e0:ec:01:00 [ 18.303600] cdc_ncm 2-4:1.6 wwan0: register 'cdc_ncm' at usb-0000:00:14.0-4, Mobile Broadband Network Device, 02:15:e0:ec:01:00 [ 18.303650] usbcore: registered new interface driver cdc_ncm [ 18.304141] cdc_acm 2-4:1.9: ttyACM2: USB ACM device [ 18.306697] usbcore: registered new interface driver cdc_acm [ 18.306699] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 18.309015] usbcore: registered new interface driver cdc_mbim [ 18.330020] cdc_ncm 2-4:1.6 wwp0s20u4i6: renamed from wwan0 [ 18.638088] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 18.651363] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 18.779903] media: Linux media interface: v0.10 [ 18.791618] videodev: Linux video capture interface: v2.00 [ 18.881909] uvcvideo: Found UVC 1.00 device Integrated Rear Camera (04ca:7027) [ 18.893678] uvcvideo 4-1.3:1.0: Entity type for entity Extension 8 was not initialized! [ 18.893681] uvcvideo 4-1.3:1.0: Entity type for entity Extension 2 was not initialized! [ 18.893684] uvcvideo 4-1.3:1.0: Entity type for entity Extension 6 was not initialized! [ 18.893686] uvcvideo 4-1.3:1.0: Entity type for entity Processing 3 was not initialized! [ 18.893688] uvcvideo 4-1.3:1.0: Entity type for entity Camera 1 was not initialized! [ 18.893782] input: Integrated Rear Camera as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.3/4-1.3:1.0/input/input16 [ 18.903353] input: Atmel Atmel maXTouch Digitizer as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.0/0003:03EB:8406.0002/input/input17 [ 18.903639] input: Atmel Atmel maXTouch Digitizer Pen as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.0/0003:03EB:8406.0002/input/input18 [ 18.903942] hid-multitouch 0003:03EB:8406.0002: input,hiddev0,hidraw0: USB HID v1.11 Device [Atmel Atmel maXTouch Digitizer] on usb-0000:00:1d.0-1.6/input0 [ 18.925956] alg: No test for fips(ansi_cprng) (fips_ansi_cprng) [ 18.952082] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 18.967409] Bluetooth: Core ver 2.22 [ 18.967429] NET: Registered protocol family 31 [ 18.967431] Bluetooth: HCI device and connection manager initialized [ 18.967535] Bluetooth: HCI socket layer initialized [ 18.967538] Bluetooth: L2CAP socket layer initialized [ 18.967545] Bluetooth: SCO socket layer initialized [ 18.979423] usbcore: registered new interface driver btusb [ 19.042958] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 19.068666] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 19.070793] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 19.070794] Bluetooth: BNEP filters: protocol multicast [ 19.070798] Bluetooth: BNEP socket layer initialized [ 19.092057] uvcvideo: Found UVC 1.00 device Integrated Camera (04ca:7028) [ 19.092130] Bluetooth: hci0: BCM: chip id 63 [ 19.093125] Bluetooth: hci0: BCM: features 0x07 [ 19.109144] Bluetooth: hci0: SparkyHelix [ 19.110041] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 [ 19.110067] bluetooth hci0: firmware: failed to load brcm/BCM20702A1-0a5c-21e6.hcd (-2) [ 19.110070] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 19.110072] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2 [ 19.110074] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e6.hcd not found [ 19.136735] uvcvideo 1-1.6:1.0: Entity type for entity Extension 4 was not initialized! [ 19.136738] uvcvideo 1-1.6:1.0: Entity type for entity Extension 3 was not initialized! [ 19.136740] uvcvideo 1-1.6:1.0: Entity type for entity Processing 2 was not initialized! [ 19.136743] uvcvideo 1-1.6:1.0: Entity type for entity Camera 1 was not initialized! [ 19.136877] input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input19 [ 19.136951] usbcore: registered new interface driver uvcvideo [ 19.136952] USB Video Class driver (1.1.1) [ 19.367260] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 19.450975] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 19.566161] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 21.108840] Bluetooth: RFCOMM TTY layer initialized [ 21.108848] Bluetooth: RFCOMM socket layer initialized [ 21.108854] Bluetooth: RFCOMM ver 1.11 [ 22.955055] vboxdrv: loading out-of-tree module taints kernel. [ 22.955330] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 22.967275] vboxdrv: Found 4 processor cores [ 22.993281] vboxdrv: TSC mode is Invariant, tentative frequency 2294782310 Hz [ 22.993283] vboxdrv: Successfully loaded version 6.0.4_Debian (interface 0x00290008) [ 23.020480] VBoxNetFlt: Successfully started. [ 23.087100] VBoxNetAdp: Successfully started. [ 23.135394] VBoxPciLinuxInit [ 23.166627] vboxpci: IOMMU not found (not registered) [ 28.014857] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 28.317140] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0 [ 28.402212] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 30.204213] fuse init (API version 7.27) [ 31.675588] wlp3s0: authenticate with c8:0e:14:77:fa:51 [ 31.690372] wlp3s0: send auth to c8:0e:14:77:fa:51 (try 1/3) [ 31.692755] wlp3s0: authenticated [ 31.693191] wlp3s0: waiting for beacon from c8:0e:14:77:fa:51 [ 31.753647] wlp3s0: associate with c8:0e:14:77:fa:51 (try 1/3) [ 31.760479] wlp3s0: RX AssocResp from c8:0e:14:77:fa:51 (capab=0x431 status=0 aid=4) [ 31.768619] wlp3s0: associated [ 32.793907] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 33.034572] kauditd_printk_skb: 28 callbacks suppressed [ 33.034574] audit: type=1400 audit(1556554221.312:40): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/local/lib/libz.so.1.2.11" pid=2154 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 33.580535] rfkill: input handler disabled ** Model information sys_vendor: LENOVO product_name: 37012NM product_version: ThinkPad Helix chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: GFET35WW (1.14 ) board_vendor: LENOVO board_name: 37012NM board_version: Win8 Pro DPK TPG ** Loaded modules: ctr ccm fuse pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm cmac bnep btusb btrtl btbcm btintel bluetooth drbg ansi_cprng hid_sensor_als hid_sensor_accel_3d hid_sensor_magn_3d hid_sensor_incl_3d hid_sensor_rotation hid_sensor_gyro_3d hid_sensor_trigger hid_sensor_iio_common industrialio_triggered_buffer kfifo_buf ecdh_generic industrialio uvcvideo videobuf2_vmalloc hid_multitouch videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media cdc_mbim cdc_ncm cdc_acm usbnet cdc_wdm mii cpufreq_conservative cpufreq_userspace cpufreq_powersave binfmt_misc msr arc4 iwldvm mei_wdt mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek irqbypass intel_cstate snd_hda_codec_generic intel_uncore intel_rapl_perf iwlwifi pcspkr joydev snd_hda_intel serio_raw snd_hda_codec wmi_bmof snd_hda_core sg snd_hwdep snd_pcm iTCO_wdt cfg80211 iTCO_vendor_support snd_timer mei_me thinkpad_acpi mei nvram tpm_tis tpm_tis_core snd tpm soundcore rng_core rfkill ac battery pcc_cpufreq evdev soc_button_array intel_smartconnect acpi_cpufreq parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher af_alg dm_crypt dm_mod sd_mod hid_sensor_custom hid_sensor_hub hid_generic usbhid hid crct10dif_pclmul i915 crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc i2c_algo_bit drm_kms_helper ahci xhci_pci libahci psmouse libata ehci_pci xhci_hcd ehci_hcd drm scsi_mod aesni_intel thermal i2c_i801 usbcore aes_x86_64 crypto_simd cryptd glue_helper lpc_ich usb_common wmi video button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Lenovo 3rd Gen Core processor DRAM Controller [17aa:2207] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx- Latency: 0 Capabilities: <access denied> Kernel driver in use: ivb_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2207] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 28 Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo 7 Series/C210 Series Chipset Family USB xHCI Host Controller [17aa:2207] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 27 Region 0: Memory at f1500000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: Lenovo 7 Series/C216 Chipset Family MEI Controller [17aa:2207] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 29 Region 0: Memory at f1515000 (64-bit, non-prefetchable) [size=16] Capabilities: <access denied> Kernel driver in use: mei_me Kernel modules: mei_me 00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller [8086:1e3d] (rev 04) (prog-if 02 [16550]) Subsystem: Lenovo 7 Series/C210 Series Chipset Family KT Controller [17aa:2207] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 19 Region 0: I/O ports at 4090 [size=8] Region 1: Memory at f151b000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: serial 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI]) Subsystem: Lenovo 7 Series/C216 Chipset Family USB Enhanced Host Controller [17aa:2207] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at f151a000 (32-bit, non-prefetchable) [size=1K] Capabilities: <access denied> Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller [8086:1e20] (rev 04) Subsystem: Lenovo 7 Series/C216 Chipset Family High Definition Audio Controller [17aa:2207] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 30 Region 0: Memory at f1510000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: f0d00000-f14fffff Prefetchable memory behind bridge: 00000000f0400000-00000000f0bfffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 17 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: f0c00000-f0cfffff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: <access denied> Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI]) Subsystem: Lenovo 7 Series/C216 Chipset Family USB Enhanced Host Controller [17aa:2207] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 23 Region 0: Memory at f1519000 (32-bit, non-prefetchable) [size=1K] Capabilities: <access denied> Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: Intel Corporation QS77 Express Chipset LPC Controller [8086:1e56] (rev 04) Subsystem: Lenovo QS77 Express Chipset LPC Controller [17aa:2207] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Capabilities: <access denied> Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [17aa:2207] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 26 Region 0: I/O ports at 4088 [size=8] Region 1: I/O ports at 409c [size=4] Region 2: I/O ports at 4080 [size=8] Region 3: I/O ports at 4098 [size=4] Region 4: I/O ports at 4060 [size=32] Region 5: Memory at f1518000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Lenovo 7 Series/C216 Chipset Family SMBus Controller [17aa:2207] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin C routed to IRQ 18 Region 0: Memory at f1514000 (64-bit, non-prefetchable) [size=256] Region 4: I/O ports at efa0 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 96) Subsystem: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:c220] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 31 Region 0: Memory at f0c00000 (64-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi ** USB devices: Bus 004 Device 004: ID 03eb:8406 Atmel Corp. Bus 004 Device 003: ID 04ca:7027 Lite-On Technology Corp. Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 04ca:7028 Lite-On Technology Corp. Bus 001 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 003: ID 8087:0a04 Intel Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0bdb:1936 Ericsson Business Mobile Networks BV Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (1000, 'testing'), (500, 'oldstable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-4-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133 ii kmod 26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-4-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-3 Versions of packages linux-image-4.19.0-4-amd64 suggests: pn debian-kernel-handbook <none> ii grub-pc 2.02+dfsg1-16 pn linux-doc-4.19 <none> Versions of packages linux-image-4.19.0-4-amd64 is related to: pn firmware-amd-graphics <none> pn firmware-atheros <none> pn firmware-bnx2 <none> pn firmware-bnx2x <none> pn firmware-brcm80211 <none> pn firmware-cavium <none> pn firmware-intel-sound <none> pn firmware-intelwimax <none> pn firmware-ipw2x00 <none> pn firmware-ivtv <none> ii firmware-iwlwifi 20190114-1 pn firmware-libertas <none> pn firmware-linux-nonfree <none> pn firmware-misc-nonfree <none> pn firmware-myricom <none> pn firmware-netxen <none> pn firmware-qlogic <none> pn firmware-realtek <none> pn firmware-samsung <none> pn firmware-siano <none> pn firmware-ti-connectivity <none> pn xen-hypervisor <none> -- no debconf information
Severity set to 'normal' from 'important'
Request was from Antoine Beaupré <anarcat@debian.org>
to 922666-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:05 GMT) (full text, mbox, link).
Marked as found in versions linux/4.19.16-1.
Request was from Antoine Beaupré <anarcat@debian.org>
to 922666-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:07 GMT) (full text, mbox, link).
Merged 922666 928189
Request was from Antoine Beaupré <anarcat@debian.org>
to 922666-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:10 GMT) (full text, mbox, link).
Severity set to 'important' from 'normal'
Request was from Antoine Beaupré <anarcat@debian.org>
to 922666-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:11 GMT) (full text, mbox, link).
Added tag(s) patch.
Request was from Antoine Beaupré <anarcat@debian.org>
to 922666-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:12 GMT) (full text, mbox, link).
Added tag(s) confirmed.
Request was from Antoine Beaupré <anarcat@debian.org>
to 922666-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:13 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Thu, 12 Sep 2019 00:33:15 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Thu, 12 Sep 2019 00:33:15 GMT) (full text, mbox, link).
Message #22 received at 928189@bugs.debian.org (full text, mbox, reply):
Control: forcemerge 922666 928189
Control: severity 922666 important
Control: tags 922666 +patch +confirmed
I also see a regression with touchpads and trackpoint on a Thinkpad E431
after upgrading from Debian stretch to buster. My research indicates
this is a kernel regression, as yet to be fixed.
This is the result of my research, as available online at:
https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep
On a Thinkpad E431, the entire mouse interface (touch, trackpoint)
freezes after sleep. Keyboard still works but not mouse until a
reboot.
There's [bug 922666][] in Debian buster, without a fix. It also says
it eventually recovers, which is not our experience. Possible dupe is
[bug 928189][].
[bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189
[bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666
There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and
which proposes the following workarounds:
* In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled`
* A .service file:
# /etc/systemd/system/touchpad-sleep.service
# restore touchpad on suspend
[Unit]
Description=Restore Touchpad on suspend
Before=sleep.target
StopWhenUnneeded=yes
[Service]
#Type=oneshot
Type=idle
RemainAfterExit=yes
ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind'
ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind'
[Install]
WantedBy=sleep.target
* "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?"
* reloading `psmouse`:
sudo modprobe -r psmouse
sudo modprobe psmouse
* "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue."
* whatever this is:
# echo 1 > /sys/devices/rmi4-00/nosleep
* "Anyone who still affected by touchpad issues after S3. Please
switch back to suspend-to-idle in BIOS if s2idle is
supported. ThinkPad Carbon 6th and Yoga 3rd do support
suspend-to-idle in BIOS->config->power menu."
[bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
There's also [bug 1442699][] in Fedora, which suggests those
workarounds:
* another module reload:
sudo rmmod i2c_hid
sudo modprobe i2c_hid
* "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing
and this issue seems to have been resolved (for me)."
* another `/proc` hack:
echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl
* "The `psmouse.synaptics_intertouch=0` workaround still works for me."
[bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699
Also related is this [libinput bug][] that's closed as "not our bug"
because they claim it's a bug in the kernel.
[libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149
There are [two][] [patches][] on the Linux kernel which apparently fix the
issue, still pending approval:
[two]: https://lkml.org/lkml/2019/2/20/700
[patches]: https://lkml.org/lkml/2019/2/20/701
Possibly related: https://lkml.org/lkml/2016/8/18/134
[5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A
[pull request][] has been merged in mainline with two other fixes on
the module./ [5.0.11][] also has fixes on the module. It's clearly a
regression from Debian stretch (kernel 4.9) since it was working fine
before.
Possibly related, [two-finger scrolling bug in Ubuntu][], which
identifies [this commit][] as the source of the regression. [Upstream
kernel bug][], still open.
[5.1rc7]: https://lkml.org/lkml/2019/4/28/270
[pull request]: https://lkml.org/lkml/2019/7/12/19
[5.0.11]: https://lkml.org/lkml/2019/5/2/287
[Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719
[this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738
[two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478
I haven't tried any of those workarounds. I hope this helps!
--
Si les triangles avaient un Dieu, ils lui donneraient trois côtés.
- Montesquieu, Lettres persanes
Merged 922666 928189
Request was from Antoine Beaupré <anarcat@debian.org>
to 928189-submit@bugs.debian.org.
(Thu, 12 Sep 2019 00:33:16 GMT) (full text, mbox, link).
Added tag(s) moreinfo.
Request was from Salvatore Bonaccorso <carnil@debian.org>
to 922666-submit@bugs.debian.org.
(Fri, 30 Apr 2021 19:09:03 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Fri, 30 Apr 2021 19:09:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <carnil@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Fri, 30 Apr 2021 19:09:05 GMT) (full text, mbox, link).
Message #31 received at 928189@bugs.debian.org (full text, mbox, reply):
Control: tags -1 + moreinfo Hi Tollef, Antoine, On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote: > Control: forcemerge 922666 928189 > Control: severity 922666 important > Control: tags 922666 +patch +confirmed > > I also see a regression with touchpads and trackpoint on a Thinkpad E431 > after upgrading from Debian stretch to buster. My research indicates > this is a kernel regression, as yet to be fixed. > > This is the result of my research, as available online at: > > https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep > > On a Thinkpad E431, the entire mouse interface (touch, trackpoint) > freezes after sleep. Keyboard still works but not mouse until a > reboot. > > There's [bug 922666][] in Debian buster, without a fix. It also says > it eventually recovers, which is not our experience. Possible dupe is > [bug 928189][]. > > [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 > [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 > > There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and > which proposes the following workarounds: > > * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled` > > * A .service file: > > # /etc/systemd/system/touchpad-sleep.service > # restore touchpad on suspend > > [Unit] > Description=Restore Touchpad on suspend > Before=sleep.target > StopWhenUnneeded=yes > > [Service] > #Type=oneshot > Type=idle > RemainAfterExit=yes > ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind' > ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind' > > [Install] > WantedBy=sleep.target > > * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?" > > * reloading `psmouse`: > > sudo modprobe -r psmouse > sudo modprobe psmouse > > * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue." > > * whatever this is: > > # echo 1 > /sys/devices/rmi4-00/nosleep > > * "Anyone who still affected by touchpad issues after S3. Please > switch back to suspend-to-idle in BIOS if s2idle is > supported. ThinkPad Carbon 6th and Yoga 3rd do support > suspend-to-idle in BIOS->config->power menu." > > [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 > > There's also [bug 1442699][] in Fedora, which suggests those > workarounds: > > * another module reload: > > sudo rmmod i2c_hid > sudo modprobe i2c_hid > > * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing > and this issue seems to have been resolved (for me)." > > * another `/proc` hack: > > echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl > > * "The `psmouse.synaptics_intertouch=0` workaround still works for me." > > [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699 > > Also related is this [libinput bug][] that's closed as "not our bug" > because they claim it's a bug in the kernel. > > [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149 > > There are [two][] [patches][] on the Linux kernel which apparently fix the > issue, still pending approval: > > [two]: https://lkml.org/lkml/2019/2/20/700 > [patches]: https://lkml.org/lkml/2019/2/20/701 > > Possibly related: https://lkml.org/lkml/2016/8/18/134 > > [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A > [pull request][] has been merged in mainline with two other fixes on > the module./ [5.0.11][] also has fixes on the module. It's clearly a > regression from Debian stretch (kernel 4.9) since it was working fine > before. > > Possibly related, [two-finger scrolling bug in Ubuntu][], which > identifies [this commit][] as the source of the regression. [Upstream > kernel bug][], still open. > > [5.1rc7]: https://lkml.org/lkml/2019/4/28/270 > [pull request]: https://lkml.org/lkml/2019/7/12/19 > [5.0.11]: https://lkml.org/lkml/2019/5/2/287 > [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719 > [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738 > [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478 > > I haven't tried any of those workarounds. I hope this helps! Can you confirm if this issue is still present with a recent kernel? Regards, Salvatore
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Fri, 30 Apr 2021 19:39:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Tollef Fog Heen <tfheen@err.no>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Fri, 30 Apr 2021 19:39:04 GMT) (full text, mbox, link).
Message #36 received at 928189@bugs.debian.org (full text, mbox, reply):
]] Salvatore Bonaccorso > Can you confirm if this issue is still present with a recent kernel? I haven't seen it for quite some time on my Buster machine, so from my point of view, it can be closed. Regards, -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Fri, 30 Apr 2021 23:39:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Fri, 30 Apr 2021 23:39:04 GMT) (full text, mbox, link).
Message #41 received at 928189@bugs.debian.org (full text, mbox, reply):
On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
>
> Hi Tollef, Antoine,
>
> On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote:
>> Control: forcemerge 922666 928189
>> Control: severity 922666 important
>> Control: tags 922666 +patch +confirmed
>>
>> I also see a regression with touchpads and trackpoint on a Thinkpad E431
>> after upgrading from Debian stretch to buster. My research indicates
>> this is a kernel regression, as yet to be fixed.
>>
>> This is the result of my research, as available online at:
>>
>> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep
>>
>> On a Thinkpad E431, the entire mouse interface (touch, trackpoint)
>> freezes after sleep. Keyboard still works but not mouse until a
>> reboot.
>>
>> There's [bug 922666][] in Debian buster, without a fix. It also says
>> it eventually recovers, which is not our experience. Possible dupe is
>> [bug 928189][].
>>
>> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189
>> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666
>>
>> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and
>> which proposes the following workarounds:
>>
>> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled`
>>
>> * A .service file:
>>
>> # /etc/systemd/system/touchpad-sleep.service
>> # restore touchpad on suspend
>>
>> [Unit]
>> Description=Restore Touchpad on suspend
>> Before=sleep.target
>> StopWhenUnneeded=yes
>>
>> [Service]
>> #Type=oneshot
>> Type=idle
>> RemainAfterExit=yes
>> ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind'
>> ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind'
>>
>> [Install]
>> WantedBy=sleep.target
>>
>> * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?"
>>
>> * reloading `psmouse`:
>>
>> sudo modprobe -r psmouse
>> sudo modprobe psmouse
>>
>> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue."
>>
>> * whatever this is:
>>
>> # echo 1 > /sys/devices/rmi4-00/nosleep
>>
>> * "Anyone who still affected by touchpad issues after S3. Please
>> switch back to suspend-to-idle in BIOS if s2idle is
>> supported. ThinkPad Carbon 6th and Yoga 3rd do support
>> suspend-to-idle in BIOS->config->power menu."
>>
>> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
>>
>> There's also [bug 1442699][] in Fedora, which suggests those
>> workarounds:
>>
>> * another module reload:
>>
>> sudo rmmod i2c_hid
>> sudo modprobe i2c_hid
>>
>> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing
>> and this issue seems to have been resolved (for me)."
>>
>> * another `/proc` hack:
>>
>> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl
>>
>> * "The `psmouse.synaptics_intertouch=0` workaround still works for me."
>>
>> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699
>>
>> Also related is this [libinput bug][] that's closed as "not our bug"
>> because they claim it's a bug in the kernel.
>>
>> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149
>>
>> There are [two][] [patches][] on the Linux kernel which apparently fix the
>> issue, still pending approval:
>>
>> [two]: https://lkml.org/lkml/2019/2/20/700
>> [patches]: https://lkml.org/lkml/2019/2/20/701
>>
>> Possibly related: https://lkml.org/lkml/2016/8/18/134
>>
>> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A
>> [pull request][] has been merged in mainline with two other fixes on
>> the module./ [5.0.11][] also has fixes on the module. It's clearly a
>> regression from Debian stretch (kernel 4.9) since it was working fine
>> before.
>>
>> Possibly related, [two-finger scrolling bug in Ubuntu][], which
>> identifies [this commit][] as the source of the regression. [Upstream
>> kernel bug][], still open.
>>
>> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270
>> [pull request]: https://lkml.org/lkml/2019/7/12/19
>> [5.0.11]: https://lkml.org/lkml/2019/5/2/287
>> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719
>> [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738
>> [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478
>>
>> I haven't tried any of those workarounds. I hope this helps!
>
> Can you confirm if this issue is still present with a recent kernel?
e.g. buster-backports?
--
The flesh you so fancifully fry
Is not succulent, tasty or kind
It's death for no reason
And death for no reason is murder
- Morrissey
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Sat, 01 May 2021 06:03:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <carnil@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Sat, 01 May 2021 06:03:04 GMT) (full text, mbox, link).
Message #46 received at 928189@bugs.debian.org (full text, mbox, reply):
Hi Antoine On Fri, Apr 30, 2021 at 07:34:04PM -0400, Antoine Beaupré wrote: > On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote: > > Control: tags -1 + moreinfo > > > > Hi Tollef, Antoine, > > > > On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote: > >> Control: forcemerge 922666 928189 > >> Control: severity 922666 important > >> Control: tags 922666 +patch +confirmed > >> > >> I also see a regression with touchpads and trackpoint on a Thinkpad E431 > >> after upgrading from Debian stretch to buster. My research indicates > >> this is a kernel regression, as yet to be fixed. > >> > >> This is the result of my research, as available online at: > >> > >> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep > >> > >> On a Thinkpad E431, the entire mouse interface (touch, trackpoint) > >> freezes after sleep. Keyboard still works but not mouse until a > >> reboot. > >> > >> There's [bug 922666][] in Debian buster, without a fix. It also says > >> it eventually recovers, which is not our experience. Possible dupe is > >> [bug 928189][]. > >> > >> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 > >> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 > >> > >> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and > >> which proposes the following workarounds: > >> > >> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled` > >> > >> * A .service file: > >> > >> # /etc/systemd/system/touchpad-sleep.service > >> # restore touchpad on suspend > >> > >> [Unit] > >> Description=Restore Touchpad on suspend > >> Before=sleep.target > >> StopWhenUnneeded=yes > >> > >> [Service] > >> #Type=oneshot > >> Type=idle > >> RemainAfterExit=yes > >> ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind' > >> ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind' > >> > >> [Install] > >> WantedBy=sleep.target > >> > >> * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?" > >> > >> * reloading `psmouse`: > >> > >> sudo modprobe -r psmouse > >> sudo modprobe psmouse > >> > >> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue." > >> > >> * whatever this is: > >> > >> # echo 1 > /sys/devices/rmi4-00/nosleep > >> > >> * "Anyone who still affected by touchpad issues after S3. Please > >> switch back to suspend-to-idle in BIOS if s2idle is > >> supported. ThinkPad Carbon 6th and Yoga 3rd do support > >> suspend-to-idle in BIOS->config->power menu." > >> > >> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 > >> > >> There's also [bug 1442699][] in Fedora, which suggests those > >> workarounds: > >> > >> * another module reload: > >> > >> sudo rmmod i2c_hid > >> sudo modprobe i2c_hid > >> > >> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing > >> and this issue seems to have been resolved (for me)." > >> > >> * another `/proc` hack: > >> > >> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl > >> > >> * "The `psmouse.synaptics_intertouch=0` workaround still works for me." > >> > >> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699 > >> > >> Also related is this [libinput bug][] that's closed as "not our bug" > >> because they claim it's a bug in the kernel. > >> > >> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149 > >> > >> There are [two][] [patches][] on the Linux kernel which apparently fix the > >> issue, still pending approval: > >> > >> [two]: https://lkml.org/lkml/2019/2/20/700 > >> [patches]: https://lkml.org/lkml/2019/2/20/701 > >> > >> Possibly related: https://lkml.org/lkml/2016/8/18/134 > >> > >> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A > >> [pull request][] has been merged in mainline with two other fixes on > >> the module./ [5.0.11][] also has fixes on the module. It's clearly a > >> regression from Debian stretch (kernel 4.9) since it was working fine > >> before. > >> > >> Possibly related, [two-finger scrolling bug in Ubuntu][], which > >> identifies [this commit][] as the source of the regression. [Upstream > >> kernel bug][], still open. > >> > >> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270 > >> [pull request]: https://lkml.org/lkml/2019/7/12/19 > >> [5.0.11]: https://lkml.org/lkml/2019/5/2/287 > >> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719 > >> [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738 > >> [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478 > >> > >> I haven't tried any of those workarounds. I hope this helps! > > > > Can you confirm if this issue is still present with a recent kernel? > > e.g. buster-backports? Yes exactly either buster-backports, unsteable or mainline. Initial goal on asking you back is that the issue as reported for some kernels way back, try to find out if the issue is still present or if we can close the bug otherwise as maintenance. Regards, Salvatore
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Mon, 03 May 2021 00:24:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Mon, 03 May 2021 00:24:04 GMT) (full text, mbox, link).
Message #51 received at 928189@bugs.debian.org (full text, mbox, reply):
On 2021-05-01 07:59:01, Salvatore Bonaccorso wrote:
> Hi Antoine
>
> On Fri, Apr 30, 2021 at 07:34:04PM -0400, Antoine Beaupré wrote:
>> On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote:
>> > Control: tags -1 + moreinfo
>> >
>> > Hi Tollef, Antoine,
>> >
>> > On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote:
>> >> Control: forcemerge 922666 928189
>> >> Control: severity 922666 important
>> >> Control: tags 922666 +patch +confirmed
>> >>
>> >> I also see a regression with touchpads and trackpoint on a Thinkpad E431
>> >> after upgrading from Debian stretch to buster. My research indicates
>> >> this is a kernel regression, as yet to be fixed.
>> >>
>> >> This is the result of my research, as available online at:
>> >>
>> >> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep
>> >>
>> >> On a Thinkpad E431, the entire mouse interface (touch, trackpoint)
>> >> freezes after sleep. Keyboard still works but not mouse until a
>> >> reboot.
>> >>
>> >> There's [bug 922666][] in Debian buster, without a fix. It also says
>> >> it eventually recovers, which is not our experience. Possible dupe is
>> >> [bug 928189][].
>> >>
>> >> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189
>> >> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666
>> >>
>> >> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and
>> >> which proposes the following workarounds:
>> >>
>> >> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled`
>> >>
>> >> * A .service file:
>> >>
>> >> # /etc/systemd/system/touchpad-sleep.service
>> >> # restore touchpad on suspend
>> >>
>> >> [Unit]
>> >> Description=Restore Touchpad on suspend
>> >> Before=sleep.target
>> >> StopWhenUnneeded=yes
>> >>
>> >> [Service]
>> >> #Type=oneshot
>> >> Type=idle
>> >> RemainAfterExit=yes
>> >> ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind'
>> >> ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind'
>> >>
>> >> [Install]
>> >> WantedBy=sleep.target
>> >>
>> >> * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?"
>> >>
>> >> * reloading `psmouse`:
>> >>
>> >> sudo modprobe -r psmouse
>> >> sudo modprobe psmouse
>> >>
>> >> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue."
>> >>
>> >> * whatever this is:
>> >>
>> >> # echo 1 > /sys/devices/rmi4-00/nosleep
>> >>
>> >> * "Anyone who still affected by touchpad issues after S3. Please
>> >> switch back to suspend-to-idle in BIOS if s2idle is
>> >> supported. ThinkPad Carbon 6th and Yoga 3rd do support
>> >> suspend-to-idle in BIOS->config->power menu."
>> >>
>> >> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
>> >>
>> >> There's also [bug 1442699][] in Fedora, which suggests those
>> >> workarounds:
>> >>
>> >> * another module reload:
>> >>
>> >> sudo rmmod i2c_hid
>> >> sudo modprobe i2c_hid
>> >>
>> >> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing
>> >> and this issue seems to have been resolved (for me)."
>> >>
>> >> * another `/proc` hack:
>> >>
>> >> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl
>> >>
>> >> * "The `psmouse.synaptics_intertouch=0` workaround still works for me."
>> >>
>> >> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699
>> >>
>> >> Also related is this [libinput bug][] that's closed as "not our bug"
>> >> because they claim it's a bug in the kernel.
>> >>
>> >> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149
>> >>
>> >> There are [two][] [patches][] on the Linux kernel which apparently fix the
>> >> issue, still pending approval:
>> >>
>> >> [two]: https://lkml.org/lkml/2019/2/20/700
>> >> [patches]: https://lkml.org/lkml/2019/2/20/701
>> >>
>> >> Possibly related: https://lkml.org/lkml/2016/8/18/134
>> >>
>> >> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A
>> >> [pull request][] has been merged in mainline with two other fixes on
>> >> the module./ [5.0.11][] also has fixes on the module. It's clearly a
>> >> regression from Debian stretch (kernel 4.9) since it was working fine
>> >> before.
>> >>
>> >> Possibly related, [two-finger scrolling bug in Ubuntu][], which
>> >> identifies [this commit][] as the source of the regression. [Upstream
>> >> kernel bug][], still open.
>> >>
>> >> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270
>> >> [pull request]: https://lkml.org/lkml/2019/7/12/19
>> >> [5.0.11]: https://lkml.org/lkml/2019/5/2/287
>> >> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719
>> >> [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738
>> >> [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478
>> >>
>> >> I haven't tried any of those workarounds. I hope this helps!
>> >
>> > Can you confirm if this issue is still present with a recent kernel?
>>
>> e.g. buster-backports?
>
> Yes exactly either buster-backports, unsteable or mainline.
>
> Initial goal on asking you back is that the issue as reported for some
> kernels way back, try to find out if the issue is still present or if
> we can close the bug otherwise as maintenance.
Understood.
The situation, right now, is this:
1. the user of this machine has been running the 5.7.10 kernel since
around August 2020, from buster-backports
2. they indeed reported the bug not happening for "a month or two" but,
in their opinion it was "still happening" intermittently, and they
expressed surprise at the idea that the bug was fixed
3. i therefore completed the last buster point upgrade and installed the
5.10.24 Linux kernel, again from backports
4. i then rebooted the machine in the new kernel, logged in as said
user, then closed the lid, waited a few seconds, and opened the lid
back up
The mouse froze.
I rebooted (because that you can still do, of course, with
control-alt-delete), and again reproduced it.
So, from my perspective, this bug is definitely not fixed, even with the
latest backported kernel, in Debian buster.
[I'll note that, interestingly, I'm not actually sure the machine goes to
sleep. The red light on the "i" of the "Thinkpad" lid logo doesn't
actually start flashing slowly like it typically does during sleep. But
from a user perspective, that doesn't matter: it's "close the lid,
computer crashes" kind of experience, which is a pretty nasty regression
from stretch.]
a.
Marked as found in versions linux/5.10.24-1.
Request was from Salvatore Bonaccorso <carnil@debian.org>
to 922666-submit@bugs.debian.org.
(Mon, 03 May 2021 05:39:06 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Mon, 03 May 2021 05:39:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <carnil@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Mon, 03 May 2021 05:39:08 GMT) (full text, mbox, link).
Message #58 received at 928189@bugs.debian.org (full text, mbox, reply):
Control: found -1 5.10.24-1 Hi Antoine, On Sun, May 02, 2021 at 08:22:07PM -0400, Antoine Beaupré wrote: > On 2021-05-01 07:59:01, Salvatore Bonaccorso wrote: > > Hi Antoine > > > > On Fri, Apr 30, 2021 at 07:34:04PM -0400, Antoine Beaupré wrote: > >> On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote: > >> > Control: tags -1 + moreinfo > >> > > >> > Hi Tollef, Antoine, > >> > > >> > On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote: > >> >> Control: forcemerge 922666 928189 > >> >> Control: severity 922666 important > >> >> Control: tags 922666 +patch +confirmed > >> >> > >> >> I also see a regression with touchpads and trackpoint on a Thinkpad E431 > >> >> after upgrading from Debian stretch to buster. My research indicates > >> >> this is a kernel regression, as yet to be fixed. > >> >> > >> >> This is the result of my research, as available online at: > >> >> > >> >> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep > >> >> > >> >> On a Thinkpad E431, the entire mouse interface (touch, trackpoint) > >> >> freezes after sleep. Keyboard still works but not mouse until a > >> >> reboot. > >> >> > >> >> There's [bug 922666][] in Debian buster, without a fix. It also says > >> >> it eventually recovers, which is not our experience. Possible dupe is > >> >> [bug 928189][]. > >> >> > >> >> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189 > >> >> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666 > >> >> > >> >> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and > >> >> which proposes the following workarounds: > >> >> > >> >> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled` > >> >> > >> >> * A .service file: > >> >> > >> >> # /etc/systemd/system/touchpad-sleep.service > >> >> # restore touchpad on suspend > >> >> > >> >> [Unit] > >> >> Description=Restore Touchpad on suspend > >> >> Before=sleep.target > >> >> StopWhenUnneeded=yes > >> >> > >> >> [Service] > >> >> #Type=oneshot > >> >> Type=idle > >> >> RemainAfterExit=yes > >> >> ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind' > >> >> ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind' > >> >> > >> >> [Install] > >> >> WantedBy=sleep.target > >> >> > >> >> * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?" > >> >> > >> >> * reloading `psmouse`: > >> >> > >> >> sudo modprobe -r psmouse > >> >> sudo modprobe psmouse > >> >> > >> >> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue." > >> >> > >> >> * whatever this is: > >> >> > >> >> # echo 1 > /sys/devices/rmi4-00/nosleep > >> >> > >> >> * "Anyone who still affected by touchpad issues after S3. Please > >> >> switch back to suspend-to-idle in BIOS if s2idle is > >> >> supported. ThinkPad Carbon 6th and Yoga 3rd do support > >> >> suspend-to-idle in BIOS->config->power menu." > >> >> > >> >> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 > >> >> > >> >> There's also [bug 1442699][] in Fedora, which suggests those > >> >> workarounds: > >> >> > >> >> * another module reload: > >> >> > >> >> sudo rmmod i2c_hid > >> >> sudo modprobe i2c_hid > >> >> > >> >> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing > >> >> and this issue seems to have been resolved (for me)." > >> >> > >> >> * another `/proc` hack: > >> >> > >> >> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl > >> >> > >> >> * "The `psmouse.synaptics_intertouch=0` workaround still works for me." > >> >> > >> >> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699 > >> >> > >> >> Also related is this [libinput bug][] that's closed as "not our bug" > >> >> because they claim it's a bug in the kernel. > >> >> > >> >> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149 > >> >> > >> >> There are [two][] [patches][] on the Linux kernel which apparently fix the > >> >> issue, still pending approval: > >> >> > >> >> [two]: https://lkml.org/lkml/2019/2/20/700 > >> >> [patches]: https://lkml.org/lkml/2019/2/20/701 > >> >> > >> >> Possibly related: https://lkml.org/lkml/2016/8/18/134 > >> >> > >> >> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A > >> >> [pull request][] has been merged in mainline with two other fixes on > >> >> the module./ [5.0.11][] also has fixes on the module. It's clearly a > >> >> regression from Debian stretch (kernel 4.9) since it was working fine > >> >> before. > >> >> > >> >> Possibly related, [two-finger scrolling bug in Ubuntu][], which > >> >> identifies [this commit][] as the source of the regression. [Upstream > >> >> kernel bug][], still open. > >> >> > >> >> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270 > >> >> [pull request]: https://lkml.org/lkml/2019/7/12/19 > >> >> [5.0.11]: https://lkml.org/lkml/2019/5/2/287 > >> >> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719 > >> >> [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738 > >> >> [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478 > >> >> > >> >> I haven't tried any of those workarounds. I hope this helps! > >> > > >> > Can you confirm if this issue is still present with a recent kernel? > >> > >> e.g. buster-backports? > > > > Yes exactly either buster-backports, unsteable or mainline. > > > > Initial goal on asking you back is that the issue as reported for some > > kernels way back, try to find out if the issue is still present or if > > we can close the bug otherwise as maintenance. > > Understood. > > The situation, right now, is this: > > 1. the user of this machine has been running the 5.7.10 kernel since > around August 2020, from buster-backports > > 2. they indeed reported the bug not happening for "a month or two" but, > in their opinion it was "still happening" intermittently, and they > expressed surprise at the idea that the bug was fixed > > 3. i therefore completed the last buster point upgrade and installed the > 5.10.24 Linux kernel, again from backports > > 4. i then rebooted the machine in the new kernel, logged in as said > user, then closed the lid, waited a few seconds, and opened the lid > back up > > The mouse froze. > > I rebooted (because that you can still do, of course, with > control-alt-delete), and again reproduced it. > > So, from my perspective, this bug is definitely not fixed, even with the > latest backported kernel, in Debian buster. > > [I'll note that, interestingly, I'm not actually sure the machine goes to > sleep. The red light on the "i" of the "Thinkpad" lid logo doesn't > actually start flashing slowly like it typically does during sleep. But > from a user perspective, that doesn't matter: it's "close the lid, > computer crashes" kind of experience, which is a pretty nasty regression > from stretch.] Thanks for reporting back, much appreciated you took time again to recheck. So I suspect the problem from Tollef and yours might be different. Do logs (dmesg, X logs) give any helpful hints? Might it be possible for you to (re-)bring the issue to upstream? Regards, Salvatore
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Mon, 03 May 2021 15:00:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Mon, 03 May 2021 15:00:04 GMT) (full text, mbox, link).
Message #63 received at 928189@bugs.debian.org (full text, mbox, reply):
On 2021-05-03 07:37:42, Salvatore Bonaccorso wrote:
> Control: found -1 5.10.24-1
>
> Hi Antoine,
>
> On Sun, May 02, 2021 at 08:22:07PM -0400, Antoine Beaupré wrote:
>> On 2021-05-01 07:59:01, Salvatore Bonaccorso wrote:
>> > Hi Antoine
>> >
>> > On Fri, Apr 30, 2021 at 07:34:04PM -0400, Antoine Beaupré wrote:
>> >> On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote:
>> >> > Control: tags -1 + moreinfo
>> >> >
>> >> > Hi Tollef, Antoine,
>> >> >
>> >> > On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote:
>> >> >> Control: forcemerge 922666 928189
>> >> >> Control: severity 922666 important
>> >> >> Control: tags 922666 +patch +confirmed
>> >> >>
>> >> >> I also see a regression with touchpads and trackpoint on a Thinkpad E431
>> >> >> after upgrading from Debian stretch to buster. My research indicates
>> >> >> this is a kernel regression, as yet to be fixed.
>> >> >>
>> >> >> This is the result of my research, as available online at:
>> >> >>
>> >> >> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep
>> >> >>
>> >> >> On a Thinkpad E431, the entire mouse interface (touch, trackpoint)
>> >> >> freezes after sleep. Keyboard still works but not mouse until a
>> >> >> reboot.
>> >> >>
>> >> >> There's [bug 922666][] in Debian buster, without a fix. It also says
>> >> >> it eventually recovers, which is not our experience. Possible dupe is
>> >> >> [bug 928189][].
>> >> >>
>> >> >> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189
>> >> >> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666
>> >> >>
>> >> >> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and
>> >> >> which proposes the following workarounds:
>> >> >>
>> >> >> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled`
>> >> >>
>> >> >> * A .service file:
>> >> >>
>> >> >> # /etc/systemd/system/touchpad-sleep.service
>> >> >> # restore touchpad on suspend
>> >> >>
>> >> >> [Unit]
>> >> >> Description=Restore Touchpad on suspend
>> >> >> Before=sleep.target
>> >> >> StopWhenUnneeded=yes
>> >> >>
>> >> >> [Service]
>> >> >> #Type=oneshot
>> >> >> Type=idle
>> >> >> RemainAfterExit=yes
>> >> >> ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind'
>> >> >> ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind'
>> >> >>
>> >> >> [Install]
>> >> >> WantedBy=sleep.target
>> >> >>
>> >> >> * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?"
>> >> >>
>> >> >> * reloading `psmouse`:
>> >> >>
>> >> >> sudo modprobe -r psmouse
>> >> >> sudo modprobe psmouse
>> >> >>
>> >> >> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue."
>> >> >>
>> >> >> * whatever this is:
>> >> >>
>> >> >> # echo 1 > /sys/devices/rmi4-00/nosleep
>> >> >>
>> >> >> * "Anyone who still affected by touchpad issues after S3. Please
>> >> >> switch back to suspend-to-idle in BIOS if s2idle is
>> >> >> supported. ThinkPad Carbon 6th and Yoga 3rd do support
>> >> >> suspend-to-idle in BIOS->config->power menu."
>> >> >>
>> >> >> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
>> >> >>
>> >> >> There's also [bug 1442699][] in Fedora, which suggests those
>> >> >> workarounds:
>> >> >>
>> >> >> * another module reload:
>> >> >>
>> >> >> sudo rmmod i2c_hid
>> >> >> sudo modprobe i2c_hid
>> >> >>
>> >> >> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing
>> >> >> and this issue seems to have been resolved (for me)."
>> >> >>
>> >> >> * another `/proc` hack:
>> >> >>
>> >> >> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl
>> >> >>
>> >> >> * "The `psmouse.synaptics_intertouch=0` workaround still works for me."
>> >> >>
>> >> >> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699
>> >> >>
>> >> >> Also related is this [libinput bug][] that's closed as "not our bug"
>> >> >> because they claim it's a bug in the kernel.
>> >> >>
>> >> >> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149
>> >> >>
>> >> >> There are [two][] [patches][] on the Linux kernel which apparently fix the
>> >> >> issue, still pending approval:
>> >> >>
>> >> >> [two]: https://lkml.org/lkml/2019/2/20/700
>> >> >> [patches]: https://lkml.org/lkml/2019/2/20/701
>> >> >>
>> >> >> Possibly related: https://lkml.org/lkml/2016/8/18/134
>> >> >>
>> >> >> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A
>> >> >> [pull request][] has been merged in mainline with two other fixes on
>> >> >> the module./ [5.0.11][] also has fixes on the module. It's clearly a
>> >> >> regression from Debian stretch (kernel 4.9) since it was working fine
>> >> >> before.
>> >> >>
>> >> >> Possibly related, [two-finger scrolling bug in Ubuntu][], which
>> >> >> identifies [this commit][] as the source of the regression. [Upstream
>> >> >> kernel bug][], still open.
>> >> >>
>> >> >> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270
>> >> >> [pull request]: https://lkml.org/lkml/2019/7/12/19
>> >> >> [5.0.11]: https://lkml.org/lkml/2019/5/2/287
>> >> >> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719
>> >> >> [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738
>> >> >> [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478
>> >> >>
>> >> >> I haven't tried any of those workarounds. I hope this helps!
>> >> >
>> >> > Can you confirm if this issue is still present with a recent kernel?
>> >>
>> >> e.g. buster-backports?
>> >
>> > Yes exactly either buster-backports, unsteable or mainline.
>> >
>> > Initial goal on asking you back is that the issue as reported for some
>> > kernels way back, try to find out if the issue is still present or if
>> > we can close the bug otherwise as maintenance.
>>
>> Understood.
>>
>> The situation, right now, is this:
>>
>> 1. the user of this machine has been running the 5.7.10 kernel since
>> around August 2020, from buster-backports
>>
>> 2. they indeed reported the bug not happening for "a month or two" but,
>> in their opinion it was "still happening" intermittently, and they
>> expressed surprise at the idea that the bug was fixed
>>
>> 3. i therefore completed the last buster point upgrade and installed the
>> 5.10.24 Linux kernel, again from backports
>>
>> 4. i then rebooted the machine in the new kernel, logged in as said
>> user, then closed the lid, waited a few seconds, and opened the lid
>> back up
>>
>> The mouse froze.
>>
>> I rebooted (because that you can still do, of course, with
>> control-alt-delete), and again reproduced it.
>>
>> So, from my perspective, this bug is definitely not fixed, even with the
>> latest backported kernel, in Debian buster.
>>
>> [I'll note that, interestingly, I'm not actually sure the machine goes to
>> sleep. The red light on the "i" of the "Thinkpad" lid logo doesn't
>> actually start flashing slowly like it typically does during sleep. But
>> from a user perspective, that doesn't matter: it's "close the lid,
>> computer crashes" kind of experience, which is a pretty nasty regression
>> from stretch.]
>
> Thanks for reporting back, much appreciated you took time again to
> recheck. So I suspect the problem from Tollef and yours might be
> different.
>
> Do logs (dmesg, X logs) give any helpful hints?
I'll check again.
> Might it be possible for you to (re-)bring the issue to upstream?
Problem here is: which upstream? I found about half a dozen projects
that could be at fault here... And if it's "Linux kernel", how exactly
do I bring this up? Their bugzilla?
This is a tough nut to crack...
a.
--
Imagination is more important than knowledge.
Knowledge is limited.
Imagination encircles the world.
- Albert Einstein
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Tue, 04 May 2021 00:30:06 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Tue, 04 May 2021 00:30:06 GMT) (full text, mbox, link).
Message #68 received at 928189@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On 2021-05-03 07:37:42, Salvatore Bonaccorso wrote:
> Control: found -1 5.10.24-1
>
> Hi Antoine,
>
> On Sun, May 02, 2021 at 08:22:07PM -0400, Antoine Beaupré wrote:
>> On 2021-05-01 07:59:01, Salvatore Bonaccorso wrote:
>> > Hi Antoine
>> >
>> > On Fri, Apr 30, 2021 at 07:34:04PM -0400, Antoine Beaupré wrote:
>> >> On 2021-04-30 21:04:29, Salvatore Bonaccorso wrote:
>> >> > Control: tags -1 + moreinfo
>> >> >
>> >> > Hi Tollef, Antoine,
>> >> >
>> >> > On Wed, Sep 11, 2019 at 08:20:22PM -0400, Antoine Beaupré wrote:
>> >> >> Control: forcemerge 922666 928189
>> >> >> Control: severity 922666 important
>> >> >> Control: tags 922666 +patch +confirmed
>> >> >>
>> >> >> I also see a regression with touchpads and trackpoint on a Thinkpad E431
>> >> >> after upgrading from Debian stretch to buster. My research indicates
>> >> >> this is a kernel regression, as yet to be fixed.
>> >> >>
>> >> >> This is the result of my research, as available online at:
>> >> >>
>> >> >> https://anarc.at/services/upgrades/buster/#touchpad-trackpoint-freeze-after-sleep
>> >> >>
>> >> >> On a Thinkpad E431, the entire mouse interface (touch, trackpoint)
>> >> >> freezes after sleep. Keyboard still works but not mouse until a
>> >> >> reboot.
>> >> >>
>> >> >> There's [bug 922666][] in Debian buster, without a fix. It also says
>> >> >> it eventually recovers, which is not our experience. Possible dupe is
>> >> >> [bug 928189][].
>> >> >>
>> >> >> [bug 928189]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928189
>> >> >> [bug 922666]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922666
>> >> >>
>> >> >> There's also [bug 1791427][] in Ubuntu 18.04 that seems related, and
>> >> >> which proposes the following workarounds:
>> >> >>
>> >> >> * In gsettings: `org.gnome.desktop.peripherals.touchpad click-method disabled`
>> >> >>
>> >> >> * A .service file:
>> >> >>
>> >> >> # /etc/systemd/system/touchpad-sleep.service
>> >> >> # restore touchpad on suspend
>> >> >>
>> >> >> [Unit]
>> >> >> Description=Restore Touchpad on suspend
>> >> >> Before=sleep.target
>> >> >> StopWhenUnneeded=yes
>> >> >>
>> >> >> [Service]
>> >> >> #Type=oneshot
>> >> >> Type=idle
>> >> >> RemainAfterExit=yes
>> >> >> ExecStart=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/unbind'
>> >> >> ExecStop=/bin/bash -c 'echo "0000:00:1f.4" > /sys/bus/pci/drivers/i801_smbus/bind'
>> >> >>
>> >> >> [Install]
>> >> >> WantedBy=sleep.target
>> >> >>
>> >> >> * "Maybe try xserver-xorg-input-evdev instead of xserver-xorg-input-libinput?"
>> >> >>
>> >> >> * reloading `psmouse`:
>> >> >>
>> >> >> sudo modprobe -r psmouse
>> >> >> sudo modprobe psmouse
>> >> >>
>> >> >> * "`modprobe i2c-i801` after removing it from the `blacklist.conf` seems to solve the issue."
>> >> >>
>> >> >> * whatever this is:
>> >> >>
>> >> >> # echo 1 > /sys/devices/rmi4-00/nosleep
>> >> >>
>> >> >> * "Anyone who still affected by touchpad issues after S3. Please
>> >> >> switch back to suspend-to-idle in BIOS if s2idle is
>> >> >> supported. ThinkPad Carbon 6th and Yoga 3rd do support
>> >> >> suspend-to-idle in BIOS->config->power menu."
>> >> >>
>> >> >> [bug 1791427]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
>> >> >>
>> >> >> There's also [bug 1442699][] in Fedora, which suggests those
>> >> >> workarounds:
>> >> >>
>> >> >> * another module reload:
>> >> >>
>> >> >> sudo rmmod i2c_hid
>> >> >> sudo modprobe i2c_hid
>> >> >>
>> >> >> * "Just updated to kernel-4.12.5-300.fc26.x86_64 in updates-testing
>> >> >> and this issue seems to have been resolved (for me)."
>> >> >>
>> >> >> * another `/proc` hack:
>> >> >>
>> >> >> echo -n "reconnect" > /sys/bus/serio/devices/serio1/drvctl
>> >> >>
>> >> >> * "The `psmouse.synaptics_intertouch=0` workaround still works for me."
>> >> >>
>> >> >> [bug 1442699]: https://bugzilla.redhat.com/show_bug.cgi?id=1442699
>> >> >>
>> >> >> Also related is this [libinput bug][] that's closed as "not our bug"
>> >> >> because they claim it's a bug in the kernel.
>> >> >>
>> >> >> [libinput bug]: https://bugs.freedesktop.org/show_bug.cgi?id=103149
>> >> >>
>> >> >> There are [two][] [patches][] on the Linux kernel which apparently fix the
>> >> >> issue, still pending approval:
>> >> >>
>> >> >> [two]: https://lkml.org/lkml/2019/2/20/700
>> >> >> [patches]: https://lkml.org/lkml/2019/2/20/701
>> >> >>
>> >> >> Possibly related: https://lkml.org/lkml/2016/8/18/134
>> >> >>
>> >> >> [5.1rc7][] shipped two fixes against the `synaptics-rmi4` module. A
>> >> >> [pull request][] has been merged in mainline with two other fixes on
>> >> >> the module./ [5.0.11][] also has fixes on the module. It's clearly a
>> >> >> regression from Debian stretch (kernel 4.9) since it was working fine
>> >> >> before.
>> >> >>
>> >> >> Possibly related, [two-finger scrolling bug in Ubuntu][], which
>> >> >> identifies [this commit][] as the source of the regression. [Upstream
>> >> >> kernel bug][], still open.
>> >> >>
>> >> >> [5.1rc7]: https://lkml.org/lkml/2019/4/28/270
>> >> >> [pull request]: https://lkml.org/lkml/2019/7/12/19
>> >> >> [5.0.11]: https://lkml.org/lkml/2019/5/2/287
>> >> >> [Upstream kernel bug]: https://bugzilla.kernel.org/show_bug.cgi?id=196719
>> >> >> [this commit]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e839ffab028981ac77f650faf8c84f16e1719738
>> >> >> [two-finger scrolling bug in Ubuntu]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478
>> >> >>
>> >> >> I haven't tried any of those workarounds. I hope this helps!
>> >> >
>> >> > Can you confirm if this issue is still present with a recent kernel?
>> >>
>> >> e.g. buster-backports?
>> >
>> > Yes exactly either buster-backports, unsteable or mainline.
>> >
>> > Initial goal on asking you back is that the issue as reported for some
>> > kernels way back, try to find out if the issue is still present or if
>> > we can close the bug otherwise as maintenance.
>>
>> Understood.
>>
>> The situation, right now, is this:
>>
>> 1. the user of this machine has been running the 5.7.10 kernel since
>> around August 2020, from buster-backports
>>
>> 2. they indeed reported the bug not happening for "a month or two" but,
>> in their opinion it was "still happening" intermittently, and they
>> expressed surprise at the idea that the bug was fixed
>>
>> 3. i therefore completed the last buster point upgrade and installed the
>> 5.10.24 Linux kernel, again from backports
>>
>> 4. i then rebooted the machine in the new kernel, logged in as said
>> user, then closed the lid, waited a few seconds, and opened the lid
>> back up
>>
>> The mouse froze.
>>
>> I rebooted (because that you can still do, of course, with
>> control-alt-delete), and again reproduced it.
>>
>> So, from my perspective, this bug is definitely not fixed, even with the
>> latest backported kernel, in Debian buster.
>>
>> [I'll note that, interestingly, I'm not actually sure the machine goes to
>> sleep. The red light on the "i" of the "Thinkpad" lid logo doesn't
>> actually start flashing slowly like it typically does during sleep. But
>> from a user perspective, that doesn't matter: it's "close the lid,
>> computer crashes" kind of experience, which is a pretty nasty regression
>> from stretch.]
>
> Thanks for reporting back, much appreciated you took time again to
> recheck. So I suspect the problem from Tollef and yours might be
> different.
>
> Do logs (dmesg, X logs) give any helpful hints?
On closing the lid, this seems to appear in Xorg.log:
[ 75.548] (II) config/udev: removing device TPPS/2 IBM TrackPoint
[ 75.548] (**) Option "fd" "30"
[ 75.549] (II) event13 - TPPS/2 IBM TrackPoint: device removed
[ 75.553] (II) UnloadModule: "libinput"
[ 75.553] (II) systemd-logind: releasing fd for 13:77
[ 75.555] (EE) systemd-logind: failed to release device: Device not taken
dmesg is similarly unhappy:
May 3 20:11:13 topcrapn kernel: [ 75.150214] psmouse serio2: Failed to disable mouse on rmi4-00.fn03/serio0
Interestingly, it seems that the machine indeed doesn't go to sleep: it
loops over a failure to sleep and fills up syslog with errors as long as
it's trying to sleep, pretty catastrophic, from a battery usage
perspective.
I attach the two logs and am continuing my investigation. User now
reports situation is actually much worse than before the backports
upgrade: at least 5.7 was intermittent, now the crash is systematic.
A.
--
La propriété est un piège: ce que nous croyons posséder nous possède.
- Alphonse Karr
[Xorg.log (text/plain, attachment)]
[kern.log (text/plain, attachment)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Tue, 04 May 2021 00:48:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Tue, 04 May 2021 00:48:04 GMT) (full text, mbox, link).
Message #73 received at 928189@bugs.debian.org (full text, mbox, reply):
On 2021-05-03 20:27:26, Antoine Beaupré wrote:
[...]
> Interestingly, it seems that the machine indeed doesn't go to sleep: it
> loops over a failure to sleep and fills up syslog with errors as long as
> it's trying to sleep, pretty catastrophic, from a battery usage
> perspective.
>
> I attach the two logs and am continuing my investigation. User now
> reports situation is actually much worse than before the backports
> upgrade: at least 5.7 was intermittent, now the crash is systematic.
Relevant: booting into 4.19.132, from plain buster, doesn't reproduce
the above failure to suspend. The machine suspends fine, and resumes,
and the mouse even still works correctly.
I wonder if this is a regression introduced in backports. But I could
have sworn this was happening *before* I upgraded to the backported
kernels...
And here I was hoping that upgrading to bullseye might fix this, maybe
it would make things even worse because the old kernel wouldn't be
available anymore (although if it's an interoperability issue, then
maybe it would fix it, who knows nowadays...)
--
No animal has more liberty than the cat; but it buries the mess it
makes. The cat is the best anarchist. Until they learn that from the cat
I cannot respect them.
- For whom the bell tolls, Ernest Hemingway
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Tue, 04 May 2021 01:51:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Tue, 04 May 2021 01:51:04 GMT) (full text, mbox, link).
Message #78 received at 928189@bugs.debian.org (full text, mbox, reply):
On 2021-05-03 20:44:31, Antoine Beaupré wrote:
> On 2021-05-03 20:27:26, Antoine Beaupré wrote:
>
> [...]
>
>> Interestingly, it seems that the machine indeed doesn't go to sleep: it
>> loops over a failure to sleep and fills up syslog with errors as long as
>> it's trying to sleep, pretty catastrophic, from a battery usage
>> perspective.
>>
>> I attach the two logs and am continuing my investigation. User now
>> reports situation is actually much worse than before the backports
>> upgrade: at least 5.7 was intermittent, now the crash is systematic.
>
> Relevant: booting into 4.19.132, from plain buster, doesn't reproduce
> the above failure to suspend. The machine suspends fine, and resumes,
> and the mouse even still works correctly.
>
> I wonder if this is a regression introduced in backports. But I could
> have sworn this was happening *before* I upgraded to the backported
> kernels...
And that is confirmed: it does happen in older kernels, just less
reliably.
a.
--
We know the road to freedom has always been stalked by death.
- Angela Davis
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#928189; Package src:linux.
(Tue, 04 May 2021 19:12:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Antoine Beaupré <anarcat@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>.
(Tue, 04 May 2021 19:12:04 GMT) (full text, mbox, link).
Message #83 received at 928189@bugs.debian.org (full text, mbox, reply):
Another thing I should mention is that I accidentally (I swear) ended up in memtest86 during some kernel switching tests, and figured I would let that run. It found about a dozen errors in 10-20 minutes testing, so there's also that: it could be a problem with the RAM. That said, those are new modules I got on this laptop, and the problem was happening before those were changed...
Removed tag(s) patch.
Request was from Salvatore Bonaccorso <carnil@debian.org>
to control@bugs.debian.org.
(Thu, 13 May 2021 20:39:03 GMT) (full text, mbox, link).
Message #86 received at 922666-done@bugs.debian.org (full text, mbox, reply):
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
Message #87 received at 928189-done@bugs.debian.org (full text, mbox, reply):
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
Message sent on
to Mattis <e.mail.mattis@googlemail.com>:
Bug#928189.
(Sat, 10 Aug 2024 12:03:06 GMT) (full text, mbox, link).
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Sun, 08 Sep 2024 07:29:34 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.