Re: unexpected machine check on 5.0 alpha

2003-01-16 Thread Mike Tibor 
On Thu, 16 Jan 2003, Trevor Johnson wrote:

 I just got a similar crash:

   unexpected machine check:

   mces= 0x1
   vector  = 0x670
   param   = 0xfc004e10
   pc  = 0xfc4069bc
   ra  = 0xfc4069b4
   curproc = 0xfc001f169200
   pid = 23, comm = intr: sym1


 I was sitting next to it when it crashed, and I would have noticed if the
 fans had stopped.  From earlier logs, I see that the temperature has
 varied between 21 and 27 Celsius.  I don't know what it is now, but it
 feels warmish when I'm wearing just a tee shirt.  There's a fan that
 constantly blows air into the room, which points toward the back of the
 computer.  Should I run the air conditioner more often?

I believe a 670 machine check can also result from a read of a
non-existent I/O space.  I'm not a programmer, but could that be the
problem here?

Mike


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: unexpected machine check on 5.0 alpha

2003-01-16 Thread Mike Tibor 
On Thu, 16 Jan 2003, Andrew Gallatin wrote:

(I wrote: )
   I believe a 670 machine check can also result from a read of a
   non-existent I/O space.  I'm not a programmer, but could that be the
   problem here?

 No, that's a 660. (system machine check).
 A 670 is much more likely to be bad ram, bad cache, bad CPU, etc.
 Its not always overheating.

Hmm... well, I got that from Jay Estabrook (works at DEC/Compaq/HP) via
the [EMAIL PROTECTED]  The archived message is here:

http://www.lib.uaa.alaska.edu/axp-list/archive/1998-12/0491.html

FWIW...

Mike


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message