From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Subject: dead keyboard in lk 2.5.25
Date: Sun, 07 Jul 2002 10:20:16 -0400 [thread overview]
Message-ID: <3D284E20.D5D00F99@torque.net> (raw)
When I first booted lk 2.5.25 on an Athlon box the AT keyboard
was inactive. The mouse worked and the box was accessible across
the network so it looked like a problem with the keyboard or its
driver.
/var/log/messages contained this sequence:
Jul 6 09:57:00 frig kernel: mice: PS/2 mouse device common for all mice
Jul 6 09:57:00 frig kernel: spurious 8259A interrupt: IRQ7.
Jul 6 09:57:00 frig kernel: i8042.c: Can't get irq 1 for KBD
Jul 6 09:57:00 frig kernel: i8042.c: Can't get irq 1 for KBD
Jul 6 09:57:00 frig kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jul 6 09:57:00 frig kernel: input.c: hotplug returned -2
and /proc/interrupts indicated that irq 1 was owned by
"keyboard" which implied drivers/char/pc_keyb.c owned the
keyboard. The attempt by "i8042" to claim irq 1 returned
-EBUSY which caused the "can't get irq 1" line above.
Since nobody else has reported this error it could be
local to my environment. If you get this problem, the
crude patch below fixed it for me.
Doug Gilbert
--- linux/drivers/input/serio/i8042.c Sat Jul 6 08:57:35 2002
+++ linux/drivers/input/serio/i8042.c2525fix Sun Jul 7 09:52:50 2002
@@ -269,8 +269,11 @@
*/
if (request_irq(values->irq, i8042_interrupt, 0, "i8042", NULL)) {
- printk(KERN_ERR "i8042.c: Can't get irq %d for %s\n", values->irq, values->name);
- return -1;
+ free_irq(values->irq, NULL);
+ if (request_irq(values->irq, i8042_interrupt, 0, "i8042", NULL)) {
+ printk(KERN_ERR "i8042.c: Can't get irq %d for %s\n", values->irq, values->name);
+ return -1;
+ }
}
/*
next reply other threads:[~2002-07-07 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 14:20 Douglas Gilbert [this message]
2002-07-07 15:45 ` dead keyboard in lk 2.5.25 Russell King
2002-07-07 21:26 ` Vojtech Pavlik
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=3D284E20.D5D00F99@torque.net \
--to=dougg@torque.net \
--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.