From owner-freebsd-current Mon Jul 13 15:17:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21174 for freebsd-current-outgoing; Mon, 13 Jul 1998 15:17:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (root@dyn-max8-191.chicago.il.ameritech.net [206.141.211.191] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21115 for ; Mon, 13 Jul 1998 15:17:39 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id SAA11292; Mon, 13 Jul 1998 18:17:24 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35AA8772.80993BB2@ameritech.net> Date: Mon, 13 Jul 1998 18:17:22 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Andrew Gallatin CC: current@FreeBSD.ORG Subject: Re: PF_LOCAL socket problems? References: <13738.22232.735035.745625@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > Over the weekend, I built world (and kernel) for the first time in > months. Much to my chagrin, I've had X apps dying with BadLength X > errors all day. The primary offendors are Netscape & Xemacs, which > tend lock up after issuing errors like: > > X Error of failed request: BadLength (poly request too large or internal Xlib length error) > Major opcode of failed request: 86 (X_AllocColorCells) > Serial number of failed request: 59501 > Current serial number in output stream: 59576 > Widget hierarchy of resource: unknown > > I can generally crash Netscape within a few seconds by loading a large > page & scrolling around in it. > > The reason I suspect PF_LOCAL sockets is because these problems go > away if I set my DISPLAY to machinename:0.0 rather than :0.0. > As I recall, X apps talk to a server with a display of :0.0 via > PF_LOCAL sockets. > > Not that it matters, but this is on a 300Mhz PII, running XF86 3.3.2 > (XF86_SVGA atop a 4MB NNidia Riva128 agp video card) > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I too run 3.3.2 and SVGA server and -current and have been noticing the same symptoms with VNC, and sure enough using -display myhostname:0 cleared it up, thanks for the workaround! I was getting this before, while using VNC to contant either of my two NT machines. To one machine it bombed out reliably on the first screen refresh, and the other randomly. X Error of failed request: BadLength (poly request too large or internal Xlib l ength error) Major opcode of failed request: 16 (X_InternAtom) Serial number of failed request: 8403 Current serial number in output stream: 8930 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message