From owner-freebsd-current@FreeBSD.ORG Sun Jun 17 11:57:24 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6CD31065670; Sun, 17 Jun 2012 11:57:24 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8845A8FC08; Sun, 17 Jun 2012 11:57:24 +0000 (UTC) Received: by yhgm50 with SMTP id m50so3769002yhg.13 for ; Sun, 17 Jun 2012 04:57:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jx1ZINH0m0SZeoVzKlKhPuH1R3eOJCDCtaWsmSKnp5A=; b=BQA28b1AYSnK+MORRu8Et3IBAA5AnBJWa2gjoWNDu8K31CaWhDfynIF7vxBldhtupZ xX01MjJ8TfLsOy7aqEtSqHyTXb/dupY3dSxzApZwCyr+kpQdtHAlCBIl53Xw5ZFyjOjy g4yOdlkWt087Q8piX3KKcAd6+ycNHwmTsibgzYz4ZdATpJSn9wG4k+8wrHTvG3BYi3Gh fL2cSFcVp2t3F8qN/t5hIOEf1Wm7xnhcOnugpjMiDugMa6sA75hKR35JC4FM6PZHDVF/ QpbLl86JCBWBRvab9+6KDN556seE6+DNuU1LbmerWVe92eb9a8xbdIHxanjhN10RP30z QcIw== MIME-Version: 1.0 Received: by 10.42.189.73 with SMTP id dd9mr2946424icb.49.1339934237860; Sun, 17 Jun 2012 04:57:17 -0700 (PDT) Received: by 10.231.136.1 with HTTP; Sun, 17 Jun 2012 04:57:17 -0700 (PDT) Received: by 10.231.136.1 with HTTP; Sun, 17 Jun 2012 04:57:17 -0700 (PDT) In-Reply-To: References: Date: Sun, 17 Jun 2012 13:57:17 +0200 Message-ID: From: Daniel Nebdal To: Alexander Yerenkow Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Current , FreeBSD Stable Subject: Re: Stucking processes 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: Sun, 17 Jun 2012 11:57:25 -0000 Couldn't that just be because you're running a world that expects one kernel but finds another? As far as I know, running a newer world in a jail on an older system is not really recommended (while the opposite ought to be ok)? On Jun 16, 2012 11:33 AM, "Alexander Yerenkow" wrote: > Hello all. > Since I'm using stable as host, and current in chroot, I'll write to > both mail list, sorry for any inconvenience. > > My host is binary freebsd-updated 9; > FreeBSD 9.0-RELEASE-p3 (GENERIC) #0: Tue Jun 12 02:52:29 UTC 2012 > > I have chroot with latest current there installed r237089 (make > buildworld && buildkernel, no specific flags) > When I built from ports some programs in chroot all went fine, until I > got stucked process automoc (when building kdelibs4); > After few restarts I got build, and forget about it. > I'm toying now with portupgrade, and see similar stucks in ruby18 and > ruby19 (Even got few times in miniruby while building 1.8); > > Here's example of stucked processes (they aren't in top, and seems > totally inactive. I haven't kill them yet, so can try to dig, but to > where?): > 2677 5 Is 0:00,00 | `-- /bin/sh > 2678 5 I 0:00,00 | `-- sudo su > 2679 5 I 0:00,00 | `-- su > 2680 5 I 0:00,01 | `-- _su (csh) > 2687 5 I 0:00,03 | `-- /bin/csh -i > 2690 5 I+ 0:04,34 | `-- ruby19: portupgrade: [1/237] > audio/libsamplerate (ruby19) > > # procstat -k 2690 > PID TID COMM TDNAME KSTACK > 2690 100477 ruby19 - mi_switch > sleepq_catch_signals sleepq_timedwait_sig _sleep do_wait > __umtx_op_wait_uint_private_compat32 ia32_syscall Xint0x80_syscall > 2690 101110 ruby19 - mi_switch > sleepq_catch_signals sleepq_wait_sig _cv_wait_sig seltdwait > kern_select freebsd32_select ia32_syscall Xint0x80_syscall > > #top (with inactive filtered out;) > last pid: 11049; load averages: 0.09, 0.16, 0.19 > > up 0+00:14:48 12:27:20 > 63 processes: 1 running, 62 sleeping > CPU: 1.0% user, 0.0% nice, 0.8% system, 1.2% interrupt, 97.0% idle > Mem: 184M Active, 96M Inact, 1104M Wired, 2412K Cache, 171M Buf, 454M Free > Swap: 4096M Total, 4096M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 2610 root 2 20 0 261M 82548K kqread 1 0:12 1.27% > rtorrent > > > Is this my side's problem, or there's something wrong with current? :) > Any help appreciated. > > -- > Regards, > Alexander Yerenkow > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >