From: Pavel Machek <pavel@ucw.cz>
To: "legolas558@users.sourceforge.net" <legolas558@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
Date: Sat, 20 Oct 2007 20:33:09 +0200 [thread overview]
Message-ID: <20071020183309.GB11373@elf.ucw.cz> (raw)
In-Reply-To: <4719EAEB.6060703@users.sourceforge.net>
Hi!
> > Try disabling acpi embedded controller.
> >
> How can I accomplish this? Are you referring to the i8042?
rmmod acpi_ec or how is it called. But I'm not sure how easy this is.
> > Try watching keyboard interrupts. Are they lost?
> >
> I am pretty sure they are. I think that ACPI pauses interrupts for a
> while (100ms?) and so some keyboard interrupts are lost.
input layer can poll keyboard on its own, perhaps that helps?
Can you try to measure the interrupt latencies?
Does this happen in init=/bin/bash?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-10-20 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 21:42 [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c legolas558
2007-10-11 8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
2007-10-12 11:52 ` Laptop keyboard unusable when ACPI is active legolas558
2007-11-22 7:24 ` legolas558
2007-11-24 4:21 ` Len Brown
2007-11-24 19:08 ` legolas558
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
2007-10-20 11:47 ` legolas558
2007-10-20 18:33 ` Pavel Machek [this message]
2007-10-21 9:43 ` legolas558
2007-11-24 4:27 ` Len Brown
2007-11-24 19:14 ` legolas558
2007-10-21 11:07 ` legolas558
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=20071020183309.GB11373@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=legolas558@users.sourceforge.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 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).