Alerts
Loading...
Signal Name | Description | Condition | Impact |
---|---|---|---|
A bad/faulty USB device was plugged into the system
|
|
-
|
|
The Media Control Unit (MCU) detects the maps storage device, microSD card or embedded multimedia card (eMMC), has encountered a filesystem error, which may affect navigation functionality.
|
The maps storage device (microSD card or eMMC) encounters a filesystem error.
|
Navigation may be unavailable or may not function as expected.
|
|
UDP stream between AP and UI is dropping packets
|
|
-
|
|
USB drive filesystem is corrupt
|
|
-
|
|
The Graphics Processing Unit (GPU) has encountered a major issue, causing it to stop working (aka wedged) and potentially making the system slow or unresponsive.
|
The GPU engines are declared wedged by the Media Control Unit (MCU).
|
System performance may be severely degraded or unresponsive.
|
|
The recovery process for the Graphics Processing Unit (GPU) has failed, indicating a persistent problem. System may be slow or unresponsive.
|
The GPU recovery process fails to recover the GPU.
|
System performance may be severely degraded or unresponsive.
|
|
USB drive has no medium
|
|
-
|
|
Pending configuration changes will apply once the vehicle is parked.
|
|
-
|
|
System will reboot to apply configuration changes.
|
|
-
|
|
The GUI_neverSleep data value in the UI prevents the vehicle from going to sleep and may lead to an increased rate of battery drain.
|
|
-
|
|
The Media Control Unit (MCU) detects the user interface (UI) frames per second (FPS) rate is below the minimum threshold.
|
The UI draw rate is less than 15FPS, indicating the FPS counter is crawling.
|
The UI may be slow to respond and/or appear to be lagging.
|
|
Modem firmware update FAILED
|
|
-
|
|
USB drive could not be mounted due to an error
|
|
-
|
|
A filesystem consistency check on the infotainment system failed
|
|
-
|
|
A post-boot filesystem error occurred at runtime
|
|
-
|
|
A process was killed by its cgroup for exceeding its memory limit
|
|
-
|
|
Kernel disabled an IRQ due to excessive spurious interrupt events
|
Kernel detected too many unhandled interrupt events
|
Sluggish UI performance, loss of some UI functionality depending on which IRQ was disabled
|
|
Audiod input is starving, audiod restarted
|
|
-
|
|
The audio watchdog detects a critical audio error during vehicle wake, which may cause the Media Control Unit (MCU) to restart and/or audio to be temporarily unavailable.
|
The audio watchdog detects a critical audio error within 60 seconds of vehicle wake.
|
If blocked alert log signal values are reported, audio may be unavailable until the next vehicle wake. If rebooted alert log signal values are reported, the MCU will reboot.
|
|
The tegra MCU display FPGA was reset to counter multiple communication errors
|
FPGA errors detected which require a reset
|
-
|