Date: Fri, 15 May 1998 02:38:54 -0500 (EST) From: "John S. Dyson" <dyson@FreeBSD.ORG> To: sos@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: People having problems with X windows? Message-ID: <199805150738.CAA03075@dyson.iquest.net> In-Reply-To: <199805150636.IAA01056@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "May 15, 98 08:36:43 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. 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?199805150738.CAA03075>