Re: [PATCH] aacraid: fails to initialize after a kexec operation

2007-05-01 Thread Vivek Goyal
On Mon, Apr 30, 2007 at 10:11:03AM -0400, Salyzyn, Mark wrote: > Foreign arrays are arrays configured on another adapter then moved over > to the current host adapter. I do not know why this may be the case in > your situation, but it had the smell of behaving like a foreign array > and thus my sug

RE: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-30 Thread Salyzyn, Mark
-- Mark Salyzyn > -Original Message- > From: Vivek Goyal [mailto:[EMAIL PROTECTED] > Sent: Monday, April 30, 2007 5:54 AM > To: Salyzyn, Mark > Cc: James Bottomley; Kexec Mailing List; Judith Lebzelter; > linux-scsi@vger.kernel.org; Darrick J. Wong > Subject: Re: [PATCH]

Re: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-30 Thread Vivek Goyal
On Tue, Apr 24, 2007 at 09:21:35AM -0400, Salyzyn, Mark wrote: > The system BIOS sets up the card's PCI configuration and there is code > in the kernel that is capable of picking up some of the BIOS' > information from the BIOS Data Space (not sure if it is actively > collected in your configuratio

RE: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-24 Thread Salyzyn, Mark
> linux-scsi@vger.kernel.org > Subject: Re: [PATCH] aacraid: fails to initialize after a > kexec operation > > > On Mon, Apr 23, 2007 at 01:20:32PM -0400, Salyzyn, Mark wrote: > > That is a failure to route the interrupts and is possibly > an issue with > >

Re: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-24 Thread Vivek Goyal
On Tue, Apr 24, 2007 at 02:14:44PM +0530, Vivek Goyal wrote: > > In second attempt, it mounted the file system but it found some issue > with "resize" inode and asked me to run fsck manually. Which in turn > deleted whole lot of inodes. > > In third attemt it panics later when it finds ext3 to b

Re: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-24 Thread Vivek Goyal
On Mon, Apr 23, 2007 at 01:20:32PM -0400, Salyzyn, Mark wrote: > That is a failure to route the interrupts and is possibly an issue with > the kernel and the hardware, and not the driver directly (since there is > an expectation that request_irq will connect the interrupt to the > interrupt service

RE: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-23 Thread Salyzyn, Mark
nal Message- > From: Vivek Goyal [mailto:[EMAIL PROTECTED] > Sent: Monday, April 23, 2007 12:12 PM > To: Salyzyn, Mark > Cc: linux-scsi@vger.kernel.org; James Bottomley; Kexec > Mailing List; Judith Lebzelter > Subject: Re: [PATCH] aacraid: fails to initialize after a > ke

Re: [PATCH] aacraid: fails to initialize after a kexec operation

2007-04-23 Thread Vivek Goyal
On Mon, Apr 23, 2007 at 09:38:43AM -0400, Salyzyn, Mark wrote: > Missing portion of the kexec changes to the aacraid driver. The platform > functions were not initialized when the restart function is activated > resulting in a panic when these platform functions are called. Please > note that it is

[PATCH] aacraid: fails to initialize after a kexec operation

2007-04-23 Thread Salyzyn, Mark
Missing portion of the kexec changes to the aacraid driver. The platform functions were not initialized when the restart function is activated resulting in a panic when these platform functions are called. Please note that it is NOT a mistake that the disable interrupt handler is used as the initia