linux-kernel - Re: [BUG] 2.6.23-rc3-mm1 kernel BUG at mm/page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0708231303050.14720@schroedinger.engr.sgi.com>
Date:	Thu, 23 Aug 2007 13:05:22 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Mel Gorman <mel@...net.ie>, linux-kernel@...r.kernel.org,
	Balbir Singh <balbir@...ux.vnet.ibm.com>, linux-mm@...ck.org
Subject: Re: [BUG] 2.6.23-rc3-mm1 kernel BUG at mm/page_alloc.c:2876!

On Thu, 23 Aug 2007, Kamalesh Babulal wrote:

> After applying the patch, the call trace is gone but the kernel bug
> is still hit

Yes that is what we expected. We need more information to figure out why 
the kmalloc_node fails there. It should walk through all nodes to find 
memory.

I see that you have 4 cpus and 16 nodes. How are the cpus assigned to 
nodes? If a cpu would be assigned to a nonexisting node then this could be 
the result.

Could you post the full boot log?

-
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/