From: leroy christophe <christophe.leroy@c-s.fr>
To: Scott Wood <scottwood@freescale.com>
Cc: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel@vger.kernel.org
Subject: BUG: Patch "Convert some mftb/mftbu into mfspr" breaks MPC885
Date: Wed, 20 Nov 2013 10:37:21 +0100 [thread overview]
Message-ID: <528C82D1.4090803@c-s.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
Scott,
The patch "Convert some mftb/mftbu into mfspr"
(beb2dc0a7a84be003ce54e98b95d65cc66e6e536
<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/powerpc/include/asm/reg.h?id=beb2dc0a7a84be003ce54e98b95d65cc66e6e536>)
breaks startup on MPC885.
The CPU traps (SoftwareEmulation trap) at sched_clock() when trying to
read TBU with mfspr.
Reverting the patch solves the issue.
What's the prefered way to fix this ?
Christophe
[-- Attachment #2: Type: text/html, Size: 1160 bytes --]
next reply other threads:[~2013-11-20 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 9:37 leroy christophe [this message]
2013-11-20 16:57 ` BUG: Patch "Convert some mftb/mftbu into mfspr" breaks MPC885 Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 10:21 leroy christophe
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=528C82D1.4090803@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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).