From owner-freebsd-questions Mon Oct 28 00:42:04 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA13161 for questions-outgoing; Mon, 28 Oct 1996 00:42:04 -0800 (PST) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA13153 for ; Mon, 28 Oct 1996 00:41:56 -0800 (PST) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.7.5/8.6.12) id KAA25248; Mon, 28 Oct 1996 10:41:05 +0200 (IST) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma025243; Mon Oct 28 10:40:45 1996 Message-ID: <32747178.2677@barcode.co.il> Date: Mon, 28 Oct 1996 10:40:24 +0200 From: Nadav Eiron X-Mailer: Mozilla 2.02 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: adrian@virginia.edu CC: FreeBSD Questions List Subject: Re: instability with 2.1.5 kernel References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Adrian T. Filipi-Martin wrote: > > Hi folks, > > When shutting down my 2.1.5-RELEASE system, the kernel is failing > with alarming regularity to flush all of the buffers. I frequently see > about a dozen 4's and the a "giving up" message before the system > reboots. When the systme comes up the root filesystem and sometimes > others are not marked clean and must be fsck'ed. > > Has anyone else seen this? Yes! I never bothered to post to questions (or stable) about it as I seldom shutdown my machines, but almost whenever I do, I can see this symptom. There are other weird things with shutdown on 2.1.5: For example, shutting down from an xterm (which used to work just fine) would hang up the machine instead of switching back to the console vty0 before halting. > > I have also seen a 'shutdown -h +0' go directly to rebooting. > > These problems did not appear until after upgrading from 2.1. I > have not seen any wierdness with prior version. > > Bad hardware or a bug? I guess it's a bug of some sortrs, as I see the same behaviour on two machines (though I only shut them down for kernel rebuilds and the such, which is not very often). > > thanks, > Adrian > > adrian@virginia.edu ---->>>>| Support your local programmer, > System Administrator --->>>| STOP Software Patent Abuses NOW! > NVL, NIIMS and Telemedicine Labs -->>| For an application and information > Member: League for Programming Freedom ->| see: http://www.lpf.org/ Nadav