-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
zram kernel oops on PI4-8GB board in 32bit #3839
Comments
I have a very similar issue (the same?) also with a PI4-8GB board in 32bit. A slightly different stack trace though |
kern :err : [ 2218.163204] zram: Decompression failed! err=-22, page=33126 uname -a I think similer. It happens after newest kernel update. |
Does disabling the upper 4GB of RAM using |
Yes, loads fine that way |
And am I right in thinking, given the issue title, that the 64-bit kernel has no such problems? Should we be unable to find a solution to this, would saying "use the 64-bit kernel" be an option for you? |
Correct 64bit kernels load zram fine. I opened the issue after ensuring RaspiOS had the same problem, but my work is purely for the custom OS piCorePlayer. Which loads the whole base OS on a Ramdrive. We had been running 64bit kernels with 32bit user space on piCorePlayer. But I'll be launching pCP7 soon, and we will now have a 32bit userland and a 64 bit userland. Right or wrong, we use the kernel mode to know what environment we are running. So now using the 64bit kernel with 32 bit userland is not a good option for us. Our images still work on every rpi board, so those older boards with small memory sizes, we do see a benefit from using the zram compression. So we ship images with Zram on. If you cannot find a solution, I would likely build a trap in the zram startup script to not load if memory size is >4gb. Let me know if I need to go that route. |
It happened to me too. RPI4, 4GB
|
[32375.779020] swapper/0: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 pi 3B 1GB 32bit uname -a |
@yutayu, your log message contains nothing about zram. |
@Alexey-Tsarev |
Same here on a Pi Zero W. Sporadic: on Linux version 5.4.72+ (dom@buildbot) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #1356 Thu Oct 22 13:56:00 BST 2020 |
https://askubuntu.com/questions/1295809/zram-decompression-failed-with-new-kernels This error happens in arm kernel only. |
It seems to me as with the recent kernel update the bug is gone on my PI Zero W. I am now on: May be someone can confirm that between 72+ and 79+ something was done on corresponding code parts? |
[39580.361213] zram: Decompression failed! err=-22, page=25684 free -h zramctl with 3B , Still it happens when I use chromium. |
@lanmarc77 |
root@raspberrypi:/etc/modprobe.d# cat zsmalloc.conf modprobe -D zsmalloc I am trying this mobule option. [ 25.091398] zsmalloc: unknown parameter 'pgtable_mapping' ignored In vain sorry. |
Just another "me too" ... I also find my PI4-8GB board crashes when I try to use zram. |
uname -a It seeems fixed. |
@yutayu Thanks for the update, I will reenable it on my pi zero and report back in a week or so |
No problems detected anymore. Works for me on a Pi Zero W |
@paul-1 okay to close? |
Sure thing. |
Describe the bug
Enabling zram swap space causes kernel oops. This only happens on the Pi4-8GB board. The 4GB board (And other Pi boards) works fine.
To reproduce
System
Pi4-8GB (Raspberry Pi 4 Model B Rev 1.4)
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Linux raspberrypi 5.4.61-v7l+ #1339 SMP Tue Sep 1 18:51:27 BST 2020 armv7l GNU/Linux
Logs
The text was updated successfully, but these errors were encountered: