From owner-freebsd-hackers  Wed Feb 18 14:50:04 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA04313
          for freebsd-hackers-outgoing; Wed, 18 Feb 1998 14:50:04 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from singapore.eecs.umich.edu (singapore.eecs.umich.edu [141.213.8.39])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04205
          for <freebsd-hackers@FreeBSD.ORG>; Wed, 18 Feb 1998 14:49:40 -0800 (PST)
          (envelope-from weeteck@eecs.umich.edu)
Received: (from weeteck@localhost)
	by singapore.eecs.umich.edu (8.8.8/8.8.7) id RAA11619;
	Wed, 18 Feb 1998 17:49:01 -0500 (EST)
From: Wee Teck Ng <weeteck@eecs.umich.edu>
Message-Id: <199802182249.RAA11619@singapore.eecs.umich.edu>
Subject: machine check handler
To: freebsd-hackers@FreeBSD.ORG
Date: Wed, 18 Feb 1998 17:49:01 -0500 (EST)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hi all,

i'm working on freebsd 2.2.1 on pentium II pcs, and noticed 
that machine check is not enabled by the kernel. i checked 
3.0 current and found the same thing. my questions are:

- are there any benefits in enabling machine check? 
- the intel manuals seem to imply that the processor can't recover
  from a machine check exception. the current trap handler (trap.c)
  call trap_fatal if it encounters a machine check exception. besides
  logging the error events, is it reasonable to attempt a recovery?

thanks!
wee teck

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message