|Summary:||aarch64 mustang: unhandled level  translation faults|
|Product:||[Fedora] Fedora||Reporter:||Peter Robinson <pbrobinson>|
|Component:||kernel||Assignee:||Peter Robinson <pbrobinson>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||23||CC:||gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, mjuszkie, msalter, pbrobinson, rmaas|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2016-10-26 17:00:51 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Peter Robinson 2015-08-31 13:58:09 UTC
Comment 1 Mark Salter 2015-08-31 15:41:16 UTC
The thing that jumps out at me is the 18446744073709545384 pages reserved. This is calculated as total_reserved - total_cma and should never fall below zero (18446744073709545384 is -6232) because cma should be included in total_reserved. So something bad happened to the page accounting, but I'm not sure what.
Comment 2 Peter Robinson 2015-08-31 16:21:40 UTC
(In reply to Mark Salter from comment #1) > The thing that jumps out at me is the 18446744073709545384 pages reserved. > This is calculated as total_reserved - total_cma and should never fall below > zero (18446744073709545384 is -6232) because cma should be included in > total_reserved. > So something bad happened to the page accounting, but I'm not sure what. Sounds lovely :-/ is there a debug option(s) we could enable to try and get more information? We can recreate it in about 5 days
Comment 3 Laura Abbott 2015-08-31 16:23:26 UTC
I think the CMA issue is known, see https://patchwork.kernel.org/patch/6825901/ which is now in the mmotm tree http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/commit/lib/show_mem.c?id=3a83eda52f34b97168b70098ef0e34dbcaeaaf8f The unhandled faults are all userspace crashes. Something not getting the memory it wants and then crashing?
Comment 4 Mark Salter 2015-08-31 18:34:37 UTC
I still think pages reserved is wrong. There should be more than cma pages. Agree about unhandled faults. I wasn't concerned about those. The page allocation failures are the issue with network going down (last one leaves driver without a ring buffer for rx packets). The question is why are we running out of memory?
Comment 5 Fedora End Of Life 2015-11-04 10:40:29 UTC
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Comment 6 Peter Robinson 2015-11-04 10:53:17 UTC
Bumping to F-23, the patch is applied, we're still seeing some issues, we'll know more when we move the builders to F-23 (and hpefully 4.3) around the same time.
Comment 7 Marcin Juszkiewicz 2016-02-09 18:40:57 UTC
Comment 8 Ronald Maas 2016-03-16 03:22:27 UTC
Try updating /etc/sysctl.conf with the following line and reboot: vm.min_free_kbytes=131072 Default value was 15256 for Centos 7.2 arm64, which is apparently too low for X-Gene hardware. After this change the page allocation failure did not occur again. Hope this helps, Ronald
Comment 9 Laura Abbott 2016-09-23 19:55:39 UTC
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. 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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
Comment 10 Laura Abbott 2016-10-26 17:00:51 UTC
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.
Comment 11 Peter Robinson 2017-07-03 12:12:37 UTC