| 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
| ||
|
Message-id: <465E513E.60903@shaw.ca> Date: Wed, 30 May 2007 22:38:22 -0600 From: Robert Hancock <hancockr@...w.ca> To: Parag Warudkar <parag.warudkar@...il.com> Cc: jpiszcz@...idpixels.com, linux-kernel@...r.kernel.org Subject: Re: Case: 7454422: Re: Kernel 2.6.21.3 does not work with 8GB of RAM on Intel 965WH motherboards. (FULL DMESG) Parag Warudkar wrote: > Robert Hancock wrote: > > >> 0-3319MB >> 4096-8832MB >> >> leaving 64MB of memory at the top of RAM uncached. What do you want to >> bet that something important (kernel code?) is getting loaded there.. >> >> So essentially it's a BIOS problem, it's not setting up the MTRRs >> properly in order to map all of RAM as cacheable. As Andi says, complain >> to Intel. >> > > Could the BADRAM patch be useful for him? > http://rick.vanrein.org/linux/badram/download.html has 2.6.21 version. > It says it supports x86_64. May be using this patch he can exclude > that RAM from being used/accessed? I think that mem=8832M would work as well, to make the kernel use only the memory that is marked cacheable. (It looks like this parameter takes the highest memory address we want the kernel to use, not the highest memory amount.) -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@...pamshaw.ca Home Page: http://www.roberthancock.com/ - 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