Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Jan 2006 20:30:15 GMT
From:      Jos Witters <jos.witters@tiscali.nl>
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   Re: ports/91392: k3b port install causes reboot
Message-ID:  <200601082030.k08KUF9m004359@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/91392; it has been noted by GNATS.

From: Jos Witters <jos.witters@tiscali.nl>
To: Heiner <h.eichmann@gmx.de>
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
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601082030.k08KUF9m004359>