On Fri, 17 Sep 2004, Greg A. Woods wrote:

> OK, so I've got a shiny "new" 4-CPU 16-GB AlphaServer ES40 Model 2 to
> play with now!

  The 8GB ES40 I've been playing with has gotten a panic when trying to
do very much disk I/O.  I haven't had time to look into it any further
yet.  It looks like something is trying to free a partial region of an
extent that had been allocated for DMA.  I've never been able to get a
dump out of it yet (since the panic occurs during disk I/O, the driver
probably won't be able to do anything).

  There's also the problem that when the USB controller is configured, it
can cause continuous interrupts.  [There's a PR or two currently open on
this.]

extent `tsp_sgmap' (0x0 - 0x7fffff), flags = 0x2
     0x0 - 0x1fff
     0x2000 - 0x3fff
     0x4000 - 0x7fff
     0x8000 - 0xbfff
extent_free: start 0x4000, end 0x5fff
panic: extent_free: region not found
Begin traceback...
alpha trace requires known PC =eject=
End traceback...
syncing disks... extent `tsp_sgmap' (0x0 - 0x7fffff), flags = 0x2
     0x0 - 0x1fff
     0x2000 - 0x3fff
     0x4000 - 0x7fff
     0x8000 - 0xbfff
extent_free: start 0x8000, end 0x9fff
panic: extent_free: region not found
Begin traceback...
alpha trace requires known PC =eject=
End traceback...
cpu3: shutting down...

...

extent `tsp_sgmap' (0x0 - 0x7fffff), flags = 0x2
     0x0 - 0x1fff
     0xe000 - 0x11fff
extent_free: start 0xe000, end 0xffff
panic: extent_free: region not found
Stopped in pid 20945.1 (sh) at  netbsd:cpu_Debugger+0x4:        ret
zero,(ra
)
db{0}> t
cpu_Debugger() at netbsd:cpu_Debugger+0x4
panic() at netbsd:panic+0x208
extent_free() at netbsd:extent_free+0x194
pci_sgmap_pte64_unload() at netbsd:pci_sgmap_pte64_unload+0xf4
tsp_bus_dmamap_unload_sgmap() at netbsd:tsp_bus_dmamap_unload_sgmap+0x30
mlx_ccb_unmap() at netbsd:mlx_ccb_unmap+0xa8
ld_mlx_handler() at netbsd:ld_mlx_handler+0xb4
mlx_intr() at netbsd:mlx_intr+0x10c
alpha_shared_intr_dispatch() at netbsd:alpha_shared_intr_dispatch+0x6c
dec_6600_iointr() at netbsd:dec_6600_iointr+0x4c
interrupt() at netbsd:interrupt+0x334
XentInt() at netbsd:XentInt+0x1c
--- interrupt (from ipl 0) ---
acquire() at netbsd:acquire+0xb4
lockmgr() at netbsd:lockmgr+0x5b0
trap() at netbsd:trap+0x95c
XentMM() at netbsd:XentMM+0x20
--- memory management fault ---
--- user mode ---
db{0}> reboot 10c
cpu3: shutting down...
cpu1: shutting down...
cpu2: shutting down...




--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA