Oryx Pro 7 cannot suspend

pop-os / pop

A project for managing all Pop!_OS sources

https://system76.com/pop

2.48k stars 87 forks source link

Oryx Pro 7 cannot suspend #1683

Open Yuri6037 opened 3 years ago

Yuri6037 commented 3 years ago

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="20.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.10"
VERSION_ID="20.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

Issue/Bug Description: I recently got a System76 Oryx Pro 7 (FHD screen) system. Everything seem to work fine for now except one essential component: suspend. Everytime I suspend the laptop goes black screen as expected and then immediatly turns back on and shows login prompt, essentially suspend has no effect except screen blinking and a bunch of logs in journalctl saying "system is about to suspend" nothing more. I have tried in both Hybrid mode and Intel only mode; exact same issue.

After some research it appears a service called xhci is blocking suspend. I applied the fix as mentioned in https://gist.github.com/ioggstream/8f380d398aef989ac455b93b92d42048 however it did not work far better: after running suspend with this script I get to a black screen and few seconds later a weird "System76" logo appears and then system reboot by itself (sounds like kernel panic). After reboot journalctl shows the following for the previous boot when grepping "suspend":

May 05 19:35:28 X ModemManager[1083]: <info>  [sleep-monitor] system is about to suspend
May 05 19:35:28 X systemd-logind[3723]: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service not found.

The same error log is shown no matter if intel or hybrid mode.

Steps to reproduce (if you know):

Just suspend

Expected behavior: The system should just go to sleep

Other Notes: On a HP ElliteBook 840 G3 the problem does not appear despite the system being installed by NVIDIA ISO.

EDIT: Is it possible that by any chance when the laptop is suspended there's no LED information? The strange thing is in Intel mode there's a "Resuming" message that occurs after "Lid opened". Does S76 laptops auto wake from suspend like Apple Mac Books?

asifash commented 3 years ago

I'm getting a similar issue on a Razer blade 17 pro. Using systemctl suspend or the suspend button, screen goes black, then it lights back up, back to login screen. if i try to suspend again, it kernel panics. The issue has only cropped up today; not sure what's changed but this didnt happen yesterday. i'm using the Nvidia ISO.

NAME="Pop!_OS" VERSION="20.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 20.04 LTS" VERSION_ID="20.04" HOME_URL="https://pop.system76.com" SUPPORT_URL="https://support.system76.com" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" PRIVACY_POLICY_URL="https://system76.com/privacy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal LOGO=distributor-logo-pop-os

Yuri6037 commented 3 years ago

After some more debugging, it's not kernel panic, otherwise TTY would not work. In this specific case TTY still works and I can even login through raw TTY so Linux kernel still runs fine and that means also no driver/nvidia crash.

After reading the entire log from journalctl, I isolated the software that crashes: it's XOrg. It says something with gdm failure and then terminates, but somehow another process is trying to restart it and it crashes again. It's like a loop: you switch to tty, then back to GDM, login, xorg crashes again, repeat same action and you end up in an inifinite loop of xorg crashing. Stangely the crash always happens in hybrid mode. I will try further to make sure it's the simple fact of having NVIDIA driver running which causes Xorg to crash on suspend.

EDIT: Well bad luck it just crashed again but this time Intel only. So nevermind it's a random failure with an increased probablity when NVIDIA drvier is running.

asifash commented 3 years ago

@Yuri6037, I can access the TTY as well, didnt think to access. I might try rolling back the kernel to 5.11.0.7612 and see if that does anything. What updates were pushed on the pop-os ppa today? This issue has literally only cropped up today for me. My laptop was suspended and woken multiple times yesterday without incident, and its only after installing the latest updates on pop-shop and (not really reading what packages were updated), have these issues come through.

Yuri6037 commented 3 years ago

I tried applying the two kernel parameters that were given. Absolutely no changes. I don't know if it ever worked as unfortunatly I've let the system do updates after creating the session. Perhaps I should have left it as is.

This is a real problem. Until I can get this sleep to work I can't use this laptop: it's supposed to be a work tool and I can't work on something which has a chance of crashing on me while I'm editing some documents...

jacobgkau commented 3 years ago

@Yuri6037 I'm sorry about the suspend trouble with your Oryx Pro. For System76 hardware, it's best to open a support ticket so our support team can assist you directly. They will have access to your hardware configuration and will be able to set up an RMA if any of the hardware is defective.

They will likely ask for logs from the System76 Driver app, so you can help them help you faster by providing those in your initial message (you may need to open the ticket, then send another message with the logs attached.)

Especially if you're not sure whether it ever worked, I would suggest trying a live disk and/or Recovery mode and seeing if suspend/resume works there. If it doesn't, that will point towards a hardware issue; if it does, that would point towards a software or configuration issue.

If your system has more than one stick of RAM, removing one stick and testing with one stick at a time to determine if a bad RAM stick is causing the issue is another good troubleshooting step.

The strange thing is in Intel mode there's a "Resuming" message that occurs after "Lid opened". Does S76 laptops auto wake from suspend like Apple Mac Books?

I'm not sure what comparison you're making with Macbooks, but yes, the laptop should resume from suspend when you open the lid, regardless of how it was put to sleep (lid close, Fn-F12, top-right menu, etc.) A defective lid switch is a possibility (making the laptop think it's being opened when it's not), but would be very rare/unlikely.

System76 customers can reach out to support for technical assistance. For non-System76 hardware, you can seek community support on Reddit or Mattermost.

Yuri6037 commented 3 years ago

@Yuri6037 I'm sorry about the suspend trouble with your Oryx Pro. For System76 hardware, it's best to open a support ticket so our support team can assist you directly. They will have access to your hardware configuration and will be able to set up an RMA if any of the hardware is defective.

They will likely ask for logs from the System76 Driver app, so you can help them help you faster by providing those in your initial message (you may need to open the ticket, then send another message with the logs attached.)

Especially if you're not sure whether it ever worked, I would suggest trying a live disk and/or Recovery mode and seeing if suspend/resume works there. If it doesn't, that will point towards a hardware issue; if it does, that would point towards a software or configuration issue.

If your system has more than one stick of RAM, removing one stick and testing with one stick at a time to determine if a bad RAM stick is causing the issue is another good troubleshooting step.

The strange thing is in Intel mode there's a "Resuming" message that occurs after "Lid opened". Does S76 laptops auto wake from suspend like Apple Mac Books?

I'm not sure what comparison you're making with Macbooks, but yes, the laptop should resume from suspend when you open the lid, regardless of how it was put to sleep (lid close, Fn-F12, top-right menu, etc.) A defective lid switch is a possibility (making the laptop think it's being opened when it's not), but would be very rare/unlikely.

System76 customers can reach out to support for technical assistance. For non-System76 hardware, you can seek community support on Reddit or Mattermost.

Oh ok I see. Thanks a lot for the tip of space bar. I thought you could not boot anything other than main OS on this laptop. So it turns out I was wrong. The machine work flawlessly: when I boot into recovery, then close the lid the power LED starts blinking like my old HP laptop (in non recovery it always stayed on). Then when I open back the lid everything is fine it comes back to the login page. By the way I never expected laptops to wake up automatically that never occured on any of my windows/linux laptops before this is the first time I see auto-wake working.

So that means for sure a software issue on the main partition. My guess is one of the millions of updates that passed broke it.

EDIT: It's neither NVIDIA driver nor kernel: even after downgrading those I still get the same issues.

Marivishnu commented 3 years ago

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="20.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.10"
VERSION_ID="20.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME):

Issue/Bug Description: I recently got a System76 Oryx Pro 7 (FHD screen) system. Everything seem to work fine for now except one essential component: suspend. Everytime I suspend the laptop goes black screen as expected and then immediatly turns back on and shows login prompt, essentially suspend has no effect except screen blinking and a bunch of logs in journalctl saying "system is about to suspend" nothing more. I have tried in both Hybrid mode and Intel only mode; exact same issue.

After some research it appears a service called xhci is blocking suspend. I applied the fix as mentioned in https://gist.github.com/ioggstream/8f380d398aef989ac455b93b92d42048 however it did not work far better: after running suspend with this script I get to a black screen and few seconds later a weird "System76" logo appears and then system reboot by itself (sounds like kernel panic). After reboot journalctl shows the following for the previous boot when grepping "suspend":
May 05 19:35:28 X ModemManager[1083]: <info>  [sleep-monitor] system is about to suspend
May 05 19:35:28 X systemd-logind[3723]: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service not found.
The same error log is shown no matter if intel or hybrid mode.

Steps to reproduce (if you know):
* Just suspend
Expected behavior: The system should just go to sleep

Other Notes: On a HP ElliteBook 840 G3 the problem does not appear despite the system being installed by NVIDIA ISO.

EDIT: Is it possible that by any chance when the laptop is suspended there's no LED information? The strange thing is in Intel mode there's a "Resuming" message that occurs after "Lid opened". Does S76 laptops auto wake from suspend like Apple Mac Books?

Hello, I am using Asus Vivobook 15 X510U with Intel i7 - 8550U, 8 GB RAM, Nvidia MX 150. After a recent update, my laptop is also failing to suspend when the lid closes. When I open the lid again, it shows only the Asus logo and I have to hard reboot the system again. Did you get any solution?

POP!_OS : 20.10 Kernel : 5.11.0-7614-generic

Yuri6037 commented 3 years ago

I have fixed the problem finally! Here are the steps:

First we need to understand why it broke. It appears that initial log I had with nvidia-suspend and nvidia-resume were correct. On my system after the upgrade those files were masked + deleted.
Before anything else unmask both nvidia-suspend and nvidia-resume
Now that we know the cause the fix is to reinstall nvidia-driver 450 then install 460 on top of it and somehow this will make those two missing units back.
Now you can try to close the lid or call suspend

If there are still some problems perhaps you can try adding the two kernel parameters specified in the other suspend related issue.

Marivishnu commented 3 years ago

https://askubuntu.com/questions/840093/suspend-on-lid-close-doesnt-work-16-04?rq=1 This post solved my issue!

asifash commented 3 years ago

I have fixed the problem finally! Here are the steps:

* First we need to understand why it broke. It appears that initial log I had with nvidia-suspend and nvidia-resume were correct. On my system after the upgrade those files were masked + deleted.

* Before anything else unmask both nvidia-suspend and nvidia-resume

* Now that we know the cause the fix is to reinstall nvidia-driver 450 then install 460 on top of it and somehow this will make those two missing units back.

* Now you can try to close the lid or call suspend

If there are still some problems perhaps you can try adding the two kernel parameters specified in the other suspend related issue.

Want to +1 and say this resolved the issue for me as well.