X-Org problem

[Paul B. Mahol]

On 4/24/09, Ott Koestner <OttK at zzz.ee> wrote:
> Neal Hogan wrote:
>> On Fri, Apr 24, 2009 at 7:33 AM, Ott Koestner <ottk at zzz.ee> wrote:
>>
>>> Dear list,
>>>
>>> After upgrading Xorg from ports to the latest version
>>> xorg-server-1.6.0,1
>>> xorg-7.4_1
>>>
>>> I am experiencing very unpleasant phenomenon, Xorg randomly exiting with
>>> message:
>>>
>>> Apr 24 15:16:16 ott kernel: pid 7445 (Xorg), uid 0: exited on signal 6
>>> Apr 24 15:16:16 ott kdm-bin[1020]: X server for display :0 terminated
>>> unexpectedly
>>>
>>> Also, there is a strange behavior with dual-head mode -- when moving
>>> cursor from one screen to another, the little white arrow remains on the
>>> other screen.
>>>
>>> Please help! What might it be? Recompiled probably everything related to
>>> Xorg. Using Nvidia driver version
>>> nvidia-driver-96.43.11
>>>
>>
>> I'm no expert, but to help those that are, I suggest that you post the
>> contents of your /etc/X11/Xorg.0.log (perhaps a dmesg, too).
>>
>>
> After the crash Xorg is instantly restarted. Probably there is no reason
> to copy the whole log here. Everything looks normal for some time and
> then it restarts just at a random moment. No reason to blame hardware.
> It was stable before pre-previous Xorg server update (over 100 days uptime).
>
> Ill-effects started after I upgraded to xorg-server-1.5.3. Mouse buttons
> started to freeze randomly. That is why I chose to upgrade to
> xorg-server-1.6.0.
> Xorg.0.log.old ends like this:
> ...
> (II) LoadModule: "mouse"
> (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so
> (II) Module mouse: vendor="X.Org Foundation"
>         compiled for 1.6.0, module version = 1.4.0
>         Module class: X.Org XInput Driver
>         ABI class: X.Org XInput driver, version 4.0
> (**) PS/2 Mouse: Device: "/dev/sysmouse"
> (==) PS/2 Mouse: Protocol: "Auto"
> (**) PS/2 Mouse: always reports core events
> (**) Option "Device" "/dev/sysmouse"
> (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50
> (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5
> (**) PS/2 Mouse: Buttons: 9
> (**) PS/2 Mouse: Sensitivity: 1
> (II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE)
> (**) PS/2 Mouse: (accel) keeping acceleration scheme 1
> (**) PS/2 Mouse: (accel) filter chain progression: 2.00
> (**) PS/2 Mouse: (accel) filter stage 0: 20.00 ms
> (**) PS/2 Mouse: (accel) set acceleration profile 0
> (II) PS/2 Mouse: SetupAuto: hw.iftype is 4, hw.model is 0
> (II) PS/2 Mouse: SetupAuto: protocol is SysMouse
>
> Fatal server error:
> Caught signal 11.  Server aborting
>
>
> 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.
>
> (II) UnloadModule: "kbd"
> (II) UnloadModule: "mouse"
> (II) Screen 0 shares mem & io resources
> (II) Screen 1 shares mem & io resources
>
> ----------------------------------------------------------
>
> # dmesg | tail -n 15
> pid 6766 (PBReg), uid 1001: exited on signal 10
> pid 6787 (NetworkTray), uid 1001: exited on signal 11
> pid 6796 (NetworkTray), uid 1001: exited on signal 11
> pid 6478 (Xorg), uid 0: exited on signal 6
> pid 7710 (PBReg), uid 1001: exited on signal 10
> pid 7727 (NetworkTray), uid 1001: exited on signal 11
> pid 7730 (NetworkTray), uid 1001: exited on signal 11
> pid 7445 (Xorg), uid 0: exited on signal 6
> pid 8095 (PBReg), uid 1001: exited on signal 10
> pid 8112 (NetworkTray), uid 1001: exited on signal 11
> pid 8115 (NetworkTray), uid 1001: exited on signal 11
> pid 7797 (Xorg), uid 0: exited on signal 6
> pid 47182 (PBReg), uid 1001: exited on signal 10
> pid 47199 (NetworkTray), uid 1001: exited on signal 11
> pid 47200 (NetworkTray), uid 1001: exited on signal 11
>
>
>
>>
>>> With best regards,
>>> Ott Koestner
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> freebsd-questions at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to
>>> "freebsd-questions-unsubscribe at freebsd.org"
>>>
>>>
>>
>>
>>
>>
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>

I saw on svn-head that signal 6 crash is caused by FreeBSD
malloc/libc, and is fixed on CURRENT but that may not be related to
your problem.

-- 
Paul