[Bug 27949] New: [KMS] After wake from Suspend2Ram is OS freezed Xorg 7.5 - MESA R300 - Radeon9550 (RV350)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=27949

           Summary: [KMS] After wake from Suspend2Ram is OS freezed Xorg
                    7.5 - MESA R300 - Radeon9550 (RV350)
           Product: xorg
           Version: 7.5
          Platform: x86 (IA32)
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/Radeon
        AssignedTo: xorg-driver-ati at lists.x.org
        ReportedBy: snop3 at seznam.cz
         QAContact: xorg-team at lists.x.org


Created an attachment (id=35392)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=35392)
my xorg.cong, which I have used in all older OS versions

Hi,

I haven't never problems with suspend2ram on my mythbuntu computer, i'm
using mythbuntu from version 8.04 LTS and before I have used this comp
for my own purposes with Ubuntu and it was from version dapper drake
6.06 without any problems with suspend2ram.

Now I have upgraded from 9.10 Karmic Koala with Xorg 7.4 to the 10.04
Lucid Lynx with Xorg 7.5 ( where is KMS enabled ) and when I do suspend2ram and
then wake up
(it's connected only TV-Output SVideo) the TV looks like this:
http://img203.imageshack.us/i/foto01113927428.jpg/
http://img535.imageshack.us/i/foto01103934043.jpg/


EVERYTHING is without problem, Xorg detects my graph. card without
xorg.conf without any problems ( that it's great !!! ) and it's only
connected TV-Output SVideo !

I have tried start with my xorg.conf, which I have used in all older
versions of the mythbuntu it's in attachment.

I'm attaching Xorg log files without xorg.conf and Xorg log file with my
xorg.conf.

Some info from glxheads:
  GL_VERSION:  1.5 Mesa 7.7.1
  GL_VENDOR:   DRI R300 Project
  GL_RENDERER: Mesa DRI R300 (RV350 4153) 20090101 x86/MMX+/3DNow!+/SSE
TCL DRI2

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.