All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	Judith Lebzelter <judith@linux-foundation.org>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aacraid: fails to initialize after a  kexec operation
Date: Mon, 23 Apr 2007 21:42:03 +0530	[thread overview]
Message-ID: <20070423161203.GA2129@in.ibm.com> (raw)
In-Reply-To: <AE4F746F2AECFC4DA4AADD66A1DFEF0188ADCE@otce2k301.adaptec.com>

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 NOT a mistake that the disable interrupt handler is used
> as the initial value of the enable interrupt platform function, it will
> be set up correctly once the adapter is discovered and initialized.
> 
> Please note that aacraid_kexec_5.patch contains this fix, since an
> earlier aacraid_kexec patch was applied to the tree and appears to have
> propagated, this is meant to supersede the earlier patch and bring it up
> to date with aacraid_kexec_5.patch, but expected to break when the
> aacraid_kexec_5.patch propagates... James, can you sort out this mess
> (either by stopping aacraid_kexec_5.patch, or by letting this enclosed
> patch move with some level of priority)?
> 
> ObligatoryDisclaimer: Please accept my condolences regarding Outlook's
> handling of patches.
> 
> This attached patch is against current scsi-misc-2.6. Also expect this
> patch can be applied to 2.6.21-rc6-mm1
> 
> Signed-off-by: Mark Salyzyn <aacraid@adaptec.com>
> 
> ---
> 

Thanks Mark,

I applied this patch but it still does not work. Now oops is gone but
I get following while aacraid is trying to initialize.

Adaptec aacraid driver (1.1-5[2437]-mh4)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25
aacraid: aac_fib_send: first asynchronous command timed out.
Usually a result of a PCI interrupt routing problem;
update mother board BIOS or consider utilizing one of
the SAFE mode kernel options (acpi, apic etc)
aac_fib_free, XferState != 0, fibptr = 0xffff810104140000, XferState = 0x810ad
ACPI: PCI interrupt for device 0000:01:02.0 disabled
aacraid: probe of 0000:01:02.0 failed with error -110


Thanks
Vivek


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	Judith Lebzelter <judith@linux-foundation.org>
Subject: Re: [PATCH] aacraid: fails to initialize after a  kexec operation
Date: Mon, 23 Apr 2007 21:42:03 +0530	[thread overview]
Message-ID: <20070423161203.GA2129@in.ibm.com> (raw)
In-Reply-To: <AE4F746F2AECFC4DA4AADD66A1DFEF0188ADCE@otce2k301.adaptec.com>

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 NOT a mistake that the disable interrupt handler is used
> as the initial value of the enable interrupt platform function, it will
> be set up correctly once the adapter is discovered and initialized.
> 
> Please note that aacraid_kexec_5.patch contains this fix, since an
> earlier aacraid_kexec patch was applied to the tree and appears to have
> propagated, this is meant to supersede the earlier patch and bring it up
> to date with aacraid_kexec_5.patch, but expected to break when the
> aacraid_kexec_5.patch propagates... James, can you sort out this mess
> (either by stopping aacraid_kexec_5.patch, or by letting this enclosed
> patch move with some level of priority)?
> 
> ObligatoryDisclaimer: Please accept my condolences regarding Outlook's
> handling of patches.
> 
> This attached patch is against current scsi-misc-2.6. Also expect this
> patch can be applied to 2.6.21-rc6-mm1
> 
> Signed-off-by: Mark Salyzyn <aacraid@adaptec.com>
> 
> ---
> 

Thanks Mark,

I applied this patch but it still does not work. Now oops is gone but
I get following while aacraid is trying to initialize.

Adaptec aacraid driver (1.1-5[2437]-mh4)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25
aacraid: aac_fib_send: first asynchronous command timed out.
Usually a result of a PCI interrupt routing problem;
update mother board BIOS or consider utilizing one of
the SAFE mode kernel options (acpi, apic etc)
aac_fib_free, XferState != 0, fibptr = 0xffff810104140000, XferState = 0x810ad
ACPI: PCI interrupt for device 0000:01:02.0 disabled
aacraid: probe of 0000:01:02.0 failed with error -110


Thanks
Vivek


  reply	other threads:[~2007-04-23 16:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23  7:49 AACRAID fails to initialize after an kexec operation Vivek Goyal
2007-04-23  7:49 ` Vivek Goyal
2007-04-23 13:01 ` Salyzyn, Mark
2007-04-23 13:01   ` Salyzyn, Mark
2007-04-23 13:38   ` [PATCH] aacraid: fails to initialize after a " Salyzyn, Mark
2007-04-23 13:38     ` Salyzyn, Mark
2007-04-23 16:12     ` Vivek Goyal [this message]
2007-04-23 16:12       ` Vivek Goyal
2007-04-23 17:20       ` Salyzyn, Mark
2007-04-23 17:20         ` Salyzyn, Mark
2007-04-24  8:44         ` Vivek Goyal
2007-04-24  8:44           ` Vivek Goyal
2007-04-24  9:01           ` Vivek Goyal
2007-04-24  9:01             ` Vivek Goyal
2007-04-24 13:21           ` Salyzyn, Mark
2007-04-24 13:21             ` Salyzyn, Mark
2007-04-30  9:53             ` Vivek Goyal
2007-04-30  9:53               ` Vivek Goyal
2007-04-30 14:11               ` Salyzyn, Mark
2007-04-30 14:11                 ` Salyzyn, Mark
2007-05-02  4:21                 ` Vivek Goyal
2007-05-02  4:21                   ` Vivek Goyal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070423161203.GA2129@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=judith@linux-foundation.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.