From: "paul.bilke" <listmail@conspiracy.net>
To: Wolfgang Denk <wd@denx.de>
Cc: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: simple bootloader 2.6.10-rc3 8xx
Date: Tue, 28 Dec 2004 11:12:38 -0600 [thread overview]
Message-ID: <41D19406.2050904@conspiracy.net> (raw)
In-Reply-To: <20041228095119.F07EDC1430@atlas.denx.de>
Actually wd is right, one quick check to see if this is the problem is
to disable the I-Cache. The problem only shows up the the I cache
enabled. I ran my
870 with them disabled for months (I know its painful) until I got the
powers that be to approve wd to spend the time we did not have to fix it.
Some of the best money I ever spent.
Paul
Wolfgang Denk wrote:
>Dear Alex,
>
>in message <313680C9A886D511A06000204840E1CF0A64741E@whq-msgusr-02.pit.comms.marconi.com> you wrote:
>
>
>>
>>
>>
>>>Moving things around in the kernel sometimes
>>>makes this go away but really its just hidden.
>>>In my case it would explode in zlib_inflate also. Putting some output
>>>in the routine would move it ...
>>>
>>>
>>Yes that is exactly what I have observed (but I did'nt have the correct
>>explanation for it)
>>
>>
>
>I think Paul may be right with his suspicion; it sounds like a
>manifestation of the CPU15 problem (but it could also be incorrectly
>initialized SDRAMs which fail during heavy load with burst mode
>accesses, or one more instability of the 2.6 kernel on 8xx systems).
>
>Note that all our work relating to this problem was done on the 2.4
>kernel base, and I make no claims that it might actually help for
>your 2.6 problems.
>
>
>
>>Could this code be used for 2.6 ?
>>
>>
>
>The patch does not apply cleanly as is to the 2.6 tree, but it should
>be simple enough to port.
>
>
>
>>Could someone point me to it, please ?
>>
>>
>
>It's in the linuxppc_2_4_devel tree on our CVS server.
>
>Please find attached the patch to the 2.4 kernel tree which
>implements the workaround, and a test application to reliably
>reproduce the CPU15 errata. It usually takes 1-10 minutes for the
>application to crash, if the workaround is disabled:
>
> bash-2.05b# date; ./cpu15 ; date
> Thu Aug 2 02:02:42 MEST 2001
> Illegal instruction
> Thu Aug 2 02:02:54 MEST 2001
> bash-2.05b# date; ./cpu15 ; date
> Thu Aug 2 02:02:58 MEST 2001
> Illegal instruction
> Thu Aug 2 02:03:48 MEST 2001
> bash-2.05b# date; ./cpu15 ; date
> Thu Aug 2 02:03:54 MEST 2001
> Illegal instruction
> Thu Aug 2 02:03:57 MEST 2001
> bash-2.05b# date; ./cpu15 ; date
> Thu Aug 2 02:04:07 MEST 2001
> Illegal instruction
> Thu Aug 2 02:04:16 MEST 2001
> bash-2.05b#
>
>We noticed that some background activitly, like logging in/out to the
>target via 'telnet', while the application is running over the serial
>console, additionally speeds up the crash.
>
>You can use this command to enable the workaround at run-time (it is
>disabled by default):
>
> bash# sysctl -w kernel.8xx_cpu15=1
>
>Please note that for the h/w problem to show up, the instruction
>cache has to be enabled.
>
>Hope this helps.
>
>Best regards,
>
>Wolfgang Denk
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
next prev parent reply other threads:[~2004-12-28 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 9:51 simple bootloader 2.6.10-rc3 8xx Wolfgang Denk
2004-12-28 17:12 ` paul.bilke [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 0:53 Povolotsky, Alexander
2004-12-28 17:28 Povolotsky, Alexander
2004-12-28 17:47 ` Steven Rostedt
2005-01-05 17:36 ` Tom Rini
2004-12-28 17:48 ` Wolfgang Denk
2004-12-28 3:52 Povolotsky, Alexander
2004-12-27 20:38 Povolotsky, Alexander
2004-12-28 3:30 ` paul.bilke
2004-12-28 9:13 ` Wolfgang Denk
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=41D19406.2050904@conspiracy.net \
--to=listmail@conspiracy.net \
--cc=Alexander.Povolotsky@marconi.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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.