[Info-vax] Changed Boot behavior on XP1000 since 2013

[Phillip Helbig---undress to reply]

In article <kdj504$3jf$1 at speranza.aioe.org>, Joukj
<joukj at hrem.nano.tudelft.nl> writes: 

> > Since 2013 all machines booting up from "Power off" or after doing
> > ">>> INIT" on the boot prompt stop booting and ask for the system time
> > DD-MMM-YYYY MM:HH. IF you set the time back to 2012 they boot until
> > login normally. All XP1000 boot normally too if power wasn't off or if
> > no >>> INIT was given on the boot prompt.
> > 
> > Only XP1000 are infected, our DS10 and some other alphas boot as
> > expected.
> > 
> > You can force the machines to boot through with another TIMEPROMPTWAIT
> > value, but than the system time will be inaccurate (time of last boot
> > or of last $SET TIME).
> > 
> > It seems that any time from 2013 on is an invalid time for the
> > processors time-of-year clock and this clock becomes important after
> > "power off" or >>>INIT.
> I see the same on some of my alpha's since 1-JAN-2013.
> Definitely one of my XP1000 does it (on the other 2 I have not seen it 
> yet, but I did not do a power-cycle on those, only a "reset" by pressing 
> the button).
> I see the same on a DPWS500au and a AlphaServer 2000 4/200, but not on 
> the boot-member of my cluster, a DPWS600au (I even power-cycled this 
> machine)

I noticed my ALPHAstation 500/500 satellite booted slowly (I normally 
boot it without the console).  It's not the first boot this year, but 
then I tend to switch it on and come back a bit later.  Maybe it is 
waiting for the time then continuing after timing out.

> When I mentioned this to HP-support, they blamed the battery. I have not 
> had time to replace them to see if they are right. But I'm still 
> wondering why 3 systems failed on this point at the same time (since 
> 1-jan-2013).

Someone here mentioned the changed behaviour even though the battery was 
good.