Bug 1759879
Summary: | System hang up when memory swapping (kswapd deadlock) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mirek Svoboda <goodmirek> | ||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 31 | CC: | airlied, bskeggs, goodmirek, haydn.reysenbach, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, pasik, patdung100+redhat, redhat, samoht0-bugzilla, steved | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-03-25 22:25:15 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Mirek Svoboda
2019-10-09 10:12:24 UTC
The issue happens also on non-tainted kernel-5.3.5-300.fc31.x86_64. I/O Scheduler: BFQ While the issue is happening, the disk LED indicates no disk activity, although the LED works otherwise. Attaching kernel log dmesg-5.3.5.txt from an affected run of 5.3.5 kernel. Created attachment 1623777 [details]
kernel 5.3.5 log
Trying rawhide kernel 5.4.0-0.rc1.git1.1.fc32.x86_64. It is also affected by this bug. I see following warning in dmesg: <truncated> Oct 09 13:47:08 kernel: WARNING: possible circular locking dependency detected Oct 09 13:47:08 kernel: 5.4.0-0.rc1.git1.1.fc32.x86_64 #1 Not tainted <truncated> *** DEADLOCK *** Oct 09 13:47:08 kernel: 4 locks held by kswapd0/157: Oct 09 13:47:08 kernel: #0: ffffffff83781540 (fs_reclaim){+.+.}, at: __fs_reclaim_acquire+0x5/0x30 Oct 09 13:47:08 kernel: #1: ffffffff837743d8 (shrinker_rwsem){++++}, at: shrink_slab+0x134/0x2b0 Oct 09 13:47:08 kernel: #2: ffff8e2e0dd920e8 (&type->s_umount_key#56){++++}, at: trylock_super+0x16/0x50 Oct 09 13:47:08 kernel: #3: ffff8e2e0dd57a58 (&pag->pag_ici_reclaim_lock){+.+.}, at: xfs_reclaim_inodes_ag+0x95/0x450 [xfs] Full dmesg is attached. Created attachment 1623793 [details]
kernel log 5.4.0-0.rc1.git1.1.fc32.x86_64
I have opened an upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=205135 Only known recovery from the freeze is a hard reset. This is not a temporary freeze, but system hang up. This unreproduced bot crash sounds related to me: https://lore.kernel.org/linux-mm/20190910071804.2944-1-hdanton@sina.com/ Something for the maintainers to look into. kernel-5.4.0-0.rc2.git1.1.fc32.x86_64 is also affected. Everyone who uses a swapfile on XFS filesystem seem affected by this hang up. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. The issue does not happen on FC31 with kernel 5.5.13. |