Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug][Linux] /v1/embeddings always fails with qds_device::wait() unexpected command state (Krackan Point, FLM 1.0.6)

Abierto
  • ¿Algo no está bien?
#752 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
c, cpp, linux
Área
ai-infra-agents, backend, devtools

Línea de trabajo

The issue is in the NPU driver stack, likely in the XRT plugin or amdxdna driver. Start by examining the server logs around the embedding dispatch and the error 'qds_device::wait() unexpected command state'. Look at the related issues #732, #661, #647, #655 for context on similar Linux/NPU problems. Check the embedding model loading and inference path in the FastFlowLM codebase, focusing on how it interfaces with the XRT API for the Krackan Point hardware. Reproduce the error with the given steps to confirm the environment.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem Description

On Linux, every request to /v1/embeddings fails with the same internal XRT error, deterministically, while chat completions on the same server instance keep working fine.

Request:

curl http://127.0.0.1:52625/v1/embeddings \
  -d '{"model":"embed-gemma:300m","input":"hola"}'

Response (100% of requests):

{"error":"qds_device::wait() unexpected command state"}

Server log shows the request arriving and being accepted, then the error:

[LOG]  Target: /v1/embeddings
    "model": "embed-gemma:300m"
Embedding input[0]: hola
→ {"error":"qds_device::wait() unexpected command state"}

Notes:

  • Happens with single-string input and with arrays.
  • flm serve llama3.2:1b --embed 1 loads both models successfully (Embedding mode enabled: reserving additional 300MB); failure only occurs at the actual embed dispatch.
  • Without --embed 1, chat on the same box is fine (96 tok/s prefill / 42 tok/s decode with llama3.2:1b).
  • The error message text matches the generic XRT/NPU queue-state error also seen in Xilinx/mlir-aie#1751 and amd/RyzenAI-SW#177.

Related issues (but not the same symptom): #732 and #661 report embeddings that complete but are wrong/collapsed on Linux; #647 reports non-determinism; #655 reports an IOCTL regression on the same chip family (Krackan Point). This report adds the case where the embed dispatch itself errors out on every request.

Environment
Item Value
Hardware AMD Ryzen AI 5 PRO 340 (Krackan Point), PCI 1022:17f0, Lenovo subsystem
OS Omarchy (Arch Linux), Wayland
Kernel 7.2.5-4-omarchy
NPU FW 1.1.2.64
Device /dev/accel/accel0 with 8 columns
amdxdna in-tree, reported as 0.10 by flm validate
XRT xrt 2.21.75-14 + xrt-plugin-amdxdna 2.21.75-2 (Arch extra)
FLM fastflowlm 1.0.6-1 (Arch extra)
Memlock unlimited (via ulimit wrapper)

flm validate output:

[Linux]  Kernel: 7.2.5-4-omarchy
[Linux]  NPU: /dev/accel/accel0 with 8 columns
[Linux]  NPU FW Version: 1.1.2.64
[Linux]  amdxdna version: 0.10
[Linux]  Memlock Limit: infinity
Steps to reproduce
flm pull llama3.2:1b
flm pull embed-gemma:300m
flm serve llama3.2:1b --embed 1

curl http://127.0.0.1:52625/v1/embeddings \
  -H 'Content-Type: application/json' \
  -d '{"model":"embed-gemma:300m","input":"hola"}'
Expected

A vector array response:

{"data":[{"embedding":[...],...}]}
Actual
{"error":"qds_device::wait() unexpected command state"}

CPU governor/pmode (--pmode balanced) does not change the outcome; also reproduced with pmode default. Model files pass flm check after a fresh verified download.

Lenguaje dominante
C++
Estrellas
1.9k
Forks
156
Merge medio
2 d 2 h
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ROCm/FastFlowLM

Todos los issues de ROCm/FastFlowLM

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.