-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Who triggered OCB_ OISR0? #30
Comments
What type of system and firmware level are you using? |
Also, did you ensure the system rebooted after the checkstop was triggered? |
|
What type of system are you using? Specifically, is this a P9 or P10 system? |
This is P9 system |
Good, because P10 is a completely different analysis design. Let me poke around. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
occ/src/occ_405/errl/errl.c
Line 832 in 16131c3
When testing the RAS function of the OpenPOWER system, we found that after the Checkstop was triggered, "l_oisr0_status. fields. check_stop_ppc405" has a certain probability of being false, resulting in the FIR data not being collected. Excuse me?
Which module is this register set by?
The OCC determines whether to collect FIR data based on this value. At that time, it was determined that this value would be set up when the check stop?
The text was updated successfully, but these errors were encountered: