public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: "Marty Leisner" <leisner@rochester.rr.com>
To: linuxppc-embedded@ozlabs.org
Subject: taiga/MPC7448 issues (reboot, nap, DFS)
Date: Thu, 20 Sep 2007 15:38:39 -0400	[thread overview]
Message-ID: <200709201938.l8KJcdEc018680@dell2.home> (raw)

I'm running linux 2.6.20.16 on my taiga board.

Reboot always hangs, and the system needs a power cycle to access the disk again
(just hitting reset doesn't do it).  Does anyone have a patch that fixes this
problem?  Or is it inherent in the hardware design.
(Older kernels exhibit this behavior too...)

I've seen problems with nap and DFS modes...

What happens is peripherals (i.e. ethernet and disk) lose their minds at times
when in this modes...

On the taiga, DFS/2 works fine.   DFS/4 has this problems.
We have another 7448 running at another frequency which only supports DFS/2.
It has the same problems as the taiga when we divide by 4.

Comments?  

(The DFS works within the linux cpufreq system -- when I run on ram disk and use the 
serial console, the byte benchmarks did behave somewhat as expected).

marty

                 reply	other threads:[~2007-09-20 19:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200709201938.l8KJcdEc018680@dell2.home \
    --to=leisner@rochester.rr.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