[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1035068: linux-image-6.1.0-7-amd64: occasionally no trackpad/trackpoint on resume from hibernate



Thanks. I've installed 6.1.25-1 and will do further testing. The script is something I did, which in my (adminitingly unscientific) testing, seemed to work well with occasional cases of no trackpad/trackpoint input. I'm not quite sure what you mean by the sequence being in reverse... my thought was to remove the module before going to suspend and then load it again after resume. You're right, it's probably safe to remove the entry to load elan_i2c, as psmouse should pull it in. Not sure why I have it in there.

On Fri, Apr 28, 2023 at 4:07 PM Diederik de Haas <didi.debian@cknow.org> wrote:
Control: tag -1 moreinfo

On Friday, 28 April 2023 20:15:46 CEST Harold Grove wrote:
> Package: src:linux
> Version: 6.1.20-2

Unstable now has version 6.1.25-1, could you try that?

> I'm also seeing a possibly related kernel oops when unloading the psmouse
> module. The module is being unloaded via a script under
> /lib/systemd/system-sleep/ which contains:
> #!/bin/sh
> # Reload the trackpoint and trackpad drivers on L13 Yoga Gen 2
> case $1 in
>         pre)
>                 rmmod psmouse;
>                 sleep 1;
>                 rmmod elan_i2c;
>                 ;;
>         post)
>                 modprobe psmouse;
>                 sleep 1;
>                 modprobe elan_i2c;
>                 ;;
> esac

Did you create that yourself or is that some a package?
In any case, the sequence seems odd to me as I'd expect the 'post' sequence to
be the reverse of the 'pre' sequence, thus first `modprobe elan_i2c` and then
`modprobe psmouse`.
Also, if `psmouse` needs `elan_i2c` it should trigger the loading by itself.



Confidentiality Notice: The material transmitted herein is intended only for the use of the addressee and may contain information that constitutes work product or is confidential and exempt from disclosure under applicable law. Distribution or copying of this communication or reliance upon its contents by unauthorized participants is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone or email.

Reply to: