Bug 20134

Summary: [G33] GL temporary "hangs" when running Xorg for the second time
Product: xorg Reporter: Loïc Minier <lool>
Component: Driver/intelAssignee: Eric Anholt <eric>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: n-roeser
Version: 7.4 (2008.09)Keywords: NEEDINFO
Hardware: All   
OS: All   
i915 platform: i915 features:
Description Flags
Working Xorg.0.log from Feb 12
NON-Working (slow) Xorg.0.log from Feb 12 none

Description Loïc Minier 2009-02-16 01:05:27 UTC

compiz works relatively fine on my G33 hardware, but if I startx + logout + startx, it will be slow and hangs frequently for a couple of seconds (especially when switching workspaces).  This only happens in the second run of Xorg, during my first session it seems alright.  This bug was recently discovered after the resolution of bug #9498.

I'll attach Xorg logs of the two sessions.

I can see some warnings appearing in the second run:
[    0.987232] (WW) intel(0): PIPEASTAT before: status: VSYNC_INT_STATUS
[    0.987238] (WW) intel(0): PIPEASTAT after: status: FIFO_UNDERRUN

and later:
[    1.200378] (WW) intel(0): ESR is 0x00000001, instruction error
[    1.200385] (WW) intel(0): Existing errors found in hardware state.

Current package versions (Ubuntu 9.04/Jaunty):

libdrm-dev 2.4.4-0ubuntu6
libdrm-intel1 2.4.4-0ubuntu6
libdrm2 2.4.4-0ubuntu6
xserver-xorg-core 2:
xserver-xorg-video-intel 2:2.6.1-1ubuntu2

Comment 1 Loïc Minier 2009-02-16 01:06:57 UTC
Created attachment 22974 [details]
Working Xorg.0.log from Feb 12
Comment 2 Loïc Minier 2009-02-16 01:07:32 UTC
Created attachment 22975 [details]
NON-Working (slow) Xorg.0.log from Feb 12
Comment 3 Eric Anholt 2009-08-03 10:49:50 UTC
Does the problem still exist with KMS?  The G33 is touchy as far as setting up the hardware state, and it may be that setup after a teardown is failing, which would be avoided with KMS.
Comment 4 Eric Anholt 2009-10-09 14:44:34 UTC
Feedback timout -- we expect that this is fixed with KMS.  Please re-open if the problem still exists.

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.