Re: X.org segmentation fault - snapshot amd64
On 11/15/21 01:49, Matthieu Herrb wrote: On Sun, Nov 14, 2021 at 09:38:09PM -0500, David Hill wrote: This did not help my machine: quick gdb on Xorg.core: Loaded symbols for /usr/X11R6/lib/modules/input/kbd_drv.so Reading symbols from /usr/X11R6/lib/modules/input/ws_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/input/ws_drv.so #0 thrkill () at /tmp/-:3 3 /tmp/-: No such file or directory. in /tmp/- Current language: auto; currently asm (gdb) bt #0 thrkill () at /tmp/-:3 #1 0x0f83e0ffaaae in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 #2 0x0f819d6b79da in OsAbort () from /usr/X11R6/bin/Xorg #3 0x0f819d6be7ae in AbortServer () from /usr/X11R6/bin/Xorg #4 0x0f819d6bcdeb in FatalError () from /usr/X11R6/bin/Xorg #5 0x0f819d6b4f14 in OsSigHandler () from /usr/X11R6/bin/Xorg #6 #7 0x0f83e1059394 in memcpy (dst0=Variable "dst0" is not available. ) at /usr/src/lib/libc/string/memcpy.c:103 #8 0x0f819d516474 in ActivatePassiveGrab () from /usr/X11R6/bin/Xorg #9 0x0f819d51486c in CheckPassiveGrabsOnWindow () from /usr/X11R6/bin/Xorg #10 0x0f819d51682f in CheckDeviceGrabs () from /usr/X11R6/bin/Xorg #11 0x0f819d615537 in ProcessOtherEvent () from /usr/X11R6/bin/Xorg #12 0x0f819d6415af in ProcessPointerEvent () from /usr/X11R6/bin/Xorg #13 0x0f819d50ff40 in PlayReleasedEvents () from /usr/X11R6/bin/Xorg #14 0x0f819d5110c8 in ComputeFreezes () from /usr/X11R6/bin/Xorg #15 0x0f819d510ea3 in DeactivatePointerGrab () from /usr/X11R6/bin/Xorg #16 0x0f819d511926 in AllowSome () from /usr/X11R6/bin/Xorg #17 0x0f819d511baa in ProcAllowEvents () from /usr/X11R6/bin/Xorg #18 0x0f819d4ff6a4 in Dispatch () from /usr/X11R6/bin/Xorg #19 0x0f819d50a78c in dix_main () from /usr/X11R6/bin/Xorg #20 0x0f819d4f11a8 in _start () from /usr/X11R6/bin/Xorg #21 0x in ?? () Thanks. Is there anything special you do to reproduce the crash ? (application, window manager,. specific input devices ... ) The XAllowEvent() call that seem to cause it is not used by any application in base as far as I can see. So this code path in the X server is not tested often, but this area got quite some churn during the 1.20 -> 21.1 release cycle... I am using xfce4. It crashes regularly when using Firefox along with the mouse and scroll wheel.
Re: X.org segmentation fault - snapshot amd64
On Sun, Nov 14, 2021 at 09:38:09PM -0500, David Hill wrote: > > This did not help my machine: > > quick gdb on Xorg.core: > > Loaded symbols for /usr/X11R6/lib/modules/input/kbd_drv.so > Reading symbols from /usr/X11R6/lib/modules/input/ws_drv.so...done. > Loaded symbols for /usr/X11R6/lib/modules/input/ws_drv.so > #0 thrkill () at /tmp/-:3 > 3 /tmp/-: No such file or directory. > in /tmp/- > Current language: auto; currently asm > (gdb) bt > #0 thrkill () at /tmp/-:3 > #1 0x0f83e0ffaaae in _libc_abort () at > /usr/src/lib/libc/stdlib/abort.c:51 > #2 0x0f819d6b79da in OsAbort () from /usr/X11R6/bin/Xorg > #3 0x0f819d6be7ae in AbortServer () from /usr/X11R6/bin/Xorg > #4 0x0f819d6bcdeb in FatalError () from /usr/X11R6/bin/Xorg > #5 0x0f819d6b4f14 in OsSigHandler () from /usr/X11R6/bin/Xorg > #6 > #7 0x0f83e1059394 in memcpy (dst0=Variable "dst0" is not available. > ) > at /usr/src/lib/libc/string/memcpy.c:103 > #8 0x0f819d516474 in ActivatePassiveGrab () from /usr/X11R6/bin/Xorg > #9 0x0f819d51486c in CheckPassiveGrabsOnWindow () from > /usr/X11R6/bin/Xorg > #10 0x0f819d51682f in CheckDeviceGrabs () from /usr/X11R6/bin/Xorg > #11 0x0f819d615537 in ProcessOtherEvent () from /usr/X11R6/bin/Xorg > #12 0x0f819d6415af in ProcessPointerEvent () from /usr/X11R6/bin/Xorg > #13 0x0f819d50ff40 in PlayReleasedEvents () from /usr/X11R6/bin/Xorg > #14 0x0f819d5110c8 in ComputeFreezes () from /usr/X11R6/bin/Xorg > #15 0x0f819d510ea3 in DeactivatePointerGrab () from /usr/X11R6/bin/Xorg > #16 0x0f819d511926 in AllowSome () from /usr/X11R6/bin/Xorg > #17 0x0f819d511baa in ProcAllowEvents () from /usr/X11R6/bin/Xorg > #18 0x0f819d4ff6a4 in Dispatch () from /usr/X11R6/bin/Xorg > #19 0x0f819d50a78c in dix_main () from /usr/X11R6/bin/Xorg > #20 0x0f819d4f11a8 in _start () from /usr/X11R6/bin/Xorg > #21 0x in ?? () > Thanks. Is there anything special you do to reproduce the crash ? (application, window manager,. specific input devices ... ) The XAllowEvent() call that seem to cause it is not used by any application in base as far as I can see. So this code path in the X server is not tested often, but this area got quite some churn during the 1.20 -> 21.1 release cycle... -- Matthieu Herrb
Re: X.org segmentation fault - snapshot amd64
On 11/14/21 14:09, Matthieu Herrb wrote: On Sun, Nov 14, 2021 at 10:19:43AM -0800, ariel a wrote: Synopsis: Xorg segmentation fault Category: amd64 Environment: System : OpenBSD 7.0 Details : OpenBSD 7.0-current (GENERIC.MP) #87: Wed Nov 10 10:29:31 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 Description: I believe I noticed the graphical interface stutter or slow down during mouse movement just before the crash. The X server crashed (see log below), dropping into the console for a moment and then displaying the xenodm login screen. How-To-Repeat: I don't know how to repeat it. The crash seemed to happen during normal system use: running graphical programs, with a monitor attached, during mouse cursor movement, but has not repeated itself yet. Let me know if there's something I can do to try to make this repeatable. Someone else got this on different hardware, also amd64, see https://marc.info/?l=openbsd-misc=163673726428574=2 Xorg.0.log.old: [29.449] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [29.449]linear framebuffer access unavailable [29.479] (--) Using wscons driver on /dev/ttyC4 [29.498] X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 Can you try with an /etc/X11/xorg.conf file containing just the 4 lines below ? The intel(4) driver has not been updated for a while and is almost abandonned upstreams. Your hardware should work with modesetting(4) too: Section Device Identifier "modesetting" Driver "modesetting" EndSection This did not help my machine: quick gdb on Xorg.core: Loaded symbols for /usr/X11R6/lib/modules/input/kbd_drv.so Reading symbols from /usr/X11R6/lib/modules/input/ws_drv.so...done. Loaded symbols for /usr/X11R6/lib/modules/input/ws_drv.so #0 thrkill () at /tmp/-:3 3 /tmp/-: No such file or directory. in /tmp/- Current language: auto; currently asm (gdb) bt #0 thrkill () at /tmp/-:3 #1 0x0f83e0ffaaae in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 #2 0x0f819d6b79da in OsAbort () from /usr/X11R6/bin/Xorg #3 0x0f819d6be7ae in AbortServer () from /usr/X11R6/bin/Xorg #4 0x0f819d6bcdeb in FatalError () from /usr/X11R6/bin/Xorg #5 0x0f819d6b4f14 in OsSigHandler () from /usr/X11R6/bin/Xorg #6 #7 0x0f83e1059394 in memcpy (dst0=Variable "dst0" is not available. ) at /usr/src/lib/libc/string/memcpy.c:103 #8 0x0f819d516474 in ActivatePassiveGrab () from /usr/X11R6/bin/Xorg #9 0x0f819d51486c in CheckPassiveGrabsOnWindow () from /usr/X11R6/bin/Xorg #10 0x0f819d51682f in CheckDeviceGrabs () from /usr/X11R6/bin/Xorg #11 0x0f819d615537 in ProcessOtherEvent () from /usr/X11R6/bin/Xorg #12 0x0f819d6415af in ProcessPointerEvent () from /usr/X11R6/bin/Xorg #13 0x0f819d50ff40 in PlayReleasedEvents () from /usr/X11R6/bin/Xorg #14 0x0f819d5110c8 in ComputeFreezes () from /usr/X11R6/bin/Xorg #15 0x0f819d510ea3 in DeactivatePointerGrab () from /usr/X11R6/bin/Xorg #16 0x0f819d511926 in AllowSome () from /usr/X11R6/bin/Xorg #17 0x0f819d511baa in ProcAllowEvents () from /usr/X11R6/bin/Xorg #18 0x0f819d4ff6a4 in Dispatch () from /usr/X11R6/bin/Xorg #19 0x0f819d50a78c in dix_main () from /usr/X11R6/bin/Xorg #20 0x0f819d4f11a8 in _start () from /usr/X11R6/bin/Xorg #21 0x in ?? () Xorg.0.log.old [ 40144.478] This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. [ 40144.478] X.Org X Server 1.21.1.1 X Protocol Version 11, Revision 0 [ 40144.479] Current Operating System: OpenBSD test.domain.com 7.0 GENERIC.MP#0 amd64 [ 40144.479] [ 40144.479] Current version of pixman: 0.40.0 [ 40144.480] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 40144.480] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 40144.481] (==) Log file: "/home/dhill/.local/share/xorg/Xorg.0.log", Time: Sun Nov 14 21:25:39 2021 [ 40144.481] (==) Using config file: "/etc/X11/xorg.conf" [ 40144.482] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [
Re: X.org segmentation fault - snapshot amd64
On Sun, 14 Nov 2021 at 11:10:31 -0800, ariel a wrote: > Will do, thanks! > > The reason I have been using the intel driver is solve some tearing I > was experiencing (with Option "TearFree" "true") so I will look into > other fixes for that. Running a compositor like compton or picom helps greatly with tearing, even if you don't use any of the other fancy features like shadows and stuff.
Re: X.org segmentation fault - snapshot amd64
On Sun Nov 14, 2021 at 11:09 AM PST, Matthieu Herrb wrote: > On Sun, Nov 14, 2021 at 10:19:43AM -0800, ariel a wrote: > > > > >Synopsis: Xorg segmentation fault > > >Category: amd64 > > >Environment: > > System : OpenBSD 7.0 > > Details : OpenBSD 7.0-current (GENERIC.MP) #87: Wed Nov 10 10:29:31 > > MST 2021 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > I believe I noticed the graphical interface stutter or slow down > > during mouse movement just before the crash. The X server > > crashed (see log below), dropping into the console for a moment > > and then displaying the xenodm login screen. > > >How-To-Repeat: > > I don't know how to repeat it. The crash seemed to happen during > > normal system use: running graphical programs, with a monitor > > attached, during mouse cursor movement, but has not repeated > > itself yet. Let me know if there's something I can do to try to > > make this repeatable. > > > > Someone else got this on different hardware, also amd64, see > > https://marc.info/?l=openbsd-misc=163673726428574=2 > > > > Xorg.0.log.old: > > > > [29.449] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem > > (Operation not permitted) > > Check that you have set 'machdep.allowaperture=1' > > in /etc/sysctl.conf and reboot your machine > > refer to xf86(4) for details > > [29.449]linear framebuffer access unavailable > > [29.479] (--) Using wscons driver on /dev/ttyC4 > > [29.498] > > X.Org X Server 1.20.13 > > X Protocol Version 11, Revision 0 > > > Can you try with an /etc/X11/xorg.conf file containing just the 4 > lines below ? The intel(4) driver has not been updated for a while and > is almost abandonned upstreams. Your hardware should work with > modesetting(4) too: > > Section Device > Identifier "modesetting" > Driver "modesetting" > EndSection > > > -- > Matthieu Herrb Will do, thanks! The reason I have been using the intel driver is solve some tearing I was experiencing (with Option "TearFree" "true") so I will look into other fixes for that.
Re: X.org segmentation fault - snapshot amd64
On Sun, Nov 14, 2021 at 10:19:43AM -0800, ariel a wrote: > > >Synopsis:Xorg segmentation fault > >Category:amd64 > >Environment: > System : OpenBSD 7.0 > Details : OpenBSD 7.0-current (GENERIC.MP) #87: Wed Nov 10 10:29:31 > MST 2021 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > I believe I noticed the graphical interface stutter or slow down > during mouse movement just before the crash. The X server > crashed (see log below), dropping into the console for a moment > and then displaying the xenodm login screen. > >How-To-Repeat: > I don't know how to repeat it. The crash seemed to happen during > normal system use: running graphical programs, with a monitor > attached, during mouse cursor movement, but has not repeated > itself yet. Let me know if there's something I can do to try to > make this repeatable. > > Someone else got this on different hardware, also amd64, see > https://marc.info/?l=openbsd-misc=163673726428574=2 > > Xorg.0.log.old: > > [29.449] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem > (Operation not permitted) > Check that you have set 'machdep.allowaperture=1' > in /etc/sysctl.conf and reboot your machine > refer to xf86(4) for details > [29.449] linear framebuffer access unavailable > [29.479] (--) Using wscons driver on /dev/ttyC4 > [29.498] > X.Org X Server 1.20.13 > X Protocol Version 11, Revision 0 Can you try with an /etc/X11/xorg.conf file containing just the 4 lines below ? The intel(4) driver has not been updated for a while and is almost abandonned upstreams. Your hardware should work with modesetting(4) too: Section Device Identifier "modesetting" Driver "modesetting" EndSection -- Matthieu Herrb
