X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C874B4.61EFE458@onstor-exch02.onstor.net>; Thu, 21 Feb 2008 11:05:46 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C874B4.61EFE458"
Content-class: urn:content-classes:message
Subject: RE: mailbox failures are back with Sub9 opt (gone and closed in Sub8)
Date: Thu, 21 Feb 2008 11:05:46 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E018AE84D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: mailbox failures are back with Sub9 opt (gone and closed in Sub8)
Thread-Index: Ach0njNTIkepNOcbReCZmo0qFLiW1AAAxajbAAQSUDI=
References: <BB375AF679D4A34E9CA8DFA650E2B04E0875E64B@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E04228ED2@onstor-exch02.onstor.net>
From: "Jeff Miller" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=JEFF+2EMILLER@onstor.com>
To: "Raj Kumar" <raj.kumar@onstor.com>,
	"John Keiffer" <john.keiffer@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>
Cc: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C874B4.61EFE458
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This mailbox failure, 'mbox in 0-7: 0031', is different from the other =
(mbox in 0-7: 006b).  The 31 is a command to the Qlogic chip telling it =
to read the EEPROM on the SFP.  Probably it is a bad SFP.  The code =
won't try to read the SFP data if there is no SFP.  The code tries to =
read the SFP as part of enabling the link and it will retry every few =
seconds.  Perhaps the code should be changed to just put out one message =
(and an elog entry) rather than on every failure.  Most of the info in =
the SFP prom is just useful for debugging but there is also a field that =
indicates the link speed that is is capable of, so we can avoid trying =
to 2G SFPs for 4G links.  There is a fcadmin command to display the SFP =
data.

There isn't any other error associated with this is there?
Jeff


-----Original Message-----
From: Raj Kumar
Sent: Thu 2/21/2008 7:49 AM
To: John Keiffer; Vikas Saini; Jeff Miller
Cc: Sandrine Boulanger
Subject: RE: mailbox failures are back with Sub9 opt (gone and closed in =
Sub8)
=20
New.

________________________________

From: John Keiffer
Sent: Thu 2/21/2008 7:26 AM
To: Vikas Saini; Jeff Miller
Cc: Raj Kumar; Sandrine Boulanger
Subject: mailbox failures are back with Sub9 opt (gone and closed in =
Sub8)



I closed 21860 in Sub8. Now the issue is back. Should I file a new =
defect or reopen this one?

=20

Because now with Sub9 opt build I see these tons of these again.

=20

Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: Mailbox failure:

Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: mbox in 0-7: 0031 00a0 =
e250 680c 0900 9de5 0000 0051

Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: mbox in 8-9: 0040 0000

Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: mbox out 0-2: 4005 00a0

Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: HCCR 0x0, ISR 0x8, =
H_TO_R_HiLow 0x40058011

Feb 21 06:25:08 g6r10 kernel: fp2:     REQ_IN 0x0, REQ_OUT 0x0, RESP_IN =
0x0, RESP_OUT 0x0

Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: ispfc_init_adap_1: Port =
2 Could not read SFP data

=20

Thank you,

John Keiffer

=20

=20




------_=_NextPart_001_01C874B4.61EFE458
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: mailbox failures are back with Sub9 opt (gone and closed in =
Sub8)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>This mailbox failure, 'mbox in 0-7: 0031', is =
different from the other (mbox in 0-7: 006b).&nbsp; The 31 is a command =
to the Qlogic chip telling it to read the EEPROM on the SFP.&nbsp; =
Probably it is a bad SFP.&nbsp; The code won't try to read the SFP data =
if there is no SFP.&nbsp; The code tries to read the SFP as part of =
enabling the link and it will retry every few seconds.&nbsp; Perhaps the =
code should be changed to just put out one message (and an elog entry) =
rather than on every failure.&nbsp; Most of the info in the SFP prom is =
just useful for debugging but there is also a field that indicates the =
link speed that is is capable of, so we can avoid trying to 2G SFPs for =
4G links.&nbsp; There is a fcadmin command to display the SFP data.<BR>
<BR>
There isn't any other error associated with this is there?<BR>
Jeff<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Raj Kumar<BR>
Sent: Thu 2/21/2008 7:49 AM<BR>
To: John Keiffer; Vikas Saini; Jeff Miller<BR>
Cc: Sandrine Boulanger<BR>
Subject: RE: mailbox failures are back with Sub9 opt (gone and closed in =
Sub8)<BR>
<BR>
New.<BR>
<BR>
________________________________<BR>
<BR>
From: John Keiffer<BR>
Sent: Thu 2/21/2008 7:26 AM<BR>
To: Vikas Saini; Jeff Miller<BR>
Cc: Raj Kumar; Sandrine Boulanger<BR>
Subject: mailbox failures are back with Sub9 opt (gone and closed in =
Sub8)<BR>
<BR>
<BR>
<BR>
I closed 21860 in Sub8. Now the issue is back. Should I file a new =
defect or reopen this one?<BR>
<BR>
<BR>
<BR>
Because now with Sub9 opt build I see these tons of these again.<BR>
<BR>
<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: Mailbox failure:<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: mbox in 0-7: 0031 00a0 =
e250 680c 0900 9de5 0000 0051<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: mbox in 8-9: 0040 =
0000<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: mbox out 0-2: 4005 =
00a0<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: HCCR 0x0, ISR 0x8, =
H_TO_R_HiLow 0x40058011<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2:&nbsp;&nbsp;&nbsp;&nbsp; REQ_IN 0x0, =
REQ_OUT 0x0, RESP_IN 0x0, RESP_OUT 0x0<BR>
<BR>
Feb 21 06:25:08 g6r10 kernel: fp2: ispfc:sp1.2: ispfc_init_adap_1: Port =
2 Could not read SFP data<BR>
<BR>
<BR>
<BR>
Thank you,<BR>
<BR>
John Keiffer<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C874B4.61EFE458--
