FS#4554 - CONFIG_HIGHMEM mis-configuration

Attached to Project: Arch Linux
Opened by John Piel (uberGeek) - Wednesday, 03 May 2006, 02:43 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Very Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I suspect CONFIG_HIGHMEM4G=y and CONFIG_HIGHMEM64G=y are exclusive, and the first one found is used. I've not confirmed this, however, they are both set to y in the current kernel config file and zcat /proc/config.gz | grep reports that 64G is NOT ENABLED. I've built a kernel now with a single edit to the current config "#CONFIG_HIGHMEM4G=y", leaving CONFIG_HIGHMEM64G=y, and I now have my full 4GB back.

Thank you.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 05 May 2006, 06:36 GMT
Reason for closing:  Implemented
Comment by Tobias Powalowski (tpowa) - Wednesday, 03 May 2006, 07:21 GMT
ups ok jsut missed this for .13 kernel, but i guess kernel .14 is coming soon.

Loading...