From owner-freebsd-bugs  Tue Nov 11 02:02:16 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA12682
          for bugs-outgoing; Tue, 11 Nov 1997 02:02:16 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA12666
          for <freebsd-bugs@hub.freebsd.org>; Tue, 11 Nov 1997 02:02:10 -0800 (PST)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id UAA29162; Tue, 11 Nov 1997 20:52:44 +1100
Date: Tue, 11 Nov 1997 20:52:44 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199711110952.UAA29162@godzilla.zeta.org.au>
To: freebsd-bugs@hub.freebsd.org, sprice@HiWAAY.net
Subject: Re: docs/4381: mount -t msdos causes panic:vm_fault
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> >Fix
> >
> >      Is this something to do with EIDE bugs?
> >      Should I perhaps start over with a clean drive, and make sure
> >      FreeBSD starts in the first 512 MB?
> 
> No this is not an EIDE bug.  It is a limitation with the PC
> BIOS that restricts bootable partitions to the first 1024
> cylinders.  See http://www.freebsd.org/FAQ/FAQ34.html#34

This has nothing to do with the BIOS either, since `mount -t msdos'
does not use the BIOS.

Apparently the file system is invalid, and msdosfs crashes on some
garbage in it.  It may be really invalid, or just a W95 file system.
It's not clear whether msdosfs can do something reasonable with
parts of a W95 file system that it doesn't understand.

Bruce