From: "Gerhard Pircher" <gerhard_pircher@gmx.net>
To: "Leisner, Martin" <Martin.Leisner@xerox.com>, linuxppc-dev@ozlabs.org
Cc: Nathan.Lund@xerox.com
Subject: Re: 7448/2.6.20 problems (double boots or hangs)
Date: Wed, 19 Mar 2008 23:31:45 +0100 [thread overview]
Message-ID: <20080319223145.249840@gmx.net> (raw)
In-Reply-To: <556445368AFA1C438794ABDA8901891C084C2113@USA0300MS03.na.xerox.net>
-------- Original-Nachricht --------
> Datum: Wed, 19 Mar 2008 17:52:16 -0400
> Von: "Leisner, Martin" <Martin.Leisner@xerox.com>
> An: linuxppc-dev@ozlabs.org
> CC: "Lund, Nathan \\(Nathan.Lund@usa.xerox.com\\)" <Nathan.Lund@xerox.com>
> Betreff: 7448/2.6.20 problems (double boots or hangs)
> My taiga board is now dead -- on our development board (with a taiga
> kernel
> and a custom modified dts) we see either
>
>
> 1) it hangs at the same point ("PID has table entries")
> or
> 2) it boots but it seems to restart the boot process after the "PID hash
> table entries line"
I observed the same behavior on my AmigaOne, if the PAGE_COHERENT flag was
set for page mappings by CPU_FTR_NEED_COHERENT. The 7448 CPU doesn't need
CPU_FTR_NEED_COHERENT to be set (no CPU bug that needs to be worked
around), but there is no define for the 7448 in arch/powerpc/cputable.h in
kernel v2.6.20 (but it's in v2.6.22!). Thus I guess it is detected as a
744[0|5|7], which have this flag set.
On the other side my hardware is _very_ buggy, so it's unlikely that this
could be the problem on your hardware.
Gerhard
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
prev parent reply other threads:[~2008-03-19 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 21:52 7448/2.6.20 problems (double boots or hangs) Leisner, Martin
2008-03-19 22:31 ` Gerhard Pircher [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=20080319223145.249840@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=Martin.Leisner@xerox.com \
--cc=Nathan.Lund@xerox.com \
--cc=linuxppc-dev@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).