Sounds like it may be hanging in interrupt establishment. Can you mail
me the dmesg with MPVERBOSE enabled (for as far as it gets, anyway)?
LOCKDEBUG can be switched off again, obviously there's no locking issue.

Also, what did esiop print out that it was interrupting at? In the MP
case that is.. you previously said "irq 5", but an MP kernel should
print something like "interrupting at ioapic0 pin 5".

- Frank

-- 
Frank van der Linden                                            fvdl@netbsd.org
===============================================================================
NetBSD. Free, Unix-like OS. > 45 different platforms.    http://www.netbsd.org/