Unhandled fault: external abort on non-linefetch (0x1028) at 0xd8050010xternal abort on non-linefetch (0x1028) at 0xd805001

Hi all,

I have been working on solving this error, which i am getting on beagle
board (has arm cortex on it), from quite a few days.

(1) After digging to as much as i can, I found that this error message is
because of a data abort exception, i am getting while i am trying to do a
register read. I am using code sourcery cross compiler to compile kernel
and modules for beagle board.

I checked that the physical base address i am giving is correct. Is there
any way to check the virtual address i got, after ioremap of physical base
address, is in correct memory range or not. I checked for returned virtual
address not being zero and it is not in my case. I am asking more on this
because, i am reading the cause for this case of data abort exceptions is
mostly accessing from a non-initialized pointer, which i am not seeing as
the problem in my error.

And i did not make out, correctly understanding the entire error message
in:
Unhandled fault: external abort on non-linefetch (0x1028) at 0xd8050010
Internal error: : 1028 [#1]
last sysfs file: /sys/class/net/lo/type
Modules linked in: omapfb(+)
CPU: 0    Not tainted  (2.6.32-dirty #127)
PC is at DssInit_forTV+0x8c/0x1a4 [omapfb]
LR is at DssInit_forTV+0x84/0x1a4 [omapfb]
pc : [<bf000f04>]    lr : [<bf000efc>]    psr: 20000013
sp : cfa15e88  ip : 0000163e  fp : 00000000
r10: c0354b48  r9 : cfa14000  r8 : 00000002
r7 : 00000000  r6 : 00000001  r5 : 00050010  r4 : bf001e38
r3 : d8000000  r2 : cfa15e7c  r1 : bf001acd  r0 : bf001aec
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 10c5387d  Table: 8f988019  DAC: 00000015
Process insmod (pid: 823, stack limit = 0xcfa142e8)
Stack: (0xcfa15e88 to 0xcfa16000)
5e80:                   c0354b50 c0354b50 c0354b50 cf9b9340 cfb22c80
bf000798
5ea0: c0354b48 00000002 c0354b50 c0354b50 bf001be8 cf9b9340 c036d408
cfa14000
5ec0: 00000000 c019785c c0354b50 c01969ec c0354b50 c0354b84 bf001be8
cf9b9340
5ee0: c036d408 c0196af8 00000000 c0196a98 bf001be8 c01962c0 cf803af8
cf8423f0
5f00: 00000000 bf001be8 bf001be8 c0195bd8 bf001121 bf001121 00000001
00000000
5f20: bf001cf4 bf001be8 00000000 c0025f88 00000000 c0196dc8 00000000
bf001cf4
5f40: bf005000 00000000 c0025f88 bf005090 00000000 00000000 00000000
c0025334
5f60: 00000000 bf001cf4 00012008 40155008 c0025f88 00000000 bf001cf4
00012008
5f80: 40155008 c006e0d8 40155008 0002daef 00012008 4000e920 00040000
40155008
5fa0: 00000080 c0025de0 4000e920 00040000 40155008 0002daef 00012008
00000001
5fc0: 4000e920 00040000 40155008 00000080 00012008 00000000 00000003
00000000
5fe0: bea30e72 bea30bfc 00008e90 400f1084 60000010 40155008 00000000
00000000
[<bf000f04>] (DssInit_forTV+0x8c/0x1a4 [omapfb]) from [<bf000798>]
(omapfb_probe+0x54/0x30c [omap
fb])
[<bf000798>] (omapfb_probe+0x54/0x30c [omapfb]) from [<c019785c>]
(platform_drv_probe+0x18/0x1c)
[<c019785c>] (platform_drv_probe+0x18/0x1c) from [<c01969ec>]
(driver_probe_device+0xa0/0x14c)
[<c01969ec>] (driver_probe_device+0xa0/0x14c) from [<c0196af8>]
(__driver_attach+0x60/0x84)
[<c0196af8>] (__driver_attach+0x60/0x84) from [<c01962c0>]
(bus_for_each_dev+0x44/0x74)
[<c01962c0>] (bus_for_each_dev+0x44/0x74) from [<c0195bd8>]
(bus_add_driver+0x9c/0x220)
[<c0195bd8>] (bus_add_driver+0x9c/0x220) from [<c0196dc8>]
(driver_register+0xa8/0x130)
[<c0196dc8>] (driver_register+0xa8/0x130) from [<bf005090>]
(omapfb_init+0x90/0xdc [omapfb])
[<bf005090>] (omapfb_init+0x90/0xdc [omapfb]) from [<c0025334>]
(do_one_initcall+0x5c/0x1b4)
[<c0025334>] (do_one_initcall+0x5c/0x1b4) from [<c006e0d8>]
(sys_init_module+0xb8/0x1e8)
[<c006e0d8>] (sys_init_module+0xb8/0x1e8) from [<c0025de0>]
(ret_fast_syscall+0x0/0x2c)
Code: e0811005 eb499c36 e5943000 e59f00f0 (e7931005) 
---[ end trace aa115121a5465365 ]---
Segmentation fault


In above error message:
(1)what is the significance of 0x1028?
(2)PC is at DssInit_forTV+0x8c/0x1a4 [omapfb], in this what are 0x8c and
0x1a4?

Thanks.


	   
					
---------------------------------------		
Posted through http://www.EmbeddedRelated.com