From: Fionn Behrens <fionn-ZPjJJ+sDHmfddJNmlsFzeA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Acer Notebook: acpi IRQ stuck after S3
Date: Wed, 12 Jan 2005 12:08:50 +0100 [thread overview]
Message-ID: <1105528130.14488.68.camel@laptop> (raw)
log and backtrace:
12:49:00 samt kernel: PM: Preparing system for suspend
12:49:00 samt kernel: Stopping tasks:
=======================================|
12:49:00 samt kernel: PM: Entering state.
12:49:00 samt kernel: Back to C!
12:49:00 samt kernel: irq 9: nobody cared!
12:49:00 samt kernel: [<c010724a>] __report_bad_irq+0x2a/0x90
12:49:00 samt kernel: [<c0107340>] note_interrupt+0x70/0xb0
12:49:00 samt kernel: [<c01075f0>] do_IRQ+0x120/0x130
12:49:00 samt kernel: [<c01053c8>] common_interrupt+0x18/0x20
12:49:00 samt kernel: [<c013007b>] unqueue_me+0x3b/0xb0
12:49:00 samt kernel: [<c012046e>] __do_softirq+0x2e/0x90
12:49:00 samt kernel: [<c01204f7>] do_softirq+0x27/0x30
12:49:00 samt kernel: [<c01075ca>] do_IRQ+0xfa/0x130
12:49:00 samt kernel: [<c01053c8>] common_interrupt+0x18/0x20
12:49:00 samt kernel: [<c0134ca8>] suspend_enter+0x38/0x50
12:49:00 samt kernel: [<c0134d84>] enter_state+0x64/0xb0
12:49:00 samt kernel: [<c02020c9>] acpi_suspend+0x3e/0x4d
12:49:00 samt kernel: [<c0202478>] acpi_system_write_sleep+0x60/0x8b
12:49:00 samt kernel: [<c020248d>] acpi_system_write_sleep+0x75/0x8b
12:49:00 samt kernel: [<c0155a68>] vfs_write+0xb8/0x130
12:49:00 samt kernel: [<c0154f99>] filp_close+0x59/0x90
12:49:00 samt cardmgr[1467]: executing: './network suspend eth1'
12:49:00 samt kernel: [<c0155bb1>] sys_write+0x51/0x80
12:49:00 samt kernel: [<c010525b>] syscall_call+0x7/0xb
12:49:00 samt kernel: handlers:
12:49:00 samt kernel: [<c01eb827>] (acpi_irq+0x0/0x16)
12:49:00 samt kernel: Disabling IRQ #9
12:49:00 samt kernel: PM: Finishing up.
As you can see, IRQ 9 gets stuck here and consequently, the next ACPI
event (e.g. lid button) causes a system freeze. Hoping that the problem
might relate to some uninitialized memory after resume I raised the
limit for unhandled IRQs in spurious.c (irq.c before 2.6.10). But that
does not help.
I'd really like to debug this but I need help from an expert where to
look at to find out what happens to this acpi IRQ.
Thanks,
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 reply other threads:[~2005-01-12 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 11:08 Fionn Behrens [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2005-01-13 9:32 ` 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=1105528130.14488.68.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