Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Sep 1997 16:04:03 +0930
From:      Greg Lehey <grog@lemis.com>
To:        =?iso-8859-1?Q?S=F8ren_Schmidt?= <sos@sos.freebsd.dk>
Cc:        FreeBSD Hackers <hackers@freebsd.org>
Subject:   Re: Current unusable :(
Message-ID:  <19970905160403.53603@lemis.com>
In-Reply-To: =?iso-8859-1?Q?=3C199709050622=2EIAA01395=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Fri=2C_Sep_05=2C_1997_at_08=3A22=3A5?= =?iso-8859-1?Q?8AM_%2B0200?=
References:  <19970905105229.28743@lemis.com> <199709050622.IAA01395@sos.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 05, 1997 at 08:22:58AM +0200, Søren Schmidt wrote:
> In reply to Greg Lehey who wrote:
>>>> I still believe this actually can be the case. Since xquake won't work
>>>> with network game any longer for me (haven't since around the 18-20/8 (I
>>>> think :)). If anyone want a kdump mail me and i'll give you one.
>>>
>>> Hmm, I found out my problem is the XF86_SVGA server, it goes totally
>>> wild when starwriter is run, causing the system to go into a tight
>>> loop using all CPU cycles between system & user in the XF86_SVGA
>>> process. If I use the XF86_S3V or Xaccel-2.1 (yes I'm on a ViRGE DX)
>>> this problem does not surface.
>>
>> Yes, I'm using Xaccel on both systems, so that at least explains why
>> the thing doesn't crash.
>>
>>> So its not our problem, it belongs in the XFree86 camp :)
>>
>> I wouldn't go that far.  Do you get the thing to work with Xaccel?
>> Have you tried displaying on a different server?
>
> Just tried that, works pretty well, albeit slow.
> It fails exceptionally well if I use the XF86_VGA server :)
> Well the XFree86 group says that the ViRGE driver in XF86_SVGA is new
> and raw, so I guess I asked for it....

Well, I tried again.  Yes, it's some kind of DNS problem.  Ever run
tcpdump on the loopback interface? :-)

tcpdump: listening on lo0
15:58:20.827404 freebie.lemis.com.1132 > freebie.lemis.com.domain: 36050+ A? freebie.lemis.com. (35)
15:58:20.828349 freebie.lemis.com.domain > freebie.lemis.com.1132: 36050* 1/3/3 A freebie.lemis.com (173)
15:58:21.954206 freebie.lemis.com.1133 > freebie.lemis.com.domain: 12023+ PTR? 137.197.109.192.in-addr.arpa. (46)
15:58:21.955195 freebie.lemis.com.domain > freebie.lemis.com.1133: 12023* 1/3/3 PTR freebie.lemis.com. (214)
15:58:26.094915 freebie.lemis.com.1134 > freebie.lemis.com.domain: 17952+ A? freebie.lemis.com. (35)
15:58:26.095738 freebie.lemis.com.domain > freebie.lemis.com.1134: 17952* 1/3/3 A freebie.lemis.com (173)
15:58:31.111972 freebie.lemis.com.1135 > freebie.lemis.com.domain: 17952+ A? freebie.lemis.com. (35)
15:58:31.112768 freebie.lemis.com.domain > freebie.lemis.com.1135: 17952* 1/3/3 A freebie.lemis.com (173)
15:58:41.134568 freebie.lemis.com.1136 > freebie.lemis.com.domain: 17952+ A? freebie.lemis.com. (35)
15:58:41.135338 freebie.lemis.com.domain > freebie.lemis.com.1136: 17952* 1/3/3 A freebie.lemis.com (173)
15:59:01.162085 freebie.lemis.com.1137 > freebie.lemis.com.domain: 17952+ A? freebie.lemis.com. (35)
15:59:01.162887 freebie.lemis.com.domain > freebie.lemis.com.1137: 17952* 1/3/3 A freebie.lemis.com (173)
15:59:41.193847 freebie.lemis.com.1138 > freebie.lemis.com.domain: 17953+ A? freebie.lemis.com.lemis.com. (45)
15:59:41.219415 freebie.lemis.com.domain > freebie.lemis.com.1138: 17953 NXDomain* 0/1/0 (103)
15:59:46.202378 freebie.lemis.com.1139 > freebie.lemis.com.domain: 17953+ A? freebie.lemis.com.lemis.com. (45)
15:59:46.202899 freebie.lemis.com.domain > freebie.lemis.com.1139: 17953 NXDomain* 0/1/0 (103)
15:59:56.221882 freebie.lemis.com.1140 > freebie.lemis.com.domain: 17953+ A? freebie.lemis.com.lemis.com. (45)
15:59:56.222395 freebie.lemis.com.domain > freebie.lemis.com.1140: 17953 NXDomain* 0/1/0 (103)

It looks as if it's not able to handle the response correctly.

Greg



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