[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46CF0B70.1050302@linux.vnet.ibm.com>
Date: Fri, 24 Aug 2007 22:16:40 +0530
From: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
To: Yasunori Goto <y-goto@...fujitsu.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mel@...net.ie>, "Luck, Tony" <tony.luck@...el.com>,
Jeremy Higdon <jeremy@....com>, Andi Kleen <ak@...e.de>,
linux-kernel@...r.kernel.org,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
linux-ia64@...r.kernel.org, Christoph Lameter <clameter@....com>,
linux-mm@...ck.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)
Yasunori Goto wrote:
> I found find_next_best_node() was wrong.
> I confirmed boot up by the following patch.
> Mel-san, Kamalesh-san, could you try this?
>
> Bye.
> ---
>
> Fix decision of memoryless node in find_next_best_node().
> This can be cause of SW-IOMMU's allocation failure.
>
> This patch is for 2.6.23-rc3-mm1.
>
> Signed-off-by: Yasunori Goto <y-goto@...fujitsu.com>
>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: current/mm/page_alloc.c
> ===================================================================
> --- current.orig/mm/page_alloc.c 2007-08-24 16:03:17.000000000 +0900
> +++ current/mm/page_alloc.c 2007-08-24 16:04:06.000000000 +0900
> @@ -2136,7 +2136,7 @@ static int find_next_best_node(int node,
> * Note: N_HIGH_MEMORY state not guaranteed to be
> * populated yet.
> */
> - if (pgdat->node_present_pages)
> + if (!pgdat->node_present_pages)
> continue;
>
> /* Don't want a node to appear more than once */
>
>
This patch resolves the kernel panic problem.
-
Kamalesh Babulal.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists