From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756515AbYIIO1L (ORCPT ); Tue, 9 Sep 2008 10:27:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753352AbYIIO05 (ORCPT ); Tue, 9 Sep 2008 10:26:57 -0400 Received: from emita2.mittwald.de ([85.199.129.253]:56968 "EHLO emita2.mittwald.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752480AbYIIO05 (ORCPT ); Tue, 9 Sep 2008 10:26:57 -0400 X-Greylist: delayed 1283 seconds by postgrey-1.27 at vger.kernel.org; Tue, 09 Sep 2008 10:26:56 EDT From: Holger Schurig To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: OOPS: getting an ACPI interrupt while in an ACPI interrupt hangs my box Date: Tue, 9 Sep 2008 16:05:07 +0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809091605.07734.hs4233@mail.mn-solutions.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I just got this OOPS: irq 9: nobody cared (try booting with the "irqpoll" option) Pid: 0, comm: swapper Tainted: P 2.6.26.3 #3 [] __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_create_operands+0x1c/0xf9 [] __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/0x1d9 [] 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 138s! [syslogd:1952] If I read that OOPS right, then I got an interrupt ("common_interrupt"), which made the kernel run the ACPI function "acpi_ds_create_operands" and while this executed, I've got another interupt, which killed my for for 138 seconds ... Shouldn't there some sort of protection about this or is the DSDT of my device just bogus? Kernel 2.6.26.3 CPU: "Geode(TM) Integrated Processor by AMD PCS" How to reproduce: press ACPI buttons repeatedly ACPI related kernel-commandline entries: "pci=noacpi acpi_serialize". The first is vital (no boot without), the second one is an experiment, I got OOPSes without that, too.