When I run GHCi, it sometimes segfaults immediately. Reproducible: Sometimes Steps to Reproduce: 1. Run GHCi. Actual Results: $ ghci GHCi, version 9.2.6: https://www.haskell.org/ghc/ :? for help ghc-9.2.6: mmap 4096 bytes at (nil): Cannot allocate memory ghc-9.2.6: Try specifying an address with +RTS -xm<addr> -RTS Segmentation fault (core dumped) Expected Results: GHCi does not segfault.
Created attachment 1966312 [details] ABRT info including coredump
Thanks for the report - I have noticed the abrt backtraces :-( This is actually due to mmap related changes in the Linux kernel... As a workaround you can try using ghc9.4 instead for the time being. For more details see https://discourse.haskell.org/t/facing-mmap-4096-bytes-at-nil-cannot-allocate-memory-youre-not-alone/6259/12 where I also posted a comment, including a workaround (ghc scratch build) for F38.
Also a partial temporary workaround is to revert from kernel-6.3 to 6.2 which seems less affected. Or 6.2.9 which doesn't have the problem.
I may start by first committing the proposed upstream backport to the ghc9.2 package first.
Moving this at least temporarily to kernel for awareness.
FEDORA-2023-5c8c091faf has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5c8c091faf
I have pushed fixed for the current Fedora ghc package (and will for Fedora ghc9.2 as well) but the problem is that any upstream ghc builds before 9.2.8 (yet to be released) or ghc 9.4 as well as any Haskell executables made with them as liable to exhibit this crash with kernel > 6.2.9. It would be great to known if the upstream is going to do anything about this. I heard there was some mm patchset perhaps, but curious if anything else is affected and if something will be done in the kernel? I will likely have to rebuild most of the executable haskell packages in Fedora too for this. For F37 we don't even have a backport. :-(
From others I believe this regression is related to the "Maple Tree" changes (I am not a kernel person). There is discussion here: https://lore.kernel.org/linux-mm/20230302184341.bju3vjqhkfm4giqm@revolver/ https://lore.kernel.org/linux-mm/190c5b1b-df67-eb54-1559-706ed4e5719a@hercules-ci.com/ https://lore.kernel.org/linux-mm/20230505145829.74574-1-zhangpeng.00@bytedance.com/
FEDORA-2023-5c8c091faf has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5c8c091faf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5c8c091faf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-2f144e888a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2f144e888a
(In reply to Jens Petersen from comment #8) > https://lore.kernel.org/linux-mm/20230505145829.74574-1-zhangpeng. > 00/ Okay I learned that this already got into kernel-6.3.4 :-) So that is quite a relief, thanks
Also fixed apparently with kernel-6.4.0-0.rc3.20230523gitae8373a5add4.29.fc39
FEDORA-2023-997fc4d8a6 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-997fc4d8a6
FEDORA-2023-2f144e888a has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-2f144e888a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-2f144e888a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-997fc4d8a6 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-997fc4d8a6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-997fc4d8a6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-514965dd8a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-514965dd8a
FEDORA-2023-2f35633034 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2f35633034
FEDORA-2023-2f35633034 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-416474be55 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-416474be55` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-416474be55 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-514965dd8a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-5c8c091faf has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-928c7761f6 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-928c7761f6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-928c7761f6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-416474be55 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-928c7761f6 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.