From owner-freebsd-questions@FreeBSD.ORG Wed Jul 16 01:03:51 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA68B37B411 for ; Wed, 16 Jul 2003 01:03:51 -0700 (PDT) Received: from mx0.gmx.net (mx0.gmx.de [213.165.64.100]) by mx1.FreeBSD.org (Postfix) with SMTP id 5947643F3F for ; Wed, 16 Jul 2003 01:03:50 -0700 (PDT) (envelope-from daniela5743@gmx.net) Received: (qmail 26777 invoked by uid 0); 16 Jul 2003 08:03:48 -0000 Date: Wed, 16 Jul 2003 10:03:48 +0200 (MEST) From: daniela5743@gmx.net To: Matthew Seaman MIME-Version: 1.0 References: <20030715213636.GB66706@happy-idiot-talk.infracaninophile.co.uk> X-Priority: 3 (Normal) X-Authenticated-Sender: #0008958870@gmx.net X-Authenticated-IP: [212.33.58.27] Message-ID: <31052.1058342628@www48.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit cc: freebsd-questions@freebsd.org Subject: Re: KDE process is unkillable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 08:03:52 -0000 > Are you by any chance using the NVIDIA supplied drivers? I had > exactly the same symptoms with X freezing, especially when doing > something that puts a bit of load on the system. The recent upgrade > to the drivers actually made things worse. In the short term, the > only way to get the console screen back was to reboot. > > However, in the long term, it seems the problem was a bad interaction > with the FreeBSD AGP GART -- ie. the agp.ko kernel module. I > recompiled the driver to use it's own built in AGP GART and since then > everything has been rock solid stable --- the x11/nvidia port makes it > easy to switch, but remember to edit /boot/loader.conf or your kernel > config to take out (or add) the agp module. NVIDIA docs are a bit > equivocal about recommending one way or the other -- which way to > choose depends on the precise hardware you have. Only way to tell is > by experiment. There's also a sysctl hw.nvidia.agp.status.rate that > lets you control the agp card rate: it should all work automatically, > but you may find that dropping the rate will help stabilize things. > Of course, that will have a deleterious impact on graphics > performance. I don't have NVIDIA drivers. Is there any known bug in the ATI Radeon driver? I rebooted, and all I have is the saved output from fstat, no core dump. Is this enough to find out what was wrong? Can I reproduce it under controlled circumstances? -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern!