Bug 28471

Summary: Intermittent X server failures when unlocking screen
Product: xorg Reporter: James <theholyettlz>
Component: Driver/intelAssignee: Carl Worth <cworth>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
First Xorg.0.log with EQ overflow
none
Second Xorg.0.log with EQ overflow none

Description James 2010-06-09 13:45:29 UTC 
Created attachment 36182 [details]
First Xorg.0.log with EQ overflow

I've been seeing some instabilities in X with:

xorg-x11-server-Xorg-1.8.0-12.fc13.x86_64
xorg-x11-drv-intel-2.11.0-4.fc13.x86_64

on Intel X3100 graphics. The common thread is that problems occur most frequently when unlocking the screen, i.e., typing in the password and hitting the Enter key. On two occasions now X has locked with EQ overflows (see attached Xorg logs), and on a couple of others it has segfaulted when the screen is unlocked.

In one of the EQ overflow incidents, I was able to kill X and restart it (albeit with a few corrupted graphics at the subsequent login screen). The Xorg.0.logs from both incidents are attached. Info on the segfaults was collected by Abrt and may be found at:

https://bugzilla.redhat.com/show_bug.cgi?id=596022
https://bugzilla.redhat.com/show_bug.cgi?id=601110


Other components present:

kernel-2.6.33.5-112.fc13.x86_64
gnome-screensaver-2.30.0-1.fc13.x86_64
gnome-power-manager-2.30.1-1.fc13.x86_64
Comment 1 James 2010-06-09 13:46:20 UTC 
Created attachment 36183 [details]
Second Xorg.0.log with EQ overflow
Comment 2 Chris Wilson 2010-07-01 06:51:21 UTC 
Excuse the forward dupe. My working hypothesis for these "infinite loop" is that we are triggering another page-fault-of-doom. Whilst patching the kernel to prevent the lockup is important, I have some (longer term) alternate plans for doing fallback acceleration that should circumvent the issue.

*** This bug has been marked as a duplicate of bug 28478 ***

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.