All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Capello <luca@pca.it>
To: acpi-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] No APIC interrupts after ACPI suspend
Date: Mon, 28 Jun 2004 11:18:26 +0200	[thread overview]
Message-ID: <40DFE262.3040107@pca.it> (raw)
In-Reply-To: <40DFDB5A.7070301@travellingkiwi.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

on 06/28/04 10:48, Hamie wrote:
> Li, Shaohua wrote:
>> I attached a new patch to handler all level triggered IRQs after resume
>> for 8259 in http://bugme.osdl.org/show_bug.cgi?id=2643. Please try and
>> attach your test result on it.
> Uh.... That might work.... Except that after applying the patch &
> restarting. Then suspend-resume I get another small problem... My
> thinkpad (r50p) uses the power button to wake up from suspend... The
> system wakes, but with this latest patch, acpid then kicks in & says
> 'Ohh! I saw him press the power button' and promptly shuts down...
<cut>
> Sleeps, wakes & a shutdown... Should acpid do that? (i.e. shouldn't it
> eat the power button event that woke it up as a wakeup? Should it even
> get that?) Or is it the previous patch for drivers/acpi/sleep/main.c
> resetting the IRQ9 to edge triggered that's killing me? (I'll try
> removing that now).
this is a known /bug/, I experienced the same on my ancient ASUS M3N. It
has nothing to do with 'acpid'. Please refer to this thread:
	http://marc.theaimsgroup.com/?l=acpi4linux&m=107291320113621&w=2

For the moment, you can use the workaround I proposed here
	http://marc.theaimsgroup.com/?l=acpi4linux&m=107333070225744&w=2

Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFA3+JiVAp7Xm10JmkRAoioAJ0Wm/HoUcW0CH2yePQvjB4YGJDs/gCdHd8S
NHmS97q0bfg8JOec6H7fFKs=
=J5E+
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-06-28  9:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28  6:20 No APIC interrupts after ACPI suspend Li, Shaohua
2004-06-28  6:20 ` [ACPI] " Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F032D566A-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-06-28  8:48   ` Hamie
2004-06-28  9:18     ` Luca Capello [this message]
2004-06-28 20:50 ` [ACPI] " Hamie
  -- strict thread matches above, loose matches on Subject: below --
2004-06-28  1:35 Li, Shaohua
2004-06-28  1:35 ` Li, Shaohua
2004-06-25 10:48 Matthew Garrett
2004-06-26 16:42 ` [ACPI] " David Eriksson
2004-06-26 18:03   ` Hamie
2004-06-27 17:57     ` Hamie
2004-06-27 18:52       ` Alexander Gran
2004-06-27 19:16         ` Hamie
2004-06-27 20:27           ` Hamie
2004-06-27 22:06           ` Karol Kozimor
2004-06-27 19:22         ` Alexander Gran
2004-06-27 16:27   ` Matthew Garrett

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=40DFE262.3040107@pca.it \
    --to=luca@pca.it \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.