Re: panic in bus_dma_tag_destroy()

[Chuck Tuffli <chuck_tuffli@xxxxxxxxxxx>]

On Wed, Oct 06, 2004 at 04:00:06PM -0700, Matthew Dillon wrote:
. ..
>     Get a backtrace from the DDB prompt.   The 'trace' command. If you
>     aren't getting a DDB prompt then compile up a kernel with 'options DDB'
>     in the kernel config.

The console wedges after the panic, but below is what shows up before
that. If this isn't enough, I can copy down the backtrace

svd0: Agilent Tachyon Driver Version 1.0
svd0: <Agilent Tachyon QX4 PCI-E FC Adapter rev 1.0> port 0xc000-0xc0ff,0xc400-0xc4ff mem 0xfe9f8000-0xfe9f9fff irq 11 at device 0.0 on
pci5
parent_dmat 0xce8d2290
map_count 0
ref_count 1
segments  0xc1a86000
parent_dmat 0xce8d2290
map_count 0
ref_count 1
segments  0xc1a86000
panic: assertion: z->z_Magic == ZALLOC_SLAB_MAGIC in free
mp_lock = 00000001; cpuid = 1; lapic.id = 06000000
panic(c1a80000,ff808000,0,cee1db38,c0240483) at panic+0xbd
panic(c04468e0,c044692d,ce8d2290,0,0) at panic+0xbd
free(c1a86000,c04c3ae0) at free+0x193
bus_dma_tag_destroy(ce8d2290,c814bd70,c814bd70,cee1db74,cee27771) at bus_dma_tag_destroy+0x36
svd_release_bus(cec6a928,c814bd70,cee1db88,c024f5be,c814bd70) at svd_release_bus+0x77
svd_pci_detach(c814bd70) at svd_pci_detach+0x11
device_detach(c814bd70) at device_detach+0x56
devclass_delete_driver(c1600bf8,cee28f84,ce8d20d0,c80bae80,cebca0b8) at devclass_delete_driver+0x82
driver_module_handler(ce8d20d0,1,cee28f9c,cee1dbf4,c022db1e) at driver_module_handler+0x90
module_unload(ce8d20d0,cebca0b8,c80bae80,1,0) at module_unload+0x11
linker_file_unload(cebca0b8,0,cee1dd40,c03f12d2,cee1dc38) at linker_file_unload+0x5a
kldunload(cee1dc38,0,bfbffcbe,3,cee1dd20) at kldunload+0x65
syscall2(2f,2f,2f,3,bfbffcbe) at syscall2+0x266
Xint0x80_syscall() at Xint0x80_syscall+0x2a
Debugger("panic")

CPU1 stopping CPUs: 0x00000001
 stopped
Stopped at      Debug

-- 
Chuck Tuffli
Agilent Technologies