Problems with MMU: address translation for 0xXXXXXXXX failed

[Wolfgang Denk]

In message <3EC07D9A.6050604 at embeddededge.com> you wrote:
>
> If that doesn't work, just out of curiosity use hard breakpoints (set
> BREAKMODE HARD).  Just test it setting one breakpoint.  If this works,
> I suspect the BDI is honoring the write protection (via the MMU) on the
> kernel text pages and we can't set a soft breakpoint.  In this case, we'll
> have to add a kernel configuration to allow a debugger write.  The
> CONFIG_KGDB and CONFIG_XMON enable the text writing, but they also add
> too much baggage and could interfere with the BDI.  It's another thing

It should be sufficient to enable  CONFIG_BDI_SWITCH  in  the  kernel
configuration (after enabling CONFIG_DEBUG_KERNEL).


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.

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