From miek@q8.se Fri Oct 29 06:50:07 1999
Return-Path: <miek@q8.se>
Received: from kpserv.q8.se (kpserv.q8.se [192.16.144.70])
	by hub.freebsd.org (Postfix) with ESMTP id CFB97155DE
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 29 Oct 1999 06:49:58 -0700 (PDT)
	(envelope-from miek@q8.se)
Received: from kpserv (localhost [127.0.0.1])
	by kpserv.q8.se (8.9.3/8.9.3) with ESMTP id PAA27976
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 29 Oct 1999 15:50:01 +0200 (MET DST)
Message-Id: <199910291350.PAA27976@kpserv.q8.se>
Date: Fri, 29 Oct 1999 15:50:01 +0200
From: Mikael Eklund <miek@q8.se>
Reply-To: miek@q8.se
To: FreeBSD-gnats-submit@freebsd.org
Subject: kernel panic writing to floppy
X-Send-Pr-Version: 3.2

>Number:         14590
>Category:       kern
>Synopsis:       kernel panic writing to floppy
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 29 07:00:00 PDT 1999
>Closed-Date:    Thu Aug 3 00:12:01 PDT 2000
>Last-Modified:  Thu Aug 03 00:14:00 PDT 2000
>Originator:     Mikael Eklund
>Release:        FreeBSD 3.3-RELEASE i386
>Organization:
OK-Q8 AB
>Environment:

	AST Bravo MS5166, Pentium 166MHz, 64MB RAM, 2GB disk

>Description:

	Kernel panics when trying to write to a write-protected floppy.

>How-To-Repeat:

	Insert a write-protected floppy.
	Run the command: dd if=foo of=/dev/fd0 bs=512

>Fix:
	
	Use the correct (raw) device instead. :-)

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->suspended 
State-Changed-By: phk 
State-Changed-When: Fri Oct 29 23:46:18 PDT 1999 
State-Changed-Why:  
This is no longer a problem for since block devices now act as char devices. 
I am not sure however, if this problem would also manifest itself if the 
faulty floppy was mounted as a filesystem, therefore the "suspend" state. 

From: "Matthew Emmerton" <matt@gsicomp.on.ca>
To: <freebsd-gnats-submit@FreeBSD.org>, <miek@q8.se>
Cc:  
Subject: Re: kern/14590: kernel panic writing to floppy
Date: Thu, 3 Aug 2000 00:30:00 -0400

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_000B_01BFFCE1.F532C6D0
 Content-Type: text/plain;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 Using 3.4-RELEASE:
 
 The dd command using the char device (rfd0) works fine (no panic), but =
 using the block device (fd0) panics.
 
 On to the open->suspend rationale:
 
 Mounting a writeable floppy, pulling the disk, write-protecting it, =
 replacing it, and then writing to the FS results in a console message =
 complaining about writing to a write-protected media (expected), but =
 when the FS is unmounted, a kernel panic occurs.
 
 Jul 17 19:02:33 styx /kernel: panic: vinvalbuf: dirty bufs
 Jul 17 19:02:33 styx /kernel:
 Jul 17 19:02:33 styx /kernel: syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 =
 1 1 1 1 1 1 1 giving up
 
 [ 1 1 1... may be replaced by 2 2 2...]
 
 
 
 ------=_NextPart_000_000B_01BFFCE1.F532C6D0
 Content-Type: text/html;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META content=3D"text/html; charset=3Diso-8859-1" =
 http-equiv=3DContent-Type>
 <META content=3D"MSHTML 5.00.3018.900" name=3DGENERATOR>
 <STYLE></STYLE>
 </HEAD>
 <BODY bgColor=3D#ffffff>
 <DIV><FONT face=3DArial size=3D2>Using 3.4-RELEASE:</FONT></DIV>
 <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>The dd command using the char device =
 (rfd0) works=20
 fine (no panic), but using the block device (fd0) panics.</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>On to the open-&gt;suspend =
 rationale:</FONT></DIV>
 <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>Mounting a&nbsp;</FONT><FONT =
 face=3DArial=20
 size=3D2>writeable floppy, pulling the disk, write-protecting it, =
 replacing it,=20
 and then writing to the FS results in a console message complaining =
 about=20
 writing to a write-protected media (expected), but when the FS is =
 unmounted, a=20
 kernel panic occurs.</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>Jul 17 19:02:33 styx /kernel: panic: =
 vinvalbuf:=20
 dirty bufs<BR>Jul 17 19:02:33 styx /kernel:<BR>Jul 17 19:02:33 styx =
 /kernel:=20
 syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1&nbsp;1 1 1 giving=20
 up</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>[ 1 1 1... may be replaced&nbsp;by 2 2=20
 2...]</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV>&nbsp;</DIV></BODY></HTML>
 
 ------=_NextPart_000_000B_01BFFCE1.F532C6D0--
 
 
State-Changed-From-To: suspended->closed 
State-Changed-By: sheldonh 
State-Changed-When: Thu Aug 3 00:12:01 PDT 2000 
State-Changed-Why:  
So then we're back to a known problem.  Duplicate of kern/11808 
and kern/10870 . 

http://www.freebsd.org/cgi/query-pr.cgi?pr=14590 
>Unformatted:
