On Sat, Jun 26, 2010 at 04:58:26PM +0200, Joachim Ott wrote:
> On 25 June 2010 18:16, Martin Jansa <[email protected]> wrote:
> > Can you try to run Xorg -verbose 3 in gdb after installing -dbg packages
> > (from tests/shr-unstable.29) and get some backtrace from this
> > segmentation fault (I have never seen this one it if it's really from adding
> > keyboard).
> >
> > And make sure that you're starting only Xorg not whole Xsession, because
> > ie enlightenment fails to start when there is wrong mouse device node in
> > xorg.conf and exiting enlightenment as last process of Xsession kills
> > the Xorg then..
>
> The dbg-packages does not to work with my system (version mismatch?).
> After installing a lot of dbg-packages, I get this from gdb:
>
> # gdb /usr/bin/Xorg
I've slightly better backtrace and -keeptty gave me error from libc
<snip>
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(II) Glamo(0): Creating default Display subsection in Screen section
"Default Screen" for depth/fbbpp 16/16
(==) Glamo(0): Depth 16, (==) framebuffer bpp 16
(==) Glamo(0): RGB weight 565
(==) Glamo(0): Default visual is TrueColor
(==) Glamo(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Glamo(0): Output LCD using monitor section LCD Panel
*** glibc detected *** /usr/bin/Xorg: free(): invalid pointer:
0x00133a10 ***
Program received signal SIGABRT, Aborted.
0x4029f52c in raise () from /lib/libc.so.6
(gdb) back
#0 0x4029f52c in raise () from /lib/libc.so.6
#1 0x402a31b8 in abort () from /lib/libc.so.6
#2 0x402ced58 in __libc_message () from /lib/libc.so.6
#3 0x00000000 in ?? ()
And seems to happen somewhere after GlamoCrtcInit, but I'm not really
sure where, if I trace it more then it's able to continue and fails to
find valid node :/, but doesn't abort.
(==) Glamo(0): Default visual is
TrueColorib/xorg/modules/drivers/glamo_drv.so
(==) Glamo(0): Using gamma correction (1.0, 1.0, 1.0)
0x4043e28e in GlamoCrtcInit () from
/usr/lib/xorg/modules/drivers/glamo_drv.so
Breakpoint 2, 0x4043e28a in GlamoCrtcInit ()
0x4from
/usr/lib/xorg/modules/drivers/glamo_drv.somodules/drivers/glamo_drv.so
(gdb)
0x4043e292 in GlamoCrtcInit () from
/usr/lib/xorg/modules/drivers/glamo_drv.so
(gdb)
0x4043e294 in GlamoCrtcInit () from
/usr/lib/xorg/modules/drivers/glamo_drv.so
(gdb)
0x4043e296 in GlamoCrtcInit () from
/usr/lib/xorg/modules/drivers/glamo_drv.so
(gdb)
0x4043e298 in GlamoCrtcInit () from
/usr/lib/xorg/modules/drivers/glamo_drv.so
(gdb)
(II) Glamo(0): Output LCD using monitor section LCD Panel
(II) Glamo(0): Not using default mode "640x350" (width too large forvirtual
size)
(II) Glamo(0): Not using default mode "320x175" (doublescan mode notsupported)
(II) Glamo(0): Not using default mode "640x400" (width too large for virtual
size)
....
(II) Glamo(0): Not using default mode "1024x768" (doublescan mode not supported)
(II) Glamo(0): Printing probed modes for output LCD
(II) Glamo(0): Modeline "480x640"x72.5 24.50 480 496 504 512 640 656 658
660 (47.9 kHz)
(II) Glamo(0): Modeline "240x320"x50.2 24.50 240 736 738 740 320 656 658
660 (33.1 kHz)
(II) Glamo(0): Output LCD connected
(II) Glamo(0): Using exact sizes for initial modes
(II) Glamo(0): Output LCD using initial mode 480x640
(EE) Glamo(0): No valid modes.
(II) UnloadModule: "glamo"
(II) UnloadModule: "fbdevhw"
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
It can be one of s/xfree/free change in glamo-output.c
http://git.openmoko.org/?p=xf86-video-glamo.git;a=commit;h=e43cf499d0df41eb6ca2a1a7c21af71e31207635
or one of tousands similar changes all over xserver tree
Regards,
--
Jansa 'JaMa' Martin jabber: [email protected]
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
