[18.04][LTCTest][OPAL][OP930] IMC PMU (null) Register failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Critical
|
Ubuntu on IBM Power Systems Bug Triage | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Frank Heimes |
Bug Description
== Comment: #0 - PAVAMAN SUBRAMANIYAM <email address hidden> - 2019-04-10 00:15:32 ==
Install a P9 Open Power Hardware with the latest OP930 Firmware images provided in the following link:
http://
root@witherspoon:~# cat /etc/os-release
ID="openbmc-
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="ibm-v2.3"
VERSION_
PRETTY_
BUILD_ID=
root@witherspoon:~# cat /var/lib/
IBM-witherspoo
occ-58e422d
sbe-1410677
Then seeing the following messages in dmesg of Linux HOST OS and also when we reboot the machine in the SOL console.
[ 1.731663] nest_phb0_imc performance monitor hardware support registered
[ 1.731704] nest_phb1_imc performance monitor hardware support registered
[ 1.731746] nest_phb2_imc performance monitor hardware support registered
[ 1.731788] nest_phb3_imc performance monitor hardware support registered
[ 1.731829] nest_phb4_imc performance monitor hardware support registered
[ 1.731870] nest_phb5_imc performance monitor hardware support registered
[ 1.731944] nest_powerbus0_imc performance monitor hardware support registered
[ 1.734458] thread_imc performance monitor hardware support registered
[ 1.734460] IMC Unknown Device type
[ 1.734462] IMC PMU (null) Register failed
[ 1.734558] nest_xlink0_imc performance monitor hardware support registered
[ 1.734614] nest_xlink1_imc performance monitor hardware support registered
[ 1.734670] nest_xlink2_imc performance monitor hardware support registered
[ 1.747043] Initialise system trusted keyrings
[ 1.747054] Key type blacklist registered
[ 1.747170] workingset: timestamp_bits=38 max_order=23 bucket_order=0
== Comment: #2 - PAVAMAN SUBRAMANIYAM <email address hidden> - 2019-04-10 00:30:47 ==
So should this bug be moved to kernel to get the fixes be made available to Ubuntu 18.04 release or should we keep this bug opened for skiboot under OPAL itself, since we are already in the upstream level of skiboot installed on the system.
== Comment: #5 - Application Cdeadmin <email address hidden> - 2019-04-11 15:15:13 ==
==== State: Open by: jayeshp on 11 April 2019 15:05:22 ====
#=#=# 2019-04-11 15:05:21 (CDT) #=#=#
New Fix_Potential = [P910.40W]
#=#=#=#
== Comment: #7 - Application Cdeadmin <email address hidden> - 2019-04-16 06:12:44 ==
cde00 (<email address hidden>) added native attachment /tmp/AIXOS11139
== Comment: #8 - Deborah L. McLemore <email address hidden> - 2019-04-20 09:58:13 ==
== Comment: #9 - Application Cdeadmin <email address hidden> - 2019-04-26 08:25:05 ==
==== State: Open by: csburns on 26 April 2019 08:15:35 ====
The patch in comment #7 was included in a test pnor driver - op999.1999.
== Comment: #10 - VASANT HEGDE <email address hidden> - 2019-05-14 23:02:35 ==
Anju,
Where are we with this patch? Did you push changes to upstream?
Also is this really a ship issue?
-Vasant
== Comment: #15 - Klaus Heinrich Kiwi <email address hidden> - 2020-03-25 06:27:01 ==
(In reply to comment #13)
> Patch is now upstream.
> https:/
>
> Thanks,
> Anju
== Comment: #16 - Klaus Heinrich Kiwi <email address hidden> - 2020-03-25 06:33:24 ==
(In reply to comment #14)
> (In reply to comment #13)
> > Patch is now upstream.
> > https:/
> >
> > Thanks,
> > Anju
>
> What next? will you be sending fix to distros?
>
> -Vasant
tags: | added: architecture-ppc64le bugnameltc-176827 severity-critical targetmilestone-inin2004 |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → kernel-package (Ubuntu) |
affects: | kernel-package (Ubuntu) → linux (Ubuntu) |
tags: |
added: targetmilestone-inin2004 removed: targetmilestone-1804 |
tags: |
added: targetmilestone-inin2004 removed: targetmilestone-inin1804 |
Since there is the tag "targetmileston e-inin2004" set, I assume this bug was opened against focal / 20.04.
Doing a look-up of b59bd3527fe3 "powerpc/powernv: Return for invalid IMC domain" in the focal master tree (that correlates to the kernel that is currently in focal's release pocket and is with that the current default kernel) shows that this specific patch/commit is already in:
$ git clone https:/ /git.launchpad. net/~ubuntu- kernel/ ubuntu/ +source/ linux/+ git/focal 5.4-5.4. 0-10.13 5.4-5.4. 0-11.14 5.4-5.4. 0-12.15 5.4-5.4. 0-13.16 5.4-5.4. 0-14.17
...
$ git log --oneline --grep "powerpc/powernv: Return for invalid IMC domain"
b59bd3527fe3 powerpc/powernv: Return for invalid IMC domain
$ git tag --contains b59bd3527fe3
Ubuntu-
Ubuntu-
Ubuntu-
Ubuntu-
Ubuntu-
Ubuntu-5.4.0-15.18
Ubuntu-5.4.0-16.19
Ubuntu-5.4.0-17.20
Ubuntu-5.4.0-17.21
Ubuntu-5.4.0-18.22
Ubuntu-5.4.0-19.23
Ubuntu-5.4.0-20.24
Ubuntu-5.4.0-8.11
Ubuntu-5.4.0-9.12
v5.4
So I'm wondering which kernel version was used in your case?
Please can you share the output of 'uname -a'?