From owner-freebsd-bugs Wed Aug 2 21:40:11 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id CC85A37B65C for ; Wed, 2 Aug 2000 21:40:07 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA93389; Wed, 2 Aug 2000 21:40:07 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 2 Aug 2000 21:40:07 -0700 (PDT) Message-Id: <200008030440.VAA93389@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Matthew Emmerton" Subject: Re: kern/14590: kernel panic writing to floppy Reply-To: "Matthew Emmerton" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/14590; it has been noted by GNATS. From: "Matthew Emmerton" To: , 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

Using 3.4-RELEASE:

The dd command using the char device = (rfd0) works=20 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,=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.

Jul 17 19:02:33 styx /kernel: panic: = vinvalbuf:=20 dirty bufs
Jul 17 19:02:33 styx /kernel:
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 1 1 1 giving=20 up

[ 1 1 1... may be replaced by 2 2=20 2...]

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