From owner-freebsd-current@FreeBSD.ORG Sun Mar 14 21:44:25 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 855A1106566C for ; Sun, 14 Mar 2010 21:44:25 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 481EC8FC15 for ; Sun, 14 Mar 2010 21:44:24 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id o2ELiXOR079595; Sun, 14 Mar 2010 21:44:33 GMT (envelope-from kientzle@freebsd.org) Received: from horton.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id sm5rwstfpf82yi9qiugi863nde; Sun, 14 Mar 2010 21:44:32 +0000 (UTC) (envelope-from kientzle@freebsd.org) Message-ID: <4B9D58B5.4050002@freebsd.org> Date: Sun, 14 Mar 2010 14:44:21 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20100105 SeaMonkey/1.1.18 MIME-Version: 1.0 To: Peter Jeremy References: <4B989064.5030105@freebsd.org> <7d6fde3d1003102245l41ab8287r81680aa40281d802@mail.gmail.com> <4B9C9885.5040601@freebsd.org> <20100314195622.GA88471@server.vk2pj.dyndns.org> In-Reply-To: <20100314195622.GA88471@server.vk2pj.dyndns.org> Content-Type: multipart/mixed; boundary="------------060408090904080708090203" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-x11@freebsd.org, "freebsd-current@freebsd.org" Subject: Re: X11 crash on exit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 14 Mar 2010 21:44:25 -0000 This is a multi-part message in MIME format. --------------060408090904080708090203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Peter Jeremy wrote: > On 2010-Mar-14 00:04:21 -0800, Tim Kientzle wrote: >> Okay, I've updated a bunch of ports and am still seeing the >> crash. I rebuilt the server with debug symbols and finally >> got something informative; here's the relevant portion of >> the backtrace (frame #10 is the signal 11 delivery). >> >> #11 0x0819e363 in DeliverPropertyEvent (pWin=0x5a5a5a5a, >> value=0xbfbfec0c) at rrproperty.c:34 >> #12 0x0807015d in TraverseTree (pWin=0x28775f80, func=0x819e340 >> , data=0xbfbfec0c) at window.c:234 .... >> #18 0x0806f4e3 in FreeAllResources () at resource.c:824 >> #19 0x0806bbf0 in main (argc=4, argv=0xbfbfed68, envp=0xbfbfed7c) at >> main.c:411 > > This looks identical to the problem I reported as ports/131930. > Whilst my patch wasn't applied, ISTR a similar patch got applied > upstream to fix the issue. I've run through portsnap/portupgrade a few times, so my server should be up-to-date and I still see the crash. I suspect the upstream patch you're referring to would be the memset(WindowTable, 0, sizeof()) that appears a few lines after the call that triggers the crash. > Other than that, I can confirm that you _can_ run X on an AA1, > at least on 8.x (that's what I'm currently using). What window manager are you using? Right now, I'm using TWM but suspect there's something a bit better suited to this small screen. (Ideally, something that adapts well to either the built-in screen or the external 20" monitor I often use.) > Are you using hal/dbus? Yes. I implemented the fix I suggested earlier (scanning the WindowTable to remove Window objects as they're deleted) and it does consistently resolve the crash, but now the X server restarts itself when xinit asks it to exit, so there's clearly still something amiss. Patch attached for anyone interested. Tim --------------060408090904080708090203--