-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Kernel Oops - BUG: Bad page map in process #483
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
Comments
Are you overclocking anything - ARM, SDRAM or GPU? |
Yep (see below), the device is currently set to the 'Pi2' overclocking profile via raspi-config. I was concerned about that being a potential cause yesterday evening, so I ran approximately 2 hours of stress tests (OpenGL, CPU/Storage) but I failed to replicate any form of instability so personally dismissed it as a potential cause. /boot/config.txt |
Can you remove the overclock and see if you get the kernel panic. |
I had the same issue using overclock
I removed the overlock now and report back as well in case the kernel Oops happens again. |
@richardkennedy have you tested without overclock? |
Not entirely, reduced it to 900Mhz with a core frequency of 250, sdram of 450 and an over voltage of 2. Still monitoring at the moment, I'll go through my logs this evening to see how it's performing. |
The most likely issue is the sdram_freq. If it seems stable with no overclock, you may well be okay with the arm and core overclocks in place, but the sdram overclock disabled. (My guess is that >90% of Pi2's can handle the core and arm overclock, but perhaps only 50% can handle the sdram overclock reliably). But first, make sure everything is stable without any overclock. |
@richardkennedy how did this end up? Can this issue be closed? Please do so, if it has been resolved or provide further information for investigation. Thanks. |
@popcornmix this issue looks like it was caused by overclocking sdram. It should be closed as there have been no response to your suggestion 1 Nov 2015 |
One of my headless clients running Debian Jessie and Kernel 4.1.8 (608c3b3e994e086d400f77469682ff1e8f346e27), became unresponsive over the weekend due to a Kernel Oops (logs below) however it's the first time I've personally come across a 'Bad page map' error, is this referencing a possible OOM event? At the time of the failure, my records show that the device had a temperature of 54.6 degrees, CPU uitlisation was at 24% and RAM utilisation was at 40%. Any insight appreciated.
The text was updated successfully, but these errors were encountered: