On Ubuntu maverick kernel 2.6.35 xorg 1.9.0 latest intel drivers packaged for the platform (2.13.0+git20101025) latest libdrm packaged for the platform (2.4.22+git20101028) when suspending, at resume kwin systematically crashes reporting a segfault in 0x00007fe3fbb52900 in ?? () from /usr/lib/dri/i965_dri.so #7 0x00007fe3fbb46d77 in ?? () from /usr/lib/dri/i965_dri.so #8 0x00007fe3fbb4918a in ?? () from /usr/lib/dri/i965_dri.so before the crash, often (but not always) some screen corruption is present: 1) after resume, the screensaver appears... 2) when I press a key, a window to unlock the screen should appear. However, often only the part of the window where text is to be introduced appears, the rest of the screen remains black. While typing in the password, the rest of the window appears for very short amounts of time. At times, instead of the kwin crash, the machine freezes. When kwin crashes, most of the time it is automatically restarted and from that moment on the machine appears to be normally usable. I am experiencing this on a DELL E6500.
Please install the debug symbols for the driver (mesa-dri*dbg).
Installed. I get the following. Is this enough or should I install debug symbols from other packages as well? [KCrash Handler] #6 intel_region_buffer (intel=0x2fda5f0, region=0x0, flag=2) at intel_regions.c:514 #7 0x00007fb573c4ed77 in intelClearWithBlit (ctx=0x2fda5f0, mask=2) at intel_blit.c:266 #8 0x00007fb573c5118a in intelClear (ctx=0x2fda5f0, mask=<value optimized out>) at intel_clear.c:173
It's enough: commit 3469878bafc8d329309ef60e2473156b08fb40f3 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Oct 1 00:52:34 2010 +0100 intel: Skip clear for invalid render buffers Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=30509 Reported-by: Magnus Kessler <Magnus.Kessler@gmx.net> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> *** This bug has been marked as a duplicate of bug 30509 ***
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.