-
Notifications
You must be signed in to change notification settings - Fork 31
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
Open() system call causes internal error #2
Comments
Thanks for reaching out about this -- unfortunately I haven't seen or heard about anything similar. Can you provide a bit more information about your setup?
Any additional information you can provide will help narrow down what could be going wrong. Thank you, |
Hi Katie, |
Yes, that makes sense and definitely seems like an issue. I will make a fix — thanks for following up with those details. |
Thanks so much for your detailed description of the issue here. I've incorporated a fix in the newest release (1.3.0) and added more details in the release notes. Please let me know if you run into any other issues. |
Hi,
Post deploying this driver I had tried to read the device file enumerated at /dev/U3V0 from a user application and just included some validating print statement to check whether the device file could be opened as shown in the code below.the open system call is causing the system to generate the internal error and the process hangs.
when i run dmesg i observe the following bug:
BUG:Unable to handle Kernel NULL pointer dereference at(null)
The system generates an internal errror.
However I get a Device file Opened succesfully message but the user process hangs.
Any suggestion on what could be prob and whats the solution is very much helpful.Thanks in advance
The text was updated successfully, but these errors were encountered: