This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958774
Title:
Black screen after suspending and closing LID
Status in linux package in Ubuntu:
Confirmed
Bug description:
These bugs occur after I upgrade the linux-generic package from 5.11
(not sure) to 5.13 today. After that, I have met two similar bugs:
1. Every time I suspend my computer and re-activate it, I will get a black
screen with a bleaking cursor.
2. Every time I close my laptop's LID and reopen it, I will get an empty
black screen (without anything).
These bugs really trouble me. It will be very helpful if you fix it.
UPDATE on 2022/01/25: After I upgraded the "core" package using "snap
refresh", the first bug has been fixed. However, the second bug
related to laptop devices is still there.
UPDATE on 2022/01/26: The first bug is still there. It seems that the
bug just occasionally disappeared when I tried it yesterday, but
actually it is still there since today I enter the bleaking-cursor-
black-screen situation again.
UPDATE on 2022/01/27:
With respect to the suspend bug:
I followed Thomas's guide and suspended my computer for several times. I have
the following observation:
1. When I use the commandline to put my PC into STR or STI (I cannot put it
into Hibernation, not sure whether this is because I don't allocate a swap
partition for it) by commands like "echo mem | sudo tee /sys/power/state", it
never encounters any problem.
2. The problem occurs only when I use the suspend button in the menu at the
right end of the GNOME status bar. After that, the PC will get into a black
screen, and then immediately and automatically revoke itself. After that, it
shows the logging screen. I enter the password and punch the enter key. Then,
it prints a long error message as follows:
> [ 121.509899] gdm3[11143]: segfault at 0 ip 0000558aaf0a912a sp
00007fff1cd7cf10 error 4 in gdm3[558aaf093000+32000]
> [ 121.509926] Code: 95 c7 40 0f b6 ff e8 d5 8a 01 00 8b 54 24 08 be 80 00
00 00 48 89 df 49 89 c7 4c 8d 05 04 ea 01 00 48 8d 05 1b 51 02 00 85 d2 <49> 8b
0f 48 8d 15 6c 02 02 00 4c 0f 44 c0 31 c0 e8 d1 dd fe ff 45
It gets stuck there and I have to use the power button to force
reboot.
With respect to the LID bug:
I still cannot get any information. After I close the LID and reopen
it, my PC gets stuck at a pure black screen without anything, even a
cursor. Moreover, it's not totally black, but with a bit LED light,
which means that the LID has power supply. I'm not sure whether I
describe this clearly. You can imagine closing your iPhone. It will
first get into a status where the screen still has power and some
light before completely shutting down. My LID is a bit like this.
I'll try to ssh to my computer in this status and look for more info.
UPDATE #2 on 2022/01/27: It seems that I've found the reason for the
LID bug. I close and reopen my laptop's LID to put it into the black
screen status, and then I ssh to it. I then enter "systemctl list-
units" and find that there are two units failed. The info of these two
units got by "systemctl status" is as follows:
> [email protected] - Load Kernel Module drm
> Loaded: loaded (/lib/systemd/system/[email protected]; static)
> Active: failed (Result: start-limit-hit) since Thu 2022-01-27 17:12:07
CST; 43s ago
> Docs: man:modprobe(8)
> Process: 8387 ExecStart=/sbin/modprobe -abq drm (code=exited,
status=0/SUCCESS)
> Main PID: 8387 (code=exited, status=0/SUCCESS)
> CPU: 2ms
>
> Jan 27 17:12:07 lenovopc systemd[1]: Finished Load Kernel Module drm.
> Jan 27 17:12:07 lenovopc systemd[1]: [email protected]: Start request
repeated too quickly.
> Jan 27 17:12:07 lenovopc systemd[1]: [email protected]: Failed with
result 'start-limit-hit'.
> Jan 27 17:12:07 lenovopc systemd[1]: Failed to start Load Kernel Module drm.
> Jan 27 17:12:07 lenovopc systemd[1]: [email protected]: Start request
repeated too quickly.
> Jan 27 17:12:07 lenovopc systemd[1]: [email protected]: Failed with
result 'start-limit-hit'.
> Jan 27 17:12:07 lenovopc systemd[1]: Failed to start Load Kernel Module drm.
> Jan 27 17:12:07 lenovopc systemd[1]: [email protected]: Start request
repeated too quickly.
> Jan 27 17:12:07 lenovopc systemd[1]: [email protected]: Failed with
result 'start-limit-hit'.
> Jan 27 17:12:07 lenovopc systemd[1]: Failed to start Load Kernel Module drm.
and
> systemd-logind.service - User Login Management
> Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
> Active: failed (Result: exit-code) since Thu 2022-01-27 17:12:07 CST;
1min 7s ago
> Docs: man:sd-login(3)
> man:systemd-logind.service(8)
> man:logind.conf(5)
> man:org.freedesktop.login1(5)
> Process: 8417 ExecStart=/lib/systemd/systemd-logind (code=exited,
status=1/FAILURE)
> Main PID: 8417 (code=exited, status=1/FAILURE)
> Status: "Shutting down..."
> Error: 132 (Operation not possible due to RF-kill)
> CPU: 47ms
>
> Jan 27 17:12:07 lenovopc systemd[1]: systemd-logind.service: Scheduled
restart job, restart counter is at 6.
> Jan 27 17:12:07 lenovopc systemd[1]: Stopped User Login Management.
> Jan 27 17:12:07 lenovopc systemd[1]: systemd-logind.service: Start request
repeated too quickly.
> Jan 27 17:12:07 lenovopc systemd[1]: systemd-logind.service: Failed with
result 'exit-code'.
> Jan 27 17:12:07 lenovopc systemd[1]: Failed to start User Login Management.
> Jan 27 17:12:07 lenovopc systemd[1]: systemd-logind.service: Start request
repeated too quickly.
> Jan 27 17:12:07 lenovopc systemd[1]: systemd-logind.service: Failed with
result 'exit-code'.
> Jan 27 17:12:07 lenovopc systemd[1]: Failed to start User Login Management.
There are other 3 units failed, but when the OS functions well they
are also there, so I don't think they're related to the bug.
After I resart [email protected] and systemd-logind.service, the login
screen appears. I enter the password and then my PC gets the same error message
as described before, that is,
> [ 121.509899] gdm3[11143]: segfault at 0 ip 0000558aaf0a912a sp
00007fff1cd7cf10 error 4 in gdm3[558aaf093000+32000]
> [ 121.509926] Code: 95 c7 40 0f b6 ff e8 d5 8a 01 00 8b 54 24 08 be 80 00
00 00 48 89 df 49 89 c7 4c 8d 05 04 ea 01 00 48 8d 05 1b 51 02 00 85 d2 <49> 8b
0f 48 8d 15 6c 02 02 00 4c 0f 44 c0 31 c0 e8 d1 dd fe ff 45
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-generic 5.13.0.27.37
ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nomanous 5648 F.... pulseaudio
/dev/snd/controlC1: nomanous 5648 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 23 23:02:24 2022
InstallationDate: Installed on 2021-06-29 (208 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: HASEE Computer NH5x_7xDCx_DDx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-27-generic N/A
linux-backports-modules-5.13.0-27-generic N/A
linux-firmware 1.201.3
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
dmi.bios.date: 04/18/2020
dmi.bios.release: 7.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.03THZX
dmi.board.asset.tag: Tag 12345
dmi.board.name: NH5x_7xDCx_DDx
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.1
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: NH5x_7xDCx_DDx
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: HASEE Computer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958774/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
