omapfb not initialised - ioremap failure

This is fixed by (after cleaning up the patch): http://permalink.gmane.org/gmane.linux.ports.arm.omap/41348

Tested fix on Beagle C4 and xM.

Nico, mind merging http://permalink.gmane.org/gmane.linux.ports.arm.omap/41348 into linux-linaro stable and -next?

Thanks

This bug was fixed in the package linux-linaro - 2.6.35-1004.9

---------------
linux-linaro (2.6.35-1004.9) maverick; urgency=low

  [ Upstream Kernel Changes ]

  * ARM: OMAP: Beagle: revision detection
    - LP: #613855
  * ARM: OMAP: Beagle: only Cx boards use pin 23 for write protect
    - LP: #613855
  * ARM: OMAP: Beagle: no gpio_wp pin connection on xM
    - LP: #613855
  * OMAP: DSS2: OMAPFB: use phys_to_virt for RAM mappings
    - LP: #624115
 -- John Rigby <email address hidden> Fri, 27 Aug 2010 20:27:29 -0600

On my Rev A2 Beagle-XM using the beta candidate:

cat /proc/cmdline
console=tty0 console=ttyS2,115200n8 earlyprintk fixrtc nocompcache root=UUID=1a62aa74-64be-43ec-90da-4a8272f3f293 rootwait ro vram=12M omapfb.debug=y omapfb.mode=dvi:1280x720MR-16@60

at bootup the following is seen in the dmsg:

[ 6.822784] ------------[ cut here ]------------
[ 6.827514] WARNING: at /build/buildd/linux-linaro-2.6.35/arch/arm/mm/ioremap.c:207 __arm_ioremap_pfn_caller+0x20c/0x214()
[ 6.838745] Modules linked in:
[ 6.841918] [<c004a3e0>] (unwind_backtrace+0x0/0x100) from [<c05074b8>] (dump_stack+0x18/0x1c)
[ 6.850708] [<c05074b8>] (dump_stack+0x18/0x1c) from [<c008054c>] (warn_slowpath_common+0x5c/0x6c)
[ 6.859832] [<c008054c>] (warn_slowpath_common+0x5c/0x6c) from [<c0080580>] (warn_slowpath_null+0x24/0x2c)
[ 6.869659] [<c0080580>] (warn_slowpath_null+0x24/0x2c) from [<c004f1c4>] (__arm_ioremap_pfn_caller+0x20c/0x214)
[ 6.879974] [<c004f1c4>] (__arm_ioremap_pfn_caller+0x20c/0x214) from [<c004f248>] (__arm_ioremap_caller+0x5c/0x64)
[ 6.890502] [<c004f248>] (__arm_ioremap_caller+0x5c/0x64) from [<c0062bc8>] (omap_ioremap+0x7c/0x90)
[ 6.899780] [<c0062bc8>] (omap_ioremap+0x7c/0x90) from [<c02dba7c>] (omapfb_alloc_fbmem+0x94/0x1ec)
[ 6.908996] [<c02dba7c>] (omapfb_alloc_fbmem+0x94/0x1ec) from [<c02dbc80>] (omapfb_alloc_fbmem_display+0xac/0x19c)
[ 6.919494] [<c02dbc80>] (omapfb_alloc_fbmem_display+0xac/0x19c) from [<c02dbf48>] (omapfb_allocate_all_fbs+0x1d8/0x260)
[ 6.930541] [<c02dbf48>] (omapfb_allocate_all_fbs+0x1d8/0x260) from [<c02dce3c>] (omapfb_create_framebuffers+0x1a8/0x4c8)
[ 6.941650] [<c02dce3c>] (omapfb_create_framebuffers+0x1a8/0x4c8) from [<c02dd2e8>] (omapfb_probe+0x18c/0x488)
[ 6.951812] [<c02dd2e8>] (omapfb_probe+0x18c/0x488) from [<c03124e8>] (platform_drv_probe+0x20/0x24)
[ 6.961120] [<c03124e8>] (platform_drv_probe+0x20/0x24) from [<c031106c>] (really_probe+0x6c/0x168)
[ 6.970306] [<c031106c>] (really_probe+0x6c/0x168) from [<c03111b8>] (driver_probe_device+0x50/0x68)
[ 6.979583] [<c03111b8>] (driver_probe_device+0x50/0x68) from [<c0311264>] (__driver_attach+0x94/0x98)
[ 6.989044] [<c0311264>] (__driver_attach+0x94/0x98) from [<c0310784>] (bus_for_each_dev+0x68/0x94)
[ 6.998229] [<c0310784>] (bus_for_each_dev+0x68/0x94) from [<c0310f10>] (driver_attach+0x24/0x28)
[ 7.007232] [<c0310f10>] (driver_attach+0x24/0x28) from [<c030febc>] (bus_add_driver+0xd8/0x328)
[ 7.016174] [<c030febc>] (bus_add_driver+0xd8/0x328) from [<c0311550>] (driver_register+0x80/0x198)
[ 7.025360] [<c0311550>] (driver_register+0x80/0x198) from [<c0312a3c>] (platform_driver_register+0x5c/0x60)
[ 7.035339] [<c0312a3c>] (platform_driver_register+0x5c/0x60) from [<c0026654>] (omapfb_init+0x38/0x54)
[ 7.044891] [<c0026654>] (omapfb_init+0x38/0x54) from [<c00423c4>] (do_one_initcall+0x3c/0x1dc)
[ 7.053741] [<c00423c4>] (do_one_initcall+0x3c/0x1dc) from [<c00085b4>] (do_basic_setup+0x64/0x74)
[ 7.062835] [<c00085b4>] (do_basic_setup+0x64/0x74) from [<c0008654>] (kernel_init+0x90/0x120)
[ 7.071594] [<c0008654>] (kernel_init+0x90/0x120) from [<c0043b04>] (kernel_thread_exit+0x0/0x8)
[ 7.08053...

The Daily 0831-2 build does not have this issue on either my Rev C4 Beagle nor does it have this issue on my Rev A2 Beagle XM

I think this bug can be marked fixed.

Tom, the bug is marked as fixed in the ubuntu/linux-linaro source package, but there's an open task in merging that fix in git.linaro.org/kernel/linux-linaro*.git trees.

The fix has been committed to git.linaro.org/kernel/linux-linaro-2.6.35.git:

http://git.linaro.org/gitweb?p=kernel/linux-linaro-2.6.35.git;a=commit;h=a0e1e0f754955ad1237ff38286717773b58168c1

but not git://git.linaro.org/kernel/linux-linaro-next.git

Done, plus a few others.

On Wed, 1 Sep 2010, John Rigby wrote:

> The fix has been committed to git.linaro.org/kernel/linux-
> linaro-2.6.35.git:
>
> http://git.linaro.org/gitweb?p=kernel/linux-
> linaro-2.6.35.git;a=commit;h=a0e1e0f754955ad1237ff38286717773b58168c1
>
> but not git://git.linaro.org/kernel/linux-linaro-next.git
>
> --
> omapfb not initialised - ioremap failure
> https://bugs.launchpad.net/bugs/624115
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Linaro Linux: Triaged
> Status in “linux-linaro” package in Ubuntu: Fix Released
>
> Bug description:
> omapfb does not seem to work for me in the linaro trees right now.
>
> Tested on Beagle C3 (I've also had reports of similar problems with omapfb on OMAP3EVM).
>
>
> I tried the following kernel trees and configurations (actual files attached below)
>
> git://git.linaro.org/ubuntu/linux-linaro.git (linaro-2.6.35-2 branch)
> HEAD is ea914bd44cd2b7c31313a2c72225471b2bedbdce
>
> Successful build:
> * config: config-linaro_linaro-2.6.35-2
> * build log: make.log-linaro_linaro-2.6.35-2
> * dmesg output: dmesg-linaro_linaro-2.6.35-2.txt
>
> 8<--
> [ 1.833618] OMAPFB: omapfb_init
> [ 1.833740] OMAPFB: omapfb_probe
> [ 1.833831] fbcvt: 1280x720@60: CVT Name - .921M9-R
> [ 1.838867] OMAPFB: create 3 framebuffers
> [ 1.838897] OMAPFB: fb_infos allocated
> [ 1.838928] OMAPFB: allocating 1843200 bytes for fb 0
> [ 1.850341] ------------[ cut here ]------------
> [ 1.855102] WARNING: at arch/arm/mm/ioremap.c:207 __arm_ioremap_pfn_caller+0x20c/0x214()
> [ 1.863281] Modules linked in:
> [ 1.866424] [<c004b2fc>] (unwind_backtrace+0x0/0x100) from [<c04fed38>] (dump_stack+0x18/0x1c)
> [ 1.875183] [<c04fed38>] (dump_stack+0x18/0x1c) from [<c0080fc4>] (warn_slowpath_common+0x5c/0x6c)
> [ 1.884277] [<c0080fc4>] (warn_slowpath_common+0x5c/0x6c) from [<c0080ff8>] (warn_slowpath_null+0x24/0x2c)
> [ 1.894073] [<c0080ff8>] (warn_slowpath_null+0x24/0x2c) from [<c00500cc>] (__arm_ioremap_pfn_caller+0x20c/0x214)
> [ 1.904388] [<c00500cc>] (__arm_ioremap_pfn_caller+0x20c/0x214) from [<c0050150>] (__arm_ioremap_caller+0x5c/0x64)
> [ 1.914855] [<c0050150>] (__arm_ioremap_caller+0x5c/0x64) from [<c0063484>] (omap_ioremap+0x7c/0x90)
> [ 1.924133] [<c0063484>] (omap_ioremap+0x7c/0x90) from [<c02d6ed8>] (omapfb_alloc_fbmem+0x94/0x1ec)
> [ 1.933319] [<c02d6ed8>] (omapfb_alloc_fbmem+0x94/0x1ec) from [<c02d7364>] (omapfb_allocate_all_fbs+0x334/0x460)
> [ 1.943634] [<c02d7364>] (omapfb_allocate_all_fbs+0x334/0x460) from [<c02d8430>] (omapfb_probe+0x324/0xb24)
> [ 1.953491] [<c02d8430>] (omapfb_probe+0x324/0xb24) from [<c030db48>] (platform_drv_probe+0x20/0x24)
> [ 1.962768] [<c030db48>] (platform_drv_probe+0x20/0x24) from [<c030c728>] (driver_probe_device+0xa4/0x1ac)
> [ 1.972564] [<c030c728>] (driver_probe_device+0xa4/0x1ac) from [<c030c8c4>] (__driver_attach+0x94/0x98)
> [ 1.982086] [<c030c8c4>] (__driver_attach+0x94/0x98) from [<c030be08>] (bus_for_each_dev+0x68/0x94)
> [ 1.991271] [<c030be08>] (bus_for_each_dev+0x68/0x94) from [<c030c594>] (driver_attach+0x24/0x28)
> [ 2.00027...

Thanks Nicolas,

http://git.linaro.org/gitweb?p=kernel/linux-linaro-next.git;a=commit;h=a0e1e0f754955ad1237ff38286717773b58168c1

I'm going to mark this fixed.

http://lwn.net/Articles/409689/