Xilinx / Xilinx/Vitis_Accel_Examples

Failed to run for P2P bandwidth Example

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
605
Forks
233
Avg merge
1m
Merged PRs (30d)
1

Description

Hi,
According to the VITIS ACCEL EXAMPLE Doc, I'm tring to test the code of P2P bandwidth example for my SmartSSD. However, I got a error when I run the command
./p2p_bandwidth -x ./build_dir.hw.xilinx_u2_gen3x4_xdma_gc_2_202110_1/bandwidth.xclbin -f ./data/sample.txt -p /dev/nvme0n1

the whole output of terminal is below:


WARNING: Ignoring -f option when -p options is set. -p has high precedence over -f.
Found Platform
Platform Name: Xilinx
INFO: Reading ./build_dir.hw.xilinx_u2_gen3x4_xdma_gc_2_202110_1/bandwidth.xclbin
Loading: './build_dir.hw.xilinx_u2_gen3x4_xdma_gc_2_202110_1/bandwidth.xclbin'
Trying to program device[0]: xilinx_u2_gen3x4_xdma_gc_base_2

Message from syslogd@iad0-SYS-220U-TNR at Aug 10 16:00:27 ...
kernel:[53262.306491] watchdog: BUG: soft lockup - CPU#81 stuck for 22s! [kworker/u224:8:1313]


Before executing the application, I run make all PLATFORM=xilinx_u2_gen3x4_xdma_gc_2_202110_1 TARGET=hw. There's no error in this process.
By the way, the hw_emu and sw_emu are all passed.

Here is my environment config:
OS: Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-155-generic x86_64)
XILINX XRT: version 2022.1
platform: xilinx_u2_gen3x4_xdma_gc_2_202110_1
device: SmartSSD

I passed the validation mentioned in the UG1382v1.3 by running sudo xbutil validate -d <bdf>

What should I do to run the application? Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the p2p_bandwidth command, the bandwidth.xclbin build output, and the SmartSSD environment described in the issue; compare the hardware run with the passing hw_emu and sw_emu runs. Done means the hardware application executes without the watchdog soft-lockup, using the documented platform and device configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, ubuntu
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.