Date: Sun, 12 Jul 2009 23:06:04 -0800 From: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net> To: freebsd-current@freebsd.org Cc: "Robert N. M. Watson" <rwatson@freebsd.org> Subject: Re: odd make/build output on ^Z / fg Message-ID: <200907122306.04887.mel.flynn%2Bfbsd.current@mailing.thruhere.net> In-Reply-To: <3a142e750907121652k290f0314rde7eac2ebd2cd57@mail.gmail.com> References: <alpine.BSF.2.00.0907090836050.10745@fledge.watson.org> <0EF108C4-703F-4EC9-88B1-C04BE47035CF@freebsd.org> <3a142e750907121652k290f0314rde7eac2ebd2cd57@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 12 July 2009 15:52:46 Paul B. Mahol wrote: > On 7/12/09, Robert N. M. Watson <rwatson@freebsd.org> wrote: > > On 12 Jul 2009, at 19:16, Mel Flynn wrote: > >> On Wednesday 08 July 2009 23:37:36 Robert Watson wrote: > >>> *** Signal 1 > >>> couldn't resume audit_arg.o: No such process > >>> *** Signal 1 > >>> couldn't resume nlm_prot_impl.o: No such process > >>> *** Signal 1 > >>> couldn't resume nfs_serv.o: No such process > >>> *** Signal 1 > >>> couldn't resume nfs_vnops.o: No such process > >>> *** Signal 1 > >>> couldn't resume modules-obj: No such process > >>> ===> usb/uether (obj) > >>> ===> usb/aue (obj) > >>> ... > >>> ===> xfs (obj) > >>> ===> xl (obj) > >>> ===> zfs (obj) > >>> ===> zlib (obj) > >>> *** Signal 1 > >>> 6 errors > >>> > >>> I've never seen that before, but I also don't suspend builds all that > >>> frequently. New bug? Old bug? > >> > >> Also seen this with a suspended port build, but didn't investigate > >> further, > >> just restarted the build. Shell used is zsh, in case that matters. I > >> am not > >> sure if I was building in parallel. Currently running r195188M: Tue > >> Jun 30 > >> 12:16:01 AKDT 2009. I remember I had that build suspended for a few > >> hours, but > >> not a chance I ran out of swap (which would kill processes without > >> my direct > >> knowledge). > > > > I'm using tcsh here. > > I got same with some ports few weeks ago, disabling multiple jobs fixed it > almost always. > > Will try to reproduce with kernel next time ... Is it possible you guys let it suspend over 24 hours? It's possible I did that. Would be a scenario since kqueue timers roll over. I can't think of anything else too obvious, since I'm sure I didn't kill something, updated source during the build or otherwise affected timestamps. I also don't have mysteriously disappearing processes haunting my system. 3 fatal attempts to reproduce today with make -j2 buildworld. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907122306.04887.mel.flynn%2Bfbsd.current>