> > The following command prints the stack backtrace: > > > > ::stack > > I get: > > pcplusmp`apic_error_intr() > displatch_hilevel+0x1f(f1, 0) > do_interrupt+0xbe(ffffff00074d1ee0, 0) > _interrupt+0xba() > dispatch_hilevel+0x1a(d1, 0) > switch_sp_and_call+0x13() > do_interrupt+0xd9(fffffffffbc4d870, 2d81fb0) > _interrupt+0xba() > pcplusmp`apic_cpu_start+0x197(1, ffffff01c0a66000) > mach_cpu_start+0x22(ffffff01c0909080, ffffff01c0a66000) > start_cpu+0x59(1) > start_other_cpus+0x1a5(0) > main+0x286() > _locore_start+0x92()
Ok. Seems the APIC interrupt controller signals an error interrupt as soon as interrupts are enabled after initializing the APIC... You should probably file a new bug at http://bugs.opensolaris.org/ as this seems to be a new problem. A possible workaround might be to disable the pcplusmp kernel module, and run the system in uniprocessor mode. Instructions to disable pcplusmp can be found in the workaround section for bug 1253669 "pcplusmp: need to support second I/O APIC or I/O APIC with more than 16 entries" http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=1253669 -- This message posted from opensolaris.org
