Summary: | [CI][DRMTIP] igt@gem_mmap_gtt@fault-concurrent - dmesg-warn - page allocation failure | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | minor | ||
Priority: | low | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | I915G | i915 features: | GEM/Other |
Description
Lakshmi
2019-09-30 10:12:53 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * GDG: igt@gem_mmap_gtt@fault-concurrent - dmesg-warn - page allocation failure - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-gdg-551/igt@gem_mmap_gtt@fault-concurrent.html Same old swap allocation failure warning. The only question here is that fault-concurrent isn't meant to be hitting swap. It uses 32 x 16MiB objects, an estimated 512 MiB which seems perhaps a little excessive, but not really. The object needs to be large enough to hit partial mmaps, but ideally we would have a mixture of object sizes to avoid them all hitting the same code paths. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/467. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.