-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
BUG: Bad page state in process #865
Comments
My usual rule of thumb says that seemingly random crashes in MM code are often due to a power supply fault. Is your Pi2 adequately powered? Are the USB devices externally powered? Start your use case then after a while run If the crashes are more systematic then I would begin to suspect one of the drivers. |
The PSU has nice rapi logo on it, and identifies itself as USB wise, I have two self powered hubs connected to it. I've run vcgencmd get_throttled a few times and always get 0x0 back. It's running at 600 MHz, using the powersave controller. |
So it's not power then - thanks, I had to ask. Looking more closely at the log you can see that it appears to be corruption of a contiguous set of
This is interesting because If it happens again then report back, but until then we don't have enough to go on. |
Will do. I've run this box for 2+ years and all but the initial few months using own compiled kernels (gentoo). I've never seen this exact error, but other kernel crashes has been there. As a tidbit, when I moved to gcc5 (userspace and kernel) I got the perception that I got more segfaults (userspace), and kernel memory stuff such as unaligned accesses in kernelspace and what not. Got me thinking that gcc5@gentoo was not stable for arm. Now I'm back to all gcc4, and those errors are gone (user and kernel space). I'm inclined to move userspace to gcc5 in a few months to see what happens. I see you use crosstool gcc 4.x. Any reason you're not on gcc5 yet? |
Another question I should have asked earlier - are you overclocked? Toolchain changes can reveal different silicon-specific timing issues when running the chip at out-of-spec clock speeds. I'll let @popcornmix answer the gcc5 question. |
gcc 4.9 has been used to match the version debian jessie uses. |
Hi, I'm not overclocked. config.txt says: dtdebug=on cpupower frequency-info: If I get more memory related errors I'll look into changing the psu. As for now, the kevent errors are the most common source of lockups. |
I would advise against spending money on a new PSU - based on what you've said so far it now seems unlikely to be a power problem. However, transient power glitches may go unnoticed by the firmware, so we can't rule it out. If you get a similar crash again, one option would be to patch the "Bad page state" error code to print a hex dump of a larger window around the offending |
Thanks. I'll keep that in mind. |
Another weird kernel error which might be related. [58483.819723] Unable to handle kernel paging request at virtual address f5613015 |
Closing due to lack of activity. Please request to be reopened if you feel this issue is still relevant. |
While streaming TV from tvheadend, I was greeted with this bug. This is on foundation provided 4.9.45 kernel. Never seen this before (on my self-compiled kernels)
The text was updated successfully, but these errors were encountered: