[meta-freescale] Vivante on small memory system

[Gary Thomas]

I have an i.MX6S system which has only 512MB of DRAM, running a Yocto based system.
On this system, when I run X11, it fails to run.

I have the same system running on an i.MX6Q (SabreLite) which has 1GB DRAM.
Everything is the same except for the kernel between these two systems and
the SabreLite runs X11 just fine.  Both systems are built using the same
kernel tree (linux-boundary 3.0.35-4.1.0+yocto)

When I try to run X on the i.MX6S system, it fails like this:

X.Org X Server 1.14.0
Release Date: 2013-03-05
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-54-generic x86_64
Current Operating System: Linux teton-p8301 3.0.35-gc35aea8-dirty #17 SMP PREEMPT Thu Nov 21 10:05:30 MST 2013 armv7l
Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=lcd,CLAA-WVGA,if=RGB24 console
blank=0 fbmem=10M vmalloc=128M
Build Date: 20 November 2013  11:13:04AM

Current version of pixman: 0.30.2
         Before reporting problems, check http://wiki.x.org
         to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 21 17:15:00 2013
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
Loading extension vivext
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0xc

I've traced this into the X server starting up the Vivante extension.
 From GDB, I got this:

Program received signal SIGSEGV, Segmentation fault.
0x2b0843f0 in gcoOS_GetBaseAddress (Os=Os at entry=0x0, BaseAddress=0x7efffaf0,
     BaseAddress at entry=0x7efffae8) at gc_hal_user_os.c:1391
1391    gc_hal_user_os.c: No such file or directory.
(gdb) bt
#0  0x2b0843f0 in gcoOS_GetBaseAddress (Os=Os at entry=0x0,
     BaseAddress=0x7efffaf0, BaseAddress at entry=0x7efffae8)
     at gc_hal_user_os.c:1391
#1  0x2afeb214 in gcoHAL_MapUserMemory (Logical=0x2b258000,
     Physical=402653184, Size=1152000, Info=0x1c86dc, GPUAddress=0x1c86e0)
     at gc_hal_user.c:753
#2  0x2afc6db8 in ?? () from /usr/lib/xorg/modules/drivers/vivante_drv.so
#3  0x2afc6db8 in ?? () from /usr/lib/xorg/modules/drivers/vivante_drv.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I have a feeling that this has something to do with shared memory, etc?

Any ideas where I can look/change?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------