Difference between revisions of "Panic codes"
Jump to navigation
Jump to search
| (6 intermediate revisions by 2 users not shown) | |||
| Line 32: | Line 32: | ||
|- | |- | ||
| <div style="width: 60px; height: 20px; background:#0000FF;"></div> || 0x0000FF || Kernel | | <div style="width: 60px; height: 20px; background:#0000FF;"></div> || 0x0000FF || Kernel | ||
| + | |- | ||
| + | | <div style="width: 60px; height: 20px; background:#FF7700;"></div> || 0xFF7700 || Secure Monitor (exception vectors) | ||
|- | |- | ||
| <div style="width: 60px; height: 20px; background:#00FFFF;"></div> || 0x00FFFF || Secure Monitor (general errors) | | <div style="width: 60px; height: 20px; background:#00FFFF;"></div> || 0x00FFFF || Secure Monitor (general errors) | ||
|- | |- | ||
| − | | <div style="width: 60px; height: 20px; background:#00AAFF;"></div> || 0x00AAFF || Secure Monitor (deep sleep) | + | | <div style="width: 60px; height: 20px; background:#00AAFF;"></div> || 0x00AAFF || Secure Monitor (deep sleep) [1.0.0+] |
| + | |- | ||
| + | | <div style="width: 60px; height: 20px; background:#FF77FF;"></div> || 0xFF77FF || Secure Monitor (deep sleep) [4.0.0+] | ||
|- | |- | ||
| <div style="width: 60px; height: 20px; background:#AA00FF;"></div> || 0xAA00FF || Bootloader (general errors) | | <div style="width: 60px; height: 20px; background:#AA00FF;"></div> || 0xAA00FF || Bootloader (general errors) | ||
|- | |- | ||
| − | | <div style="width: 60px; height: 20px; background:#FFFFAA;"></div> || 0xFFFFAA || Bootloader ( | + | | <div style="width: 60px; height: 20px; background:#FFFFAA;"></div> || 0xFFFFAA || Bootloader (booting SafeMode) [1.0.0-3.0.2] |
| − | |||
| − | |||
|} | |} | ||
| Line 64: | Line 66: | ||
| 0x6 || <div style="width: 60px; height: 20px; background:#00FFFF;"></div> || Unknown Abort | | 0x6 || <div style="width: 60px; height: 20px; background:#00FFFF;"></div> || Unknown Abort | ||
|- | |- | ||
| − | | 0x7 || <div style="width: 60px; height: 20px; background:# | + | | 0x7 || <div style="width: 60px; height: 20px; background:#FF77FF;"></div> || Invalid CPU context |
|- | |- | ||
| − | | 0x8 || <div style="width: 60px; height: 20px; background:# | + | | 0x8 || <div style="width: 60px; height: 20px; background:#FF77FF;"></div> || Invalid SE state |
|- | |- | ||
| − | | 0x9 || <div style="width: 60px; height: 20px; background:# | + | | 0x9 || <div style="width: 60px; height: 20px; background:#FF77FF;"></div> || CPU is already awake [2.0.0+] |
|- | |- | ||
| − | | 0x10 || | + | | 0x10 || <div style="width: 60px; height: 20px; background:#FF7700;"></div> || Unknown exception |
|- | |- | ||
| 0x20 || <div style="width: 60px; height: 20px; background:#000000;"></div> || Rebooting into SafeMode | | 0x20 || <div style="width: 60px; height: 20px; background:#000000;"></div> || Rebooting into SafeMode | ||
| Line 88: | Line 90: | ||
| 0x35 || <div style="width: 60px; height: 20px; background:#AA00FF;"></div> || Failed to boot SafeMode | | 0x35 || <div style="width: 60px; height: 20px; background:#AA00FF;"></div> || Failed to boot SafeMode | ||
|- | |- | ||
| − | | 0x36 || <div style="width: 60px; height: 20px; background:#AA00FF;"></div> || [4.0.0+] | + | | 0x36 || <div style="width: 60px; height: 20px; background:#AA00FF;"></div> || Activity Monitor fired [4.0.0+] |
|- | |- | ||
| 0x40 || <div style="width: 60px; height: 20px; background:#0000FF;"></div> || Show error called (kernel panic) | | 0x40 || <div style="width: 60px; height: 20px; background:#0000FF;"></div> || Show error called (kernel panic) | ||
|} | |} | ||
Latest revision as of 18:41, 22 April 2018
All elements in the Switch's boot chain up to the kernel have the ability to issue a system panic.
Panics are handled by writing a panic code in the PMC_SCRATCH200 register and requesting a reboot by programming a dedicated hardware watchdog (WDT4). The bootloaders and the Secure Monitor are able to do this right away, but the kernel must invoke the Panic SMC.
When the system reboots, the encrypted bootloader checks if the reset was requested by the watchdog (PMC_RST_STATUS register is set to 0x01) and parses the panic code stored in PMC_SCRATCH200.
If a panic did occur, the Switch will paint the main screen with a solid color and halt execution.
Structure
| Bits | Field |
|---|---|
| 31-28 | Blue value |
| 27-24 | Green value |
| 23-20 | Red value |
| 19-0 | Description |
The blue, green and red values are nibbles which represent the color that will fill the panic screen. Each nibble is duplicated to form a full byte before writing the final color to the display's MMIO.
Panic colors
Different colors are used to represent panic events coming from different execution levels within the system.
| Color | Value | Level |
|---|---|---|
| 0x000000 | Default | |
| 0x0000FF | Kernel | |
| 0xFF7700 | Secure Monitor (exception vectors) | |
| 0x00FFFF | Secure Monitor (general errors) | |
| 0x00AAFF | Secure Monitor (deep sleep) [1.0.0+] | |
| 0xFF77FF | Secure Monitor (deep sleep) [4.0.0+] | |
| 0xAA00FF | Bootloader (general errors) | |
| 0xFFFFAA | Bootloader (booting SafeMode) [1.0.0-3.0.2] |
Panic codes
While any combination of panic colors and codes is possible, several panic codes are specifically tied to a certain color.
| Value | Color | Description |
|---|---|---|
| 0x0 | Any | No information |
| 0x1 | Package2 signature verification failed | |
| 0x2 | Package2 meta verification failed | |
| 0x3 | Package2 version check failed | |
| 0x4 | Package2 payload verification failed | |
| 0x5 | Unknown SMC | |
| 0x6 | Unknown Abort | |
| 0x7 | Invalid CPU context | |
| 0x8 | Invalid SE state | |
| 0x9 | CPU is already awake [2.0.0+] | |
| 0x10 | Unknown exception | |
| 0x20 | Rebooting into SafeMode | |
| 0x21 | Rebooting for anti-downgrade | |
| 0x30 | General bootloader error | |
| 0x31 | Invalid DRAM ID | |
| 0x32 | Invalid size | |
| 0x33 | Invalid argument | |
| 0x34 | Bad GPT | |
| 0x35 | Failed to boot SafeMode | |
| 0x36 | Activity Monitor fired [4.0.0+] | |
| 0x40 | Show error called (kernel panic) |