From owner-freebsd-current@FreeBSD.ORG Sat Jul 9 01:02:02 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 32A9316A41C for ; Sat, 9 Jul 2005 01:02:02 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C10DB43D45 for ; Sat, 9 Jul 2005 01:01:58 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from [192.168.1.11] (tardiss.hsd1.ma.comcast.net[66.30.82.93]) by comcast.net (rwcrmhc11) with ESMTP id <200507090101560130032p11e>; Sat, 9 Jul 2005 01:01:57 +0000 Message-ID: <42CF21F2.2060108@comcast.net> Date: Fri, 08 Jul 2005 21:01:38 -0400 From: Sean User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam K Kirchhoff References: <42C098B0.5060004@voicenet.com> In-Reply-To: <42C098B0.5060004@voicenet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Portupgrade, -CURRENT & SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rsh.lists@comcast.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2005 01:02:02 -0000 Adam K Kirchhoff wrote: > > I have three machines which I just upgraded from 5.4 to -CURRENT. They > are two SMP desktops and a UP laptop. > > After building world and installing, I started to run portupgrade on my > systems. On the laptop, everything has been running smoothly.. On both > SMP systems, portupgrade hangs. top shows the ruby18 process stuck in > the *vnode state. On one machine, which I can't physically access, it's > been this way for hours. I can't ssh into this machine, and only have > access to sessions that were connected before the hang. On my home > machine (which I can physically access), I've been able to log in on the > virtual consoles and reboot when this happens (though it's not ever able > to sync all buffers and cleanly unmount /). It's now happened with 5 or > 6 consecutive attempts at portupgrade on this machine. The most recent > time this happened, on a hunch, I built a UP kernel, rebooted, and tried > portupgrade again. It's now been running for two hours without hanging > (previous record was less than five minutes). > > I've googled around a bit for this problem, but haven't come across > anythign yet. Has anyone seen this before? I'll gladly submit a pr, > but I'm just looking for more idea, or maybe some confirmation from > others who have seen this. > > Adam > > _______________________________________________ > 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" > Adam, Thought you might be interested. I booted with an older kernel I made back in January, and all portupgrades worked without problems. The config for this build and my one build a week or three ago are the same. So I would figure that this would suggest that it is most likely not the port, but something in the recent source for the kernel? Sean