On Mon, Aug 21, 2006 at 07:22:09PM -0400, Len Brown wrote: > Please dump the stack so we can find the secretive caller to > acpi_format_exception(). I get three of these when booting and the output from dump_stack is the same for each. I've observed no problems as a result of these reported failures. Here is the output from the first call of dump_stack: Aug 22 19:39:33 tlg kernel: ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA [20060707] Aug 22 19:39:33 tlg kernel: Aug 22 19:39:33 tlg kernel: Call Trace: Aug 22 19:39:33 tlg kernel: [<ffffffff80267cb8>] dump_trace+0xba/0x39e Aug 22 19:39:33 tlg kernel: [<ffffffff80267fd8>] show_trace+0x3c/0x52 Aug 22 19:39:33 tlg kernel: [<ffffffff80268003>] dump_stack+0x15/0x17 Aug 22 19:39:33 tlg kernel: [<ffffffff803c8d10>] acpi_format_exception+0xc0/0xcb Aug 22 19:39:33 tlg kernel: [<ffffffff803c54e5>] acpi_ut_status_exit+0x38/0x73 Aug 22 19:39:33 tlg kernel: [<ffffffff803c11a0>] acpi_walk_resources+0x12e/0x140 Aug 22 19:39:33 tlg kernel: [<ffffffff803d85e5>] acpi_motherboard_add+0x26/0x32 Aug 22 19:39:33 tlg kernel: [<ffffffff803d73d7>] acpi_bus_driver_init+0x3a/0x98 Aug 22 19:39:33 tlg kernel: [<ffffffff803d796c>] acpi_bus_register_driver+0xbd/0x144 Aug 22 19:39:33 tlg kernel: [<ffffffff807dcbd4>] acpi_motherboard_init+0x10/0x130 Aug 22 19:39:33 tlg kernel: [<ffffffff802668f1>] init+0x13b/0x313 Aug 22 19:39:33 tlg kernel: [<ffffffff8025dba8>] child_rip+0xa/0x12 Aug 22 19:39:33 tlg kernel: DWARF2 unwinder stuck at child_rip+0xa/0x12 Aug 22 19:39:33 tlg kernel: Leftover inexact backtrace: Aug 22 19:39:33 tlg kernel: [<ffffffff802632ae>] _spin_unlock_irq+0x2b/0x53 Aug 22 19:39:33 tlg kernel: [<ffffffff8025d300>] restore_args+0x0/0x30 Aug 22 19:39:33 tlg kernel: [<ffffffff80215fed>] release_console_sem+0x4d/0x238 Aug 22 19:39:33 tlg kernel: [<ffffffff802667b6>] init+0x0/0x313 Aug 22 19:39:33 tlg kernel: [<ffffffff8025db9e>] child_rip+0x0/0x12 Cheers, Grant - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
