ACPI Errors with 8-socket DCPMM system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
intel |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Description
A customer reporting ACPI errors during Linux boot in an 8 socket glueless system with 6 DCPMM modules installed per socket. After OS has completed initialization, any attempt to use NDCTL or IPMCTL results in a process or system hang. The system boots and the apps are ok when reducing the system configuration to 6 sockets. Log extract is below.
A web search turned up what looks like the same problem. See https:/
Can you confirm if it is the same problem described below (it looks like it is) and if the proposed kernel change describe in the link is the correction?
Customer has checked kernel.org and the latest versions of the affected files do not have kernel change.
They are validating RedHat and Suse Enterprise for 8+ socket system with maximum DCPMMs installed.
Are there other items that must be updated to go along with the kernel change?
These messages are extracted from the start-up log showing the OS and Kernel versions plus the ACPI errors.
Welcome to SUSE Linux Enterprise Server 12 SP4 (x86_64) - Kernel 4.12.14-
ACPI Error: Could not allocate new OwnerId (255 max), AE_OWNER_ID_LIMIT (20170303/
Merged for v5.4:
67a72420a326 ACPICA: Increase total number of possible Owner IDs
Target Release: 20.04
Target Kernel: 5.4
Changed in intel: | |
status: | New → Fix Committed |
Changed in intel: | |
status: | Fix Committed → Fix Released |
description: | updated |
tags: |
added: intel-kernel-20.04 removed: intel-kernel-19.10 |
Changed in intel: | |
status: | Fix Released → Fix Committed |
Changed in intel: | |
status: | Fix Committed → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1842681
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.