[pca] patch issue

[Bliss, Kevin L]

I opened a case with Sun, the engineer opened a bug, they found that the bug was a duplicate so closed the new one.  The fix is supposedly complete but won't be available until Sol 10 update 9 (which I thought was available).  In case you are interested the bug is CR6797442.  Not as much detail as you received in your ticket but neither is complete.  

-----Original Message-----
From: pca-bounces at lists.univie.ac.at [mailto:pca-bounces at lists.univie.ac.at] On Behalf Of Hannu Kivimäki
Sent: Tuesday, November 03, 2009 6:23 AM
To: pca at lists.univie.ac.at
Subject: Re: [pca] patch issue

Hi,

On Thu, 2009-10-22 at 11:09 -0700, Bliss, Kevin L wrote:
> This is not a pca issue but may be helpful to those on the list.  A
> recent Solaris 10 patch has created a "compatibility" issue with fmd
> which causes it to log 10+ errors per second to /var/fm/fmd/errlog.  I
> only noticed because one of the systems patched was running low on
> space.  I opened a case with Sun yesterday morning but so far have not
> received any useful information, including which patch caused the
> problem.  The system is the following error being logged several times a
> second:
> 
> Oct 21 2009 12:35:09.061332556 ereport.io.ddi.fm-capability
> nvlist version: 0
>         class = ereport.io.ddi.fm-capability
>         ena = 0x2196595e6b07001
>         detector = (embedded nvlist)
>         nvlist version: 0
>                 version = 0x0
>                 scheme = dev
>                 device-path = /
>         (end detector)
> 
>         dvr-name = fp
>         __ttl = 0x1
>         __tod = 0x4adf626d 0x3a7dc4c

A quick note about this older topic - I patched some servers yesterday
and
noticed /var/fm/fmd/errlog getting filled with
ereport.io.ddi.fm-capability
messages (500+ MB of them overnight). Contacted Sun Support and they
told
me to back out Emulex patch 141876-05. FMA support was introduced in
141876-03 and apparently something broke it already in 141876-05.

We never had any revisions of 141876 installed before, so after
removing 141876-05, we are now back to Emulex patch 139608-05 with
no fmd issues. I guess we have to wait for 141876-06 before trying
patching Emulex HBA drivers again.


Hannu