From: Wolfgang Denk <wd@denx.de>
To: Lucinda Schafer <lucsch@adaptivemicro.com>
Cc: Patrick Lerda <Lerda@microprocess.com>,
"'Dan Malek'" <dan@netx4.com>,
Nguyen Xuan Hoang <hoang_nguyen@op.com.sg>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: MMU problems?
Date: Thu, 22 Jun 2000 19:25:04 +0200 [thread overview]
Message-ID: <200006221725.TAA04909@denx.local.net> (raw)
In-Reply-To: Your message of "Thu, 22 Jun 2000 08:44:29 CDT." <A109131318C4D1119AC20060088DECE330F4B1@amwmail.adaptivemicro.com>
In message <A109131318C4D1119AC20060088DECE330F4B1@amwmail.adaptivemicro.com> you wrote:
>
> I agree. I believe we ARE dealing with a kernel bug, and it is particular to
> the MPC823.
What makes you think so? Have you run the same hardware with other
CPUs without problems? Have you seen other "good" hardware (TQ
Components, Embedded Planet) having with similar problems, and only
when running with 823 CPUs?
> Let's hear some success stories--embedded units in production, running in
> the field for days, shutting down power and rebooting with no kernel panics.
> That may help convince me we are dealing with a hardware issue.
OK, then here is a success story.
I have several systems in test here, a mix of 823, 850, 860, -DE, -T,
-SR, and some development systems are in permanent use by my
customers, and I can't say I see any differences between the CPU's.
Booting or shutting down was _never_ a problem. We had the usual
crashes whith early versions of 2.2.13 when running low on memory,
but that's fixed.
With recent kernels (for instance, the 2.2.13 version from MV) I
haven't problems for a _very_ long time (except for the 2.4.0 test
kernels - but I don't use these in production yet).
Did you check if environmental parameters make any difference? How
stable is your power supply - are the voltages for your board clean
and within limits?
Did you measure CPU temperatures, or did you try cooling the CPU's? I
remember early versions of some TQ modules (MPC821 + Adaptec SCSI
controller on a credit card sized modules) which got too hot and
stopped working.
And yes, I just compiled (once more) a Linux kernel on one of my
boxes (that's why I reply so late - it takes more than 140 minutes
with a NFS based root filsystem and 16 MB of RAM). You are right, it
makes kind of a good regression test - it streeses all of CPU, I/O
and (with NFS root) networking.
You asked for success stories: It works for me.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Virtual" means never knowing where your next byte is coming from.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-22 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-22 13:44 MMU problems? Lucinda Schafer
2000-06-22 14:19 ` Daris Nevil
2000-06-22 17:25 ` Wolfgang Denk [this message]
[not found] <17B78BDF120BD411B70100500422FC63079FA3@IIS000>
2000-06-25 16:41 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2000-06-23 8:06 Patrick Lerda
2000-06-23 7:43 Patrick Lerda
2000-06-23 8:32 ` Wolfgang Denk
2000-06-22 7:01 Patrick Lerda
2000-06-22 15:58 ` Dan Malek
1999-12-22 4:02 Nguyen Xuan Hoang
2000-06-22 3:56 ` Dan Malek
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=200006221725.TAA04909@denx.local.net \
--to=wd@denx.de \
--cc=Lerda@microprocess.com \
--cc=dan@netx4.com \
--cc=hoang_nguyen@op.com.sg \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=lucsch@adaptivemicro.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 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).