Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
The User Interface (UI) main application, also known as QtCar, is intentionally rebooting due to a user-initiated action.
|
QtCar receives a valid request to reboot, such as a user-initiated software update or a settings change that requires a restart.
|
QtCar will temporarily be unavailable during reboot, which may cause a brief interruption to the user's interaction with the vehicle's systems.
|
No
|
|
|
The Instrument Cluster (IC) reported firmware version does not match the vehicle firmware version reported by the Gateway.
|
The Instrument Cluster (IC) reported firmware version does not match the vehicle firmware version reported by the Gateway.
|
A potential degradation of the User Interface (UI) experience or lack of communication between the UI and vehicle.
|
No
|
|
|
The navigation service encountered an error when processing a navigation request.
|
Navigation service reports an error when attempting to navigate to a destination.
|
Navigation service falls back to offline routing. This can occur even if the vehicle has connectivity.
|
No
|
|
|
The tegra MCU failed to communicate to the audio DSP over SPI
|
Failure to write/read to/from the audio DSP
|
-
|
No
|
|
|
The Center Information Display (CID) reported firmware version does not match the vehicle firmware version reported by the Gateway.
|
The Center Information Display (CID) reported firmware version does not match the vehicle firmware version reported by the Gateway.
|
A potential degradation of the User Interface (UI) experience or lack of communication between the UI and vehicle.
|
No
|
|
|
No hardware audio devices available in the system
|
Hardware audio devices intialization failed and will be re-tried
|
No audio
|
No
|
|
|
The tegra MCU display FPGA was reset to counter multiple communication errors
|
FPGA errors detected which require a reset
|
-
|
No
|
|
|
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.
|
No
|
|
|
Audiod input is starving, audiod restarted
|
|
-
|
No
|
|
|
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
|
No
|
|
|
A process was killed by its cgroup for exceeding its memory limit
|
|
-
|
No
|
|
|
A post-boot filesystem error occurred at runtime
|
|
-
|
No
|
|
|
A filesystem consistency check on the infotainment system failed
|
|
-
|
No
|
|
|
USB drive could not be mounted due to an error
|
|
-
|
No
|
|
|
Modem firmware update FAILED
|
|
-
|
No
|
|
|
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.
|
No
|
|
|
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.
|
|
-
|
No
|
|
|
System will reboot to apply configuration changes.
|
|
-
|
No
|
|
|
Pending configuration changes will apply once the vehicle is parked.
|
|
-
|
No
|
|
|
USB drive has no medium
|
|
-
|
No
|