Lenovo Thinkpad P14s Gen3 amd Ryzen 7 PRO 6850U various segfault and system becoming irresponsive

Bug #2034523 reported by __JEAN_FRANCOIS__
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux-signed-oem-6.5 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello

This bug report is related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033756 : the hardware is the same.

I'm still hoping that my laptop does not crash once a day (in average), I'm now trying the kernel 6.5. It seems a bit better but:
- I got screen flickering (screen goes black ~2s then comes back) both on external monitor and on internal. It seems to happen once for each screen, not at the same time.
- Various programs are crashing with segfault
- System become nearly unusable (soft lockup loop), maybe closing the lid stop this loop. This last point was triggered by launching a huge compilation.

Let me know if I can do some tests that could help to solve the problem.

Kind regards

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-1003-oem 6.5.0-1003.3
ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0
Uname: Linux 6.5.0-1003-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 6 09:53:02 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02
InstallationDate: Installed on 2023-06-02 (95 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42
ProcEnviron:
 TERM=alacritty
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: linux-signed-oem-6.5
UpgradeStatus: Upgraded to jammy on 2023-08-12 (24 days ago)

Revision history for this message
__JEAN_FRANCOIS__ (jean-francois--) wrote :
description: updated
Revision history for this message
__JEAN_FRANCOIS__ (jean-francois--) wrote :

After reporting the bug, I continued to run this kernel. Then at some point the system completely freeze.
Closing the lid did not do it this time.
I don't know if the last logs are relevant or not.
I rebooted with Alt + PrintScreen + SUB

I have attached the related kernel log (journalctl -k -b -1).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-oem-6.5 (Ubuntu):
status: New → Confirmed
Revision history for this message
Dominik (dominalien) wrote :

This is related to kernel 6.5 and happens for me on Ryzen 5 3500U on Mantic Minotaur.

It is fixed in kernel 6.5.6, as described here: https://gitlab.freedesktop.org/drm/amd/-/issues/2830

I first saw this on Fedora with kernel 6.5.5 (it was not present on kernel 6.4) and can confirm kernel 6.5.6 fixes it.

I really hope Mantic is not released with the kernel it has now.

Revision history for this message
__JEAN_FRANCOIS__ (jean-francois--) wrote :

Sounds like a good news.

On my side I was also experiencing hw issues (hence many many freezes and other problems), the motherboard of my laptop has been replaced recently.

As suggested by someone from lenovo on lenovo forum, I'm now running fedora 38 which seemed to be stable for him (I'm waiting for Ubuntu 23.10 and a more recent kernel).
On fedora I'm running kernel 6.5.5-200.fc38.x86_64.
Gdm is started but I'm using the laptop remotely through ssh (I'm still worried about the system stability) so there is not much graphical activity (only journalctl -k -f on tty2) it's probably why I haven't faced any issue yet (uptime is 6 days).

It seems the issue is solved, but let me know if you want me to try something on the kernel I'm running.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.