Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault #22

Open
qiuhaojie opened this issue Nov 19, 2022 · 5 comments
Open

Segmentation fault #22

qiuhaojie opened this issue Nov 19, 2022 · 5 comments
Assignees

Comments

@qiuhaojie
Copy link

After I finished compiling the hw section and burning the bit flow through the jtag interface into vcu118, I executed
insmod coyote_drv.ko
A segment error has occurred, as shown below
image
And the printed kernel information is as follows:
Screenshot from 2022-11-18 10-50-01
The read configuration information is all 1. I do not know the cause

@d-kor
Copy link
Contributor

d-kor commented Nov 21, 2022

Did your rescan the PCIe bus?

@qiuhaojie
Copy link
Author

Yes, restart the host after burning the bitstream. After restart, check the device before loading the driver and input instructions
lspci -vv -d 10EE:
image
However, insmod coyote_drv.ko will still appear Segmentation fault.

@qiuhaojie
Copy link
Author

All the information is as follows:
image

@d-kor
Copy link
Contributor

d-kor commented Nov 24, 2022

What is the benchmark you are running and what is the config?

@qiuhaojie
Copy link
Author

The instructions I entered were:

cmake -DFDEV_NAME=vcu118 -DEXAMPLE=gbm_dtrees ..

make shell compile

Then load the bitstream to vcu118, restart the host, and load the driver to produce this error

@d-kor d-kor self-assigned this Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants