xorg-server running on 10-current under VMware?
Guy Helmer
guy.helmer at gmail.com
Fri May 24 15:47:58 UTC 2013
On May 24, 2013, at 8:08 AM, Thomas Mueller <tmueller at sysgo.com> wrote:
> On Thu, 23 May 2013 16:20:35 -0500, Guy Helmer wrote:
>> I've tried using drivers xf86-video-vmware (vmware) and xf86-video-vesa
>> (vesa) for 10-current under VMware Fusion. Regardless, the X server
>> fails with the error:
>>
>>> [...]
>>> Fatal server error:
>>> AddScreen/ScreenInit failed for driver 0
>>>
>>>
>>> Please consult the The X.Org Foundation support
>>> at http://wiki.x.org
>>> for help.
>>> Please also check the log file at "/var/log/Xorg.0.log" for additional information.
>>>
>>> Segmentation fault at address 0x290
>>>
>>> FatalError re-entered, aborting
>>> Caught signal 11 (Segmentation fault). Server aborting
>>
>> Any hints?
>
> I'm observing the same behaviour with 10-current running as guest in VirtualBox.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000454bec in dixLookupPrivate (privates=0x290, key=0x804e2be38) at privates.c:79
> 79 return *key && *privates &&
> Current language: auto; currently minimal
> (gdb) bt
> #0 0x0000000000454bec in dixLookupPrivate (privates=0x290, key=0x804e2be38) at privates.c:79
> #1 0x0000000804c27310 in ShadowLeaveVT () from /usr/local/lib/xorg/modules/libshadowfb.so
> #2 0x000000000047a076 in AbortDDX () at xf86Init.c:1249
> #3 0x00000000004739fd in AbortServer () at log.c:404
> #4 0x00000000004732b6 in FatalError (f=<value optimized out>) at log.c:529
> #5 0x00000000004799a9 in InitOutput (pScreenInfo=0x7c5560, argc=3, argv=0x7fffffffdc38) at xf86Init.c:1057
> #6 0x0000000000431f6e in main (argc=3, argv=0x7fffffffdc38, envp=<value optimized out>) at main.c:204
>
> The segmentation fault in dixLookupPrivate() seems like a subsequent fault of
> xf86Init.c:1043 scr_index = AddScreen(xf86Screens[i]->ScreenInit, argc, argv);
> indicating failure to add the screen.
>
> Building xorg-server with gcc
> make USE_GCC=any
> or with clang and -O0
> mage CFLAGS=-O0
> gives me an X server that appears to work (displays root weave, xterm,
> and twm).
Thank you! Rebuilding as you suggested resolved the problem for me.
Guy
More information about the freebsd-current
mailing list