On 05/18/2011 01:23 PM, Ian Pilcher wrote:
>
> It looks like the problematic commit is one of:
>
> e1ff5182304e00c0d392092069422cae7626cf8d Handle drawable/client
> destruction in pending swaps/flips
>
> 86f23f21ab57fcbc031bcd2b8f432a08ff4cc320 Skip client and drawable
>resource delete
On 05/18/2011 10:54 AM, Ian Pilcher wrote:
> I'm in the process of trying to bisect 2.14.0 - 2.15.0.
It looks like the problematic commit is one of:
e1ff5182304e00c0d392092069422cae7626cf8d Handle drawable/client
destruction in pending swaps/flips
86f23f21ab57fcbc031bcd2b8f432a08ff4cc320 S
On 05/18/2011 02:43 AM, Chris Wilson wrote:
> What sort of tasks do you do during the sessions that encounter this
> corruption? Is it limited to a single chipset?
It doesn't seem to take much ... I basically log in to KDE (startx), do
a bit of work, and logout. I haven't been able to reproduce t
On Tue, 17 May 2011 23:17:01 -0500, Ian Pilcher wrote:
> With the recently pushed Fedora 15 update to 2.15.0, I'm getting a hard
> X hang every time I log out. gdb backtrace reveals that glibc is dead-
> locking trying to report a heap corruption:
What sort of tasks do you do during the sessions
With the recently pushed Fedora 15 update to 2.15.0, I'm getting a hard
X hang every time I log out. gdb backtrace reveals that glibc is dead-
locking trying to report a heap corruption:
#0 __lll_lock_wait_private () at
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:100
#1 0x7fb07f8c
