linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org, linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: 2.6.15.1: Frequent keyboard driver reset
Date: Sun, 22 Jan 2006 00:28:40 -0500	[thread overview]
Message-ID: <200601220028.41161.dtor_core@ameritech.net> (raw)
In-Reply-To: <200601220012.05970.arvidjaar@mail.ru>

On Saturday 21 January 2006 16:11, Andrey Borzenkov wrote:
> I have Ali based Toshiba notebook. In dmesg I see frequent resets like:
> 
> input: AT Translated Set 2 keyboard as /class/input/input6
> input: AT Translated Set 2 keyboard as /class/input/input7
> input: AT Translated Set 2 keyboard as /class/input/input8
> 
> Interesting is I checked sysfs after having seen those messages and
> 
> {pts/0}% LC_ALL=C ll /sys/class/input
> total 0
> drwxr-xr-x  6 root root 0 Jan 21 13:14 input1/
> drwxr-xr-x  4 root root 0 Jan 21 23:54 input8/
> drwxr-xr-x  2 root root 0 Jan 21 13:14 mice/
> lrwxrwxrwx  1 root root 0 Jan 22 00:02 mouse0
> -> ../../class/input/input1/mouse0/
> lrwxrwxrwx  1 root root 0 Jan 22 00:02 ts0 -> ../../class/input/input1/ts0/
> 
> So it appears similar to SCSI - old instance is stuck and new instance is
> created.
>

Hmm, I lost you... input1 is mouse, input8 is keyboard. I don't see
anything "stuck" here.

> How can I debug it further? System information:
>

I would start with opening the notebook and reseating keyboard cable.
 
-- 
Dmitry

      reply	other threads:[~2006-01-22  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 21:11 2.6.15.1: Frequent keyboard driver reset Andrey Borzenkov
2006-01-22  5:28 ` 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=200601220028.41161.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=arvidjaar@mail.ru \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --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;
as well as URLs for NNTP newsgroup(s).