mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Xorg doesn't find input devices with "Input: allow matching device IDs on property bits" applied
Date: Mon, 23 Oct 2017 06:02:06 +1030	[thread overview]
Message-ID: <83e020ff-959e-9a75-5bab-380c7e1373b0@internode.on.net> (raw)

After a recent git pull and kernel build and reboot, Xorg could not find 
the input devices and I was left with unresponsive mouse and keyboard 
until I could remotely shut-down and boot into an earlier kernel.

With good kernels, Xorg.log showed evdev finding the mouse and keyboard.

Bisecting lead to this commit:

  git bisect good
8724ecb072293f109a6f5dc93be8a98bf61fe14f is the first bad commit
commit 8724ecb072293f109a6f5dc93be8a98bf61fe14f
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Mon Oct 9 12:01:14 2017 -0700

     Input: allow matching device IDs on property bits

     Let's allow matching input devices on their property bits, both 
in-kernel
     and when generating module aliases.

     Tested-by: Roderick Colenbrander <roderick.colenbrander@sony.com>
     Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

:040000 040000 4192943bfd5affbe9e86c14efd690bda5c90bd82 
d30b9d9c3a7ed1a6078f56a3bec2a82e0ba09570 M      drivers
:040000 040000 d39ca313c8d6dc86ad1175bf9374c76d9c134e82 
8717e17cbb0556629dd8cf7a7c34694dd299925c M      include
:040000 040000 ba4684d3706ca73868f39e90f673e3926e23e3ba 
811ed0e561768778c86eefa4c5ea5f866a542156 M      scripts

I am happy to run further tests if needed.

Arthur.

             reply	other threads:[~2017-10-22 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 19:32 Arthur Marsh [this message]
2017-10-22 19:33 ` Randy Dunlap
2017-10-22 19:45   ` Dmitry Torokhov
2017-10-22 19:53     ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83e020ff-959e-9a75-5bab-380c7e1373b0@internode.on.net \
    --to=arthur.marsh@internode.on.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®