| 2023-01-11 04:00:05 |
Paul Gear |
bug |
|
|
added bug |
| 2023-01-11 04:00:41 |
Paul Gear |
description |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I'm going to mark this as high, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. |
|
| 2023-01-11 04:03:40 |
Paul Gear |
summary |
Blank screen on bootup |
ThinkPad L14 Gen 3 blank screen on bootup |
|
| 2023-01-11 04:06:14 |
Paul Gear |
description |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. |
|
| 2023-01-11 04:06:26 |
Paul Gear |
summary |
ThinkPad L14 Gen 3 blank screen on bootup |
ThinkPad L14 Gen 3 blank laptop screen on bootup |
|
| 2023-01-11 04:08:04 |
Paul Gear |
description |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
|
| 2023-01-11 20:27:12 |
Timo Aaltonen |
affects |
linux-signed-oem-5.10 (Ubuntu) |
linux-oem-5.17 (Ubuntu) |
|
| 2023-01-11 20:27:33 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-01-11 20:27:33 |
Timo Aaltonen |
bug task added |
|
linux-oem-5.17 (Ubuntu Jammy) |
|
| 2023-01-11 20:30:53 |
Timo Aaltonen |
linux-oem-5.17 (Ubuntu): status |
New |
Invalid |
|
| 2023-01-11 20:31:02 |
Timo Aaltonen |
linux-oem-5.17 (Ubuntu Jammy): status |
New |
Incomplete |
|
| 2023-01-13 03:40:32 |
Paul Gear |
attachment added |
|
lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641117/+files/lspci.txt |
|
| 2023-01-13 03:42:37 |
Paul Gear |
attachment removed |
lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641117/+files/lspci.txt |
|
|
| 2023-01-13 03:50:05 |
Paul Gear |
attachment added |
|
lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641118/+files/lspci.txt |
|
| 2023-01-13 03:52:23 |
Paul Gear |
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 |
|
| 2023-01-13 03:54:37 |
Paul Gear |
attachment added |
|
kern.log-5.17.0-1026-oem https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641120/+files/kern.log-5.17.0-1026-oem |
|
| 2023-01-13 04:08:29 |
Paul Gear |
attachment added |
|
kern.log-6.0.0-1010-oem https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641122/+files/kern.log-6.0.0-1010-oem |
|
| 2023-01-13 08:51:29 |
AceLan Kao |
bug watch added |
|
https://gitlab.freedesktop.org/drm/amd/-/issues/2220 |
|
| 2023-01-17 04:55:17 |
AaronMa |
bug watch added |
|
https://bugzilla.kernel.org/show_bug.cgi?id=216373 |
|
| 2023-01-17 04:55:31 |
AaronMa |
bug |
|
|
added subscriber AaronMa |
| 2023-01-17 04:55:44 |
AaronMa |
linux-oem-5.17 (Ubuntu Jammy): status |
Incomplete |
Triaged |
|
| 2023-01-17 08:58:00 |
AceLan Kao |
bug watch added |
|
https://gitlab.freedesktop.org/drm/amd/-/issues/2216 |
|
| 2023-01-17 11:04:03 |
Paul Gear |
attachment added |
|
lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5641903/+files/lspci.txt |
|
| 2023-01-18 00:40:22 |
Paul Gear |
attachment added |
|
kern.log-5.17.0-2026-oem https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+attachment/5642117/+files/kern.log-5.17.0-2026-oem |
|
| 2023-01-18 01:34:03 |
AceLan Kao |
linux-oem-5.17 (Ubuntu Jammy): assignee |
|
AceLan Kao (acelankao) |
|
| 2023-01-18 05:29:13 |
AceLan Kao |
description |
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
[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 other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too.
https://gitlab.freedesktop.org/drm/amd/-/issues/2216
[Test]
Verified by Aaron Ma.
[Where problems could occur]
Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it.
================
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
|
| 2023-01-18 05:36:04 |
AceLan Kao |
description |
[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 other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too.
https://gitlab.freedesktop.org/drm/amd/-/issues/2216
[Test]
Verified by Aaron Ma.
[Where problems could occur]
Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it.
================
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
[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 other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too.
https://gitlab.freedesktop.org/drm/amd/-/issues/2216
BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it.
[Test]
Verified by Aaron Ma.
[Where problems could occur]
Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it.
================
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
|
| 2023-01-19 06:30:33 |
AceLan Kao |
description |
[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 other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too.
https://gitlab.freedesktop.org/drm/amd/-/issues/2216
BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it.
[Test]
Verified by Aaron Ma.
[Where problems could occur]
Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it.
================
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
[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 other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too.
https://gitlab.freedesktop.org/drm/amd/-/issues/2216
BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it.
[Test]
Verified by Aaron Ma and the bug reporter.
[Where problems could occur]
Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it.
================
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. |
|
| 2023-01-19 06:31:44 |
AceLan Kao |
linux-oem-5.17 (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2023-01-19 19:11:09 |
Timo Aaltonen |
linux-oem-5.17 (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
linux-oem-5.17 (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
cve linked |
|
2022-3545 |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
cve linked |
|
2022-42895 |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
cve linked |
|
2022-42896 |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
cve linked |
|
2022-4378 |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
cve linked |
|
2022-45934 |
|
| 2023-02-08 17:39:20 |
Launchpad Janitor |
cve linked |
|
2023-0179 |
|
| 2023-02-13 07:55:38 |
Timo Aaltonen |
bug task added |
|
linux (Ubuntu) |
|
| 2023-02-13 07:55:50 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-02-13 07:55:50 |
Timo Aaltonen |
bug task added |
|
linux (Ubuntu Lunar) |
|
| 2023-02-13 07:55:50 |
Timo Aaltonen |
bug task added |
|
linux-oem-5.17 (Ubuntu Lunar) |
|
| 2023-02-13 07:55:50 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-02-13 07:55:50 |
Timo Aaltonen |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2023-02-13 07:55:50 |
Timo Aaltonen |
bug task added |
|
linux-oem-5.17 (Ubuntu Kinetic) |
|
| 2023-02-13 07:55:56 |
Timo Aaltonen |
linux (Ubuntu Lunar): status |
New |
Invalid |
|
| 2023-02-13 07:55:58 |
Timo Aaltonen |
linux (Ubuntu Kinetic): status |
New |
Invalid |
|
| 2023-02-13 07:56:02 |
Timo Aaltonen |
linux (Ubuntu Jammy): status |
New |
Invalid |
|
| 2023-02-13 07:56:07 |
Timo Aaltonen |
linux-oem-5.17 (Ubuntu Kinetic): status |
New |
Invalid |
|
