[Summary-partial] FRU error

From: Ermanno Polli <Ermanno.Polli_at_lnf.infn.it>
Date: Thu, 07 Dec 2000 13:18:31 +0100 (MET)

First the usual THANK YOU to those who answered my request:

Jem Treadwell
Lavelle, Bryan
Colin Walters
alan_at_nabeth.cxo.dec.com

I'm sorry for the delay in making this summary, but the problem is not
fixed, yet. I've been waiting, but I had no answer since a week, so I'm
posting a partial summary.

It turned out that my problem is a two-faced one.
Fisrt: the error log.

Jem Treadwell said:

> Hi, the DECevent group development group gave me this information:
>
> The basic problem is that DECevent does not support the
> Regatta (ES40) FRU Table at all -- thus the unrecognized header and
> subsequent DUMP.
>
> There is a more general, application problem here, in that, DECevent
> does not support and should not be used to interpret/analyze any ES40
> or other Regatta platform error logs. They should be using WEBES/Compaq
> Analyze V3.1 or higher. They also need to be sure that all required OS
> and Console upgrades are installed when using WEBES/CA (see the WEBES
> user's Guide).
>
> Your local support office should be able to help if you need more
> information
> about WEBES/Compaq Analyze.

There were some summaries along this line recently..

I replyed telling him I didn't want to use Compaq Analyze because of the
not-so-good reports I read some time ago in this list.
Moreover I saw, in the product CD that came along with 5.0A, no
documentation about WEBES (2.1, BTW) except some web pages that had
"Windows 2000" as its header.
Really fancy, having a unix product announce itself as a Windows program
:-(
I discarded installing it just for this..
BTW. I have a Mac and it was impossible for me to use the web pages...
They asked
for a beeootiful ;-) search.exe that was along with the html files. :-(
I complained in my answer to Jem, about having non unix stuff along with
the unix programs.
I know... PC's are everywhere... most of us use them as a remote station
to our unixes, and so on.
Ok, this is the trend, but not all the world is WindowsSomething. Apple
is a pc, (lowercase intended), right?
It's not widespread, but it is on the pc market as a good second runner.
Why letting it out?

O well.. I got carried away. I was talking as a long time Mac user.
Anyway those were the lines of my answer to Compaq. Jem told me he
passed my comments on.

Second: the FRU error itself.

This one is not solved yet.
Bryan Lavelle tried to help me, suggested to upgrade the firmware, but
I'm at the latest release (5.8); talked about the ECU utility, but the
ES40 has no EISA bus. Eventually all he could do was to ask for help
("I'll try to verify", he said).
I'm still waiting..

Original post follows.

> 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 Thu Dec 07 2000 - 12:19:44 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT