From owner-freebsd-questions  Thu Nov  9 12:30:51 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from dh198-236.dhcp.sunysb.edu (dh198-236.dhcp.sunysb.edu [129.49.198.236])
	by hub.freebsd.org (Postfix) with ESMTP id AFE4937B479
	for <freebsd-questions@freebsd.org>; Thu,  9 Nov 2000 12:30:46 -0800 (PST)
Received: (from chris@localhost)
	by dh198-236.dhcp.sunysb.edu (8.9.3/8.9.3) id PAA03713;
	Thu, 9 Nov 2000 15:30:42 -0500 (EST)
	(envelope-from chris)
From: Christopher Rued <c.rued@xsb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14859.2418.463305.245239@chris.xsb.com>
Date: Thu, 9 Nov 2000 15:30:42 -0500 (EST)
To: freebsd-questions@freebsd.org
Subject: crash with fd0/msdos_fs/more
X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Last night, while attempting to do a `more' on a file on a MS-DOS
floppy, my system crashed.  I did not see the error message right
away, and the next thing I knew the system was rebooting.  So, I
decided to try it again.  Here's what I did:

# mount_msdos /dev/fd0 /mnt
# cd /mnt
# cp I\ Quit.doc ~
vm_fault: pager read error, pid 3379 (cp)  <-- from syslog, I think
cp: /home/chris/I Quit.doc: Bad address
# more I\ Quit.doc
panic: vm_fault fault on nofault entry addr: c58f200

<< system reboots >>

This was on a FreeBSD 3.5-STABLE machine.  

I was curious at this point, and decided to check if the same thing
would happen on my 4.1.1-RELEASE machine:

# mount_msdos /dev/fd0 /mnt
# cd /mnt
# cp I\ Quit.doc ~
vm_fault: pager read error, pid 58 (cp)  <-- from syslog, I think
cp: /home/chris/I Quit.doc: Bad address
# more I\ Quit.doc

<< Here, I got a couple of screenfuls of junk with @^ and <FF>, etc,
   which is probably OK, since it is a MS-Word doc. >>

panic: isa_dmacheck: no physical page present.

<< system reboots >>

I imagine that I should probably submit a bug report for this, since I
really don't think a bad floppy should crash my system :).

This is not really a major problem, but I think it's an issue.  It
only happens on the one specific file.  I am able to access the other
files on the disk without a problem.

Has anyone heard of such a thing happening?

Why would `more' consistently crash my system, but `cp' not?  I think
cp handled it properly -- report the error without crashing.  The
problem is with more.  I haven't tried any other commands on the file.

What category would this go into?  `misc', `kern', `bin', `i386',
other?
-- 
Christopher Rued


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message