public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rudolf Usselmann <rudi@asics.ws>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel (64bit) 4GB memory support
Date: Sun, 12 Dec 2004 11:12:15 +0700	[thread overview]
Message-ID: <1102824735.17081.187.camel@cpu0> (raw)
In-Reply-To: <41BB32A4.2090301@pobox.com>

On Sun, 2004-12-12 at 00:47, Jeff Garzik wrote:
...
> All 2.6 kernels work with 64bit and >4GB memory, on my configurations 
> (x86-64, ia64, and alpha).
> 
> It is a mistake to assume that all 64bit and/or >4GB is broken.
> 
> > (Tiger K8W, dual Opteron)
> 
> Ok, we finally get a bit of useful information.
> 
> Are you CERTAIN that you are booting a 64bit kernel?
> Is your memory PC1600, PC2100, or PC2700?
> Is your memory installed in matched pairs?
> Is all your memory ECC registered?
> Is your BIOS at the latest version?

Hi Jeff,

"yes" to all of the above. I am 100% certain this is not a
hardware problem. I have paired simms and with a 32 bit kernel
can use the entire 4GB. I also have run memtest86 ...

> Once we get through the hardware issues, now it is time to do a binary 
> search of 2.6 kernels, to see which one works for you.  If no 2.6 
> kernels work for you, then give 2.4 kernels a try.
> 
> 	Jeff

I have previously reported this bug to the list (about a week
ago). I am greatfull for every response and am willing to
investigate everything.

Previously I was running Fedora Core 2 32BIT with the 2.6.9
kernel and never had problems with 4GB. After finally upgrading
to 64 bit I can't use 4GB memory anymore.


# ver_linux

Linux cpu10 2.6.9RU1.1 #11 SMP Sun Dec 5 11:42:18 ICT 2004 x86_64 x86_64 x86_64 GNU/Linux

Gnu C                  3.4.2
Gnu make               3.80
binutils               2.15.92.0.2
util-linux             2.12a
mount                  2.12a
module-init-tools      3.1-pre5
e2fsprogs              1.35
reiserfsprogs          line
reiser4progs           line
pcmcia-cs              3.2.7
quota-tools            3.12.
PPP                    2.4.2
nfs-utils              1.0.6
Linux C Library        2.3.3
Dynamic linker (ldd)   2.3.3
Procps                 3.2.3
Net-tools              1.60
Kbd                    1.12
Sh-utils               5.2.1
Modules Loaded         autofs4 nfs lockd sunrpc binfmt_misc dm_mod button battery ac nvidia ipv6 ohci_hcd uhci_hcd ehci_hcd hw_random snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore floppy


The attached boot log shows the kernel panic ....

Kind Regards,
rudi


  reply	other threads:[~2004-12-12  4:12 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 [this message]
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
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=1102824735.17081.187.camel@cpu0 \
    --to=rudi@asics.ws \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox