From owner-freebsd-stable  Fri Dec 10  0:21:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29])
	by hub.freebsd.org (Postfix) with ESMTP id 2DD5615085
	for <FreeBSD-stable@FreeBSD.ORG>; Fri, 10 Dec 1999 00:21:51 -0800 (PST)
	(envelope-from lee@lcremeans.erols.com)
Received: (from lee@localhost)
	by lcremeans.erols.com (8.9.3/8.9.3) id DAA03161;
	Fri, 10 Dec 1999 03:21:38 -0500 (EST)
	(envelope-from lee)
Date: Fri, 10 Dec 1999 03:21:38 -0500
From: Lee Cremeans <lcremeans@erols.com>
To: Greg Quinlan <gwq_uk@yahoo.com>
Cc: FreeBSD-stable@FreeBSD.ORG
Subject: Re: Bad Floppy causes Kernel Panic (3.4-RC)
Message-ID: <19991210032138.A3133@lcremeans.erols.com>
References: <19991209223956.5578.qmail@web1403.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <19991209223956.5578.qmail@web1403.mail.yahoo.com>; from gwq_uk@yahoo.com on Thu, Dec 09, 1999 at 02:39:56PM -0800
X-OS: FreeBSD 3.0-STABLE
Organization: My room? Are you crazy? :)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Dec 09, 1999 at 02:39:56PM -0800, Greg Quinlan wrote:
> Hi All,
> 
> Operating on a cvsup-ed 3.4-RC 10-12-99:
> 
> I had a bad floppy which I was trying to "tar" to but
> my server kernel panic-ed with the message:
> 
> fd0c: hard error writing fsbn ....
> Dirty Buffers
> 
> kernel panic
> 
> etc....
> 
> When I have tried to reproduce it (ie. damage a floppy
> and "tar" to it) I got a similar message but NO panic.
> 
> I put the original floppy back and "tar"-ed to it
> again, and  the system panic-ed and rebooted. So it
> was unique to this floppy.
> 
> When I tried formating the floppy (fdformat) I got:
> 
> EVVVVVVVVV......
> 
> So it appears to be that the very first part of the
> floppy was bad and this caused the kernel panic.

I've also noticed this when I use bad 1.44MB floppies with my LS-120 drive.
THe panic I get, in particular, is 

panic: vinvalbuf: dirty bufs

and my theory is that it's choking because it has dirty bufs it can't write
to disk (because of the hard errors). What do people think? I'm running
3.3-STABLE as of about 2 weeks ago.

-lee

-- 
+--------------------------------------------------------------------+
|      Lee Cremeans -- Manassas, VA, USA  (WakkyMouse on WTnet)      |  
|         lcremeans@erols.com | http://wakky.dyndns.org/~lee         |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message