https://bugzilla.kernel.org/show_bug.cgi?id=213323

            Bug ID: 213323
           Summary: ACPI Error: No handler for Region [WST1]
                    (000000000d8f0d66) [GenericSerialBus]
                    (20200925/evregion-132) DELL PowerEdge T40
           Product: ACPI
           Version: 2.5
    Kernel Version: 4.18.0-305.3.1.el8_4.x86_64
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: BIOS
          Assignee: acpi_b...@kernel-bugs.osdl.org
          Reporter: secancri...@gmail.com
        Regression: No

Created attachment 297129
  --> https://bugzilla.kernel.org/attachment.cgi?id=297129&action=edit
ACPI dump for Dell PowerEdge T40

Hello all,

As suggested by Zhang Rui from Intel, I've opened a new bug report related to
the exact same ACPI related issue encountered on Dell Precision 3630, the only
difference is that I have a slightly different model Dell PowerEdge T40.

Every time my system boots up, I receive the following ACPI error (early boot):

[root@vHost ~]# uname -a
Linux vHost 4.18.0-305.3.1.el8_4.x86_64 #1 SMP Mon May 17 10:08:25 EDT 2021
x86_64 x86_64 x86_64 GNU/Linux
[root@vHost ~]# dmesg | grep -i error
[    0.149258] ACPI Error: No handler for Region [WST1] (000000000d8f0d66)
[GenericSerialBus] (20200925/evregion-132)
[    0.149258] ACPI Error: Region GenericSerialBus (ID=9) has no handler
(20200925/exfldio-265)
[    0.149260] ACPI Error: Aborting method \_SB.PCI0.I2C0.PAS1 due to previous
error (AE_NOT_EXIST) (20200925/psparse-531)
[    0.149260] ACPI Error: Aborting method \_GPE._L20 due to previous error
(AE_NOT_EXIST) (20200925/psparse-531)
[    0.149260] ACPI Error: AE_NOT_EXIST, while evaluating GPE method [_L20]
(20200925/evgpe-515)
[    0.736748] pcieport 0000:00:1b.0: error containment capabilities: Int Msg
#0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.738689] ERST: Error Record Serialization Table (ERST) support is
initialized.
[root@vHost ~]# 

I can confirm that this issue is encountered on all Linux distros that I have
installed, regarding which flavour or kernel verion (be it 3.10 / 4.16 / 4.18 /
5.11 or 5.12).

As requested by Zhang, I've done the following troubleshooting steps:

1. output of discovered devices using lspci:

[root@vHost ~]# lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Workstation
Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD
Graphics P630]
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 /
6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal
Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host
Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial
IO I2C Controller #0 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI
Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller
(rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21
(rev f0)
00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI
Controller (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM
(rev 10)
01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection
(rev 03)
[root@vHost ~]# lspci -vvx -s 00:15.0
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial
IO I2C Controller #0 (rev 10)
        DeviceName: Onboard - Other
        Subsystem: Dell Device 095b
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at 4000014000 (64-bit, non-prefetchable) [virtual]
[size=4K]
        Capabilities: [80] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [90] Vendor Specific Information: Len=14 <?>
        Kernel driver in use: intel-lpss
        Kernel modules: intel_lpss_pci
00: 86 80 68 a3 06 01 10 00 10 00 80 0c 10 00 80 00
10: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 5b 09
30: 00 00 00 00 80 00 00 00 00 00 00 00 ff 01 00 00

[root@vHost ~]# 


2. Checking if INT34B2:0 is present:

[root@vHost ~]# ll /sys/bus/acpi/devices/ | grep -i INT34B2
[root@vHost ~]# ll /sys/bus/acpi/devices/ | grep -i INT34B
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT0000:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00/INT0000:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT346F:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00/INT346F:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT3471:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00/INT3471:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT3474:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B6:00/INT3474:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B0:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B0:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B1:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B1:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B3:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B3:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B4:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B5:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B5:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B6:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B6:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B7:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B7:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B8:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B8:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34B9:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B9:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34BA:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34BA:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT34BC:00 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34BC:00
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT3515:01 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B3:00/INT3515:01
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT3515:02 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00/INT3515:02
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 INT3515:03 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B5:00/INT3515:03
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 XXXX0000:02 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B3:00/XXXX0000:02
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 XXXX0000:03 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B3:00/XXXX0000:03
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 XXXX0000:04 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00/XXXX0000:04
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 XXXX0000:05 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B4:00/XXXX0000:05
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 XXXX0000:06 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B5:00/XXXX0000:06
lrwxrwxrwx. 1 root root 0 Jun  2 17:22 XXXX0000:07 ->
../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT34B5:00/XXXX0000:07
[root@vHost ~]# 

As you can see, INT34B2:0 is not present at all.

3. The is no "ACPI enumeration mode" nor "PCI enumeration mode" present in the
BIOS system.

If there's anything else you need, please do not hesitate to reply.

BR,
Cristian

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to