From owner-freebsd-stable Tue May 25 11:56:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from news.kiev.sovam.com (news.kiev.sovam.com [194.186.143.16]) by hub.freebsd.org (Postfix) with ESMTP id A48AA15AD0 for ; Tue, 25 May 1999 11:56:36 -0700 (PDT) (envelope-from mail@news.kiev.sovam.com) Received: from mail by news.kiev.sovam.com with local (Exim 2.12 #1) id 10mMNP-0008Cb-00 for freebsd-stable@freebsd.org; Tue, 25 May 1999 21:56:35 +0300 From: gw-bsd-stable@news.kiev.sovam.com To: freebsd-stable@freebsd.org Reply-To: Vladimir Litovka Subject: Re: Stability Date: 25 May 1999 18:56:34 GMT Message-ID: <7ierp2$up4$1@news.kiev.sovam.com> X-Organization: Sovam Teleport Kiev (post does not reflect views of Sovam Teleport) X-Gated-By: news2list v1.0-b1, (c) Vladimir Litovka X-Gated-Date: Tue May 25 21:56:35 EEST 1999 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 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 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) And again and again and again... Infinite loop. Not good, as for me. 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 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 -- doka To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message