Tru64 Folks,
Thanks. I downgraded the firmware to 5.6 and things appear fine.
Hunter, Mark E [MarkE.Hunter_at_Energizer.com]:
Yes, We had the same problem. Upgrade to firmware 5.7-6. 5.7-4 was
"buggered" with regards to Mylex controllers.
Sutter Arnold [arnold.sutter_at_udt.ch]:
Do you have backplane RAID Controllers in there (DAC960, Mylex,
KZPAC, SWXCR) then you need FW 5.7-6.
Peter Reynolds [PReynolds_at_synstar.com]:
I know that this may sound odd, but have you run the ECU? I know that
systems running VMS are not too fussy about the configuration generated
by the ECU, but UNIX systems definitely are. Although you may not have
any EISA cards in the system, some functions are treated as pseudo EISA
devices, so I would recommend running V1.11 of the ECU and see if that
makes any difference.
Pulkkinen Miika [Miika.Pulkkinen_at_icl.fi]:
Funnily, I received corresponding output from an AS4000 after I had
upgraded to FW 5.7. The Compaq guy never found anything odd, but when
I downgraded to FW 5.5, the machine booted and the strange connotations
Dev_table_add: device Mylex DAC960 or bus PCI not found
Dev_table_add: device Mylex DAC1100 or bus PCI not found
Dev_table_add: device Mylex DAC1200 or bus PCI not found
disappeared.
Nikola Milutinovic [Nikola.Milutinovic_at_ev.co.yu]:
Perhaps OSTYPE is not OK?
>>> sh ostype
should give UNIX.
Dr. Tom Blinn, 603-884-0646 [tpb_at_doctor.zk3.dec.com]:
I have no idea what version of console firmware was certified with
V4.0D for the AlphaServer 4100, but you may have firmware that is
too new. And I have no idea what EISA configuration data you may
have for that system, but its altogether possible it's invalid (I
believe the AlphaServer 4100 does have an EISA bus).
If I were you, I'd want to make sure the firmware is the one that
shipped with V4.0D for that platform, and I'd want to run the ECU
under control of the firmware to make sure it's compatible.
If that doesn't work, my next step would be to check the revisions
of ALL the hardware options; sometimes OpenVMS supports something
that Tru64 UNIX (formerly Digital UNIX) does not, and vice versa,
and you might be stumbling on a hardware incompatibility.
John J. Francini [francini_at_zk3.dec.com]
I've seen this once in a while.
One thing to try: make sure the console variable "BOOT_RESET" is set
on, so that the system will always go through a full reset cycle when
booting or rebooting.
While this adds about a minute to every boot, it may help you get
around the problem.
-----Original Message-----
From: Surlow, Jim [mailto:surlow_at_lucent.com]
Sent: Wednesday, August 16, 2000 3:31 PM
To: 'tru64-unix-managers_at_ornl.gov'
Subject: DU4.0d/AS4100/firmware 5.7 - "!!! Console entry context is not va
lid - Reset the system !!!"
Tru64 folks,
I've just received an old AS4100 which had VMS on it. I've
installed DU 4.0d and tried to install the jumbo patch.
I have a console off the serial port. I have discovered that
the system won't reboot.
Upon reboot, I get
"!!! Console entry context is not valid - Reset the system !!!"
and then I have to power cycle the system.
I can halt the system and then boot from PROM, but I can't issue
a reboot from the OS.
I had first thought that it was kernel related and I've built
numerous kernels, but then discovered that I can power on the
system and it will boot the kernel in /vmunix.
I then thought that it was due to the error that I was getting
from the PROM upon boot, showing that the keyboard was not present.
I've attached a keyboard, to no avail (PROM value console shows
"serial" anyway).
I'm running version 5.7-4 of the firmware. I have to run 4.0d for the OS.
Any ideas as to how I can reboot?
Thanks,
Jim Surlow
Lucent Technologies
Some of the PROM detail shows below (I editted a bit).
syncing disks... done
rebooting.... (transferring to monitor)
halted CPU 1
CP - SAVE_TERM routine to be called
CP - SAVE_TERM exited with hlt_req = 1, r0 = 00000000.00000000
halted CPU 0
halt code = 5
HALT instruction executed
PC = fffffc000047b7d0
CPU 0 booting
(boot dra0.0.0.2.1 -flags A)
Dev_table_add: device Mylex DAC960 or bus PCI not found
Dev_table_add: device Mylex DAC1100 or bus PCI not found
Dev_table_add: device Mylex DAC1200 or bus PCI not found
Overlay name memadr topadr size ref
rawhide 1a000 71400 357376 0
advshell a4b00 abd00 29184 1
basiccmd 990e0 a4ae0 47616 1
advcmd abd20 bcf20 70144 1
environ 7c660 83e60 30720 1
phase3 948c0 990c0 18432 1
boot 13f840 14f040 63488 2
eeprom dd560 e2160 19456 100
pci 83e80 90680 51200 1
eisa 906a0 948a0 16896 1
ether e3160 e6f60 15872 1
scsi d3300 d8500 20992 1
fat d8b40 dd540 18944 100
dac960 71420 76020 19456 1
dv d0100 d2b00 10752 1
kbd ee940 f2f40 17920 1
vga bcf40 c1140 16896 1
dump of active call frames:
PC = 0006903C
PD = 0005E650 (IO_GET_WINDOW_BASE)
FP = 00137720
SP = 001375E0
R2 R3 R29 saved starting at 00137728
R2 = 00075410
[...]
halt code = 5
pcb 1
!!! Console entry context is not valid - Reset the system !!!
Brk 0 at 0006913C
0006913C ! BPT
Received on Thu Aug 17 2000 - 19:53:04 NZST