On Apr 1, 2007, at 2:39 PM, Manuel Bouyer wrote:
As it's reproductible, if it was a memory issue I think it would have already found it.It seems to be related to ioapics, so maybe a chipset issue. But I stillstrongly suspect a hardware issue, or maybe something that changed in BIOS. You may be able to get it running again by disabling both ACPI and ioapics at xen and NetBSD levels: kernel=xen.gz ... acpi=off noapic module=netbsd ... -c disable acpi disable ioapic quit
Just to be sure I understand correctly - a dual-core processor (such as the Pentium D in this computer) /should/ be using ACPI and ioapic while running as a dom0 in "normal" operation?
--david