linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Timothy Ritchey <tritchey@vacuumgenesis.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kswapd Oops
Date: Mon, 15 Jan 2001 13:45:57 -0500	[thread overview]
Message-ID: <3A634565.ED2F77C6@mvista.com> (raw)
In-Reply-To: 3A6342EA.DEA7FA9B@vacuumgenesis.com


Timothy Ritchey wrote:

> That is what I figured, although I had to make some changes to get the
> FEC driver to compile

Hmmm...you may have grabbed something a little old.  I would suggest
starting with the Embedded Planet "CLLF" LSP.

> > Are you including the software work arounds for the CPU6 silicon
> > errata?
>
> yes

Although it shouldn't be causing the trouble, there is/was a bug
in the code with this option enabled.  Check the file
arch/ppc/kernel/head.S and make sure the 'cpu6_bug' buffer is
declared '.space 16' instead of '.space 4'.

> ARRRGGGGHHH. You can't imagine how much this pains me. Well.... perhaps
> you can :)

Yes, I can.  You are not the first to see this and won't be the
last.  I have been very fortunate to work with some awesome hardware
engineers in the past, where the the first round of hardware had
high speed logic connectors to the processor bus.  The MPC8xx
memory controller can do some pretty weird things, all legitimate
and logical, and not something you will comprehend from reading
the manual.  You have to see it in action, especially when running Linux.

> .... I am going to disable everything I can WRT caches, etc. and
> see if it clears up.

Another thing to test is setting burst inhibit in the ORx for the DRAM.
This will prevent the CPM DMA from generating burst cycles as well.
Most people can get the single cycle memory operations working because
the timing isn't as critical and there is lots of overhead so a few
wasted clock cycles are seldom noticed.  Burst mode has to be perfect.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-01-15 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15  1:36 kswapd Oops Timothy Ritchey
2001-01-15  5:37 ` Dan Malek
2001-01-15 17:16   ` Timothy Ritchey
2001-01-15 17:22     ` Dan Malek
2001-01-15 18:35       ` Timothy Ritchey
2001-01-15 18:45         ` Dan Malek [this message]

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=3A634565.ED2F77C6@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=tritchey@vacuumgenesis.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).