From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-acpi@vger.kernel.org
Subject: ACPI locks my box for minutes
Date: Thu, 4 Sep 2008 13:00:20 +0200 [thread overview]
Message-ID: <200809041300.20141.hs4233@mail.mn-solutions.de> (raw)
Hi people !
On 2.6.26.3 I'm using ACPI and the Atlas driver
(drivers/input/misc/atlas_btns.c), which uses the ASIM0000 acpi
device.
Most of the time this works great. That is, I can press 20
or 50 times the button and it always works, I always get a
scan-code report via the input subsystem.
However, occossianelly my box hangs. It's a hard lock, e.g.
the blinking cursor in X won't work, the keyboard won't work. The
box is just completely locked up for a period of time. Eventually
it recovers. When I now look at "dmesg", I see this:
##HS acpi_atlas_button_handler()
##HS acpi_atlas_button_handler()
##HS acpi_atlas_button_handler()
##HS acpi_atlas_button_handler()
irq 9: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P 2.6.26.3 #12
[<c012f063>] __report_bad_irq+0x24/0x69
[<c012f06a>] __report_bad_irq+0x2b/0x69
[<c012f257>] note_interrupt+0x1af/0x1e4
[<c01cbc97>] acpi_irq+0xb/0x1c
[<c012e983>] handle_IRQ_event+0x1a/0x3f
[<c012f917>] handle_level_irq+0x63/0x84
[<c01046d0>] do_IRQ+0x4b/0x60
[<c010320f>] common_interrupt+0x23/0x28
[<c01d007b>] acpi_ds_init_aml_walk+0xb2/0xfe
[<c0118f03>] __do_softirq+0x2c/0x75
[<c0118f6e>] do_softirq+0x22/0x26
[<c01191ea>] irq_exit+0x25/0x53
[<c01046d5>] do_IRQ+0x50/0x60
[<c010320f>] common_interrupt+0x23/0x28
[<c01e90a7>] acpi_idle_enter_simple+0x16d/0x1da
[<c02553f6>] cpuidle_idle_call+0x49/0x77
[<c02553ad>] cpuidle_idle_call+0x0/0x77
[<c010176c>] cpu_idle+0x48/0x61
=======================
handlers:
[<c01cbc8c>] (acpi_irq+0x0/0x1c)
Disabling IRQ #9
BUG: soft lockup - CPU#0 stuck for 136s! [events/0:5]
Modules linked in: wlan_wep wlan_scan_sta ath_rate_sample ath_pci wlan ath_hal(P)
IRQ 9 is, of course, the ACPI interrupt. This is the state after
the lock-up-and-recoverage:
# cat /proc/interrupts
CPU0
0: 51339 XT-PIC-XT timer
2: 0 XT-PIC-XT cascade
4: 606 XT-PIC-XT serial
5: 2012 XT-PIC-XT serial
7: 3 XT-PIC-XT
9: 200000 XT-PIC-XT acpi
10: 0 XT-PIC-XT yenta, yenta
11: 6252 XT-PIC-XT ehci_hcd:usb1, ohci_hcd:usb2, CS5535 Audio, wifi0
14: 88924 XT-PIC-XT ide0
15: 0 XT-PIC-XT ide1
NMI: 0 Non-maskable interrupts
LOC: 0 Local timer interrupts
TRM: 0 Thermal event interrupts
SPU: 0 Spurious interrupts
ERR: 1
MIS: 0
Note the extraordinary high interrupt number of IRQ 9 ! This
does not happen before this error triggers:
# grep 9: /proc/interrupts
9: 2 XT-PIC-XT acpi
---> now I press one ACPI button <---
# grep 9: /proc/interrupts
9: 4 XT-PIC-XT acpi
Any hint about resolving this issue?
next reply other threads:[~2008-09-04 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 11:00 Holger Schurig [this message]
2008-09-04 21:36 ` ACPI (atlas_btns) locks my box for minutes Len Brown
2008-09-05 6:31 ` Holger Schurig
2008-09-05 7:34 ` Holger Schurig
2008-09-05 7:53 ` Holger Schurig
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=200809041300.20141.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=linux-acpi@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