Difference between revisions of "Checkstop"
Jump to navigation
Jump to search
JeremyRand (talk | contribs) (nvram) |
JeremyRand (talk | contribs) (→Diagnosing a Checkstop: opal-prd) |
||
| Line 10: | Line 10: | ||
If you're lucky, it will return a log of the most recent checkstop. If you instead get <code>nvram: ERROR: can't decompress text: inflate() returned -3</code>, then the log in NVRAM is corrupted for some reason, and you'll need to try a different approach. | If you're lucky, it will return a log of the most recent checkstop. If you instead get <code>nvram: ERROR: can't decompress text: inflate() returned -3</code>, then the log in NVRAM is corrupted for some reason, and you'll need to try a different approach. | ||
| + | |||
| + | == opal-prd == | ||
| + | |||
| + | Before the checkstop occurs, run the following from the OS (this is for Debian; most other distros package it as well; see your distro's documentation for details): | ||
| + | |||
| + | <code>sudo apt install opal-prd</code> | ||
| + | |||
| + | Once installed, if you're lucky, any subsequent checkstops should show up in <code>journalctl</code> output. | ||
Revision as of 10:12, 10 February 2023
Diagnosing a Checkstop
There are a few ways to obtain logs of a checkstop.
nvram
From either the OS or Skiroot, run this as root/sudo after the machine has rebooted following the checkstop (but before rebooting again):
nvram --unzip lnx,oops-log
If you're lucky, it will return a log of the most recent checkstop. If you instead get nvram: ERROR: can't decompress text: inflate() returned -3, then the log in NVRAM is corrupted for some reason, and you'll need to try a different approach.
opal-prd
Before the checkstop occurs, run the following from the OS (this is for Debian; most other distros package it as well; see your distro's documentation for details):
sudo apt install opal-prd
Once installed, if you're lucky, any subsequent checkstops should show up in journalctl output.
