Re: Same problem, new year 2100A machine check

From: Wilko Bulte <wkb_at_freebie.xs4all.nl>
Date: Sun, 25 Jan 2004 12:57:41 +0100
On Sun, Jan 25, 2004 at 12:51:12PM +0100, Bernd Walter wrote:
> On Fri, Jan 23, 2004 at 05:06:14PM -0700, Tom Ponsford wrote:
> > I decided to replace a disk on the ol' 2100A. I had been running VMS on it 
> > without any troubles, until a disk started giving me errors. After 
> > replacing the disk, I decided to give 5.2 a go, thinking maybe some of the 
> > problems of last year may have been resolved.
> > 
> > No such luck.

...

> > unexpected machine check:
> > 
> >     mces    = 0x1
> >     vector  = 0x670
> >     param   = 0xfffffc0000006000
> >     pc      = 0xfffffc00003b48d4
> >     ra      = 0xfffffc00003b4908
> >     curproc = 0xfffffc0000810ee0
> >         pid = 0, comm = swapper
> > 
> > panic: machine check
> > cpuid = 0;
> > Uptime: 1s
> > Automatic reboot in 15 seconds - press a key on the console to abort
> 
> Maybe there is something wrong with the EISA configuration on your
> machine.

Hmm, could be. But 2100[a] are not really well supported/tested..

-- 
Wilko Bulte				wilko_at_FreeBSD.org
Received on Sun Jan 25 2004 - 02:57:51 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:39 UTC