greturn 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, th
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 t
Maxim Sobolev wrote:
>
> Maxim Sobolev wrote:
> >
> > Maxim Sobolev wrote:
> > >
> > > Andrew Gallatin wrote:
> > > >
> > > > Maxim Sobolev writes:
> > > >
> > > > > > Between this, and the Type1 bezier
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 sa
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
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
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.
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.
>
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.
--
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
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.
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 p
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
> suspicio
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
greturn 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 abo
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 ha
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 wha
x80d219c 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 runni
ybody 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 ma
common/S3/obj/usr/src/sys/LAPTOP_30W_NC i386
g1-7(5.0-C)[2]
So... move along, folks; nothing to see here Sorry for the noise.
Cheers,
david (links to my resume at http://www.catwhisker.org/~david)
--
David H. Wolfskill [EMAIL PROTECTED]
I believe it wo
Okay, AFTER rebuilding linuxthreads with the most recent port, IT DID make it past
gen_lex_hash.
Word to the wise, if you haven't rebuilt linuxthreads, I suggest you do to avoid the
problems I have had.
Again, I am running -current of the early hours [CDT] of Sunday morning.
Jim Bryant wrote:
While trying to upgrade a 3.3-Stable box to 4.2-Release, we crashed
during the upgrade. After restoring the system from tape, password no
longer work.
We've tried killing all files except master.passwd and regenerating with
pwd_mkdb, but that didn't work.
Any help would be greatly appreciated.
---
[EMAIL PROTECTED] ICQ 13383291
Metro Tasmania Pty Ltd Phone 0419585308
- If it works, tear it apart and find out why!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I was thinking about -current something and wrote current. Please
disregard my message.
Soren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Well, I wasn't back in town until last night with 5000 messages to catch
> up on. Sorry for not getting your questions first.
>
> There are other things broken too. Oh well- I really shouldn't get wired.
> *BSD will get taken as a serious effort as much as it d
recently would have alleviated (sp?) the hangs I've been getting
> > > > while building things in ports for the last couple of months.
> > > >
> > > > It used to be that just NFS would hang, now it seems to crash the
> > > > entire box.
ugh,
signal 11
*** Error code 1
Sorry! My BIOS settings was incorrect! Make world is OK!
REM
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
27 matches
Mail list logo
