AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080501144955.0e46038b@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.keiffer@onstor.com>,<manohar.divate@onstor.com>,<may.ma@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E09B2B97C@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 1 May 2008 14:52:07 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "John Keiffer" <john.keiffer@onstor.com>
Cc: "Manohar Divate" <manohar.divate@onstor.com>, "May Ma"
 <may.ma@onstor.com>
Subject: Re: Defect  TED00023257 kernel oops while writing core file
Message-ID: <20080501145207.2689654d@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E09B2B97C@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E09B2B97C@onstor-exch02.onstor.net>
Organization: Onstor
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

Heh.  Don't forget TED00023192  ~:^)

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

> Manny/May,
> 
> I don't really know how to figure out which oops is which yet (in
> spite of Andy grilling me). ;-)
> 
> 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.
> 
> Thanks,
> John
> 
> -----Original Message-----
> From: andy.sharp@onstor.com [mailto:andy.sharp@onstor.com] 
> 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
> 
> Headline: kernel oops while writing core file
> id: TED00023257
> Note_Entry: 
> Dude, you have to get your kernel oopses correct!
> This is another example of
> 
> TED00023034 - kernel crash: DBE in yenta_irq during shutdown
> 
> 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.
> 
> Your clues are that at the top of the stack trace it says:
> 
> [<ffffffff8218afe4>] yenta_interrupt+0x14/0x118
> 
> and somewhere underneath that is a line similar to
> 
> [<ffffffff82195fdc>] mgmtbus_hard_start_xmit+0x11c/0x188
> 
> The actual numbers may change, but the function names,
> yenta_interrupt and mgmtbus_hard_start_xmit will stay the same.
> 
> 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
> 
