From owner-freebsd-current Fri Jan 30 00:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20137 for current-outgoing; Fri, 30 Jan 1998 00:56:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@spain-7.ppp.hooked.net [206.169.228.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20131 for ; Fri, 30 Jan 1998 00:56:48 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id AAA00382; Fri, 30 Jan 1998 00:58:13 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 30 Jan 1998 00:58:13 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Kris Kennaway cc: FreeBSD Current Mailing List Subject: Re: Current and X11R6 3.3 get Signal 11 abort In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, 30 Jan 1998, Kris Kennaway wrote: > On Thu, 29 Jan 1998, Ron Bolin wrote: > > > I am getting X server abort errors after running X for about 3 hours > > with a signal 11. > > Anybody else seen this. I never experienced this before this month. > > I have been getting similar problems with recent versions of current - I > reverted back to a source tree from Dec 23 (what was reported as the > "most recent stable current") and didnt seem to have any problems, but > when I resupped to the latest tree a few days ago after the reports that > things were fixed, my troubles started again. As it stands for me, it's > touch and go whether things like ports will compile fully in one go > without coredumping, which makes it annoying to do things like a whole make > world :) > > John mentioned a few days ago that he's starting to suspect some of his > changes had some unforseen side-effects for Pentium systems. I think I'll > revert to the older kernel again to confirm that my problems are > software, and not hardware-related, and hopefully this will be fixed soon :) I'm running a slightly overclocked P5 with a somewhat average motherboard, and so far, I've encountered no problems whatsoever (cept when my lkms are out of date). Heck, I even started recompiling bits and pieces of my system (kernel, libc and m) with pgcc -O9 -mpentium. So far no trouble, then of course I haven't left the system on too long recently (<5 hrs). Only today did I see one problem when the building (-j3) of lkms sigabort'd. Linux: The Microsoft Windows(tm) of the Unix(tm) world. - alex