From owner-freebsd-stable Tue May 25 15:54:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6BA10151AF for ; Tue, 25 May 1999 15:54:07 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA06457; Wed, 26 May 1999 00:13:22 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA05565; Tue, 25 May 1999 23:58:05 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905252158.XAA05565@yedi.iaf.nl> Subject: Re: Stability In-Reply-To: <7ierp2$up4$1@news.kiev.sovam.com> from "gw-bsd-stable@news.kiev.sovam.com" at "May 25, 1999 6:56:34 pm" To: doka@triton.kiev.sovam.com Date: Tue, 25 May 1999 23:58:05 +0200 (CEST) Cc: freebsd-stable@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As gw-bsd-stable@news.kiev.sovam.com wrote ... > Wilko Bulte wrote: > > >> Second i made a small experiment trying to see wether the floppy > >> problem is still there. > > > > FreeBSD yedi.iaf.nl 3.2-STABLE FreeBSD 3.2-STABLE #0: Tue May 25 17:26:33 CEST 1999 root@yedi.iaf.nl:/usr/freebsd-3.1-stable-src/src/sys/compile/YEDI i386 > [ ... ] > > No panic. NREP as far as I can see. > > FreeBSD 3.2-19990522-STABLE: when dd'ing /kernel to write protected > floppy, it doesn't panic, but I can't kill this process in any way and In my case it exits immediately with an error. > this process doesn't finish in reasonable time. I waited about 10 > minutes and then rebooted computer - it couldn't correctly shutdown, said > "Syncing disks" and rebooted. After restart it said that / wasn't > properly dismounted. Almost panic, without panic message... > > While dd'ing it logs lots of information about this process, something > similar to: > > cdrw /kernel: fd0c: hard error writing fsbn 0 of 0-3 (No status) > ^^^^^^^^ > and this for all source's size space It sure looks like your system's kernel can not tell the disk is write protected and tries to write. > and then, without pause: > > cdrw /kernel: fd0c: hard error writing fsbn 0 of 0-3 (ST0 40 ST1 2 ST2 0 cyl 0 hd 0 sec 1) Write protect detected after all. Strange.. > Ok. dd'ing boot.flp (2949120 bytes) to write protected 1.44 fd gives such > result: > > dd if=boot.flp of=/dev/fd0 > dd: /dev/fd0: end of device > 358+0 records in > 358+0 records out > 182784 bytes transferred in 49.324598 secs (3706 bytes/sec) > ^^^^^^ > Note transferred size. Even not 1.44Mb... > > and then panic with message: > > panic: vinvalbuf: dirty bufs Ah! Try: dd if=boot.flp of=/dev/rfd0 (note the rfd0 instead of the fd0) > Third test: dd'ing boot.flp to write enabled 1.44Mb floppy is correct > - 2881+0 records in, 2880+0 records out. BUT! When used bs=8192, FreeBSD > hanged immediately. > > And last: quite unexpected behaviour when eject diskette from drive while > dd'ing to it something. In my case it was panic with message: > > fd0c: hard error writing fsbn 81 of 80-83 (No status) > fd0c: hard error writing fsbn 84 of 84-87 (No status) > fd0c: hard error writing fsbn 81 of 80-83 (No status) > fd0c: hard error writing fsbn 81 of 80-83 (No status) > fd0c: hard error writing fsbn 81 of 80-83 (No status) > fd0c: hard error writing fsbn 81 of 80-83 (No status) > panic: vinvalbuf: dirty bufs > > syncing disk... 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 giving up > Automatic reboot in 15 seconds ... > ... > > So, work with FDD still unstable in FreeBSD 3.x I don't agree.. Start using the raw device and report back please. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message