| View previous topic :: View next topic |
| Author |
Message |
Mika15
n00b
Joined: 09 Dec 2010
Posts: 64
Location: Barcelona, Spain
|
 Posted: Mon Jan 11, 2021 10:52 am Post subject: [Solved]Problem on sleep |
 |
|
Hi there,
I have a problem with my Gentoo when I try to put it in sleep mode, it tries then come back on the login screen, on /var/log/messages and dmesg, I have theses lines:
| Code: |
[ 2224.323384] elogind-daemon[1359]: Failed to suspend system. System resumed again: Input/output error
[ 2224.324013] elogind-daemon[1359]: Error during inhibitor-delayed operation (already returned success to client): Input/output error
|
I don't have more information and I don't know how to check and solve this problem.
My Gentoo is fully updated with 5.10.6 Kernel, this problem doesn't happen with 5.10.5 or 5.9.1.
Do you have any idea ?
Thanks.
Last edited by Mika15 on Thu Jan 14, 2021 4:07 pm; edited 3 times in total |
|
| Back to top |
|
 |
Mika15
n00b
Joined: 09 Dec 2010
Posts: 64
Location: Barcelona, Spain
|
| Posted: Mon Jan 11, 2021 2:26 pm Post subject: |
|
|
I checked this page:
https://wiki.gentoo.org/wiki/Elogind
My Kernel is configured correctly, same as USE flags (elogind -systemd), and the service is automatically started at boot.
I don't know where to find something to help me, if someone have a clue, I will appreciate it!
Thanks. |
|
| Back to top |
|
|
Mika15
n00b
Joined: 09 Dec 2010
Posts: 64
Location: Barcelona, Spain
|
| Posted: Mon Jan 11, 2021 2:59 pm Post subject: Solved! |
|
|
Finally solved!
I selected all components in "Control Group Support" on my kernel configuration and it seems to work. |
|
| Back to top |
|
|
Mika15
n00b
Joined: 09 Dec 2010
Posts: 64
Location: Barcelona, Spain
|
| Posted: Thu Jan 14, 2021 9:00 am Post subject: |
|
|
Hi everyone,
I still having this issue after updating to kernel 5.10.7...
Here, more logs from /var/log/message:
| Code: | Jan 14 09:36:19 mikap kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 14 09:36:19 mikap kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 14 09:36:19 mikap kernel: NVRM: GPU 0000:04:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jan 14 09:36:19 mikap kernel: PM: pci_pm_suspend(): nvidia_isr_kthread_bh+0x5e0/0x620 [nvidia] returns -5
Jan 14 09:36:19 mikap kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x210 returns -5
Jan 14 09:36:19 mikap NetworkManager[1799]: <info> [1610613379.2876] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 14 09:36:19 mikap kernel: PM: Device 0000:04:00.0 failed to suspend async: error -5
Jan 14 09:36:19 mikap kernel: PM: Some devices failed to suspend, or early wake event detected
Jan 14 09:36:19 mikap kernel: sd 0:0:0:0: [sda] Starting disk
Jan 14 09:36:19 mikap kernel: r8169 0000:03:00.1 eth0: Link is Down
Jan 14 09:36:19 mikap kernel: OOM killer enabled.
Jan 14 09:36:19 mikap kernel: Restarting tasks ... done.
Jan 14 09:36:19 mikap kernel: PM: suspend exit
Jan 14 09:36:19 mikap kernel: PM: suspend entry (s2idle)
Jan 14 09:36:19 mikap kernel: Filesystems sync: 0.003 seconds
Jan 14 09:36:19 mikap kernel: psmouse serio1: synaptics: queried max coordinates: x [..5660], y [..4642]
Jan 14 09:36:19 mikap kernel: psmouse serio1: synaptics: queried min coordinates: x [1366..], y [1298..]
Jan 14 09:36:20 mikap kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jan 14 09:36:20 mikap kernel: OOM killer disabled.
Jan 14 09:36:20 mikap kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 14 09:36:20 mikap kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 14 09:36:20 mikap kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 14 09:36:20 mikap kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 14 09:36:20 mikap kernel: NVRM: GPU 0000:04:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jan 14 09:36:20 mikap kernel: PM: pci_pm_suspend(): nvidia_isr_kthread_bh+0x5e0/0x620 [nvidia] returns -5
Jan 14 09:36:20 mikap kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x210 returns -5
Jan 14 09:36:20 mikap kernel: PM: Device 0000:04:00.0 failed to suspend async: error -5
Jan 14 09:36:20 mikap kernel: PM: Some devices failed to suspend, or early wake event detected |
It seems that is Nvidia's driver the problem, I don't get much informations about that, someone knows how to deal with that ?
Thank you.
Have a nice day. |
|
| Back to top |
|
|
gorbag
n00b
Joined: 29 Apr 2004
Posts: 19
|
| Posted: Thu Jan 14, 2021 2:33 pm Post subject: |
|
|
| If you are using the unstable nvidia driver you may suffering from the problem reported here: https://bugs.gentoo.org/763129 |
|
| Back to top |
|
|
Mika15
n00b
Joined: 09 Dec 2010
Posts: 64
Location: Barcelona, Spain
|
| Posted: Thu Jan 14, 2021 4:07 pm Post subject: |
|
|
Many thanks Gorbag, this is the problem...
I'm using nvidia-drivers-460.27.04!
Putting NVreg_PreserveVideoMemoryAllocations=0 in /etc/modprobe.d/nvidia.conf, solved my problem! |
|
| Back to top |
|
|
|
Kernel & Hardware
