[ 0.172384] ACPI Exception: Could not find/resolve named package element: OC06 (20170831/dspkginit-381) [ 0.172444] ACPI Exception: Could not find/resolve named package element: OC07 (20170831/dspkginit-381)

This change was made by a bot.

This should be an ACPI BIOS bug, and there is not much to be done in Linux.

An acpidump log (sudo acpidump > acpi.log) is required for more analysis of what functions are impacted.

sudo acpidump > acpi.log

dmesg|grep "ACPI Warning"
[ 23.405042] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x000000000000049F (\_SB.PCI0.SBRG.GPIO) (20170831/utaddress-247)
[ 23.405056] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x000000000000049F (\_SB.PCI0.SBRG.GPIO) (20170831/utaddress-247)

acpi.log

"
Firmware Warning (ACPI): Incorrect checksum in table [OEMB] - 0x00, should be 0xFB (20180105/tbprint-239)
OEMB @ 0x0000000000000000
  0000: 4F 45 4D 42 46 00 00 00 01 00 41 20 4D 20 49 20 OEMBF.....A M I
  0010: 41 4D 49 5F 4F 45 4D 20 09 06 00 06 4D 53 46 54 AMI_OEM ....MSFT
  0020: 97 00 00 00 0D 05 00 00 00 00 30 00 00 F8 FF 00 ..........0.....
  0030: 00 0C 00 00 00 02 00 00 00 00 30 00 00 00 D0 00 ..........0.....
  0040: 00 00 00 00 00 00
"

The error messages are caused by BIOS bugs, and they cannot be fixed in Ubuntu.

OC07 error in descriptions is declared but not defined in ACPI DSDT, i.e. External (OC07, UnknownObj).

The OEMB in #6 has a checksum (i.e. one of OEMx) is a OEM-specific table and that's probably used in Windows only (maybe a workaround).

Many ACPI functions are optional and it is sometimes okay to fail when these features are not used or can be disabled. If you have not obvious failures you can ignore them.

#5 simply complains that ACPI BIOS can directly access I/O ports and Linux kernel is not fond of it. The warnings are very often harmless.

Changing boot options "noapic acpi=off"
Disable Advanced Configuration and Power Interface.
The error with that disappears.
System hold is not working, power management is not working.
Linux is running and no problem is seen.
The browser allows me to write this message.
This computer hardware is aged from 2006.
Replacing with a new one solves the problem.
New problems may be related to the new BIOS / UEFI.
Unified Extensible Firmware Interface
Linux Ubuntu Operating System supports UEFI
Equipment from different manufacturers is possible.

sudo gedit /etc/default/grub

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic acpi=off"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_GFXPAYLOAD_LINUX=None

Problem with booting Linux Ubuntu on UEFI hardware.
Samsung Ultrabook
"UEFI boot bricks SAMSUNG 530U3C laptop
+ UEFI boot live-usb bricks SAMSUNG 530U3C laptop"
{https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557}

UEFI - protection of the so-called intellectual property of computer hardware developers
https://help.ubuntu.com/community/Installation/UEFI-and-BIOS

The error occurs after updating to "Ubuntu 20.04.1 LTS"
sudo do-release-upgrade
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"

It is slightly different in the way the bug report is presented.

[ 0.256863] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - OC06 (20190816/dspkginit-438)
[ 0.256924] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - OC07 (20190816/dspkginit-438)

[ 1.942168] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x000000000000049F (\_SB.PCI0.SBRG.GPIO) (20190816/utaddress-204)
[ 1.942179] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.015158] ACPI Warning: SystemIO range 0x0000000000000400-0x000000000000041F conflicts with OpRegion 0x0000000000000400-0x000000000000040F (\_SB.PCI0.SBRG.ASOC.SMRG) (20190816/utaddress-204)
[ 2.015171] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.437201] gpio_ich gpio_ich.2.auto: ACPI BAR is busy, GPI 0 - 15 unavailable
[ 17.635992] parport_pc 00:02: reported by Plug and Play ACPI

ACPI Error: AE_NOT_FOUND

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

Product: ACPI
Component: ACPICA-Core
Hardware: x86-64 Linux

Many OEMs don't implement ACPI as fully as, perhaps, they should. There
are stories of certain functions being unavailable unless the operating
system declares itself to be "Windows"

"OC07 error in descriptions is declared but not defined in ACPI DSDT, i.e. External (OC07, UnknownObj)."

"The OEMB in #6 has a checksum (i.e. one of OEMx) is a OEM-specific table and that's probably used in Windows only (maybe a workaround)."

ACPI Machine Language (AML)
https://wiki.osdev.org/AML

The programming language equivalent for AML.
ASL is compiled into AML images.
This is the language that the DSDT is written in.

If you need to fix your DSDT, you'll have to write at least a little bit of ASL.

Differentiated System Description Table (DSDT)

An OEM must supply a DSDT to an ACPI-compatible OS.

"The DSDT contains the Differentiated Definition Block, which supplies the implementation and configuration information about the base system. The OS always inserts the DSDT information into the ACPI Namespace at system boot time and never removes it."

Missing or incompletely supported functionality in /proc/acpi
May be a buggy DSDT.

/sys/firmware/acpi/tables/DSDT
/sys/firmware/acpi/tables/OEMB

"ASL is compiled into AML images."
https://www.acpica.org/downloads

# SSDT_FILES=`ls /sys/firmware/acpi/tables/ | grep SSDT`
# for file in $SSDT_FILES ; do cat "/sys/firmware/acpi/tables/$file" > "$file.dat"; done
# cat /sys/firmware/acpi/tables/DSDT > DSDT.dat

To decompile

$ iasl -d DSDT.dat
$ iasl -d SSDT*.dat

"Old and historical" acpi.sourceforge.net" "http://acpi.sourceforge.net/dsdt/index.php"
"https://www.intel.com/content/www/us/en/design/resource-design-center.html"

sudo apt update
sudo apt upgrade
apt install iasl "or" apt install acpica-tools

iasl was written by Robert Moore <email address hidden>

apt install fwts libfwts1 libfwtsiasl1 libfwtsacpica1

fwts (20.03.00-0ubuntu1) focal; urgency=medium

  [Colin Ian King]
  * ACPI: crsdump: include crsdump.h in crsdump.h, rename guard macro
  * acpi: madt: unconstify data argument
  * lib: fwts_summary: fix build warning with gcc-10
  * Makfile: add more warning flags to ensure we catch more issues

  [Ivan Hu]
  * acpi: msdm: fix print typo
  * lib: add kernel lockdown check
  * uefi: check the kernel lockdown for uefi tests

 -- Alex Hung <email address hidden> Mon, 23 Mar 2020 12:42:11 -0600

fwts (20.02.00-0ubuntu1) focal; urgency=medium

  [Alex Hung]
  * fwts_hwinfo: add device check for Type-C
  * fwts_hwinfo: fix copy & paste typos
  * fwts_hwinfo: add device check for disks
  * fwts_hwinfo: add device check for attached monitors
  * live-image: replace hard-coded "oem-tests.lst" by a variable
  * live-image: add an option for creating oem-tests.lst

  [Colin Ian King]
  * ACPICA: Update to version 20200214
  * fwts-test/syntaxcheck: sync regression log with latest ACPICA output

  [Ivan Hu]
  * auto-packager: mkpackage.sh: remove disco

 -- Ivan Hu <email address hidden> Wed, 26 Feb 2020 09:39:35 +0800

$ sudo cat /sys/firmware/acpi/tables/DSDT > DSDT.dat
$ iasl -d DSDT.dat

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20190509
Copyright (c) 2000 - 2019 Intel Corporation

File appears to be binary: found 8931 non-ASCII characters, disassembling
Binary file appears to be a valid ACPI table, disassembling
Input file DSDT.dat, Length 0x68D5 (26837) bytes
ACPI: DSDT 0x0000000000000000 0068D5 (v01 A0452 A0452001 00000001 INTL 02002026)
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output: DSDT.dsl - 296332 bytes
$

 //////////////////////////////////////////////////////////////////////////

 * Disassembling to symbolic ASL+ operators
 *
 * Disassembly of DSDT.dat, Sun Dec 13 20:41:17 2020
 *
 * Original Table Header:
 * Signature "DSDT"
 * Length 0x000068D5 (26837)
 * Revision 0x01 **** 32-bit table (V1), no 64-bit math support
 * Checksum 0xE6
 * OEM ID "A0452"
 * OEM Table ID "A0452001"
 * OEM Revision 0x00000001 (1)
 * Compiler ID "INTL"
 * Compiler Version 0x02002026 (33562662)
 */
DefinitionBlock ("", "DSDT", 1, "A0452", "A0452001", 0x00000001)
{
    External (OC06, UnknownObj)
    External (OC07, UnknownObj)

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
[ 0.256863] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - OC06 (20190816/dspkginit-438)
[ 0.256924] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - OC07 (20190816/dspkginit-438)
/////////////////////////////////////////////////////////////////////////////////

Results generated by fwts: Version V20.03.00 (2020-03-23 18:42:42).

//////////////////////////////////////////////////////////////
Test 2 of 4: Test DMI/SMBIOS tables for errors.
SMBIOS table loaded from /sys/firmware/dmi/tables/DMI
PASSED: Test 2, Entry @ 0x000f04d0 'BIOS Information (Type 0)'
FAILED [MEDIUM] DMIProductVersion: Test 2, String index 0x03 in table entry
'System Information (Type 1)' @ 0x000f0512, field 'Version', offset 0x06 has a
default value 'System Version' and probably has not been updated by the BIOS
vendor.

ADVICE: The DMI table contains data which is clearly been left in a default
setting and not been configured for this machine. Somebody has probably
forgotten to define this field and it basically means this field is effectively
useless. Note that the kernel uses this field so it probably should be corrected
to ensure the kernel is using sane values.

FAILED [MEDIUM] DMISerialNumber: Test 2, String index 0x04 in table entry
'System Information (Type 1)' @ 0x000f0512, field 'Serial Number', offset 0x07
has a default value 'System Serial Number' and probably has not been updated by
the BIOS vendor.
/////////////////////////////////////////////////////////////

https://github.com/torvalds/linux/tree/master/drivers/acpi
https://wiki.ubuntu.com/KernelTeam/HardwareEnableWithDSDT
https://www.kernel.org/doc/Documentation/acpi/initrd_table_override.txt

The ICH chips have their GPIO pins organized in 2 or 3 independent
groups of 32 GPIO pins.

It can happen that the ACPI BIOS wants to make use of pins in one group, preventing the OS to access these.

This doesnot prevent the OS from accessing the other group(s).

This is the case for example on my Asus board.

The ACPI BIOS wants to control GPIO 18 (group 1), while I (the OS) need to control
GPIO 52 and 53 (group 2) for SMBus multiplexing.

So instead of checking for ACPI resource conflict on the whole I/O
range, check on a per-group basis, and consider it a success if at
least one of the groups is available for the OS to use.

lpc_ich: Resource conflict(s) found affecting gpio_ich

https://github.com/torvalds/linux/blame/master/drivers/mfd/lpc_ich.c
https://github.com/torvalds/linux/blob/master/drivers/gpio/gpio-ich.c
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f600ada70beeb1dfe08e11e871bf31015aa0a3d

Old antique computer hardware.
No updates available.
No BIOS update.
https://www.asus.com/us/Motherboards/P5GPLX_SE/HelpDesk_BIOS/

lpc-ich: Resource conflict(s) found affecting gpio_ich
kernel module: lpc-ich.ko and gpio_ich.ko driver conflicts between
Intel hardware chipset Intel ICH6
https://www.intel.pl/content/www/pl/pl/io/io-controller-hub-6-datasheet.html

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/mfd/lpc_ich.c

Makefile
-----------------------

KERNELRELEASE ?= $(shell uname -r)
KERNEL_DIR ?= /lib/modules/$(KERNELRELEASE)/build
PWD := $(shell pwd)

obj-m := lpc_ich.o

all:
 $(MAKE) -C $(KERNEL_DIR) M=$(PWD) modules

install:
 $(MAKE) -C $(KERNEL_DIR) M=$(PWD) modules_install

clean:
 $(MAKE) -C $(KERNEL_DIR) M=$(PWD) clean

insmod:
 sudo insmod lpc_ich.ko

rmmod:
 sudo rmmod lpc_ich.ko

-----------------------

$ make
$ ls
lpc_ich.c lpc_ich.mod lpc_ich.mod.o Makefile Module.symvers
lpc_ich.ko lpc_ich.mod.c lpc_ich.o modules.order
$ sudo make install

https://www.kernel.org/doc/html/v4.18/process/applying-patches.html
https://askubuntu.com/questions/11249/correct-way-to-apply-patches-to-your-kernel

GNU patch command

$ patch --version
GNU patch 2.7.6
Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc.
Copyright (C) 1988 Larry Wall

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Larry Wall and Paul Eggert

https://lore.kernel.org/patchwork/patch/736648/

PATCH for lpc_ich.c

https://help.ubuntu.com/community/Kernel/Compile
https://www.kernel.org
https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/
https://patchwork.kernel.org

GNU diff and patch command
https://www.thegeekstuff.com/2014/12/patch-command-examples/

The attachment "lpc_ich.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]