All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Kernel crash running omap3-sgx-modules_4.05.00.03 on 3.x kernels
  2013-08-16 12:25 Kernel crash running omap3-sgx-modules_4.05.00.03 on 3.x kernels Kovesdi Gyorgy
@ 2013-08-16 11:31 ` Sundareson, Prabindh
  2013-08-16 14:33   ` Kovesdi Gyorgy
  0 siblings, 1 reply; 3+ messages in thread
From: Sundareson, Prabindh @ 2013-08-16 11:31 UTC (permalink / raw)
  To: Kovesdi Gyorgy, meta-ti mailing list

Hello Kovesdi - 

Have you enabled the clocks - looks like the pvrsrv-init (or an init script of similar name) has not been run before and pvrsrv-ctl is not run ?

regards,
Prabu

-----Original Message-----
From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Kovesdi Gyorgy
Sent: Friday, August 16, 2013 5:56 PM
To: meta-ti mailing list
Subject: [meta-ti] Kernel crash running omap3-sgx-modules_4.05.00.03 on 3.x kernels

Hi,

I have Beagleboard-C4, kerner 3.2.28

At last i could compile libgles and sgx modules version 4.05.00.03 with some hacks, and found the following error running any gles-based application:

[   74.792510] Unhandled fault: external abort on non-linefetch (0x1008) at 
0xd0b00ca8                                                                                              
[   74.800476] Internal error: : 1008 [#1]                                                                                                                                          
[   74.804473] Modules linked in: bufferclass_ti(O) omaplfb(O) pvrsrvkm(O)                                                                                                          
[   74.811370] CPU: 0    Tainted: G           O  (3.2.28 #1)                                                                                                                        
[   74.817108] PC is at PollForValueKM+0x48/0xb8 [pvrsrvkm]                                                                                                                         
[   74.822692] LR is at PollForValueKM+0x38/0xb8 [pvrsrvkm]                                                                                                                         

Previously i tried it on Angstrom with the same result. The kernel can be any 3.x version, the result is also the same. It can run on 2.6 kernels only.

The calltrace is:

[<bf005aa0>] (PollForValueKM+0x48/0xb8 [pvrsrvkm]) from [<bf0117f8>]
(SGXResetInvalDC.isra.2+0x58/0x60 [pvrsrvkm]) [<bf0117f8>] (SGXResetInvalDC.isra.2+0x58/0x60 [pvrsrvkm]) from [<bf011990>] (SGXReset+0x190/0x1ac [pvrsrvkm]) [<bf011990>] (SGXReset+0x190/0x1ac [pvrsrvkm]) from [<bf00ec90>]
(SGXInitialise+0x48/0x110 [pvrsrvkm])
[<bf00ec90>] (SGXInitialise+0x48/0x110 [pvrsrvkm]) from [<bf011c04>]
(SGXPostPowerState+0x4c/0xa0 [pvrsrvkm]) [<bf011c04>] (SGXPostPowerState+0x4c/0xa0 [pvrsrvkm]) from [<bf001778>]
(PVRSRVDevicePostPowerStateKM_AnyVaCb+0x74/0x88 [pvrsrvkm]) [<bf001778>] (PVRSRVDevicePostPowerStateKM_AnyVaCb+0x74/0x88 [pvrsrvkm]) from [<bf008768>] (List_PVRSRV_POWER_DEV_PVRSRV_ERROR_Any_va+0x30/0x58 [pvrsrvkm]) [<bf008768>] (List_PVRSRV_POWER_DEV_PVRSRV_ERROR_Any_va+0x30/0x58 [pvrsrvkm]) from [<bf0019cc>] (PVRSRVSetDevicePowerStateKM+0x6c/0xa8 [pvrsrvkm]) [<bf0019cc>] (PVRSRVSetDevicePowerStateKM+0x6c/0xa8 [pvrsrvkm]) from [<bf00fbf8>] (SGXScheduleCCBCommandKM+0x2c/0xa4 [pvrsrvkm]) [<bf00fbf8>] (SGXScheduleCCBCommandKM+0x2c/0xa4 [pvrsrvkm]) from [<bf00e224>]
(SGXSubmitTransferKM+0x118/0x2b4 [pvrsrvkm]) [<bf00e224>] (SGXSubmitTransferKM+0x118/0x2b4 [pvrsrvkm]) from [<bf014f2c>]
(SGXSubmitTransferBW+0x164/0x170 [pvrsrvkm]) [<bf014f2c>] (SGXSubmitTransferBW+0x164/0x170 [pvrsrvkm]) from [<bf0145b4>]
(BridgedDispatchKM+0xe0/0x138 [pvrsrvkm]) [<bf0145b4>] (BridgedDispatchKM+0xe0/0x138 [pvrsrvkm]) from [<bf00e004>] (PVRSRV_BridgeDispatchKM+0xac/0xec [pvrsrvkm]) [<bf00e004>] (PVRSRV_BridgeDispatchKM+0xac/0xec [pvrsrvkm]) from [<c00ec554>]
(vfs_ioctl+0x20/0x3c)
[<c00ec554>] (vfs_ioctl+0x20/0x3c) from [<c00ecf94>]
(do_vfs_ioctl+0x488/0x4e0)
[<c00ecf94>] (do_vfs_ioctl+0x488/0x4e0) from [<c00ed034>]
(sys_ioctl+0x48/0x70)
[<c00ed034>] (sys_ioctl+0x48/0x70) from [<c000d600>]
(ret_fast_syscall+0x0/0x30)
Code: e59d3004 e1a07000 ea000011 e1a05003 (e5983000)

Regards
György Kövesdi

_______________________________________________
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Kernel crash running omap3-sgx-modules_4.05.00.03 on 3.x kernels
@ 2013-08-16 12:25 Kovesdi Gyorgy
  2013-08-16 11:31 ` Sundareson, Prabindh
  0 siblings, 1 reply; 3+ messages in thread
From: Kovesdi Gyorgy @ 2013-08-16 12:25 UTC (permalink / raw)
  To: meta-ti mailing list

Hi,

I have Beagleboard-C4, kerner 3.2.28

At last i could compile libgles and sgx modules version 4.05.00.03 with some 
hacks, and found the following error running any gles-based application:

[   74.792510] Unhandled fault: external abort on non-linefetch (0x1008) at 
0xd0b00ca8                                                                                              
[   74.800476] Internal error: : 1008 [#1]                                                                                                                                          
[   74.804473] Modules linked in: bufferclass_ti(O) omaplfb(O) pvrsrvkm(O)                                                                                                          
[   74.811370] CPU: 0    Tainted: G           O  (3.2.28 #1)                                                                                                                        
[   74.817108] PC is at PollForValueKM+0x48/0xb8 [pvrsrvkm]                                                                                                                         
[   74.822692] LR is at PollForValueKM+0x38/0xb8 [pvrsrvkm]                                                                                                                         

Previously i tried it on Angstrom with the same result. The kernel can be any 
3.x version, the result is also the same. It can run on 2.6 kernels only.

The calltrace is:

[<bf005aa0>] (PollForValueKM+0x48/0xb8 [pvrsrvkm]) from [<bf0117f8>] 
(SGXResetInvalDC.isra.2+0x58/0x60 [pvrsrvkm])
[<bf0117f8>] (SGXResetInvalDC.isra.2+0x58/0x60 [pvrsrvkm]) from [<bf011990>] 
(SGXReset+0x190/0x1ac [pvrsrvkm])
[<bf011990>] (SGXReset+0x190/0x1ac [pvrsrvkm]) from [<bf00ec90>] 
(SGXInitialise+0x48/0x110 [pvrsrvkm])
[<bf00ec90>] (SGXInitialise+0x48/0x110 [pvrsrvkm]) from [<bf011c04>] 
(SGXPostPowerState+0x4c/0xa0 [pvrsrvkm])
[<bf011c04>] (SGXPostPowerState+0x4c/0xa0 [pvrsrvkm]) from [<bf001778>] 
(PVRSRVDevicePostPowerStateKM_AnyVaCb+0x74/0x88 [pvrsrvkm])
[<bf001778>] (PVRSRVDevicePostPowerStateKM_AnyVaCb+0x74/0x88 [pvrsrvkm]) from 
[<bf008768>] (List_PVRSRV_POWER_DEV_PVRSRV_ERROR_Any_va+0x30/0x58 [pvrsrvkm])
[<bf008768>] (List_PVRSRV_POWER_DEV_PVRSRV_ERROR_Any_va+0x30/0x58 [pvrsrvkm]) 
from [<bf0019cc>] (PVRSRVSetDevicePowerStateKM+0x6c/0xa8 [pvrsrvkm])
[<bf0019cc>] (PVRSRVSetDevicePowerStateKM+0x6c/0xa8 [pvrsrvkm]) from 
[<bf00fbf8>] (SGXScheduleCCBCommandKM+0x2c/0xa4 [pvrsrvkm])
[<bf00fbf8>] (SGXScheduleCCBCommandKM+0x2c/0xa4 [pvrsrvkm]) from [<bf00e224>] 
(SGXSubmitTransferKM+0x118/0x2b4 [pvrsrvkm])
[<bf00e224>] (SGXSubmitTransferKM+0x118/0x2b4 [pvrsrvkm]) from [<bf014f2c>] 
(SGXSubmitTransferBW+0x164/0x170 [pvrsrvkm])
[<bf014f2c>] (SGXSubmitTransferBW+0x164/0x170 [pvrsrvkm]) from [<bf0145b4>] 
(BridgedDispatchKM+0xe0/0x138 [pvrsrvkm])
[<bf0145b4>] (BridgedDispatchKM+0xe0/0x138 [pvrsrvkm]) from [<bf00e004>] 
(PVRSRV_BridgeDispatchKM+0xac/0xec [pvrsrvkm])
[<bf00e004>] (PVRSRV_BridgeDispatchKM+0xac/0xec [pvrsrvkm]) from [<c00ec554>] 
(vfs_ioctl+0x20/0x3c)
[<c00ec554>] (vfs_ioctl+0x20/0x3c) from [<c00ecf94>] 
(do_vfs_ioctl+0x488/0x4e0)
[<c00ecf94>] (do_vfs_ioctl+0x488/0x4e0) from [<c00ed034>] 
(sys_ioctl+0x48/0x70)
[<c00ed034>] (sys_ioctl+0x48/0x70) from [<c000d600>] 
(ret_fast_syscall+0x0/0x30)
Code: e59d3004 e1a07000 ea000011 e1a05003 (e5983000)

Regards
György Kövesdi



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Kernel crash running omap3-sgx-modules_4.05.00.03 on 3.x kernels
  2013-08-16 11:31 ` Sundareson, Prabindh
@ 2013-08-16 14:33   ` Kovesdi Gyorgy
  0 siblings, 0 replies; 3+ messages in thread
From: Kovesdi Gyorgy @ 2013-08-16 14:33 UTC (permalink / raw)
  To: meta-ti mailing list

> Have you enabled the clocks - looks like the pvrsrv-init (or an init script
> of similar name) has not been run before and pvrsrv-ctl is not run ?
How can i check it? In dmesg, there is a "Starting PVR" message, i do not see 
others.
Everything is in default state, i have not changed anything. It works with 
2.6.39 kernel, built the same way.
I found a script '/usr/bin/pvrsrvinit': if i start it after boot then it 
returns immediately without printing anything, and the system fails the same 
way starting any gles application.

Regards
György Kövesdi




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-08-16 13:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-16 12:25 Kernel crash running omap3-sgx-modules_4.05.00.03 on 3.x kernels Kovesdi Gyorgy
2013-08-16 11:31 ` Sundareson, Prabindh
2013-08-16 14:33   ` Kovesdi Gyorgy

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.