From owner-freebsd-stable@FreeBSD.ORG Mon May 2 16:28:38 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1316A4CE for ; Mon, 2 May 2005 16:28:38 +0000 (GMT) Received: from ll.mit.edu (LLMAIL.LL.MIT.EDU [129.55.12.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB61E43D58 for ; Mon, 2 May 2005 16:28:37 +0000 (GMT) (envelope-from mak@ll.mit.edu) Received: (from smtp@localhost) by ll.mit.edu (8.12.10/8.8.8) id j42GSb5T002981 for ; Mon, 2 May 2005 12:28:37 -0400 (EDT) Received: from koerber.llan.ll.mit.edu( ), claiming to be "[155.34.104.109]" via SMTP by llpost, id smtpdAAA.Uaagf; Mon May 2 12:28:21 2005 Message-ID: <42765525.6060607@ll.mit.edu> Date: Mon, 02 May 2005 12:28:21 -0400 From: "Michael A. Koerber" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050330) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org References: <427630ED.80000@ll.mit.edu> <44fyx5d7ae.fsf@be-well.ilk.org> In-Reply-To: <44fyx5d7ae.fsf@be-well.ilk.org> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: mount_msdosfs /dev/fd0 causes reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 16:28:38 -0000 mtools was actually my first attempt at accessing the floppy drive. Exactly the same end result. I issued 'mdir a:' and after a few seconds I was watching my system reboot. After doing that twice with mdir, I uninstalled mtools thinking it was the problem. When I saw mount_msdosfs gave me the same result, I began to suspect something more basic to be at fault. mike --------------------- Dr Michael A. Koerber x3250 Lowell Gilbert wrote: > "Michael A. Koerber" writes: > > >>I'm using 5.3-RELEASE and issuing the subject command, after a few >>seconds pause, causes a reboot. There are no /var/log/messages. In one >>case I saw a "stray irq 9" message flash across the console. Has anyone >>come across this problem? > > > The IRQ 9 is *probably* unrelated. > > Although it doesn't excuse the presence of bugs in the first place, > problems with mounted filesystems affect the kernel itself, so I've > always been leery of mounting filesystems from unreliable media (like > floppies) and usually stick to using mtools. Do you have the mtools > port installed? > >