From owner-freebsd-stable Tue Apr 29 09:28:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24021 for stable-outgoing; Tue, 29 Apr 1997 09:28:04 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23988 for ; Tue, 29 Apr 1997 09:27:57 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id JAA25385; Tue, 29 Apr 1997 09:27:53 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id JAA06658; Tue, 29 Apr 1997 09:27:53 -0700 (PDT) Date: Tue, 29 Apr 1997 09:27:53 -0700 (PDT) From: Chris Timmons To: Brian Tao cc: freebsd-stable@freebsd.org Subject: Re: System freezes with 2.2-970420 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've seen the newfs'ing-the-block-device situation in recent RELENG_2_2 kernels and even 3.0-current. On the 2.2 machine I hit ^C - and at about that time everything hung. I didn't have physical access to the machine at the time so in desperation I ssh'd it a 'reboot' just in case. Nothing happened at first, and I then noticed that even ping requests of the machine were failing. But before the ssh command timed out the machine fully recovered... and then rebooted :( -Chris On Mon, 28 Apr 1997, Brian Tao wrote: > Changing from an old 3.0 snapshot to a recent 2.2-STABLE seems to > have fixed the ahc-related problems (it survived a 36-hour burn-in > with two 2940UW's and seven 4.3GB drives). However, I've come across > two ways to freeze up a 2.2-970420-RELENG system, one of them I was > able to reproduce consistently. > > The first is newfs'ing a disk via the block device rather than the > raw device. Doing so freezes up the machine at the same point in the > newfs each time. Using the raw device works fine: [...]