From: "legolas558@users.sourceforge.net" <legolas558@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Cc: Pavel Machek <pavel@ucw.cz>, mnowak@redhat.com, shaohua.li@intel.com
Subject: Re: Laptop keyboard unusable when ACPI is active
Date: Thu, 22 Nov 2007 08:24:28 +0100 [thread overview]
Message-ID: <47452EAC.5060801@users.sourceforge.net> (raw)
In-Reply-To: <470F600B.3030305@users.sourceforge.net>
Hi all,
some upates about this issue (see also bug 9147
http://bugzilla.kernel.org/show_bug.cgi?id=9147 ).
The 'ac', 'battery' and 'thermal' modules (compiled as stand-alone) do
cause the bug; it suffices that one of them (or any set of them) is
loaded to trigger the bug either immediately or after some time.
If none of them is loaded into memory, the bug does not happen.
Also, the 'battery' module does not generate system messages although
the problem is equally verified.
The 'thermal' module instead, when loaded with 'modprobe thermal',
causes the enter key pressed to execute the command to be indefinitively
repeated into any terminal. This is currently a perfectly reproducible
testcase for bug 9147.
The bug has been confirmed by at least another user (with different
hardware configuration); please reply for either bug addressing or
confirmation.
The current known best workaround to this bug is to compile all the
above mentioned ACPI modules as stand-alone and to not (auto)load them
(loosing their vital functionalities, since we are talking about laptops
here, see http://gentoo-wiki.com/HARDWARE_Maxdata_Pro_7000_DX for an
example of affected hardware).
It is also important to note that this bug always comes with bug 8740
http://bugzilla.kernel.org/show_bug.cgi?id=8740 (also confirmed and also
an ACPI issue).
Best regards,
--
Daniele C.
legolas558@users.sourceforge.net ha scritto:
> I am posting this message just to say that this bug is being addressed
> on the bug tracker:
> http://bugzilla.kernel.org/show_bug.cgi?id=9147
>
> Regards,
> --
> Daniele C.
>
>
> legolas558@users.sourceforge.net ha scritto:
>
>> legolas558@users.sourceforge.net ha scritto:
>>
>>
>>> Kernel: 2.6.22-r5
>>> Kernel option: i8042.nomux=1
>>>
>>>
>> I am now using kernel 2.6.22-r8 (Gentoo) and the following kernel options:
>>
>> i8042.nomux=1 acpi=off
>>
>> I have tried kernel 2.6.23-rc9 but the problem is still there.
>>
>>
>>
>>> The problem which still remains, and I can't fix or work it around, is
>>> witnessed by the below dmesg lines:
>>> -----
>>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>>> isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>>> isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>>> atkbd.c: Unknown key released (translated set 2, code 0xe0 on
>>> isa0060/serio0).
>>> atkbd.c: Use 'setkeycodes e060 <keycode>' to make it known.
>>> -----
>>> The release event for some keys is never caught, so all sorts of
>>> troubles happen if for example I use the Del key and it stucks, or if
>>> I use the Ctrl key and it never gets released...pushing again the
>>> stuck key brings back the key in the proper status.
>>>
>>>
>> With acpi=off the problem is totally worked around.
>>
>>
>>
>>> Can somebody please give me some clues about this issue, and possible
>>> solutions? I have been searching the web for a couple of weeks and
>>> seems like it is a common trouble of notebook users, but nobody has
>>> yet published a solution.
>>>
>>>
>> I am trying to find a path myself in this issue - which dates back to at
>> least 2005 and has never been resolved.
>>
>> I would now try some other kernel parameter in order to preserve ACPI
>> functionality and possibly prevent ACPI from messing up the keyboard IRQs.
>> Can somebody please give me istructions regarding the correct tests
>> (regarding kernel parameters and/or anything else) to perform in order
>> to better isolate the issue?
>>
>> Related Gentoo bug tracker item:
>> http://bugs.gentoo.org/show_bug.cgi?id=194781
>>
>> Other messages about the same kernel bug (many more can be found
>> googling around, and no solution yet):
>> https://lists.linux-foundation.org/pipermail/bugme-new/2005-January/011736.html
>> http://dev.laptop.org/ticket/2401
>>
>> Regards,
>> --
>> Daniele C.
next prev parent reply other threads:[~2007-11-22 7:22 UTC|newest]
Thread overview: 15+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2007-11-23 7:44 Laptop keyboard unusable when ACPI is active Mats Johannesson
2007-11-24 4:04 ` Len Brown
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=47452EAC.5060801@users.sourceforge.net \
--to=legolas558@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mnowak@redhat.com \
--cc=pavel@ucw.cz \
--cc=shaohua.li@intel.com \
/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).