From: Gautam Borad <gautam@eisodus.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: frequent sig 11 with malloc() on mpc8xx
Date: Fri, 05 May 2006 19:30:56 +0530 [thread overview]
Message-ID: <445B5A98.8020004@eisodus.com> (raw)
In-Reply-To: <20060505094007.0F169353AD3@atlas.denx.de>
Wolfgang Denk wrote:
>No, of course not. Please read the FAQ to understand why standard RAM
>tests will never detect this type of problem.
>
>Best regards,
>
>Wolfgang Denk
>
>
>
Thanks for the reply.
We are aware that its a FAQ and we rechecked the SDRAM configuration,
everything seems fine.
We disabled burst mode and tried but that didnt help. Now we want to
disable cache and check.
Is the cache disabled from u-boot or linux? Where do we have to modify
the code to disable
the cache completely. Basically we want to run the linux without using
cache.
regards,
gautam.
next prev parent reply other threads:[~2006-05-05 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 7:48 frequent sig 11 with malloc() on mpc8xx Gautam Borad
2006-05-04 14:46 ` Wolfgang Denk
2006-05-04 15:46 ` David Jander
2006-05-05 8:43 ` Gautam Borad
2006-05-05 9:40 ` Wolfgang Denk
2006-05-05 14:00 ` Gautam Borad [this message]
2006-05-05 14:17 ` Mark Chambers
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=445B5A98.8020004@eisodus.com \
--to=gautam@eisodus.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).