Date: Mon, 18 Mar 2013 11:54:51 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Tom Evans <tevans.uk@googlemail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: FreeBSD is very slow when Memory chip sizes are imbalanced in slots Message-ID: <35878.1363607691@critter.freebsd.dk> In-Reply-To: <CAFHbX1KkD7fWP%2BKZNrSjzCStUM_Smjw7GdKDTo=DjjMoe5ttGA@mail.gmail.com> References: <CAOgwaMss0cB9bFqCkjzukb-=9FqgLN9vthL5QdQsk-6Lknk5VQ@mail.gmail.com> <CAFHbX1LcCGoWy%2BHzp8T7z4noFZAMK1-sCuWpO_Z_ybhnoMMY5A@mail.gmail.com> <CAOgwaMtTmx4LhEdrg3WNjZA-uyTRSN913RBWrrqMia4GZhP_zA@mail.gmail.com> <CAFHbX1KkD7fWP%2BKZNrSjzCStUM_Smjw7GdKDTo=DjjMoe5ttGA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <CAFHbX1KkD7fWP+KZNrSjzCStUM_Smjw7GdKDTo=DjjMoe5ttGA@mail.gmail.com>, Tom Evans writes: >You say this, have you actually measured/checked. sysutils/dmidecode >will interrogate your BIOS and tell us what it thinks is installed in >each RAM socket. It is not uncommon for RAM to say one thing on the >outside, and report something completely different to the BIOS. I can only second Tom's call for a proper scientific approach to debugging this issue, rather than just assume that it is the operating systems fault. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35878.1363607691>