Summary: | [PNV] S3 /S4 resume cause call trace, and screen failed to light up after resume while X is running. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Ding Heng <hengx.ding> | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||||||
Version: | DRI git | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Created attachment 116386 [details]
xorg log
This might be a duplicate of bug 90396, where the force restore modeset fails in the atomic checks. Could you reproduce the bug again with 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg again? Created attachment 116410 [details]
dmesg with drm.debug=0x1e
(In reply to Ander Conselvan de Oliveira from comment #2) > This might be a duplicate of bug 90396, where the force restore modeset > fails in the atomic checks. Could you reproduce the bug again with > 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg > again? I had tried the bisect commit in bug 90396, this kernel works well on PNV. (In reply to Ander Conselvan de Oliveira from comment #2) > This might be a duplicate of bug 90396, where the force restore modeset > fails in the atomic checks. Could you reproduce the bug again with > 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg > again? [ 295.839385] [drm:drm_atomic_helper_check_modeset] [CRTC:22] enabled/connectors mismatch ... [ 295.839449] [drm:drm_atomic_helper_check_modeset] [CRTC:19] enabled/connectors mismatch It's the same bug. *** This bug has been marked as a duplicate of bug 90396 *** |
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.
Created attachment 116385 [details] dmesg System Environment: -------------------------- Regression: not sure. Platform: PNV kernel: drm-intel-testing-05-22 Bug detailed description: ----------------------------- S3 and S4 will cause call trace in dmesg. Screen will fail to light up after S3/S4 resume while X is running. Reproduce steps: --------------------------- 1. xinit & 2. echo mem > /sys/power/state 3. resume and check if the screen shows normally. 4. kill X and check dmesg.