Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Sep 1997 10:52:29 +0930
From:      Greg Lehey <grog@lemis.com>
To:        =?iso-8859-1?Q?S=F8ren_Schmidt?= <sos@sos.freebsd.dk>
Cc:        Johan Larsson <gozer@ludd.luth.se>, hackers@freebsd.org
Subject:   Re: Current unusable :(
Message-ID:  <19970905105229.28743@lemis.com>
In-Reply-To: =?iso-8859-1?Q?=3C199709041512=2ERAA00285=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Thu=2C_Sep_04=2C_1997_at_05=3A12=3A0?= =?iso-8859-1?Q?0PM_%2B0200?=
References:  <Pine.SUN.3.95.970904152805.3394B-100000@father.ludd.luth.se> <199709041512.RAA00285@sos.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 04, 1997 at 05:12:00PM +0200, Søren Schmidt wrote:
> In reply to Johan Larsson who wrote:
>> On Thu, 4 Sep 1997, Greg Lehey wrote:
>>> On Thu, Sep 04, 1997 at 09:15:28AM +0200, Søren Schmidt wrote:
>>>> I just found out that -current is hosed, try run the linuxulator and
>>>> then start up a moderately big app (eg StarWriter), and the system
>>>> just hangs no panic no nothing just a hang....
>>>>
>>>> Seems this has been for awhile, a 970827 kernel fails too...
>>> To follow up on my last message: after several minutes, StarWriter
>>> came up as usual.  Here's the critical part of the ktrace.  If I had
>>> time, I'd fix ktrace so that it would understand Linux system calls...
>>> BTW, I was monitoring the connection to the outside world during this
>>> time, since I suspected that it might be doing a DNS query, but that
>>> doesn't seem to be the case.
>> 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?

Greg



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