Xorg crashes - maybe someone can help.
Since about a month and a half I've been experiencing Xorg crashes. I'm using KDE and it maybe the problem, but maybe it is not - I don't know and don't know how to tell. I'm using Dell D430 with Intel i945GM graphics. I'm using the latest available stable drivers. Here are some examples of segfaults from Xorg logs: First try: [61.068] X.Org X Server 1.10.1 Release Date: 2011-04-15 [61.083] X Protocol Version 11, Revision 0 [61.083] Build Operating System: PLD/Linux PLD/Team [61.083] Current Operating System: Linux laptok 2.6.38.2-2 #1 SMP Sat Apr 2 11:11:59 CEST 2011 i686 [61.083] Kernel command line: auto BOOT_IMAGE=test root=302 resume=/dev/hda7 5 [61.083] Build Date: 16 April 2011 08:26:05AM [61.083] [61.083] Current version of pixman: 0.20.2 [...] [ 12764.361] Backtrace: [ 12764.361] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80df337] [ 12764.362] 1: /usr/bin/X (0x8048000+0x5905a) [0x80a105a] [ 12764.362] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb7702410] [ 12764.362] 3: /usr/lib/xorg/modules/extensions/libglx.so (0xb735b000+0x31e9a) [0xb738ce9a] [ 12764.362] 4: /usr/bin/X (FreeClientResources+0xe4) [0x808b763] [ 12764.362] 5: /usr/bin/X (FreeAllResources+0x51) [0x808b81e] [ 12764.362] 6: /usr/bin/X (0x8048000+0x1a346) [0x8062346] [ 12764.362] 7: /lib/libc.so.6 (__libc_start_main+0xf2) [0xb7490dee] [ 12764.362] Segmentation fault at address 0x29fec5c0 [ 12764.362] Fatal server error: [ 12764.362] Caught signal 11 (Segmentation fault). Server aborting Second try: [ 13931.591] X.Org X Server 1.10.1 Release Date: 2011-04-15 [ 13931.591] X Protocol Version 11, Revision 0 [ 13931.591] Build Operating System: PLD/Linux PLD/Team [ 13931.591] Current Operating System: Linux laptok 2.6.38.2-2 #1 SMP Sat Apr 2 11:11:59 CEST 2011 i686 [ 13931.591] Kernel command line: auto BOOT_IMAGE=test root=302 resume=/dev/hda7 5 [ 13931.591] Build Date: 16 April 2011 08:26:05AM [ 13931.591] [ 13931.591] Current version of pixman: 0.22.0 [...] [ 22931.194] Backtrace: [ 22931.195] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80df337] [ 22931.195] 1: /usr/bin/X (0x8048000+0x5905a) [0x80a105a] [ 22931.195] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb770d410] [ 22931.195] 3: /usr/bin/X (FreeClientResources+0xe4) [0x808b763] [ 22931.195] 4: /usr/bin/X (FreeAllResources+0x51) [0x808b81e] [ 22931.195] 5: /usr/bin/X (0x8048000+0x1a346) [0x8062346] [ 22931.195] 6: /lib/libc.so.6 (__libc_start_main+0xf2) [0xb7496dee] [ 22931.195] Segmentation fault at address (nil) [ 22931.195] Fatal server error: [ 22931.195] Caught signal 11 (Segmentation fault). Server aborting Third try: [69.913] X.Org X Server 1.10.1 Release Date: 2011-04-15 [69.928] X Protocol Version 11, Revision 0 [69.928] Build Operating System: PLD/Linux PLD/Team [69.928] Current Operating System: Linux laptok 2.6.38.6_nogrsecurity-0.1 #1 SMP Tue May 10 22:27:55 CEST 2011 i686 [69.928] Kernel command line: BOOT_IMAGE=test root=302 resume=/dev/hda7 5 [69.928] Build Date: 16 April 2011 08:26:05AM [69.928] [69.928] Current version of pixman: 0.22.0 [...] [ 20741.240] Backtrace: [ 20741.264] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80df337] [ 20741.264] 1: /usr/bin/X (0x8048000+0x5905a) [0x80a105a] [ 20741.265] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb779b40c] [ 20741.265] 3: /usr/bin/X (FreeResource+0xea) [0x808b13b] [ 20741.265] 4: /usr/bin/X (0x8048000+0x21c18) [0x8069c18] [ 20741.265] 5: /usr/bin/X (0x8048000+0x26362) [0x806e362] [ 20741.265] 6: /usr/bin/X (0x8048000+0x1a31a) [0x806231a] [ 20741.265] 7: /lib/libc.so.6 (__libc_start_main+0xf2) [0xb7524dee] [ 20741.265] Segmentation fault at address 0x24 [ 20741.265] Fatal server error: [ 20741.265] Caught signal 11 (Segmentation fault). Server aborting >From time to time after such segfault my screen is not getting back to the console and I have to reboot my laptop. Does anyone have an idea, if the problem is in Xorg, in kernel (errors suggest, that the error comes from there but may be caused by parameters coming from somewhere else) or in KDE? -- Łukasz Maśko GG: 2441498_o) Lukasz.Masko(at)ipipan.waw.pl /\\ Registered Linux User #61028 _\_V Ubuntu: staroafrykańskie słowo oznaczające "Nie umiem zainstalować Debiana" ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Xorg crashes...
On Mon, 2010-02-22 at 22:44 +0100, Tom Cowell wrote: > Well, that's good news (unless your email has triggered the problem again!). Not yet. ;) > Just out of curiosity, has another auto-generated .xmodmaprc appeared? No new .xmodmaprc file has appeared. I'm thinking that may have been something left behind from my FVWM days... -- 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 Mon, 2010-01-18 at 22:48 +0100, Tom Cowell wrote:
> Well, according to my primitive understanding, xmodmap is normally
> used for a little bit of tweaking of the keyboard layout (fiddling
> with delete and backspace, for instance, or swapping CapsLock and
> Ctrl).
>
> Your file looks odd to me ("slash question slash question slash
> question"). Since you didn't write it, it was presumably generated by
> some piece of software, and maybe a confused and over-enthusiastic
> piece of software. I don't have 248 keys on my keyboard.
>
> If you are really lucky, then this was the entire source of your
> problem. It might be informative to run the xmodmap command with this
> file as an argument, and see if it instantly causes problems.
Strange as it may be, I have been problem free since removing my
$HOME/.xmodmaprc file. It's been a little over a month, so I think I'm
safe in saying that. :)
--
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...
Well, according to my primitive understanding, xmodmap is normally
used for a little bit of tweaking of the keyboard layout (fiddling
with delete and backspace, for instance, or swapping CapsLock and
Ctrl).
Your file looks odd to me ("slash question slash question slash
question"). Since you didn't write it, it was presumably generated by
some piece of software, and maybe a confused and over-enthusiastic
piece of software. I don't have 248 keys on my keyboard.
If you are really lucky, then this was the entire source of your
problem. It might be informative to run the xmodmap command with this
file as an argument, and see if it instantly causes problems.
Cheers
Tom
2010/1/18 Ryan Daly :
> On 01/18/2010 04:23 PM, Tom Cowell wrote:
>> What was/is in the .xmodmaprc?
>
> 248 lines of things like this:
>
> keycode 61 = slash question slash question slash question
> keycode 62 = Shift_R NoSymbol Shift_R NoSymbol Shift_R
> keycode 63 = KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab
> KP_Multiply XF86_ClearGrab
> keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L
> keycode 65 = space NoSymbol space NoSymbol space
> keycode 66 = Caps_Lock NoSymbol Caps_Lock NoSymbol Caps_Lock
> --
>
>
> 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/18/2010 04:23 PM, Tom Cowell wrote: > What was/is in the .xmodmaprc? 248 lines of things like this: keycode 61 = slash question slash question slash question keycode 62 = Shift_R NoSymbol Shift_R NoSymbol Shift_R keycode 63 = KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab KP_Multiply XF86_ClearGrab keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L keycode 65 = space NoSymbol space NoSymbol space keycode 66 = Caps_Lock NoSymbol Caps_Lock NoSymbol Caps_Lock -- 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...
What was/is in the .xmodmaprc? 2010/1/18 Ryan Daly : > On 01/18/2010 03:17 PM, Ryan Daly wrote: >> I was able to start Xorg w/ 'startx' as root. I'm writing trace files >> out, so as soon as I get it to exit on me, I'll look through and see >> what's left. > > One bad thing... The strace files started taking up so much room that I > needed to stop the session I was running. > > But, I noticed something while I was running as "root." I was up for > about 3 hours without any trouble. I noticed while I was logged in that > my alt, shift, and ctrl keys weren't working. That prompted me to start > poking around and I found that I had a $HOME/.xmodmaprc. I'm wondering > if this could have any impact on things. Could it be possible that > something was mapped in such a way that when a particular key sequence > was hit it caused my session to exit? I know Gnome maps keys on its > own. Maybe I was confusing things by having $HOME/.xmodmaprc in place. > > I have since removed $HOME/.xmodmaprc and restarted my X session, but > I'm running as myself. I'm still unable to strace this because of the > earlier permissions issue that was posted. I'd still like to hear > thoughts regarding this, though. Thanks. > > > 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: Xorg crashes...
On 01/18/10 13:12, Ryan Daly wrote: > On 01/18/2010 03:17 PM, Ryan Daly wrote: >> I was able to start Xorg w/ 'startx' as root. I'm writing trace files >> out, so as soon as I get it to exit on me, I'll look through and see >> what's left. > > One bad thing... The strace files started taking up so much room that I > needed to stop the session I was running. > > But, I noticed something while I was running as "root." I was up for > about 3 hours without any trouble. I noticed while I was logged in that > my alt, shift, and ctrl keys weren't working. That prompted me to start > poking around and I found that I had a $HOME/.xmodmaprc. I'm wondering > if this could have any impact on things. Could it be possible that > something was mapped in such a way that when a particular key sequence > was hit it caused my session to exit? I know Gnome maps keys on its > own. Maybe I was confusing things by having $HOME/.xmodmaprc in place. > > I have since removed $HOME/.xmodmaprc and restarted my X session, but > I'm running as myself. I'm still unable to strace this because of the > earlier permissions issue that was posted. I'd still like to hear > thoughts regarding this, though. Thanks. > > could be... but then again you might just receive some error message on your screen once exiting out of the xserver. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/18/2010 03:17 PM, Ryan Daly wrote: > I was able to start Xorg w/ 'startx' as root. I'm writing trace files > out, so as soon as I get it to exit on me, I'll look through and see > what's left. One bad thing... The strace files started taking up so much room that I needed to stop the session I was running. But, I noticed something while I was running as "root." I was up for about 3 hours without any trouble. I noticed while I was logged in that my alt, shift, and ctrl keys weren't working. That prompted me to start poking around and I found that I had a $HOME/.xmodmaprc. I'm wondering if this could have any impact on things. Could it be possible that something was mapped in such a way that when a particular key sequence was hit it caused my session to exit? I know Gnome maps keys on its own. Maybe I was confusing things by having $HOME/.xmodmaprc in place. I have since removed $HOME/.xmodmaprc and restarted my X session, but I'm running as myself. I'm still unable to strace this because of the earlier permissions issue that was posted. I'd still like to hear thoughts regarding this, though. Thanks. 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/11/2010 09:16 AM, Tom Cowell wrote: > Yes, that's what I meant. I suppose the action of strace (and > valgrind, probably) will slow things down, so maybe the "timeout" > messages can be taken at face value, and maybe there is a timeout that > can be increased so that the strace/valgrind of startx as root can be > made to work. > > I'll look in man pages and let you know if I find anything. > I was able to start Xorg w/ 'startx' as root. I'm writing trace files out, so as soon as I get it to exit on me, I'll look through and see what's left. 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...
2010/1/11 Ryan Daly : > On 01/11/2010 09:00 AM, Tom Cowell wrote: >> Does it work as root if you run it without strace or valgrind? >> >> Can you tell I'm getting out of my depth? > > startx works as root if that's what you mean... > Yes, that's what I meant. I suppose the action of strace (and valgrind, probably) will slow things down, so maybe the "timeout" messages can be taken at face value, and maybe there is a timeout that can be increased so that the strace/valgrind of startx as root can be made to work. I'll look in man pages and let you know if I find anything. Cheers Tom ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/11/2010 09:00 AM, Tom Cowell wrote: > Does it work as root if you run it without strace or valgrind? > > Can you tell I'm getting out of my depth? startx works as root if that's what you mean... 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/11/10 06:04, Ryan Daly wrote: > On 01/11/2010 09:02 AM, Justin P. Mattock wrote: >> On 01/11/10 05:53, Ryan Daly wrote: >>> On 01/11/2010 08:47 AM, Tom Cowell wrote: Ah yes. My strace suggestion would have the same problem. On my machine (and presumably yours) the Xorg binary is setuid-root - it acquires elevated permissions when you run it, and this breaks the process tracing (and it seems odd to me (though I haven't tried) that you were able to debug it). You could try repeating your valgrind test as root, maybe. >>> >>> I did try the strace as root, but I received errors there, too: >>> >>> >>> xauth: timeout in locking authority file /root/.Xauthority >>> xauth: timeout in locking authority file /root/.Xauthority >>> xauth: timeout in locking authority file /root/.Xauthority >>> xauth: timeout in locking authority file /root/.Xauthority >>> >>> X: unable to open wrapper config file /etc/X11/Xwrapper.config >>> X: user not authorized to run the X server, aborting. >>> giving up. >>> xinit: No such file or directory (errno 2): unable to connect to X >>> server >>> xinit: No such process (errno 3): Server error. >>> xauth: timeout in locking authority file /root/.Xauthority >>> >>> >> >> my bad didn't even think about setuid(thought valgrind >> would work without the whole root thing). >> I guess abort that idea. > > No problem... Let me know if you come up with anything else I can try... > -- cool, at the moment away from myoffice(remotely), if anything comes to mind I'll think outloud with a post.. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/11/2010 09:02 AM, Justin P. Mattock wrote: > On 01/11/10 05:53, Ryan Daly wrote: >> On 01/11/2010 08:47 AM, Tom Cowell wrote: >>> Ah yes. My strace suggestion would have the same problem. >>> >>> On my machine (and presumably yours) the Xorg binary is setuid-root - >>> it acquires elevated permissions when you run it, and this breaks the >>> process tracing (and it seems odd to me (though I haven't tried) that >>> you were able to debug it). >>> >>> You could try repeating your valgrind test as root, maybe. >> >> I did try the strace as root, but I received errors there, too: >> >> >> xauth: timeout in locking authority file /root/.Xauthority >> xauth: timeout in locking authority file /root/.Xauthority >> xauth: timeout in locking authority file /root/.Xauthority >> xauth: timeout in locking authority file /root/.Xauthority >> >> X: unable to open wrapper config file /etc/X11/Xwrapper.config >> X: user not authorized to run the X server, aborting. >> giving up. >> xinit: No such file or directory (errno 2): unable to connect to X >> server >> xinit: No such process (errno 3): Server error. >> xauth: timeout in locking authority file /root/.Xauthority >> >> > > my bad didn't even think about setuid(thought valgrind > would work without the whole root thing). > I guess abort that idea. No problem... Let me know if you come up with anything else I can try... -- 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/11/2010 08:21 AM, Ryan Daly wrote: > Maybe I'm starting this wrong, but I'm getting the following: > > > prompt> valgrind --log-file=/usr2/tmp/valgrind.out --trace-children=yes > startx > > exec: 5: /usr/bin/X11/X: Permission denied > giving up. > /usr/bin/xinit: No such file or directory (errno 2): unable to connect > to X server > /usr/bin/xinit: No such process (errno 3): Server error. > > > I tried this late last week, but the child process of startx didn't get > traced, which doesn't seem like it would be of much value. > valgrind doesn't start as root, either: exec: 5: /usr/bin/X11/X: Permission denied giving up. /usr/bin/xinit: No such file or directory (errno 2): unable to connect to X server /usr/bin/xinit: No such process (errno 3): Server error. Same type of error... 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/11/10 05:53, Ryan Daly wrote: > On 01/11/2010 08:47 AM, Tom Cowell wrote: >> Ah yes. My strace suggestion would have the same problem. >> >> On my machine (and presumably yours) the Xorg binary is setuid-root - >> it acquires elevated permissions when you run it, and this breaks the >> process tracing (and it seems odd to me (though I haven't tried) that >> you were able to debug it). >> >> You could try repeating your valgrind test as root, maybe. > > I did try the strace as root, but I received errors there, too: > > > xauth: timeout in locking authority file /root/.Xauthority > xauth: timeout in locking authority file /root/.Xauthority > xauth: timeout in locking authority file /root/.Xauthority > xauth: timeout in locking authority file /root/.Xauthority > > X: unable to open wrapper config file /etc/X11/Xwrapper.config > X: user not authorized to run the X server, aborting. > giving up. > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. > xauth: timeout in locking authority file /root/.Xauthority > > my bad didn't even think about setuid(thought valgrind would work without the whole root thing). I guess abort that idea. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
Does it work as root if you run it without strace or valgrind? Can you tell I'm getting out of my depth? Tom 2010/1/11 Ryan Daly : > On 01/11/2010 08:47 AM, Tom Cowell wrote: >> Ah yes. My strace suggestion would have the same problem. >> >> On my machine (and presumably yours) the Xorg binary is setuid-root - >> it acquires elevated permissions when you run it, and this breaks the >> process tracing (and it seems odd to me (though I haven't tried) that >> you were able to debug it). >> >> You could try repeating your valgrind test as root, maybe. > > I did try the strace as root, but I received errors there, too: > > > xauth: timeout in locking authority file /root/.Xauthority > xauth: timeout in locking authority file /root/.Xauthority > xauth: timeout in locking authority file /root/.Xauthority > xauth: timeout in locking authority file /root/.Xauthority > > X: unable to open wrapper config file /etc/X11/Xwrapper.config > X: user not authorized to run the X server, aborting. > giving up. > xinit: No such file or directory (errno 2): unable to connect to X server > xinit: No such process (errno 3): Server error. > xauth: timeout in locking authority file /root/.Xauthority > > > 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/11/2010 08:47 AM, Tom Cowell wrote: > Ah yes. My strace suggestion would have the same problem. > > On my machine (and presumably yours) the Xorg binary is setuid-root - > it acquires elevated permissions when you run it, and this breaks the > process tracing (and it seems odd to me (though I haven't tried) that > you were able to debug it). > > You could try repeating your valgrind test as root, maybe. I did try the strace as root, but I received errors there, too: xauth: timeout in locking authority file /root/.Xauthority xauth: timeout in locking authority file /root/.Xauthority xauth: timeout in locking authority file /root/.Xauthority xauth: timeout in locking authority file /root/.Xauthority X: unable to open wrapper config file /etc/X11/Xwrapper.config X: user not authorized to run the X server, aborting. giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. xauth: timeout in locking authority file /root/.Xauthority 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...
Ah yes. My strace suggestion would have the same problem. On my machine (and presumably yours) the Xorg binary is setuid-root - it acquires elevated permissions when you run it, and this breaks the process tracing (and it seems odd to me (though I haven't tried) that you were able to debug it). You could try repeating your valgrind test as root, maybe. Cheers Tom 2010/1/11 Ryan Daly : > On 01/08/2010 04:13 PM, Justin P. Mattock wrote: >> 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. > > Maybe I'm starting this wrong, but I'm getting the following: > > > prompt> valgrind --log-file=/usr2/tmp/valgrind.out --trace-children=yes > startx > > exec: 5: /usr/bin/X11/X: Permission denied > giving up. > /usr/bin/xinit: No such file or directory (errno 2): unable to connect > to X server > /usr/bin/xinit: No such process (errno 3): Server error. > > > I tried this late last week, but the child process of startx didn't get > traced, which doesn't seem like it would be of much value. > > > 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 04:13 PM, Justin P. Mattock wrote: > 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. Maybe I'm starting this wrong, but I'm getting the following: prompt> valgrind --log-file=/usr2/tmp/valgrind.out --trace-children=yes startx exec: 5: /usr/bin/X11/X: Permission denied giving up. /usr/bin/xinit: No such file or directory (errno 2): unable to connect to X server /usr/bin/xinit: No such process (errno 3): Server error. I tried this late last week, but the child process of startx didn't get traced, which doesn't seem like it would be of much value. 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
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 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...
> > 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: Xorg crashes...
On Fri, Jan 8, 2010 at 7:19 AM, Ryan Daly 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...
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 8:19 AM, Dan Nicholson wrote: > On Fri, Jan 8, 2010 at 7:19 AM, Ryan Daly 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/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 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 Daly 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: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/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...
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 : > 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 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 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...
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 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 Fri, Jan 8, 2010 at 6:01 AM, Ryan Daly 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/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 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: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...
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 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 : > On 01/07/2010 05:30 PM, Peter Hutterer wrote: waiting for X server to shut down ddxSigGiveUp: Closing log 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: Xorg crashes...
On Thu, Jan 7, 2010 at 2:45 PM, Ryan Daly wrote: > On 01/07/2010 05:30 PM, Peter Hutterer wrote: waiting for X server to shut down ddxSigGiveUp: Closing log 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? 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` -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/07/10 14:45, Ryan Daly wrote: > On 01/07/2010 05:30 PM, Peter Hutterer wrote: waiting for X server to shut down ddxSigGiveUp: Closing log 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? > -- 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. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/07/2010 05:30 PM, Peter Hutterer wrote: >>> waiting for X server to shut down ddxSigGiveUp: Closing log >>> >>> >>> 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
Re: Xorg crashes...
On Thu, Jan 07, 2010 at 10:25:33AM -0800, Justin P. Mattock wrote: > >Bad news... I started X from a tty and still had it exit on me. The > >only thing worth noting from the output is below: > > > > > >The XKEYBOARD keymap compiler (xkbcomp) reports: > > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 > > symbols > > >Ignoring extra symbols > >Errors from xkbcomp are not fatal to the X server > >The XKEYBOARD keymap compiler (xkbcomp) reports: > > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 > > symbols > > >Ignoring extra symbols > >Errors from xkbcomp are not fatal to the X server > >The XKEYBOARD keymap compiler (xkbcomp) reports: > > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 > > symbols > > >Ignoring extra symbols > >Errors from xkbcomp are not fatal to the X server > >The XKEYBOARD keymap compiler (xkbcomp) reports: > > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 > > symbols > > >Ignoring extra symbols > >Errors from xkbcomp are not fatal to the X server > >xinit: connection to X server lost. > > > >waiting for X server to shut down ddxSigGiveUp: Closing log > > > > > >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. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On Thu, Jan 7, 2010 at 11:26 AM, Ryan Daly wrote: > On 01/07/2010 01:25 PM, Justin P. Mattock wrote: >>> 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. > > I read through the bug reports... No one has a fix yet, so I'm not sure > what I should do with regard to that. And if you don't think it's > causing X to quit, then it may not be worth going down that road anyway. xkbcomp is almost certainly not killing the server. If you run startx then switch back to the VT you started from, you'll see those errors are only generated during initialization (unless you plug in another keyboard later). If you run "startx `which xterm`" so that you're just running a terminal, does the server still exit? -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/07/10 11:26, Ryan Daly wrote: > On 01/07/2010 01:25 PM, Justin P. Mattock wrote: >>> 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. > > I read through the bug reports... No one has a fix yet, so I'm not sure > what I should do with regard to that. And if you don't think it's > causing X to quit, then it may not be worth going down that road anyway. > > All I can verify is that when X goes, I'm always typing something. I > can't be sure whether or not I hit either ALT keys when it goes, I just > know I'm typing. > > Would you like me to try anything with this mapping? > > well.. if your typing and your getting also some xkbcomp error with this then that might be the problem. (could also be with xf86-keyboard). hmm.. if your able to reproduce this by just typing I'm wondering if it's possible todo a bisect(but you would have to find what's causing this to happen first i.g. xf86-keyboard,X,xinit,etc then start from there). Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/07/2010 01:25 PM, Justin P. Mattock wrote: >> 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. I read through the bug reports... No one has a fix yet, so I'm not sure what I should do with regard to that. And if you don't think it's causing X to quit, then it may not be worth going down that road anyway. All I can verify is that when X goes, I'm always typing something. I can't be sure whether or not I hit either ALT keys when it goes, I just know I'm typing. Would you like me to try anything with this mapping? 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/10 08:45, Ryan Daly wrote: > On 01/06/2010 10:34 PM, Ryan Daly wrote: >> On 01/06/2010 10:26 PM, Justin P. Mattock wrote: >>> the module should work.. hopefully their the same arch's >>> >>> as for the next step: >>> try starting the server from a TTY instead of through gdm >>> (as stated by peter hutterer from the other post try this and then go >>> from there). >>> >>> keep in mind evdev might be fine, at this point it could be >>> anything.(so hopefully doing the above gives some useful info >>> to target the problem). >> >> Yep. A 'uname -m' reports i686 on both systems and a 'file' on >> evdev_drv.so reports both are identical (only I didn't strip mine). >> >> I will start the server from a tty and see what happens. The system in >> question is at work, so I won't be doing anything more on this until >> tomorrow. Thanks very much for the help you've given so far. I'll post >> an update when I have one. > > Bad news... I started X from a tty and still had it exit on me. The > only thing worth noting from the output is below: > > > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > >Ignoring extra symbols > Errors from xkbcomp are not fatal to the X server > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > >Ignoring extra symbols > Errors from xkbcomp are not fatal to the X server > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > >Ignoring extra symbols > Errors from xkbcomp are not fatal to the X server > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > >Ignoring extra symbols > Errors from xkbcomp are not fatal to the X server > xinit: connection to X server lost. > > waiting for X server to shut down ddxSigGiveUp: Closing log > > > 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. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 10:34 PM, Ryan Daly wrote: > On 01/06/2010 10:26 PM, Justin P. Mattock wrote: >> the module should work.. hopefully their the same arch's >> >> as for the next step: >> try starting the server from a TTY instead of through gdm >> (as stated by peter hutterer from the other post try this and then go >> from there). >> >> keep in mind evdev might be fine, at this point it could be >> anything.(so hopefully doing the above gives some useful info >> to target the problem). > > Yep. A 'uname -m' reports i686 on both systems and a 'file' on > evdev_drv.so reports both are identical (only I didn't strip mine). > > I will start the server from a tty and see what happens. The system in > question is at work, so I won't be doing anything more on this until > tomorrow. Thanks very much for the help you've given so far. I'll post > an update when I have one. Bad news... I started X from a tty and still had it exit on me. The only thing worth noting from the output is below: The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xinit: connection to X server lost. waiting for X server to shut down ddxSigGiveUp: Closing log I know it says these errors aren't fatal to the X server, but could they be causing me problems? 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 Thu, 2010-01-07 at 11:37 +0100, Michel Dänzer wrote: > On Thu, 2010-01-07 at 11:47 +1000, Peter Hutterer wrote: > > either your session is terminating for some reason or another or you might > > be getting an unresolved symbol error. that terminates the server as well. > > try starting the server from a TTY instead of through gdm, once it exits you > > can see if it complains about a symbol error. > > That would be SIGKILL though, or some other signal that can't be caught. Unresolved symbols don't raise a signal on Linux. ld.so just calls _exit(). - ajax signature.asc Description: This is a digitally signed message part ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On Thu, 2010-01-07 at 11:47 +1000, Peter Hutterer wrote: > On Wed, Jan 06, 2010 at 08:26:40PM -0500, Ryan Daly wrote: > > On 01/06/2010 08:04 PM, Peter Hutterer wrote: > > >> The backtrace is pretty consistent with the following few lines: > > >> > > >> Program received signal SIGTERM, Terminated. > > >> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > > >> (gdb) backtrace r full > > >> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > > >> No symbol table info available. > > >> #1 0x7f1466f61516 in ?? () from > > >> /usr/lib/xorg/modules/input//evdev_drv.so > > >> No symbol table info available. > > >> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > > >> ../../dix/devices.c:407 > > >> > > >> Are those lines pointing to a device or to the card possibly? > > >> > > >> I'm running the same version of Ubuntu on three different machines, and > > >> I'm only experiencing the Xorg restarts on one system. I'm at a loss... > > > > > > > > > uhm. SIGTERM is the termination signal. Something's shutting down your > > > server. > > > > Right, but it's nothing I'm doing. That's the problem. I'm not > > initiating an exit, nor am I hitting ctrl-backspace (I don't think > > that's enabled by default any longer anyway). > > > > I'm looking for suggestions as to WHAT may be causing the SIGTERM. > > either your session is terminating for some reason or another or you might > be getting an unresolved symbol error. that terminates the server as well. > try starting the server from a TTY instead of through gdm, once it exits you > can see if it complains about a symbol error. That would be SIGKILL though, or some other signal that can't be caught. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 10:26 PM, Justin P. Mattock wrote: > the module should work.. hopefully their the same arch's > > as for the next step: > try starting the server from a TTY instead of through gdm > (as stated by peter hutterer from the other post try this and then go > from there). > > keep in mind evdev might be fine, at this point it could be > anything.(so hopefully doing the above gives some useful info > to target the problem). Yep. A 'uname -m' reports i686 on both systems and a 'file' on evdev_drv.so reports both are identical (only I didn't strip mine). I will start the server from a tty and see what happens. The system in question is at work, so I won't be doing anything more on this until tomorrow. Thanks very much for the help you've given so far. I'll post an update when I have one. 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/06/10 19:17, Ryan Daly wrote: > On 01/06/2010 09:39 PM, Justin P. Mattock wrote: >> you need a newer version of xmacros >> (everything is at cgit.freedesktop.org) > > Got'em and installed in /usr/local. > >> hopefully ubuntu is up-to-date >> i.g. hopefully it doesn't take >> much to use the latest version. >> (you can also grab the tar ball >> there if it becomes too much, or try older >> versions of ubuntu's package); >> >> hard part right I see is pinpointing what exactly >> is exiting your server, so you don't have to >> do the trial and error approach. > > I got a clean compile after using the latest version of the macros. > > I compiled on a separate x86 system, but the same version of Ubuntu. > Can I take xf86-input-evdev/src/.libs/evdev_drv.so and simply copy that > to /usr/lib/xorg/modules/input/evdev_drv.so (the Ubuntu location) on the > troubled system and restart X? Should I continue to run w/ GDB attached > to obtain another backtrace? > > the module should work.. hopefully their the same arch's as for the next step: try starting the server from a TTY instead of through gdm (as stated by peter hutterer from the other post try this and then go from there). keep in mind evdev might be fine, at this point it could be anything.(so hopefully doing the above gives some useful info to target the problem). Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On Wed, Jan 06, 2010 at 09:25:43PM -0500, Ryan Daly wrote: > On 01/06/2010 08:47 PM, Peter Hutterer wrote: > >> Right, but it's nothing I'm doing. That's the problem. I'm not > >> initiating an exit, nor am I hitting ctrl-backspace (I don't think > >> that's enabled by default any longer anyway). > >> > >> I'm looking for suggestions as to WHAT may be causing the SIGTERM. > > > > either your session is terminating for some reason or another or you might > > be getting an unresolved symbol error. that terminates the server as well. > > try starting the server from a TTY instead of through gdm, once it exits you > > can see if it complains about a symbol error. > > I'll definitely try this...but wouldn't any symbol errors appear in the > gdb output that I captured? no. fwiw, I've had this happen to me just the other day and gdb didn't complain at all. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 09:39 PM, Justin P. Mattock wrote: > you need a newer version of xmacros > (everything is at cgit.freedesktop.org) Got'em and installed in /usr/local. > hopefully ubuntu is up-to-date > i.g. hopefully it doesn't take > much to use the latest version. > (you can also grab the tar ball > there if it becomes too much, or try older > versions of ubuntu's package); > > hard part right I see is pinpointing what exactly > is exiting your server, so you don't have to > do the trial and error approach. I got a clean compile after using the latest version of the macros. I compiled on a separate x86 system, but the same version of Ubuntu. Can I take xf86-input-evdev/src/.libs/evdev_drv.so and simply copy that to /usr/lib/xorg/modules/input/evdev_drv.so (the Ubuntu location) on the troubled system and restart X? Should I continue to run w/ GDB attached to obtain another backtrace? 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/06/10 18:21, Ryan Daly wrote: > On 01/06/2010 03:59 PM, Justin P. Mattock wrote: >> over here my xorg modules live in: >> /usr/lib/xorg/modules/* >> ubuntu might be the same(but can't remember). >> >> as for uninstalling, synaptic I think >> might let you uninstall a module >> individually, but you never know might >> want to uninstall a whole mess load of stuff. >> (dependencies) >> >> depending on what synaptic does if it wants to uninstall >> a mess load, I would not even bother, and just locate >> the evdev_drv.so/la modules rename them or move them to a >> safe location. then git clone >> git://anongit.freedesktop.org/xorg/driver/xf86-input-evdev >> (or just leave them their and write over them with a fresh copy, >> and when done use apt-get reinstall on it to copy that version again). >> >> compile it, remember you might need to specify the location of >> the modules with a switch i.g. >> ./configure --someswitch=/specifying/the/location/of/input/modules >> (that's if ubuntu has them in another location other than default); >> >> then see if it fixes your issue. >> now keep in mind it could be evdev, it could >> even be libpthread or libxrandr.. tough to say. > > I grabbed the source and some dependencies, but I'm getting an error on > the version of the macros installed. > > d...@riddler<31#> sh autogen.sh > autoreconf: Entering directory `.' > autoreconf: configure.ac: not using Gettext > autoreconf: running: aclocal > configure.ac:36: error: must install xorg-macros 1.3 or later before you need a newer version of xmacros (everything is at cgit.freedesktop.org) > running autoconf/autogen > configure.ac:36: the top level > autom4te: /usr/bin/m4 failed with exit status: 1 > aclocal: autom4te failed with exit status: 1 > autoreconf: aclocal failed with exit status: 1 > > I'm not sure how to overcome that one... Ubuntu provides a package that > contains xorg-macros.m4, but I'm gathering that the version I have is > too low. I commented out the line that checks for the version to get > passed it, but I'm not certain if that was OK. I'm getting another > error on the compilation: > > d...@riddler<36#> make > make all-recursive > make[1]: Entering directory `/home/daly/xf86-input-evdev' > Making all in src > make[2]: Entering directory `/home/daly/xf86-input-evdev/src' > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I.. -I../include/ -I/usr/include/xorg -I/usr/include/pixman-1 -g > -O2 -MT evdev.lo -MD -MP -MF .deps/evdev.Tpo -c -o evdev.lo evdev.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include/ > -I/usr/include/xorg -I/usr/include/pixman-1 -g -O2 -MT evdev.lo -MD -MP > -MF .deps/evdev.Tpo -c evdev.c -fPIC -DPIC -o .libs/evdev.o > evdev.c: In function `EvdevKbdCtrl': > evdev.c:1083: warning: ignoring return value of `write', declared with > attribute warn_unused_result > evdev.c: At top level: > evdev.c:2097: error: `PACKAGE_VERSION_MAJOR' undeclared here (not in a > function) > evdev.c:2097: error: `PACKAGE_VERSION_MINOR' undeclared here (not in a > function) > evdev.c:2097: error: `PACKAGE_VERSION_PATCHLEVEL' undeclared here (not > in a function) > make[2]: *** [evdev.lo] Error 1 > make[2]: Leaving directory `/home/daly/xf86-input-evdev/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/daly/xf86-input-evdev' > make: *** [all] Error 2 > > Is that error caused by the macros being too old, or is that something > completely unrelated? > > hopefully ubuntu is up-to-date i.g. hopefully it doesn't take much to use the latest version. (you can also grab the tar ball there if it becomes too much, or try older versions of ubuntu's package); hard part right I see is pinpointing what exactly is exiting your server, so you don't have to do the trial and error approach. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 08:47 PM, Peter Hutterer wrote: >> Right, but it's nothing I'm doing. That's the problem. I'm not >> initiating an exit, nor am I hitting ctrl-backspace (I don't think >> that's enabled by default any longer anyway). >> >> I'm looking for suggestions as to WHAT may be causing the SIGTERM. > > either your session is terminating for some reason or another or you might > be getting an unresolved symbol error. that terminates the server as well. > try starting the server from a TTY instead of through gdm, once it exits you > can see if it complains about a symbol error. I'll definitely try this...but wouldn't any symbol errors appear in the gdb output that I captured? 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/06/2010 03:59 PM, Justin P. Mattock wrote: > over here my xorg modules live in: > /usr/lib/xorg/modules/* > ubuntu might be the same(but can't remember). > > as for uninstalling, synaptic I think > might let you uninstall a module > individually, but you never know might > want to uninstall a whole mess load of stuff. > (dependencies) > > depending on what synaptic does if it wants to uninstall > a mess load, I would not even bother, and just locate > the evdev_drv.so/la modules rename them or move them to a > safe location. then git clone > git://anongit.freedesktop.org/xorg/driver/xf86-input-evdev > (or just leave them their and write over them with a fresh copy, > and when done use apt-get reinstall on it to copy that version again). > > compile it, remember you might need to specify the location of > the modules with a switch i.g. > ./configure --someswitch=/specifying/the/location/of/input/modules > (that's if ubuntu has them in another location other than default); > > then see if it fixes your issue. > now keep in mind it could be evdev, it could > even be libpthread or libxrandr.. tough to say. I grabbed the source and some dependencies, but I'm getting an error on the version of the macros installed. d...@riddler <31#> sh autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal configure.ac:36: error: must install xorg-macros 1.3 or later before running autoconf/autogen configure.ac:36: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 I'm not sure how to overcome that one... Ubuntu provides a package that contains xorg-macros.m4, but I'm gathering that the version I have is too low. I commented out the line that checks for the version to get passed it, but I'm not certain if that was OK. I'm getting another error on the compilation: d...@riddler <36#> make make all-recursive make[1]: Entering directory `/home/daly/xf86-input-evdev' Making all in src make[2]: Entering directory `/home/daly/xf86-input-evdev/src' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include/ -I/usr/include/xorg -I/usr/include/pixman-1 -g -O2 -MT evdev.lo -MD -MP -MF .deps/evdev.Tpo -c -o evdev.lo evdev.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include/ -I/usr/include/xorg -I/usr/include/pixman-1 -g -O2 -MT evdev.lo -MD -MP -MF .deps/evdev.Tpo -c evdev.c -fPIC -DPIC -o .libs/evdev.o evdev.c: In function `EvdevKbdCtrl': evdev.c:1083: warning: ignoring return value of `write', declared with attribute warn_unused_result evdev.c: At top level: evdev.c:2097: error: `PACKAGE_VERSION_MAJOR' undeclared here (not in a function) evdev.c:2097: error: `PACKAGE_VERSION_MINOR' undeclared here (not in a function) evdev.c:2097: error: `PACKAGE_VERSION_PATCHLEVEL' undeclared here (not in a function) make[2]: *** [evdev.lo] Error 1 make[2]: Leaving directory `/home/daly/xf86-input-evdev/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/daly/xf86-input-evdev' make: *** [all] Error 2 Is that error caused by the macros being too old, or is that something completely unrelated? 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 Wed, Jan 06, 2010 at 08:26:40PM -0500, Ryan Daly wrote: > On 01/06/2010 08:04 PM, Peter Hutterer wrote: > >> The backtrace is pretty consistent with the following few lines: > >> > >> Program received signal SIGTERM, Terminated. > >> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > >> (gdb) backtrace r full > >> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > >> No symbol table info available. > >> #1 0x7f1466f61516 in ?? () from > >> /usr/lib/xorg/modules/input//evdev_drv.so > >> No symbol table info available. > >> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > >> ../../dix/devices.c:407 > >> > >> Are those lines pointing to a device or to the card possibly? > >> > >> I'm running the same version of Ubuntu on three different machines, and > >> I'm only experiencing the Xorg restarts on one system. I'm at a loss... > > > > > > uhm. SIGTERM is the termination signal. Something's shutting down your > > server. > > Right, but it's nothing I'm doing. That's the problem. I'm not > initiating an exit, nor am I hitting ctrl-backspace (I don't think > that's enabled by default any longer anyway). > > I'm looking for suggestions as to WHAT may be causing the SIGTERM. either your session is terminating for some reason or another or you might be getting an unresolved symbol error. that terminates the server as well. try starting the server from a TTY instead of through gdm, once it exits you can see if it complains about a symbol error. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 08:04 PM, Peter Hutterer wrote: >> The backtrace is pretty consistent with the following few lines: >> >> Program received signal SIGTERM, Terminated. >> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 >> (gdb) backtrace r full >> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 >> No symbol table info available. >> #1 0x7f1466f61516 in ?? () from >> /usr/lib/xorg/modules/input//evdev_drv.so >> No symbol table info available. >> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at >> ../../dix/devices.c:407 >> >> Are those lines pointing to a device or to the card possibly? >> >> I'm running the same version of Ubuntu on three different machines, and >> I'm only experiencing the Xorg restarts on one system. I'm at a loss... > > > uhm. SIGTERM is the termination signal. Something's shutting down your > server. Right, but it's nothing I'm doing. That's the problem. I'm not initiating an exit, nor am I hitting ctrl-backspace (I don't think that's enabled by default any longer anyway). I'm looking for suggestions as to WHAT may be causing the SIGTERM. -- 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 Wed, Jan 06, 2010 at 11:56:28AM -0500, Ryan Daly wrote: > On 01/06/2010 10:53 AM, Jeremy Huddleston wrote: > > On Jan 6, 2010, at 10:50, Ryan Daly wrote: > > > >>> not sure whats going on, but by > >>> looking at the log I see some userspace tools > >>> erroring out(which should not keep the screen from > >>> going forward), but I also see something about > >>> fglrx not found.. could either mean that you > >>> haven't the xorg module, as well as the kernel module, > >>> or the fglrx module is crapping out with the > >>> xserver version(had this a while ago with fglrx, > >>> ended up switching to radeon); > >>> > >>> hope this helps. > >>> > >>> Justin P. Mattock > >>> > >> Justin - thanks for your reply. > >> > >> Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all > >> play together, though. > > > > fglrx is the closed-source ATI driver > > > > OK. That rules that out then... > > The backtrace is pretty consistent with the following few lines: > > Program received signal SIGTERM, Terminated. > 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > (gdb) backtrace r full > #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > No symbol table info available. > #1 0x7f1466f61516 in ?? () from > /usr/lib/xorg/modules/input//evdev_drv.so > No symbol table info available. > #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > ../../dix/devices.c:407 > > Are those lines pointing to a device or to the card possibly? > > I'm running the same version of Ubuntu on three different machines, and > I'm only experiencing the Xorg restarts on one system. I'm at a loss... uhm. SIGTERM is the termination signal. Something's shutting down your server. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/10 11:54, Ryan Daly wrote: > On 01/06/2010 02:28 PM, Justin P. Mattock wrote: >> >> alright.. so at least you can switch >> modules i.g. from nvidia to vesa and such. >> From what it seems your hitting something >> maybe with evdev, or mouse/kbd(but could be wrong). >> >> over here I've noticed something like that >> with using fluxbox and the latest xserver from git. >> every so often if I right click >> the xserver will exit out instantly. >> >> hmm.. from your log I see something >> with evdev, maybe you should upgrade >> the evdev module(from git) to see if this problem >> has been fixed for you. > > I'm running the stock Xorg from Ubuntu 9.10. They're using version > 2:1.6.4-2ubuntu4, but /usr/lib/xorg/modules/input/evdev_drv.so lives in > another package (xserver-xorg-input-evdev) which is version > 1:2.2.5-1ubuntu6. > > Would I be able to insert an updated module without changing anything else? > -- > > over here my xorg modules live in: /usr/lib/xorg/modules/* ubuntu might be the same(but can't remember). as for uninstalling, synaptic I think might let you uninstall a module individually, but you never know might want to uninstall a whole mess load of stuff. (dependencies) depending on what synaptic does if it wants to uninstall a mess load, I would not even bother, and just locate the evdev_drv.so/la modules rename them or move them to a safe location. then git clone git://anongit.freedesktop.org/xorg/driver/xf86-input-evdev (or just leave them their and write over them with a fresh copy, and when done use apt-get reinstall on it to copy that version again). compile it, remember you might need to specify the location of the modules with a switch i.g. ./configure --someswitch=/specifying/the/location/of/input/modules (that's if ubuntu has them in another location other than default); then see if it fixes your issue. now keep in mind it could be evdev, it could even be libpthread or libxrandr.. tough to say. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg Crashes ... Ryan Daly
On 01/06/2010 02:49 PM, Tim McConnell wrote: > > Thanks, > Tim McConnell > mailto:timothy.mcconn...@comcast.net>> > > > > On Wed, 2010-01-06 at 11:27 -0800, xorg-requ...@lists.freedesktop.org wrote: > > What is the model of the Nvidia card? Also what do you have installed as > far as software versions (xorg, that sort of thing)? > I know in Fedora there are different versions of the Nvidia drivers that > you have to get from a separate repo ( I think Debian calls them non > free contribs, wouldn't know about any version of Unbuntu), to me it > sounds like you have the wrong drivers installed. > The model of the card is below: : linux13 63#; lspci | fgrep -i nvidi 02:00.0 VGA compatible controller: nVidia Corporation G84 [Quadro FX 570] (rev a1) I have the most recent Xorg packages provided by Ubuntu. The Xorg server is below: : linux13 72#; apt-cache show xserver-xorg-core Package: xserver-xorg-core Priority: optional Section: x11 Installed-Size: 4264 Maintainer: Ubuntu X-SWAT Original-Maintainer: Debian X Strike Force Architecture: i386 Source: xorg-server Version: 2:1.6.4-2ubuntu4 [...] I also have the most recent proprietary nVidia driver provided by Ubuntu: ii nvidia-185-kernel-source 185.18.36-0ubuntu9 NVIDIA binary kernel module source -- 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 ... Ryan Daly
Thanks, Tim McConnell On Wed, 2010-01-06 at 11:27 -0800, xorg-requ...@lists.freedesktop.org wrote: What is the model of the Nvidia card? Also what do you have installed as far as software versions (xorg, that sort of thing)? I know in Fedora there are different versions of the Nvidia drivers that you have to get from a separate repo ( I think Debian calls them non free contribs, wouldn't know about any version of Unbuntu), to me it sounds like you have the wrong drivers installed. > > Message: 3 > Date: Wed, 06 Jan 2010 10:31:14 -0800 > From: "Justin P. Mattock" > Subject: Re: Xorg crashes... > To: Ryan Daly > Cc: xorg@lists.freedesktop.org > Message-ID: <4b44d6f2.2040...@gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 01/06/10 08:56, Ryan Daly wrote: > > On 01/06/2010 10:53 AM, Jeremy Huddleston wrote: > >> On Jan 6, 2010, at 10:50, Ryan Daly wrote: > >> > >>>> not sure whats going on, but by > >>>> looking at the log I see some userspace tools > >>>> erroring out(which should not keep the screen from > >>>> going forward), but I also see something about > >>>> fglrx not found.. could either mean that you > >>>> haven't the xorg module, as well as the kernel module, > >>>> or the fglrx module is crapping out with the > >>>> xserver version(had this a while ago with fglrx, > >>>> ended up switching to radeon); > >>>> > >>>> hope this helps. > >>>> > >>>> Justin P. Mattock > >>>> > >>> Justin - thanks for your reply. > >>> > >>> Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all > >>> play together, though. > >> > >> fglrx is the closed-source ATI driver > >> > > > > OK. That rules that out then... > > > > The backtrace is pretty consistent with the following few lines: > > > > Program received signal SIGTERM, Terminated. > > 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > > (gdb) backtrace r full > > #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > > No symbol table info available. > > #1 0x7f1466f61516 in ?? () from > > /usr/lib/xorg/modules/input//evdev_drv.so > > No symbol table info available. > > #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > > ../../dix/devices.c:407 > > > > Are those lines pointing to a device or to the card possibly? > > > > I'm running the same version of Ubuntu on three different machines, and > > I'm only experiencing the Xorg restarts on one system. I'm at a loss... > > > > yeah.. fglrx is specific to > ati chipsets(but could be wrong). > > In your case If you have nvidia > you probably should be using > nv, nouveau, or the proprietary module. > > if you can does changing your xorg.conf > to use vesa/vga have the xserver start properly? > > > Justin P. Mattock > > > > -- > > Message: 4 > Date: Wed, 06 Jan 2010 13:47:14 -0500 > From: Ryan Daly > Subject: Re: Xorg crashes... > To: "Justin P. Mattock" > Cc: xorg@lists.freedesktop.org > Message-ID: <4b44dab2.3090...@ctc.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 01/06/2010 01:31 PM, Justin P. Mattock wrote: > >>> fglrx is the closed-source ATI driver > >>> > >> > >> OK. That rules that out then... > >> > >> The backtrace is pretty consistent with the following few lines: > >> > >> Program received signal SIGTERM, Terminated. > >> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > >> (gdb) backtrace r full > >> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > >> No symbol table info available. > >> #1 0x7f1466f61516 in ?? () from > >> /usr/lib/xorg/modules/input//evdev_drv.so > >> No symbol table info available. > >> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > >> ../../dix/devices.c:407 > >> > >> Are those lines pointing to a device or to the card possibly? > >> > >> I'm running the same version of Ubuntu on three different machines, and > >> I'm only experiencing the Xorg restarts on one system. I'm at a loss... > >> > > > > yeah.. fglrx is specific to > > ati chipsets(but could be wrong). > > > > In your case I
Re: Xorg crashes...
On 01/06/2010 02:28 PM, Justin P. Mattock wrote: > > alright.. so at least you can switch > modules i.g. from nvidia to vesa and such. > From what it seems your hitting something > maybe with evdev, or mouse/kbd(but could be wrong). > > over here I've noticed something like that > with using fluxbox and the latest xserver from git. > every so often if I right click > the xserver will exit out instantly. > > hmm.. from your log I see something > with evdev, maybe you should upgrade > the evdev module(from git) to see if this problem > has been fixed for you. I'm running the stock Xorg from Ubuntu 9.10. They're using version 2:1.6.4-2ubuntu4, but /usr/lib/xorg/modules/input/evdev_drv.so lives in another package (xserver-xorg-input-evdev) which is version 1:2.2.5-1ubuntu6. Would I be able to insert an updated module without changing anything else? -- 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/06/10 10:47, Ryan Daly wrote: > On 01/06/2010 01:31 PM, Justin P. Mattock wrote: fglrx is the closed-source ATI driver >>> >>> OK. That rules that out then... >>> >>> The backtrace is pretty consistent with the following few lines: >>> >>> Program received signal SIGTERM, Terminated. >>> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 >>> (gdb) backtrace r full >>> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 >>> No symbol table info available. >>> #1 0x7f1466f61516 in ?? () from >>> /usr/lib/xorg/modules/input//evdev_drv.so >>> No symbol table info available. >>> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at >>> ../../dix/devices.c:407 >>> >>> Are those lines pointing to a device or to the card possibly? >>> >>> I'm running the same version of Ubuntu on three different machines, and >>> I'm only experiencing the Xorg restarts on one system. I'm at a loss... >>> >> >> yeah.. fglrx is specific to >> ati chipsets(but could be wrong). >> >> In your case If you have nvidia >> you probably should be using >> nv, nouveau, or the proprietary module. >> >> if you can does changing your xorg.conf >> to use vesa/vga have the xserver start properly? > > Well, my xorg.conf is set up to use the nVidia proprietary module: > > Section "Device" > Identifier "Device0" > Driver "nvidia" > VendorName "NVIDIA Corporation" > BoardName "Quadro FX 570" > EndSection > > The X server will start properly and it allows me to log in. Sometimes > my session will last hours, other times it will restart 3 or 4 times in > 15 minutes. I have left it logged in without it restarting on its own, > so it definitely appears to be triggered by something. I can say this, > I'm typing 100% of the time it ups and restarts on me. > > I have left the proprietary driver out and still received a restart, too. > > alright.. so at least you can switch modules i.g. from nvidia to vesa and such. From what it seems your hitting something maybe with evdev, or mouse/kbd(but could be wrong). over here I've noticed something like that with using fluxbox and the latest xserver from git. every so often if I right click the xserver will exit out instantly. hmm.. from your log I see something with evdev, maybe you should upgrade the evdev module(from git) to see if this problem has been fixed for you. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 01:31 PM, Justin P. Mattock wrote: >>> fglrx is the closed-source ATI driver >>> >> >> OK. That rules that out then... >> >> The backtrace is pretty consistent with the following few lines: >> >> Program received signal SIGTERM, Terminated. >> 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 >> (gdb) backtrace r full >> #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 >> No symbol table info available. >> #1 0x7f1466f61516 in ?? () from >> /usr/lib/xorg/modules/input//evdev_drv.so >> No symbol table info available. >> #2 0x00447723 in DisableDevice (dev=0x18a33a0) at >> ../../dix/devices.c:407 >> >> Are those lines pointing to a device or to the card possibly? >> >> I'm running the same version of Ubuntu on three different machines, and >> I'm only experiencing the Xorg restarts on one system. I'm at a loss... >> > > yeah.. fglrx is specific to > ati chipsets(but could be wrong). > > In your case If you have nvidia > you probably should be using > nv, nouveau, or the proprietary module. > > if you can does changing your xorg.conf > to use vesa/vga have the xserver start properly? Well, my xorg.conf is set up to use the nVidia proprietary module: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "Quadro FX 570" EndSection The X server will start properly and it allows me to log in. Sometimes my session will last hours, other times it will restart 3 or 4 times in 15 minutes. I have left it logged in without it restarting on its own, so it definitely appears to be triggered by something. I can say this, I'm typing 100% of the time it ups and restarts on me. I have left the proprietary driver out and still received a restart, too. 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/06/10 08:56, Ryan Daly wrote: > On 01/06/2010 10:53 AM, Jeremy Huddleston wrote: >> On Jan 6, 2010, at 10:50, Ryan Daly wrote: >> not sure whats going on, but by looking at the log I see some userspace tools erroring out(which should not keep the screen from going forward), but I also see something about fglrx not found.. could either mean that you haven't the xorg module, as well as the kernel module, or the fglrx module is crapping out with the xserver version(had this a while ago with fglrx, ended up switching to radeon); hope this helps. Justin P. Mattock >>> Justin - thanks for your reply. >>> >>> Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all >>> play together, though. >> >> fglrx is the closed-source ATI driver >> > > OK. That rules that out then... > > The backtrace is pretty consistent with the following few lines: > > Program received signal SIGTERM, Terminated. > 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > (gdb) backtrace r full > #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 > No symbol table info available. > #1 0x7f1466f61516 in ?? () from > /usr/lib/xorg/modules/input//evdev_drv.so > No symbol table info available. > #2 0x00447723 in DisableDevice (dev=0x18a33a0) at > ../../dix/devices.c:407 > > Are those lines pointing to a device or to the card possibly? > > I'm running the same version of Ubuntu on three different machines, and > I'm only experiencing the Xorg restarts on one system. I'm at a loss... > yeah.. fglrx is specific to ati chipsets(but could be wrong). In your case If you have nvidia you probably should be using nv, nouveau, or the proprietary module. if you can does changing your xorg.conf to use vesa/vga have the xserver start properly? Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/06/2010 10:53 AM, Jeremy Huddleston wrote: > On Jan 6, 2010, at 10:50, Ryan Daly wrote: > >>> not sure whats going on, but by >>> looking at the log I see some userspace tools >>> erroring out(which should not keep the screen from >>> going forward), but I also see something about >>> fglrx not found.. could either mean that you >>> haven't the xorg module, as well as the kernel module, >>> or the fglrx module is crapping out with the >>> xserver version(had this a while ago with fglrx, >>> ended up switching to radeon); >>> >>> hope this helps. >>> >>> Justin P. Mattock >>> >> Justin - thanks for your reply. >> >> Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all >> play together, though. > > fglrx is the closed-source ATI driver > OK. That rules that out then... The backtrace is pretty consistent with the following few lines: Program received signal SIGTERM, Terminated. 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 (gdb) backtrace r full #0 0x7f146bab8110 in __close_nocancel () from /lib/libpthread.so.0 No symbol table info available. #1 0x7f1466f61516 in ?? () from /usr/lib/xorg/modules/input//evdev_drv.so No symbol table info available. #2 0x00447723 in DisableDevice (dev=0x18a33a0) at ../../dix/devices.c:407 Are those lines pointing to a device or to the card possibly? I'm running the same version of Ubuntu on three different machines, and I'm only experiencing the Xorg restarts on one system. I'm at a loss... 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 Jan 6, 2010, at 10:50, Ryan Daly wrote: >> not sure whats going on, but by >> looking at the log I see some userspace tools >> erroring out(which should not keep the screen from >> going forward), but I also see something about >> fglrx not found.. could either mean that you >> haven't the xorg module, as well as the kernel module, >> or the fglrx module is crapping out with the >> xserver version(had this a while ago with fglrx, >> ended up switching to radeon); >> >> hope this helps. >> >> Justin P. Mattock >> > > Justin - thanks for your reply. > > Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all > play together, though. fglrx is the closed-source ATI driver smime.p7s Description: S/MIME cryptographic signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
> not sure whats going on, but by > looking at the log I see some userspace tools > erroring out(which should not keep the screen from > going forward), but I also see something about > fglrx not found.. could either mean that you > haven't the xorg module, as well as the kernel module, > or the fglrx module is crapping out with the > xserver version(had this a while ago with fglrx, > ended up switching to radeon); > > hope this helps. > > Justin P. Mattock > Justin - thanks for your reply. Is fglrx ATI specific? I have a nVidia card. I'm not sure how they all play together, 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/05/10 21:34, Ryan Daly wrote: > Would anyone be able to take a look at a bug report I filed with Ubuntu? > > My Xorg server keeps terminating on me and sends me back to the login > screen. I have obtained a number of backtraces, all of which are logged > in the bug report. The link to the bug report is below. > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/499484 > > I appreciate anyone who can shed some light on this for me. Thanks. > -- > > > 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 > not sure whats going on, but by looking at the log I see some userspace tools erroring out(which should not keep the screen from going forward), but I also see something about fglrx not found.. could either mean that you haven't the xorg module, as well as the kernel module, or the fglrx module is crapping out with the xserver version(had this a while ago with fglrx, ended up switching to radeon); hope this helps. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Xorg crashes...
Would anyone be able to take a look at a bug report I filed with Ubuntu? My Xorg server keeps terminating on me and sends me back to the login screen. I have obtained a number of backtraces, all of which are logged in the bug report. The link to the bug report is below. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/499484 I appreciate anyone who can shed some light on this for me. Thanks. -- 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
