public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI Exception breaking Thinkpad T43 on 2.6.22-rc
Date: Wed, 13 Jun 2007 23:40:17 +0200	[thread overview]
Message-ID: <46706441.7080300@ens-lyon.org> (raw)
In-Reply-To: <46706080.1090607@ens-lyon.org>

Brice Goglin wrote:
> Henrique de Moraes Holschuh wrote:
>   
>>> CONFIG_BLINK=m
>>>     
>>>       
>> Set the above to "n" and recompile (it is in Drivers|Misc|Keyboard blink
>> driver".  Does it fix things?
>>   
>>     
>
>
> Ok, I'll try that and report back. However, since blink was built as a
> module and not loaded, could it really break something?
>   

I just loaded it explicitly for fun and got the problem within 3 minutes:

[16659.584000] Enabling keyboard blinking
[16840.500000] ACPI Exception (evregion-0420): AE_TIME, Returned by
Handler for [EmbeddedControl] [20070126]
[16840.500000] ACPI Error (psparse-0537): Method parse/execution failed
[\_SB_.PCI0.LPC_.EC__.AC__._PSR] (Node dfeda9f0), AE_TIME
[16840.500000] ACPI Exception (ac-0095): AE_TIME, Error reading AC
Adapter state [20070126]

Now that blink is not built at all in my kernel, I'll report back if the
problem occurs again. Let me know if you need me to test/debug anything.

thanks,
Brice


  reply	other threads:[~2007-06-13 21:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 20:38 ACPI Exception breaking Thinkpad T43 on 2.6.22-rc Brice Goglin
2007-06-13 21:18 ` Henrique de Moraes Holschuh
2007-06-13 21:24   ` Brice Goglin
2007-06-13 21:40     ` Brice Goglin [this message]
2007-06-14  0:33     ` Henrique de Moraes Holschuh
2007-06-14  6:04       ` Brice Goglin
2007-06-24  9:49       ` Brice Goglin

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=46706441.7080300@ens-lyon.org \
    --to=brice.goglin@ens-lyon.org \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@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