device bring up issue (v80-smi write-static-shell)
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- cli, embedded-iot
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Tcl
- Stars
- 48
- Forks
- 23
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Xilinx/SLASH
-
SMBus and DCMAC license requirement not in docsPossibly taken @mariodruiz claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Supporting asynchronous HBM clock crossing and AXI width conversionPossibly taken @hpc-aulmamei claimed this 6 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
V80 SLASH shell silently drops host `s_axi_control` writes to offsets `0x40–0xBF`Possibly taken @quetric claimed this 12 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pytest-dev/pytest#15146 ·
Maintainers usually reply within 1 day
-
agentic-workflows Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
status:approved type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Gentleman-Programming/gentle-ai#5326 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day