[ANNOUNCE] dri2proto 2.2
New DRI2 proto release with the new driver type and swap etc. events. Aaron Plattner (1): Add a DRI2DriverVDPAU driver type. Gaetan Nadon (7): .gitignore: use common defaults with custom section # 24239 configure.ac: AM_MAINTAINER_MODE missing #24238 configure.ac: deploy the new XORG_DEFAULT_OPTIONS #24242 Makefile.am: INSTALL file is missing or incorrect #24206 Makefile.am: ChangeLog not required: EXTRA_DIST or *CLEANFILES #24432 README: file created or updated #24206 Makefile.am: add ChangeLog and INSTALL on MAINTAINERCLEANFILES Jesse Barnes (9): Add SwapBuffers request Update protocol description for swapbuffers Add swap interval and synchronization support Fix DRI2SwapBuffers reply length Bump package version to 2.2 Add DRI2SwapInterval protocol Pad out DRI2 swap buffers reply Add DRI2 event support for DRI2BufferSwapComplete Fix cut paste error: Extension Requests - Extension Events Kristian Høgsberg (1): Make swapbuffers an async request git tag: dri2proto-2.2 http://xorg.freedesktop.org/archive/individual/proto/dri2proto-2.2.tar.bz2 MD5: 3ca8ddb42cd4ee31b8690031303221af dri2proto-2.2.tar.bz2 SHA1: 21e9c0c7e0be5fe971f51589d0573b0273202b7f dri2proto-2.2.tar.bz2 http://xorg.freedesktop.org/archive/individual/proto/dri2proto-2.2.tar.gz MD5: df58be4c4485d553337c0cb223a599fc dri2proto-2.2.tar.gz SHA1: 77f5afe65c63c3a9317de743a84d2c1e12fa72bd dri2proto-2.2.tar.gz ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
[ANNOUNCE] glproto 1.4.11
New GL proto with event support. Gaetan Nadon (7): .gitignore: use common defaults with custom section # 24239 configure.ac: AM_MAINTAINER_MODE missing #24238 configure.ac: deploy the new XORG_DEFAULT_OPTIONS #24242 Makefile.am: INSTALL file is missing or incorrect #24206 Makefile.am: ChangeLog not required: EXTRA_DIST or *CLEANFILES #24432 README: file created or updated #24206 Makefile.am: add ChangeLog and INSTALL on MAINTAINERCLEANFILES Jesse Barnes (2): Add GLX swap buffers event support Bump version for release git tag: glproto-1.4.11 http://xorg.freedesktop.org/archive/individual/proto/glproto-1.4.11.tar.bz2 MD5: 78e7c4dc7dcb74b1869fee7897e00f59 glproto-1.4.11.tar.bz2 SHA1: 7c2a723d488dc0e09e7e0e28bde838502d774b16 glproto-1.4.11.tar.bz2 http://xorg.freedesktop.org/archive/individual/proto/glproto-1.4.11.tar.gz MD5: 0753d5ebe5a1b7eae389eb480f8a2df7 glproto-1.4.11.tar.gz SHA1: e643f341d7bcdec529bbdbfaaf68b65ef296fdea glproto-1.4.11.tar.gz ___ xorg-announce mailing list xorg-announce@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg-announce
Re: Xorg crashes...
I'm a novice here - excuse me butting int, and ignore me if this isn't useful. If I understand correctly, you have: a) The X Server receives SIGTERM and exits. b) The source of the SIGTERM is unknown (but perhaps one of the clients of the X Server). c) You can reproduce this by starting X and the console command line. What about tracing all of this with strace? e.g.: strace -fo suitable_log_file_name startx This will generate a vast amount of output, including the part where the X Server receives SIGTERM and exists. Hopefully, a little bit before this, you might see another process sending the SIGTERM with kill(). Cheers Tom 2010/1/7 Ryan Daly d...@ctc.com: On 01/07/2010 05:30 PM, Peter Hutterer wrote: waiting for X server to shut down ddxSigGiveUp: Closing log /Xorg.out I know it says these errors aren't fatal to the X server, but could they be causing me problems? as for xkbcomp doing a quick google gave me this: http://bugs.gentoo.org/269931 but still don't see that this is the culprit. this is a non-fatal error and doesn't affect anything but the warning to be printed out. OK. I won't pursue that, then. Do you have any suggestions on what my next step would be? Have you picked up anything from the backtrace that's attached to the bug report at bugs.launchpad.net? -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: some help please X freeze laptop
-Ursprüngliche Nachricht- Von: Morgan M.C.M-L morgan-informati...@laposte.net Gesendet: 08.01.10 02:02:01 An: cour...@web.de CC: xorg@lists.freedesktop.org Betreff: Re: some help please X freeze laptop Thank you Felix for helping me. I'm a newbee on NetBSD, so : 1- uname -a - 5.0.1-Release, and I've made a netinstallation. I'm a strong Debian user so at the reboot I just start X and there were messages. After analysing all I discover I had nothing ; moving the xorg.conf gives this : but you can still tail -f /var/log/Xorg.0.log tail -f /var/log/Xorg.1.log tail -f /var/log/Xorg.0.log.old !!! Strange because it gives me a black screen but it does not freeze this is a good sign. Pretty sure that you have hal, and dbus already in your userland and up running! The new xorg package on the 5.0.1 image does not need any xorg.conf !!! I've been able to ctrl+alt+F2 and log and shutdown -r now !!! I don't know why it works a little now, perhaps there is little pieces of program somewhere (I tryed to compile pkgsrc yesterday but there were too many errors and it was long i stopped it...) So the laptop isn't frozen without xorg.conf ! 2- for hal and dbus I don't know it is a simple install but whith everything (do I need to compile pkgsrc ???) There is no need to compile pkgsrc! Just get it and keep it update check whether hald and dbus is running e.g ps aux | grep hal file 3- lspci not found - I drop a compilation of pkgsrc this night. Just checkout, or unpack the source into your directory e.g /usr and you are almost done lspci does on *BSD not exist (sorry) you have to look after pciutils Contacting you tomorow. Morgan cour...@web.de a écrit : Hi, try to start x without xorg.conf provided you have packages hal and dbus installed. could you post the output from lspci -vv cheers felix -Ursprüngliche Nachricht- Von: Morgan M.C.M-L morgan-informati...@laposte.net Gesendet: 07.01.10 01:47:33 An: xorg@lists.freedesktop.org Betreff: some help please X freeze laptop Hello I've been installing NetBSD on a laptop Acer Inspire 1350 but I have some trooble with X. 1- 'X -configure' gave me a skeleton in '/root/xorg.conf.new' 2- I wrote in : HorizSync31.5 - 48.0 VertRefresh 59.0 - 75.0 Modes 1024x768 3- 'X -config /root/xorg.conf.new' gave me red/black vertical waves and the lappy was frozen. 4- Changing driver 'Via' by 'Vesa' gave me red/black/blue vertical waves and the lappy was frozen. 5- Trying lots of diferents 'Modes' and 'Refresh' have been the same. 6- xorgconfig gave me a file wich freeze with a black screen. So I think I will ?? Compile a new Xorg ?? Xfree ?? At least I need little help. Here are some files 'Xorg.0.log, xorg.conf, xorg.conf.xorgconfig, dmesg' hr ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg __ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg __ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/07/2010 06:07 PM, Justin P. Mattock wrote: not sure what might be the next step for you at this point. I've an old machine over here, I can throw in ubuntu to see if I hit this as well(you said typing triggers this). with that, you are using gdb to debug, out of curiosity maybe valgrind might provide something(even though it's for memory leaks); keep in mind it might take me a few to get things running on the old beast of a machine. Yes, typing seems to be the trigger...but there are times when it stays up for hours, if not a day or two before exiting on me. Then, once it does it seems to do it frequently if I log in again. Could hardware problems trigger this? I apologize if I'm repeating, but I have Ubuntu 9.10 on three systems, and only this one particular desktop is exhibiting this behavior. (The other two systems are laptops...) This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 08:38 AM, Ryan Daly wrote: On 01/07/2010 06:07 PM, Justin P. Mattock wrote: Yes, typing seems to be the trigger...but there are times when it stays up for hours, if not a day or two before exiting on me. Then, once it does it seems to do it frequently if I log in again. Could hardware problems trigger this? I apologize if I'm repeating, but I have Ubuntu 9.10 on three systems, and only this one particular desktop is exhibiting this behavior. (The other two systems are laptops...) I was able to obtain another backtrace after starting via a tty. This produced a different backtrace from what I'm used to seeing. Although, it could be because I'm using a newer evdev_drv.so. The link where I posted the new backtrace is below: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/499484/comments/7 This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/07/2010 06:11 PM, Dan Nicholson wrote: Not sure this will work, but if it's a symbol resolving problem, you can try to get it to crash faster by using LD_BIND_NOW. LD_BIND_NOW=1 startx `which xterm` X will not start with LD_BIND_NOW set to 1. It's unable to load /usr/lib/xorg/modules/drivers/nv_drv.so. This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On Fri, Jan 8, 2010 at 6:01 AM, Ryan Daly d...@ctc.com wrote: On 01/07/2010 06:11 PM, Dan Nicholson wrote: Not sure this will work, but if it's a symbol resolving problem, you can try to get it to crash faster by using LD_BIND_NOW. LD_BIND_NOW=1 startx `which xterm` X will not start with LD_BIND_NOW set to 1. It's unable to load /usr/lib/xorg/modules/drivers/nv_drv.so. OK, doesn't seem like that's the issue anyway. -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 03:50 AM, Tom Cowell wrote: I'm a novice here - excuse me butting int, and ignore me if this isn't useful. If I understand correctly, you have: a) The X Server receives SIGTERM and exits. b) The source of the SIGTERM is unknown (but perhaps one of the clients of the X Server). c) You can reproduce this by starting X and the console command line. What about tracing all of this with strace? e.g.: strace -fo suitable_log_file_name startx This will generate a vast amount of output, including the part where the X Server receives SIGTERM and exists. Hopefully, a little bit before this, you might see another process sending the SIGTERM with kill(). No, no. Thanks for the input. I've run Xorg under a debugger and it has produced some backtraces. I'm not sure if running strace would produce anything beyond what gdb is already providing. I could be wrong, though. -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 08:59 AM, Pat Kane wrote: On Fri, Jan 8, 2010 at 7:38 AM, Ryan Daly d...@ctc.com wrote: Could hardware problems trigger this? Yes, have you run memcheck on the flakey system? If the first pass is okay, let it run all night. No, I have not. I'm not familiar with that tool. I'll look into that, but if you can pass on any pointers it'd be appreciated. -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
I was responding to this remark from Peter Hutterer: uhm. SIGTERM is the termination signal. Something's shutting down your server. If SIGTERM is coming from another process, then the debugger won't provide any information about _which_ process. However, a recursive strace of startx (and all its children and grandchildren) _might_ identify the source of the signal. Even if the X Server is killing itself with SIGTERM, that would be worth knowing. However, if it stays up for days before crashing, strace might generate an unacceptable amount of output. Cheers Tom 2010/1/8 Ryan Daly d...@ctc.com: On 01/08/2010 03:50 AM, Tom Cowell wrote: I'm a novice here - excuse me butting int, and ignore me if this isn't useful. If I understand correctly, you have: a) The X Server receives SIGTERM and exits. b) The source of the SIGTERM is unknown (but perhaps one of the clients of the X Server). c) You can reproduce this by starting X and the console command line. What about tracing all of this with strace? e.g.: strace -fo suitable_log_file_name startx This will generate a vast amount of output, including the part where the X Server receives SIGTERM and exists. Hopefully, a little bit before this, you might see another process sending the SIGTERM with kill(). No, no. Thanks for the input. I've run Xorg under a debugger and it has produced some backtraces. I'm not sure if running strace would produce anything beyond what gdb is already providing. I could be wrong, though. -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 10:11 AM, Tom Cowell wrote: I was responding to this remark from Peter Hutterer: uhm. SIGTERM is the termination signal. Something's shutting down your server. If SIGTERM is coming from another process, then the debugger won't provide any information about _which_ process. However, a recursive strace of startx (and all its children and grandchildren) _might_ identify the source of the signal. Even if the X Server is killing itself with SIGTERM, that would be worth knowing. However, if it stays up for days before crashing, strace might generate an unacceptable amount of output. I gotcha... I'll try that and post any relevant information. -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 10:19 AM, Pat Kane wrote: See: http://www.memtest.org/ Many boot/live CDs have memtest as an option when booting from them. I know that my Fedora and Ubuntu install CDs let me boot into memtest. Ahh, OK. I have used that tool before. I'll run the 'strace' as suggested earlier and see what happens there first. This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/10 07:03, Ryan Daly wrote: On 01/08/2010 08:59 AM, Pat Kane wrote: On Fri, Jan 8, 2010 at 7:38 AM, Ryan Dalyd...@ctc.com wrote: Could hardware problems trigger this? Yes, have you run memcheck on the flakey system? If the first pass is okay, let it run all night. No, I have not. I'm not familiar with that tool. I'll look into that, but if you can pass on any pointers it'd be appreciated. -- well looking at your debug log you provided on launchpad It seems to be doing something with nss before crapping out as well as something with libc and tls. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 10:30 AM, Justin P. Mattock wrote: well looking at your debug log you provided on launchpad It seems to be doing something with nss before crapping out as well as something with libc and tls. The screen left some output that may be of interest, too. (I transposed this manually, so please excuse any typos.) Backtrace: 0: /usr/bin/X11/X(xorg_backtrace+0x3b) [0x8133d6b] 1: /usr/bin/X11/X(xf86SigHandler+0x55) [0x80c7d35] 2: [0xdd1400] 3: /usr/bin/X11/X(GetKeyboardValuatorEvents+0x314) [0x80a0e94] 4: /usr/bin/X11/X(GetKeyboardEvents+0x4a) [0x80a0f4a] 5: /usr/bin/X11/X(xf86PostKeyboardEvent+0x8f) [0x80d81bf] 6: /usr/lib/xorg/modules/input//evdev_drv.so [0x29da3a] 7: /usr/bin/X11/X [0x80c7ef7] 8: /usr/bin/X11/X [0x80b87b4] 9: [0xdd1400] 10: /usr/bin/X11/X(Dispatch+0x98) [0x808ceb8] 11: /usr/bin/X11/X(main+0x395) [0x8072515] 12: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0x126b56] 13: /usr/bin/X11/X [0x80719c1] Saw signal 11. Server aborting. ddxSigGiveUp: Closing log ddxSigGiveUp: re-raising 11 xinit: connection to S server lost. Looking at the backtrace, is the most recent entry (i.e. 0:) the function call that it was last in before the signal 11? -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On Fri, Jan 8, 2010 at 8:19 AM, Dan Nicholson dbn.li...@gmail.com wrote: On Fri, Jan 8, 2010 at 7:19 AM, Ryan Daly d...@ctc.com wrote: On 01/08/2010 10:11 AM, Tom Cowell wrote: I was responding to this remark from Peter Hutterer: uhm. SIGTERM is the termination signal. Something's shutting down your server. If SIGTERM is coming from another process, then the debugger won't provide any information about _which_ process. However, a recursive strace of startx (and all its children and grandchildren) _might_ identify the source of the signal. Even if the X Server is killing itself with SIGTERM, that would be worth knowing. However, if it stays up for days before crashing, strace might generate an unacceptable amount of output. I gotcha... I'll try that and post any relevant information. FYI, the error in the log on launchpad was a segfault (SIGSEGV), so you appear to have two different errors. The segfault (signal 11) should be fixable. The mysterious SIGTERM might be tough to handle since it could come from anywhere. Peter, do you have any ideas about this one: http://launchpadlibrarian.net/37615863/gdb-Xorg.txt -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/10 08:18, Ryan Daly wrote: On 01/08/2010 10:30 AM, Justin P. Mattock wrote: well looking at your debug log you provided on launchpad It seems to be doing something with nss before crapping out as well as something with libc and tls. The screen left some output that may be of interest, too. (I transposed this manually, so please excuse any typos.) Backtrace: 0: /usr/bin/X11/X(xorg_backtrace+0x3b) [0x8133d6b] 1: /usr/bin/X11/X(xf86SigHandler+0x55) [0x80c7d35] 2: [0xdd1400] 3: /usr/bin/X11/X(GetKeyboardValuatorEvents+0x314) [0x80a0e94] 4: /usr/bin/X11/X(GetKeyboardEvents+0x4a) [0x80a0f4a] 5: /usr/bin/X11/X(xf86PostKeyboardEvent+0x8f) [0x80d81bf] 6: /usr/lib/xorg/modules/input//evdev_drv.so [0x29da3a] 7: /usr/bin/X11/X [0x80c7ef7] 8: /usr/bin/X11/X [0x80b87b4] 9: [0xdd1400] 10: /usr/bin/X11/X(Dispatch+0x98) [0x808ceb8] 11: /usr/bin/X11/X(main+0x395) [0x8072515] 12: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0x126b56] 13: /usr/bin/X11/X [0x80719c1] Saw signal 11. Server aborting. ddxSigGiveUp: Closing log ddxSigGiveUp: re-raising 11 xinit: connection to S server lost. Looking at the backtrace, is the most recent entry (i.e. 0:) the function call that it was last in before the signal 11? -- hmmm.. I'm seeing tls in the mix. wondering if there's a missing switch somewhere i.g. libc has a tls switch, mesa, as well as xserver but then again could be something other than this. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On Fri, Jan 8, 2010 at 7:19 AM, Ryan Daly d...@ctc.com wrote: On 01/08/2010 10:11 AM, Tom Cowell wrote: I was responding to this remark from Peter Hutterer: uhm. SIGTERM is the termination signal. Something's shutting down your server. If SIGTERM is coming from another process, then the debugger won't provide any information about _which_ process. However, a recursive strace of startx (and all its children and grandchildren) _might_ identify the source of the signal. Even if the X Server is killing itself with SIGTERM, that would be worth knowing. However, if it stays up for days before crashing, strace might generate an unacceptable amount of output. I gotcha... I'll try that and post any relevant information. FYI, the error in the log on launchpad was a segfault (SIGSEGV), so you appear to have two different errors. The segfault (signal 11) should be fixable. The mysterious SIGTERM might be tough to handle since it could come from anywhere. -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
FYI, the error in the log on launchpad was a segfault (SIGSEGV), so you appear to have two different errors. The segfault (signal 11) should be fixable. The mysterious SIGTERM might be tough to handle since it could come from anywhere. Indeed. Some of the debugger traces (the earlier ones, on the whole) have SIGTERM, and some have SIGSEGV. What I have proposed is (probably) only any use for the SIGTERM cases. Cheers Tom ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: some help please X freeze laptop
Hello tail -f /var/log/Xorg.0.log - attached tail.log0 tail -f /var/log/Xorg.1.log - file dos not exist (probably because I've erased 2 times some log) tail -f /var/log/Xorg.0.log.old - attached tail.log0.old But taking a look at 'dbus' and 'hal', (I began to anderstand : HAL Hardware Abstraction Layer), I've seen I have not the deamons running. --- ps -aux | grep hald - nothing ps -aux | grep dbus - nothing --- looking for pciutils and lspci --- Thank you for taking time to help me, someone gave the pkgsrc guide link - reading this, I knew I had to do this before but i felt self confident with my debian experience, I'll contact you when I'l have more tools like lspci, pciutils and more. Best regards, Morgan -- cour...@web.de a écrit : -Ursprüngliche Nachricht- Von: Morgan M.C.M-L morgan-informati...@laposte.net Gesendet: 08.01.10 02:02:01 An: cour...@web.de CC: xorg@lists.freedesktop.org Betreff: Re: some help please X freeze laptop Thank you Felix for helping me. I'm a newbee on NetBSD, so : 1- uname -a - 5.0.1-Release, and I've made a netinstallation. I'm a strong Debian user so at the reboot I just start X and there were messages. After analysing all I discover I had nothing ; moving the xorg.conf gives this : but you can still tail -f /var/log/Xorg.0.log tail -f /var/log/Xorg.1.log tail -f /var/log/Xorg.0.log.old !!! Strange because it gives me a black screen but it does not freeze this is a good sign. Pretty sure that you have hal, and dbus already in your userland and up running! The new xorg package on the 5.0.1 image does not need any xorg.conf !!! I've been able to ctrl+alt+F2 and log and shutdown -r now !!! I don't know why it works a little now, perhaps there is little pieces of program somewhere (I tryed to compile pkgsrc yesterday but there were too many errors and it was long i stopped it...) So the laptop isn't frozen without xorg.conf ! 2- for hal and dbus I don't know it is a simple install but whith everything (do I need to compile pkgsrc ???) There is no need to compile pkgsrc! Just get it and keep it update check whether hald and dbus is running e.g ps aux | grep hal file 3- lspci not found - I drop a compilation of pkgsrc this night. Just checkout, or unpack the source into your directory e.g /usr and you are almost done lspci does on *BSD not exist (sorry) you have to look after pciutils Contacting you tomorow. Morgan cour...@web.de a écrit : Hi, try to start x without xorg.conf provided you have packages hal and dbus installed. could you post the output from lspci -vv cheers felix -Ursprüngliche Nachricht- Von: Morgan M.C.M-L morgan-informati...@laposte.net Gesendet: 07.01.10 01:47:33 An: xorg@lists.freedesktop.org Betreff: some help please X freeze laptop Hello I've been installing NetBSD on a laptop Acer Inspire 1350 but I have some trooble with X. 1- 'X -configure' gave me a skeleton in '/root/xorg.conf.new' 2- I wrote in : HorizSync31.5 - 48.0 VertRefresh 59.0 - 75.0 Modes 1024x768 3- 'X -config /root/xorg.conf.new' gave me red/black vertical waves and the lappy was frozen. 4- Changing driver 'Via' by 'Vesa' gave me red/black/blue vertical waves and the lappy was frozen. 5- Trying lots of diferents 'Modes' and 'Refresh' have been the same. 6- xorgconfig gave me a file wich freeze with a black screen. So I think I will ?? Compile a new Xorg ?? Xfree ?? At least I need little help. Here are some files 'Xorg.0.log, xorg.conf, xorg.conf.xorgconfig, dmesg' hr ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg __ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg __ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] dri2proto 2.2
New DRI2 proto release with the new driver type and swap etc. events. Aaron Plattner (1): Add a DRI2DriverVDPAU driver type. Gaetan Nadon (7): .gitignore: use common defaults with custom section # 24239 configure.ac: AM_MAINTAINER_MODE missing #24238 configure.ac: deploy the new XORG_DEFAULT_OPTIONS #24242 Makefile.am: INSTALL file is missing or incorrect #24206 Makefile.am: ChangeLog not required: EXTRA_DIST or *CLEANFILES #24432 README: file created or updated #24206 Makefile.am: add ChangeLog and INSTALL on MAINTAINERCLEANFILES Jesse Barnes (9): Add SwapBuffers request Update protocol description for swapbuffers Add swap interval and synchronization support Fix DRI2SwapBuffers reply length Bump package version to 2.2 Add DRI2SwapInterval protocol Pad out DRI2 swap buffers reply Add DRI2 event support for DRI2BufferSwapComplete Fix cut paste error: Extension Requests - Extension Events Kristian Høgsberg (1): Make swapbuffers an async request git tag: dri2proto-2.2 http://xorg.freedesktop.org/archive/individual/proto/dri2proto-2.2.tar.bz2 MD5: 3ca8ddb42cd4ee31b8690031303221af dri2proto-2.2.tar.bz2 SHA1: 21e9c0c7e0be5fe971f51589d0573b0273202b7f dri2proto-2.2.tar.bz2 http://xorg.freedesktop.org/archive/individual/proto/dri2proto-2.2.tar.gz MD5: df58be4c4485d553337c0cb223a599fc dri2proto-2.2.tar.gz SHA1: 77f5afe65c63c3a9317de743a84d2c1e12fa72bd dri2proto-2.2.tar.gz ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] glproto 1.4.11
New GL proto with event support. Gaetan Nadon (7): .gitignore: use common defaults with custom section # 24239 configure.ac: AM_MAINTAINER_MODE missing #24238 configure.ac: deploy the new XORG_DEFAULT_OPTIONS #24242 Makefile.am: INSTALL file is missing or incorrect #24206 Makefile.am: ChangeLog not required: EXTRA_DIST or *CLEANFILES #24432 README: file created or updated #24206 Makefile.am: add ChangeLog and INSTALL on MAINTAINERCLEANFILES Jesse Barnes (2): Add GLX swap buffers event support Bump version for release git tag: glproto-1.4.11 http://xorg.freedesktop.org/archive/individual/proto/glproto-1.4.11.tar.bz2 MD5: 78e7c4dc7dcb74b1869fee7897e00f59 glproto-1.4.11.tar.bz2 SHA1: 7c2a723d488dc0e09e7e0e28bde838502d774b16 glproto-1.4.11.tar.bz2 http://xorg.freedesktop.org/archive/individual/proto/glproto-1.4.11.tar.gz MD5: 0753d5ebe5a1b7eae389eb480f8a2df7 glproto-1.4.11.tar.gz SHA1: e643f341d7bcdec529bbdbfaaf68b65ef296fdea glproto-1.4.11.tar.gz ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/10 09:37, Tom Cowell wrote: FYI, the error in the log on launchpad was a segfault (SIGSEGV), so you appear to have two different errors. The segfault (signal 11) should be fixable. The mysterious SIGTERM might be tough to handle since it could come from anywhere. Indeed. Some of the debugger traces (the earlier ones, on the whole) have SIGTERM, and some have SIGSEGV. What I have proposed is (probably) only any use for the SIGTERM cases. Cheers Tom ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg gripes!! valgrind breaks with libc 2.11.90(I'll see later on this), In your case what does valgrind output's say when the crash occurs? Justin P. mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/2010 03:56 PM, Justin P. Mattock wrote: gripes!! valgrind breaks with libc 2.11.90(I'll see later on this), In your case what does valgrind output's say when the crash occurs? Did you use any options with valgrind or just 'valgrind startx'? This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/08/10 13:05, Ryan Daly wrote: On 01/08/2010 03:56 PM, Justin P. Mattock wrote: gripes!! valgrind breaks with libc 2.11.90(I'll see later on this), In your case what does valgrind output's say when the crash occurs? Did you use any options with valgrind or just 'valgrind startx'? not yet(breaks with libc2.11.90) if I can get this thing fixed then I can see. but from past experiences I think theirs a log file valgrind creates. i.g. valgrind --tool=memcheck(or other) --log-file=(some-file) programname (as soon as I figure/find something I can run valgrind over here to see what it produces) you never know could find something. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
