On Tue, Jan 08, 2008 at 12:50:35AM +0100, Anders Hjalmarsson wrote: > cpu_Debugger() at netbsd:cpu_Debugger+0x4 > panic() at netbsd:panic+0x1c8 > console_restart() at netbsd:console_restart+0x78 > XentRestart() at netbsd:XentRestart+0x90 > --- console restart (from ipl 5) --- > nullop() at netbsd:nullop > mutex_vector_enter() at netbsd:mutex_vector_enter+0x320 > pool_put() at netbsd:pool_put+0x40 > pmap_tlb_shootdown_job_put() at netbsd:pmap_tlb_shootdown_job_put+0x30 > pmap_do_tlb_shootdown() at netbsd:pmap_do_tlb_shootdown+0x16c > alpha_ipi_process() at netbsd:alpha_ipi_process+0xb8 > interrupt() at netbsd:interrupt+0x80 > XentInt() at netbsd:XentInt+0x1c > --- interrupt (from ipl 0) --- > idle_loop() at netbsd:idle_loop+0x164 > exception_return() at netbsd:exception_return I made some changes to the pmap that could help the situation (rev 1.230 of arch/alpha/alpha/pmap.c). Can you try updating and see if the problem still persists? If it happens again, it would be really useful if you could get a backtrace from all the CPUs. For example: mach cpu 0 bt mach cpu 1 bt mach cpu 2 bt .... Thanks, Andrew