Bug 1211

Summary:	Xorg produce garbage screen after resume from suspend to disk
Product:	xorg	Reporter:	Konstantin Filtschew <mailoperator>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED NOTOURBUG	QA Contact:
Severity:	major
Priority:	high
Version:	git
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Konstantin Filtschew 2004-08-27 12:14:31 UTC

hi,

System: IBM Laptop T40 2373-8cg
Debian Linux Sid
Kernel 2.6.8.1 + acpi patch
ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
Xorg.CVS from 2004-08-27 6pm middle european time

I have that small problem and don't know how to fix this.
Suspend to Ram works fine without problems.

If I try to suspend to disk: swsusp oder pmdisk,I get
a garbage screen after resume with Xwindows running.

swsusp2 trys to change to Xwindows after console view,
but can not manage it and the Xwindows freezes.

I've tried it without a windows manager and it is always
the same behaviour.

here are some logs(in both  nothing special):
http://fallenangel.deathcon.de/xorg.log
http://fallenangel.deathcon.de/dmesg.log

I've tried to remove all modules from kernel and tried it
with modules, but nothing changed.

For testing, I've used the Frame buffer radeon(new) device
and on console with the fb-dev and without every suspend
worked fine.

Because of the not used windows manager(for testing), I think
this must be a x.org problem. Console suspending and resuming
was always without problems.

Greetz

Konstantin Filtschew

Comment 1 Konstantin Filtschew 2004-08-27 12:30:46 UTC

killing Xorg with:

Ctl + Alt + <== 

and tipieng in blindly "startx" works fine.
The screen turns to normal and I can work
again. Also returning to console works after killing
the Xwindows and restarting it.
But it's not a solution :(

Comment 2 Konstantin Filtschew 2004-08-28 05:06:56 UTC

that was not xorg, but the dri module for ati.

Have to contact the guys!

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.