Re: sorry state of Xserver in 5.0
On Mon, 2002-10-07 at 11:13, Andrew Gallatin wrote: Every so often, my X server locks up. It seems to be in a tight loop, 95% user time, and making only these ktrace'able calls: 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.39 CALL sigreturn(0xbd9e7b0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.15 CALL sigreturn(0xbd9e6e0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 Anybody have a workaround for this? The whole system (2.53 Ghz P4) was compiled from sources late last week... Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Basically what this ktrace output means, from my reading, is that the server is stuck processing some client request and never gets back to it main scheduling loop / goes idle and turns off the alarm. Finding where the server is sitting would be valuable. If you have a hardware cursor and smooth mouse on (it's default) you'll still be able to move the mouse because the mouse response is done in a signal handler, so a busy server doesn't make your mouse stop working. Still wishing I could get a working gdb on an X. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Maxim Sobolev wrote: Maxim Sobolev wrote: Maxim Sobolev wrote: Andrew Gallatin wrote: Maxim Sobolev writes: Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Agreed. I could add that after recent kernel updating I'm also often observing XFree86 dying with SIGFPU. I guess that it may have something to do with recent context saving changes. Note that the recent sys/i386/i386/machdep.c (1.540 and 1.541) should be backed out if you're running any FP apps (like, say, X). It somehow messes up the fp context and causes a gpf. Happens to me when I start gnome2. 1.539 more or less works, albeit with the problems I'm compaining about above. Backing out 1.540 and 1.541 didn't solve the problem with SIGFPE for me, so that the problem is probably elsewhere. :( The same situation is after backing out 1.539. Downgrading the whole kernel to the state as of 2-weeks ago (cvs up -D 2 weeks ago sys) solved the problem with SIGFPE. Tomorrow I'll try to narrow the gap between working and non-working. SIGFPE crashes still happed even on 2-weeks old kernel, but they are much less frequent. I'll try to go back in time to 4-weeks old kernel to see if it helps. -Maxim Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Wed, 09 Oct 2002 14:27:45 +0300
Maxim Sobolev [EMAIL PROTECTED] wrote:
SIGFPE crashes still happed even on 2-weeks old kernel, but they are
much less frequent. I'll try to go back in time to 4-weeks old kernel
to see if it helps.
As a data point... I still get signal 6, even without type1 activated...
Mittwoch, 09. Oktober 2002, 16:28:08
{0} FreeBSD 5.0-CURRENT [Magelan:~]
(1) netchild@ttyp0 % grep type1 /var/log/XFree86.0.log
Mittwoch, 09. Oktober 2002, 16:29:33
{1} FreeBSD 5.0-CURRENT [Magelan:~]
(2) netchild@ttyp0 % grep type1 /etc/X11/XF86Config-4
# Load type1
Bye,
Alexander.
--
I believe the technical term is Oops!
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
÷ Mon, 07.10.2002, × 22:13, Andrew Gallatin ÎÁÐÉÓÁÌ: Every so often, my X server locks up. It seems to be in a tight loop, 95% user time, and making only these ktrace'able calls: 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.39 CALL sigreturn(0xbd9e7b0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.15 CALL sigreturn(0xbd9e6e0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 Anybody have a workaround for this? The whole system (2.53 Ghz P4) was compiled from sources late last week... Me too :( Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. For me it happens an about 90% cases when I have move frame border in evolution and in some other cases :( Xserver starts eat all CPU and, sometimes dies with 6 signal. any ideas ? I have tried to build fresh Xserver from ports - but it don't buildable. Sigh. Drew -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Maxim Sobolev writes: Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Agreed. I could add that after recent kernel updating I'm also often observing XFree86 dying with SIGFPU. I guess that it may have something to do with recent context saving changes. Note that the recent sys/i386/i386/machdep.c (1.540 and 1.541) should be backed out if you're running any FP apps (like, say, X). It somehow messes up the fp context and causes a gpf. Happens to me when I start gnome2. 1.539 more or less works, albeit with the problems I'm compaining about above. Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Tue, 8 Oct 2002 09:04:27 -0400 (EDT) Andrew Gallatin [EMAIL PROTECTED] wrote: Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. I got this by only upgrading the kernel. I'm going to downgrade sys/i386/i386/machdep.c to 1.539 now and have a look how the system behaves. Bye, Alexander. -- Intel: where Quality is job number 0.9998782345! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Tue, 8 Oct 2002 15:27:27 +0200 Alexander Leidinger [EMAIL PROTECTED] wrote: I'm going to downgrade sys/i386/i386/machdep.c to 1.539 now and have a look how the system behaves. Doesn't work, I still get signal 6. Bye, Alexander. -- Yes, I've heard of decaf. What's your point? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Alexander Leidinger writes: On Tue, 8 Oct 2002 15:27:27 +0200 Alexander Leidinger [EMAIL PROTECTED] wrote: I'm going to downgrade sys/i386/i386/machdep.c to 1.539 now and have a look how the system behaves. Doesn't work, I still get signal 6. That won't fix signal 6. That will just fix the kernel panic. To fix signal 6, I think you need to rebuild your X server. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Tue, 8 Oct 2002 10:56:54 -0400 (EDT) Andrew Gallatin [EMAIL PROTECTED] wrote: I'm going to downgrade sys/i386/i386/machdep.c to 1.539 now and have a look how the system behaves. Doesn't work, I still get signal 6. That won't fix signal 6. That will just fix the kernel panic. I don't see a kernel panic with any rev of machdep.c. To fix signal 6, I think you need to rebuild your X server. Do you think I have to rebuild or do you know I have to rebuild? Bye, Alexander. -- 0 and 1. Now what could be so hard about that? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Tue, 8 Oct 2002, Alexander Leidinger wrote: To fix signal 6, I think you need to rebuild your X server. Do you think I have to rebuild or do you know I have to rebuild? I've rebuilt several times. I'm guessing NO, since I still have the problems periodically. -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Alexander Leidinger writes: On Tue, 8 Oct 2002 10:56:54 -0400 (EDT) Andrew Gallatin [EMAIL PROTECTED] wrote: I'm going to downgrade sys/i386/i386/machdep.c to 1.539 now and have a look how the system behaves. Doesn't work, I still get signal 6. That won't fix signal 6. That will just fix the kernel panic. I don't see a kernel panic with any rev of machdep.c. You're lucky. To fix signal 6, I think you need to rebuild your X server. Do you think I have to rebuild or do you know I have to rebuild? Nevermind. 6 is abort, I thought it was FPE. Check your var/log/X*log and see if you see something about beziers the next time it crashes. One hacky workaround is to not load the Type1 module (just comment it out in your /etc/X11/XF86Config) # This loads the Type1 and FreeType font modules #Loadtype1 Loadfreetype A longer term fix would be to fix the kernel.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Andrew Gallatin wrote: Maxim Sobolev writes: Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Agreed. I could add that after recent kernel updating I'm also often observing XFree86 dying with SIGFPU. I guess that it may have something to do with recent context saving changes. Note that the recent sys/i386/i386/machdep.c (1.540 and 1.541) should be backed out if you're running any FP apps (like, say, X). It somehow messes up the fp context and causes a gpf. Happens to me when I start gnome2. 1.539 more or less works, albeit with the problems I'm compaining about above. Backing out 1.540 and 1.541 didn't solve the problem with SIGFPE for me, so that the problem is probably elsewhere. :( -Maxim Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Maxim Sobolev wrote: Andrew Gallatin wrote: Maxim Sobolev writes: Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Agreed. I could add that after recent kernel updating I'm also often observing XFree86 dying with SIGFPU. I guess that it may have something to do with recent context saving changes. Note that the recent sys/i386/i386/machdep.c (1.540 and 1.541) should be backed out if you're running any FP apps (like, say, X). It somehow messes up the fp context and causes a gpf. Happens to me when I start gnome2. 1.539 more or less works, albeit with the problems I'm compaining about above. Backing out 1.540 and 1.541 didn't solve the problem with SIGFPE for me, so that the problem is probably elsewhere. :( The same situation is after backing out 1.539. -Maxim Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Maxim Sobolev wrote: Maxim Sobolev wrote: Andrew Gallatin wrote: Maxim Sobolev writes: Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Agreed. I could add that after recent kernel updating I'm also often observing XFree86 dying with SIGFPU. I guess that it may have something to do with recent context saving changes. Note that the recent sys/i386/i386/machdep.c (1.540 and 1.541) should be backed out if you're running any FP apps (like, say, X). It somehow messes up the fp context and causes a gpf. Happens to me when I start gnome2. 1.539 more or less works, albeit with the problems I'm compaining about above. Backing out 1.540 and 1.541 didn't solve the problem with SIGFPE for me, so that the problem is probably elsewhere. :( The same situation is after backing out 1.539. Downgrading the whole kernel to the state as of 2-weeks ago (cvs up -D 2 weeks ago sys) solved the problem with SIGFPE. Tomorrow I'll try to narrow the gap between working and non-working. -Maxim Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
On Tue, 8 Oct 2002, Andrew Gallatin wrote: ... Question: Did the Bezier too big stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. Definitely after having upgraded the kernel/libc_r combo. Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sorry state of Xserver in 5.0
Every so often, my X server locks up. It seems to be in a tight loop, 95% user time, and making only these ktrace'able calls: 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.39 CALL sigreturn(0xbd9e7b0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.15 CALL sigreturn(0xbd9e6e0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 Anybody have a workaround for this? The whole system (2.53 Ghz P4) was compiled from sources late last week... Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
This sounds very similar to a problem I am seeing that does not result in a fatal lockup, but rather several minutes of complete unresponsiveness. It only seems to happen when Konqueror tries to autocomplete from the location bar. On Mon, 7 Oct 2002, Andrew Gallatin wrote: Every so often, my X server locks up. It seems to be in a tight loop, 95% user time, and making only these ktrace'able calls: 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.39 CALL sigreturn(0xbd9e7b0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 27069 XFree86 0.15 CALL sigreturn(0xbd9e6e0c) 27069 XFree86 0.04 RET sigreturn JUSTRETURN 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 Anybody have a workaround for this? The whole system (2.53 Ghz P4) was compiled from sources late last week... Between this, and the Type1 bezier font abort, the state of 5.0 on a desktop is very sorry indeed. My old alpha running -stable is far more stable. Sigh. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sorry state of Xserver in 5.0
Wesley Morgan writes: This sounds very similar to a problem I am seeing that does not result in a fatal lockup, but rather several minutes of complete unresponsiveness. It only seems to happen when Konqueror tries to autocomplete from the location bar. I'm not really sure what was happening when I triggered it. I'll try taking a deep breath and waiting a few minutes. From running top on a remote machine, it appeared that X kept on growing and growing.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
