** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Kinetic)
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1027.28
---
linux-oem-5.17 (5.17.0-1027.28) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1027.28 -proposed tracker (LP:
#2003451)
* CVE-2022-3545
- nfp: fix use-after-free in area_cache_get()
*
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank
SRU submitted, thanks
https://lists.ubuntu.com/archives/kernel-team/2023-January/136392.html
** Description changed:
[Impact]
The commit in 5.17.0.1026.27 introduce an regression that leads to the panel
of ThinkPad L14 Gen 3 becomes blank after bootup
224dffc89a957 drm/amdgpu: make sure
@acelankao: Thanks very much! Confirmed that your test kernel fixes the
screen blanking problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen
** Description changed:
[Impact]
The commit in 5.17.0.1026.27 introduce an regression that leads to the panel
of ThinkPad L14 Gen 3 becomes blank after bootup
224dffc89a957 drm/amdgpu: make sure to init common IP before gmc
[Fix]
Revert this commit as it looks like it requires some
** Description changed:
+ [Impact]
+ The commit in 5.17.0.1026.27 introduce an regression that leads to the panel
of ThinkPad L14 Gen 3 becomes blank after bootup
+ 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc
+
+ [Fix]
+ Revert this commit as it looks like it requires some
Hi Paul,
Aaron has found the bad commit which is
224dffc89a957 drm/amdgpu: make sure to init common IP before gmc
I've updated the test kernel at the same location which reverted the commit.
https://people.canonical.com/~acelan/bugs/lp2002467/
I'm going to submit SRU to revert this one, please
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14
Unfortunately, the 5.17.0-2026.27 kernel removing commit
d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a did not resolve the problem -
it exhibits the same display blanking characteristics on the ThinkPad
L14 Gen3 AMD as the signed release 5.17.0-1026-oem does. Boot log for
this kernel attached.
**
lspci -nnvv output on ThinkPad E14 AMD Gen3.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641903/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
6.1.0-1004-oem worked fine in terms of stability over yesterday's work
day, with no amdgpu protection faults, but when I tried to suspend by
closing the lid at the end of the work day, I got some very strange
behaviour that I've never seen before - see video here:
This commit is required for bug 2000110, and I can't figure out any good
solution for this.
"drm/amdgpu: make sure to init common IP before gmc" introduces regression
which could be found here https://gitlab.freedesktop.org/drm/amd/-/issues/2216
and has been reverted from 5.10 stable kernel.
Hi Acelan,
The first bad commit:
commit 224dffc89a957e2f006de3202d12c09bf348f992 (refs/bisect/bad)
Author: Alex Deucher
Date: Wed Dec 21 15:26:47 2022 +0800
drm/amdgpu: make sure to init common IP before gmc
BugLink: https://launchpad.net/bugs/2000110
Move common IP
I've confirmed that 6.1.0-1004-oem (the current version of linux-image-
oem-22.04c) does not have the screen disabling bug. I'll test for
stability in the face of amdgpu protection faults today and see what
happens.
--
You received this bug notification because you are a member of Kernel
Similar to the issue on upstream
https://gitlab.freedesktop.org/drm/amd/-/issues/2220
Compare what we backported and the kernel versions reported on the
upstream bug, I feel like it's below commit introduce the regression
Could you try this test kernel to see if it helps, it only reverts the
note that 6.0.0-1010 has the fix for 1995956
712c02e5d2d3680 drm/amdgpu: workaround for TLB seq race
so if it's buggy, test oem-6.1 and hope it has more goodies
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
I'm not sure this will get fixed for 5.17 at this point, we're already
planning to move to oem-6.1 and EOL 5.17 & 6.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
@tjaalton: Added logs for 1 working and 2 non-working versions. It
seems like there has been quite a lot of churn in the amdgpu driver
between 5.17 and 6.0. Hope this helps narrow down the problem commits.
--
You received this bug notification because you are a member of Kernel
Packages, which
Log from booting 6.0.0-1010-oem - non-viable due to what appears to be
an instance of
https://bugs.launchpad.net/ubuntu/kinetic/+source/linux/+bug/1995956 or
a related bug. Errors start at line 1202. The 80 minutes which it took
for this bug to surface while using Slack is the longest this
Log from booting 5.17.0-1026-oem - this is the kernel that blanks the
screen and is thus unusable. Note the amdgpu errors beginning at line
961 which do not appear in the 5.17.0-1025-oem log.
** Attachment added: "kern.log-5.17.0-1026-oem"
Log from booting 5.17.0-1025-oem - this is the kernel that works
correctly.
** Attachment added: "kern.log-5.17.0-1025-oem"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641119/+files/kern.log-5.17.0-1025-oem
--
You received this bug notification because
lspci -vvnn output
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641118/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in
Hi Paul,
Could you upload the result of "lspci -vvnn" command here?
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop
I ended up on 5.17 because I installed linux-oem-22.04 myself. (Ubuntu
isn't available on this hardware model in my region; it's a self-
install.) There was a bug introduced in 5.19 (I'll find the reference
when I get a moment) which meant that it wasn't stable on my system, but
I can give the
You could try installing linux-oem-22.04b which installs oem-6.0, that
one also has the fix for bug 2000110 but it didn't need other backports.
I suspect those broke just oem-5.17
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
How did you end up with oem-5.17 kernel?
** Package changed: linux-signed-oem-5.10 (Ubuntu) => linux-oem-5.17
(Ubuntu)
** Also affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Invalid
** Changed in:
29 matches
Mail list logo
