memory problem about s5pv210 porting

[meng-qy]

Hi,Adam,

The problem has been solved, thank you for your supports!
Indeed, that fault is caused by cache. In file "pagetable-arch", the 
code only flush dcache and do not flush icache which leads to this 
unstable phenomenon.
Now, the system seem to ok after I adding it.

Steven Meng

On 2013年03月01日 19:00, l4-hackers-request at os.inf.tu-dresden.de wrote:
> On Thu Feb 28, 2013 at 21:33:53 +0800, meng-qy wrote:
>> >      Thank you for your suggestion!  Following your guidance, I log the PF info when system dead like this:
>> >  
>> >  test 1:
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       144
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       143
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       142
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       141
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       140
>> >  test 2:
>> >  pf:  000a pfa=20144128 ip=20144128 (r-) spc=0xf12e475c                       105
>> >  pf:  000a pfa=20144128 ip=20144128 (r-) spc=0xf12e475c                       104
>> >  pf:  000a pfa=20144128 ip=20144128 (r-) spc=0xf12e475c                       103
>> >  pf:  000a pfa=20144128 ip=20144128 (r-) spc=0xf12e475c                       102
>> >  test 3:
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       116
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       115
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       114
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       113
>> >  pf:  000a pfa=2016a8f8 ip=2016a8f8 (r-) spc=0xf12e475c                       112
>> >  
>> >       What is spc? pc or sp ? I objdump the image, and did not found that address.
> pc is the program counter, sp is the stack pointer, spc is a kernel
> internal data structure (Space). So this is a code pagefault, likely in
> the roottask/moe.
>
>> >  However,  we can't get more info in dump file because the file didn't include any symbol table(Can we
>> >  dump the symbol table by adding some compile option? ).
> Use fiasco.image file for the kernel.
>
>> >        At last, different from other chip, we found that address
>> >        e0000000-fb000000 in s5pv210 is some important register, and the
>> >        kernel seem to map that address, it doesn't matter?
> What you describe are physical addresses, the kernel uses virtual ones,
> i.e. the virtual address does not point to the physical address. So yes,
> it does not matter.
>
>
>
>
> Adam
> -- Adam adam at os.inf.tu-dresden.de Lackorzynski 
> http://os.inf.tu-dresden.de/~adam/

---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
immediately notify the sender by return e-mail, and delete the original message and all copies from 
your system. Thank you. 
---------------------------------------------------------------------------------------------------