Comment 164 for bug 1791427

Revision history for this message
Henry Bigelow (hrbigelow) wrote :

Hi Aaron,

I did:

$ sudo dpkg -i linux-{image,headers}-4.20.0-rc3+_4.20.0-rc3+-6_amd64.deb

# edit /etc/default/grub so it now reads:
GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi='Windows 2009' modprobe.blacklist=nouveau rmi_core.debug_flags=0x7"

$ sudo update-grub
$ sudo /sbin/shutdown now

# reboot into kernel 4.20
# touchpad now more responsive - it picks up lighter and faster touches as clicks.
# close lid to suspend. on first two wakeups, touchpad worked
# on third wakeup, touchpad didn't work. then:

$ cat /proc/interrupts | grep rmi > rmi_irq.log

# move finger around on touchpad for several seconds, even though mouse pointer didn't move

$ cat /proc/interrupts | grep rmi >> rmi_irq.log

# rmi_irq.log is empty

$ journalctl -b 0 -k > journalctl.log

# just for curiosity, close lid again, wait 10 seconds, reopen. Still, mousepad is unresponsive.
# Then, without warning, laptop goes into sleep mode (with lid still open. I press the button to resume. Screen blinks about five times, and finally wakes up. Now, mousepad works.

$ journalctl -b 0 -k > journalctl.after_blink.log

$ wc -l journalctl.*
  1735 journalctl.after_blink.log
  1586 journalctl.log

Have attached journalctl.after_blink.log

Thanks in advance for any information you could provide!