*BSD News Article 10821


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA758 ; Sun, 07 Feb 93 09:01:24 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!uw-beaver!newsfeed.rice.edu!rice!news.Rice.edu!rich
From: rich@Rice.edu (Richard Murphey)
Subject: Re: [386bsd] XFree88 Still Chewing [was Re: Does XFree86 work with patchkit 0.2?]
In-Reply-To: jkh@whisker.lotus.ie's message of Sat, 6 Feb 1993 11:49:17 GMT
Message-ID: <RICH.93Feb6100907@omicron.Rice.edu>
Sender: news@rice.edu (News)
Reply-To: Rich@Rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
References: <51995@seismo.CSS.GOV> <1993Feb5.184620.26347@coe.montana.edu>
	<JKH.93Feb6114917@whisker.lotus.ie>
Date: Sat, 6 Feb 1993 16:09:07 GMT
Lines: 29

In article <JKH.93Feb6114917@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
   It does work, but it also *loops* now (I.E. eats a lot of CPU time it
   shouldn't be eating).  To wit:  (Totally Generic XFree86 sources compiled
   for ET4000 with gcc 2.3.3):

   jkh@whisker-> ps aux | egrep '^root.*X'; date
   root       104 97.5  4.1  1744 1308 vg  R     9:58PM  200:18.60 X :0
   Sat Feb  6 01:20:05 PST 1993
   jkh@whisker-> ps aux | egrep '^root.*X'; date
   root       104 96.4  4.1  1744 1308 vg  R     9:58PM  200:23.85 X :0
   Sat Feb  6 01:20:11 PST 1993
   jkh@whisker-> ps aux | egrep '^root.*X'; date
   root       104 95.6  4.1  1744 1308 vg  R     9:58PM  200:28.77 X :0
   Sat Feb  6 01:20:16 PST 1993

   As you can see, it's eating away.  Some of the time is naturally spent
   in scrolling the xterm I did this in, but if I leave it totally alone
   for 5 minutes (with no server I/O occuring) and come back, you'll see
   a substantial amount of time eaten up.

   This didn't begin happening until post 0.2.  I even reloaded all the
   386bsd sources from tape, reapplied patckit 0.2 and recompiled the
   world from *scratch* just on the off-chance that some of my own
   earlier hackery had caused it.  Nope.  No difference.

In the past this has most often be due to a bug in select().  Check
your patches to com.c against those in /usr/lib/X11/etc/386bsd.patch
to make sure that there isn't an off by one error that breaks select()
on the com ports.  Rich