View previous topic :: View next topic |
Author |
Message |
avnt n00b
Joined: 21 Jun 2022 Posts: 4
|
Posted: Tue Jun 21, 2022 7:54 pm Post subject: Suspend hangs with black screen, X11 segfaults on resume |
|
|
So X11 has been segfaulting when my laptop lid is closed for long enough. I'm on a Thinkpad T15g gen 1, with an RTX 2070. I'm faily certain that it has to do with elogind, as well as my NVIDIA drivers, as I'm also experiencing this bug with my NVIDIA GPU/PRIME setup, https://bugs.gentoo.org/693384. I believe that the NVIDIA drivers are most likely the culprit, however, adding scripts that trigger nvidia-sleep.sh or the like doesn't seem to help at all, both with the mentioned bug and with the segfaulting issue. Does anybody have any idea what I should do?
The relevent portion of my Xorg logs (paste link is below for full log):
Code: |
[ 6961.019] (II) systemd-logind: releasing fd for 13:89
[ 11729.685] (EE) intel(0): Failed to set backlight intel_backlight for output eDP1, disabling
[ 23989.595] (**) Option "fd" "29"
[ 23989.595] (II) event2 - Power Button: device removed
[ 23989.595] (**) Option "fd" "26"
[ 23989.595] (II) event7 - Video Bus: device removed
[ 23989.595] (**) Option "fd" "30"
[ 23989.595] (II) event6 - Video Bus: device removed
[ 23989.595] (**) Option "fd" "32"
[ 23989.595] (II) event0 - Sleep Button: device removed
[ 23989.595] (**) Option "fd" "31"
[ 23989.595] (II) event10 - Integrated Camera: Integrated C: device removed
[ 23989.595] (**) Option "fd" "28"
[ 23989.595] (II) event3 - AT Translated Set 2 keyboard: device removed
[ 23989.595] (**) Option "fd" "53"
[ 23989.595] (II) event5 - TPPS/2 Elan TrackPoint: device removed
[ 23989.595] (**) Option "fd" "27"
[ 23989.595] (II) event8 - ThinkPad Extra Buttons: device removed
[ 24014.628] (EE) systemd-logind: failed to ack pause: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[ 24039.654] (EE) systemd-logind: failed to ack pause: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[ 24044.120] (EE)
[ 24044.120] (EE) Backtrace:
[ 24044.120] (EE) 0: /usr/bin/X (xorg_backtrace+0x5b) [0x56359911785b]
[ 24044.121] (EE) 1: /usr/bin/X (0x563598fde000+0x13d495) [0x56359911b495]
[ 24044.121] (EE) 2: /lib64/libc.so.6 (0x7fea71877000+0x3d7c0) [0x7fea718b47c0]
[ 24044.121] (EE) 3: /lib64/libc.so.6 (0x7fea71877000+0x16d35a) [0x7fea719e435a]
[ 24044.121] (EE) 4: /usr/bin/X (0x563598fde000+0x18faf1) [0x56359916daf1]
[ 24044.121] (EE) 5: /usr/lib64/libdbus-1.so.3 (dbus_connection_dispatch+0x3bd) [0x7fea71adc61d]
[ 24044.121] (EE) 6: /usr/lib64/libdbus-1.so.3 (0x7fea71ac5000+0x17a28) [0x7fea71adca28]
[ 24044.121] (EE) 7: /usr/bin/X (0x563598fde000+0x1b0051) [0x56359918e051]
[ 24044.122] (EE) 8: /usr/bin/X (0x563598fde000+0x13de01) [0x56359911be01]
[ 24044.122] (EE) 9: /usr/bin/X (WaitForSomething+0x193) [0x563599115053]
[ 24044.122] (EE) 10: /usr/bin/X (0x563598fde000+0x72d44) [0x563599050d44]
[ 24044.122] (EE) 11: /usr/bin/X (0x563598fde000+0x76cab) [0x563599054cab]
[ 24044.122] (EE) 12: /lib64/libc.so.6 (0x7fea71877000+0x2931a) [0x7fea718a031a]
[ 24044.122] (EE) 13: /lib64/libc.so.6 (__libc_start_main+0x7c) [0x7fea718a03cc]
[ 24044.122] (EE) 14: /usr/bin/X (_start+0x21) [0x56359901a051]
[ 24044.122] (EE)
[ 24044.123] (EE) Segmentation fault at address 0x0
[ 24044.123] (EE)
Fatal server error:
[ 24044.123] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 24044.123] (EE)
[ 24044.123] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 24044.123] (EE) Please also check the log file at "/home/avalon/usr/share/xorg/Xorg.0.log" for additional information.
[ 24044.123] (EE)
[ 24045.059] (EE) Server terminated with error (1). Closing log file.
|
Full X log: https://dpaste.com/HRNGVYTJY _________________ she/they
Last edited by avnt on Wed Jun 22, 2022 12:05 am; edited 2 times in total |
|
Back to top |
|
|
CooSee Veteran
Joined: 20 Nov 2004 Posts: 1429 Location: Earth
|
Posted: Tue Jun 21, 2022 11:12 pm Post subject: |
|
|
hello and welcome to GenToo.
please update your kernel to 5.15.48 and after that re-emerge nvidia-drivers.
if this doesn't work, maybe try with kernel-5.18.5.
it's just my opinion, but i always had weird problems, while using any current stable kernel.
and also, is your filesystem sane?
good luck _________________ " Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
Back to top |
|
|
avnt n00b
Joined: 21 Jun 2022 Posts: 4
|
Posted: Tue Jun 21, 2022 11:47 pm Post subject: |
|
|
CooSee wrote: | hello and welcome to GenToo.
please update your kernel to 5.15.48 and after that re-emerge nvidia-drivers.
if this doesn't work, maybe try with kernel-5.18.5.
it's just my opinion, but i always had weird problems, while using any current stable kernel.
and also, is your filesystem sane?
good luck |
Thanks, it's emerging right now, though I don't have much hope as I've been having these issues across kernel versions, and across versions of the driver, as well as versions of elogind. As it turns out, it seems as though my system is actually
freezing before suspending, rather than just refusing to suspend and blackscreening as I thought, so this might be a different bug entirely (though possibly related). Still, whenever I resume, I get the segfault from X11. I haven't timed it but it seems as though it'll be frozen for minutes before actually suspending. Logs don't show much in terms of useful info.
And I'm not sure what you mean specifically by sane? Like are you asking if it's corrupted or if I've messed with files/directories I shouldn't mess with? Because my filesystem isn't corrupt, and I haven't messed with it too much. _________________ she/they |
|
Back to top |
|
|
CooSee Veteran
Joined: 20 Nov 2004 Posts: 1429 Location: Earth
|
Posted: Wed Jun 22, 2022 6:27 pm Post subject: |
|
|
Quote: | my filesystem isn't corrupt |
ok.
Quote: | I'm faily certain that it has to do with elogind |
but, i think you're using systemd and not openrc (elogind).
Quote: | [ 24014.628] (EE) systemd-logind: failed to ack pause: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. |
is your bios the current one?
also, deactivate all the things which you don't need or doesn't work on linux, e.g. fingerprint sensor etc. in BIOS!
nvidia seems to be pita >>> i found some articles on github - just search for thinkpad on github
it is odd, because the Gen 2 version was certified for ubuntu.
you could use intel graphics, until you found a working solution.
maybe wayland onyl desktop works better !?
or, you can also try with any available live iso from other distros, to get sure it's not kernels (.config) fault.
you've to do some research regarding your device.
or there's one thinkpad gentoo user who can help you
have you read some articles on lenovo support sites?
https://pcsupport.lenovo.com/de/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t15g-gen-1-type-20ur-20us/parts/pd031426-linux-for-personal-systems
please provide your emerge --info _________________ " Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
Back to top |
|
|
avnt n00b
Joined: 21 Jun 2022 Posts: 4
|
Posted: Fri Jun 24, 2022 1:57 am Post subject: |
|
|
CooSee wrote: | Quote: | my filesystem isn't corrupt |
ok.
Quote: | I'm faily certain that it has to do with elogind |
but, i think you're using systemd and not openrc (elogind).
Quote: | [ 24014.628] (EE) systemd-logind: failed to ack pause: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. |
is your bios the current one?
also, deactivate all the things which you don't need or doesn't work on linux, e.g. fingerprint sensor etc. in BIOS!
nvidia seems to be pita >>> i found some articles on github - just search for thinkpad on github
it is odd, because the Gen 2 version was certified for ubuntu.
you could use intel graphics, until you found a working solution.
maybe wayland onyl desktop works better !?
or, you can also try with any available live iso from other distros, to get sure it's not kernels (.config) fault.
you've to do some research regarding your device.
or there's one thinkpad gentoo user who can help you
have you read some articles on lenovo support sites?
https://pcsupport.lenovo.com/de/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t15g-gen-1-type-20ur-20us/parts/pd031426-linux-for-personal-systems
please provide your emerge --info |
I did a BIOS update recently, no change in behavior. I'm not using systemd, I'm using openrc (with elogind, top shows that elogind is running and it's the only logind on my system). I don't know why it logs it like that, but if I had to guess it'd be a program (probably X) falsely assuming that anything that implements org.freedesktop.login1 is a systemd-logind instance.
NVIDIA is definetly a pain.
Wayland has similar problems with suspend/resume, though, instead of segfaulting, sway will just remain frozen in place.
I haven't tried any live ISOs as of yet, however this problem has persisted since install, and it seems to be a problem on other non-systemd systems too, as I've found one fourm post with the exact same problem on artix. https://forum.artixlinux.org/index.php/topic,3627.0.html
Unfortunately I think this is a problem that needs to be taken up with elogind devs, I'm going to submit a bug report.
emerge --info is here: http://dpaste.com/CSS6JYPTG _________________ she/they |
|
Back to top |
|
|
spica Apprentice
Joined: 04 Jun 2021 Posts: 282
|
Posted: Fri Jun 24, 2022 6:01 am Post subject: |
|
|
avnt wrote: | Wayland has similar problems with suspend/resume, though, instead of segfaulting, sway will just remain frozen in place. |
I observe wayland session is frozen too |
|
Back to top |
|
|
yance n00b
Joined: 24 Mar 2022 Posts: 4
|
Posted: Wed Jun 29, 2022 11:01 pm Post subject: |
|
|
avnt wrote: | CooSee wrote: | hello and welcome to GenToo.
please update your kernel to 5.15.48 and after that re-emerge nvidia-drivers.
if this doesn't work, maybe try with kernel-5.18.5.
it's just my opinion, but i always had weird problems, while using any current stable kernel.
and also, is your filesystem sane?
good luck |
Thanks, it's emerging right now, though I don't have much hope as I've been having these issues across kernel versions, and across versions of the driver, as well as versions of elogind. As it turns out, it seems as though my system is actually
freezing before suspending, rather than just refusing to suspend and blackscreening as I thought, so this might be a different bug entirely (though possibly related). Still, whenever I resume, I get the segfault from X11. I haven't timed it but it seems as though it'll be frozen for minutes before actually suspending. Logs don't show much in terms of useful info.
And I'm not sure what you mean specifically by sane? Like are you asking if it's corrupted or if I've messed with files/directories I shouldn't mess with? Because my filesystem isn't corrupt, and I haven't messed with it too much. |
I'm having the same problem. I thought I was the only one experiencing this and so far haven't found any solution. |
|
Back to top |
|
|
CooSee Veteran
Joined: 20 Nov 2004 Posts: 1429 Location: Earth
|
Posted: Thu Jun 30, 2022 12:27 am Post subject: |
|
|
than this is not by accident.
maybe there's something wrong with elogind, regarding suspend/hibernate!?
are you all using elogind?
i can't test it, because i don't use suspend/hibernate on my system. _________________ " Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
Back to top |
|
|
yance n00b
Joined: 24 Mar 2022 Posts: 4
|
Posted: Thu Jun 30, 2022 4:00 am Post subject: |
|
|
CooSee wrote: | than this is not by accident.
maybe there's something wrong with elogind, regarding suspend/hibernate!?
are you all using elogind?
i can't test it, because i don't use suspend/hibernate on my system. |
Yes. I am. My first time use gentoo with openrc+elogind, suspend works very well. I haven't noticed since when this happened. but i have tried to downgrade the kernel and nvidia driver, but the result is still the same. And refer to logind man page on https://manpages.debian.org/unstable/elogind/logind.conf.5.en.html, the official /usr/bin/nvidia-sleep.sh can not be used from a system-sleep hook script for some reason. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21490
|
Posted: Thu Jun 30, 2022 2:58 pm Post subject: |
|
|
Is the problem reproducible on an untainted kernel? You would need to blacklist the nVidia drivers and reboot to clear the taint, then test. |
|
Back to top |
|
|
yance n00b
Joined: 24 Mar 2022 Posts: 4
|
Posted: Tue Jul 05, 2022 4:34 pm Post subject: |
|
|
Hu wrote: | Is the problem reproducible on an untainted kernel? You would need to blacklist the nVidia drivers and reboot to clear the taint, then test. |
I have tried blacklisting the nvidia driver and restarting, but the suspend issue still remain (no changes). |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|