Hi, could you reboot boot with kernel parameters
i2c-hid.debug=1 dyndbg='file drivers/i2c/* +pt'
and paste dmesg since boot to the symptom occurs (after deep suspend)?
Please refer to this tutorial[1] for modifications to boot params.
Detailed steps are:
1. Edit grub settings:
$ gksu gedit /etc/default/grub
Then edit the line beginning with "GRUB_CMDLINE_LINUX_DEFAULT=" as:
GRUB_CMDLINE_LINUX_DEFAULT="i2c-hid.debug=1 dyndbg='file
drivers/i2c/* +pt' log_buf_len=32M"
I also added "log_buf_len=32M" here to extend kernel log buffer size
so that everything since boot will be kept. Save changes, quit gedit.
2. Re-generate grub.conf:
$ sudo update-grub
3. After rebooted, open a terminal and save dmesg:
$ dmesg -w | sudo tee dmesg.$(uname -r).i2c-debug
This will run forever until interrupted (Ctrl-C).
4. Open another terminal and trigger system suspend by command
$ systemctl suspend
Resume the system by pressing keyboard keys, power buttons whatever
fits your case after 1 minute.
5. Interrupt previous dmesg command in 3) and paste the saved dmesg log.
[1]: https://www.howtogeek.com/196655/how-to-configure-the-grub2-boot-
loaders-settings/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857776
Title:
touchpad freeze after long suspention
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857776/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
