From owner-freebsd-current@FreeBSD.ORG Wed Sep 28 19:17:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C86F616A41F for ; Wed, 28 Sep 2005 19:17:49 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DF0043D4C for ; Wed, 28 Sep 2005 19:17:47 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by smtp1-g19.free.fr (Postfix) with ESMTP id 15DBF2FE4F; Wed, 28 Sep 2005 21:17:46 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id ADEF6405A; Wed, 28 Sep 2005 21:17:46 +0200 (CEST) Date: Wed, 28 Sep 2005 21:17:46 +0200 From: Jeremie Le Hen To: Roger Grosswiler Message-ID: <20050928191746.GB1027@obiwan.tataz.chchile.org> References: <433AE588.2070002@gwch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <433AE588.2070002@gwch.net> User-Agent: Mutt/1.5.10i Cc: freebsd-current@freebsd.org Subject: Re: Problems loading Gnome X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2005 19:17:49 -0000 Hi Roger, > i recently installed Beta4 sucessfully, but after login i have to wait > 10 minutes to get a workin system. > > Dmesg shows this: > > lock order reversal > 1st 0xc097f8e0 UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1494 > 2nd 0xc1060144 system map (system map) @ /usr/src/sys/vm/vm_map.c:2317 > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c09348c0,c0934a00,c08bef84) at kdb_backtrace+0x29 > witness_checkorder(c1060144,9,c0875486,90d) at witness_checkorder+0x564 > _mtx_lock_flags(c1060144,0,c0875486,90d) at _mtx_lock_flags+0x5b > _vm_map_lock(c10600c0,c0875486,90d) at _vm_map_lock+0x26 > vm_map_remove(c10600c0,c1d05000,c1d06000,cc9ffc0c,c07827a9) at > vm_map_remove+0x1f > kmem_free(c10600c0,c1d05000,1000,cc9ffc3c,c0782156) at kmem_free+0x25 > page_free(c1d05000,1000,2) at page_free+0x29 > zone_drain(c103f000) at zone_drain+0x26a > zone_foreach(c0781eec,cc9ffcec,c07940d7,cc9ffc74,246) at zone_foreach+0x37 > uma_reclaim(cc9ffc74,246,0,cc9ffc80,c062b7d9) at uma_reclaim+0x12 > vm_pageout_scan(0,c097fd40,0,c0876973,604) at vm_pageout_scan+0x103 > vm_pageout(0,cc9ffd38,0,c0794f2c,0) at vm_pageout+0x2c3 > fork_exit(c0794f2c,0,cc9ffd38) at fork_exit+0xa0 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xcc9ffd6c, ebp = 0 --- > > > What can this be? What can i do? This is clearly explained by Robert Watson in this post : http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.html What you can do depends on your skills actually. If you feel strong enough, you can fix it. If not, you can check this page http://sources.zabbadoz.net/freebsd/lor.html maintained by Bjoern A. Zeeb if this LOR is already reported (this should be done pretty quickly by looking for the string "UMA lock" for intance). In case of it is not, then report it on this very list. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >