Arch Linux

netpro2k

Member

Registered: 2019-10-23

Posts: 2

[SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

Just setup Arch on my new 2019 model Razer Blade 15 Advanced and am having issues with resume after suspend. I previously had an older Razer (2017 model I think) laptop which I used Arch on for the past few years without issue. I did have to use the button.lid_init_state=open kernel param on both this and my older machine to prevent it from suspend looping on resume, but still have an issue where resuming stalls for ~50-60 seconds. After the stall things seem to work fine (though I haven't tried with any USB-C devices, I suspect they may not recover).

Looking at dmesg it seems like the stall is caused by ucsi_ccg timing out: (log of a suspend and resume)

[ 2660.668510] PM: suspend entry (deep)
[ 2660.687187] Filesystems sync: 0.018 seconds
[ 2660.760595] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2660.762129] OOM killer disabled.
[ 2660.762130] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2660.763513] printk: Suspending console(s) (use no_console_suspend to debug)
[ 2660.764141] wlp2s0: deauthenticating from b4:fb:e4:72:0b:f1 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 2662.420713] ACPI: EC: interrupt blocked
[ 2662.523690] ACPI: Preparing to enter system sleep state S3
[ 2662.527039] ACPI: EC: event blocked
[ 2662.527041] ACPI: EC: EC stopped
[ 2662.527042] PM: Saving platform NVS memory
[ 2662.527061] Disabling non-boot CPUs ...
[ 2662.528787] smpboot: CPU 1 is now offline
[ 2662.531546] smpboot: CPU 2 is now offline
[ 2662.534179] smpboot: CPU 3 is now offline
[ 2662.536832] smpboot: CPU 4 is now offline
[ 2662.539510] smpboot: CPU 5 is now offline
[ 2662.542265] smpboot: CPU 6 is now offline
[ 2662.544998] smpboot: CPU 7 is now offline
[ 2662.547477] smpboot: CPU 8 is now offline
[ 2662.550028] smpboot: CPU 9 is now offline
[ 2662.552511] smpboot: CPU 10 is now offline
[ 2662.555002] smpboot: CPU 11 is now offline
[ 2662.560929] ACPI: Low-level resume complete
[ 2662.561041] ACPI: EC: EC started
[ 2662.561042] PM: Restoring platform NVS memory
[ 2662.562427] Enabling non-boot CPUs ...
[ 2662.562461] x86: Booting SMP configuration:
[ 2662.562462] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 2662.563144] intel_pstate: Disabling energy efficiency optimization
[ 2662.563267] CPU1 is up
[ 2662.563289] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 2662.563871] CPU2 is up
[ 2662.563887] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 2662.564456] CPU3 is up
[ 2662.564478] smpboot: Booting Node 0 Processor 4 APIC 0x8
[ 2662.565045] CPU4 is up
[ 2662.565062] smpboot: Booting Node 0 Processor 5 APIC 0xa
[ 2662.565642] CPU5 is up
[ 2662.565659] smpboot: Booting Node 0 Processor 6 APIC 0x1
[ 2662.566274] CPU6 is up
[ 2662.566291] smpboot: Booting Node 0 Processor 7 APIC 0x3
[ 2662.566964] CPU7 is up
[ 2662.566984] smpboot: Booting Node 0 Processor 8 APIC 0x5
[ 2662.567565] CPU8 is up
[ 2662.567583] smpboot: Booting Node 0 Processor 9 APIC 0x7
[ 2662.568165] CPU9 is up
[ 2662.568182] smpboot: Booting Node 0 Processor 10 APIC 0x9
[ 2662.568794] CPU10 is up
[ 2662.568810] smpboot: Booting Node 0 Processor 11 APIC 0xb
[ 2662.569419] CPU11 is up
[ 2662.572302] ACPI: Waking up from system sleep state S3
[ 2662.572858] ACPI Error: No handler for Region [VRTC] (00000000a5952eb6) [SystemCMOS] (20190703/evregion-127)
[ 2662.572860] ACPI Error: Region SystemCMOS (ID=5) has no handler (20190703/exfldio-261)
[ 2662.572863] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20190703/psparse-529)
[ 2662.572866] ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20190703/psparse-529)
[ 2662.572868] ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20190703/psparse-529)
[ 2662.572870] ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20190703/hwesleep-47)
[ 2662.573613] ACPI: EC: interrupt unblocked
[ 2662.735951] ACPI: EC: event unblocked
[ 2662.753704] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[ 2662.850875] nvme nvme0: 12/0/0 default/read/poll queues
[ 2662.919220] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
[ 2662.928180] iwlwifi 0000:02:00.0: BIOS contains WGDS but no WRDS
[ 2662.978979] usb 1-7: reset high-speed USB device number 3 using xhci_hcd
[ 2663.327914] usb usb3: root hub lost power or was reset
[ 2663.327915] usb usb4: root hub lost power or was reset
[ 2664.318641] ucsi_ccg 0-0008: i2c_transfer failed -110
[ 2709.401962] ucsi_ccg 0-0008: PPM NOT RESPONDING
[ 2709.401973] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 [ucsi_ccg] returns -110
[ 2709.401976] PM: Device 0-0008 failed to resume: error -110
[ 2709.417481] acpi LNXPOWER:08: Turning OFF
[ 2709.418449] acpi LNXPOWER:03: Turning OFF
[ 2709.420201] acpi LNXPOWER:02: Turning OFF
[ 2709.421136] OOM killer enabled.
[ 2709.421137] Restarting tasks ... done.
[ 2709.431165] audit: type=1130 audit(1571816457.863:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2709.528479] PM: suspend exit

Looking at the kernel mailing list it does seem like some work has been done on this module recently (unclear if the patches have landed yet, or if they will fix this issue). Any thoughts on fixes or workaround?

Last edited by netpro2k (2019-10-23 23:56:28)

igelbox

Member

Registered: 2016-09-16

Posts: 1

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

I just solved this issue for my MSI GS65. The solution is to "blacklist i2c_nvidia_gpu" (see https://bugzilla.redhat.com/show_bug.cgi?id=1720876).

Last edited by igelbox (2019-10-23 13:39:14)

netpro2k

Member

Registered: 2019-10-23

Posts: 2

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

Awesome! Blacklisting `i2c_nvidia_gpu` did the trick! How did you go about narrowing that down?

theodore

Member

Registered: 2008-09-09

Posts: 151

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

@igelbox thanks for reporting the solution, I will try it once I am back home as well.
@netpro2k I am owing the same machine, and I was facing the same issue as well other strange issues with the resume from suspend. Thus, I would like to ask you some questions if not a problem.

1. Are you still have the button.lid_init_state=open enabled. Initially I had it also enabled since I thought that this might solve the problem but since I noticed that there was no affect at the end, currently I have removed it.
2. Which desktop manager are you using? Here I am with Plasma kde.
3. Most important have you tried to suspend (either using the menu option / command line with systemctl suspend or by closing the lid) and having an external screen plugged in (in any of the 3 external outputs i.e. hdmi, usb-c, mD). In my case most of the time when the external screen is connected my session restarts and thus I am losing my previous windows and work, this issue is more intense, almost always I would say, when I suspend/resume by closing/opening the lid respectively. Have you faced any similar issues? I would appreciate if you could try it with an external screen connected if possible and report back.

Last edited by theodore (2019-10-24 09:59:01)

labotsirc

Member

Registered: 2013-08-21

Posts: 108

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

Dear members,
I am facing the same issue with a razer blade 15 advanced late 2019. I tried blacklisting the module earlier mentioned, it wakes up after i close the lip or sleep, but after a few seconds gnome crashes and it takes me again to the login screen. From there, it keeps crashing every time I login, ussually after a few seconds. Therefore I removed the blacklist.

One thing I noticed, is that without any blacklist the laptop does wake up, its just that it takes about 20 seconds to do it, dont know why. But waking the laptop this way makes the system not crash afterwards, so I am keeping it this way until I find a better solution.

What are you using? X, Wayland?

theodore

Member

Registered: 2008-09-09

Posts: 151

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

I am with X and KDE plasma. Could you also please try what I am suggesting with an external screen if possible. I am curious to see whether other users with blade have the same issue (though my feeling is that the problem is related with the nvidia drivers and xrandr).

Lomelgande

Member

Registered: 2019-12-29

Posts: 1

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

I have the Razer Blade Stealth 13 late 2019 model with the GTX 1650 with Ubuntu 19.10 installed (I know it isn't Arch but I figured it is worth posting as I am experiencing the same thing that labotsirc is describing). This is the output of the screen after the laptop wakes up each time (similar to snippets of what netpro2k posted)

ACPI Error: No handler for Region [VRTC] (0000000051cd48ee) [SystemCMOS] (20190703/evregion-127)
ACPI Error: Region SystemCMOS (ID = 5) has no handler (20190703/exfldlo-261)
ACPI Error: Aborting method \_SB.PCIO.LPCB.ECO.RTEC due to previous error (AE_NOT_EXIST) (20190703/psparse-529)
ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20190703/psparse-529)
ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20190703/psparse-529)
ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20190703/hwesleep-47)
iwlfifi 0000:00:14.3: BIOS contains WGDS but no WRDS

Last edited by Lomelgande (2019-12-29 00:15:28)

theodore

Member

Registered: 2008-09-09

Posts: 151

Re: [SOLVED] Razer Blade 15 Adv 2019 resume from suspend stall

@Lomelgande I am getting the same errors, actually I think everyone with a latest razer laptop gets it.
Quick question is this happening by applying suspend with closing/opening the lid or also by suspending from the menu command?

If it the first case then I think it is related with how the _WAK acpi output is addressed based on the DSDT table (I am describing a similar issue related to how the acpi status is not updated when I open the screen here, see the first two links that I have linked in my thread they actually talk how to patch the DSDT table in order the _WAK to actually change acpi lid status). My guess is that it has to do with the manufacturer and the latest kernel is not yet updated to recognize how razer (maybe also other manufacturers) handles this hardware triggering (I guess there might need to be some bug report as well to the kernel bugzilla).

Last edited by theodore (2019-12-29 03:09:28)