public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Dmitry Torokhov <dtor_core@ameritech.net>
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, 04 Nov 2005 16:07:43 +0100	[thread overview]
Message-ID: <436B793F.3040808@drzeus.cx> (raw)
In-Reply-To: <200511040011.18393.dtor_core@ameritech.net>

Dmitry Torokhov wrote:
> 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?
>
>   

Haven't the slightest. There is nothing to control the backlight in 
/proc/acpi at least (all brightness say '<not supported>').

>> 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.
>
>   

I've been suspending the machine all day now and I have yet to get it to 
fail. There must have been something different yesterday but I can't 
figure out what... I'll do some more testing during the weekend and see 
if I can provoke it again. Otherwise I suppose we can write it off as 
something temporary.

Rgds
Pierre


      reply	other threads:[~2005-11-04 15:07 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
2005-11-04 15:07   ` Pierre Ossman [this message]

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=436B793F.3040808@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=dtor_core@ameritech.net \
    --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