Summary: | DRI functionality is not completely restored after software suspend | ||
---|---|---|---|
Product: | xorg | Reporter: | Slava Gorbunov <slavag> |
Component: | Driver/savage | Assignee: | Tormod Volden <bugzi11.fdo.tormod> |
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | major | ||
Priority: | high | CC: | erik.andren, slava |
Version: | 6.8.99.901 (6.9 RC1) | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=4607 | ||
Whiteboard: | 2011BRB_Reviewed | ||
i915 platform: | i915 features: | ||
Attachments: |
Description
Slava Gorbunov
2006-04-16 04:12:19 UTC
Please post xorg.conf and your xorg.log after resuming from suspend. Also a backtrace of the hanging would be nice. Created attachment 5364 [details]
My xorg.conf
Created attachment 5365 [details]
Xorg.log after resuming from suspend
Created attachment 5366 [details]
Screenshot of Blender's window after resuming from suspend
Blender was started _after_ resuming from suspend (it renders all of its GUI
through OpenGL). Notice the absense of any text in its window and garbage in
the center of screen (where should be the pop-up menu) and in the top-left
corner of the screen above window frame. Before resuming everything rendered
correctly.
My xorg version is 6.8.99.901 (6.9.0 RC 1) (Minimal DRI build from X.org tree) frow dri.freedesktop.org, using savage driver from savage-20060115 snapshot. I have found the following in my syslog after system (or only X11?) lockup. Lockup was caused by running screensaver 'starwars' after resuming system from suspend-to-disk. I have also noticed small amount of garbage in the top left corner of the screen (like on screenshot with Blender's window). May 28 00:21:59 nout kernel: [drm:savage_bci_wait_event_shadow] *ERROR* failed! May 28 00:21:59 nout kernel: [drm] status=0x00008b1f, e=0x8b2b There was no other messages related to drm in syslog or Xorg.log I have this problem on Ubuntu 6.10 RC: https://launchpad.net/bugs/37218 Option "DmaMode" "None" seems to help, Option "DmaType" "PCI" helps a little less. Can we provide more information that would help you to track this down? Like register dumps before/after hibernation or more debug output from drm? Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. Now, with xf86-video-savage-2.1.2 and savage drm modules from git.freedesktop.org (this version of the driver doesn't work with drm shipped with the kernel) the behavior similar to described above (Blender doesn't render any text, garbage on the screen) is observed even without software suspend (e. g. right after clean system boot). Simple OpenGL applications (like glxgears) work fine, more complex (like Blender) aren't. The garbage pattern is different from one shown above, I'll post the screenshot later. Created attachment 10431 [details]
Blender window, just after system boot
Here is the screenshot of Blender's window, just after the system boot (without any attempts to suspend/resume) with xf86-video-savage-2.1.2 and drm modules from git.freedesktop.org. You can see that the problems, that arose only after suspend+resume with savage-2.0 and drm from the kernel (like incorrect rendering of complex objects, like fonts in Blender), now (with savage-2.1 and drm from freedesktop.org) emerge right after clean boot, without suspend/resume.
Created attachment 10432 [details]
Xorg.log (xf86-video-savage-2.1.2, drm from git.freedesktop.org)
Xorg.log. No suspend/resume, just normal boot. The problem described above exists.
Is this a kernel bug? Should this be closed out? There's no longer a savage DRI driver. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-savage/issues/1. |
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.