Date: Wed, 29 Jun 2005 18:53:30 -0400 From: Adam K Kirchhoff <adamk@voicenet.com> To: rsh.lists@comcast.net Cc: freebsd-current@freebsd.org Subject: Re: Portupgrade, -CURRENT & SMP Message-ID: <42C3266A.3000901@voicenet.com> In-Reply-To: <42C31D30.3000009@comcast.net> References: <42C098B0.5060004@voicenet.com> <42C119FE.7020809@comcast.net> <42C1381B.9000901@voicenet.com> <42C31D30.3000009@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean wrote: > Adam K Kirchhoff wrote: > >> Sean wrote: >> >>> 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" >>>> >>> >>> Same problem here, with no solution for the problem. >>> >>> Sean >>> _______________________________________________ >>> 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" >>> >> >> Well, since I at least know that I'm not alone in this, I've >> submitted a pr (after searching for one with SMP and portupgrade and >> coming up blank): >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=82730 >> >> Anyone having this problem, please take note and add your own >> comments if possible. >> >> Adam >> >> > So I guess for now we have to rebuild the kernel to go SMP, > portupgrade, then rebuild back to SMP. Annoying. I think you mean '...we have to rebuild the kernel to go UP, portupgrade..." Which, yes, is quite annoying and, IMHO, is a pretty critical bug that needs fixing. It makes SMP on -CURRENT nearly unusable if you want to regularly update your ports. Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C3266A.3000901>