public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Mel Gorman <mel@skynet.ie>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	Jeremy Higdon <jeremy@sgi.com>, Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	linux-ia64@vger.kernel.org, Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted)
Date: Fri, 24 Aug 2007 11:49:31 -0400	[thread overview]
Message-ID: <1187970572.5869.10.camel@localhost> (raw)
In-Reply-To: <20070824145233.GA26374@skynet.ie>

On Fri, 2007-08-24 at 15:52 +0100, Mel Gorman wrote:
> On (24/08/07 15:53), Yasunori Goto didst pronounce:
> > 
> > I found find_next_best_node() was wrong.
> > I confirmed boot up by the following patch.
> > Mel-san, Kamalesh-san, could you try this?
> > 
> 
> This boots the IA-64 successful and gets rid of that DMA corrupts
> memory message. As a bonus, it fixes up the memoryless nodes (the bug
> where Total pages == 0 and there is a BUG in page_alloc.c) by building
> zonelists properly. The machine still fails to boot with the more familiar
> net/core/skbuff.c:95 but that is a separate problem.
> 
> Well spotted Yasunori-san.
> 
> Andrew, this fixes a real problem and should be considered a fix to
> memoryless-nodes-fixup-uses-of-node_online_map-in-generic-code.patch unless
> Christoph Lameter objects.

I reworked that patch and posted the update on 16aug which does not have
this problem:

http://marc.info/?l=linux-mm&m=118729871101418&w=4

This should replace
memoryless-nodes-fixup-uses-of-node_online_map-in-generic-code.patch
in -mm.

Lee



  reply	other threads:[~2007-08-24 15:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 14:32 [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Kamalesh Babulal
2007-08-22 16:19 ` Andrew Morton
2007-08-22 17:25   ` Andi Kleen
2007-08-22 18:31     ` Kamalesh Babulal
2007-08-22 21:04       ` Luck, Tony
2007-08-22 22:24         ` Kamalesh Babulal
2007-08-22 22:56           ` Luck, Tony
2007-08-22 23:11             ` Jeremy Higdon
2007-08-22 23:27               ` Luck, Tony
2007-08-22 23:54                 ` Jeremy Higdon
2007-08-23  0:05                   ` Luck, Tony
2007-08-23  1:09                     ` Jeremy Higdon
2007-08-23  1:16                       ` Jeremy Higdon
2007-08-23  9:15                 ` Mel Gorman
2007-08-23 13:27                   ` Yasunori Goto
2007-08-23 17:22                     ` Luck, Tony
2007-08-23 21:21                       ` Andrew Morton
2007-08-24  6:53                         ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Yasunori Goto
2007-08-24 14:52                           ` Mel Gorman
2007-08-24 15:49                             ` Lee Schermerhorn [this message]
2007-08-24 17:00                               ` Christoph Lameter
2007-08-24 18:03                                 ` Lee Schermerhorn
2007-08-24 18:08                                   ` Christoph Lameter
2007-08-24 17:02                             ` Christoph Lameter
2007-08-24 16:46                           ` Kamalesh Babulal
2007-08-28 22:41                           ` Adam Litke
2007-08-23  9:22                 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Kamalesh Babulal

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=1187970572.5869.10.camel@localhost \
    --to=lee.schermerhorn@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=clameter@sgi.com \
    --cc=jeremy@sgi.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@skynet.ie \
    --cc=tony.luck@intel.com \
    --cc=y-goto@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox