Re: new xorg segfault 11 with KMS
On 12/14/12 01:24, Johannes Dieterich wrote: On Thu, Dec 13, 2012 at 6:51 PM, Artyom Mirgorodskiy art...@ijminteractive.net wrote: This patch work for me. Thanks. I can confirm that it also works for me. Thanks a lot! On Friday 14 December 2012 00:30:52 Niclas Zeising wrote: Can you please try the attached patch, against x11-servers/xorg-server. Apply it and recompile xorg-server with normal flags (that is, no debugging) and let me and the list know the result when starting X. Regards! Patch is applied to the ports tree now. Thanks for help testing! Regards! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 12/14/12 00:51, Artyom Mirgorodskiy wrote: This patch work for me. Thanks. On Friday 14 December 2012 00:30:52 Niclas Zeising wrote: Can you please try the attached patch, against x11-servers/xorg-server. Apply it and recompile xorg-server with normal flags (that is, no debugging) and let me and the list know the result when starting X. Regards! Patch is in the ports tree now. Thanks for testing! Regards! -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
I have a similar problem when running firefox On Thursday 13 December 2012 15:49:38 Johannes Dieterich wrote: Dear all, I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Unfortunately, I cannot tell what is the root cause of the problems as I first got bitten by the pcre update and also did the world update to the clang3.2 import. Needless to say that everything worked prior and the configuration (no xorg.conf here) did not change. uname -a: FreeBSD X 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r244180: Thu Dec 13 09:46:06 EST 2012 root@X:/usr/obj/usr/src/sys/GENERIC amd64. Xorg.0.log: [88.021] X.Org X Server 1.10.6 Release Date: 2012-02-10 [88.021] X Protocol Version 11, Revision 0 [88.021] Build Operating System: FreeBSD 10.0-CURRENT amd64 [88.021] Current Operating System: FreeBSD X 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r244180: Thu Dec 13 09:46:06 EST 2012 root@XXX:/usr/obj/usr/src/sys/GENERIC amd64 [88.021] Build Date: 13 December 2012 06:30:07AM [88.021] [88.021] Current version of pixman: 0.24.2 [88.021]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [88.021] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [88.022] (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 13 15:01:42 2012 [88.024] (II) Loader magic: 0x7c1930 [88.024] (II) Module ABI versions: [88.024]X.Org ANSI C Emulation: 0.4 [88.024]X.Org Video Driver: 10.0 [88.024]X.Org XInput driver : 12.2 [88.024]X.Org Server Extension : 5.0 [88.025] (--) PCI:*(0:0:2:0) 8086:0166:17aa:2200 rev 9, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0x5000/64, BIOS @ 0x/65536 [88.025] (==) Using default built-in configuration (30 lines) [88.025] (==) --- Start of built-in configuration --- [88.025]Section Device [88.025]Identifier Builtin Default intel Device 0 [88.025]Driver intel [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default intel Screen 0 [88.025]Device Builtin Default intel Device 0 [88.025]EndSection [88.025]Section Device [88.025]Identifier Builtin Default vesa Device 0 [88.025]Driver vesa [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default vesa Screen 0 [88.025]Device Builtin Default vesa Device 0 [88.025]EndSection [88.025]Section Device [88.025]Identifier Builtin Default fbdev Device 0 [88.025]Driver fbdev [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default fbdev Screen 0 [88.025]Device Builtin Default fbdev Device 0 [88.026]EndSection [88.026]Section ServerLayout [88.026]Identifier Builtin Default Layout [88.026]Screen Builtin Default intel Screen 0 [88.026]Screen Builtin Default vesa Screen 0 [88.026]Screen Builtin Default fbdev Screen 0 [88.026]EndSection [88.026] (==) --- End of built-in configuration --- [88.026] (==) ServerLayout Builtin Default Layout [88.026] (**) |--Screen Builtin Default intel Screen 0 (0) [88.026] (**) | |--Monitor default monitor [88.026] (**) | |--Device Builtin Default intel Device 0 [88.026] (==) No monitor specified for screen Builtin Default intel Screen 0. Using a default monitor configuration. [88.026] (**) |--Screen Builtin Default vesa Screen 0 (1) [88.026] (**) | |--Monitor default monitor [88.026] (**) | |--Device Builtin Default vesa Device 0 [88.026] (==) No monitor specified for screen Builtin Default vesa Screen 0. Using a default monitor configuration. [88.026] (**) |--Screen Builtin Default fbdev Screen 0 (2) [88.027] (**) | |--Monitor default monitor [88.027] (**) | |--Device Builtin Default fbdev Device 0 [88.027] (==) No monitor specified for screen Builtin Default fbdev Screen 0. Using a default monitor configuration. [88.027] (==) Automatically adding devices [88.027] (==) Automatically enabling devices [88.027] (WW) The
Re: new xorg segfault 11 with KMS
Rebuilding xorg-server with gcc resolves the problem, bt points at libdrm2. On Thu, Dec 13, 2012 at 10:51 PM, Artyom Mirgorodskiy art...@ijminteractive.net wrote: I have a similar problem when running firefox On Thursday 13 December 2012 15:49:38 Johannes Dieterich wrote: Dear all, I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Unfortunately, I cannot tell what is the root cause of the problems as I first got bitten by the pcre update and also did the world update to the clang3.2 import. Needless to say that everything worked prior and the configuration (no xorg.conf here) did not change. uname -a: FreeBSD X 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r244180: Thu Dec 13 09:46:06 EST 2012 root@X:/usr/obj/usr/src/sys/GENERIC amd64. Xorg.0.log: [88.021] X.Org X Server 1.10.6 Release Date: 2012-02-10 [88.021] X Protocol Version 11, Revision 0 [88.021] Build Operating System: FreeBSD 10.0-CURRENT amd64 [88.021] Current Operating System: FreeBSD X 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r244180: Thu Dec 13 09:46:06 EST 2012 root@XXX:/usr/obj/usr/src/sys/GENERIC amd64 [88.021] Build Date: 13 December 2012 06:30:07AM [88.021] [88.021] Current version of pixman: 0.24.2 [88.021]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [88.021] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [88.022] (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 13 15:01:42 2012 [88.024] (II) Loader magic: 0x7c1930 [88.024] (II) Module ABI versions: [88.024]X.Org ANSI C Emulation: 0.4 [88.024]X.Org Video Driver: 10.0 [88.024]X.Org XInput driver : 12.2 [88.024]X.Org Server Extension : 5.0 [88.025] (--) PCI:*(0:0:2:0) 8086:0166:17aa:2200 rev 9, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0x5000/64, BIOS @ 0x/65536 [88.025] (==) Using default built-in configuration (30 lines) [88.025] (==) --- Start of built-in configuration --- [88.025]Section Device [88.025]Identifier Builtin Default intel Device 0 [88.025]Driver intel [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default intel Screen 0 [88.025]Device Builtin Default intel Device 0 [88.025]EndSection [88.025]Section Device [88.025]Identifier Builtin Default vesa Device 0 [88.025]Driver vesa [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default vesa Screen 0 [88.025]Device Builtin Default vesa Device 0 [88.025]EndSection [88.025]Section Device [88.025]Identifier Builtin Default fbdev Device 0 [88.025]Driver fbdev [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default fbdev Screen 0 [88.025]Device Builtin Default fbdev Device 0 [88.026]EndSection [88.026]Section ServerLayout [88.026]Identifier Builtin Default Layout [88.026]Screen Builtin Default intel Screen 0 [88.026]Screen Builtin Default vesa Screen 0 [88.026]Screen Builtin Default fbdev Screen 0 [88.026]EndSection [88.026] (==) --- End of built-in configuration --- [88.026] (==) ServerLayout Builtin Default Layout [88.026] (**) |--Screen Builtin Default intel Screen 0 (0) [88.026] (**) | |--Monitor default monitor [88.026] (**) | |--Device Builtin Default intel Device 0 [88.026] (==) No monitor specified for screen Builtin Default intel Screen 0. Using a default monitor configuration. [88.026] (**) |--Screen Builtin Default vesa Screen 0 (1) [88.026] (**) | |--Monitor default monitor [88.026] (**) | |--Device Builtin Default vesa Device 0 [88.026] (==) No monitor specified for screen Builtin Default vesa Screen 0. Using a default monitor configuration. [88.026] (**) |--Screen Builtin Default fbdev Screen 0 (2) [88.027] (**) | |--Monitor default monitor [88.027] (**) | |--Device Builtin Default fbdev
Re: new xorg segfault 11 with KMS
On Thu, Dec 13, 2012 at 12:51 PM, Artyom Mirgorodskiy art...@ijminteractive.net wrote: I have a similar problem when running firefox I don't run into this problem with CURRENT and fluxbox/Firefox on my Netbook. There's just a nasty misprogrammed region across my screen that I've been meaning to file a bug about... My Netbook has a Pineview chipset. Thanks! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On Thu, Dec 13, 2012 at 4:01 PM, George Liaskos geo.lias...@gmail.com wrote: Rebuilding xorg-server with gcc resolves the problem, bt points at libdrm2. So basically this is a regression from the previous clang3.1 to the clang3.2 import then? Is anyone of the clang guys aware of this? On Thu, Dec 13, 2012 at 10:51 PM, Artyom Mirgorodskiy art...@ijminteractive.net wrote: I have a similar problem when running firefox On Thursday 13 December 2012 15:49:38 Johannes Dieterich wrote: Dear all, I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Unfortunately, I cannot tell what is the root cause of the problems as I first got bitten by the pcre update and also did the world update to the clang3.2 import. Needless to say that everything worked prior and the configuration (no xorg.conf here) did not change. uname -a: FreeBSD X 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r244180: Thu Dec 13 09:46:06 EST 2012 root@X:/usr/obj/usr/src/sys/GENERIC amd64. Xorg.0.log: [88.021] X.Org X Server 1.10.6 Release Date: 2012-02-10 [88.021] X Protocol Version 11, Revision 0 [88.021] Build Operating System: FreeBSD 10.0-CURRENT amd64 [88.021] Current Operating System: FreeBSD X 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r244180: Thu Dec 13 09:46:06 EST 2012 root@XXX:/usr/obj/usr/src/sys/GENERIC amd64 [88.021] Build Date: 13 December 2012 06:30:07AM [88.021] [88.021] Current version of pixman: 0.24.2 [88.021]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [88.021] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [88.022] (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 13 15:01:42 2012 [88.024] (II) Loader magic: 0x7c1930 [88.024] (II) Module ABI versions: [88.024]X.Org ANSI C Emulation: 0.4 [88.024]X.Org Video Driver: 10.0 [88.024]X.Org XInput driver : 12.2 [88.024]X.Org Server Extension : 5.0 [88.025] (--) PCI:*(0:0:2:0) 8086:0166:17aa:2200 rev 9, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0x5000/64, BIOS @ 0x/65536 [88.025] (==) Using default built-in configuration (30 lines) [88.025] (==) --- Start of built-in configuration --- [88.025]Section Device [88.025]Identifier Builtin Default intel Device 0 [88.025]Driver intel [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default intel Screen 0 [88.025]Device Builtin Default intel Device 0 [88.025]EndSection [88.025]Section Device [88.025]Identifier Builtin Default vesa Device 0 [88.025]Driver vesa [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default vesa Screen 0 [88.025]Device Builtin Default vesa Device 0 [88.025]EndSection [88.025]Section Device [88.025]Identifier Builtin Default fbdev Device 0 [88.025]Driver fbdev [88.025]EndSection [88.025]Section Screen [88.025]Identifier Builtin Default fbdev Screen 0 [88.025]Device Builtin Default fbdev Device 0 [88.026]EndSection [88.026]Section ServerLayout [88.026]Identifier Builtin Default Layout [88.026]Screen Builtin Default intel Screen 0 [88.026]Screen Builtin Default vesa Screen 0 [88.026]Screen Builtin Default fbdev Screen 0 [88.026]EndSection [88.026] (==) --- End of built-in configuration --- [88.026] (==) ServerLayout Builtin Default Layout [88.026] (**) |--Screen Builtin Default intel Screen 0 (0) [88.026] (**) | |--Monitor default monitor [88.026] (**) | |--Device Builtin Default intel Device 0 [88.026] (==) No monitor specified for screen Builtin Default intel Screen 0. Using a default monitor configuration. [88.026] (**) |--Screen Builtin Default vesa Screen 0 (1) [88.026] (**) | |--Monitor default monitor [88.026] (**) | |--Device Builtin Default vesa Device 0 [88.026] (==) No monitor specified for screen Builtin Default vesa Screen 0.
Re: new xorg segfault 11 with KMS
On Thu, Dec 13, 2012 at 1:03 PM, Garrett Cooper yaneg...@gmail.com wrote: On Thu, Dec 13, 2012 at 12:51 PM, Artyom Mirgorodskiy art...@ijminteractive.net wrote: I have a similar problem when running firefox I don't run into this problem with CURRENT and fluxbox/Firefox on my Netbook. There's just a nasty misprogrammed region across my screen that I've been meaning to file a bug about... My Netbook has a Pineview chipset. Good point -- my ports were last built with gcc before I upgraded recently; haven't tried with clang. Thanks! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 2012-12-13 21:49, Johannes Dieterich wrote: I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Please post the backtrace anyway. :-) Or recompile xorg-server with WITH_DEBUG=yes in your environment, and reproduce the crash. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 12/13/12 16:36, Dimitry Andric wrote: On 2012-12-13 21:49, Johannes Dieterich wrote: I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Please post the backtrace anyway. :-) Or recompile xorg-server with WITH_DEBUG=yes in your environment, and reproduce the crash. Here we go: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd. Core was generated by `Xorg'. Program terminated with signal 6, Aborted. #0 0x000802c4520a in ?? () (gdb) bt #0 0x000802c4520a in ?? () #1 0x000802cf72bc in ?? () #2 0x000802cf85ca in ?? () #3 0x007cdd5c in ?? () #4 0xffdf in ?? () #5 0x in ?? () #6 0x in ?? () #7 0x00575f06 in ?? () #8 0x7fffce50 in ?? () #9 0x00472c9e in ?? () #10 0x7fffce60 in ?? () #11 0x0047e034 in ?? () #12 0x7fffce70 in ?? () #13 0x004704ed in ?? () #14 0x7fffcf50 in ?? () #15 0x0046fd26 in ?? () #16 0x3246 in ?? () #17 0x000b in ?? () #18 0x000802f31a10 in ?? () #19 0xf801 in ?? () #20 0x0101010101010101 in ?? () #21 0x8080808080808080 in ?? () #22 0x in ?? () #23 0x0001 in ?? () #24 0x6e7dec389dd25e4d in ?? () #25 0x000802c60f9e in ?? () #26 0x000802f31a10 in ?? () #27 0x000802f31a10 in ?? () #28 0x in ?? () #29 0x000b in ?? () #30 0x7fffcf50 in ?? () #31 0x000802c19662 in ?? () #32 0x0006 in ?? () #33 0x00470e50 in ?? () #34 0x000b in ?? () #35 0x7fffd730 in ?? () #36 0x6e7dec389dd25e4d in ?? () #37 0x000b in ?? () #38 0x00300018 in ?? () #39 0x7fffcf60 in ?? () ---Type return to continue, or q return to quit--- #40 0x7fffce80 in ?? () #41 0x000b in ?? () #42 0x7fffcf70 in ?? () #43 0x00470ee3 in ?? () #44 0x7fffd358 in ?? () #45 0x7fffd3c0 in ?? () #46 0x7fffd330 in ?? () #47 0x0008029ca2e6 in ?? () #48 0x in ?? () I also rebuild xorg with debug enabled. Interestingly, I cannot reproduce the crash anymore. Either I forgot to rebuild something (seems unlikely) or the crash has to do with optimizations or flags not present in a debug build. Hope this helps. Johannes ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 13 Dec 2012, at 21:48, Johannes Dieterich wrote: GNU gdb 6.1.1 [FreeBSD] You might try with gdb 7.x from ports. gdb 6.1.1 from the base system doesn't do a good job of understanding the newer version of DWARF that clang emits. David ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 12/13/12 22:48, Johannes Dieterich wrote: On 12/13/12 16:36, Dimitry Andric wrote: On 2012-12-13 21:49, Johannes Dieterich wrote: I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Please post the backtrace anyway. :-) Or recompile xorg-server with WITH_DEBUG=yes in your environment, and reproduce the crash. Here we go: I also rebuild xorg with debug enabled. Interestingly, I cannot reproduce the crash anymore. Either I forgot to rebuild something (seems unlikely) or the crash has to do with optimizations or flags not present in a debug build. This is not unlikely. There are probably places in the X codebase which depends on gcc specific behavior, or undefined behavior, by accident or by chance. Regards -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 12/13/12 16:53, David Chisnall wrote: On 13 Dec 2012, at 21:48, Johannes Dieterich wrote: GNU gdb 6.1.1 [FreeBSD] You might try with gdb 7.x from ports. gdb 6.1.1 from the base system doesn't do a good job of understanding the newer version of DWARF that clang emits. Did that but it doesn't change much: GNU gdb (GDB) 7.5 [GDB v7.5 for FreeBSD] Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-portbld-freebsd10.0. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. [New process 100714] Core was generated by `Xorg'. Program terminated with signal 6, Aborted. #0 0x000802c4520a in ?? () (gdb) bt #0 0x000802c4520a in ?? () #1 0x000802cf72bc in ?? () #2 0x000802cf85ca in ?? () #3 0x007cdd5c in ?? () #4 0xffdf in ?? () #5 0x in ?? () #6 0x in ?? () #7 0x00575f06 in ?? () #8 0x7fffce50 in ?? () #9 0x00472c9e in ?? () #10 0x7fffce60 in ?? () #11 0x0047e034 in ?? () #12 0x7fffce70 in ?? () #13 0x004704ed in ?? () #14 0x7fffcf50 in ?? () #15 0x0046fd26 in ?? () #16 0x3246 in ?? () #17 0x000b in ?? () #18 0x000802f31a10 in ?? () #19 0xf801 in ?? () #20 0x0101010101010101 in ?? () #21 0x8080808080808080 in ?? () #22 0x in ?? () #23 0x0001 in ?? () #24 0x6e7dec389dd25e4d in ?? () #25 0x000802c60f9e in ?? () #26 0x000802f31a10 in ?? () #27 0x000802f31a10 in ?? () #28 0x in ?? () #29 0x000b in ?? () #30 0x7fffcf50 in ?? () #31 0x000802c19662 in ?? () #32 0x0006 in ?? () #33 0x00470e50 in ?? () #34 0x000b in ?? () #35 0x7fffd730 in ?? () #36 0x6e7dec389dd25e4d in ?? () #37 0x000b in ?? () #38 0x00300018 in ?? () #39 0x7fffcf60 in ?? () ---Type return to continue, or q return to quit--- #40 0x7fffce80 in ?? () #41 0x000b in ?? () #42 0x7fffcf70 in ?? () #43 0x00470ee3 in ?? () #44 0x7fffd358 in ?? () #45 0x7fffd3c0 in ?? () #46 0x7fffd330 in ?? () #47 0x0008029ca2e6 in ?? () #48 0x in ?? () I guess marking xorg-server to require USE_GCC=4.2+ would be a reasonable workaround for the time being? Best Johannes ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
I have recompile xorg-server with WITH_DEBUG=yes and did not get crash On Thursday 13 December 2012 22:36:24 Dimitry Andric wrote: On 2012-12-13 21:49, Johannes Dieterich wrote: I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly causes the segfault (log attached), gnome survives a bit longer but starting any bigger application (e.g. firefox) causes it to crash with the same log. I have a Xorg.core file, but since it is without debug symbols the backtrace makes little sense to me. Please post the backtrace anyway. :-) Or recompile xorg-server with WITH_DEBUG=yes in your environment, and reproduce the crash. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- This message is for the person(s) named above only and may contain privileged, proprietary, or otherwise private information. If you received this transmission in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On 12/13/12 23:03, Johannes Dieterich wrote: On 12/13/12 16:53, David Chisnall wrote: On 13 Dec 2012, at 21:48, Johannes Dieterich wrote: GNU gdb 6.1.1 [FreeBSD] You might try with gdb 7.x from ports. gdb 6.1.1 from the base system doesn't do a good job of understanding the newer version of DWARF that clang emits. Did that but it doesn't change much: I guess marking xorg-server to require USE_GCC=4.2+ would be a reasonable workaround for the time being? I have a shot in the dark before we try that, I just need to finish the patch. I'll let you all know when it's ready. Regards -- Niclas -- Niclas Zeising ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
Can you please try the attached patch, against x11-servers/xorg-server.
Apply it and recompile xorg-server with normal flags (that is, no
debugging) and let me and the list know the result when starting X.
Regards!
--
Niclas Zeising
Index: x11-servers/xorg-server/Makefile
===
--- x11-servers/xorg-server/Makefile (revision 308805)
+++ x11-servers/xorg-server/Makefile (working copy)
@@ -29,7 +29,8 @@
XORG_REVISION= 1
PLIST_SUB+= OLD=@comment NEW=
EXTRA_PATCHES+= ${FILESDIR}/extra-hw_dmx_glxProxy_compsize.h \
- ${FILESDIR}/extra-hw_dmx_glxProxy_glxcmds.h
+ ${FILESDIR}/extra-hw_dmx_glxProxy_glxcmds.h \
+ ${FILESDIR}/extra-clang
.else
XORG_VERSION= 1.7.7
XORG_REVISION= 6
Index: x11-servers/xorg-server/files/extra-clang
===
--- x11-servers/xorg-server/files/extra-clang (revision 0)
+++ x11-servers/xorg-server/files/extra-clang (working copy)
@@ -0,0 +1,53 @@
+--- hw/xfree86/common/xf86Xinput.c.orig 2012-12-13 23:58:55.673738569 +0100
hw/xfree86/common/xf86Xinput.c 2012-12-13 23:59:52.528738525 +0100
+@@ -479,7 +479,7 @@
+ MatchAttrToken(const char *attr, struct list *patterns,
+int (*compare)(const char *attr, const char *pattern))
+ {
+-const xf86MatchGroup *group;
++const xf86MatchGroup *group = NULL;
+
+ /* If there are no patterns, accept the match */
+ if (list_is_empty(patterns))
+--- hw/xfree86/parser/InputClass.c.orig 2012-12-14 00:03:07.149734651 +0100
hw/xfree86/parser/InputClass.c 2012-12-14 00:04:09.522735172 +0100
+@@ -338,7 +338,8 @@
+ XF86ConfInputClassPtr prev;
+
+ while (ptr) {
+-xf86MatchGroup *group, *next;
++xf86MatchGroup *group = NULL;
++xf86MatchGroup *next;
+ char **list;
+
+ TestFree(ptr-identifier);
+--- hw/xfree86/dri2/dri2.c.orig 2012-12-14 00:06:39.680738243 +0100
hw/xfree86/dri2/dri2.c 2012-12-14 00:08:14.310729622 +0100
+@@ -201,7 +201,7 @@
+ static DRI2DrawableRefPtr
+ DRI2LookupDrawableRef(DRI2DrawablePtr pPriv, XID id)
+ {
+-DRI2DrawableRefPtr ref;
++DRI2DrawableRefPtr ref = NULL;
+
+ list_for_each_entry(ref, pPriv-reference_list, link) {
+ if (ref-id == id)
+@@ -267,7 +267,8 @@
+ {
+ DRI2DrawablePtr pPriv = p;
+ DRI2ScreenPtr ds = pPriv-dri2_screen;
+-DRI2DrawableRefPtr ref, next;
++DRI2DrawableRefPtr ref = NULL;
++DRI2DrawableRefPtr next;
+ WindowPtr pWin;
+ PixmapPtr pPixmap;
+ DrawablePtr pDraw;
+@@ -534,7 +535,7 @@
+ DRI2InvalidateDrawable(DrawablePtr pDraw)
+ {
+ DRI2DrawablePtr pPriv = DRI2GetDrawable(pDraw);
+-DRI2DrawableRefPtr ref;
++DRI2DrawableRefPtr ref = NULL;
+
+ if (!pPriv)
+ return;
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
This patch work for me. Thanks. On Friday 14 December 2012 00:30:52 Niclas Zeising wrote: Can you please try the attached patch, against x11-servers/xorg-server. Apply it and recompile xorg-server with normal flags (that is, no debugging) and let me and the list know the result when starting X. Regards! -- This message is for the person(s) named above only and may contain privileged, proprietary, or otherwise private information. If you received this transmission in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: new xorg segfault 11 with KMS
On Thu, Dec 13, 2012 at 6:51 PM, Artyom Mirgorodskiy art...@ijminteractive.net wrote: This patch work for me. Thanks. I can confirm that it also works for me. Thanks a lot! On Friday 14 December 2012 00:30:52 Niclas Zeising wrote: Can you please try the attached patch, against x11-servers/xorg-server. Apply it and recompile xorg-server with normal flags (that is, no debugging) and let me and the list know the result when starting X. Regards! -- This message is for the person(s) named above only and may contain privileged, proprietary, or otherwise private information. If you received this transmission in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
