From owner-freebsd-questions@FreeBSD.ORG Wed Jul 16 15:30:50 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 05E0237B401 for ; Wed, 16 Jul 2003 15:30:50 -0700 (PDT) Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by mx1.FreeBSD.org (Postfix) with SMTP id CB78843F85 for ; Wed, 16 Jul 2003 15:30:48 -0700 (PDT) (envelope-from daniela5743@gmx.net) Received: (qmail 20200 invoked by uid 0); 16 Jul 2003 22:30:47 -0000 Date: Thu, 17 Jul 2003 00:30:47 +0200 (MEST) From: daniela5743@gmx.net To: Jan Grant MIME-Version: 1.0 References: X-Priority: 3 (Normal) X-Authenticated-Sender: #0008958870@gmx.net X-Authenticated-IP: [212.33.58.27] Message-ID: <2680.1058394647@www42.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 22:30:50 -0000 > On Wed, 16 Jul 2003 daniela5743@gmx.net wrote: > > > 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? > > You said the process was marked as stuck waiting for disk activity. Do > you have any network-mounted (or other unusual) filesystems on this > machine? I have a NFS server, but there were no connections at this time. KDE sends stuff on port 111 via the loopback interface, but I don't really know what it is doing. > If a processes wedges in the middle of a kernel call, then you won't be > able to kill it - the behaviour you've seen here. This may be a dumb question, but why the hell did the process use up all the CPU time while it was waiting? I tried attaching to it with gdb and with truss, but I got no information. I guess it is some kind of overflow, that caused the process to execute one instruction repeatedly (only guessed, I'm not an expert). If it is an overflow, the cause must be in the environment. KDE was just starting up, it did what it always does on startup. -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern!