public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Vivek Goyal <vgoyal@in.ibm.com>,
	James.Bottomley@SteelEye.com, Eric.Moore@lsil.com,
	bharata@in.ibm.com, Roy.Wade@lsil.com, Jared.Hayes@lsil.com,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [IBM] RE: [BUG] Fusion MPT Base Driver initialization failure wit h kdum p
Date: Tue, 26 Jul 2005 16:33:11 +0530	[thread overview]
Message-ID: <20050726110311.GC4047@in.ibm.com> (raw)
In-Reply-To: <20050725151033.25196965.akpm@osdl.org>

On Mon, Jul 25, 2005 at 03:10:33PM -0700, Andrew Morton wrote:
> Vivek Goyal <vgoyal@in.ibm.com> wrote:
> >
> > > If you don't stop the DMA engines before you boot the new kernel, the
> >  > addresses they have to send data to will now be random points in that
> >  > kernel's memory, leading to potential corruption of the new kernel
> >  > image.
> > 
> >  [Copying it to fastboot and linux-kernel mailing lists]
> > 
> >  We are booting second kernel (capture kernel) from a reserved memory location
> >  to take care of on-going DMA issues. So even if some DMA transactions are going
> >  on after the crash they will not corrupt the new kernel.
> > 
> >  > 
> >  > The interrupt panic of the fusion is probably a symptom of this: I bet a
> >  > DMA transfer has just completed and the interrupt is to inform us of
> >  > this (however, in the new kernel we're not expecting any transfers).
> > 
> >  That might very well be the case. So driver should simply ignore the interrupt
> >  when it is not expecting it or it should reset the device if it finds that 
> >  some interrupts are pending when it should not have been there.
> > 
> >  Basically it is a matter of hardening the driver so that it can handle/
> >  initialize the device even if the device is not in reset state. 
> 
> I'd expect that a lot of these problems could be reduced by simply pausing
> for a while in the crash handler, wait for I/O to complete.
> 

Andrew, We will test it out and see if it helps on some of the already
reported issues.

Thanks
Vivek

      reply	other threads:[~2005-07-26 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 11:25 [IBM] RE: [BUG] Fusion MPT Base Driver initialization failure wit h kdum p Vivek Goyal
2005-07-25 22:10 ` Andrew Morton
2005-07-26 11:03   ` Vivek Goyal [this message]

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=20050726110311.GC4047@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=Eric.Moore@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Jared.Hayes@lsil.com \
    --cc=Roy.Wade@lsil.com \
    --cc=akpm@osdl.org \
    --cc=bharata@in.ibm.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox