public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-acpi@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compaq X1050 multiple suspend problems (ACPI, PS2)
Date: Tue, 14 Feb 2006 17:13:40 -0600	[thread overview]
Message-ID: <43F26424.8040708@shaw.ca> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F840AEE20B9@pdsmsx403>

No difference there either.. The contents of 
/proc/acpi/embedded_controller/C0EA/info both before and after suspend are:

gpe bit:                 0x1c
ports:                   0x66, 0x62
use global lock:         no

I'll open a Bugzilla report.

Yu, Luming wrote:
>> I have not seen any ACPI errors other than during suspend/resume.
>>
>> Tried ec_intr=0 option on the command line, same problem.
>>
>> ACPI_EC_DELAY=100 patch did not help either, same or at least similar 
>> problem. Output attached.
>>
> 
> Please try boot with lapic. I'm NOT sure if it is irq related resume
> issue.
> After resume, please try cat /proc/acpi/embedded_controller/*/info.
> Please test if it do the trick.
> 
> If still not, please file a bug in ACPI category on bugzilla.kernel.org.
> 
> 
> Thanks,
> Luming
> 

  reply	other threads:[~2006-02-14 23:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14  5:47 Compaq X1050 multiple suspend problems (ACPI, PS2) Yu, Luming
2006-02-14 23:13 ` Robert Hancock [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-14  3:19 Yu, Luming
2006-02-14  4:01 ` Robert Hancock
     [not found] <3ACA40606221794F80A5670F0AF15F840AE81145@pdsmsx403>
2006-02-14  2:56 ` Robert Hancock
2006-02-13  6:31 Yu, Luming
2006-02-13  5:26 Robert Hancock

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=43F26424.8040708@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@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