Summary: | [CI][SHARDS] igt@gem_userptr_blits@readonly-unsync - fail - WARNING: CPU: 2 PID: 1202 at mm/filemap.c:220 unaccount_page_cache_page | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | KBL | i915 features: | GEM/Other |
Description
Martin Peres
2019-07-08 09:12:16 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * KBL: igt@runner@aborted - fail - Previous test: gem_userptr_blits (readonly-unsync) - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3240/shard-kbl3/igt@runner@aborted.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6413/shard-kbl2/igt@runner@aborted.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13508/shard-kbl7/igt@runner@aborted.html The complaint is that it saw a dirty page... But all dirt should have been flushed by the invalidate/truncate itself. One possibility is that the rcu fput() is racing against shmemfs activity... Except we fput after we teardown the pages on freeing the object -- there should not be a race! So I wonder if this is our race at all. I haven't seen this since v5.2, so I am assuming it wasn't ours. |
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.