From owner-freebsd-current@FreeBSD.ORG  Mon Mar 18 11:54:59 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 1EBD9D2
 for <freebsd-current@freebsd.org>; Mon, 18 Mar 2013 11:54:59 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id C06893DE
 for <freebsd-current@freebsd.org>; Mon, 18 Mar 2013 11:54:58 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 05EDA8A521;
 Mon, 18 Mar 2013 11:54:51 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.14.6/8.14.6) with ESMTP id r2IBsp6t035879;
 Mon, 18 Mar 2013 11:54:51 GMT (envelope-from phk@phk.freebsd.dk)
To: Tom Evans <tevans.uk@googlemail.com>
Subject: Re: FreeBSD is very slow when Memory chip sizes are imbalanced in
 slots
In-reply-to: <CAFHbX1KkD7fWP+KZNrSjzCStUM_Smjw7GdKDTo=DjjMoe5ttGA@mail.gmail.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <CAOgwaMss0cB9bFqCkjzukb-=9FqgLN9vthL5QdQsk-6Lknk5VQ@mail.gmail.com>
 <CAFHbX1LcCGoWy+Hzp8T7z4noFZAMK1-sCuWpO_Z_ybhnoMMY5A@mail.gmail.com>
 <CAOgwaMtTmx4LhEdrg3WNjZA-uyTRSN913RBWrrqMia4GZhP_zA@mail.gmail.com>
 <CAFHbX1KkD7fWP+KZNrSjzCStUM_Smjw7GdKDTo=DjjMoe5ttGA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1>
Date: Mon, 18 Mar 2013 11:54:51 +0000
Message-ID: <35878.1363607691@critter.freebsd.dk>
Cc: freebsd-current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 11:54:59 -0000

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.