From: Rudolf Usselmann <rudi@asics.ws>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: "Frank Denis (Jedi/Sector One)" <j@pureftpd.org>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: kernel (64bit) 4GB memory support
Date: Tue, 21 Dec 2004 23:23:15 +0700 [thread overview]
Message-ID: <1103646195.3652.196.camel@cpu0> (raw)
In-Reply-To: <Pine.LNX.4.61.0412201246180.12334@montezuma.fsmlabs.com>
On Tue, 2004-12-21 at 02:49, Zwane Mwaikambo wrote:
>
> Rudolf, thanks for collecting that information. Since you said that
> 2.6.10-rc3 also had similar results it counts out a number of suspects i
> had in the -mm tree. Could you work towards isolating a working kernel
> version? You could try these;
>
> 2.6.8.1
> 2.6.9
> 2.6.9-mm1
>
> Thanks,
> Zwane
Zwane,
is there a more scientific approach to this problem ?
See my problem is that I have a very expensive motherboard
and very expensive simm modules which I already inserted and
removed several dozen times. I would like to avoid doing this
experimenting as much as possible. Specially if there might
be a more contractive way. We don't know if there ever has
been a kernel that has worked with this configuration, right ?
memtest86 seems to detect and test all 4gb just fine. So there
must be some way to find the problem ...
I mean you guys must have a pretty good idea what is going wrong.
Is it possible to add some debugging information ? The latest
mm4-jeda kernel seems to be able to "recover" from panics/crashes.
It doesn't "die" it just kills the offending app (at least thats
my limited understanding).
Kind Regards,
rudi
next prev parent reply other threads:[~2004-12-21 16:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 8:16 kernel (64bit) 4GB memory support Rudolf Usselmann
2004-12-11 10:06 ` Jeff Garzik
2004-12-11 10:13 ` Rudolf Usselmann
2004-12-11 11:22 ` Andrew Walrond
2004-12-11 17:47 ` Jeff Garzik
2004-12-12 4:12 ` Rudolf Usselmann
2004-12-12 4:41 ` Zwane Mwaikambo
2004-12-12 5:10 ` Rudolf Usselmann
2004-12-12 8:32 ` Zwane Mwaikambo
2004-12-12 9:15 ` Rudolf Usselmann
2004-12-12 16:35 ` Zwane Mwaikambo
2004-12-14 12:25 ` Rudolf Usselmann
2004-12-15 4:22 ` Zwane Mwaikambo
[not found] ` <20041216074905.GA2417@c9x.org>
2004-12-16 16:09 ` Rudolf Usselmann
2004-12-20 19:49 ` Zwane Mwaikambo
2004-12-21 16:23 ` Rudolf Usselmann [this message]
2004-12-21 16:33 ` Zwane Mwaikambo
2004-12-21 16:39 ` Rudolf Usselmann
2004-12-21 16:56 ` Zwane Mwaikambo
2005-05-09 15:56 ` Rudolf Usselmann
2005-05-09 20:07 ` Lennart Sorensen
2005-05-10 19:48 ` Rudolf Usselmann
2005-05-10 20:03 ` Lee Revell
2005-05-11 5:02 ` Rudolf Usselmann
2005-05-10 22:58 ` Terry Vernon
2005-05-12 3:53 ` Stefan Smietanowski
2005-05-11 14:27 ` Lennart Sorensen
2005-05-12 3:56 ` Stefan Smietanowski
2005-05-12 4:04 ` Rudolf Usselmann
2005-05-12 15:13 ` William Lee Irwin III
2005-05-09 20:07 ` Andi Kleen
2005-05-09 22:24 ` Zwane Mwaikambo
2005-05-10 19:50 ` Rudolf Usselmann
2005-05-09 23:13 ` kernel (64bit) 4GB memory support II Andi Kleen
2005-01-13 17:26 ` kernel (64bit) 4GB memory support Rudolf Usselmann
2005-01-14 23:34 ` Zwane Mwaikambo
2005-01-15 5:34 ` Rudolf Usselmann
2005-01-17 4:54 ` Zwane Mwaikambo
2004-12-11 11:35 ` bert hubert
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=1103646195.3652.196.camel@cpu0 \
--to=rudi@asics.ws \
--cc=j@pureftpd.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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.