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
Possible kernel memory corruption / driver crash #522
Comments
Yeah, correlation seems pretty strong, multiple crashes per day with openrazer installed and none in two months without it. |
When the crashes happen do you interact with the driver at all? Or just when the driver is loaded? Can you reproduce the issue at all or is it just these random crashes? |
It seems to happen after resume-from-ram or after connecting or disconnecting the keyboard, but not immediately, but after a few minutes of delay. I cannot reproduce it easily, even if I suspend and resume many times it doesn't always occur, but in normal usage (a few disconnects per day) it occurs daily. Symptoms are that first all input devices stop working but clock on the screen still runs, then after a few seconds the clock also stops and I have to reboot, after which I find the crash message in /var/log. |
uninstall it and see if it stops |
Yes, no crashes since I uninstalled openrazor in February. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
After installing openrazer-kernel-modules-dkms 2.2.0~ubuntu16.04.1 on kernel 4.10.0-42-generic with Razer Ornata, my computer has started crashing every few days. The timing matches and it's previously been very stable, but there is nothing directly pointing to openrazer so this is just a hunch for now. I'll uninstall the driver and monitor what happens, but here is a report in case someone else hits this.
Log from crash:
Which seems to happen in kfree() in the usb driver for my card reader. Perhaps some kind of heap corruption?
The text was updated successfully, but these errors were encountered: