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 s
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'?
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.
>>
>
> Inde
New GL proto with event support.
Gaetan Nadon (7):
.gitignore: use common defaults with custom section # 24239
configure.ac: AM_MAINTAINER_MODE missing #24238
configure.ac: deploy the new XORG_DEFAULT_OPTIONS #24242
Makefile.am: INSTALL file is missing or incorrect #24206
New DRI2 proto release with the new driver type and swap etc. events.
Aaron Plattner (1):
Add a DRI2DriverVDPAU driver type.
Gaetan Nadon (7):
.gitignore: use common defaults with custom section # 24239
configure.ac: AM_MAINTAINER_MODE missing #24238
configure.ac: deploy t
Hello
tail -f /var/log/Xorg.0.log -> attached tail.log0
tail -f /var/log/Xorg.1.log -> file dos not exist (probably because I've erased
2 times some log)
tail -f /var/log/Xorg.0.log.old -> attached tail.log0.old
But taking a look at 'dbus' and 'hal', (I began to anderstand : HAL Hardware
Abstr
>
> 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 o
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
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
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
> serv
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
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
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 ea
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_
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 al
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 loo
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
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 L
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/m
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.
>
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
-Ursprüngliche Nachricht-
Von: "Morgan M.C.M-L"
Gesendet: 08.01.10 02:02:01
An: cour...@web.de
CC: xorg@lists.freedesktop.org
Betreff: Re: some help please X freeze laptop
Thank you Felix for helping me. I'm a newbee on NetBSD, so :
1- uname -a -> 5.0.1-Release, and I've made a netinsta
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
23 matches
Mail list logo
