Hi, all.
I have a corrupted FRU entry since when I bought a ES40 with one EV67 CPU.
The local Compaq said that it's not something to be worried, since it
affects only the error logging.
And it does!
Just after *each* reboot I have a very long dump of FRU table!
Here it is (at least the beginning.)
**** V3.2 ********************** ENTRY 4 ***********************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 0.
Timestamp of occurrence 22-NOV-2000 14:13:15
Host name ax2hermes
System type register x00000022 Systype 34. (Regatta Family)
Number of CPUs (mpnum) x00000001
CPU logging event (mperr) x00000000
Event validity 1. O/S claims event is valid
Event severity 5. Low Priority
Entry type 110. Generalized Machine State Type
3. - (minor class)
SWI Minor class 3. System configuration
FRU Rev50 Enable Flag x00000001
******************** FRU Table Header ******************
And a loooong dump follows..
Moreover, the daemon.log file has en entry...
**ERROR svrsys_fru_parse.c line 1264: FRU Table TLV tag of 0 is not
ISOLATIN1
last message repeated 3 times
...just after the boot.
I'm sick and tired of this things. How can I fix the FRU table ? There is
a command in console mode, but it seems that I have to give some info with
it... What info?
The corrupted FRU entry looks like this:
SMB0.CPB0.SBM0 00 ?????????????????? ffffffff ffff ff
and it's the last one in the table.
Thank you.
Ermanno Polli
ermanno.polli_at_lnf.infn.it
Received on Fri Nov 24 2000 - 10:20:26 NZDT