From owner-freebsd-x11@FreeBSD.ORG Mon Jun 23 14:04:02 2014 Return-Path: Delivered-To: x11@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 AEBB1D7D; Mon, 23 Jun 2014 14:04:02 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CF302BFE; Mon, 23 Jun 2014 14:04:01 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id bs8so4435770wib.9 for ; Mon, 23 Jun 2014 07:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LVN0WrUGtRGdSL2TkIdoKuDoTrAbFIssOggzOeoqKKM=; b=vfm2k5yuBNnn2BiAeHHVBOLwQPQGhrzccRYcOhCj2W+VnReXdxCoXrXVit2TiolUTj 0ssSIsIuwLf/pgcsypVMu0TMsW12i0pysQqeqfaAx5fQlY3Dxq9aYUiTQbS5fRefkX7W d3ebDRtbA3XfoGIv+sBTOTydZEFupEfwwK+6JoTKRHlgxZdM3WI8+D02dPJdkm5XwAoQ J5lrCpxoIYmqu4MnMk8ZkadMQR8CDyhmRNVyX1g8nedfQhNnaEu3uladLtZgXRgmYIy/ eDpz9jcu1RMZtfmaU9Mcfk2SN7P/smAsSK/6AyD5+iocIXd/VAeVHEnyjsaS8kXXS6K7 Oizg== X-Received: by 10.180.228.6 with SMTP id se6mr26286946wic.52.1403532237712; Mon, 23 Jun 2014 07:03:57 -0700 (PDT) Received: from [192.168.1.197] (xdsl-205-163.nblnetworks.fi. [83.145.205.163]) by mx.google.com with ESMTPSA id nb8sm33689183wic.18.2014.06.23.07.03.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Jun 2014 07:03:57 -0700 (PDT) Message-ID: <53A833CC.70207@gmail.com> Date: Mon, 23 Jun 2014 17:03:56 +0300 From: Jukka Ukkonen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Warren Block Subject: Re: Xorg 7.7 suddenly lost the keyboard References: <53A03A3F.9000503@gmail.com> <53A15FD1.6040206@gmail.com> <53A4013A.2090904@gmail.com> <53A41B08.1080304@gmail.com> <53A69BA5.2090100@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kevin Oberman , ray@freebsd.org, "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 14:04:02 -0000 On 2014-06-22 15:23, Warren Block wrote: > On Sun, 22 Jun 2014, Jukka Ukkonen wrote: > >> So, AFAIK the culprit holding the kbdmux open is vt. I just did not >> even think of having also updated the OS to the latest 10-stable >> around the same time when I updated the ports kits. >> I guess there is a risk that anyone that update their OS to the latest >> 10-stable using vt instead of syscons as well as Xorg to the latest >> 7.7 which depends on vt(9) could start seeing the same lost keyboard >> problem when they launch X the next time. >> >> I cc this also to ray@freebsd.org (the author of the commit to vt >> on June 16th) hoping for a confirmation for the issue. >> Can you test using the latest 10-stable and the latest Xorg? >> >> --jau >> >> >> PS. >> In fact I already have a patch which helps with releasing the kbdmux >> device. A lot of the calls to kbd_allocate() and kbd_release() were >> passing as the token the keyboard id while other calls to the same >> functions were passing as the token a pointer to struct vt_device. >> This does not mean, though, that X were yet aware of how to wrestle >> the kbdmux device out of vt's grab and then able to open it from within >> xf86-input-keyboard. > > I'm using 10-STABLE r267699 and vt on this machine, and the keyboard > works. It could be important that HAL is not installed, xorg.conf > does not list input devices, and neither HAL nor DEVD were enabled > when building the xorg-server port. Right... Next I have to ask whether you have started X from the command line using startx or using a display manager via init and /etc/ttys? There might be some difference there. --jau PS. The patch to homogenize the use of token parameters when calling kbd_allocate() and kbd_release() is now in bugzilla.