[[6.11.5] Unraid crash (kernel: BUG: Bad rss-counter state mm:00000000f7646224 type:MM_SHMEMPAGES val:1)]

As the bug appears to originate within huge_memory.c, would it be worth turning off transparent huge pages and seeing if that cures the issue? There seems to be a lot of issues with hugepages at the moment and looking at the kernel forums there seem to be unresolved issues with splitting pages, particularly with Docker as it also uses hugepages if they are enabled.

 

See this post for details on turning off THP - https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/?do=findComment&comment=21761

 

Alternatively you could add transparent_hugepage=never to the end of your flash drive syslinux config (Main -> Flash -> syslinux configuration -> Unraid OS -> add to end of append statement 'append initrd=/bzroot transparent_hugepage=never')

[Crashes since updating to v6.11.x for qBittorrent and Deluge users]

On 11/29/2022 at 3:15 PM, binhex said:

no, the upstream build is still using libtorrent 2.x as can be seen from the qbittorrent web ui:-

That's odd, the qbittorrent build config appears to require the addition of a flag to include libtorrent 2.x otherwise it will default to building with 1.2.18?

[Crashes since updating to v6.11.x for qBittorrent and Deluge users]

15 hours ago, canuck said:

So, I reverted back to 6.10.3, uninstalled all the plugins i've been using (recommended via another post). I'm still experiencing hard crashes.

I had some odd issues when I reverted and found some data corruption in my docker images (possibly from crashes in 6.11.1). I removed everything and re-installed all dockers and plugins and it has been running perfectly since. Might be worth a shot?