From: Haren Myneni <haren@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, ellerman@au1.ibm.com,
Milton Miller <miltonm@bga.com>, Olaf Hering <olh@suse.de>
Subject: [PATCH] kdump: Fix for machine checkstop on DMA fault
Date: Wed, 22 Mar 2006 20:30:26 -0800 [thread overview]
Message-ID: <44222462.2030103@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
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.
Signed-off-by: Haren Myneni <haren@us.ibm.com>
[-- Attachment #2: kdump-dma-fault-fix.patch --]
[-- Type: text/x-patch, Size: 557 bytes --]
--- 2616-git5-k1/arch/powerpc/kernel/iommu.c.orig 2006-04-04 19:08:02.000000000 -0700
+++ 2616-git5-k1/arch/powerpc/kernel/iommu.c 2006-04-04 10:50:45.000000000 -0700
@@ -427,8 +427,10 @@ struct iommu_table *iommu_init_table(str
tbl->it_largehint = tbl->it_halfpoint;
spin_lock_init(&tbl->it_lock);
+#ifndef CONFIG_CRASH_DUMP
/* Clear the hardware table in case firmware left allocations in it */
ppc_md.tce_free(tbl, tbl->it_offset, tbl->it_size);
+#endif
if (!welcomed) {
printk(KERN_INFO "IOMMU table initialized, virtual merging %s\n",
next reply other threads:[~2006-03-23 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 4:30 Haren Myneni [this message]
2006-03-23 5:38 ` [PATCH] kdump: Fix for machine checkstop on DMA fault Olof Johansson
2006-03-23 6:06 ` Michael Ellerman
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=44222462.2030103@us.ibm.com \
--to=haren@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).