AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Ed.Kwan@lsi.com>,<brian.stark@lsi.com>,<bill.fisher@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	2B044E14371DA244B71F8BF2514563F504212093@cosmail03.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 9 Dec 2009 15:51:13 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Kwan, Ed" <Ed.Kwan@lsi.com>
Cc: Brian Stark <brian.stark@lsi.com>, Bill Fisher <bill.fisher@lsi.com>
Subject: Re: TED 27548 Case 13462 - LSI Logic - Linux crash on Cougar at
 4.0.2.6
Message-ID: <20091209155113.070f20b8@ripper.onstor.net>
In-Reply-To: <2B044E14371DA244B71F8BF2514563F504212093@cosmail03.lsi.com>
References: <2B044E14371DA244B71F8BF2514563F504212093@cosmail03.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 9 Dec 2009 11:33:55 -0700 "Kwan, Ed" <Ed.Kwan@lsi.com> wrote:

> Hi Andy & Rendell,
> 
> What's the next step for this defect?

Mark it as limbo?

I'm not sure what we can do.  Possibly Bill has some ideas as he knows
a thing or two about the mgmt bus.  Maybe we can print out the bogus
address in question or something.  Not sure if anyone would be able to
do anything with that or not.  Maybe we can put a long sleep in there
which possibly would allow the TXRX to dump core if it's crashing.  If
it's just "off in the weeds" that wouldn't do anything except delay a
failover.

If there's a bug in the Linux kernel mgmtbus driver, possibly Bill can
spot it with some code inspection.  I'm hesitant to ask him to do that
unless you think this is hot enough.  Truth is, this was back in Oct.,
all it did was cause the vsvrs to fail over, do I have that correct?  I
know they want explanations, but we have to trim expectations some if
they really require testimony for each and every imperfection in the
product.