From mboxrd@z Thu Jan 1 00:00:00 1970 From: Holger Schurig Subject: ACPI locks my box for minutes Date: Thu, 4 Sep 2008 13:00:20 +0200 Message-ID: <200809041300.20141.hs4233@mail.mn-solutions.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from emita2.mittwald.de ([85.199.129.253]:46758 "EHLO emita2.mittwald.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752227AbYIDLXg (ORCPT ); Thu, 4 Sep 2008 07:23:36 -0400 Received: from mx51.mymxserver.com (unknown [172.16.51.3]) by emita2.mittwald.de (Postfix) with ESMTP id CB0AF1F8508 for ; Thu, 4 Sep 2008 13:00:42 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by localhost.mx51.mymxserver.com (Postfix) with ESMTP id 281E94B00F for ; Thu, 4 Sep 2008 13:00:36 +0200 (CEST) Received: from mx51.mymxserver.com ([127.0.0.1]) by localhost (mx51.mymxserver.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQ-2GQADYAI7 for ; Thu, 4 Sep 2008 13:00:36 +0200 (CEST) Received: from lin01.mn-solutions.de (pD95FB352.dip0.t-ipconnect.de [217.95.179.82]) by mx51.mymxserver.com (Postfix) with ESMTP id 953954B016 for ; Thu, 4 Sep 2008 13:00:35 +0200 (CEST) Received: from mnz66.mn-solutions.de (mnz66.mn-solutions.de [192.168.233.66]) by lin01.mn-solutions.de (Postfix) with ESMTP id 1EA231E00DD for ; Thu, 4 Sep 2008 13:00:29 +0200 (CEST) Content-Disposition: inline Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: linux-acpi@vger.kernel.org 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 [] __report_bad_irq+0x24/0x69 [] __report_bad_irq+0x2b/0x69 [] note_interrupt+0x1af/0x1e4 [] acpi_irq+0xb/0x1c [] handle_IRQ_event+0x1a/0x3f [] handle_level_irq+0x63/0x84 [] do_IRQ+0x4b/0x60 [] common_interrupt+0x23/0x28 [] acpi_ds_init_aml_walk+0xb2/0xfe [] __do_softirq+0x2c/0x75 [] do_softirq+0x22/0x26 [] irq_exit+0x25/0x53 [] do_IRQ+0x50/0x60 [] common_interrupt+0x23/0x28 [] acpi_idle_enter_simple+0x16d/0x1da [] cpuidle_idle_call+0x49/0x77 [] cpuidle_idle_call+0x0/0x77 [] cpu_idle+0x48/0x61 ======================= handlers: [] (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?