yuzhaogoogle

Thanks. Now we may consider switching all boards to MGLRU on 6.1 😀

So I guess you didn't find the package either? Just checking in case somebody has successfully built Firefox and uploaded the package somewhere.

The stock image of VisionFive has a working Firefox. Where can I download Firefox for Armbian, if there is one? Thanks.

Thanks all. Ubuntu released images for Nezha and VisionFive last week.

Great work! Are we expecting an official release for VisionFive? If so, what's its ETA? Thanks!

Yeah, I'm working on it. Will keep you posted. Thanks.

I guess most users won't hit this problem unless they poke into the debugfs interface.

Great job! 💯🎉🍻 Thank you! @jock

Hi @jock According to the following warning from dmesg.log, it seems the first version of the fix @hexdump posted was used -- unfortunately it's also buggy (sorry)... [ 1235.795803] ------------[ cut here ]------------ [ 1235.795827] WARNING: CPU: 2 PID: 55 at mm/vmscan.c:4464 lru_gen_look_around+0x3fc/0x728 I do have the latest MGLRU backported to v5.18, and you can apply it by git fetch https://linux-mm.googlesource.com/page-reclaim refs/changes/17/1617/2 && git cherry-pick FETCH_HEAD~14..FETCH_HEAD I'm also trying to attach the patch file here but it seems I'm too new to be allowed to attach files. Please feel free to send me an email if you need the patch file or anything else. From kernel_panic.log, it seems the bad thing already happened before root@rk3318-box:~# [ 9596.639183] BUG: Bad page state in process kswapd0 pfn:1d8b6 [ 9596.640943] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000a60 Usually the Bad page state warning appears when there is a double-free or free-after-use memory corruption. It'd be helpful if there is a way to grab the log preceding this error. Alternatively, if we can't fix the v5.18 baseline kernel, I can further backport MGLRU to v5.17.

@hexdumppointed me to this discussion -- thank you for all the testing, much appreciated! If you have MGLRU related questions, please feel free to shoot me emails. The following option occasionally causes problems, so please set it to zero. The analyses from Ubuntu, Debian and a few others I'm too lazy to quote $ cat /proc/sys/vm/watermark_boost_factor 0 I'll submit a fix later today and hopefully it'll be in v5.20.