Bug 212131

Created attachment 295725 [details]
dmesg

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
...

Created attachment 296161 [details]
acpidump kernel 5.11

Created attachment 296163 [details]
dmesg kernel 5.11

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.

Created attachment 298721 [details]
dmesg from 5.14.1 NixOS on Razer RZ09-0367

Created attachment 298723 [details]
acpidump from 5.14.1 NixOS on Razer RZ09-0367

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.

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.

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

(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?

(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.

(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.

(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.

Any updates on this? Thank you!

I too experience this exact issue, on my Razor Blade laptop. Am I right in thinking the aforementioned patch doesn't actually work?

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) ]---

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.