From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Éric Piel" <eric.piel@tremplin-utc.net>
Cc: Greg KH <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore
Date: Wed, 21 Oct 2009 13:20:16 -0700 [thread overview]
Message-ID: <200910211320.16339.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <4ADF6237.9070004@tremplin-utc.net>
On Wednesday 21 October 2009 12:34:15 pm Éric Piel wrote:
> Op 15-10-09 23:59, Dmitry Torokhov schreef:
> > Hm, this is wierd... In the dmesg you sent me in the previous mail I see:
> >
> > input: AT Raw Set 2 keyboard as
> > /devices/platform/i8042/serio0/input/input4
> >
> > So it looks like sometimes it is in raw and sometimes it is in
> > translated mode. The i8042.reset might be affecting it. Also, are you
> > using BIOS password at resume by any chance?
> >
> > I guess we'll have to wait till you get back to the box and then I want
> > fresh debug dmesgs (after poweroff) of older (with bind/unbind) and
> > latest kernels, going through boot, 1st (make sure to type qwerty) and
> > 2nd resume (qwerty again). Make sure you don't have any other i8042 or
> > atkbd switches besides i8042.debug.
>
> Hello,
> Back with some results :-)
>
> Attached is a (bzip-compressed) log [1] of a 2.6.30 kernel started with
> i8042.debug (nothing else important).
>
> The log contains 4 suspend-resumes (look for "Back to C"):
> * from the console, using "echo mem > /sys/power/state", keyboard fine
> * from the console, using "pm-suspend" (aka "all the nasty stuff done by
> the distro"), keyboard fine
> * from X, using "echo mem > /sys/power/state", keyboard gone
> * a unbind-bind cycle, keyboard back
> * from X, using "echo mem > /sys/power/state", keyboard fine
>
>
> What I realised during this experiment, is that the keyboard goes away
> after the first suspend-resume _in X_. Each time, I typed on the
> keyboard "qwerty" (and almost nothing else).
>
> Do you see what goes wrong in resuming the keyboard?
>
Nothing, as far as I can tell... I see you typing "qwerty"... Does the
keyboard work in console (let's say if you boot in run level 3 to take X out
of the picture)? Could you please try compiling evbug module - it will show if
keyboard events are propagated through input core. Also, whta driver are you
using in X? Legacy keyboard or evdev?
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Éric Piel" <eric.piel@tremplin-utc.net>
Cc: Greg KH <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore
Date: Wed, 21 Oct 2009 13:20:16 -0700 [thread overview]
Message-ID: <200910211320.16339.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <4ADF6237.9070004@tremplin-utc.net>
On Wednesday 21 October 2009 12:34:15 pm Éric Piel wrote:
> Op 15-10-09 23:59, Dmitry Torokhov schreef:
> > Hm, this is wierd... In the dmesg you sent me in the previous mail I see:
> >
> > input: AT Raw Set 2 keyboard as
> > /devices/platform/i8042/serio0/input/input4
> >
> > So it looks like sometimes it is in raw and sometimes it is in
> > translated mode. The i8042.reset might be affecting it. Also, are you
> > using BIOS password at resume by any chance?
> >
> > I guess we'll have to wait till you get back to the box and then I want
> > fresh debug dmesgs (after poweroff) of older (with bind/unbind) and
> > latest kernels, going through boot, 1st (make sure to type qwerty) and
> > 2nd resume (qwerty again). Make sure you don't have any other i8042 or
> > atkbd switches besides i8042.debug.
>
> Hello,
> Back with some results :-)
>
> Attached is a (bzip-compressed) log [1] of a 2.6.30 kernel started with
> i8042.debug (nothing else important).
>
> The log contains 4 suspend-resumes (look for "Back to C"):
> * from the console, using "echo mem > /sys/power/state", keyboard fine
> * from the console, using "pm-suspend" (aka "all the nasty stuff done by
> the distro"), keyboard fine
> * from X, using "echo mem > /sys/power/state", keyboard gone
> * a unbind-bind cycle, keyboard back
> * from X, using "echo mem > /sys/power/state", keyboard fine
>
>
> What I realised during this experiment, is that the keyboard goes away
> after the first suspend-resume _in X_. Each time, I typed on the
> keyboard "qwerty" (and almost nothing else).
>
> Do you see what goes wrong in resuming the keyboard?
>
Nothing, as far as I can tell... I see you typing "qwerty"... Does the
keyboard work in console (let's say if you boot in run level 3 to take X out
of the picture)? Could you please try compiling evbug module - it will show if
keyboard events are propagated through input core. Also, whta driver are you
using in X? Legacy keyboard or evdev?
--
Dmitry
next prev parent reply other threads:[~2009-10-21 20:20 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 2:05 [REGRESSION] "bind" a device to a driver doesn't not work anymore Dmitry Torokhov
2009-10-14 2:05 ` Dmitry Torokhov
2009-10-15 17:24 ` Éric Piel
2009-10-15 18:13 ` Dmitry Torokhov
2009-10-15 18:13 ` Dmitry Torokhov
2009-10-15 18:27 ` Dmitry Torokhov
2009-10-15 18:27 ` Dmitry Torokhov
2009-10-15 19:32 ` Éric Piel
2009-10-15 19:51 ` Dmitry Torokhov
2009-10-15 19:51 ` Dmitry Torokhov
2009-10-15 21:33 ` Éric Piel
2009-10-15 21:59 ` Dmitry Torokhov
2009-10-15 21:59 ` Dmitry Torokhov
2009-10-15 22:44 ` Éric Piel
2009-10-21 19:34 ` Éric Piel
2009-10-21 20:20 ` Dmitry Torokhov [this message]
2009-10-21 20:20 ` Dmitry Torokhov
2009-10-22 16:10 ` Éric Piel
2009-10-22 16:22 ` Dmitry Torokhov
2009-10-22 16:22 ` Dmitry Torokhov
2009-10-22 17:48 ` Éric Piel
2009-10-22 17:48 ` Éric Piel
2009-10-22 18:19 ` Dmitry Torokhov
2009-10-22 18:19 ` Dmitry Torokhov
2009-10-22 18:32 ` Dmitry Torokhov
2009-10-22 18:32 ` Dmitry Torokhov
2009-10-23 8:08 ` Éric Piel
2009-10-23 8:58 ` Dmitry Torokhov
2009-10-23 8:58 ` Dmitry Torokhov
2009-10-23 9:21 ` Éric Piel
2009-10-23 9:21 ` Éric Piel
2009-10-23 16:31 ` Dmitry Torokhov
2009-10-23 16:31 ` Dmitry Torokhov
2009-10-25 11:47 ` Éric Piel
2009-10-25 19:07 ` Dmitry Torokhov
2009-10-25 19:07 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2009-10-11 0:04 Éric Piel
2009-10-11 3:00 ` Greg KH
2009-10-12 4:35 ` Dmitry Torokhov
2009-10-12 11:46 ` Éric Piel
2009-10-12 14:44 ` Greg KH
2009-10-12 14:44 ` Greg KH
2009-10-12 15:45 ` Dmitry Torokhov
2009-10-12 15:45 ` Dmitry Torokhov
2009-10-12 17:37 ` Greg KH
2009-10-12 17:37 ` Greg KH
2009-10-12 15:48 ` Dmitry Torokhov
2009-10-12 16:48 ` Éric Piel
2009-10-12 16:48 ` Éric Piel
2009-10-12 17:35 ` Greg KH
2009-10-12 18:33 ` Dmitry Torokhov
2009-10-12 18:54 ` Greg KH
2009-10-12 19:20 ` Dmitry Torokhov
2009-10-12 19:58 ` Greg KH
2009-10-13 3:17 ` Dmitry Torokhov
2009-10-18 7:51 ` Dmitry Torokhov
2009-10-18 8:02 ` Greg KH
2009-10-23 2:01 ` Dmitry Torokhov
2009-10-26 20:59 ` Greg KH
2009-10-26 21:34 ` Dmitry Torokhov
2009-10-26 23:59 ` Greg KH
2009-10-27 16:16 ` Dmitry Torokhov
2009-10-13 9:52 ` Éric Piel
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=200910211320.16339.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=eric.piel@tremplin-utc.net \
--cc=gregkh@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.