From owner-freebsd-current@FreeBSD.ORG Sun Feb 15 18:40:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EF1E16A4CE for ; Sun, 15 Feb 2004 18:40:06 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A50043D1D for ; Sun, 15 Feb 2004 18:40:06 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i1G2ddDL062936; Sun, 15 Feb 2004 21:39:39 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i1G2dcZg062933; Sun, 15 Feb 2004 21:39:39 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 15 Feb 2004 21:39:38 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jesse Guardiani In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: process exiting strangeness under 5.2.1-RC2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 02:40:06 -0000 On Sun, 15 Feb 2004, Jesse Guardiani wrote: > These messages continued forever on my primary console until I went to > single user mode. Stock kernel. Booting with hint.apic.0.disabled=1. > > uname -a: > > FreeBSD trevarthan.int.wingnet.net 5.2.1-RC2 FreeBSD 5.2.1-RC2 #0: Thu > Feb 12 16:28:31 GMT 2004 > root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 > > I've since been unable to reproduce the problem. Still, it stikes me as > rather bad that a process was looping on core dump. I've still got the > kdeinit.core if anyone is interested. Well, I wouldn't preclude a kernel bug, but at a first glance it sounds like a bug in KDE. Signal 6 is SIGABRT, and is typically generated as a result of an application calling abort() after failing an assertion. The incrementing pid in the log suggests a series of processes being spawned off by a parent process, each one dying, and then the parent trying again. I've seen KDE behave somewhat badly when the connection to the X server dies, so perhaps kicker is trying to respawn the DCOP server. A stack trace from the core wouldn't hurt, but may not be very useful without debugging symbols for the binary and libraries. You might want to search the KDE mailing list archives and see if they mention this problem. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research