From owner-freebsd-current Fri May 15 00:24:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27342 for freebsd-current-outgoing; Fri, 15 May 1998 00:24:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27330; Fri, 15 May 1998 00:24:01 -0700 (PDT) (envelope-from spadger@best.com) Received: from best.com (dynamic58.pm07.sf3d.best.com [209.24.235.186]) by proxy3.ba.best.com (8.8.8/8.8.BEST) with ESMTP id AAA18771; Fri, 15 May 1998 00:22:36 -0700 (PDT) Message-ID: <355BED3A.CF642102@best.com> Date: Fri, 15 May 1998 00:22:34 -0700 From: Andy Sparrow Organization: What, me organised? I don't think so... X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: dyson@FreeBSD.ORG CC: Richard J Kuhns , current@FreeBSD.ORG Subject: Re: People having problems with X windows? References: <199805150415.XAA00284@dyson.iquest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson wrote: > For the first statement in /sys/i386/i386/pmap.c, pmap_setdevram, > please just place a return there. That'll mostly disable the new > feature and might fix the problem for you. If it does, let me know, > so I can disable it. Result!!! :-) That fixes the problem with X for me on a kernel/world CVSupped ~ 11th May, which rebuilding XFree86 failed to do. Previously, starting the X server might or might not lock the machine for network access, but definately stopped the console working (beep when try to switch VTs), and the server would eat 75% of CPU. Even just starting the server and moving the cursor around would lock up after a little while, any other clients just seemed to hasten that.. Been up for about 20 minutes now, everything seems normal again. Thanks! As an aside, that (previous) kernel gave me a "de0: autosense failed - cable problem?" message everytime on bootup, (Cogent EM110 card) and the ifconfig line with "media 100baseTX mediaopt full-duplex" in rc.conf didn't help. (the link and RX lights were solid on the switch, no 100TX light despite a message saying it had done the configuration, and no packets passed over that interface at all). I found that I had to take de0 down, delay a few seconds (?? 5 worked) and bring it back up again. Since applying that change to pmap.c, the Cogent Just Works again, which is a very pleasant bonus :-) Regards, AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message