From owner-freebsd-current  Fri May 15 05:44:01 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA15635
          for freebsd-current-outgoing; Fri, 15 May 1998 05:44:01 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15617;
          Fri, 15 May 1998 05:43:55 -0700 (PDT)
          (envelope-from dawes@rf900.physics.usyd.edu.au)
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id WAA16557; Fri, 15 May 1998 22:43:53 +1000 (EST)
Message-ID: <19980515224353.26233@rf900.physics.usyd.edu.au>
Date: Fri, 15 May 1998 22:43:53 +1000
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
To: dyson@FreeBSD.ORG
Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: People having problems with X windows?
References: <199805150636.IAA01056@sos.freebsd.dk> <199805150738.CAA03075@dyson.iquest.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.69
In-Reply-To: <199805150738.CAA03075@dyson.iquest.net>; from John S. Dyson on Fri, May 15, 1998 at 02:38:54AM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, May 15, 1998 at 02:38:54AM -0500, John S. Dyson wrote:
>Søren Schmidt said:
>> In reply to John S. Dyson who wrote:
>> > Check for a message something like:
>> > 
>> > pmap: added WC mapping at address ????
>> > 
>> > There might be a correlation between that message and system failures?
>> 
>> I did a few experiments here, if I start the X server from a telnet
>> session, the server comes up with all its output on the telnet
>> session, but the X display stop abruptly after very few screen
>> updates, in my case it hangs in the startup of fvwm95. I had
>> a top running on another telnet session and it continued to work
>> and showed the X server eating up all available cpu on
>> "CPU0", the top command run on CPU1 here so that might be
>> why it still worked. everything else was dead in the water,
>> ie no network no keyboard no nothing...
>> 
>I just removed my WC "improvements", by adding the return to the
>subroutine in the pmap code.  See if it is more friendly.  The
>symptoms appear to be those associated with improper setting of
>WC mode for a display adaptor.  I had to add a heuristic to make
>it work correctly on one of my cards, but I guess it was bad.
>
>The code is still in there, but I guess there is the need for more
>research into the issue.

What were you using to determine when to enable WC?

David

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message