| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Hi,
A customer have two identical AlphaServer 1000A 5/300 running DU V3.2G (Rev. 62)
and also, but probably not involved here, DCE 1.3b.
At shutdown the TOY-clock is changed
Set the date at console-prompt and then follow the procedure:
boot -fl s
date ......
mount -u /
sync
sync
halt
Then the TOY-clock is changed and the most obvious is that the year is usually
set to 2018.
From /var/adm/messages
Feb 21 09:29:23 f227a vmunix: WARNING: lost battery backup clock -- CHECK AND RE
SET THE DATE!
I would guess this is a HW/SRM problem but a HW-engineer has been working on
this, replacing every part that he felt was involved. He has also tried an
older firmware. He has come to the conclusion that this must be SW problem.
Just can't figure out how. I have search COMET/Notes and have found this
problem described but I have not seen any solution.
Can anyone give me an explanation to how this works and if this is HW or
SW related. The customer can't have the system coming up with wrong year
every time he reboots. Also, the system comes up with the clock set to the
time when the system went down. Read from disk?
I have also posted this in WRKSYS::MIKASA conference, note 847.0.
Regards,
Mikael Bringh
Unix-group, TSC, Sweden
Included, uerf -R -r 300 from both systems.
********************************* ENTRY 1. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 300. SYSTEM STARTUP
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Feb 21 09:29:21 1997
OCCURRED ON SYSTEM f227a
SYSTEM ID x0005001B
SYSTYPE x00000000
MESSAGE PCXAL keyboard, language English
_(American)
Alpha boot: available memory from
_0x9f8000 to 0xbfee000
Digital UNIX V3.2G (Rev. 62); Fri Jan
_31 09:08:35 MET 1997
physical memory = 192.00 megabytes.
available memory = 181.97 megabytes.
using 730 buffers containing 5.70
_megabytes of memory
Firmware revision: 4.7
PALcode: OSF version 1.21
AlphaServer 1000A 5/300
Mem_size = 199376896, consmem = 238
pci0 at nexus
eisa0 at pci0
ace0 at eisa0
ace1 at eisa0
lp0 at eisa0
fdi0 at eisa0
fd0 at fdi0 unit 0
vga0 at eisa0
640x480 (Cirrus )
vga0: Cirrus Logic CL-GD5429 (SVGA)
_512 Kbytes
pci2000 at pci0 slot 8
isp0 at pci2000 slot 0
isp0: QLOGIC ISP1020A
isp0: Firmware revision 2.10 (loaded
_by console)
scsi0 at isp0 slot 0
rz4 at scsi0 bus 0 target 4 lun 0 (DEC
_ RRD45 (C) DEC 0436)
tz5 at scsi0 bus 0 target 5 lun 0 (DEC
_ TLZ09 (C)DEC 0165)
tu0: DECchip 21140-AA: Revision: 1.2
tu0 at pci0 slot 11
tu0: DEC Fast Ethernet Interface,
_hardware address: 00-00-F8-30-E8-C8
tu0: console mode: selecting 10BaseT
_(UTP) port: half duplex
pza0 at pci0 slot 12
pza0 firmware version: DEC P01 A10
_
scsi1 at pza0 slot 0
rz9 at scsi1 bus 1 target 1 lun 0 (DEC
_ RZ28D (C) DEC 0010)
rz10 at scsi1 bus 1 target 2 lun 0
_(DEC RZ28D (C) DEC 0010)
rz11 at scsi1 bus 1 target 3 lun 0
_(DEC RZ28D (C) DEC 0010)
rz12 at scsi1 bus 1 target 4 lun 0
_(DEC RZ28D (C) DEC 0010)
rz13 at scsi1 bus 1 target 5 lun 0
_(DEC RZ28D (C) DEC 0010)
psiop0 at pci0 slot 13
Loading SIOP: script c000b200, reg
_82211000, data 406271b8
scsi2 at psiop0 slot 0
gpc0 at eisa0
dli: configured
********************************* ENTRY 1. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 300. SYSTEM STARTUP
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Feb 21 09:05:25 1997
OCCURRED ON SYSTEM f227b
SYSTEM ID x0005001B
SYSTYPE x00000000
MESSAGE PCXAL keyboard, language English
_(American)
Alpha boot: available memory from
_0xa76000 to 0xbffe000
Digital UNIX V3.2G (Rev. 62); Tue Feb
_11 12:45:52 MET 1997
physical memory = 192.00 megabytes.
available memory = 181.67 megabytes.
using 730 buffers containing 5.70
_megabytes of memory
Firmware revision: 4.6
PALcode: OSF version 1.21
AlphaServer 1000A 5/300
Mem_size = 199393280, consmem = 236
pci0 at nexus
eisa0 at pci0
ace0 at eisa0
ace1 at eisa0
lp0 at eisa0
fdi0 at eisa0
vga0 at eisa0
640x480 (Cirrus )
vga0: Cirrus Logic CL-GD5429 (SVGA)
_512 Kbytes
pci2000 at pci0 slot 8
isp0 at pci2000 slot 0
isp0: QLOGIC ISP1020A
isp0: Firmware revision 2.10 (loaded
_by console)
scsi0 at isp0 slot 0
rz4 at scsi0 bus 0 target 4 lun 0 (DEC
_ RRD45 (C) DEC 0436)
tu0: DECchip 21140-AA: Revision: 1.2
tu0 at pci0 slot 11
tu0: DEC Fast Ethernet Interface,
_hardware address: 00-00-F8-30-EA-91
tu0: console mode: selecting 10BaseT
_(UTP) port: half duplex
pza0 at pci0 slot 12
pza0 firmware version: DEC P01 A10
_
scsi1 at pza0 slot 0
rz9 at scsi1 bus 1 target 1 lun 0 (DEC
_ RZ28D (C) DEC 0010)
rz10 at scsi1 bus 1 target 2 lun 0
_(DEC RZ28D (C) DEC 0010)
rz11 at scsi1 bus 1 target 3 lun 0
_(DEC RZ28D (C) DEC 0010)
rz12 at scsi1 bus 1 target 4 lun 0
_(DEC RZ28D (C) DEC 0010)
rz13 at scsi1 bus 1 target 5 lun 0
_(DEC RZ28D (C) DEC 0010)
psiop0 at pci0 slot 13
Loading SIOP: script c000b700, reg
_82211000, data 406276b8
scsi2 at psiop0 slot 0
tz21 at scsi2 bus 2 target 5 lun 0
_(DEC TLZ7 (C)DEC 4BQE)
gpc0 at eisa0
dli: configured
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 8939.1 | Console time vs UNIX time | SMURF::EVERS | Tue Feb 25 1997 12:03 | 10 | |
Time should only be set while running Digital UNIX. The value of time
stored in the battery backed up time of year clock is not interpretted
consistently between Digital UNIX and the console. The root of the
inconsistency is that the console stores time in local time while
Digital UNIX stores time in GMT time. The years are stored
differently on purpose as a method to detect that the time value in the
time of year clock was not stored by Digital UNIX. This is what
happened in this case.
| |||||
| 8939.2 | Date changed on shutdown, HW or SW?, ASRV1000A, DU v3.2G | RULLE::BRINGH | Wed Feb 26 1997 11:02 | 45 | |
Hi, and thanks for the answer. If we do a date from unix then the time, date and year are correct. Then we do a shutdown and date from console prompt gives us that the clock is one hour off, which is ok because we are using the MET timezone, but the year is 2018. If we then set the correct time, it does not matter if we set it one hour off or not, with >>> date 199702261200.00 and boot. We always get the error message Feb 21 09:29:23 f227a vmunix: WARNING: lost battery backup clock -- CHECK AND RE SET THE DATE! The motherboard is replaced once and the clock was right when it was powered up for the first time, therefor the battery seems ok. I have done some testing on my AS400 4/233 which is running DU v4.0B on one disk and v3.2D-1 on another disk. If my system is up and running with the correct time, date and year, and I shut it down. Then the date at console prompt is one hour off and the year is 2045. The difference is that, whether I set the correct time (year) or not, my system has no problems booting up. The interresting thing is that if I boot v3.2D instead and immediatelly shutdown console date still says 2045. But if I set date in v3.2D in singel user mode , mount -u / and sync;sync;halt, then the console date shows the correct year. And if I then boot v4.0B, I get a similar but different error message. Feb 26 13:29:32 truxxx vmunix: over 5 years since last boot - CHECK AND RESET TH E DATE To me, this looks like something has changed in DigitalUNIX and that the ASRV1000 has a problem with it and that the problem is actually in the startup not in the shutdown. And os_type is set to UNIX, has to be in order to handle powercycles. I also post this reply in WRKSYS::MIKASA conference, note 847. Regards, Mikael Bringh Unix-group, TSC, Sweden | |||||
| 8939.3 | console time not consistent w/ Digital UNIX time | SMURF::EVERS | Mon Mar 03 1997 10:44 | 27 | |
Console time has never been consistent with Digital UNIX time that I am
aware of.
Digital UNIX 3.2g changed the way the battery backed up clock worked on
all systems. While switching between pre 3.2g and 3.2g or later, time
will not be consistent. This is normally a one time change and should
be detailed in the 3.2g release notes. It is definitely detailed in
the 4.0 release notes.
Try this:
1) Boot the system
2) Set the time
3) Shutdown the system
4) power-down the system
5) power-up the system
6) boot
While the system boots, you shouldn't see any messages indicating
time is not set correctly. Time should also be correct after UNIX
boots.
Do not set time at the console or you will corrupt the time value that
Digital UNIX uses, and time will be set to the previous shutdown time
stamp.
| |||||
| 8939.4 | Solved: lost battery backup clock | NETRIX::"[email protected]" | Mikael Bringh, Unix-support, TSC, Sweden | Wed Apr 02 1997 05:04 | 14 |
It turned out that the error message Feb 21 09:29:23 f227a vmunix: WARNING: lost battery backup clock -- CHECK AND RESET THE DATE! came from a patched clock.o for v3.2D-1 that was not intended for v3.2G. The customer removed it and the system rebooted without the error message and without reading time from disk. /Mikael Bringh [Posted by WWW Notes gateway] | |||||