Debian Bug report logs - #922666
linux-image-4.19.0-2-amd64: Trackpad and trackpoint stop working after suspend

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Tollef Fog Heen <tfheen@err.no>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux-image-4.19.0-2-amd64: Trackpad and trackpoint stop working after suspend

Date: Tue, 19 Feb 2019 06:39:50 +0100

[Message part 1 (text/plain, inline)]

Package: src:linux
Version: 4.19.16-1
Severity: normal

After resuming from a suspend, the trackpoint and trackpad on my
Thinkpad X1 carbon stops working.  If I poke the touchpad, I get a
series of:

[ 7192.255201] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4758]
[ 7192.291304] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..]
[ 7192.938759] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 7192.943708] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 7192.944854] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 7192.952492] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 7192.955009] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1
[ 7192.955011] psmouse serio1: issuing reconnect request

in the kernel log, and it eventually recovers, but only the trackpad.

When it recovers, the X log also looks like it sees the trackpoint, but
fails to enable it:

kernel: psmouse serio2: Failed to reset mouse on synaptics-pt/serio0: -5
kernel: psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x06, buttons: 3/3
kernel: input: TPPS/2 Elan TrackPoint as /devices/platform/i8042/serio1/serio2/input/input39
/usr/lib/gdm3/gdm-x-session[1912]: (II) config/udev: Adding input device TPPS/2 Elan TrackPoint (/dev/input/mouse1)
/usr/lib/gdm3/gdm-x-session[1912]: (II) No input driver specified, ignoring this device.
/usr/lib/gdm3/gdm-x-session[1912]: (II) This device may have been added with another device file.
/usr/lib/gdm3/gdm-x-session[1912]: (II) config/udev: Adding input device TPPS/2 Elan TrackPoint (/dev/input/event6)
/usr/lib/gdm3/gdm-x-session[1912]: (**) TPPS/2 Elan TrackPoint: Applying InputClass "libinput pointer catchall"
/usr/lib/gdm3/gdm-x-session[1912]: (II) Using input driver 'libinput' for 'TPPS/2 Elan TrackPoint'
/usr/lib/gdm3/gdm-x-session[1912]: (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 65 paused 0
/usr/lib/gdm3/gdm-x-session[1912]: (**) TPPS/2 Elan TrackPoint: always reports core events
/usr/lib/gdm3/gdm-x-session[1912]: (**) Option "Device" "/dev/input/event6"
/usr/lib/gdm3/gdm-x-session[1912]: (**) Option "_source" "server/udev"
/usr/lib/gdm3/gdm-x-session[1912]: (II) event6  - TPPS/2 Elan TrackPoint: is tagged by udev as: Mouse Pointingstick
/usr/lib/gdm3/gdm-x-session[1912]: (II) event6  - TPPS/2 Elan TrackPoint: device is a pointer
/usr/lib/gdm3/gdm-x-session[1912]: (II) event6  - TPPS/2 Elan TrackPoint: device removed
/usr/lib/gdm3/gdm-x-session[1912]: (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input39/event6"
/usr/lib/gdm3/gdm-x-session[1912]: (II) XINPUT: Adding extended input device "TPPS/2 Elan TrackPoint" (type: MOUSE, id 12)
/usr/lib/gdm3/gdm-x-session[1912]: (**) Option "AccelerationScheme" "none"
/usr/lib/gdm3/gdm-x-session[1912]: (**) TPPS/2 Elan TrackPoint: (accel) selected scheme none/0
/usr/lib/gdm3/gdm-x-session[1912]: (**) TPPS/2 Elan TrackPoint: (accel) acceleration factor: 2.000
/usr/lib/gdm3/gdm-x-session[1912]: (**) TPPS/2 Elan TrackPoint: (accel) acceleration threshold: 4
/usr/lib/gdm3/gdm-x-session[1912]: (II) event6  - TPPS/2 Elan TrackPoint: is tagged by udev as: Mouse Pointingstick
/usr/lib/gdm3/gdm-x-session[1912]: (II) event6  - TPPS/2 Elan TrackPoint: device is a pointer
kernel: psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

-- Package-specific info:

[Message part 2 (text/plain, attachment)]

[Message part 3 (text/plain, inline)]

-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-2-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133
ii  kmod                                    25-2
ii  linux-base                              4.5

Versions of packages linux-image-4.19.0-2-amd64 recommends:
ii  apparmor             2.13.2-7
ii  firmware-linux-free  3.4
ii  irqbalance           1.5.0-3

Versions of packages linux-image-4.19.0-2-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.04~git20171011.af7e95c3+dfsg1-6
ii  grub-efi-amd64          2.02+dfsg1-10
pn  linux-doc-4.19          <none>

Versions of packages linux-image-4.19.0-2-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

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Message #10 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: 922666@bugs.debian.org, 928189@bugs.debian.org

Cc: Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: confirmed bug report

Date: Wed, 11 Sep 2019 20:20:22 -0400

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

Message #27 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Antoine Beaupré <anarcat@debian.org>, 922666@bugs.debian.org

Cc: 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Fri, 30 Apr 2021 21:04:29 +0200

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

Message #34 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Tollef Fog Heen <tfheen@err.no>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: Antoine Beaupré <anarcat@debian.org>, 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>

Subject: Re: Bug#922666: confirmed bug report

Date: Fri, 30 Apr 2021 21:35:55 +0200

]] 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

Message #39 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>, 922666@bugs.debian.org

Cc: 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Fri, 30 Apr 2021 19:34:04 -0400

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

Message #44 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Sat, 1 May 2021 07:59:01 +0200

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

Message #49 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Sun, 02 May 2021 20:22:07 -0400

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.

Message #54 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Antoine Beaupré <anarcat@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Mon, 3 May 2021 07:37:42 +0200

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

Message #61 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Mon, 03 May 2021 10:56:59 -0400

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

Message #66 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Mon, 03 May 2021 20:27:26 -0400

[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)]

Message #71 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Mon, 03 May 2021 20:44:31 -0400

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

Message #76 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Mon, 03 May 2021 21:47:26 -0400

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

Message #81 received at 922666@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Salvatore Bonaccorso <carnil@debian.org>

Cc: 922666@bugs.debian.org, 928189@bugs.debian.org, Mattis <e.mail.mattis@googlemail.com>, Tollef Fog Heen <tfheen@debian.org>

Subject: Re: Bug#922666: confirmed bug report

Date: Tue, 04 May 2021 15:09:07 -0400

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...

Message #88 received at 922666-done@bugs.debian.org (full text, mbox, reply):

From: carnil@debian.org

To: 922666-done@bugs.debian.org

Cc: 922666-submitter@bugs.debian.org

Subject: Closing this bug (BTS maintenance for src:linux bugs)

Date: Sat, 10 Aug 2024 14:00:45 +0200 (CEST)

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

Send a report that this bug log contains spam.