This is the last info I can provide.  I looked through some other bug
reports, and I decided to see what some combinations of boot options
could do:

* acpi_skip_timer_override: I didn't see any change.
* enable_8254_timer: I didn't see any change.
* disable_8254_timer: Kernel panic - not syncing: Attempted to kill init!
* noapic: The system was able to boot, and I didn't see the bug message.  I 
did, however, see "spurious 8259A interrupt: IRQ7." when I looked through the 
dmesg output.
* noapic nolapic: I saw all of the messages/changes that I saw when just 
'noapic' was set.
* acpi=off: I didn't see any of the ACPI information at boot, and the CPU 
frequency scaling module didn't load ("powernow-k8: MP systems not supported by 
PSB BIOS structure").  I didn't see any indication of the HPETs being used 
("time.c: Using PIT/TSC based timekeeping."), but I did see the line "testing 
NMI watchdog ... OK.".
* acpi=off noapic: I saw all of the messages/changes that I saw when just 
'acpi=off' and 'noapic' were set.  There were also some PCI errors ("PCI: IRQ 0 
for device 0000:83:00.0 doesn't match PIRQ mask - try pci=usepirqmask" and 
"PCI: No IRQ known for interrupt pin A of device 0000:83:00.0. Please try using 
pci=biosirq.").
* acpi=off noapic nolapic: I saw all of the messages/changes that I saw when 
just 'acpi=off' was set, and when 'acpi=off' and 'noapic' were set.

-- 
"8254 timer not connected to IO-APIC" after BIOS upgrade on Sun X4200 M2
https://bugs.launchpad.net/bugs/257157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to