* ACPI locks my box for minutes
@ 2008-09-04 11:00 Holger Schurig
2008-09-04 21:36 ` ACPI (atlas_btns) " Len Brown
0 siblings, 1 reply; 5+ messages in thread
From: Holger Schurig @ 2008-09-04 11:00 UTC (permalink / raw)
To: linux-acpi
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?
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: ACPI (atlas_btns) locks my box for minutes
2008-09-04 11:00 ACPI locks my box for minutes Holger Schurig
@ 2008-09-04 21:36 ` Len Brown
2008-09-05 6:31 ` Holger Schurig
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Len Brown @ 2008-09-04 21:36 UTC (permalink / raw)
To: Holger Schurig; +Cc: linux-acpi, Jaya Kumar, Dmitry Torokhov
On Thu, 4 Sep 2008, Holger Schurig wrote:
> 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:
Does the hang and interrupt storm only happen
upon pressing the button?
(ie. it does not happen if you do not press the button,
and it does not happen if atlas_btns is not loaded)
thanks,
-Len
> ##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?
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: ACPI (atlas_btns) locks my box for minutes
2008-09-04 21:36 ` ACPI (atlas_btns) " Len Brown
@ 2008-09-05 6:31 ` Holger Schurig
2008-09-05 7:34 ` Holger Schurig
2008-09-05 7:53 ` Holger Schurig
2 siblings, 0 replies; 5+ messages in thread
From: Holger Schurig @ 2008-09-05 6:31 UTC (permalink / raw)
To: Len Brown; +Cc: linux-acpi, Jaya Kumar, Dmitry Torokhov
On Thursday 04 September 2008 23:36:14 Len Brown wrote:
> Does the hang and interrupt storm only happen
> upon pressing the button?
> (ie. it does not happen if you do not press the button,
> and it does not happen if atlas_btns is not loaded)
Yes, it is related to pressing the buttons. I suspect that it
migth have something with the frequency of the pressings, e.g.
when I do it very fast. Or maybe the connectors of the button to
bounce (not sure if this is the right english word for
german "prellen").
If I don't press buttons, the box doesn't lock up.
I need to find out if the existence of atlas_btns makes a
difference. My guess is that it shouldn't make any difference,
the atlas_btns driver doesn't do anything with the interrupt 9.
It's the ACPI subsystem that handles this interrupt, atlas_btns
just "subscribes" into it and filters out some events ...
/me going to find out
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ACPI (atlas_btns) locks my box for minutes
2008-09-04 21:36 ` ACPI (atlas_btns) " Len Brown
2008-09-05 6:31 ` Holger Schurig
@ 2008-09-05 7:34 ` Holger Schurig
2008-09-05 7:53 ` Holger Schurig
2 siblings, 0 replies; 5+ messages in thread
From: Holger Schurig @ 2008-09-05 7:34 UTC (permalink / raw)
To: Len Brown; +Cc: linux-acpi, Jaya Kumar, Dmitry Torokhov
> and it does not happen if atlas_btns is not loaded)
Ok, the condition for the following e-mail is that atlas_btns.ko
hasn't been loaded.
The normal operation now is that I get for every key-press:
ACPI Error (evregion-0316): No handler for Region [ASI2]
(de012190) [UserDefinedRegion] [20080321]
ACPI Error (exfldio-0290): Region UserDefinedRegion(81) has no
handler [20080321]
ACPI Error (psparse-0530): Method parse/execution failed [\BNSV]
(Node de011b58), AE_NOT_EXIST
ACPI Error (psparse-0530): Method parse/execution failed
[\_GPE._E15] (Node de011d80), AE_NOT_EXIST
ACPI Exception (evgpe-0573): AE_NOT_EXIST, while evaluating GPE
method [_E15] [20080321]
And for every key-release:
ACPI Error (evregion-0316): No handler for Region [ASI2]
(de012190) [UserDefinedRegion] [20080321]
ACPI Error (exfldio-0290): Region UserDefinedRegion(81) has no
handler [20080321]
ACPI Error (psparse-0530): Method parse/execution failed [\BNSV]
(Node de011b58), AE_NOT_EXIST
ACPI Error (psparse-0530): Method parse/execution failed
[\_GPE._E15] (Node de011d80), AE_NOT_EXIST
ACPI Exception (evgpe-0573): AE_NOT_EXIST, while evaluating GPE
method [_E15] [20080321]
Second observation: then I press the ACPI buttons quickly, I can
also trigger a lock-down of the system. It takes some presses,
here I needed about 50 or 60 presses.
Now I got the system in a state where it virtually it doesn't
recover itself. Every 60 seconds or so I get some kernel output
lines. But I cannot SSH into it to get them, so I scribbled some
stuff from the screen.
The most common output that I get is similar to this (I ommitted
registers and hex values):
BUG: soft lockup - CPU#0 stuck for 61s! [klogd:1953]
Modules linked in: wlan_wep wlan_scan_sta ath_rate_sample ath_pci
wlan ath_hal(P)
Pid: 1953, comm: klogd Tained: P (2.6.26.3 #15)
EIP: 0060:[<c01cc6f5>] EFLAGS: 00000286 CPU: 0
EIP is at acpi_os_release_lock+0x2/0x3
... lots of registers
? acpi_hw_register-read
? acpi_ev_sci_xrupt_handler
? acpi_irq
? handle_IRQ_event
? handle_level_irq
? do_IRQ
? common_interrupt
? __do_softirq
? do_softirq
? irq_exit
? do_IRQ
? common_interrupt
? pci_read_bridge_bases
====================================
Sometimes the top of the backtrace is this:
? acpi_ev_gpe_detect
? acpi_ev_sci_xrupt_handler
? acpi_irq
? handle_IRQ_event
? handle_level_irq
? do_IRQ
? common_interrupt
? __do_softirq
? do_softirq
? irq_exit
? do_IRQ
? common_interrupt
? pci_read_bridge_bases
====================================
Sometimes the EIP as well the the backtrace is different:
EIP is at acpi_os_read_port+0x27/0x41
....
? acpi_hw_register_read
? acpi_ev_fixed_event_detect
? acpi_ev_sci_xrupt
? acpi_irq
? handle_IRQ_event
? handle_level_irq
? do_IRQ
? common_interrupt
? __do_softirq
? do_softirq
? irq_exit
? do_IRQ
? common_interrupt
? pci_read_bridge_bases
====================================
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: ACPI (atlas_btns) locks my box for minutes
2008-09-04 21:36 ` ACPI (atlas_btns) " Len Brown
2008-09-05 6:31 ` Holger Schurig
2008-09-05 7:34 ` Holger Schurig
@ 2008-09-05 7:53 ` Holger Schurig
2 siblings, 0 replies; 5+ messages in thread
From: Holger Schurig @ 2008-09-05 7:53 UTC (permalink / raw)
To: Len Brown; +Cc: linux-acpi, Jaya Kumar, Dmitry Torokhov
And one more dmesg output. This time the device recovers, so I
here is the real-output, nothing scribbled down. I have no clue why all the traces look soooo different. Maybe we deal with more
than just one problem ...
ACPI Error (psparse-0530): Method parse/execution failed [\_GPE._E15] (Node de011d80), AE_NOT_EXIST
ACPI Exception (evgpe-0573): AE_NOT_EXIST, while evaluating GPE method [_E15] [20080321]
Execute Method: [\_GPE._E15] (Node de011d80)
Execute Method: [\_GPE._E15] (Node de011d80)
Execute Method: [\_GPE._E15] (Node de011d80)
Execute Method: [\_GPE._E15] (Node de011d80)
ACPI Error (evregion-0316): No handler for Region [ASI2] (de012190) [UserDefinedRegion] [20080321]
ACPI Error (exfldio-0290): Region UserDefinedRegion(81) has no handler [20080321]
ACPI Error (psparse-0530): Method parse/execution failed [\BNSV] (Node de011b58), AE_NOT_EXIST
ACPI Error (psparse-0530): Method parse/execution failed [\_GPE._E15] (Node de011d80), AE_NOT_EXIST
ACPI Exception (evgpe-0573): AE_NOT_EXIST, while evaluating GPE method [_E15] [20080321]
Execute Method: [\_GPE._E15] (Node de011d80)
ACPI Error (evregion-0316): No handler for Region [ASI2] (de012190) [UserDefinedRegion] [20080321]
ACPI Error (exfldio-0290): Region UserDefinedRegion(81) has no handler [20080321]
ACPI Error (psparse-0530): Method parse/execution failed [\BNSV] (Node de011b58), AE_NOT_EXIST
ACPI Error (psparse-0530): Method parse/execution failed [\_GPE._E15] (Node de011d80), AE_NOT_EXIST
ACPI Exception (evgpe-0573): AE_NOT_EXIST, while evaluating GPE method [_E15] [20080321]
irq 9: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Tainted: P 2.6.26.3 #16
[<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
[<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
[<c01f8458>] acpi_idle_enter_simple+0x16d/0x1d9
[<c0264bd2>] cpuidle_idle_call+0x49/0x77
[<c0264b89>] cpuidle_idle_call+0x0/0x77
[<c010176c>] cpu_idle+0x48/0x61
=======================
handlers:
[<c01cbc8c>] (acpi_irq+0x0/0x1c)
Disabling IRQ #9
Execute Method: [\_GPE._E15] (Node de011d80)
BUG: soft lockup - CPU#0 stuck for 140s! [kacpid:63]
Modules linked in: wlan_wep wlan_scan_sta ath_rate_sample ath_pci wlan ath_hal(P)
Pid: 63, comm: kacpid Tainted: P (2.6.26.3 #16)
EIP: 0060:[<c01162e0>] EFLAGS: 00000286 CPU: 0
EIP is at vprintk+0x24d/0x257
EAX: c038c818 EBX: 00000000 ECX: 00000046 EDX: c038c814
ESI: c034e40a EDI: c03eb361 EBP: 00000001 ESP: de0edeb4
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b7f960cc CR3: 1e3ed000 CR4: 00000090
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
[<c0111129>] ? wakeup_preempt_entity+0x31/0x49
[<c0113c1e>] ? check_preempt_wakeup+0x7f/0x93
[<c01ebf1e>] ? acpi_ut_status_exit+0x48/0x56
[<c01162fe>] ? printk+0x14/0x18
[<c01162fe>] ? printk+0x14/0x18
[<c01cc7fa>] ? acpi_os_vprintf+0x1d/0x20
[<c01cc810>] ? acpi_os_printf+0x13/0x15
[<c01e4f7e>] ? acpi_ns_dump_pathname+0x66/0x88
[<c01e3924>] ? acpi_ns_evaluate+0x124/0x20c
[<c01d6821>] ? acpi_ev_asynch_execute_gpe_method+0xee/0x144
[<c01cc2e5>] ? acpi_os_execute_deferred+0x0/0x25
[<c01cc302>] ? acpi_os_execute_deferred+0x1d/0x25
[<c011fd8b>] ? run_workqueue+0x63/0xca
[<c01202a3>] ? worker_thread+0x0/0x7e
[<c0120317>] ? worker_thread+0x74/0x7e
[<c0122284>] ? autoremove_wake_function+0x0/0x2d
[<c0122133>] ? kthread+0x36/0x5b
[<c01220fd>] ? kthread+0x0/0x5b
[<c010337f>] ? kernel_thread_helper+0x7/0x10
=======================
... and here the system was responsible again. That, is, except
for ACPI. Another button press didn't do anything, not even
locking up the system again :-/ But I could SSH into the device,
hurray :-)
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-09-05 7:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-04 11:00 ACPI locks my box for minutes Holger Schurig
2008-09-04 21:36 ` ACPI (atlas_btns) " Len Brown
2008-09-05 6:31 ` Holger Schurig
2008-09-05 7:34 ` Holger Schurig
2008-09-05 7:53 ` Holger Schurig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox