mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31.5: /dev/input/event? are gone sometimes
Date: Sat, 24 Oct 2009 14:05:40 -0700	[thread overview]
Message-ID: <20091024210540.GA15297@core.coreip.homeip.net> (raw)
In-Reply-To: <4AE308A8.2070309@t-online.de>

Hi Harald,

On Sat, Oct 24, 2009 at 04:01:12PM +0200, Harald Dunkel wrote:
> Hi folks,
>
> Sometimes (by chance, as it seems) the /dev/input/event? devices
> are not working after power-on or reboot. They are not listed in
> /proc/bus/input/devices. The mouse in X is not moving, keyboard
> is dead, etc. All I can do is reboot and hope.
>
> Below you can find the diff of /proc/bus/input/devices between
> a bad and a good start.
>
>
> udev is 146-5 (included with Debian Sid).
>
>
> Any helpful hints would be highly appreciated. Of course I can
> send you the .config, if there is some interest.
>
>
> Regards
>
> Harri
> ===================================================================
> % diff -u devices.bad devices.good
> --- devices.bad 2009-10-24 15:08:24.000000000 +0200
> +++ devices.good        2009-10-24 15:17:17.000000000 +0200
> @@ -3,7 +3,7 @@
>  P: Phys=isa0060/serio0/input0
>  S: Sysfs=/devices/platform/i8042/serio0/input/input0
>  U: Uniq=
> -H: Handlers=kbd
> +H: Handlers=kbd event0

Since evdev binds to -every_ input device registered its absence in the
handlers list suggests that the module is not loaded. I am not sure how
and when your distribution loads evdev; try making it built-in to avoid
cases when it is not loaded for one reason or another.

-- 
Dmitry

      reply	other threads:[~2009-10-24 21:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-24 14:01 Harald Dunkel
2009-10-24 21:05 ` Dmitry Torokhov [this message]

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=20091024210540.GA15297@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=harald.dunkel@t-online.de \
    --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®