Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750943AbWH0P1X (ORCPT ); Sun, 27 Aug 2006 11:27:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750907AbWH0P1X (ORCPT ); Sun, 27 Aug 2006 11:27:23 -0400 Received: from mxsf10.cluster1.charter.net ([209.225.28.210]:8347 "EHLO mxsf10.cluster1.charter.net") by vger.kernel.org with ESMTP id S1750743AbWH0P1W (ORCPT ); Sun, 27 Aug 2006 11:27:22 -0400 X-IronPort-AV: i="4.08,174,1154923200"; d="scan'208"; a="606876149:sNHT51019190" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17649.47572.627874.371564@stoffel.org> Date: Sun, 27 Aug 2006 11:27:16 -0400 From: "John Stoffel" To: Andrew Morton Cc: "Miles Lane" , LKML , linux-acpi@vger.kernel.org, "Brown, Len" Subject: Re: 2.6.18-rc4-mm3 -- ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [20060707] In-Reply-To: <20060827001437.ec4f7a7a.akpm@osdl.org> References: <20060827001437.ec4f7a7a.akpm@osdl.org> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3383 Lines: 77 >>>>> "Andrew" == Andrew Morton writes: Andrew> On Sat, 26 Aug 2006 23:56:09 -0700 Andrew> "Miles Lane" wrote: >> PCI: Using ACPI for IRQ routing >> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report >> ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [20060707] >> [dump_trace+100/418] dump_trace+0x64/0x1a2 >> [show_trace_log_lvl+18/37] show_trace_log_lvl+0x12/0x25 >> [show_trace+13/16] show_trace+0xd/0x10 >> [dump_stack+23/25] dump_stack+0x17/0x19 >> [acpi_format_exception+162/175] acpi_format_exception+0xa2/0xaf >> [acpi_ut_status_exit+43/88] acpi_ut_status_exit+0x2b/0x58 >> [acpi_walk_resources+269/281] acpi_walk_resources+0x10d/0x119 >> [acpi_motherboard_add+34/52] acpi_motherboard_add+0x22/0x34 >> [acpi_bus_driver_init+42/122] acpi_bus_driver_init+0x2a/0x7a >> [acpi_bus_register_driver+137/248] acpi_bus_register_driver+0x89/0xf8 >> [acpi_motherboard_init+23/249] acpi_motherboard_init+0x17/0xf9 >> [init+136/512] init+0x88/0x200 >> [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10 >> DWARF2 unwinder stuck at kernel_thread_helper+0x7/0x10 >> >> Leftover inexact backtrace: >> >> [show_trace_log_lvl+18/37] show_trace_log_lvl+0x12/0x25 >> [show_trace+13/16] show_trace+0xd/0x10 >> [dump_stack+23/25] dump_stack+0x17/0x19 >> [acpi_format_exception+162/175] acpi_format_exception+0xa2/0xaf >> [acpi_ut_status_exit+43/88] acpi_ut_status_exit+0x2b/0x58 >> [acpi_walk_resources+269/281] acpi_walk_resources+0x10d/0x119 >> [acpi_motherboard_add+34/52] acpi_motherboard_add+0x22/0x34 >> [acpi_bus_driver_init+42/122] acpi_bus_driver_init+0x2a/0x7a >> [acpi_bus_register_driver+137/248] acpi_bus_register_driver+0x89/0xf8 >> [acpi_motherboard_init+23/249] acpi_motherboard_init+0x17/0xf9 >> [init+136/512] init+0x88/0x200 >> [kernel_thread_helper+7/16] kernel_thread_helper+0x7/0x10 >> ======================= Andrew> cc's added. Thanks Andrew. I just tried doing this with 2.6.18-rc4-mm3 and it hung again. I also tried booting with irqpoll and pci=routeirq but it made no difference at all. I got the following with irqpoll: irq 17: nobody cared (try booting with the "irqpoll" option) [] __report_bad_irq+0x24/0x90 [] note_interrupt+0x218/0x250 [] handle_IRQ_event+0x33/0x70 [] handle_fasteoi_irq+0xca/0xe0 [] handle_fasteoi_irq+0x0/0xe0 [] do_IRQ+0x8d/0xf0 [] unknown_bootoption+0x0/0x270 [] common_interrupt+0x1a/0x20 [] default_idle+0x0/0x60 [] unknown_bootoption+0x0/0x270 [] default_idle+0x31/0x60 [] cpu_idle+0x6c/0x90 [] start_kernel+0x2f9/0x400 [] unknown_bootoption+0x0/0x270 ======================= handlers: [] (ata_interrupt+0x0/0x190) [] (usb_hcd_irq+0x0/0x60) Disabling IRQ #17 I'm going to try and upgrade the firmware on my RocketPort 133 from 1.21 to 1.22 to see if that makes a difference, but otherwise there's not alot I can do here. Any more information I can provide? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/