From owner-freebsd-alpha Wed Oct 25 6:25: 6 2000 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 9CCA137B479 for ; Wed, 25 Oct 2000 06:25:04 -0700 (PDT) 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 JAA17981; Wed, 25 Oct 2000 09:25:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e9PDP3S14313; Wed, 25 Oct 2000 09:25:03 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 25 Oct 2000 09:25:03 -0400 (EDT) To: alpha@shell.scrypt.net Cc: alpha Subject: Re: Instant machine check upon execution of syslog In-Reply-To: <972450296.39f669f8900cc@scrypt.net> References: <972450296.39f669f8900cc@scrypt.net> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14838.57089.511894.449513@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org alpha@shell.scrypt.net writes: > Hey, I've got a screwy one here. On a virgin install of 4.1, I get an > immediate machine check upon starting syslogd. It also happens with syslog- > ng. I've tried a couple of things such as deleteing /var/run/log, or creating > it as a character device (7,0 though isn't that klog?) but so far no good. Any > ideas? > > Oh, my box is a 164SX. Can you give any more details? The exact output from machine check itself would be quite useful. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message