RE: OMAP3ISP boot problem

RE: OMAP3ISP boot problem

[Alex Gershgorin]

Hi All,

I have problem in booting the Kernel.
Here the problematic part of the boot message.
As I understand it happens when isp_probe calling and it calls isp->iommu_dev = omap_find_iommu_device("isp");

[    1.976715] Linux media interface: v0.10
[    1.981781] Linux video capture interface: v2.00
[    1.989257] omap3isp omap3isp: Revision 2.0 found
[    1.998138] Unable to handle kernel NULL pointer dereference at virtual address 00000050
[    2.006683] pgd = c0004000
[    2.010009] [00000050] *pgd=00000000
[    2.013793] Internal error: Oops: 5 [#1]
[    2.017913] Modules linked in:
[    2.021148] CPU: 0    Tainted: G        W     (3.2.0-rc4-00002-g2d47fa7-dirty #1304)
[    2.029296] PC is at klist_next+0x10/0xc4
[    2.033508] LR is at next_device+0x8/0x14
[    2.037750] pc : [<c03c032c>]    lr : [<c0251e5c>]    psr: 60000013
[    2.037750] sp : c7425eb0  ip : c05e080c  fp : 00000000
[    2.049804] r10: c04b2367  r9 : c058b4f8  r8 : 000003ff
[    2.055297] r7 : 0000000e  r6 : 00000000  r5 : c031827c  r4 : c7425ed0
[    2.062164] r3 : c031827c  r2 : 00000000  r1 : c7425ed0  r0 : 00000024
[    2.069000] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    2.076690] Control: 10c5387d  Table: 80004019  DAC: 00000015
[    2.082733] Process swapper (pid: 1, stack limit = 0xc74242f0)
[    2.088867] Stack: (0xc7425eb0 to 0xc7426000)
[    2.093444] 5ea0:                                     c031827c c04ae343 c031827c c05d7650
[    2.102050] 5ec0: 0000000e c0251e5c c031827c c0251ec8 00000024 00000000 c76e8000 000074e0
[    2.110656] 5ee0: c058b4f0 c030462c 00000000 c01181e4 c058b4f8 c0055f04 00000000 c76e8508
[    2.119232] 5f00: c74976c0 00000000 c05d4fe4 c058b4f8 c058b52c c05d4fe4 c05d4fe4 00000000
[    2.127838] 5f20: 00000000 00000000 00000000 c0252784 c0252770 c02515e4 00000000 c058b4f8
[    2.136444] 5f40: c058b52c c05d4fe4 00000000 c0251708 c05d4fe4 c02516a0 00000000 c0250e20
[    2.145050] 5f60: c7420058 c7481490 c05d4fe4 c76c9140 c05c45d0 c0250768 c04ae33e 00000000
[    2.153656] 5f80: c7423340 c05d4fe4 c056e4cc c000dbfc 00000000 00000000 00000000 c0251d20
[    2.162231] 5fa0: c0583210 c056e4cc c000dbfc 00000000 00000000 c000857c c0582dd0 00003539
[    2.170837] 5fc0: 00000000 c0000000 00000013 c0583210 c0582dd0 c000dbfc 00000013 00000000
[    2.179443] 5fe0: 00000000 c0553204 c7423340 00000000 c0553194 c000dbfc bf0285ff fb000400
[    2.188049] [<c03c032c>] (klist_next+0x10/0xc4) from [<c0251e5c>] (next_device+0x8/0x14)
[    2.196563] [<c0251e5c>] (next_device+0x8/0x14) from [<c0251ec8>] (driver_find_device+0x60/0x78)
[    2.205841] [<c0251ec8>] (driver_find_device+0x60/0x78) from [<c030462c>] (isp_probe+0x238/0xa5c)
[    2.215179] [<c030462c>] (isp_probe+0x238/0xa5c) from [<c0252784>] (platform_drv_probe+0x14/0x18)
[    2.224517] [<c0252784>] (platform_drv_probe+0x14/0x18) from [<c02515e4>] (driver_probe_device+0xc8/0x184)
[    2.234680] [<c02515e4>] (driver_probe_device+0xc8/0x184) from [<c0251708>] (__driver_attach+0x68/0x8c)
[    2.244567] [<c0251708>] (__driver_attach+0x68/0x8c) from [<c0250e20>] (bus_for_each_dev+0x48/0x74)
[    2.254058] [<c0250e20>] (bus_for_each_dev+0x48/0x74) from [<c0250768>] (bus_add_driver+0xa0/0x21c)
[    2.263580] [<c0250768>] (bus_add_driver+0xa0/0x21c) from [<c0251d20>] (driver_register+0xa4/0x130)
[    2.273101] [<c0251d20>] (driver_register+0xa4/0x130) from [<c000857c>] (do_one_initcall+0x98/0x16c)
[    2.282714] [<c000857c>] (do_one_initcall+0x98/0x16c) from [<c0553204>] (kernel_init+0x70/0x118)
[    2.291992] [<c0553204>] (kernel_init+0x70/0x118) from [<c000dbfc>] (kernel_thread_exit+0x0/0x8)
[    2.301208] Code: e92d40f8 e1a04000 e5900000 e5946004 (e590702c)
[    2.307708] ---[ end trace 1b75b31a2719ed1e ]---
[    2.312652] Kernel panic - not syncing: Attempted to kill init!

I will appreciate any help.

Thanks
Alex Gershgorin

Re: OMAP3ISP boot problem

[Sakari Ailus]

Hi Alex,

Alex Gershgorin wrote:
> Hi All,
>
> I have problem in booting the Kernel.
> Here the problematic part of the boot message.
> As I understand it happens when isp_probe calling and it calls isp->iommu_dev = omap_find_iommu_device("isp");
>
> [    1.976715] Linux media interface: v0.10
> [    1.981781] Linux video capture interface: v2.00
> [    1.989257] omap3isp omap3isp: Revision 2.0 found
> [    1.998138] Unable to handle kernel NULL pointer dereference at virtual address 00000050
> [    2.006683] pgd = c0004000
> [    2.010009] [00000050] *pgd=00000000
> [    2.013793] Internal error: Oops: 5 [#1]
> [    2.017913] Modules linked in:
> [    2.021148] CPU: 0    Tainted: G        W     (3.2.0-rc4-00002-g2d47fa7-dirty #1304)
> [    2.029296] PC is at klist_next+0x10/0xc4
> [    2.033508] LR is at next_device+0x8/0x14
> [    2.037750] pc : [<c03c032c>]    lr : [<c0251e5c>]    psr: 60000013
> [    2.037750] sp : c7425eb0  ip : c05e080c  fp : 00000000
> [    2.049804] r10: c04b2367  r9 : c058b4f8  r8 : 000003ff
> [    2.055297] r7 : 0000000e  r6 : 00000000  r5 : c031827c  r4 : c7425ed0
> [    2.062164] r3 : c031827c  r2 : 00000000  r1 : c7425ed0  r0 : 00000024
> [    2.069000] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
> [    2.076690] Control: 10c5387d  Table: 80004019  DAC: 00000015
> [    2.082733] Process swapper (pid: 1, stack limit = 0xc74242f0)
> [    2.088867] Stack: (0xc7425eb0 to 0xc7426000)
> [    2.093444] 5ea0:                                     c031827c c04ae343 c031827c c05d7650
> [    2.102050] 5ec0: 0000000e c0251e5c c031827c c0251ec8 00000024 00000000 c76e8000 000074e0
> [    2.110656] 5ee0: c058b4f0 c030462c 00000000 c01181e4 c058b4f8 c0055f04 00000000 c76e8508
> [    2.119232] 5f00: c74976c0 00000000 c05d4fe4 c058b4f8 c058b52c c05d4fe4 c05d4fe4 00000000
> [    2.127838] 5f20: 00000000 00000000 00000000 c0252784 c0252770 c02515e4 00000000 c058b4f8
> [    2.136444] 5f40: c058b52c c05d4fe4 00000000 c0251708 c05d4fe4 c02516a0 00000000 c0250e20
> [    2.145050] 5f60: c7420058 c7481490 c05d4fe4 c76c9140 c05c45d0 c0250768 c04ae33e 00000000
> [    2.153656] 5f80: c7423340 c05d4fe4 c056e4cc c000dbfc 00000000 00000000 00000000 c0251d20
> [    2.162231] 5fa0: c0583210 c056e4cc c000dbfc 00000000 00000000 c000857c c0582dd0 00003539
> [    2.170837] 5fc0: 00000000 c0000000 00000013 c0583210 c0582dd0 c000dbfc 00000013 00000000
> [    2.179443] 5fe0: 00000000 c0553204 c7423340 00000000 c0553194 c000dbfc bf0285ff fb000400
> [    2.188049] [<c03c032c>] (klist_next+0x10/0xc4) from [<c0251e5c>] (next_device+0x8/0x14)
> [    2.196563] [<c0251e5c>] (next_device+0x8/0x14) from [<c0251ec8>] (driver_find_device+0x60/0x78)
> [    2.205841] [<c0251ec8>] (driver_find_device+0x60/0x78) from [<c030462c>] (isp_probe+0x238/0xa5c)
> [    2.215179] [<c030462c>] (isp_probe+0x238/0xa5c) from [<c0252784>] (platform_drv_probe+0x14/0x18)
> [    2.224517] [<c0252784>] (platform_drv_probe+0x14/0x18) from [<c02515e4>] (driver_probe_device+0xc8/0x184)
> [    2.234680] [<c02515e4>] (driver_probe_device+0xc8/0x184) from [<c0251708>] (__driver_attach+0x68/0x8c)
> [    2.244567] [<c0251708>] (__driver_attach+0x68/0x8c) from [<c0250e20>] (bus_for_each_dev+0x48/0x74)
> [    2.254058] [<c0250e20>] (bus_for_each_dev+0x48/0x74) from [<c0250768>] (bus_add_driver+0xa0/0x21c)
> [    2.263580] [<c0250768>] (bus_add_driver+0xa0/0x21c) from [<c0251d20>] (driver_register+0xa4/0x130)
> [    2.273101] [<c0251d20>] (driver_register+0xa4/0x130) from [<c000857c>] (do_one_initcall+0x98/0x16c)
> [    2.282714] [<c000857c>] (do_one_initcall+0x98/0x16c) from [<c0553204>] (kernel_init+0x70/0x118)
> [    2.291992] [<c0553204>] (kernel_init+0x70/0x118) from [<c000dbfc>] (kernel_thread_exit+0x0/0x8)
> [    2.301208] Code: e92d40f8 e1a04000 e5900000 e5946004 (e590702c)
> [    2.307708] ---[ end trace 1b75b31a2719ed1e ]---
> [    2.312652] Kernel panic - not syncing: Attempted to kill init!
>
> I will appreciate any help.

Just a stupid question... do you have CONFIG_OMAP_IOMMU and 
CONFIG_OMAP_IOVMM enabled? This is a known problem; the real fix 
involves using dmabuf instead of the IOMMU/IOVMM API.

Regards,

-- 
Sakari Ailus
sakari.ailus@iki.fi

RE: OMAP3ISP boot problem

[Alex Gershgorin]

Hi Sakari,

Thank you for your quick response and sorry for stupid question.
Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,  
because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and CONFIG_OMAP_IOMMU.
Please tell me how I can use dmabuf instead of the IOMMU/IOVMM API.

Regards,
Alex Gershgorin
  

Hi Alex,

Alex Gershgorin wrote:
> Hi All,
>
> I have problem in booting the Kernel.
> Here the problematic part of the boot message.
> As I understand it happens when isp_probe calling and it calls isp->iommu_dev = omap_find_iommu_device("isp");
>
> [    1.976715] Linux media interface: v0.10
> [    1.981781] Linux video capture interface: v2.00
> [    1.989257] omap3isp omap3isp: Revision 2.0 found
> [    1.998138] Unable to handle kernel NULL pointer dereference at virtual address 00000050
> [    2.006683] pgd = c0004000
> [    2.010009] [00000050] *pgd=00000000
> [    2.013793] Internal error: Oops: 5 [#1]
> [    2.017913] Modules linked in:
> [    2.021148] CPU: 0    Tainted: G        W     (3.2.0-rc4-00002-g2d47fa7-dirty #1304)
> [    2.029296] PC is at klist_next+0x10/0xc4
> [    2.033508] LR is at next_device+0x8/0x14
> [    2.037750] pc : [<c03c032c>]    lr : [<c0251e5c>]    psr: 60000013
> [    2.037750] sp : c7425eb0  ip : c05e080c  fp : 00000000
> [    2.049804] r10: c04b2367  r9 : c058b4f8  r8 : 000003ff
> [    2.055297] r7 : 0000000e  r6 : 00000000  r5 : c031827c  r4 : c7425ed0
> [    2.062164] r3 : c031827c  r2 : 00000000  r1 : c7425ed0  r0 : 00000024
> [    2.069000] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
> [    2.076690] Control: 10c5387d  Table: 80004019  DAC: 00000015
> [    2.082733] Process swapper (pid: 1, stack limit = 0xc74242f0)
> [    2.088867] Stack: (0xc7425eb0 to 0xc7426000)
> [    2.093444] 5ea0:                                     c031827c c04ae343 c031827c c05d7650
> [    2.102050] 5ec0: 0000000e c0251e5c c031827c c0251ec8 00000024 00000000 c76e8000 000074e0
> [    2.110656] 5ee0: c058b4f0 c030462c 00000000 c01181e4 c058b4f8 c0055f04 00000000 c76e8508
> [    2.119232] 5f00: c74976c0 00000000 c05d4fe4 c058b4f8 c058b52c c05d4fe4 c05d4fe4 00000000
> [    2.127838] 5f20: 00000000 00000000 00000000 c0252784 c0252770 c02515e4 00000000 c058b4f8
> [    2.136444] 5f40: c058b52c c05d4fe4 00000000 c0251708 c05d4fe4 c02516a0 00000000 c0250e20
> [    2.145050] 5f60: c7420058 c7481490 c05d4fe4 c76c9140 c05c45d0 c0250768 c04ae33e 00000000
> [    2.153656] 5f80: c7423340 c05d4fe4 c056e4cc c000dbfc 00000000 00000000 00000000 c0251d20
> [    2.162231] 5fa0: c0583210 c056e4cc c000dbfc 00000000 00000000 c000857c c0582dd0 00003539
> [    2.170837] 5fc0: 00000000 c0000000 00000013 c0583210 c0582dd0 c000dbfc 00000013 00000000
> [    2.179443] 5fe0: 00000000 c0553204 c7423340 00000000 c0553194 c000dbfc bf0285ff fb000400
> [    2.188049] [<c03c032c>] (klist_next+0x10/0xc4) from [<c0251e5c>] (next_device+0x8/0x14)
> [    2.196563] [<c0251e5c>] (next_device+0x8/0x14) from [<c0251ec8>] (driver_find_device+0x60/0x78)
> [    2.205841] [<c0251ec8>] (driver_find_device+0x60/0x78) from [<c030462c>] (isp_probe+0x238/0xa5c)
> [    2.215179] [<c030462c>] (isp_probe+0x238/0xa5c) from [<c0252784>] (platform_drv_probe+0x14/0x18)
> [    2.224517] [<c0252784>] (platform_drv_probe+0x14/0x18) from [<c02515e4>] (driver_probe_device+0xc8/0x184)
> [    2.234680] [<c02515e4>] (driver_probe_device+0xc8/0x184) from [<c0251708>] (__driver_attach+0x68/0x8c)
> [    2.244567] [<c0251708>] (__driver_attach+0x68/0x8c) from [<c0250e20>] (bus_for_each_dev+0x48/0x74)
> [    2.254058] [<c0250e20>] (bus_for_each_dev+0x48/0x74) from [<c0250768>] (bus_add_driver+0xa0/0x21c)
> [    2.263580] [<c0250768>] (bus_add_driver+0xa0/0x21c) from [<c0251d20>] (driver_register+0xa4/0x130)
> [    2.273101] [<c0251d20>] (driver_register+0xa4/0x130) from [<c000857c>] (do_one_initcall+0x98/0x16c)
> [    2.282714] [<c000857c>] (do_one_initcall+0x98/0x16c) from [<c0553204>] (kernel_init+0x70/0x118)
> [    2.291992] [<c0553204>] (kernel_init+0x70/0x118) from [<c000dbfc>] (kernel_thread_exit+0x0/0x8)
> [    2.301208] Code: e92d40f8 e1a04000 e5900000 e5946004 (e590702c)
> [    2.307708] ---[ end trace 1b75b31a2719ed1e ]---
> [    2.312652] Kernel panic - not syncing: Attempted to kill init!
>
> I will appreciate any help.

Just a stupid question... do you have CONFIG_OMAP_IOMMU and
CONFIG_OMAP_IOVMM enabled? This is a known problem; the real fix
involves using dmabuf instead of the IOMMU/IOVMM API.

Regards,

--
Sakari Ailus
sakari.ailus@iki.fi

Re: OMAP3ISP boot problem

[Sakari Ailus]

Alex Gershgorin wrote:
> Hi Sakari,
>
> Thank you for your quick response and sorry for stupid question.
> Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and CONFIG_OMAP_IOMMU.
> Please tell me how I can use dmabuf instead of the IOMMU/IOVMM API.

Unfortunately that real fix isn't available yet and won't be for some 
time. Still, it should be fully functional currently.

Looking at the backtrace again, it seems to crash in 
driver_find_device(). That looks fishy.

Do you have the ISP driver compiled into the kernel? I might try it as a 
module, albeit it of course should work when it's linked to the kernel 
as well.

-- 
Sakari Ailus
sakari.ailus@iki.fi

RE: OMAP3ISP boot problem

[Alex Gershgorin]

> Hi Sakari,
>
> Thank you for your quick response and sorry for stupid question.
> Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and CONFIG_OMAP_IOMMU.
> Please tell me how I can use dmabuf instead of the IOMMU/IOVMM API.

>Unfortunately that real fix isn't available yet and won't be for some
>time. Still, it should be fully functional currently.

>Looking at the backtrace again, it seems to crash in
>driver_find_device(). That looks fishy.

>Do you have the ISP driver compiled into the kernel? I might try it as a
>module, albeit it of course should work when it's linked to the kernel
>as well.

Yes ISP driver compiled into kernel, but if I back to previos version of the Linux kernel  3.0.0, that works well.
Here part of kernel boot message...

> [    2.063354] Linux media interface: v0.10
> [    2.068298] Linux video capture interface: v2.00
> [    2.075561] omap3isp omap3isp: Revision 2.0 found
> [    2.080932] omap-iommu omap-iommu.0: isp: version 1.1
> [    2.099365] Camera Video probed
> [    2.115997] vivi-000: V4L2 device registered as video7

Now I plan to start  using a newer version of the Linux kernel 3.2.0-rc4, but unfortunately faced with the problem.
That suggest?

Thanks,
Alex Gershgorin 

Re: OMAP3ISP boot problem

[Laurent Pinchart]

Hi Alex,

On Saturday 10 December 2011 14:36:17 Alex Gershgorin wrote:
> > Hi Sakari,
> > 
> > Thank you for your quick response and sorry for stupid question.
> > Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> > because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and
> > CONFIG_OMAP_IOMMU. Please tell me how I can use dmabuf instead of the
> > IOMMU/IOVMM API.
> >
> >Unfortunately that real fix isn't available yet and won't be for some
> >time. Still, it should be fully functional currently.
> >
> >Looking at the backtrace again, it seems to crash in
> >driver_find_device(). That looks fishy.
> >
> >Do you have the ISP driver compiled into the kernel? I might try it as a
> >module, albeit it of course should work when it's linked to the kernel
> >as well.
> 
> Yes ISP driver compiled into kernel, but if I back to previos version of
> the Linux kernel  3.0.0, that works well. Here part of kernel boot
> message...
> 
> > [    2.063354] Linux media interface: v0.10
> > [    2.068298] Linux video capture interface: v2.00
> > [    2.075561] omap3isp omap3isp: Revision 2.0 found
> > [    2.080932] omap-iommu omap-iommu.0: isp: version 1.1
> > [    2.099365] Camera Video probed
> > [    2.115997] vivi-000: V4L2 device registered as video7
> 
> Now I plan to start  using a newer version of the Linux kernel 3.2.0-rc4,
> but unfortunately faced with the problem. That suggest?

I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when 
loading the omap3-isp driver. I've tried compiling the driver in the kernel 
and as a module, and both succeeded. I've pushed my code to 
http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
sensors-board if you want to give it a try.

-- 
Regards,

Laurent Pinchart

RE: OMAP3ISP boot problem

[Alex Gershgorin]

Hi Alex,

On Saturday 10 December 2011 14:36:17 Alex Gershgorin wrote:
> > Hi Sakari,
> >
> > Thank you for your quick response and sorry for stupid question.
> > Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> > because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and
> > CONFIG_OMAP_IOMMU. Please tell me how I can use dmabuf instead of the
> > IOMMU/IOVMM API.
> >
> >Unfortunately that real fix isn't available yet and won't be for some
> >time. Still, it should be fully functional currently.
> >
> >Looking at the backtrace again, it seems to crash in
> >driver_find_device(). That looks fishy.
> >
> >Do you have the ISP driver compiled into the kernel? I might try it as a
> >module, albeit it of course should work when it's linked to the kernel
> >as well.
>
> Yes ISP driver compiled into kernel, but if I back to previos version of
> the Linux kernel  3.0.0, that works well. Here part of kernel boot
> message...
>
> > [    2.063354] Linux media interface: v0.10
> > [    2.068298] Linux video capture interface: v2.00
> > [    2.075561] omap3isp omap3isp: Revision 2.0 found
> > [    2.080932] omap-iommu omap-iommu.0: isp: version 1.1
> > [    2.099365] Camera Video probed
> > [    2.115997] vivi-000: V4L2 device registered as video7
>
> Now I plan to start  using a newer version of the Linux kernel 3.2.0-rc4,
> but unfortunately faced with the problem. That suggest?

I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when
loading the omap3-isp driver. I've tried compiling the driver in the kernel
and as a module, and both succeeded. I've pushed my code to
http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
sensors-board if you want to give it a try.

Thanks Laurent,

Tomorrow I'll try to test on Hardware that I have with using kernel 3.2-rc2
and Tell you about my results.

Regards,
Alex Gershgorin

RE: OMAP3ISP boot problem

[Alex Gershgorin]

Hi Laurent,

On Saturday 10 December 2011 14:36:17 Alex Gershgorin wrote:
> > Hi Sakari,
> >
> > Thank you for your quick response and sorry for stupid question.
> > Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
> > because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM  and
> > CONFIG_OMAP_IOMMU. Please tell me how I can use dmabuf instead of the
> > IOMMU/IOVMM API.
> >
> >Unfortunately that real fix isn't available yet and won't be for some
> >time. Still, it should be fully functional currently.
> >
> >Looking at the backtrace again, it seems to crash in
> >driver_find_device(). That looks fishy.
> >
> >Do you have the ISP driver compiled into the kernel? I might try it as a
> >module, albeit it of course should work when it's linked to the kernel
> >as well.
>
> Yes ISP driver compiled into kernel, but if I back to previos version of
> the Linux kernel  3.0.0, that works well. Here part of kernel boot
> message...
>
> > [    2.063354] Linux media interface: v0.10
> > [    2.068298] Linux video capture interface: v2.00
> > [    2.075561] omap3isp omap3isp: Revision 2.0 found
> > [    2.080932] omap-iommu omap-iommu.0: isp: version 1.1
> > [    2.099365] Camera Video probed
> > [    2.115997] vivi-000: V4L2 device registered as video7
>
> Now I plan to start  using a newer version of the Linux kernel 3.2.0-rc4,
> but unfortunately faced with the problem. That suggest?

>I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when
>loading the omap3-isp driver. I've tried compiling the driver in the kernel
>and as a module, and both succeeded. I've pushed my code to
>http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp-
>sensors-board if you want to give it a try.

>Thanks Laurent,

>Tomorrow I'll try to test on Hardware that I have with using kernel 3.2-rc2
>and Tell you about my results.

>Regards,
>Alex Gershgorin

Present result is much better, I tested it on kernel 3.2.0-rc5 and the registration is successful.
Here part of my boot message:

[    1.926635] Linux video capture interface: v2.00
[    1.936553] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
[    1.959472] omap-iommu omap-iommu.0: isp registered
*******
*******
*******
[    2.043945] omap_i2c omap_i2c.3: bus 3 rev1.3.12 at 400 kHz
[    2.056945] omap3isp omap3isp: Revision 2.0 found
[    2.062622] omap-iommu omap-iommu.0: isp: version 1.1
[    2.082092] camera 3-0057: Probing CAMERA at address 0x57
[    2.088439] camera 3-0057: CAMERA detected at address 0x57

I honestly didn't understand where's the catch .

Many thanks to all.

Regards,
Alex Gershgorin