From owner-freebsd-current Mon Mar 6 16:54:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 34C7C37BE96 for ; Mon, 6 Mar 2000 16:54:31 -0800 (PST) (envelope-from saxonww@ufl.edu) Received: from n44-230.dhnet.ufl.edu (gremlin@[128.227.44.230]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id TAA46662; Mon, 6 Mar 2000 19:54:22 -0500 Date: Mon, 6 Mar 2000 19:54:22 -0500 (EST) From: Will Saxon X-Sender: gremlin@localhost To: Devin Butterfield Cc: current@FreeBSD.ORG Subject: Re: Error: no such 386 instruction: `state' ??? In-Reply-To: <00030616230000.06832@dbm.wireless.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was having this problem a few weeks ago while trying to make world. I had just gotten a new motherboard, that was letting me overclock my processor (it offered new bus speeds). I reset the processor to run at its default speed, and I have not seen this error since. So, if you are overclocked at all I would suggest trying to clock it down a little. -Will On Mon, 6 Mar 2000, Devin Butterfield wrote: > Hi, > > I'm running a snap from 2/28: > > FreeBSD dbm.wireless.net 4.0-20000228-CURRENT FreeBSD 4.0-20000228-CURRENT #2: > Fri Mar 3 22:19:33 PST 2000 > > Often when compiling a port, the process will fail with messages like > the following: > > [...] > Compiling smbd/noquotas.c > Compiling smbd/reply.c > {standard input}: Assembler messages: > {standard input}:4939: Error: no such 386 instruction: `state' > *** Error code 1 > > Stop in /usr/ports/net/samba/work/samba-2.0.6/source. > *** Error code 1 > > Stop in /usr/ports/net/samba. > *** Error code 1 > > Stop in /usr/ports/net/samba. > *** Error code 1 > > Stop in /usr/ports/net/samba. > *** Error code 1 > > Stop in /usr/ports/net/samba. > [root@dbm /usr/ports/net/samba]# > > The strange thing is, if I just say "make" again, it will continue to compile > where it left off without any problems. > > Anyone else see these errors? Any Ideas? > -- > Regards, Devin. > > P.S. Never had this problem under 3.x. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message