Date: Tue, 17 Feb 2004 10:47:50 +0100 (MET) From: Adriaan de Groot <adridg@sci.kun.nl> To: freebsd-amd64@freebsd.org Subject: Re: The return of threading errors in ogg123 Message-ID: <Pine.GSO.4.44.0402171046590.15879-100000@wn4.sci.kun.nl> In-Reply-To: <Pine.GSO.4.44.0402171025520.15647-100000@wn4.sci.kun.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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) @
/mnt/sys/CURRENT
/src/sys/vm/swap_pager.c:1822
3rd 0xffffff003e0e8700 vm object (vm object) @
/mnt/sys/CURRENT/src/sys/vm/uma_
core.c:886
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@cs.kun.nl Kamer A6020 024-3652272
GPG Key Fingerprint 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE
http://www.cs.kun.nl/~adridg/research/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.44.0402171046590.15879-100000>