X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8ABE3.AC0009F8@onstor-exch02.onstor.net>; Thu, 1 May 2008 16:32:51 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Defect  TED00023257 kernel oops while writing core file
Date: Thu, 1 May 2008 16:32:49 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09B2BB36@onstor-exch02.onstor.net>
In-Reply-To: <20080501145207.2689654d@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Defect  TED00023257 kernel oops while writing core file
Thread-Index: Acir1Zr56fECcrZ4QW6F8hLsXlYa2wADdC5A
References: <BB375AF679D4A34E9CA8DFA650E2B04E09B2B97C@onstor-exch02.onstor.net> <20080501145207.2689654d@ripper.onstor.net>
From: "Manohar Divate" <manohar.divate@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"John Keiffer" <john.keiffer@onstor.com>
Cc: "May Ma" <may.ma@onstor.com>

John

Listen to the wise man they will figure it out
and don't forget 23602

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, May 01, 2008 2:52 PM
To: John Keiffer
Cc: Manohar Divate; May Ma
Subject: Re: Defect TED00023257 kernel oops while writing core file

Heh.  Don't forget TED00023192  ~:^)

On Thu, 1 May 2008 11:11:36 -0700 "John Keiffer"
<john.keiffer@onstor.com> wrote:

> Manny/May,
>=20
> I don't really know how to figure out which oops is which yet (in
> spite of Andy grilling me). ;-)
>=20
> Please look at defects 23257 and 23034, and try and figure out if the
> oops you hit is the same as one of these, then update the defect.
>=20
> Thanks,
> John
>=20
> -----Original Message-----
> From: andy.sharp@onstor.com [mailto:andy.sharp@onstor.com]=20
> Sent: Wednesday, April 30, 2008 9:18 AM
> To: Andy Sharp; Tim Gardner; John Keiffer
> Cc: John Keiffer; Vikas Saini
> Subject: Defect TED00023257 kernel oops while writing core file
>=20
> Headline: kernel oops while writing core file
> id: TED00023257
> Note_Entry:=20
> Dude, you have to get your kernel oopses correct!
> This is another example of
>=20
> TED00023034 - kernel crash: DBE in yenta_irq during shutdown
>=20
> As far as I know no one has seen another example of
> this bug where we got a page fault while trying to write
> a core file.
>=20
> Your clues are that at the top of the stack trace it says:
>=20
> [<ffffffff8218afe4>] yenta_interrupt+0x14/0x118
>=20
> and somewhere underneath that is a line similar to
>=20
> [<ffffffff82195fdc>] mgmtbus_hard_start_xmit+0x11c/0x188
>=20
> The actual numbers may change, but the function names,
> yenta_interrupt and mgmtbus_hard_start_xmit will stay the same.
>=20
> State: Assigned
> history: 33747250	Apr  8 2008 11:40AM	jkeiffer
> Submit no_value	Opened
> 33747486	Apr  9 2008  2:06PM	timg	Assign
> Opened	Assigned 33747495	Apr  9 2008  2:22PM
> andrews	Modify	Assigned Assigned
> 33747537	Apr  9 2008  4:14PM	sandrineb
> Modify	Assigned Assigned
> 33748546	Apr 16 2008 11:12AM	jkeiffer
> Modify	Assigned Assigned
> 33749038	Apr 18 2008  3:07PM	andrews
> Modify	Assigned Assigned
> 33749827	Apr 25 2008  9:31AM	jkeiffer
> Modify	Assigned Assigned
> 33750276	Apr 30 2008  7:20AM	jkeiffer
> Modify	Assigned Assigned
> 33750286	04/30/2008 09:17:38 AM	andrews
> Modify	Assigned Assigned
>=20
