From: Fionn Behrens <fionn-ZPjJJ+sDHmfddJNmlsFzeA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: Acer Notebook: acpi IRQ stuck after S3
Date: Thu, 13 Jan 2005 10:31:02 +0100 [thread overview]
Message-ID: <1105608662.14488.106.camel@laptop> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575FB1EF6-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu 13.01.2005, 09:09 +0800 Li, Shaohua wrote:
> Hi,
> >log and backtrace:
> >
> >12:49:00 samt kernel: irq 9: nobody cared!
> >12:49:00 samt kernel: Disabling IRQ #9
> >
> >As you can see, IRQ 9 gets stuck here and consequently, the next ACPI
> >event (e.g. lid button) causes a system freeze.
> Did any device share IRQ 9 with ACPI? If yes, please try unload the
> driver.
No, according to /proc/interrupts, IRQ 9 is being used by acpi
exclusively.
any other ideas?
br,
Fionn
--
Software patents - not allowed in Europe | See whats going on:
Archiving Email - patented in Europe | http://freepatents.org/
E-Shopping Baskets - patented in Europe | Become active easily:
Cross-compiling - patented in Europe | http://aktiv.ffii.org/eubsa/en
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-13 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 1:09 Acer Notebook: acpi IRQ stuck after S3 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575FB1EF6-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-01-13 9:31 ` Fionn Behrens [this message]
2005-01-13 9:32 ` Fionn Behrens
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 11:08 Fionn Behrens
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=1105608662.14488.106.camel@laptop \
--to=fionn-zpjjj+sdhmfddjnmlsfzea@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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