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. > > As you can see below, it's doing the machine check at almost the same point > as last year. In combing the archives, it seems that there were problems > with some cards, so I yanked out all the pci cards (there were no EISA > cards), still a machine check. > > This machine booted and ran stable under 4-xx with a uniprocessor kernel > > It seems you may have to disable the machine checks in order to get this > beast to boot, any pointers on where to start? > I'd like to play with it with FBSD before going back to VMS. > > Below is the console firmware pre-boot diag and then the actual boot -v > output and then the show config and show fru. > > Cheers > > Tom > > > eisab0: <PCI-EISA bridge> at device 2.0 on pci0 > > 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. -- B.Walter BWCT http://www.bwct.de ticso_at_bwct.de info_at_bwct.deReceived on Sun Jan 25 2004 - 02:51:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:39 UTC