From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Vojtech Pavlik <vojtech@ucw.cz>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@suse.cz>
Subject: Re: keyboard dies during failed suspend attempt
Date: Fri, 4 Nov 2005 00:11:17 -0500 [thread overview]
Message-ID: <200511040011.18393.dtor_core@ameritech.net> (raw)
In-Reply-To: <4369D04C.70509@drzeus.cx>
On Thursday 03 November 2005 03:54, Pierre Ossman wrote:
> I discovered a problem with my laptop keyboard when the machine failed
> to suspend. Pavel Machek pointed me in your direction for guidance. :)
>
> The original issue (swsusp failing) is in this thread:
>
> http://marc.theaimsgroup.com/?t=113093802700002&r=1&w=2
>
> The side issue is that the keyboard goes completely dead when the
> suspend fails like this. Not even hardware buttons that control the
> intensity of the TFT backlight work.
>
Are these controlled by ACPI?
> The problem doesn't happen every time, but it seems to be often enough
> to do some decent testing.
>
> The problem seems to have appeared after 2.6.14 was released. Since the
> problem is intermittent I can't be 100% sure of this, but it's fairly
> likely since none of the tests before 2.6.14 failed.
>
It feels like device_resume is not called somewhere when swsusp fails.
Could you try activating debug mode for i8042:
echo 1 > /sys/modules/i8042/parameters/debug
...and then making it fail. Then we'll see if i8042 resume methods are
called and whether they succeed.
--
Dmitry
next prev parent reply other threads:[~2005-11-04 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 8:54 keyboard dies during failed suspend attempt Pierre Ossman
2005-11-04 5:11 ` Dmitry Torokhov [this message]
2005-11-04 15:07 ` Pierre Ossman
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=200511040011.18393.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=vojtech@ucw.cz \
/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