Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Video process quit unexpectedly.
|
Video proces quit without receiving the SIGINT or SIGTERM signals.
|
Camera video stream unavailable or malfunctioning.
|
|
|
The Driver Assistance Electronic Control Unit (ECU) has detected an issue with the Graphics Processing Unit (GPU) driver. A message containing 'WARN_ON(i915)' may be present in the logs.
|
The Driver Assistance ECU detects an issue with the GPU driver has been detected. A message containing 'WARN_ON(i915' may be present in the logs. The GPU driver may have a condition affecting functionality.
|
The User Interface (UI) may not behave as expected. The UI screen may be blank.
|
|
|
The User Interface (UI) Electronic Control Unit (ECU) detects the Graphical Processing Unit (GPU) experiences a software error known as a GPU hang.
|
The GPU experiences a software error. Alert log signal data should provide more information on the specific reason.
|
The center display may be blank, frozen, or have unintended artifacts on the User Interface (UI).
|
|
|
The connection manager detected a condition requiring the Wi-Fi link to be reset, which may lead to a loss of Wi-Fi connectivity.
|
The connection manager resets the Wi-Fi link.
|
There may be a loss of Wi-Fi connectivity.
|
|
|
The external amplifier's boost power has detected an issue during initialization.
|
The external amplifier's boost power has detected an issue during initialization.
|
The external amplifier may not function as expected. There may be a loss of audio.
|
|
|
The User Interface (UI) main application, also known as QtCar, has encountered an unexpected or unrecoverable error causing it to reboot.
|
QtCar encountered an unexpected or unrecoverable error.
|
QtCar will reboot.
|
|
|
The operating system encounters an error, preventing the system from running as expected and causing the UI to reboot.
|
The operating system encounters an error. Alert log signal data provides a unique signature associated with the specific condition(s) detected.
|
The touchscreen UI will reboot.
|
|
|
The User Interface (UI) is unable to read 10 consecutive frames from the backup camera, which may cause the backup camera to not perform as designed.
|
The User Interface (UI) was unable to read 10 consecutive frames from the backup camera.
|
The backup camera may not perform as designed.
|
|
|
Failed to start the backup-camera stream from UI.
|
User Interface fails to start the backup-camera stream due to an IPU (Intel Image Processing Unit) issue or the related pipeline fails to be initialized successfully.
|
Backup camera / Autopilot functionality not available or limited.
|
|
|
There is a shift request, but the drive rail is not ON and the brake pedal is not pressed, which may prevent the vehicle from being shifted from the Park gear.
|
There is a shift request, but the drive rail is not ON and the brake pedal is not pressed.
|
The vehicle is unable to be shifted from the Park gear.
|
|
|
The status of the premium amplifier could not be read over the I2C bus, which may present the premium amplifier from performing as designed.
|
The status of the premium amplifier could not be read over the I2C bus.
|
The premium amplifier may not perform as designed and a new A2B discovery will occur.
|
|
|
The software running on the modem has encountered an unexpected or unrecoverable error, which may lead to a loss of cellular connectivity.
|
The software running on the modem has encountered an unexpected or unrecoverable error.
|
There is a loss of cellular connectivity.
|
|
|
Out of data roaming area, Data will be re-enabled after entering roaming area.
|
Roaming not allowed
|
Loss of connectivity
|
|
|
Backup camera reported an error when streaming. There is a high probability of a HW fault or disconnected harness.
|
Backup camera reported an error when streaming.
|
Backup camera / Autopilot functionality not available or limited.
|
|
|
The cellular modem detects the emergency call (eCall) self-test did not pass. During vehicle start-up and when the drive rail is turned ON, the emergency call (eCall) system will attempt 1 self-test with 3 retries. If the 3 retries are unsuccessful, the alert will set. Since the eCall self-tests are run on each ignition, the alert may appear and disappear depending on the result of the latest self tests.
|
The eCall self-test did not pass after the drive rail was turned ON.
|
The eCall may not perform as designed.
|
|
|
The homelink module is transmitting a signal.
|
The homelink module begins to transmit a signal.
|
The vehicle is performing as designed.
|
|
|
A condition was detected on the audio A2B primary node and now requires a new device discovery over the A2B bus, which may lead to a temporary interruption of audio. This alert only sets if the vehicle is not in sleep.
|
The audio A2B primary node requires a new device discovery.
|
There may be a temporary interruption of audio.
|
|
|
The A2B I2C bus experiences a lockup condition, which may cause audio devices on the A2B I2C bus to be inaccessible and may lead to a complete loss of audio.
|
The A2B I2C bus experiences a lockup condition.
|
Audio devices on the A2B I2C bus may be inaccessible, and there may be a complete loss of audio.
|
|
|
Audio stack is resetting within 1 minute of the vehicle waking while parked. This is due to recurring XRUN messages present in the logs.
|
Audio stack is resetting within 1 minute of the vehicle waking while parked. This is due to rapidly recurring XRUN messages (40 messages in 1 second) present in the logs. XRUN events correspond with vehicle buffer and occur when a stream is closed, interrupted, or high system load.
|
Vehicle audio and user interface (UI) may not behave as expected.
|
|
|
Audio stack resetting UI within 1 minute of waking while vehicle parked, includes payload for reset reason.
|
Triggers only when the reset has been called.
|
Vehicle audio and user interface (UI) may not behave as expected.
|