On 03/24/2012 12:25 AM, Will Set wrote:
Friday, March 23, 2012 11:06 PM Daniel Kahn Gillmor wrote: On Fri, 23 Mar 2012 19:51:37 -0700 (PDT), Will Set <debiandunes@yahoo.com> wrote:I know of 5 bug reports that confirm using boot parameter - processor.nocst=1 as a workaround for kernels < 2.6.38Thanks, i will try this the next time i get a chance to restart this machine (it's currently crashed again and i don't have physical access right now).Probably not necessary since you are using 2.6.32 (squeeze) kernels. Normally, kernels older than 2.6.39 don't need the extra boot parameter.
Do you mean that the less-than sign (<) in your earlier remark was meant to be a greater-than sign (>) ?
But 4 GiB of ram is max for the board and although HP has spec for 4 GiB of ram for your model, they also have notes recommending only 2 GiB of Ram, in another doc. http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c00072736/c00072736.pdf
i've run this machine with 4GiB of RAM for years now with no trouble until trying to upgrade to squeeze kernels or hypervisors :/
This is the first i'm hearing that the -486 flavor would cause instability on highmem machines. Can you point me to some documentation so i could understand why that might be the case?Here is a link to linux-image-2.6.32-5-686-bigmem http://packages.debian.org/squeeze/linux-image-2.6-686-bigmem.
This doesn't provide me with any information that suggests that -486 flavors would cause instability on machines with 4GiB; it only suggests that i want those kernels if i want to make full use of all 4GiB, AFAICT. Did you mean to point me to some other documentation? Am i reading it wrong?
--dkg