From owner-freebsd-current Sat Jul 18 10:52:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11649 for freebsd-current-outgoing; Sat, 18 Jul 1998 10:52:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11636 for ; Sat, 18 Jul 1998 10:52:43 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id MAA20662; Sat, 18 Jul 1998 12:52:23 -0500 (CDT) Message-Id: <199807181752.MAA20662@isua3.iastate.edu> To: Andreas Klemm cc: freebsd-current@FreeBSD.ORG Subject: Re: XFree and -current In-reply-to: Your message of "Sat, 18 Jul 1998 16:41:43 +0200." <19980718164143.A13033@klemm.gtn.com> Date: Sat, 18 Jul 1998 12:52:23 CDT From: Kent Vander Velden Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980718164143.A13033@klemm.gtn.com>, Andreas Klemm writes: >On Fri, Jul 17, 1998 at 06:54:34PM -0500, Kent Vander Velden wrote: >> >> Starting a week ago after I installed a new kernel, XFree 3.3.2 >> has become _very_ flaky. The problem only seems to show up in 24 bit >> true-color mode. Many programs such as Netscape die with, generally, a >> BadLength X error. I am using the S3 server with a 4M STB Velocity 64. > >Read the thread "State of current...". >Backout the last patch of /sys/kern/uipc_socket.c (1.41 -> 1.40) >This did the trick for many people reporting netscape instability. Thanks. I read that shortly after sending my question and then receiving the freebsd-current digest. BTW: The fix works fine for me. Too bad I spent those two days hunting down a bug with my program though :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message