From owner-freebsd-current Tue May 6 14:52:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA07519 for current-outgoing; Tue, 6 May 1997 14:52:01 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA07487 for ; Tue, 6 May 1997 14:51:51 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA17539 for freebsd-current@freefall.FreeBSD.org; Tue, 6 May 1997 23:51:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA15150; Tue, 6 May 1997 22:47:43 +0200 (MET DST) Message-ID: <19970506224743.QJ57217@uriah.heep.sax.de> Date: Tue, 6 May 1997 22:47:43 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freefall.FreeBSD.org Subject: Re: floppy related kernel messages References: <199705061714.TAA07066@gil.physik.rwth-aachen.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705061714.TAA07066@gil.physik.rwth-aachen.de>; from Christoph Kukulies on May 6, 1997 19:14:39 +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Christoph Kukulies wrote: > In 3.0-current I'm seeing floppy problems on several machines. > They're all manifesting in some kind of > > isa_dmastart: cannel 2 busy > > which seems to occur as the first message after an fdc error, e.g. door > open or write locked with the next access after fixing the condition > that led to the first error. I can reproduce this message (and will try to fix it), but i'm afraid it's unrelated to this: > In consequence of this I seemed to have had a system crash (reboot > w/o panic) a couple of minutes ago. A few people have been reporting silent reboots, but i've never been able to see them myself. Check question: you aren't perchance using the block devices, are you? (Hmm, maybe i should start using the buffered devices, too, even though it's an error to use them. Maybe this will trigger the bug...) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)