| Summary: | [CI] igt@drv_module_reload@* - dmesg-warn - WARNING: CPU: 1 PID: 1654 at drivers/gpu/drm/drm_mode_config.c:439 drm_mode_config_cleanup | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Aditya Swarup <aditya.swarup> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | clinton.a.taylor, intel-gfx-bugs, james.ausmus |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | GLK | i915 features: | display/Other |
|
Description
Martin Peres
2018-05-30 13:14:46 UTC
This seems to be a regression introduced in drmtip_53, bumping the priority. See also https://bugs.freedesktop.org/show_bug.cgi?id=106723 and https://bugs.freedesktop.org/show_bug.cgi?id=106724 Proposing this as highest since it is a CI regression. Is it seen in BAT? Last seen 3 hours ago. 264 / 324 runs (81.5%) Attempting to reproduce out side CI system now. Changing development environment to support driver load/unload Unable to reproduce with current drm-tip Issue apparently is fixed based on CI logs starting at CI_DRM_4351. (In reply to Clinton Taylor from comment #6) > Unable to reproduce with current drm-tip > > Issue apparently is fixed based on CI logs starting at CI_DRM_4351. This has been happening again regularly since CI_DRM_4523: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4523/fi-glk-j4005/igt@drv_module_reload@basic-reload-inject.html Last one: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4780/fi-glk-j4005/igt@drv_module_reload@basic-reload.html Sorry! Clint, any update here? Latest logs from CI_DRM_5024, dmesg-warn https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5024/fi-glk-j4005/igt@drv_module_reload@basic-reload.html No update yet. Customer high priority issues. Updating the priority, last seen this issue on CI_DRM_5090_188 (3 months / 1930 runs ago). Clint/Aditya any idea if the bug has been fixed? If so, I can close this bug. @Lakshmi I just started working on this issue and I am working on some priority issue as well. This will need some time for investigation. I will keep posting updates. Current plan is for Aditya to set up 1000 runs of this test on his local RVP. If he can also not reproduce it, then we should close this. Used to happen every week, then nothing for over 4 months. Closing! The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. So, I ran the test for over 3000 iterations on glkrvp and didn't come across any failures for the basic-no-display sub-test with i915_module_load. However, the subtest reload-with-fault-injection fails for every single run. Since, the bug is filed for no-display subtest, it should be closed. |
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.