Re: Disabling CPUs

On Sun, Sep 25, 2022 at 2:48 PM Tomek CEDRO <tomek@cedro.info> wrote:

> On Sun, Sep 25, 2022 at 7:08 AM Kevin Oberman  wrote:
> >
> > On Sat, Sep 24, 2022 at 12:07 AM Amar Takhar wrote:
> >>
> >> On 2022-09-23 22:58 -0700, Kevin Oberman wrote:
> >> > Thanks, Amar! I'll give this a try tomorrow.
> >>
> >> No problem!
> >>
> > Well, no joy. My BIOS had no ability to disable cores. Confirmed with
> Lenovo support. So no ability to do more than cpuset.
>
> There is that utility DMIDECODE in the port tree.. it allowed me once
> to mess with the BIOS settings even though the BIOS was locked out
> with a password I did not know.. so you can list and modify settings
> without actually using the BIOS menu program.. maybe this would come
> handy here? :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Thanks for the suggestion, but I have gone through the full output of
dmidecode and see nothing that would help me. Nothing on the CPU ties to
the cores and type 12, sttable options, is empty... just a handle and the
type.

I've been silent while waiting for the additional memory since I could not
do any real work with only 8G. It finally arrived and I installed it
yesterday. I'm very happy to say that my VirtualBox VMs seem to now be
working correctly. I've done limited testing, but seen no problems to this
point. Much better than an instant system panic when a VM finished loading.

On the plus side, with "cpuset -s 1 -l 0-3", things seem reasonably stable.
That means no crashes with many hours of use and a lot of compilations.
With only 4 cores, it's not a fast as I had hoped, but I will be
benchmarking soon.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
Email: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683