Ubuntu
linux package

Comment 3 for bug 1857776

Revision history for this message

You-Sheng Yang (vicamo) wrote on 2019-12-30:

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.