Bug 18686

Summary: [945GM XAA] 2.5.1: S3 resume crashes
Product: xorg Reporter: Damjan Georgievski <gdamjan>
Component: Driver/intelAssignee: Jesse Barnes <jbarnes>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium Keywords: NEEDINFO
Version: 7.4 (2008.09)   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log none

Description Damjan Georgievski 2008-11-24 06:23:25 UTC 
Created attachment 20550 [details]
Xorg.0.log

I've changed to XAA because of bug #18640, but now X locks up on resume from suspend to ram. This is the last line from Xorg.0.log:

intel_bufmgr_fake.c:392: Error waiting for fence: Device or resource busy.


This is on a Thinkpad X60s - i945 onboard video, i686 architecture, ArchLinux. 
Software components are:
xorg-server 1.5.3-2
xf86-video-intel  2.5.1 (compiled from source)
libpciaccess 0.10.5-1
libdrm 2.4.1-1
intel-dri 7.2-1
libgl 7.2-1
mesa 7.2-1
Comment 1 Gordon Jin 2008-11-25 17:19:15 UTC 
Please try the kernel at git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel for-airlied branch
Comment 2 Damjan Georgievski 2008-11-26 06:42:28 UTC 
Anything special I need to enable in the kernel?

Also note that I'm using XAA and AFAIK XAA doesn't use DRM?
Comment 3 Damjan Georgievski 2008-11-26 08:38:49 UTC 
With this kernel X crashed as soon as X (the login manager) started.

Since I was not connected to a network I couldn't copy the X log file.
Comment 4 Jesse Barnes 2008-12-18 14:21:43 UTC 
Damjan, you also filed 18502 which looks similar.  Are they actually the same bug?
Comment 5 Jesse Barnes 2008-12-18 14:22:42 UTC 
Double checked the machine, seems like this is actually a DUP.

*** This bug has been marked as a duplicate of bug 18502 ***
Comment 6 Damjan Georgievski 2008-12-19 09:31:44 UTC 
Maybe it's the same bug in the software, but this one is about suspend to RAM (s3) the other was about suspend to disk (Tuxonice).

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.