Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#69468 - System freeze with "kernel BUG at mm/shmem.c:940!"

Attached to Project: Arch Linux
Opened by Zhao Rui (renyuneyun) - Friday, 29 January 2021, 15:30 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 19 September 2021, 08:59 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Andreas Radke (AndyRTR)
Jan Alexander Steffens (heftig)
Levente Polyak (anthraxx)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I was using the system, with a video conference in the background and webpage in the front. Then the whole system freezes. When booted again, checking the logs, it says: kernel BUG at mm/shmem.c:940!
May be related to swap, though I'm not sure. I have 16G RAM and 16G swap. The system has swap used at that time.


Additional info:
* linux 5.10.10.arch1-1

Steps to reproduce:

Not sure.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 19 September 2021, 08:59 GMT
Reason for closing:  No response
Comment by Zhao Rui (renyuneyun) - Friday, 29 January 2021, 15:31 GMT
I'm attaching the relevant part of the journal (seems missing from the post).
Comment by Emati Mitame (Mitame) - Friday, 12 February 2021, 00:47 GMT
Possibly run into this as well, but in a completely different scenario (mpd + browser pretty much), and without a complete freeze. Instead, the kernel got stuck in a spinlock (i think) on 3 cores, with the system still mostly responsive (though my touchpad also stopped working, so not sure).

This was in linux 5.10.12-arch1-1
   kernel.log (429.9 KiB)
Comment by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 10:14 GMT
Is this still an issue? Can we close it after many updates?

Loading...