Skip to main content
Solved

Segmentation Fault when Running Inference on Voyager SDK 1.5.1 (Metis PCIe Card)

  • December 1, 2025
  • 2 replies
  • 99 views

Hi,
I installed Voyager SDK 1.5.1 on Ubuntu 22.04 and the Metis PCIe card is detected correctly, but running inference results in a segmentation fault.

System Setup

  • OS: Ubuntu 22.04 (AMD64)

  • Hardware: Axelera Metis PCIe card

  • SDK Version: Voyager SDK 1.5.1

  • GPU/CPU: AMD Ryzen + integrated GPU

  • Installation completed successfully:

No pending installation tasks. To activate the environment, type: source venv/bin/activate

PCIe Card Detection

lspci -tv correctly shows the Metis device:

+-01.1-[10]----00.0 Axelera AI Metis AIPU (rev 02)

Issue

When I run a sample inference:

./inference.py yolov5s-v7-coco media/traffic1_1080p.mp4 --verbose

I get:

WARNING: Failed to get OpenCL platforms : clGetPlatformIDs failed: PLATFORM_NOT_FOUND_KHR Segmentation fault (core dumped)

The last debug messages:

DEBUG: Setting state of pipeline0 to GST_STATE_READY DEBUG: pipeline0: state-changed (null to ready) Segmentation fault (core dumped)

What I’ve checked

  • SDK installation is complete

  • PCIe card detected

  • Firmware + drivers installed (metis-dkms == 1.4.4, axelera-multi-device == 1.0.0)

  • Activated virtual environment

  • Media file loads (GStreamer detects FPS correctly)

Questions

  1. Why does the GStreamer pipeline trigger a segmentation fault?

  2. Do the OpenCL warnings indicate a missing GPU runtime that the SDK requires?

Any help or suggestions would be greatly appreciated!

Best answer by Spanner

Hi guys, sorry to hear you’ve hit a couple of problems with 1.5.1.

Before we dig too deep, did you recompile any models that were compiled with a previous version of Voyager? There’s a breaking change in 1.5 that requires models to be recompiled, or redownloaded if it’s a pre-compiled model from the zoo.

Bit of a pain admittedly, but in the long run this change will really yield fruit! 😀

2 replies

Spanner
Axelera Team
Forum|alt.badge.img+2
  • Axelera Team
  • Answer
  • December 1, 2025

Hi guys, sorry to hear you’ve hit a couple of problems with 1.5.1.

Before we dig too deep, did you recompile any models that were compiled with a previous version of Voyager? There’s a breaking change in 1.5 that requires models to be recompiled, or redownloaded if it’s a pre-compiled model from the zoo.

Bit of a pain admittedly, but in the long run this change will really yield fruit! 😀


  • Author
  • Ensign
  • December 1, 2025

Ok spanner,  will try it out