From: Michael Neuling <mikey@neuling.org>
To: "Gorelik, Jacob (335F)" <jacob.gorelik@jpl.nasa.gov>
Cc: Linux PPC dev <linuxppc-dev@ozlabs.org>
Subject: Re: powerpc: Hardware breakpoints rewrite to handle non DABR breakpoint registers
Date: Fri, 17 May 2013 14:27:14 +1000 [thread overview]
Message-ID: <30348.1368764834@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <3F431E22-B7A9-4FCF-B34F-DC171A643E05@jpl.nasa.gov>
Hi,
> I assume you are the right person to ask this question.
Yep I am but adding linuxppc-dev mailing list to CC anyway.
> We are running the Linux kernel version 3.8.13 on a PPC750FX 32-bit
> based board without any problems; however, when I tried to boot
> version 3.9.2 on the same board, I get the following error:
>
> Mount-cache hash table entries: 512
> Oops: Exception in kernel mode, sig: 4 [#1]
> BRE750FX
> Modules linked in:
> NIP: c0007210 LR: c00072ac CTR: c00403c0
> REGS: c039be90 TRAP: 0700 Not tainted (3.9.0-svn1447)
> MSR: 00081032 <ME,IR,DR,RI> CR: 22000082 XER: 00000000
> TASK = c03833a8[0] 'swapper' THREAD: c039a000
> GPR00: c029466c c039bf40 c03833a8 00000000 00000000 00000001 00000000 00000000
> GPR08: c0383fe4 00000000 00000000 00000000 42000022 1001a6e4 00000000 100ce000
> GPR16: 00000000 00000001 00000000 00000024 00000001 c02a0000 c03a0000 c02a0000
> GPR24: c0386864 00000004 c038796c c039a000 cf4303d0 c0386490 c0386490 c03833a8
> NIP [c0007210] set_breakpoint+0x48/0x54
> LR [c00072ac] __switch_to+0x90/0x98
> Call Trace:
> [c039bf40] [c00404e4] pick_next_task_fair+0x124/0x1c0 (unreliable)
> [c039bf60] [c029466c] __schedule+0x17c/0x358
> [c039bfa0] [c0294ad0] schedule_preempt_disabled+0x10/0x20
> [c039bfb0] [c0004090] rest_init+0x60/0x70
> [c039bfc0] [c035ed60] start_kernel+0x2c4/0x2d8
> [c039bff0] [00003438] 0x3438
> Instruction dump:
> 2f890000 81630004 80e30000 5483077e 5484ef7e 91480000 91680004 7c633b78
> 419e000c 7d2903a6 4e800420 7c75fba6 <7c97fba6> 38600000 4e800020 9421ffe0
Last two instruction here are:
7c 75 fb a6 mtspr 1013,r3
7c 97 fb a6 mtspr 1015,r4 ****
The SPR 1015 is the dabrx.
Looking at the 970FX docs, it has the DABR but not DABRX. I didn't
realise that this config ever existed so I'm going to have to code
something up to fix it.
Meanwhile the below should get you going. Let me know if it works.
This patch is not for upstream.
Not-at-all-signed-off-by: Michael Neuling <mikey@neuling.org> :-)
Mikey
diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index a902723..df9eb8e 100644
--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -399,7 +399,6 @@ static inline int __set_dabr(unsigned long dabr, unsigned lo
static inline int __set_dabr(unsigned long dabr, unsigned long dabrx)
{
mtspr(SPRN_DABR, dabr);
- mtspr(SPRN_DABRX, dabrx);
return 0;
}
#else
next parent reply other threads:[~2013-05-17 4:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F431E22-B7A9-4FCF-B34F-DC171A643E05@jpl.nasa.gov>
2013-05-17 4:27 ` Michael Neuling [this message]
2013-05-17 6:27 ` [PATCH] powerpc/hw_breakpoints: Add DABRX cpu feature Michael Neuling
2013-06-04 1:59 ` Michael Neuling
2013-06-06 4:28 ` Michael Neuling
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=30348.1368764834@ale.ozlabs.ibm.com \
--to=mikey@neuling.org \
--cc=jacob.gorelik@jpl.nasa.gov \
--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).