[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Test of 0.7.0 driver...
"M.Stein" wrote:
>
> The big change from 0.6.0 to 0.7.0 is, that you don't need to specify base
> and size any longer. The memory is allocated, when test_itifg is started
> with respect to the current frame size. So, if your config file specifies
> a 3kx2k frame, 6Mb are allocated. With the '-n # of buffers' option you
> can also increse this value.
>
> Sorry, there is no up to date documentation to 0.7.0.
>
I found the ITI_SIZE_MAX define to increase the ammount of memory, and I
bumped it up to 32MB. It now starts up OK, but crashes with the
following kernel panic:
Apr 26 11:45:17 pantheon kernel: Unable to handle kernel paging request
at virtual address c8e6effc
Apr 26 11:45:17 pantheon kernel: current->tss.cr3 = 04843000, %cr3 =
04843000
Apr 26 11:45:17 pantheon kernel: *pde = 04111063
Apr 26 11:45:17 pantheon kernel: *pte = 00000000
Apr 26 11:45:17 pantheon kernel: Oops: 0002
Apr 26 11:45:17 pantheon kernel: CPU: 0
Apr 26 11:45:17 pantheon kernel: EIP: 0010:[<c8848e85>]
Apr 26 11:45:17 pantheon kernel: EFLAGS: 00010286
Apr 26 11:45:17 pantheon kernel: eax: c8e6effc ebx: 00000000 ecx:
00000361 edx: 0f00ffaa
Apr 26 11:45:17 pantheon kernel: esi: c48ca5a0 edi: 00000001 ebp:
00601000 esp: c4847f44
Apr 26 11:45:17 pantheon kernel: ds: 0018 es: 0018 ss: 0018
Apr 26 11:45:17 pantheon kernel: Process test_itifg (pid: 639, process
nr: 44, stackpage=c4847000)
Apr 26 11:45:17 pantheon kernel: Stack: 00000000 00601000 c48425b0
07a88025 c4843400 c48ca560 00601000 c8861e44
Apr 26 11:45:17 pantheon kernel: c011b7b4 c4846000 c51a5320
00000001 00000000 c48425b0 00000000 00000000
Apr 26 11:45:17 pantheon kernel: 00000000 c884673b c4831d20
c47da220 401d8000 00601000 c012550a c4831d20
Apr 26 11:45:17 pantheon kernel: Call Trace: [<c8861e44>]
[handle_mm_fault+192/332] [<c884673b>] [sys_read+174/196]
[system_call+52/56]
Apr 26 11:45:17 pantheon kernel: Code: 89 10 c7 44 24 38 00 00 00 00 39
fb 0f 8d c7 00 00 00 8d 6c
Note that you can get this behaviour even when you don't have the camera
plugged into the card.
>>>Tom