From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754115AbYCaExl (ORCPT ); Mon, 31 Mar 2008 00:53:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751768AbYCaExc (ORCPT ); Mon, 31 Mar 2008 00:53:32 -0400 Received: from fg-out-1718.google.com ([72.14.220.154]:61897 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751610AbYCaExb (ORCPT ); Mon, 31 Mar 2008 00:53:31 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rr6hO64sMY0rZSx8M7WpOxgSOXdURd4uDx8IJi9Ou6B2Jvbidg05fKqezqcE+4aHvordzNGEq3VNvw6xr9FkxnQXfNlL0aDTNPnicGTvf55c332Akkv05aWN5444g+z2v8oPGu6JNgeDjM0QfolIVgL3QmoHGpYdBTWJFFVfRls= Message-ID: <21d7e9970803302153s314d48d3o7120a56092eeaede@mail.gmail.com> Date: Mon, 31 Mar 2008 14:53:29 +1000 From: "Dave Airlie" To: "Tilman Schmidt" Subject: Re: [2.6.25-rc6] possible regression: X server dying Cc: linux-kernel@vger.kernel.org In-Reply-To: <21d7e9970803241753q433e7545pdd00eae189846a8@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47E82D68.5070305@imap.cc> <21d7e9970803241622v10b887a6p869535102b486279@mail.gmail.com> <47E83D14.8070800@imap.cc> <21d7e9970803241753q433e7545pdd00eae189846a8@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 25, 2008 at 10:53 AM, Dave Airlie wrote: > > On Tue, Mar 25, 2008 at 9:45 AM, Tilman Schmidt wrote: > > On Tue, 25 Mar 2008 09:22:32 +1000, Dave Airlie wrote: > > > On Tue, Mar 25, 2008 at 8:38 AM, Tilman Schmidt wrote: > > >> In the five days since I booted a 2.6.25-rc6 kernel on my development > > >> machine, it has happened three times already that I came back to the > > >> machine to find that the X server had exited, killing all applications > > >> that still had a window open. [...] > > > > > > > > anything in the X.org logfiles? > > > > Ah, of course. Sorry I forgot. Xorg.0.log.old ends with this: > > > > | Backtrace: > > | 0: /usr/bin/X(xf86SigHandler+0x81) [0x80e6d81] > > | 1: [0xb7fc9400] > > | 2: > > /usr/lib/xorg/modules//extensions/libGLcore.so(_swrast_Triangle+0x2d) > > [0xb51ea5dd] > > | 3: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb51f1075] > > | 4: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb5206f2e] > > | 5: /usr/lib/xorg/modules//extensions/libGLcore.so [0xb52080b8] > > | 6: > > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_run_pipeline+0x153) > > [0xb520cb83] > > | 7: > > /usr/lib/xorg/modules//extensions/libGLcore.so(_tnl_draw_prims+0x3f0) > > [0xb51f8340] > > | 8: > > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_vtx_flush+0x1fb) > > [0xb52471eb] > > | 9: > > /usr/lib/xorg/modules//extensions/libGLcore.so(vbo_exec_FlushVertices+0x78) > > [0xb52488e8] > > | 10: /usr/lib/xorg/modules//extensions/libGLcore.so(_mesa_Flush+0x83) > > [0xb5112663] > > | 11: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c6a107] > > | 12: /usr/lib/xorg/modules//extensions/libglx.so [0xb7c4aa6d] > > | 13: /usr/bin/X [0x815809e] > > | 14: /usr/bin/X(Dispatch+0x1af) [0x808f68f] > > | 15: /usr/bin/X(main+0x47e) [0x807717e] > > | 16: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d5dfe0] > > | 17: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x8076501] > > | > > | Fatal server error: > > | Caught signal 11. Server aborting > > any look finding what might have caused this? it certainly looks like some heap or address space change affects Mesa. Dave.