Bug 212131 - ACPI Error: No handler for Region [VRTC] - Razer Blade 15 Advanced, Razer RZ09-0367
Summary: ACPI Error: No handler for Region [VRTC] - Razer Blade 15 Advanced, Razer RZ0...
Status: CLOSED DOCUMENTED
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-08 10:25 UTC by Gorgo
Modified: 2022-06-21 07:37 UTC (History)
6 users (show)

See Also:
Kernel Version: 5.16.11-76051611-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments
acpidump (1.86 MB, text/plain)
2021-03-08 10:25 UTC, Gorgo
Details
dmesg (110.98 KB, text/plain)
2021-03-08 10:25 UTC, Gorgo
Details
acpidump kernel 5.11 (1.86 MB, text/plain)
2021-03-31 15:59 UTC, Gorgo
Details
dmesg kernel 5.11 (94.82 KB, text/plain)
2021-03-31 16:00 UTC, Gorgo
Details
dmesg from 5.14.1 NixOS on Razer RZ09-0367 (81.61 KB, text/plain)
2021-09-09 17:26 UTC, Victor Lemeshev
Details
acpidump from 5.14.1 NixOS on Razer RZ09-0367 (1.88 MB, text/plain)
2021-09-09 17:27 UTC, Victor Lemeshev
Details
dmesg from 5.14.1 NixOS on Razer RZ09-0367 with patch applied (80.72 KB, text/plain)
2021-09-09 18:29 UTC, Victor Lemeshev
Details

Description Gorgo 2021-03-08 10:25:10 UTC
Created attachment 295723 [details]
acpidump

Hello everyone,
As suggested by @Zhang Rui in bug 205665 I'm opening a new thread because I'm facing the same bug with my Razer Blade 15 Early 2020 ( RZ09-033 5.04 ).  

I added 'button.lid_init_state=open' to my kernel options to avoid laptop suspending 10sec after resuming.

>initrd=\EFI\Pop_OS-9623c65e-537d-46f7-8fc9-fcb4202aeef6\initrd.img root=UUID=9623c65e-537d-46f7-8fc9-fcb4202aeef6 ro quiet loglevel=0 systemd.show_status=false splash button.lid_init_state=open



OS: Pop!_OS 20.10 x86_64 
Host: Blade 15 Advanced Model (Early 2020) - RZ09-033 5.04 
Kernel: 5.8.0-7642-generic 
Shell: bash 5.0.17 
DE: GNOME 3.38.2 
Theme: Pop-dark [GTK2/3] 
CPU: Intel i7-10875H (16) @ 5.100GHz 
GPU: NVIDIA GeForce RTX 2080 SUPER Mobile / Max-Q 
GPU: Intel UHD Graphics 
Memory: 8056MiB / 15867MiB

>mar 08 09:04:39 pop-os kernel: ACPI: Waking up from system sleep state S3
mar 08 09:04:39 pop-os kernel: ACPI Error: No handler for Region [VRTC] (0000000054b52108) [SystemCMOS] (20200528/evregion-127)
mar 08 09:04:39 pop-os kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20200528/exfldio-261)
mar 08 09:04:39 pop-os kernel: No Local Variables are initialized for Method [RTEC]
mar 08 09:04:39 pop-os kernel: No Arguments are initialized for method [RTEC]
mar 08 09:04:39 pop-os kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20200528/psparse-529)
mar 08 09:04:39 pop-os kernel: ACPI Error: Aborting method \RWAK due to previous error (AE_NOT_EXIST) (20200528/psparse-529)
mar 08 09:04:39 pop-os kernel: ACPI Error: Aborting method \_WAK due to previous error (AE_NOT_EXIST) (20200528/psparse-529)
mar 08 09:04:39 pop-os kernel: ACPI Error: AE_NOT_EXIST, While executing method \_WAK (20200528/hwesleep-47)
mar 08 09:04:39 pop-os kernel: ACPI: EC: interrupt unblocked
mar 08 09:04:39 pop-os kernel: pcieport 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
mar 08 09:04:39 pop-os kernel: pcieport 0000:00:1b.0: Intel SPT PCH root port ACS workaround enabled
mar 08 09:04:39 pop-os kernel: pcieport 0000:00:1d.4: Intel SPT PCH root port ACS workaround enabled
mar 08 09:04:39 pop-os kernel: ACPI: EC: event unblocked
mar 08 09:04:39 pop-os kernel: usb usb3: root hub lost power or was reset
mar 08 09:04:39 pop-os kernel: usb usb4: root hub lost power or was reset
mar 08 09:04:39 pop-os kernel: nvme nvme0: Shutdown timeout set to 8 seconds
mar 08 09:04:39 pop-os kernel: nvme nvme0: 16/0/0 default/read/poll queues
mar 08 09:04:39 pop-os kernel: usb 1-7: reset high-speed USB device number 4 using xhci_hcd
mar 08 09:04:39 pop-os kernel: usb 1-9: reset full-speed USB device number 6 using xhci_hcd
mar 08 09:04:39 pop-os kernel: fbcon: Taking over console
mar 08 09:04:39 pop-os kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
mar 08 09:04:39 pop-os kernel: acpi LNXPOWER:06: Turning OFF
mar 08 09:04:39 pop-os kernel: acpi LNXPOWER:02: Turning OFF
mar 08 09:04:39 pop-os kernel: OOM killer enabled.
mar 08 09:04:39 pop-os kernel: Restarting tasks ... 
mar 08 09:04:39 pop-os kernel: usb 2-1: USB disconnect, device number 3
mar 08 09:04:39 pop-os kernel: ax88179_178a 2-1:1.0 enx0050b617b2cb: unregister 'ax88179_178a' usb-0000:00:14.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet
mar 08 09:04:39 pop-os kernel: done.
mar 08 09:04:39 pop-os kernel: ax88179_178a 2-1:1.0 enx0050b617b2cb: Failed to read reg index 0x0002: -19
mar 08 09:04:39 pop-os kernel: ax88179_178a 2-1:1.0 enx0050b617b2cb: Failed to write reg index 0x0002: -19
mar 08 09:04:39 pop-os kernel: Console: switching to colour frame buffer device 240x67
mar 08 09:04:39 pop-os kernel: thermal thermal_zone8: failed to read out thermal zone (-61)
mar 08 09:04:39 pop-os daemon[1007]: Power source changed! Now BAT
mar 08 09:04:39 pop-os acpid[967]: client 2468[0:0] has disconnected
mar 08 09:04:39 pop-os pipewire[2090]: [W][000017951.949864][main-loop.c:157 pw_main_loop_run()] main-loop 0x56035116d0a0: iterate error -4 (Interrupted system call)
mar 08 09:04:39 pop-os kernel: battery: [Firmware Bug]: battery: (dis)charge rate invalid.
mar 08 09:04:39 pop-os pipewire[2111]: [W][000017951.953071][main-loop.c:157 pw_main_loop_run()] main-loop 0x556ee1d01e10: iterate error -4 (Interrupted system call)
mar 08 09:04:39 pop-os systemd-logind[1029]: Lid opened.
Comment 1 Gorgo 2021-03-08 10:25:50 UTC
Created attachment 295725 [details]
dmesg
Comment 2 Gorgo 2021-03-31 15:58:52 UTC
The problem is still valid for kernel 5.11

```
gorgo@pop-os:~$ uname -a
Linux pop-os 5.11.0-7612-generic #13~1616168001~20.10~cf74746-Ubuntu SMP Mon Mar 29 17:37:00 UTC  x86_64 x86_64 x86_64 GNU/Linux
```

From dmesg:


>mar 31 17:51:36 pop-os kernel: ACPI: EC: EC started
mar 31 17:51:36 pop-os kernel: ACPI: EC: interrupt blocked
mar 31 17:51:36 pop-os kernel: ACPI Error: No handler for Region [VRTC] (000000008c740031) [SystemCMOS] (20201113/evregion-130)
mar 31 17:51:36 pop-os kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
mar 31 17:51:36 pop-os kernel: 
mar 31 17:51:36 pop-os kernel: No Local Variables are initialized for Method [RTEC]
mar 31 17:51:36 pop-os kernel: 
mar 31 17:51:36 pop-os kernel: No Arguments are initialized for method [RTEC]
mar 31 17:51:36 pop-os kernel: 
mar 31 17:51:36 pop-os kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0.RTEC due to previous error (AE_NOT_EXIST) (20201113/psparse-529)
mar 31 17:51:36 pop-os kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC0._REG due to previous error (AE_NOT_EXIST) (20201113/psparse-529)
mar 31 17:51:36 pop-os kernel: ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62
mar 31 17:51:36 pop-os kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions
mar 31 17:51:36 pop-os kernel: ACPI: Interpreter enabled
...
Comment 3 Gorgo 2021-03-31 15:59:48 UTC
Created attachment 296161 [details]
acpidump kernel 5.11
Comment 4 Gorgo 2021-03-31 16:00:09 UTC
Created attachment 296163 [details]
dmesg kernel 5.11
Comment 5 Victor Lemeshev 2021-09-09 17:24:12 UTC
Hi!


I'm encountering the same issue on a Razer RZ09-0367* laptop. Kernel is 5.14.1 on a NixOS nightly.


After suspend (both from lid closing and from `systemctl suspend`) laptop comes back to life but the built-in monitor is extremely dim (any external monitors work well).


dmesg shows the same ACPI error that @Gorgo's. I've tried playing with `acpi_osi` and `button=...` parameters to no avail.


Attaching dmesg and acpidump.
Comment 6 Victor Lemeshev 2021-09-09 17:26:59 UTC
Created attachment 298721 [details]
dmesg from 5.14.1 NixOS on Razer RZ09-0367
Comment 7 Victor Lemeshev 2021-09-09 17:27:58 UTC
Created attachment 298723 [details]
acpidump from 5.14.1 NixOS on Razer RZ09-0367
Comment 8 Victor Lemeshev 2021-09-09 18:29:26 UTC
Created attachment 298725 [details]
dmesg from 5.14.1 NixOS on Razer RZ09-0367 with patch applied

Applied the patch from https://bugzilla.kernel.org/show_bug.cgi?id=205665 (https://bugzilla.kernel.org/attachment.cgi?id=295949&action=diff&collapsed=&headers=1&format=raw)

ACPI Errors after `systemctl susped` are no longer present but the display is still dim. I didn't touch the lid, just suspended via command and woke via keyboard.
Comment 9 Victor Lemeshev 2021-09-10 18:41:49 UTC
Okay, the dimness was due to NVIDIA graphic card not controlling backlight.


After adding `video.use_native_backlight=1` and setting `Option "RegistryDwords" "EnableBrightnessControl=1"` in XOrg conf the brightness restores after suspend.

So, given that ACPI errors go away with the patch and I found a way to fix screen issues there is nothing else from my side on this bug.
Comment 10 Dimitar Atanasov 2021-11-05 13:00:59 UTC
Patch will render lid switch as unusable, with it when lid closed laptop will stay on, open and close will not be detected. Razer Blade Studio 2020
Comment 11 Zhang Rui 2021-12-15 06:09:03 UTC
(In reply to Dimitar Atanasov from comment #10)
> Patch will render lid switch as unusable, 

are you referring to https://bugzilla.kernel.org/show_bug.cgi?id=205665#c12 or some other patch?
Comment 12 Zhang Rui 2021-12-15 06:10:52 UTC
(In reply to Victor Lemeshev from comment #9)
> Okay, the dimness was due to NVIDIA graphic card not controlling backlight.
> 
> 
> After adding `video.use_native_backlight=1` and setting `Option
> "RegistryDwords" "EnableBrightnessControl=1"` in XOrg conf the brightness
> restores after suspend.
> 
> So, given that ACPI errors go away with the patch and I found a way to fix
> screen issues there is nothing else from my side on this bug.

So do I understand correctly that the problem described in this bug report can be fixed by the patch at https://bugzilla.kernel.org/show_bug.cgi?id=205665#c12?
If yes, I'm considering submit/rework the patch for upstream kernel.
Comment 13 Dimitar Atanasov 2021-12-15 09:22:37 UTC
(In reply to Zhang Rui from comment #11)
> (In reply to Dimitar Atanasov from comment #10)
> > Patch will render lid switch as unusable, 
> 
> are you referring to https://bugzilla.kernel.org/show_bug.cgi?id=205665#c12
> or some other patch?

Yes I refer to same patch, in Razer Blade lid switch is connected to EC, which is seen by system as USB keyboard. Using this patch will bypass this detection and will render lid switch unusable. Main RTC of the system is detected as supposed with or without this patch. Just EC controller have it's own RTC which is not used at all but is described in ACPI entry. So in Razer laptops this patch solve nothing (even ACPI error is there) but breaks lid switch.
Comment 14 Zhang Rui 2021-12-15 14:30:36 UTC
(In reply to Dimitar Atanasov from comment #13)
> (In reply to Zhang Rui from comment #11)
> > (In reply to Dimitar Atanasov from comment #10)
> > > Patch will render lid switch as unusable, 
> > 
> > are you referring to https://bugzilla.kernel.org/show_bug.cgi?id=205665#c12
> > or some other patch?
> 
> Yes I refer to same patch, in Razer Blade lid switch is connected to EC,
> which is seen by system as USB keyboard. Using this patch will bypass this
> detection

hmmm, how does it bypass the detection?

> and will render lid switch unusable. Main RTC of the system is
> detected as supposed with or without this patch. Just EC controller have
> it's own RTC which is not used at all but is described in ACPI entry. So in
> Razer laptops this patch solve nothing (even ACPI error is there)

I agree. This VRTC operation region looks like a dummy object, no one is using it actually.
Comment 15 Gorgo 2022-03-18 10:08:40 UTC
Any updates on this? Thank you!
Comment 16 Patrick White 2022-03-27 18:41:22 UTC
I too experience this exact issue, on my Razor Blade laptop. Am I right in thinking the aforementioned patch doesn't actually work?
Comment 17 Eric Walstrom 2022-05-05 07:16:15 UTC
I'm experiencing a similar issue on a Razer machine as well. Mine refuses to boot with the following message:

[0.394444] ACPI Error: No handler for Region [VRTC] (00000000b44dee92) [SystemCMOS] (20210730/euregion-130)
[0.394449] ACPI Error: Region SystemCMOS (ID=5) has no handler (20210730/exfldio-261)
[0.394457] ACPI Error: Aborting method N_SB.PCOO.LPCB.ECO.RTEC due to previous error (AE_HOT_EXIST) (20210730/psparse-529)
[0.394460] ACPI Error: Aborting method N_SII.PCOO.LPCB.ECO._REG due to previous error (AE_MOT_EXIST) (20210730/psparse-529)
[0.994991] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[0.995017] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.0-25-generic #25-Ubuntu
[0.995039] Hardware name: Razer Blade 17 (2022) - RZ09-0423/DI780, BIOS 1.06 01/27/2022
[0.995060] Call Trace:
[0.995071] <TASK>
[0.995084] show_stack.0x52/0x58
[0.995105] dump_stack_lu1.0x4a/Ox5f
[0.995126] dump_stack.0x10/0x12
[0.995143] panic.0x149/0x321
[0.995160] mount_block_root.0x144/0x1d9
[0.995182] mount_root.0x10c/Ox118
[0.995200] prepare_namespace.0x13f/Ox18d
[0.995220] kernel_init_freeable.0x18c/Ox1b1
[0.995243] ? rest_init.0x100/0x100
[0.995264] kernel_init.0x1b/0x150
[0.995283] ? rest init.0x100/0x100
[0.995302] ret_from_fork.0x1f/0x30
[0.995324] </TASK>
[0.995471] Kernel Offset: 0x1800000 from Oxffffffff81000000 (relocation range: Oxffffffff80000000-Oxffffffffbfffffff)
[0.995524] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) ]---
Comment 18 Zhang Rui 2022-06-21 07:37:28 UTC
There are too much reports about different issues from different reporters in this bug report.

The tile is about the VRTC error messages during boot, and there is a patch to workaround this, but as @Antanasov said, "Main RTC of the system is detected as supposed with or without this patch. Just EC controller have it's own RTC which is not used at all but is described in ACPI entry. So in Razer laptops this patch solve nothing (even ACPI error is there) but breaks lid switch."
I will not upstream this patch.

So the VRTC issue is caused by bogus firmware which exposes a dummy rtc device, and the error messages doesn't bring any functionality issue.

Thus I will close this bug report.

For the other issues, please file separate bug reports.

Note You need to log in before you can comment on or make changes to this bug.