kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

[cedric]

I do not know how to find information to help debug.
The laptop is lenovo E15 with latest BIOS 1.13

kubuntu 21.04

laptop boots correctly with 5.13.8 and trackpad works.
with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-08-12 (13 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Package: linux (not installed)
Tags: hirsute
Uname: Linux 5.13.8-051308-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2021-08-12 (14 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Package: linux (not installed)
Tags: hirsute
Uname: Linux 5.13.8-051308-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1941773

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[cedric (cedric)]

apport information

[cedric (cedric)]

apport information

[Chris Chiu (mschiu77)]

Could you run `apport-collect 1941773` again since lots of file missing.

And can you paste the kernel panic here? Doing `journalctl -k -b -1 > journal.log` after reboot and attach the journal.log here would be helpful. Thanks

[cedric (cedric)]

apport information

[cedric (cedric)]

apport information

[cedric (cedric)]

attached journal.log file, done after trying to boot with 5.13.13 (kernel panic) and rebooting with functional kernel (5.13.8)

[Chris Chiu (mschiu77)]

The journal log shows the kernel version 5.13.8. Could you log for 5.13.13? Maybe post the file generated by "journalctl -k -b -all" here. Thanks.

[cedric (cedric)]

new logs

[Chris Chiu (mschiu77)]

The new logs still belongs to 5.13.8 so there's no panic information. Since there's no difference on hid and input drivers between 5.13.8 and 5.13.9. I can try to do bisection to find out the possible culprit. Could you help test the following kernel and give me your test results? Thanks

https://people.canonical.com/~mschiu77/lp1941773/3cadaeae64dc/
https://people.canonical.com/~mschiu77/lp1941773/base/

[cedric (cedric)]

Hi Chris,

both are working, no kernel panic.

Regards

Cédric

On 8/30/21 10:26 AM, Chris Chiu wrote:
> The new logs still belongs to 5.13.8 so there's no panic information.
> Since there's no difference on hid and input drivers between 5.13.8 and
> 5.13.9. I can try to do bisection to find out the possible culprit.
> Could you help test the following kernel and give me your test results?
> Thanks
>
> https://people.canonical.com/~mschiu77/lp1941773/3cadaeae64dc/
> https://people.canonical.com/~mschiu77/lp1941773/base/
>

[Chris Chiu (mschiu77)]

Thanks. We still have 3~4 versions to try and make sure which commit cause the panic.
Please try https://people.canonical.com/~mschiu77/lp1941773/989b27104a97/ and let me know the result. Thanks.

[cedric (cedric)]

Hi,

This one works correctly.

Regards

Cédric

On 8/31/21 5:33 PM, Chris Chiu wrote:
> Thanks. We still have 3~4 versions to try and make sure which commit cause the panic.
> Please try https://people.canonical.com/~mschiu77/lp1941773/989b27104a97/ and let me know the result. Thanks.
>

[Chris Chiu (mschiu77)]

Thanks. Please try https://people.canonical.com/~mschiu77/lp1941773/f259ee2f0379/ and let me know the result. Thanks

[cedric (cedric)]

Hi Chris,

This one works also but I have this error during boot:

[    1.462530] psmouse serio1: elantech: synaptics_send_cmd query 0x01
failed.

log file is attached

Regards

Cédric

On 9/1/21 10:52 AM, Chris Chiu wrote:
> Thanks. Please try
> https://people.canonical.com/~mschiu77/lp1941773/f259ee2f0379/ and let
> me know the result. Thanks
>

[Chris Chiu (mschiu77)]

The original kernel panic shows it's caused by the kernel stack protector so I don't think it's the problem of the psmouse. I think I have the candidate which cause the problem. Can you help me test the kernel in https://people.canonical.com/~mschiu77/lp1941773/I/? Thanks

[cedric (cedric)]

this one works also

On 9/2/21 4:08 PM, Chris Chiu wrote:
> The original kernel panic shows it's caused by the kernel stack
> protector so I don't think it's the problem of the psmouse. I think I
> have the candidate which cause the problem. Can you help me test the
> kernel in https://people.canonical.com/~mschiu77/lp1941773/I/? Thanks
>

[Chris Chiu (mschiu77)]

It should be caused by the kbuild flag `-fcf-protection=none` and this will not be applied for the UBUNTU release image.

[randomdave (randomdave)]

Impish is now released but this problem persists in
linux-image-5.13.0-19-generic. Any idea when this will be fixed?

This isn't urgent because the kernel at https://people.canonical.com/~mschiu77/lp1941773/I/ is working for me for now.

[Ahmet Yıldırım (regenx)]

@randomdave I don't agree with you about the urgency of this problem. It should be fixed as soon as possible.

[randomdave (randomdave)]

After thinking more carefully I agree with y-ahmet that is bug IS urgent and should be fixed immediately.

[cedric (cedric)]

Hi Chris,

I was trying to install Ubuntu 21.10 (fresh download) and I have the
same issue.

Regards

Cédric

On 9/6/21 13:20, Chris Chiu wrote:
> It should be caused by the kbuild flag `-fcf-protection=none` and this
> will not be applied for the UBUNTU release image.
>