The return of threading errors in ogg123

Adriaan de Groot adridg at
Tue Feb 17 01:47:52 PST 2004

libc_r seems better behaved; possibly unrelated, I did just get a lock
order reversal, with this trace (1st fell off the screen, sorry):

 2nd 0xffffffff807dcca0 swap_pager swhash (swap_pager swhash) @
 3rd 0xffffff003e0e8700 vm object (vm object) @
Stack backtrace:
backtrace() at backtrace+0x17
witness_checkorder() at witness_checkorder+0x678
_mtx_lock_flags() at _mtx_lock_flags+0x80
obj_alloc() at obj_alloc+0x41
slab_zalloc() at slab_zalloc+0xa2
uma_zone_slab() at uma_zone_slab+0xd5
uma_zalloc_internal() at uma_zalloc_internal+0x3c
uma_zalloc_arg() at uma_zalloc_arg+0x3a6
swp_pager_meta_build() at swp_pager_meta_build+0x14b
swap_pager_putpages() at swap_pager_putpages+0x2f3
default_pager_putpages() at default_pager_putpages+0xa
vm_pageout_flush() at vm_pageout_flush+0x15e
vm_pageout_clean() at vm_pageout_clean+0x292
vm_pageout_scan() at vm_pageout_scan+0x65f
vm_pageout() at vm_pageout+0x377
fork_exit() at fork_exit+0xd9
fork_trampoline() at fork_trampoline+0xe

 Adriaan de Groot    adridg at     Kamer A6020     024-3652272
GPG Key Fingerprint 934E 31AA 80A7 723F 54F9  50ED 76AC EE01 FEA2 A3FE

More information about the freebsd-amd64 mailing list