All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rojhalat Ibrahim <imr@rtschenk.de>
To: Alex Gonzalez <linux-mips@packetvision.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Going over 512M of memory
Date: Mon, 25 Jul 2005 09:43:56 +0200	[thread overview]
Message-ID: <42E4983C.5030804@rtschenk.de> (raw)
In-Reply-To: <1122039139.30605.21.camel@euskadi.packetvision>

Hi,

I am not sure what patch you are actually talking about.
In the mentioned thread there were several. Did you only apply
the last one or all of them, i.e. did you also apply
the patches that keep flushing the caches?
Because those are really only a workaround and not a
solution to the root cause of the problem.

Rojhalat Ibrahim


Alex Gonzalez wrote:
> It's a RM9020.
> 
> Quoting Ibrahim's,
> 
> "With a slightly extended patch it actually works. But afterwards
> I get a lot of Illegal instructions and Segmentation faults, where
> there shouldn't be any. Below is the patch I used."
> 
> And after you post an improved patch, he says,
> 
> "I presume CKSEG is CKSEG0 in the above patch. With that it works
> about the same as before. So do you have any clue what the problem
> behind all that really is? Furthermore I still have all those
> "Illegal instruction" and "Segmentation fault" messages that
> shouldn't be there."
> 
> The illegal instructions and segmentation faults turned to be the cpu_has_64bit_gp_regs setting. So I presume it worked for him.
> 
> In our case, it seems to work completely OK. I am running a complete memory test over the whole 1G to be completely sure (with memtester), and I'll report the result back.
> 
> Thanks,
> Alex
> 
> 
> On Fri, 2005-07-22 at 14:14, Ralf Baechle wrote:
> 
>>On Fri, Jul 22, 2005 at 10:04:47AM +0100, Alex Gonzalez wrote:
>>
>>
>>>Our target experienced a kernel panic at startup when trying to access
>>>memory above 512MB.
>>>
>>>Reading the list archives I found this thread with a proposed patch:
>>>
>>>http://www.linux-mips.org/archives/linux-mips/2005-02/msg00115.html
>>>
>>>After applying the patch our target boots OK and appears to be able to
>>>access the whole memory range without problems.
>>>
>>>Any idea why this patch didn't make it to the repository? Is it safe?
>>
>>It is - but according to Ibrahim's posting that you're pointing to it
>>didn't solve his problem.
>>
>>What CPU are you using, btw?
>>
>>  Ralf

  reply	other threads:[~2005-07-25  7:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050721153359Z8225218-3678+3745@linux-mips.org>
2005-07-22  4:30 ` CVS Update@linux-mips.org: linux Ralf Baechle
2005-07-22  9:04   ` Going over 512M of memory Alex Gonzalez
2005-07-22 13:14     ` Ralf Baechle
2005-07-22 13:32       ` Alex Gonzalez
2005-07-25  7:43         ` Rojhalat Ibrahim [this message]
2005-07-25  8:54           ` Alex Gonzalez
2005-07-25  9:23             ` Rojhalat Ibrahim
2005-07-22  9:10   ` Realtime preemption patches Alex Gonzalez
2005-07-22 12:10   ` CVS Update@linux-mips.org: linux Thiemo Seufer
2005-07-22 13:06     ` Ralf Baechle
2005-07-22 13:24       ` Maciej W. Rozycki
2005-07-22 14:00         ` Ralf Baechle
2005-07-22 14:18           ` Thiemo Seufer
2005-07-26 11:12           ` Maciej W. Rozycki
2005-07-22 14:16       ` Thiemo Seufer

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=42E4983C.5030804@rtschenk.de \
    --to=imr@rtschenk.de \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mips@packetvision.com \
    /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.