From owner-freebsd-current@FreeBSD.ORG Thu Dec 13 21:36:27 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F728B77 for ; Thu, 13 Dec 2012 21:36:27 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3AF328FC08 for ; Thu, 13 Dec 2012 21:36:27 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:3197:1202:914b:a0c8] (unknown [IPv6:2001:7b8:3a7:0:3197:1202:914b:a0c8]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 618545C5A; Thu, 13 Dec 2012 22:36:25 +0100 (CET) Message-ID: <50CA4A58.7070109@FreeBSD.org> Date: Thu, 13 Dec 2012 22:36:24 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20121128 Thunderbird/18.0 MIME-Version: 1.0 To: Johannes Dieterich Subject: Re: new xorg segfault 11 with KMS References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 21:36:27 -0000 On 2012-12-13 21:49, Johannes Dieterich wrote: > I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and > WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly > causes the segfault (log attached), gnome survives a bit longer but > starting any bigger application (e.g. firefox) causes it to crash with the > same log. > > I have a Xorg.core file, but since it is without debug symbols the > backtrace makes little sense to me. Please post the backtrace anyway. :-) Or recompile xorg-server with WITH_DEBUG=yes in your environment, and reproduce the crash.