linux-kernel - Re: + powerpc-fix-code-for-reserved-memory-spanning-across-nodes.patch added to -mm tree

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]

Date:	Fri, 13 Feb 2009 16:31:10 +0530
From:	Chandru <chandru@...ibm.com>
To:	Dave Hansen <dave@...ux.vnet.ibm.com>
CC:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org,
	chandru@...ux.vnet.ibm.com, paulus@...ba.org,
	akpm@...ux-foundation.org, Johannes Weiner <hannes@...xchg.org>,
	"Jon M. Tollefson [imap]" <kniht@...ibm.com>
Subject: Re: + powerpc-fix-code-for-reserved-memory-spanning-across-nodes.patch
 added to -mm tree

Chandru wrote:
> Dave Hansen wrote:
>> On Mon, 2009-02-09 at 11:31 +1100, Benjamin Herrenschmidt wrote:
>>  
>>  
>>> (BTW. On another note, do you still have pending bug fixes that didn't
>>> got in .29 ?)
>>>     
>>
>> No, I don't think so.  There were some distro fixes but I couldn't
>> reproduce the bugs on mainline.
>>
>> -- Dave
>>
>>   
> Dave,
>
> If I remember,  the first mail that I sent on this subject said
> 2.6.28-rc9 panics. Unless something has changed in the way
> lmb's are added or are reserved, this should be also
> reproducible with the mainline kernel on the machines that
> had exhibited this problem earlier. I will verify your patch
> on these machines again and let you know the results.
>
> Thanks,
> Chandru

This still occurs with 2.6.29.rc4 on one of the machines that had
shown this problem earlier and Dave's patch solves the issue here.

The system comes up with two nodes...

<snip>
NUMA associativity depth for CPU/Memory: 3
Node 0 Memory: 0x0-0x40000000
Node 1 Memory: 0x40000000-0x80000000

I had to increase the crashkernel memory size to beyond 1G and
hence used crashkernel=1280M@.... This caused the kernel
to hit the bug as with earlier kernels.

-Chandru

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