[fm-discuss] many fmd errors on T2000

[Gavin Maltby]

On 06/20/06 20:27, Robert Milkowski wrote:

> GM> All those ereports should have resulted in some diagnosis.  What does
> GM> 'fmadm faulty' report, and what does 'fmdump -v' show?
> 
> 
> bash-3.00# fmadm faulty
>    STATE RESOURCE / UUID
> -------- ----------------------------------------------------------------------
> bash-3.00# fmdump -v
> TIME                 UUID                                 SUNW-MSG-ID
> fmdump: /var/fm/fmd/fltlog is empty
> bash-3.00#

Some closer inspection of

http://cvs.opensolaris.org/source/xref/on/usr/src/cmd/fm/eversholt/files/sparc/sun4/fire.esc

shows that there is no currently no attempt to diagnose fabric faults in the
fire diagnosis rules.  For the reports you have seen:

/*
  * For logging purpose only.
  * The Fire nexus driver generates equivalent pciex ereports for the
  * common pciex rules to diagnose.
  */
prop error.io.fire.pec.fabric_error at hostbridge/pciexrc(0) ->
     ...
     ereport.io.fire.pec.re at hostbridge/pciexrc,
     ...
     ereport.io.fire.pec.btp at hostbridge/pciexrc,
     ...;

/*
  * Upset used to hide ereports that are not currently diagnosed.
  */
event upset.io.fire.nodiag at hostbridge;

prop upset.io.fire.nodiag at hostbridge (0)->
     ....
     error.io.fire.pec.fabric_error at hostbridge/pciexrc,
     ....;

So I was wrong - no diagnosis was expected here.

Gavin

-- 
Gavin Maltby, Solaris Kernel Development.