Date: Fri, 5 Sep 2014 07:57:51 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: =?ISO-8859-15?Q?Jean-S=E9bastien_P=E9dron?= <jean-sebastien.pedron@dumbbell.fr> Cc: freebsd-stable@freebsd.org Subject: Re: Anyone else seeing lockup on boot with r271042? Message-ID: <alpine.BSF.2.11.1409050756560.23440@wonkity.com> In-Reply-To: <5408897F.2040107@dumbbell.fr> References: <alpine.BSF.2.11.1409031427070.81751@wonkity.com> <20140903204605.GA16445@dft-labs.eu> <alpine.BSF.2.11.1409031535120.4771@wonkity.com> <alpine.BSF.2.11.1409031616230.15085@wonkity.com> <5408402B.20704@FreeBSD.org> <alpine.BSF.2.11.1409040647180.31288@wonkity.com> <5408897F.2040107@dumbbell.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Sep 2014, Jean-Sébastien Pédron wrote:
> On 04.09.2014 14:52, Warren Block wrote:
>> With r271092, the lockup is still present and consistent.
>
> Another report on this mailing-list ("middle-mouse button pasting broken
> by r271022") makes me think that some commits were not merged yet. I'll
> check that.
As of r271160, startup does not have a problem with devd. Only tested
once, though.
From owner-freebsd-stable@FreeBSD.ORG Fri Sep 5 15:32:38 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id EC1BEEA5;
Fri, 5 Sep 2014 15:32:38 +0000 (UTC)
Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mailout00.t-online.de",
Issuer "TeleSec ServerPass DE-1" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id A9B381508;
Fri, 5 Sep 2014 15:32:38 +0000 (UTC)
Received: from fwd24.aul.t-online.de (fwd24.aul.t-online.de [172.20.26.129])
by mailout07.t-online.de (Postfix) with SMTP id 7D96D5939A8;
Fri, 5 Sep 2014 17:32:30 +0200 (CEST)
Received: from [192.168.119.33]
(Z4H7TkZSrhH6gla2XqA1Ecxi7hwa9vxkY+lnNr0-3gXDhAJi1RWbk75BzEqcsKrQKJ@[84.154.101.219])
by fwd24.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted)
esmtp id 1XPvUr-2PeSES0; Fri, 5 Sep 2014 17:32:21 +0200
Message-ID: <5409D77B.5030500@freebsd.org>
Date: Fri, 05 Sep 2014 17:32:11 +0200
From: Stefan Esser <se@freebsd.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: Julien Cigar <jcigar@ulb.ac.be>, =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWQ=?=
=?UTF-8?B?cm9u?= <jean-sebastien.pedron@dumbbell.fr>
Subject: Re: Xorg segfaults with vt
References: <20140905085024.GL43967@mordor.lan> <54098186.9070904@dumbbell.fr>
<20140905093640.GM43967@mordor.lan>
In-Reply-To: <20140905093640.GM43967@mordor.lan>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-ID: Z4H7TkZSrhH6gla2XqA1Ecxi7hwa9vxkY+lnNr0-3gXDhAJi1RWbk75BzEqcsKrQKJ
X-TOI-MSGID: 0d5923f9-2845-48ef-b2dd-d361f7ff704e
Cc: x11@freebsd.org, freebsd-stable@freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>;
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 15:32:39 -0000
Am 05.09.2014 um 11:36 schrieb Julien Cigar:
> On Fri, Sep 05, 2014 at 11:25:26AM +0200, Jean-SĂ©bastien PĂ©dron
> wrote:
>> On 05.09.2014 10:50, Julien Cigar wrote:
>>> Hello,
>>
>> Hello!
>>
>>> I just updated two machines and Xorg produces a segmentation
>>> fault when I $> startx. This happens only when vt is enabled
>>> (syscons is OK).
>>
>> You probably hit this bug:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191459
>
> Yes it seems to be that one.. Thanks!
We really should do something to fix this X11 server crash!
The patch I suggested in PR 193192 (a duplicate of 191459, which
perhaps should be merged into 191459, but I have no idea whether
that is possible with bugzilla), removes just the offending keys
from the map.
https://bz-attachments.freebsd.org/attachment.cgi?id=146584&action=diff&context=patch&format=raw
This will e.g. remove the Euro sign (0x20ac), but lead to an
otherwise usable keyboard in a *working* X session.
My suggested patch is just a work-around, no real fix, but it
will help avoid people wasting lots of time trying to understand
why their X server suddenly stops to work.
Since I'm in part responsible for the crashes (by committing
actual vt keymaps, that use Unicode code points >= 0x100), I'd
really like to get this fixed, before people testing the 10.1
pre-releases think that X11 has been completely broken.
Is there really nobody on the x11 list, who wants to commit this
simple patch, to stop people wasting their time or becoming
frustrated because of the X11 server crash???
It is just a work-around, but a very necessary one!!!
Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1409050756560.23440>