From: Michael Ellerman <michael@ellerman.id.au>
To: linuxppc-dev@ozlabs.org
Cc: Milton Miller <miltonm@bga.com>,
Paul Mackerras <paulus@samba.org>, Olaf Hering <olh@suse.de>,
ellerman@au1.ibm.com
Subject: Re: [PATCH] kdump: Fix for machine checkstop on DMA fault
Date: Thu, 23 Mar 2006 17:06:27 +1100 [thread overview]
Message-ID: <200603231706.35508.michael@ellerman.id.au> (raw)
In-Reply-To: <20060323053854.GA17693@pb15.lixom.net>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Thu, 23 Mar 2006 16:38, Olof Johansson wrote:
> On Wed, Mar 22, 2006 at 08:30:26PM -0800, Haren Myneni wrote:
> > Paul, If you are OK with this fix, please send it upstream.
> >
> > Thanks
> > Haren
> >
> > - Some machines checkstop on dma protection fault for ongoing DMA left
> > in the first kernel. Since, we do not shutdown devices before the kdump
> > boot, let them continue DMA to old kernel space.
>
> How is this solved for regular kexec, doesn't the same problem exist
> there?
The idea for normal kexec is that the kernel should have shut everything down
properly. It's a bug if there are still DMAs going on. Hopefully.
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-23 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 4:30 [PATCH] kdump: Fix for machine checkstop on DMA fault Haren Myneni
2006-03-23 5:38 ` Olof Johansson
2006-03-23 6:06 ` Michael Ellerman [this message]
2006-03-23 6:19 ` Olof Johansson
2006-03-23 20:12 ` Olof Johansson
2006-03-23 23:06 ` Haren Myneni
2006-03-23 23:11 ` Olof Johansson
2006-03-27 5:04 ` Michael Ellerman
2006-03-27 14:06 ` Olof Johansson
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=200603231706.35508.michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--cc=ellerman@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=olh@suse.de \
--cc=paulus@samba.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 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.