Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

device bring up issue (v80-smi write-static-shell)

Aperta
#227 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@quetric ci sta già lavorando.

Dal 28/9/2026.

  • #230 di @quetric — integrata

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
cli, embedded-iot

Direzione di ricerca

Start by reproducing v80-smi write-static-shell --flash -d 04:00 and reviewing the vrtd.service journal output included in the issue. Trace the reset and rescan path through the reported shell build-ID failure; done means identifying the cause of the internal error and confirming that the device can be brought up successfully.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

On behalf of ZIFAN HE <[email protected]>

I installed SLASH@7a528701c3f17506e5c645399b8b57c82d39632f, but there is an issue with bringing up the device (v80-smi write-static-shell)

vast@c03
: 
~
$ lspci -d 10ee: -k 04:00.0 Processing accelerators: Xilinx Corporation Device 50b4 Subsystem: Xilinx Corporation Device 000e Kernel driver in use: ami Kernel modules: ami 04:00.1 Processing accelerators: Xilinx Corporation Device 50b5 Subsystem: Xilinx Corporation Device 000e Kernel driver in use: slash_qdma Kernel modules: slash, ami 04:00.2 Processing accelerators [1280]: Xilinx Corporation Device 50b6 Subsystem: Xilinx Corporation Device 000e Kernel driver in use: slash_ctl Kernel modules: slash, ami 
vast@c03
: 
~
$ v80-smi list Board 0000:04:00 OK (PF0: OK) (PF1: OK) (PF2: OK) (VRTD: OK) Shell: compute
vast@c03
: 
~
$ ls -l /dev/slash_* crw------- 1 vrtd vrtd 507, 1 Sep 25 16:50 
/dev/slash_ctl0
crw------- 1 vrtd vrtd 507, 0 Sep 25 16:26 
/dev/slash_hotplug
crw------- 1 vrtd vrtd 507, 2 Sep 25 16:50 
/dev/slash_qdma_ctl0
vast@c03
: 
~
$ groups vast adm cdrom sudo dip plugdev lxd vrtadmin
vast@c03
: 
~
$ v80-smi write-static-shell --flash -d 04:00 Resolving device address... Connecting to VRTD... Resolving service PDI path... Resolving VRTD device... Submitting service flash program... Opening AMI device Downloading PDI: 100% (25887408/25887408 bytes) Rescanning PCIe Failed SMI execution failed: Internal error in vrtd daemon or local libvrtd 
vast@c03
: 
~
$ journalctl -u vrtd.service | tail -17 Sep 25 16:50:19 c03 vrtd[2974]: Hotplug op=reset_sequence(4) bdf=0000:04:00 dev=0 uid=1000 conn_id=14 Sep 25 16:50:19 c03 vrtd[2974]: Reset sequence submitted dev=0 bdf=0000:04:00 uid=1000 conn_id=14 Sep 25 16:50:19 c03 vrtd[2974]: Device reset starting on worker thread Sep 25 16:50:19 c03 vrtd[2974]: reset_with_ami: AMI_IOC_DEVICE_BOOT(0000:04:00.0, partition=0) OK Sep 25 16:50:19 c03 vrtd[2974]: reset_with_ami: GPIO_ALLOW_SBR set on 0000:04:00.0 Sep 25 16:50:19 c03 vrtd[2974]: reset_with_ami: removed 0000:04:00.0 (ret=0, errno=0) Sep 25 16:50:19 c03 vrtd[2974]: reset_with_ami: removed 0000:04:00.1 (ret=0, errno=0) Sep 25 16:50:19 c03 vrtd[2974]: reset_with_ami: removed 0000:04:00.2 (ret=0, errno=0) Sep 25 16:50:19 c03 vrtd[2974]: reset_with_ami: toggling SBR for 0000:04:00.0 Sep 25 16:50:20 c03 vrtd[2974]: reset_with_ami: SBR toggle complete for 0000:04:00.0 Sep 25 16:50:28 c03 vrtd[2974]: reset_with_ami: rescan complete (attempt 1/5) Sep 25 16:50:38 c03 vrtd[2974]: reset_with_ami: device 0000:04:00.0 found after reset Sep 25 16:50:38 c03 vrtd[2974]: Discovered 1 device(s) matching /dev/slash_ctl* Sep 25 16:50:38 c03 vrtd[2974]: Stripping PF function .2 from kernel BDF 0000:04:00.2; device tracked as board 0000:04:00 Sep 25 16:50:38 c03 vrtd[2974]: Paired control device /dev/slash_ctl0 with QDMA device /dev/slash_qdma_ctl0 Sep 25 16:50:38 c03 vrtd[2974]: reset_with_ami: shell build-ID register at BAR4+0x20008 did not respond; cannot confirm the service shell is loaded Sep 25 16:50:38 c03 vrtd[2974]: Async device op opcode=13(DEVICE_HOTPLUG_OP) completed ret=6 uid=1000 conn_id=14
Lingua principale
Tcl
Stelle
48
Fork
23
Merge medio
2g 3h
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Xilinx/SLASH

Tutte le issue di Xilinx/SLASH

Issue simili

Altre issue su CLI

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.