From owner-freebsd-current Fri May 10 01:00:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA01397 for current-outgoing; Fri, 10 May 1996 01:00:13 -0700 (PDT) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA01384 for ; Fri, 10 May 1996 01:00:06 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de) by mail.rwth-aachen.de (PMDF V5.0-4 #13110) id <01I4JANV3PLS000BE5@mail.rwth-aachen.de> for freebsd-current@freefall.FreeBSD.org; Fri, 10 May 1996 09:22:35 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA13456 for freebsd-current@freefall.cdrom.com; Fri, 10 May 1996 09:30:03 +0200 Date: Fri, 10 May 1996 09:30:03 +0200 From: "Christoph P. Kukulies" Subject: Re: -current kernel panics To: freebsd-current@freefall.FreeBSD.org Message-id: <199605100730.JAA13456@gilberto.physik.rwth-aachen.de> Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I didn't notice that my / FS was at 103% due to some kernels and other stuff that had cumulated in / and /root. After bringing that back to normal conditions the same kernel (newly built though) didn't panic. I was doing a mv kernel /kernel ; sync ; reboot frequently at that time and may be there is some strangeness when the root file system is full such that not all pages are flushed or something leaving an unusable kernel in / though I think it shouldn't behave that strange or at least resort with an error message. I will still try to reproduce it. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de