| Summary: | xf86-video-modesetting: Broken video after hibernate | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | nucleo <nucleo> | ||||||||||
| Component: | Driver/other | Assignee: | Patrik Jakobsson <patrik.r.jakobsson> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
| Severity: | major | ||||||||||||
| Priority: | medium | ||||||||||||
| Version: | unspecified | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| URL: | https://bugzilla.redhat.com/show_bug.cgi?id=888859 | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
The same problem with xf86-video-modesetting-0.6.0 driver. I have similar problems with Poulsbo (same kernel driver) but on suspend. We need to probe outputs and set the mode again upon resume. Fbdev seems to force a modeset on resume (by a VT switch) but modesetting does not. I'll see if I can fix this. On second thought, it seems your GTT mappings are lost after hibernate and we need to remap the pages. fbdev is still working because the stolen memory it uses is already mapped by the bios. Unfortunately I have a different issue that I need to solve first before I can get to the point where your problem appears. I'll report back when I have something for you to test. (In reply to comment #3) Thanks for working on this issue. I tried last release xf86-video-modesetting-0.7.0, issue still present. I've now (hopefully) addressed all the issues with hibernate/suspend for cedarview and poulsbo. Could you please test my tree at: https://github.com/patjak/drm-gma500.git gma500-next Thanks Patrik Created attachment 77569 [details] [review] gma500 kernel patch I still use 3.5.6 kernel, so I applied to its sources this patch with last 5 commits from drm-gma500.git. But unfortunately nothing changed. Still video broken after hibernation and fine after suspend. Thanks for testing. I've added some debugging info in commit: 1611f8457768716ba2397e0cdcc92c863cf9b58b drm/gma500: Add debugging info to psb_gtt_restore() It should tell us how many of the ranges (if any) are restored and the total size. Could you apply that patch, boot with drm.debug=0xe and attach the dmesg output? It could also be worth trying to compile the full kernel instead of patching up 3.5.6, there are plenty of changes since then. Created attachment 78045 [details]
dmesg
Now I applied last 10 commits from drm-gma500.git to gma500 from 3.8.7 kernel.
I mean last 8 commits. dmesg just after system started after hibernation. Result after hibernation was the same. Ok, you're not hitting the psb_gtt_restore path at all. There must be something missing in 3.5.6 that is present in 3.8-rc6. There are plenty of power management fixes since the 3.5 days so it's a pain to track it down. The only thing I can recommend is for you to try out my 3.8-rc6 tree. If you hit the gtt restore code you should see (in dmesg) something like: [drm:psb_gtt_restore], Restored 2 of 6 gtt ranges (4143 KB) One range is your framebuffer and the other is your cursor buffer. Thanks Created attachment 78078 [details] dmesg Now I booted with kernel from drm-gma500.git, and looks like problem with video after hibernation fixed. In Comment 8 I forgot to say that booted with kernel 3.8.7 and pached gma500 module but maybe commits used for patch not enough. Great, thanks for testing. It seems a bit odd that 3.8.7 with the patches applied didn't work but perhaps I overlooked something. Now that I know these patches don't wreck havoc on Cedarview I'm gonna ask for it to be pulled into drm-next and for inclusion in 3.10. What missing patch needed to fix problem in older kernel? There are 57 patches touching gma500 since 3.5 and that is not including any changes made to drm. I'm afraid it's not worth backporting this. I tried to compile with kernel 3.8.7 gma500 code from drm-gma500.git but with reverted two commits that makes compilation failed https://github.com/patjak/drm-gma500/commit/362063619cf67c2c2fc2eb90951b2623cbb69a7c#drivers/gpu/drm/gma500/framebuffer.c https://github.com/patjak/drm-gma500/commit/0a819515fc346b4e79d6e3fc01d837a660452c74#drivers/gpu/drm/gma500/psb_drv.c But this module also don't fixes video after hibernation and I don't see message [drm:psb_gtt_restore], Restored 2 of 4 gtt ranges (2415 KB) Maybe answer why patched gma500 don't work with 3.8.7 kernel is in reason why psb_gtt_restore don't called and some simple fix for this can be found? |
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 71813 [details] modesetting after hibernate Description of problem: Video broken when system waked up after hibernate. System is Asus X101CH with Intel gma3600 video card (gma500_gfx kernel driver used). Version-Release number of selected component (if applicable): xf86-video-modesetting-0.5.0 xorg-x11-server-1.13.1 (Fedora 18) How reproducible: Every time. Steps to Reproduce: 1. Start hibernate mode from menus or run "systemctl start systemd-hibernate.service". 2. Resume system. Actual results: Xorg video broken (see screenshot) no errors in Xorg.0.log. I can switch to terminal with Ctrl+Alt+F2, video there is fine, then I can restart kdm.service (and Xorg server) and then video in Xorg becames fine. Expected results: Video should not be broken after hibernate. Additional info: After suspend video is fine. Video is not broken after hibernate if fbdev Xorg driver used instead of modesetting.