From owner-freebsd-current@FreeBSD.ORG Sat Jan 19 05:27:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E81616A417 for ; Sat, 19 Jan 2008 05:27:02 +0000 (UTC) (envelope-from peter@wemm.org) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id DF1C613C45B for ; Sat, 19 Jan 2008 05:27:01 +0000 (UTC) (envelope-from peter@wemm.org) Received: by fg-out-1718.google.com with SMTP id 16so1446506fgg.35 for ; Fri, 18 Jan 2008 21:27:00 -0800 (PST) Received: by 10.82.121.15 with SMTP id t15mr7524319buc.26.1200720419636; Fri, 18 Jan 2008 21:26:59 -0800 (PST) Received: by 10.82.181.17 with HTTP; Fri, 18 Jan 2008 21:26:59 -0800 (PST) Message-ID: Date: Fri, 18 Jan 2008 21:26:59 -0800 From: "Peter Wemm" To: "Pawel Worach" In-Reply-To: <47917E41.3050002@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47917E41.3050002@gmail.com> Cc: current@freebsd.org Subject: Re: Processes stuck in vmo_de state 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: Sat, 19 Jan 2008 05:27:02 -0000 On Jan 18, 2008 8:36 PM, Pawel Worach wrote: > Hi, > > On recent current when building the gnome2 meta port the build gets > stuck, here is a ddb trace of the stuck process. Any ideas ? > > db> ps > pid ppid pgrp uid state wmesg wchan cmd > 46836 46834 81809 0 S+ piperd 0xc80d6da4 grep > 46835 46834 81809 0 S+ vmo_de 0xc080f074 sh > 46834 46719 81809 0 S+ wait 0xc3dc82ac sh > db> bt 46835 > Tracing pid 46835 tid 100105 td 0xc3e1f000 > sched_switch(c3e1f000,0,1,20794e9a,1b01,...) at sched_switch+0x46b > mi_switch(1,0,c3e1f000,e6597940,c05ad5e7,...) at mi_switch+0x120 > sleepq_switch(c3e1f000,0,c079c9f3,240,0,...) at sleepq_switch+0x88 > sleepq_timedwait(c080f074,1,c07acfa9,2,0,...) at sleepq_timedwait+0x37 > _sleep(c080f074,0,0,c07acfa9,1,...) at _sleep+0x2c4 > pause(c07acfa9,1,0,0,0,...) at pause+0x30 > vm_object_deallocate(c59b2480,281d8000,281f5000,c21e4000,0,...) at > vm_object_deallocate+0x34b > vm_map_delete(c4543828,0,bfc00000,c39c5000,c4543828,...) at > vm_map_delete+0x348 > vm_map_remove(c4543828,0,bfc00000,c079ff3d,11a,...) at vm_map_remove+0x55 > exec_new_vmspace(e6597be8,c07ec800,e6597be8,e6597ae8,c055855f,...) at > exec_new_vmspace+0x1b0 > exec_elf32_imgact(e6597be8,38,687,c14d51c0,e0cbf000,...) at > exec_elf32_imgact+0x21a > kern_execve(c3e1f000,e6597c5c,0,81899c0,8189ee4,e0cbf000,e0cbf000,e0cbf031,e0cbf6b8,e0cff000,3f948,4,38) > at kern_execve+0x3a1 > execve(c3e1f000,e6597cfc,c,e6597d38,e6597d2c,...) at execve+0x4c > syscall(e6597d38) at syscall+0x345 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (59, FreeBSD ELF32, execve), eip = 0x28145c2f, esp = > 0xbfbfcdfc, ebp = 0xbfbfce18 --- > > -- > Pawel I ran into the same thing recently too. Same stack trace. The machine was running with the ULE scheduler and I heard hints that this problem tends to turn up only with ULE. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5