mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rajkumar S" <rajkumars@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: HIGHMEM64G Kernel (2.6.23.1) makes system crawl
Date: Wed, 24 Oct 2007 21:46:45 +0530	[thread overview]
Message-ID: <64de5c8b0710240916k485bbcf9n88ad8f0ecf920409@mail.gmail.com> (raw)
In-Reply-To: <471F560D.4040909@shaw.ca>

On 10/24/07, Robert Hancock <hancockr@shaw.ca> wrote:
> Rajkumar S wrote:
> > Hello,
> >
> > I am using a Core 2 Duo E6750 CPU on an intel DG33FB mother board with
> > 4GB Ram, running Debian Lenny.
> >
> > Since the box has 4 GB ram I compiled a big mem kernel, but the
> > machine is very slow while running big mem kernel. It takes about 37
> > minutes to compile the intel e1000 driver  (e1000-7.6.5.tar.gz) from
> > intel site. But it's performing normally when using a non big mem
> > kernel. The diff of the .config between working and non working is as
> > follows.
>
> Post your contents of /proc/mtrr. Likely a BIOS bug which has been seen
> on a number of Intel boards, which doesn't mark all of RAM as cachable.

I have upgraded the bios to latest  (v. 0293 October 02, 2007)
Previously the /proc/mtrr was:

ravanan:~# cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
reg03: base=0xcf800000 (3320MB), size=   8MB: uncachable, count=1
reg04: base=0xcf600000 (3318MB), size=   2MB: uncachable, count=1
reg05: base=0xcf500000 (3317MB), size=   1MB: uncachable, count=1
reg06: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg07: base=0x120000000 (4608MB), size= 128MB: write-back, count=1

Now after upgrading the bios it's

reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
reg03: base=0xcf800000 (3320MB), size=   8MB: uncachable, count=1
reg04: base=0xcf400000 (3316MB), size=   4MB: uncachable, count=1
reg05: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg06: base=0x120000000 (4608MB), size= 128MB: write-back, count=1

raj

  reply	other threads:[~2007-10-24 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.7rN1uBoDAvdkB/ZVQAe63J/uvnk@ifi.uio.no>
2007-10-24 14:26 ` Robert Hancock
2007-10-24 16:16   ` Rajkumar S [this message]
     [not found] <fa.wTdv3mFEbQaGOciq1qlqjQYioTk@ifi.uio.no>
     [not found] ` <fa.5twmqnTSoQ6RAav3LKQBxq5jBTw@ifi.uio.no>
     [not found]   ` <fa.USaSUutC3B7gcx/C3bJNmlbDfJk@ifi.uio.no>
2007-10-24 23:18     ` Robert Hancock
2007-10-24 10:26 Rajkumar S
2007-10-24 14:41 ` Boaz Harrosh
2007-10-24 16:35   ` Lennart Sorensen
2007-10-24 17:56     ` Boaz Harrosh
2007-10-24 20:37       ` Lennart Sorensen
2007-10-24 17:21   ` H. Peter Anvin

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=64de5c8b0710240916k485bbcf9n88ad8f0ecf920409@mail.gmail.com \
    --to=rajkumars@gmail.com \
    --cc=hancockr@shaw.ca \
    --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

all inboxes | Powered by JetHome®