On 7/26/07, Torsten Kaiser <[EMAIL PROTECTED]> wrote: > DISCONTIGMEM+SLUB: > [ 39.833272] ..MP-BIOS bug: 8254 timer not connected to IO-APIC > [ 40.016659] Kernel panic - not syncing: IO-APIC + timer doesn't > work! Try using the 'noapic' kernel parameter > DISCONTIGMEM+SLAB: > Boots until it can't find / because I didn't append the correct initrd > It also hit the MP-BIOS bug, but was not bothered by it: > [ 36.696965] ..MP-BIOS bug: 8254 timer not connected to IO-APIC > [ 36.880537] Using local APIC timer interrupts. > [ 36.932215] result 12500283 > [ 36.940581] Detected 12.500 MHz APIC timer. > > So I think, I will postpone SPARSEMEM until -mm2, as there are seem to > be some problems in that area (Re: 2.6.23-rc1-mm1 sparsemem_vmemamp > fix) > > But maybee I will get SLUB to work. ;)
SLUB works, if I reboot (Alt+SysRq+B) from a 2.6.22-rc6-mm1 kernel. Otherwise it will panic with IO-APIC + timer not working. Differences in dmesg 2.6.22-rc6-mm1 has: [ 0.000000] Nvidia board detected. Ignoring ACPI timer override. [ 0.000000] If you got timer trouble try acpi_use_timer_override and [ 0.000000] ACPI: BIOS IRQ0 pin2 override ignored. and [ 0.000000] TSC calibrated against PM_TIMER 23-rc1-mm1 has: [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. and [ 37.340319] ..MP-BIOS bug: 8254 timer not connected to IO-APIC I did not need to use acpi_use_timer_override with the older kernel. Do you need more info about my board/ BIOS/ ACPI tables? After the warm-boot trick 2.6.23-rc1-mm1 seems stable right now... Torsten - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
