From owner-freebsd-alpha Tue Feb 26 10: 1:47 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DEA7537B430 for ; Tue, 26 Feb 2002 10:01:09 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA09138; Tue, 26 Feb 2002 13:01:09 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1QI0dk07665; Tue, 26 Feb 2002 13:00:39 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15483.52551.296701.638173@grasshopper.cs.duke.edu> Date: Tue, 26 Feb 2002 13:00:39 -0500 (EST) To: Cc: Subject: Re: "unexpected machine check" on AS1000A In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The cpu option in the config file is meaningless & should be ignored on alpha. However, you should be able to add CPUTYPE=ev56 to /etc/make.conf. This will result in smaller, faster binaries which have a better chance of avoiding optimizer bugs at higher optimization levels. However, your problem is probably bad memory. It looks like you had 5 single bit errors (one for each "Warning: received processor correctable error") then then you had a multiple bit error, which cannot be corrected & results in the hardware throwing an uncorrectable machine check. Drew Yuri Victorovich writes: > On my AS1000A 5/500, 500MHz I got FreeBSD 4.5 > installed. > Kernel cvsuped from FreeBSD 4.5 STABLE (RELENG_4) > as of today's morning and rebuilt > with > << > options DEC_1000A > cpu EV5 > >> > Other similar options DEC_XXX and EV4 are > commented out since they are for other > kinds of alpha. > > Machine boots up and after some while of > "make world" and some other activities > "unexpected machine check", see log > below. > > Can it be because of preceding "processor > correctable error"? > > Or maybe because when system boots it > identifies cpu as: > > CPU: EV56 (21164A) major=7 minor=1 extensions=0x1 > > and in options is only EV5 the closest match? > > What's strange -- this never happened during several > installs from floppies and CDROM or FTP. > > Other info of possible interest from boot log: > OSF PAL rev: 0x1000600020116 > > Or am I missing something again? )) > > Any help will be greatly appreciated! > > Yuri. > > > ================================================ > > [...] > Feb 26 11:19:11 s2 /kernel: cd0 at isp0 bus 0 target 4 lun 0 > Feb 26 11:19:11 s2 /kernel: cd0: Removable CD-ROM > SCSI-2 device > Feb 26 11:19:11 s2 /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 8) > Feb 26 11:19:11 s2 /kernel: cd0: Attempt to query device size failed: NOT > READY, Medium not present > Feb 26 11:19:48 s2 su: yuri to root on /dev/ttyp0 > Feb 26 11:20:09 s2 login: ROOT LOGIN (root) ON ttyd0 > Feb 26 11:22:57 s2 /kernel: Warning: received processor correctable error. > Feb 26 11:31:29 s2 /kernel: Warning: received processor correctable error. > Feb 26 11:33:03 s2 last message repeated 3 times > Feb 26 11:39:07 s2 /kernel: > Feb 26 11:39:07 s2 /kernel: unexpected machine check: > Feb 26 11:39:07 s2 /kernel: > Feb 26 11:39:07 s2 /kernel: mces = 0x1 > Feb 26 11:39:07 s2 /kernel: vector = 0x670 > Feb 26 11:39:07 s2 /kernel: param = 0xfffffc0000006060 > Feb 26 11:39:07 s2 /kernel: pc = 0xfffffc00003cc09c > Feb 26 11:39:07 s2 /kernel: ra = 0xfffffc00004231f4 > Feb 26 11:39:07 s2 /kernel: curproc = 0xfffffe00098ded00 > Feb 26 11:39:07 s2 /kernel: pid = 15247, comm = install > Feb 26 11:39:07 s2 /kernel: > Feb 26 11:39:07 s2 /kernel: panic: machine check > Feb 26 11:39:07 s2 /kernel: > Feb 26 11:39:07 s2 /kernel: syncing disks... 84 25 24 24 24 24 24 24 24 24 > 24 24 24 24 24 24 24 24 24 24 24 24 > Feb 26 11:39:07 s2 /kernel: giving up on 24 buffers > Feb 26 11:39:07 s2 /kernel: Uptime: 17m42s > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message