linux-kernel - Re: Problem with ata layer in 2.6.24

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: <479F7129.8010406@rtr.ca>
Date:	Tue, 29 Jan 2008 13:32:09 -0500
From:	Mark Lord <liml@....ca>
To:	rgheck <rgheck@...jweil.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Daniel Barkalow <barkalow@...ervon.org>,
	Gene Heskett <gene.heskett@...il.com>,
	Zan Lynx <zlynx@....org>,
	Calvin Walton <calvin.walton@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux ide Mailing list <linux-ide@...r.kernel.org>
Subject: Re: Problem with ata layer in 2.6.24

rgheck wrote:
> Mark Lord wrote:
>> rgheck wrote:
>>> Alan Cox wrote:
>>>>> not one problem but lots---is sufficiently widespread that a Mini 
>>>>> HOWTO, say, would be really welcome and, I'm guessing, widely used.
>>>>>     
>>>>
>>>> We don't see very many libata problems at the distro level and they for
>>>> the most part boil down to
>>>>
>>>> - sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
>>>> anyway
>>>>   
>>> Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 
>>> 4GB.
>> ..
>>
>> For all practical purposes, most memory over 3GB (or sometimes even 2GB)
>> on a 32-bit x86 system is treated as >4GB by the motherboard.
>>
>> Because it's not the amount of *memory* that matters so much,
>> but rather the amount of *used address space*.  Video cards,
>> PCI devices, other motherboard resources etc.. can all subtract
>> from the available address space, leaving much less than 4GB
>> for your RAM.
> 
> Right. So it looks like I do have this issue, though I haven't seen any 
> actual problems on 24. Is there a known workaround?
..

For now, the workaround is to not enable the RAM above 4GB.
Your kernel .config file should therefore have these two lines:

CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set

Later, once the issue is fixed at the driver level (soon),
you can get your high memory back again by enabling CONFIG_HIGHMEM64G,
though this will cost a few percent of performance in the extra
page table overhead it creates.

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