-
Notifications
You must be signed in to change notification settings - Fork 421
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
QDMA_Linux: bug in qdma_cdev_destroy??? #13
Comments
So I'm not too exactly how to recreate it, but basically you can try to mess with the driver a little bit, by trying to repeatidly add a queue that has already been added Running
A few times you get
Then dma util will hang
and the following dmesgs have been added to the kernel log
It seems logical that the kernel logic should tell the user program that it asked for something unreasonable, and keep going with the status quo, instead of putting itself in an invalid state (and hanging the QDMA driver). |
Issue is addressed in latest driver driver, Hence closing it. |
Not too sure how I got this to happen. But this is the basic history that I think can help recreate it.
All of this is being run as my own user, (with the fixed up udev rules).
I think there are a few timing bugs in the
dmautils
app, which is why whileqdma01000-MM-0
was created, it claims it can't find it, and just shuts down.The text was updated successfully, but these errors were encountered: