On Wed, 5 Nov 2003, Frank van der Linden wrote:

> 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.

will do.

> 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".

mainbus0: Intel MP Specification (Version 1.4) (COMPAQ   PROLIANT    )
...
esiop0: interrupting at apic 2 int 5 (irq 5)
...
tl0: interrupting at apic 2 int 5 (irq 5)


	Thanks for looking!

-- 

The nice thing about Windows is - It does not just crash, it displays a
dialog box and lets you press 'OK' first.
						-- Arno Schaefer