Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1387793
| Summary: | Constant alloc_contig_range: [X, Y) PFNs busy | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeremy Linton <jeremy.linton> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, r.c.i.mackenzie, rrichter |
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
| Target Release: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-28 17:04:57 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 245418 | ||
|
Description
Jeremy Linton
2016-10-21 22:30:24 UTC
The messages come from CMA allocation attempts and are a verbose way of saying the range CMA tried was not able to be allocated. This has been brought up before upstream and I think it was decided to keep the messages because it helps with debugging. I'm guessing there is something doing DMA (backed by CMA by default on aarch64) constantly and the system is under under a particular load that makes CMA allocations fail. There is a patch series in progress to fundamentally rework CMA (https://marc.info/?l=linux-mm&m=147641419014561&w=2) so I would suggest that needs to be tested as a first step. If the problem is still happening, this would need to be investigated further as a CMA problem. I faced a similar issue, where some PFNs of a zone were not assigned to the same node, leading to different zones for the PFNs and a failing zone check. See this fix: http://www.spinics.net/lists/arm-kernel/msg535191.html This was introduced with NOMAP mem ranges (see patch description). That new implementation does not properly initialize nomap pages (the memmap) which causes zone checks to fail. You can check if the c250-c251 phys mem range is marked as nomap. I used following kernel parameters for more (mm) verbosity: debug uefi_debug memblock=debug efi=debug loglevel=8 mminit_loglevel=4 It would be interesting if my patch also fixes this issue. I should add this is Juno, so I can tweak the mem ranges. (or alternativly this might be a firmware problem if the memory ranges are tagged incorrectly). I could be seeing the same issue. I'm running a newly installed copy of fedora 25 on a Raspberry Pi 3. I have freshly updated all packages this evening using dnf to (4.8.12-300.fc25.armv7hl) but the system remains really very laggy with any application taking ages to start. Often the mouse freezes when starting the terminal. The system is fairly unusable at the moment. dmesg gives lots output like this: [ x ] alloc_contig_range: [y, z) PFNs busy *********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. 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 26, and are still experiencing this issue, please change the version to Fedora 26. 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 2 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. |