Here is a sample of my dmesg just after log in: http://fpaste.org/163276/ As pointed out on Google+ (https://plus.google.com/106350121860084674477/posts/WUtZZAirnfn), the first trace on line 901 is 'CPU: 0 PID: 1127 Comm: Xorg.bin Not tainted 3.17.7-300.fc21.x86_64 #1' while the others are 'CPU: 0 PID: 1127 Comm: Xorg.bin Tainted: G W 3.17.7-300.fc21.x86_64 #1'. In between, there is a warning on line 922: 'WARNING: CPU: 0 PID: 1127 at drivers/gpu/drm/i915/intel_display.c:5034 intel_modeset_check_state+0x6ec/0x7b0 [i915]()' I use Fedora 21 64-bit. Processor: Intel® Pentium(R) Dual CPU T2390 @ 1.86GHz × 2 Graphics: Intel® 965GM GNOME Shell 3.14.2 Kernel: 3.17.7-300.fc21.x86_64
Please reproduce with drm.debug=14 module parameter set, and attach the dmesg to this bug.
(In reply to Jani Nikula from comment #1) > Please reproduce with drm.debug=14 module parameter set, and attach the > dmesg to this bug. I followed the instructions someone gave me on Google+: https://plus.google.com/u/0/+GillesPhilippeMorin/posts/U97jqTzjf2T Here is the output right after login: http://fpaste.org/165045/02235791/ Is that what you wanted?
Created attachment 111671 [details] dmesg output with drm.debug=14 As asked by Jani Nikula.
I don't know if that is related, but Xorg also often fails to load at wake after suspend. The cursor and keyboard work, though, and opening a new TTY too. Also, graphics sometimes get glitchy too. I'll attach a few screenshots.
Created attachment 112243 [details] dmesg log immediately after a successful resume from suspend I get warning messages even when the resume succeeds.
Created attachment 112245 [details] Screenshot 1 of glitchy graphics
Created attachment 112246 [details] Screenshot 2 of glitchy graphics
Created attachment 112247 [details] Screenshot 3 of glitchy graphics
Created attachment 112248 [details] Screenshot 4 of glitchy graphics
Created attachment 112249 [details] Screenshot 5 of glitchy graphics
Created attachment 112250 [details] Screenshot 6 of glitchy graphics
Can you file a separate bug for the corruption issue? Do both of these issues still happen with current code?
(In reply to Jesse Barnes from comment #12) > Can you file a separate bug for the corruption issue? Do both of these > issues still happen with current code? Not anymore, no.
Great, thanks for verifying.
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.