Resume from suspend

[Nathaniel Simard]

The screen stays black when resume from suspend systematically. Also the trackpad does not always work when booting. A few reboot are needed sometime to have a working environment. I'am unsure if the trackpad issue is related.

I tried some mainline kernels. Suspend works with kernels 5.2*, the trackpad issue is still present, but seems less frequent.

All kernels 5.3.* and 5.4-rc* have the same issue.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nathaniel 1328 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sun Oct 20 13:31:24 2019
InstallationDate: Installed on 2019-10-19 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:55a4 Generic Goodix FingerPrint Device
 Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 004: ID 8087:0aaa Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20R9
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=8df6a4ab-733f-4e29-b46a-e3f7ded2bafd ro quiet splash modprobe.blacklist=nouveau vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic N/A
 linux-firmware 1.183
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 9YCN33WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 13s-IWL
dmi.modalias: dmi:bvnLENOVO:bvr9YCN33WW:bd05/09/2019:svnLENOVO:pn20R9:pvrLenovoThinkBook13s-IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IWL:
dmi.product.family: ThinkBook 13s-IWL
dmi.product.name: 20R9
dmi.product.sku: LENOVO_MT_20R9_BU_idea_FM_ThinkBook 13s-IWL
dmi.product.version: Lenovo ThinkBook 13s-IWL
dmi.sys.vendor: LENOVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.

[Nathaniel Simard (ksyiros)]

I ran the bisect and the end result is `3f677f9c998a18d11641b5a2de6f11d0af32a153`. But I'm unsure if this is accurate because at some point the kernel just stop working.

[Kai-Heng Feng (kaihengfeng)]

It's highly unlikely this commit caused the issue.

[Nathaniel Simard (ksyiros)]

I agree! It is way more likely to be a commit in the ideapad driver, that one "55167453111d3a1e600e29ba6c8e63906bb4821b" or that one "17f1bf38c8821ce851d95708a1f1e226d17ec2c5".

[Nathaniel Simard (ksyiros)]

After some more testing, the computer comes back to life after around 1 minute. The login screen seems fine but after login, the computer is unusable. No application can be started, the wifi do not work and pretty much everything do not work. What can I do to help ?

[Kai-Heng Feng (kaihengfeng)]

Is the issue still present?

[Nathaniel Simard (ksyiros)]

With kernel 5.4.6 it's OK so I guess the problem is resolved with newer kernels.