From: Pete Zaitcev <zaitcev@redhat.com>
To: Chris Heath <chris@heathens.co.nz>
Cc: aebr@win.tue.nl, zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: i8042 problem
Date: Sun, 27 Jul 2003 02:06:21 -0400 [thread overview]
Message-ID: <20030727020621.A11637@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030726212513.A0BD.CHRIS@heathens.co.nz>; from chris@heathens.co.nz on Sat, Jul 26, 2003 at 09:41:32PM -0400
> Date: Sat, 26 Jul 2003 21:41:32 -0400
> From: Chris Heath <chris@heathens.co.nz>
> > > drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [40]
> > > drivers/input/serio/i8042.c: 60 -> i8042 (command) [50]
> > > drivers/input/serio/i8042.c: 44 -> i8042 (parameter) [50]
> > > drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1) [51]
> > > serio: i8042 KBD port at 0x60,0x64 irq 1
> > > <------------- This is it, keyboard is dead.
> >
> > Writing 44 to the command byte disables IRQ1.
>
> It looks like a timeout problem. The ack (fa) arrived 11 ticks after
> the byte (00) was sent, but it looks like the timeout is only 10 ticks.
>
> Try playing with the timeout in atkbd_sendbyte (line 217 of
> drivers/input/keyboard/atkbd.c).
Playing with timeout does not help, but on second thought
I suspect that atkbd fails to open the port for some reason,
that's why interrupts stay disabled.
-- Pete
next prev parent reply other threads:[~2003-07-27 5:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 6:11 i8042 problem Pete Zaitcev
2003-07-26 9:36 ` Andries Brouwer
2003-07-27 1:41 ` Chris Heath
2003-07-27 6:06 ` Pete Zaitcev [this message]
2003-07-27 10:47 ` Andries Brouwer
2003-07-28 1:55 ` Pete Zaitcev
2003-07-28 11:25 ` Alan Cox
2003-07-28 11:59 ` Andries Brouwer
2003-07-28 14:01 ` Maciej W. Rozycki
2003-07-28 14:54 ` Andries Brouwer
2003-07-28 15:43 ` Maciej W. Rozycki
2003-07-28 15:51 ` Andries Brouwer
2003-07-29 18:29 ` Maciej W. Rozycki
2003-08-12 20:46 ` Vojtech Pavlik
2003-08-13 13:44 ` Maciej W. Rozycki
2003-07-28 16:07 ` Pete Zaitcev
2003-08-12 20:47 ` Vojtech Pavlik
2003-08-12 20:42 ` Vojtech Pavlik
2003-08-12 23:06 ` Andries Brouwer
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=20030727020621.A11637@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=aebr@win.tue.nl \
--cc=chris@heathens.co.nz \
--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).