linux-kernel - Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH

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.0705300712230.5844@p34.internal.lan>
Date:	Wed, 30 May 2007 07:15:12 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Zoltan Boszormenyi <zboszor@...aweb.hu>
cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	support@...lbox.intel.com
Subject: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH

On Wed, 30 May 2007, Zoltan Boszormenyi wrote:

> Hi,
>
>> Look at how slow the raid benchmarks are in dmesg with 8GB of memory!
>> 
>> [   59.592560] raid6: using algorithm sse2x4 (476 MB/s)
>> [   59.597558] raid5: using function: generic_sse (56.000 MB/sec)
>> 
>> Yikes!
>> 
>> With mem=4096M:
>> [   60.336352] raid6: using algorithm sse2x4 (6804 MB/s)
>> [   60.341345] raid5: using function: generic_sse (8552.000 MB/sec)
>> 
>> What is going on here?
>> 
>> Justin.
>
> I saw a similar effect on a P5 board that could
> only cache 64MB of memory a long time ago.
> Putting more memory into it made the machine slower
> and e.g. made the sym2 driver giving up at initialization.
> Maybe it's a modern reincarnation of the problem?
>
> Best regards,
> Zoltán Böszörményi
>

I see, so Intel 965 motherboards do not work with 8GB of memory?  Or is 
this a Linux issue?

I have an Intel Case ID open 225446 but so far we have not gotten anywhere 
with this problem.  Currently I have 8GB in the machine and boot with 
mem=4096M.  Was there any type of fix?  Any recommendations as to what I 
can do?  Continue to speak with Intel?  Or perhaps someone with more 
knowledge of the kernel and chime in as to what exactly is happening here?

Justin.