From owner-freebsd-hackers Tue Jun 29 11:53: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 7497C15403 for ; Tue, 29 Jun 1999 11:53:00 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 61110 invoked from network); 29 Jun 1999 18:53:00 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 29 Jun 1999 18:53:00 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id NAA01639; Tue, 29 Jun 1999 13:52:56 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Tue, 29 Jun 1999 13:52:56 -0500 (CDT) From: David Scheidt To: Travis Cole Cc: Jamie Howard , Zhihui Zhang , freebsd-hackers@FreeBSD.ORG Subject: Re: A way to crash system (3.1 & 3.2) with floppy In-Reply-To: <19990629003945.A28540@wcug.wwu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Travis Cole wrote: > On Mon, Jun 28, 1999 at 09:30:05PM -0400, Jamie Howard wrote: > > On Mon, 28 Jun 1999, Zhihui Zhang wrote: > > > > I just reproduced this on a system running 4.0-CURRENT from about > Sun Jun 27 01:12:42 PDT > > I got a ton of these errors in dmesg and /var/log/messages: > Jun 29 00:17:53 marx /kernel: fd0c: hard error writing fsbn 19 (ST0 40 ST1 2 ST2 0 cyl 0 hd 1 sec 2) > > And it let me try several umount commands and even a umount -f. None > of them actualy umounted the floppy drive and it completly reboot my computer > after about 2 or 3 mins. No panic or anything. Once second I'm looking at X, I can do this from -CURRENT from whenever CTM broke. I have a panic, and a dump which i havne't had time to look at. The panic string is panic: vinvalbuf: dirty bufs David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message