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:<Rich.LaReau@lsi.com>,<Brian.Stark@lsi.com>,<Caeli.Collins@lsi.com>,<Ed.Kwan@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	48CB2A5C4EED4E4BB7E555147EE4D8C1F6C681D5@cosmail03.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 17 Feb 2010 12:56:17 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: "LaReau, Rich" <Rich.LaReau@lsi.com>
Cc: "Stark, Brian" <Brian.Stark@lsi.com>, "Collins, Caeli"
 <Caeli.Collins@lsi.com>, "Kwan, Ed" <Ed.Kwan@lsi.com>
Subject: Re: 0.0 Crashes on Cougars
Message-ID: <20100217125617.77968821@ripper.onstor.net>
In-Reply-To: <48CB2A5C4EED4E4BB7E555147EE4D8C1F6C681D5@cosmail03.lsi.com>
References: <48CB2A5C4EED4E4BB7E555147EE4D8C1F6C6816A@cosmail03.lsi.com>
	<E1EC65251D4B3D46BBC0AAA3C0629222B23E84D1@cosmail02.lsi.com>
	<48CB2A5C4EED4E4BB7E555147EE4D8C1F6C681D5@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=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 17 Feb 2010 11:30:20 -0700 "LaReau, Rich" <Rich.LaReau@lsi.com>
wrote:

> Lancaster: 259909301, 4.0.2.8
> Sanger: 259908823, 4.0.2.9
> LSI: PA, Milpitas, cisnas, 4.0.2.6 - .10
> Mariner: 259951059, 4.0.2.5
> Onstor: mktg3 (?)
>=20
> SGI and Sanger have also recently reported txrx cores.  If this is
> related, might they shed some light?

Possibly.

> Rich
>=20
>=20
> From: Stark, Brian
> Sent: Wednesday, February 17, 2010 9:26 AM
> To: LaReau, Rich; Collins, Caeli; Sharp, Andy
> Subject: Re: 0.0 Crashes on Cougars
>=20
> Rich,
>=20
> We've been looking at it and believe the underlying cause is a TXRX
> crash based on the stack trace. The problem is we don't have any
> crashdump or core file and are now focusing on how to collect more
> info.
>=20
> Can you summarize the customers along with sw release?
>=20
>=20
> Brian
>=20
> ________________________________
> From: LaReau, Rich
> To: Stark, Brian; Collins, Caeli; Sharp, Andy
> Sent: Wed Feb 17 10:21:26 2010
> Subject: FW: 0.0 Crashes on Cougars
> Hi all-- just FYI, this is getting very hot very fast.  Multiple
> customers, including LSI, are seeing this Linux reboots on the
> Cougars.  Anything we can do to get this resolved ASAP would be
> helpful.
>=20
> Thanks,
>=20
> Rich
>=20
>=20
> From: Cook, Neil
> Sent: Wednesday, February 17, 2010 8:44 AM
> To: Kwan, Ed
> Cc: LaReau, Rich
> Subject: RE: 0.0 Crashes
> Importance: High
>=20
> Ed,
>=20
> Sanger have seen this same crash again today, is there anything
> further we can gather to get close to this issue? I=E2=80=99ve asked them=
 to
> go to 4.0.2.13 for another case but this was more to ensure they
> didn=E2=80=99t hit other bugs. This is going to become a hot issue for th=
em
> pretty quickly. We=E2=80=99ve also got Lancaster Uni seeing the same issue
> and I believe LSI have hit it as well. Can we up the priority on this
> one please?
>=20
> Regards,
>=20
> Neil Cook
> Technical Support Engineer
> ESG File Systems Support/ONStor
>=20
> LSI Logic Europe Ltd.
> Greenwood House, London Road
> Bracknell, Berkshire
> RG12 2UB
> United Kingdom
> T +44 (0) 1344 413265
> M +44 (0) 7887 685582
> F +44 (0) 1344 413288
> Neil.Cook@lsi.com<mailto:Neil.Cook@lsi.com>
> lsi.com<http://www.lsi.com/>
>=20
> From: Kwan, Ed
> Sent: 17 February 2010 06:37
> To: Cook, Neil
> Cc: LaReau, Rich
> Subject: RE: 0.0 Crashes
>=20
> The Linux crash is a hard problem and will take quite a bit of time
> and effort to solve, so don=E2=80=99t expect a resolution anytime soon. T=
ED
> 28063 is not escalated. I=E2=80=99ll ask my team to look at the rest.
>=20
>=20
> From: Cook, Neil
> Sent: Monday, February 15, 2010 9:46 AM
> To: LaReau, Rich; Kwan, Ed
> Subject: 0.0 Crashes
>=20
> Ed / Rich,
>=20
> There are a couple of 0.0 crashes in from different sites, Lancaster
> and Sanger, could these be looked at with some urgency please?
> Lancaster has two defects for crashes, one FP and one Linux. Sanger
> appears to have three. Lancs are on 4.0.2.6 which we will look to
> upgrade them from anyway and Sanger are on 4.0.2.9. The 0.0 crash is
> the one that both appear to have seen.
>=20
> Lancs 0.0 Crash:                28085
> Lancs FP Crash:                                 28061
> Sanger Crashes:                28063, 28064, 28076
>=20
> Regards,
>=20
> Neil Cook
> Technical Support Engineer
> ESG File Systems Support/ONStor
>=20
> LSI Logic Europe Ltd.
> Greenwood House, London Road
> Bracknell, Berkshire
> RG12 2UB
> United Kingdom
> T +44 (0) 1344 413265
> M +44 (0) 7887 685582
> F +44 (0) 1344 413288
> Neil.Cook@lsi.com<mailto:Neil.Cook@lsi.com>
> lsi.com<http://www.lsi.com/>
>=20
