Summary: | [945GM] 32x32 GL_RGBA textures get corrupted after suspend/resume cycle | ||
---|---|---|---|
Product: | Mesa | Reporter: | Guy Lunardi <glunardi> |
Component: | Drivers/DRI/i915 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | eich, kent.liu, mat, quanxian.wang, reveman |
Version: | unspecified | Keywords: | NEEDINFO |
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
xorg.conf
Xorg.0.log dmesg-suspend-resume preview-border.png (fullscreen) preview-border-small.png (small) preview-glow-right.png (how it is supposed to look) xrandr --verbose output mesa texobj demo without idle function |
Description
Guy Lunardi
2009-02-10 07:52:53 UTC
Created attachment 22755 [details]
xorg.conf
Created attachment 22756 [details]
Xorg.0.log
Will cause the issue to happen again when in the office and will attach the additional documents here (dmesg output and a screenshot). I don't think this is mode related but will check. Created attachment 22760 [details]
dmesg-suspend-resume
Created attachment 22761 [details]
preview-border.png (fullscreen)
Created attachment 22762 [details]
preview-border-small.png (small)
Created attachment 22763 [details]
preview-glow-right.png (how it is supposed to look)
Created attachment 22764 [details]
xrandr --verbose output
This happens when only the LVDS output is enabled or when VGA and LVDS are used together.
I doubt it is xrandr mode related but here is my xrandr output anyway just in case.
Again regardless of the outputs and mode used, I seem to end up with that texture corrupted.
I'm betting that this is fixed with GEM+UXA. Created attachment 22824 [details] [review] mesa texobj demo without idle function not specific to 32x32 GL_RGBA textures. can easily be reproduced with mesa's texobj demo program. it could be specific to indirect rendering only. I attached the source for this demo prog but with the idle function disabled so it only redraws when receiving expose events. suspend seems to fail completely when idle function is enabled and it's constantly redrawing but I guess that's a different issue. 1) start the attached texobj demo with LIBGL_ALWAYS_INDIRECT=1 ./texobj 2) suspend to RAM 3) resume from suspend 4) the textures used by texobj demo are now corrupt
>
> Reproducible: 100%
> 1) enable that compiz is running and windows preview plug-in is enabled
> 2) ensure window previews show up when mouse over window list applet
> 3) suspend to RAM
> 4) resume from suspend
> 5) mouse over the window list applet
> 6) you will notice the border and shadows are not properly rendered
>
How to enable windows preview plug-in? Anyone knows that?
Also I remember 945GM will not enable compiz as default. It has some problems on 2008Q3 release.
(In reply to comment #12) > How to enable windows preview plug-in? Anyone knows that? The easiest way to do this is to use the "ccsm" application provided on SLED by the compizconfig-settings-manager package. The plugin itself "Windows Previews" is actually called thumbnail (libthumbnail.so). It is provided by the compiz-fusion-plugins-main package on SLED. Within ccsm, you should see the Windows preview configuration and the ability to enable it (check box). Alternatively, you can try to load the plugins at the command line with something like: "compiz --replace ccp text mousepoll thumbnail" > Also I remember 945GM will not enable compiz as default. It has some problems > on 2008Q3 release. Generally it is actually running rather well for me. I have used compiz on this machine since early 2006 with the help of David. Lately the number of issues related to compiz on that machine is very small. No idea if any of this is useful, thank you for looking into it. Best regards, -Guy So, is this working with GEM and UXA enabled? Feedback timeout for reproducing this bug on current software. Please reopen if you have the issue with the current driver. |
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.