-
Notifications
You must be signed in to change notification settings - Fork 5k
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
kernel memory corruption __kmalloc, kfree #2015
Comments
Memory corruptions like this are usually the result of an undervoltage situation.
N.B. The original CMIO board (V1.x) isn't capable of adequately powering a CM3 under heavy load - you need a V3 board. |
thanks for you help. You are probably right that it is a hardware problem. What surprises me a little though is that the overwritten bytes reported by slabinfo are always identical.
I will test with a V3 board and better cooling. |
I don't think CM3 will report under-voltage through |
@fourtrax Can this be closed? |
This issue will be closed within 30 days unless further interactions are posted. If you wish this issue to remain open, please add a comment. A closed issue may be reopened if requested. |
Closing due to lack of activity. Please request to be reopened if you feel this issue is still relevant. |
Hi, I trying to find out the reason for a kernel panic on my CM3.
The following kernel panic occurs randomly after a few hours of runtime, most of the times in kmalloc:
Also in kfree once:
To debug this I did insert "slub_debug" parameter to the kernel and ran "./slabinfo -v", which shows me this:
I am not an expert on kernel debugging but this seems to be related to the kernel panics.
I have tried a fresh installation of 2017-04-10-raspbian-jessie-lite without any modifications and slabinfo shows the same memory corruption, so it doesn't seem to be related to anything I am running on the CM3.
Any input on how to debug this is highly appreciated.
thanks in advance
The text was updated successfully, but these errors were encountered: