From: Andrew Walrond <andrew@walrond.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org,
Sergei Haller <Sergei.Haller@math.uni-giessen.de>
Subject: Re: lost memory on a 4GB amd64
Date: Fri, 24 Sep 2004 10:41:08 +0100 [thread overview]
Message-ID: <200409241041.08975.andrew@walrond.org> (raw)
In-Reply-To: <200409241127.38529.rjw@sisk.pl>
On Friday 24 Sep 2004 10:27, Rafael J. Wysocki wrote:
>
> > AW> cpu1's bank. How are yours arranged?
> >
> > my board has only four banks, each of them has a 1GB module sitting.
> > (page 26 of ftp://ftp.tyan.com/manuals/m_s2875_102.pdf)
>
> Which is what makes the difference, I think. IMO, the problem is that
> _both_ CPUs use the same memory bank that is physically attached to only
> one of them which leads to conflicts, apparently (the CPU with memory has
> also PCI/AGP/whatever attached to it via HyperTransport so I can imagine
> there may be issues with overlapping address spaces etc.). I'd bet that
> there's something wrong either with the BIOS or with the board design
> itself and I don't think there's anything that the kernel can do about it
> (usual disclaimer applies).
>
> Out of couriosity: have you tried to run the kernel with K8 NUMA enabled?
>
Actually, the block diagram on page 9 of the manual suggests that this is
_not_ a NUMA board, since all DIMMS are connected to cpu1. The block diagram
for my thunder k8w specifically shows DIMMS associated with individual
processors.
Which suggests that NUMA show be _disabled_ in the kernel config.
Have you tried it with NUMA disabled? I think I remeber it being on in
the .config you sent me.
Andrew
next prev parent reply other threads:[~2004-09-24 9:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 4:48 lost memory on a 4GB amd64 Sergei Haller
2004-09-16 13:30 ` Andrew Walrond
2004-09-16 13:48 ` Andrew Walrond
2004-09-16 14:09 ` Sergei Haller
2004-09-16 14:28 ` Andrew Walrond
2004-09-16 14:56 ` Sergei Haller
2004-09-16 15:19 ` Andrew Walrond
2004-09-16 15:52 ` Sergei Haller
2004-09-18 14:18 ` Sergei Haller
2004-09-19 20:01 ` Jon Masters
2004-09-19 21:47 ` Sergei Haller
2004-09-19 22:00 ` Jon Masters
2004-09-19 22:19 ` Sergei Haller
2004-09-20 10:26 ` Sergei Haller
2004-09-24 4:38 ` Sergei Haller
2004-09-24 4:38 ` Sergei Haller
2004-09-24 8:15 ` Andrew Walrond
2004-09-24 8:23 ` Sergei Haller
2004-09-24 8:31 ` Andrew Walrond
2004-09-24 8:57 ` Sergei Haller
2004-09-24 9:27 ` Rafael J. Wysocki
2004-09-24 9:41 ` Andrew Walrond [this message]
2004-09-24 11:42 ` Sergei Haller
2004-09-24 12:15 ` Andrew Walrond
2004-10-22 8:59 ` Sergei Haller
2004-10-22 9:26 ` Andrew Walrond
2004-10-22 18:24 ` Andi Kleen
2004-10-23 10:02 ` Andreas Klein
2004-10-23 16:43 ` Andi Kleen
2004-10-26 11:25 ` Andreas Klein
2004-10-23 10:26 ` Sergei Haller
2004-10-23 16:49 ` Andi Kleen
2004-10-24 9:53 ` Sergei Haller
[not found] ` <Pine.LNX.4.58.0410271704050.3903@pluto.physik.uni-wuerzburg.de>
2004-10-27 15:39 ` solution " Sergei Haller
2004-10-27 16:05 ` Andreas Klein
2004-10-27 16:17 ` Sergei Haller
2004-10-28 13:32 ` Andreas Klein
2004-10-27 16:44 ` linux-os
2004-10-27 17:47 ` Andrew Walrond
2004-09-24 11:50 ` Sergei Haller
[not found] <2EWxl-7CI-13@gated-at.bofh.it>
2004-09-16 7:01 ` Andi Kleen
2004-09-16 12:15 ` Sergei Haller
2004-09-16 12:34 ` Andi Kleen
2004-09-18 14:07 ` Sergei Haller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409241041.08975.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=Sergei.Haller@math.uni-giessen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.