Normal 0 false false false RU X-NONE X-NONE MicrosoftInternetExplorer4
Good day everyone!
I have a question on the video driver for Montavista for OMAP-L137. There is one trouble with this driver. A simple application that just records the frame buffer in a loop, causing a system hang within 1-2 hours after the start of (it is reported as: "BUG: soft lockup - CPU#0 stuck for 62s! [swapper:0] ").
This driver was designed for my device "SEED-DEC137" by its manufacturer ("SEED").
I tried to debug this driver and found that by increasing the priority of DMA channel, then soft lockup occurs later. I suppose that the video data delayed between kernel-space to user-space, and when they accumulate too much, the system stops.
// error message.
BUG: soft lockup - CPU#0 stuck for 62s! [swapper:0]
Modules linked in:
Pid: 0, comm: swapper
CPU: 0 Not tainted (2.6.36 #183)
PC is at default_idle+0x34/0x38
LR is at default_idle+0x28/0x38
pc : [<c002c67c>] lr : [<c002c670>] psr: 60000013
sp : c034df90 ip : 600000d3 fp : c034df9c
r10: c0020e14 r9 : 41069265 r8 : c0020e48
r7 : c0350cf4 r6 : c0023014 r5 : c0371950 r4 : c034c000
r3 : 60000013 r2 : 0005217f r1 : 0005317f r0 : 00000000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 0005317f Table: c3094000 DAC: 00000017
...
I ask your advice on how to debug this situation? And also, can write to the framebuffer be delayed in the system?