| #
be14ec2d |
| 24-Mar-2023 |
Matt Spinler <spinler@us.ibm.com> |
Change daily clock log to informational severity
The event log was using a severity of Error, and because the PEL message
registry had a severity of Informational, phosphor-log-manager would
spit ou
Change daily clock log to informational severity
The event log was using a severity of Error, and because the PEL message
registry had a severity of Informational, phosphor-log-manager would
spit out a trace about how the severities mismatched every time the PEL
was created.
Change-Id: Ia7559a5c3cfdf6ad93277783bfd85cb639af25a0
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
show more ...
|
| #
4d5b5bfe |
| 23-May-2022 |
Marri Devender Rao <devenrao@in.ibm.com> |
PHAL: Log Informational error for PEL created during poweroff
1)Log informational PELS in case system state is transitioning to
power-off for IPL procedures/hardware access failures
2) Don't add ca
PHAL: Log Informational error for PEL created during poweroff
1)Log informational PELS in case system state is transitioning to
power-off for IPL procedures/hardware access failures
2) Don't add callouts to PEL's created during transition to
power-off as the CEC will not be in expected state.
Tested: transition to poweroff
root@xxxbmc:/usr# peltool -lfh
{
"0x50003BEB": {
"SRC": "BD503001",
"Message": "Failure occurred during boot process",
"PLID": "0x50003BEB",
"CreatorID": "BMC",
"Subsystem": "CEC Hardware",
"Commit Time": "05/23/2022 13:57:53",
"Sev": "Informational Event",
"CompID": "0x3000"
}
}
root@xxxbmc:~# peltool -i 0x50003be0
{
"Private Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x3000",
"Created at": "05/23/2022 13:48:12",
"Committed at": "05/23/2022 13:48:12",
"Creator Subsystem": "BMC",
"CSSVER": "",
"Platform Log Id": "0x50003BE0",
"Entry Id": "0x50003BE0",
"BMC Event Log Id": "510"
},
"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware",
"Event Scope": "Entire Platform",
"Event Severity": "Informational Event",
"Event Type": "Miscellaneous, Informational Only",
"Action Flags": [
"Event not customer viewable",
"Report Externally"
],
"Host Transmission": "Not Sent",
"HMC Transmission": "Not Sent"
},
.
.
.
Tested: transition to running
root@ever8bmc:/tmp# peltool -i 0x50003CF9
{
"Private Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x3000",
},
"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware",
"Event Scope": "Entire Platform",
"Event Severity": "Unrecoverable Error",
},
"User Data 0": {
"Created by": "0x2000",
"BMCState": "Ready",
"BootState": "Unspecified",
"ChassisState": "On",
"FW Version ID": "fw1020.00-57.7-2-gd86188a773",
"HostState": "TransitioningToRunning",
"Process Name": "/usr/bin/openpower-proc-control",
"System IM": "50003000"
},
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: I078d5cba2e0fb705bf424d2f8f3010f2cd2063bb
show more ...
|
| #
e5ba5fd0 |
| 27-Jan-2022 |
Jayanth Othayoth <ojayanth@in.ibm.com> |
PHAL: Additional callout support for sbe timeout error
Sbe Boot timeout or chip-op timeout case BMC should run
sbe_extract_rc procedure to identify the correct callout
and service action. Currently
PHAL: Additional callout support for sbe timeout error
Sbe Boot timeout or chip-op timeout case BMC should run
sbe_extract_rc procedure to identify the correct callout
and service action. Currently this procedure based callout
handling is not place. Adding callout recommended by RAS
team till the actual callout code in place.
Tested:
"Callout Count": "2",
"Callouts": [{
"FRU Type": "Maintenance Procedure Required",
"Priority": "Mandatory, replace all with this type as a unit",
"Procedure": "BMC0002"
}, {
"FRU Type": "Normal Hardware FRU",
"Priority": "Medium Priority",
"Location Code": "xxx", --> processor callout
"Part Number": "xxx",
"CCIN": "xxx",
"Serial Number": "xxx"
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I40444eb5da1a5f329b09dea1bce15e1bab53e1d8
show more ...
|