Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Jul 1998 18:17:22 -0400
From:      Adam McDougall <mcdougall@ameritech.net>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        current@FreeBSD.ORG
Subject:   Re: PF_LOCAL socket problems?
Message-ID:  <35AA8772.80993BB2@ameritech.net>
References:  <13738.22232.735035.745625@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35AA8772.80993BB2>