Bus error at 0x0 by sysmmu_fimd (Page table base 0x000 0x00 ad808000)

Bus error at 0x0 by sysmmu_fimd (Page table base 0x000 0x00 ad808000)

[Vijay Kumar]

[-- Attachment #1.1: Type: text/plain, Size: 405 bytes --]

Hii all,
           I am new to this mailing list and i need some help.I am trying
to add exynos iommu support for my board with exynos5250-soc for fimd.I am
getting this error at exynos_sysmmu_irq.I am pretty confused with it and
didn't know what to do.I strucked at this point.So please explain why this
error occurs.My device is attaced correctly to iommu.

Thanks and Regards,
Vijay Kumar Prathipati.

[-- Attachment #1.2: Type: text/html, Size: 481 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: Bus error at 0x0 by sysmmu_fimd (Page table base 0x000 0x00 ad808000)

[Robin Murphy]

On 28/01/16 04:54, Vijay Kumar wrote:
> Hii all,
>             I am new to this mailing list and i need some help.I am trying
> to add exynos iommu support for my board with exynos5250-soc for fimd.I am
> getting this error at exynos_sysmmu_irq.I am pretty confused with it and
> didn't know what to do.I strucked at this point.So please explain why this
> error occurs.My device is attaced correctly to iommu.

It looks like something (either the client device or the sysmmu itself, 
I'm not familiar with that hardware) has tried to access physical 
address 0, and the MMU is raising the interrupt to report that it got an 
error response back for that access. On Exynos 5 that's where the boot 
ROM stuff lives, so there may well be nothing there at all in the 
non-secure memory map. Either way, it's a long way from RAM (which will 
be somewhere above 0x20000000), so you've almost certainly wound up with 
some bogus mapping in your sysmmu page table. First thing I'd try is 
adding a check in exynos_iommu_map() to scream if someone passes in a 
dodgy-looking physical address, then work backwards from there.

Robin.

>
> Thanks and Regards,
> Vijay Kumar Prathipati.
>
>
>
> _______________________________________________
> iommu mailing list
> iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>

Re: Bus error at 0x0 by sysmmu_fimd (Page table base 0x000 0x00 ad808000)

[Vijay Kumar]

[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]

Hii Robin,
                   I debugged  iommu_map function in iommu.c .In that
function exynos_iommu_map is not called .I noticed that is because of size
variable value 0.I made changes but after in exynos_iommu_map function is
throwing an error "Trying Mapping on 1MB@0xc0000000 that is mapped" .Please
help me to solve this issue.I am unable to find why this error occured .

Thanks and Regards,
Vijay Kumar Prathipati.

On Thu, Jan 28, 2016 at 6:38 PM, Robin Murphy <robin.murphy-VeJGdqYn5oNWk0Htik3J/w@public.gmane.org>
wrote:

> On 28/01/16 04:54, Vijay Kumar wrote:
>
>> Hii all,
>>             I am new to this mailing list and i need some help.I am trying
>> to add exynos iommu support for my board with exynos5250-soc for fimd.I am
>> getting this error at exynos_sysmmu_irq.I am pretty confused with it and
>> didn't know what to do.I strucked at this point.So please explain why this
>> error occurs.My device is attaced correctly to iommu.
>>
>
> It looks like something (either the client device or the sysmmu itself,
> I'm not familiar with that hardware) has tried to access physical address
> 0, and the MMU is raising the interrupt to report that it got an error
> response back for that access. On Exynos 5 that's where the boot ROM stuff
> lives, so there may well be nothing there at all in the non-secure memory
> map. Either way, it's a long way from RAM (which will be somewhere above
> 0x20000000), so you've almost certainly wound up with some bogus mapping in
> your sysmmu page table. First thing I'd try is adding a check in
> exynos_iommu_map() to scream if someone passes in a dodgy-looking physical
> address, then work backwards from there.
>
> Robin.
>
>
>> Thanks and Regards,
>> Vijay Kumar Prathipati.
>>
>>
>>
>> _______________________________________________
>> iommu mailing list
>> iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
>> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>>
>>
>

[-- Attachment #1.2: Type: text/html, Size: 2878 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]