From: Matthew Garrett <mjg59@srcf.ucam.org>
To: David Eriksson <david@2good.nu>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] No APIC interrupts after ACPI suspend
Date: Sun, 27 Jun 2004 17:27:47 +0100 [thread overview]
Message-ID: <1088353667.5113.1.camel@tyrosine> (raw)
In-Reply-To: <1088268145.14987.248.camel@zion.2good.net>
On Sat, 2004-06-26 at 18:42 +0200, David Eriksson wrote:
> Maybe you've found this bug?
>
> http://bugme.osdl.org/show_bug.cgi?id=2643
Yeah, that one was biting me, but it's not the one causing this bug.
cat /proc/interrupts shows that the ACPI interrupt is correctly set to
level triggered, but the ioapic isn't set up correctly so no interrupts
make it through. The same seems to be true for all other level-triggered
interrupts.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2004-06-27 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 10:48 No APIC interrupts after ACPI suspend Matthew Garrett
2004-06-26 0:05 ` Hamie
2004-06-26 16:42 ` [ACPI] " David Eriksson
2004-06-26 18:03 ` Hamie
[not found] ` <40DDBA7A.6010404-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.org>
2004-06-27 17:57 ` Hamie
[not found] ` <40DF0A98.9040604-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.org>
2004-06-27 18:49 ` Herman Sheremetyev
[not found] ` <1088362159.2163.38.camel-l85cmlzfk8I@public.gmane.org>
2004-06-29 21:19 ` Pavel Machek
2004-06-27 18:52 ` Alexander Gran
[not found] ` <200406272052.43326-qgpBcDF1kIxsXm07kNcISIFwBlHcXKVlHZ5vskTnxNA@public.gmane.org>
2004-06-27 19:16 ` Hamie
[not found] ` <40DF1D22.2010406-CM5YN7r2dWBr4tq51QLIbdBPR1lH4CV8@public.gmane.org>
2004-06-27 20:27 ` Hamie
2004-06-27 22:06 ` [ACPI] " Karol Kozimor
2004-06-27 19:22 ` Alexander Gran
2004-06-27 16:27 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-28 1:35 [ACPI] " Li, Shaohua
2004-06-28 6:20 Li, Shaohua
2004-06-28 8:48 ` Hamie
2004-06-28 9:18 ` [ACPI] " Luca Capello
2004-06-28 20:50 ` Hamie
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=1088353667.5113.1.camel@tyrosine \
--to=mjg59@srcf.ucam.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=david@2good.nu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox