Bug 213099 - ACPI Error: No handler for Region [VRTC] - MSI GE66
Summary: ACPI Error: No handler for Region [VRTC] - MSI GE66
Status: CLOSED DOCUMENTED
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-16 15:35 UTC by ByteEnable
Modified: 2022-06-21 07:56 UTC (History)
4 users (show)

See Also:
Kernel Version: 5.11.20-300.fc34.x86_64
Subsystem:
Regression: No
Bisected commit-id:


Attachments
acpidump output text (1.68 MB, text/plain)
2021-05-16 15:35 UTC, ByteEnable
Details

Description ByteEnable 2021-05-16 15:35:26 UTC
Created attachment 296799 [details]
acpidump output text

The ACPI error below occurs with a frequency of every hour on a MSI GE66 Dragonshield.  I have attached the output of acpidump. 


May 16 05:01:42 ByteEnable kernel: ACPI Error: No handler for Region [VRTC] (00000000aa34c144) [SystemCMOS] (20201113/evregion-130)
May 16 05:01:42 ByteEnable kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
May 16 05:01:42 ByteEnable kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q9A due to previous error (AE_NOT_EXIST) (20201113/psparse-529)

May 16 06:02:35 ByteEnable kernel: ACPI Error: No handler for Region [VRTC] (00000000aa34c144) [SystemCMOS] (20201113/evregion-130)
May 16 06:02:35 ByteEnable kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
May 16 06:02:35 ByteEnable kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q9A due to previous error (AE_NOT_EXIST) (20201113/psparse-529)

May 16 07:03:31 ByteEnable kernel: ACPI Error: No handler for Region [VRTC] (00000000aa34c144) [SystemCMOS] (20201113/evregion-130)
May 16 07:03:31 ByteEnable kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
May 16 07:03:31 ByteEnable kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q9A due to previous error (AE_NOT_EXIST) (20201113/psparse-529)

May 16 08:04:27 ByteEnable kernel: ACPI Error: No handler for Region [VRTC] (00000000aa34c144) [SystemCMOS] (20201113/evregion-130)
May 16 08:04:27 ByteEnable kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
May 16 08:04:27 ByteEnable kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q9A due to previous error (AE_NOT_EXIST) (20201113/psparse-529)

May 16 09:05:23 ByteEnable kernel: ACPI Error: No handler for Region [VRTC] (00000000aa34c144) [SystemCMOS] (20201113/evregion-130)
May 16 09:05:23 ByteEnable kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
May 16 09:05:23 ByteEnable kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q9A due to previous error (AE_NOT_EXIST) (20201113/psparse-529)

May 16 10:06:19 ByteEnable kernel: ACPI Error: No handler for Region [VRTC] (00000000aa34c144) [SystemCMOS] (20201113/evregion-130)
May 16 10:06:19 ByteEnable kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20201113/exfldio-261)
May 16 10:06:19 ByteEnable kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q9A due to previous error (AE_NOT_EXIST) (20201113/psparse-529)
Comment 1 Pablo Cholaky 2021-08-30 21:03:21 UTC
Can confirm exactly the same at MSI Delta 15.

Still happen at Linux 5.14.0
Comment 2 mitzeljg 2021-11-23 18:44:31 UTC
Yep, on the MSI Alpha 15 the exact same error is occurring.
Comment 3 chrisxvigil 2021-12-14 08:13:51 UTC
Same issue on MSI PS63 Modern 8SC
Comment 4 Zhang Rui 2021-12-15 06:12:44 UTC
Does the patch at https://bugzilla.kernel.org/show_bug.cgi?id=205665#c12 help?
Comment 5 Zhang Rui 2022-06-21 07:56:03 UTC
As described in https://bugzilla.kernel.org/show_bug.cgi?id=212131#c18,
"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."

And this also apply to this machine.
The VRTC is just a dummy one.
The error messages are caused by the bogus firmware, and there is no functionality issue.

Bug closed.
Please feel free to reopen it if you found the RTC functionality issue on this model.

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