Messages in this thread | | | Subject | oops ACPI in Linux-2.6.6-bk1 | From | Pat LaVarre <> | Date | 12 May 2004 09:28:53 -0600 |
| |
Linux-2.6.6-bk1 boot chokes here. Transcribed by hand, with conscious omissions shown as ... ellipses:
// Trial 5:
schedule+0x608/0x60d [<c01eef72>] acpi_ev_save_method_info+0x44/0x75 [<c01e94a2>] acpi_os_allocate+0xe/0x11 [<c01f7f59>] acpi_ns_get_next_node+x15/0x4e ... preempt_schedule... ... setup_irq... ... acpi_irq... ... acpi_irq... ... request_irq... ... acpi_os_install_interrupt_handler... ... acpi_irq... ... acpi_irq... ... acpi_ev_install_sci_handler... ... acpi_ev_sci_xrupt_handler... ... acpi_ev_handler_initialize... ... acpi_enable_subsystem... ... acpi_bus_init... ... acpi_init... ... do_initcalls... ... init_workqueues... [<c0100363>] init+0x62/0x193 [<c0100301>] init+0x0/0x193 [<c01042a9>] kernel_thread_helper+0x5/0xb
// Trial 4:
ACPI: Subsystem revision 20040326 Unable to handle kernel NULL pointer dereferencec01e1194 *pde = 00000000
// Trial 3:
ACPI: Subsystem revision 20040326 Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing
// Trial 2:
ACPI: Subsystem revision 20040326 Unable <o ha1dleUn kernel NULL pointer dereferenceer dereferenceOoops: 49a0 [#1]
// Trial 1:
ACPI: Subsystem revision 20040326 Unable to handle kernel NULL pointer dereference at virtual address 00000038 printing eip: c0118857 *pde = 00000000 Unable to handle kernel NULL pointer dereference at virtual address 00000034 printing eip: C0107137 *pde = 00000000
// Often before the ACPI line I see:
... NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1 PCI: Using configuration type 1 mtrr: v2.0 (20020519)
// This is my first experience of any -bk release, // risked for the sake of the new code of drivers/scsi/libata*
Enjoy, Pat LaVarre
- 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/
| |