* RE: BDI2000 and failed MMU translations
@ 2002-01-23 22:22 Gessner, Matt
2002-01-23 22:51 ` Dan Malek
0 siblings, 1 reply; 9+ messages in thread
From: Gessner, Matt @ 2002-01-23 22:22 UTC (permalink / raw)
To: 'Dan Malek', Gessner, Matt; +Cc: 'Linux PPC'
It's straight 2_4. I wasn't stopping at start_kernel though.
I don't have PTBASE set up.
Not sure what I need.
Following some advice from mattl on #mklinux, I'm going to
break at start kernel FIRST, then connect with BDI, then
see if I can look at my data.
THX and Regards,
Matt
> -----Original Message-----
> From: Dan Malek [mailto:dan@embeddededge.com]
> Sent: Wednesday, January 23, 2002 5:24 PM
> To: Gessner, Matt
> Cc: 'Linux PPC'
> Subject: Re: BDI2000 and failed MMU translations
>
>
> Gessner, Matt wrote:
>
>
> > I get a LOT of failed MMU translations reported.
> > Is this b/c I have something misconfigured?
> > I'm running 2.4.18 out of bk on an 860P.
>
> Is it 2_4 or 2_4_devel? I'm travelling for about the next
> week, but will check it out when I return (if I can borrow
> a BDI2000 from someone :-).
>
> Has it worked on previous kernel versions? If so, which ones?
>
> Thanks.
>
>
> -- Dan
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: BDI2000 and failed MMU translations
2002-01-23 22:22 BDI2000 and failed MMU translations Gessner, Matt
@ 2002-01-23 22:51 ` Dan Malek
0 siblings, 0 replies; 9+ messages in thread
From: Dan Malek @ 2002-01-23 22:51 UTC (permalink / raw)
To: Gessner, Matt; +Cc: 'Linux PPC'
Gessner, Matt wrote:
> It's straight 2_4. I wasn't stopping at start_kernel though.
You don't need to stop anywhere unless there are some breakpoints
you want to set for early debug.
> I don't have PTBASE set up.
You need:
MMU XLAT 0xc0000000
PTBASE 0x000000f0
The newer kernels initialize the page table pointers for the BDI2000,
so ignore comments about stopping and setting values. We went through
several iterations of implementation, so anything written about how to
do this manually is probably wrong :-).
> ...... I'm going to
> break at start kernel FIRST, then connect with BDI, then
> see if I can look at my data.
How do you break and then connect the BDI? You need the BDI
connected to set and trap the breakpoint.
Have fun.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: BDI2000 and failed MMU translations
@ 2002-01-23 22:58 Gessner, Matt
2002-01-23 23:34 ` Dan Malek
0 siblings, 1 reply; 9+ messages in thread
From: Gessner, Matt @ 2002-01-23 22:58 UTC (permalink / raw)
To: 'Dan Malek'; +Cc: 'Linux PPC'
Whooops, too soon.
OK, AFTER the first breakpoint, it then gets mad about
single stepping.
The MMU xlation fails for the next address.
Matt
> -----Original Message-----
> From: Dan Malek [mailto:dan@embeddededge.com]
> Sent: Wednesday, January 23, 2002 5:51 PM
> To: Gessner, Matt
> Cc: 'Linux PPC'
> Subject: Re: BDI2000 and failed MMU translations
>
>
> Gessner, Matt wrote:
>
> > It's straight 2_4. I wasn't stopping at start_kernel though.
>
> You don't need to stop anywhere unless there are some breakpoints
> you want to set for early debug.
>
> > I don't have PTBASE set up.
>
> You need:
> MMU XLAT 0xc0000000
> PTBASE 0x000000f0
>
> The newer kernels initialize the page table pointers for the BDI2000,
> so ignore comments about stopping and setting values. We went through
> several iterations of implementation, so anything written about how to
> do this manually is probably wrong :-).
>
> > ...... I'm going to
> > break at start kernel FIRST, then connect with BDI, then
> > see if I can look at my data.
>
> How do you break and then connect the BDI? You need the BDI
> connected to set and trap the breakpoint.
>
> Have fun.
>
>
> -- Dan
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: BDI2000 and failed MMU translations
2002-01-23 22:58 Gessner, Matt
@ 2002-01-23 23:34 ` Dan Malek
0 siblings, 0 replies; 9+ messages in thread
From: Dan Malek @ 2002-01-23 23:34 UTC (permalink / raw)
To: Gessner, Matt; +Cc: 'Linux PPC'
Gessner, Matt wrote:
> Whooops, too soon.
I'm sure it's my fault, I'm sorry.
I started making some changes to support large page sizes and I think
it screwed up the BDI2000. I'll have a patch in as quickly as possible
(yet tonight) and post it. I won't be able to test it with the BDI2000
but it is basically backing out some changes I made.
I apologize.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: BDI2000 and failed MMU translations
@ 2002-01-23 22:57 Gessner, Matt
0 siblings, 0 replies; 9+ messages in thread
From: Gessner, Matt @ 2002-01-23 22:57 UTC (permalink / raw)
To: 'Dan Malek', Gessner, Matt; +Cc: 'Linux PPC'
Ah... breaking at "start_here" works much better...
> -----Original Message-----
> From: Dan Malek [mailto:dan@embeddededge.com]
> Sent: Wednesday, January 23, 2002 5:51 PM
> To: Gessner, Matt
> Cc: 'Linux PPC'
> Subject: Re: BDI2000 and failed MMU translations
>
>
> Gessner, Matt wrote:
>
> > It's straight 2_4. I wasn't stopping at start_kernel though.
>
> You don't need to stop anywhere unless there are some breakpoints
> you want to set for early debug.
>
> > I don't have PTBASE set up.
>
> You need:
> MMU XLAT 0xc0000000
> PTBASE 0x000000f0
>
> The newer kernels initialize the page table pointers for the BDI2000,
> so ignore comments about stopping and setting values. We went through
> several iterations of implementation, so anything written about how to
> do this manually is probably wrong :-).
>
> > ...... I'm going to
> > break at start kernel FIRST, then connect with BDI, then
> > see if I can look at my data.
>
> How do you break and then connect the BDI? You need the BDI
> connected to set and trap the breakpoint.
>
> Have fun.
>
>
> -- Dan
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: BDI2000 and failed MMU translations
@ 2002-01-23 22:55 Gessner, Matt
0 siblings, 0 replies; 9+ messages in thread
From: Gessner, Matt @ 2002-01-23 22:55 UTC (permalink / raw)
To: 'Dan Malek'; +Cc: 'Linux PPC'
Ok,
This still doesn't solve my problem.
In the Makefile:
CONFIG_KERNEL = -g -ggdb
In mpc860.cnf for the bdi:
MMU XLAT 0xc0000000 (this is the default BTW)
PTBASE 0xf0
BREAK SOFT
On the BDI:
bi 0xc0157640 (start_kernel)
go
<breakpoint>
Now, start gdb w/ vmlinux
(gdb) target remote bdi:2001
(gdb) br scc_enet_init
On the BDI it says:
*** MMU: address translation for 0xC015ECB8 failed
(gdb) c
Continuing.
warning: Cannot insert breakpoint 1:
Error accessing memory address 0xc015ecb8: Operation not permitted
I'm using gdb 5.0.
Does this shed any more light?
TIA Dan and all,
Regards,
Matt
> -----Original Message-----
> From: Dan Malek [mailto:dan@embeddededge.com]
> Sent: Wednesday, January 23, 2002 5:51 PM
> To: Gessner, Matt
> Cc: 'Linux PPC'
> Subject: Re: BDI2000 and failed MMU translations
>
>
> Gessner, Matt wrote:
>
> > It's straight 2_4. I wasn't stopping at start_kernel though.
>
> You don't need to stop anywhere unless there are some breakpoints
> you want to set for early debug.
>
> > I don't have PTBASE set up.
>
> You need:
> MMU XLAT 0xc0000000
> PTBASE 0x000000f0
>
> The newer kernels initialize the page table pointers for the BDI2000,
> so ignore comments about stopping and setting values. We went through
> several iterations of implementation, so anything written about how to
> do this manually is probably wrong :-).
>
> > ...... I'm going to
> > break at start kernel FIRST, then connect with BDI, then
> > see if I can look at my data.
>
> How do you break and then connect the BDI? You need the BDI
> connected to set and trap the breakpoint.
>
> Have fun.
>
>
> -- Dan
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* RE: BDI2000 and failed MMU translations
@ 2002-01-23 22:44 Rudolf Ladyzhenskii
0 siblings, 0 replies; 9+ messages in thread
From: Rudolf Ladyzhenskii @ 2002-01-23 22:44 UTC (permalink / raw)
To: 'Gessner, Matt', 'Linux PPC'
I had to patch 8260 version of kernel to get this to work properly. But I
was looking through 860 code and patch for BDI is there.
Check linux start-up file (it is head.S in /arch/ppc/kernel for 8260) and
search for 'abatron' and 'bdi'.
Did you have it to work before?
Rudolf
> -----Original Message-----
> From: Gessner, Matt [mailto:mattg@aiinet.com]
> Sent: Thursday, January 24, 2002 9:08 AM
> To: 'Linux PPC'
> Subject: BDI2000 and failed MMU translations
>
>
>
> Hi, all.
>
> Seeing this is topical right now...
>
> I get a LOT of failed MMU translations reported.
> Is this b/c I have something misconfigured?
> I'm running 2.4.18 out of bk on an 860P.
>
> TIA,
>
> Regards,
>
> Matt
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* BDI2000 and failed MMU translations
@ 2002-01-23 22:08 Gessner, Matt
2002-01-23 22:23 ` Dan Malek
0 siblings, 1 reply; 9+ messages in thread
From: Gessner, Matt @ 2002-01-23 22:08 UTC (permalink / raw)
To: 'Linux PPC'
Hi, all.
Seeing this is topical right now...
I get a LOT of failed MMU translations reported.
Is this b/c I have something misconfigured?
I'm running 2.4.18 out of bk on an 860P.
TIA,
Regards,
Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: BDI2000 and failed MMU translations
2002-01-23 22:08 Gessner, Matt
@ 2002-01-23 22:23 ` Dan Malek
0 siblings, 0 replies; 9+ messages in thread
From: Dan Malek @ 2002-01-23 22:23 UTC (permalink / raw)
To: Gessner, Matt; +Cc: 'Linux PPC'
Gessner, Matt wrote:
> I get a LOT of failed MMU translations reported.
> Is this b/c I have something misconfigured?
> I'm running 2.4.18 out of bk on an 860P.
Is it 2_4 or 2_4_devel? I'm travelling for about the next
week, but will check it out when I return (if I can borrow
a BDI2000 from someone :-).
Has it worked on previous kernel versions? If so, which ones?
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2002-01-23 23:34 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-23 22:22 BDI2000 and failed MMU translations Gessner, Matt
2002-01-23 22:51 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 22:58 Gessner, Matt
2002-01-23 23:34 ` Dan Malek
2002-01-23 22:57 Gessner, Matt
2002-01-23 22:55 Gessner, Matt
2002-01-23 22:44 Rudolf Ladyzhenskii
2002-01-23 22:08 Gessner, Matt
2002-01-23 22:23 ` Dan Malek
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).