From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Jan 8 20:30:16 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C6A616A41F for ; Sun, 8 Jan 2006 20:30:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E731A43D4C for ; Sun, 8 Jan 2006 20:30:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k08KUFWf004360 for ; Sun, 8 Jan 2006 20:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k08KUF9m004359; Sun, 8 Jan 2006 20:30:15 GMT (envelope-from gnats) Date: Sun, 8 Jan 2006 20:30:15 GMT Message-Id: <200601082030.k08KUF9m004359@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Jos Witters Cc: Subject: Re: ports/91392: k3b port install causes reboot X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jos Witters List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2006 20:30:16 -0000 The following reply was made to PR ports/91392; it has been noted by GNATS. From: Jos Witters To: Heiner Cc: bug-followup@freebsd.org, edwin@freebsd.org Subject: Re: ports/91392: k3b port install causes reboot Date: Sun, 08 Jan 2006 21:24:03 +0100 OK thanx gues for your replies, Upon Edwins remarks I did the following : Reboot without the x-window system, but still with all the modules in place (including C-Media sound and Nvidia video). Root had no problem now building and installing K3b. It runs without a hitch. To be honest I've had this problem several times before, but as it happened to ports that were to me no more than nice to have, in a non critical situation I never took the trouble acting upon them. There was just one common factor. It always happened during port builds. Upon Heiners remarks I didn't really have to do anything, because during the past week I among others build : Gnome-2.12.2-, Jdk1.5-, Openoffice- ports, this trio alone is sufficient for 15 hrs of build and install time. The only problem experienced here was boredom. On the panics: My BSD disk are devided in 2 partions and 5 slices in the following way : ad1s1a / ad1s1e /tmp ad1s1d /usr/home ad1s2d /usr ad1s1f /var Panicing boot 1 : Normal system boot attempt paniced after ntp contact in KBD Panicing boot 2 : Safe mode boot same Singe user mode : did fsck_ufs on all sliced except /. As I did't have to unmount anything here I assume that they weren't mounted in the first place. Errors were found on all of them. With those repaired I rebooted without any problem except ofcause that / had to be checked. Couldn't it just have been the case that some pieces of software were located on the unmounted slices causing the panic. Jos. On Sat, 2006-01-07 at 17:28 +0100, Heiner wrote: > Hi! > > Same here. The reported kernel panics are a strong indication, that Jos' > system might be corrupt. If I reset my system during a port build, I just > have to perform a file system check during the next boot. I never saw a panic > here. > > I recommend Jos to rebuild several big ports (stress test). If other ports > kill bsd as well, it's Jos' computer. If not we should see, if others report > the same. Here (FreeBSD 5.4) k3b installed without an error. > > > Heiner