1. Please describe the problem: On an armhfp guest with an XFS filesystem and lpae kernel (aarch64 host running rhel 8.1), attempting to run mock: vmscan: shrink_slab: super_cache_scan+0x0/0x150 negative objects to delete nr=-2147483644 is repeated on the console. When left to continue eventually it hits oom-killer. The system has plenty of RAM available and does not touch swap. [root@localhost ~]# free total used free shared buff/cache available Mem: 41368220 165068 40591308 592 611844 40709764 Swap: 8380412 0 8380412 2. What is the Version-Release number of the kernel: 5.3.7-301.fc31.armv7hl+lpae 5.4.7-200.fc31.armv7hl+lpae 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Unknown. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Reproducible running an armhfp guest with 25G+ RAM allocated, and using an XFS filesystem. I have not been able to reproduce with ext4. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Will check and update the BZ. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
Created attachment 1650796 [details] oom backtrace
Created attachment 1650797 [details] journalctl
Looks like it can be triggered with any sort of load. A simple 'dnf update' was sufficient. No change with 5.5.0-0.rc5.git0.1.fc32.armv7hl+lpae
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.