Hello, During the configuration phase, just after installing 6.0-BETA2 on a notebook, i got the following message on the console: lock order reversal 1st 0xc097b240 UMA lock (UMA lock) _at_ /usr/src/sys/vm/uma_core.c:1494 2nd 0xc1060144 system map (system map) _at_ /usr/src/sys/vm/vm_kern.c:295 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c0930358,c0930498,c08bace4) at kdb_backtrace+0x29 witness_checkorder(c1060144,9,c087130e,127) at witness_checkorder+0x564 _mtx_lock_flags(c1060144,0,c087130e,127) at _mtx_lock_flags+0x5b _vm_map_lock(c10600c0,c087130e,127) at _vm_map_lock+0x26 kmem_malloc(c10600c0,1000,1,e504bba4,c077e865) at kmem_malloc+0x32 page_alloc(c104a5a0,1000,e504bb97,1,c0653450) at page_alloc+0x1a slab_zalloc(c104a5a0,1,3,c3eaa1c0,c10492ac) at slab_zalloc+0xa1 uma_zone_slab(c104a5a0,1,1,10,31fb) at uma_zone_slab+0xe8 uma_zalloc_bucket(c104a5a0,1) at uma_zalloc_bucket+0x12c uma_zalloc_arg(c104a5a0,0,1) at uma_zalloc_arg+0x2dc malloc(200,c08f5480,1,50,c1044a00) at malloc+0xae hash_alloc(e504bc74,c1044a08,0,c08705c7,1ab) at hash_alloc+0x29 zone_timeout(c26bf000) at zone_timeout+0x7e zone_foreach(c077e09c,e504bce8,c063d25f,0,c077e068) at zone_foreach+0x37 uma_timeout(0) at uma_timeout+0x12 softclock(0) at softclock+0x1e7 ithread_loop(c2325580,e504bd38,c2325580,c061f854,0) at ithread_loop+0x11c fork_exit(c061f854,c2325580,e504bd38) at fork_exit+0xa0 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe504bd6c, ebp = 0 --- The machine is already up (no panic, no hang, no shutdown). When it happened, i was in the process of editing configuration files remotely with a build of net/cvsup-without-gui using the traditional way (i.e. 'make install'). If somebody is interesting in testing something or get more information, the machine is ready to test what may be necessary. -- -jpeg.Received on Sat Aug 13 2005 - 14:44:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:41 UTC