Date: Tue, 15 Dec 2009 17:49:05 +0100 From: Gary Jennejohn <gary.jennejohn@freenet.de> To: Pierre Beyssac <pb@fasterix.frmug.org> Cc: freebsd-current@freebsd.org Subject: Re: "illegal hardware instruction (core dumped)" cvsup/amd64 Message-ID: <20091215174905.467da401@ernst.jennejohn.org> In-Reply-To: <20091215140234.GA94567@fasterix.frmug.org> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <EA53E98C-25FC-466E-8C98-D9460C097393@sarenet.es> <86d42hmu1o.fsf@ds4.des.no> <f83770800912141932l639346a4w78bbf43c9f1c9032@mail.gmail.com> <20091215080637.GA8100@rink.nu> <20091215140234.GA94567@fasterix.frmug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Dec 2009 15:02:34 +0100 Pierre Beyssac <pb@fasterix.frmug.org> wrote: > Since upgrading my world with a -current built last night, cvsup > dumps core on me. Any idea? > > It is a Intel/ATOM 330 box used in 64bit mode. Everything else on > the box runs fixe. > > Recompiling cvsup + ezm3 didn't fix the problem; neither did trying > a libc from October. > I reported this everal weeks ago but there was never a satisfactory resolution to the problem. One poster (scf@) reported that using a 32-bit binary solves the problem. In my experience running cvsup against a remote server (to keep a local CVS tree up to date) works just fine. Are you also running cvsupd and attaching to it? I've found that not starting cvsupd in /etc/rc.conf and instead starting it without -C in a shell script just before invoking cvsup works, so I use something like this: /usr/local/sbin/cvsupd& sleep 1 /usr/local/bin/cvsup supfile and have localhost in supfile. Otherwise I suggest using csup, which does not exhibit any bugs. --- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091215174905.467da401>