From owner-freebsd-hackers  Fri Nov 15 13:01:29 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA16067
          for hackers-outgoing; Fri, 15 Nov 1996 13:01:29 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA16047
          for <hackers@FreeBSD.org>; Fri, 15 Nov 1996 13:01:23 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id HAA27679; Sat, 16 Nov 1996 07:59:35 +1100
Date: Sat, 16 Nov 1996 07:59:35 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199611152059.HAA27679@godzilla.zeta.org.au>
To: bde@zeta.org.au, terry@lambert.org
Subject: Re: Sockets question...
Cc: hackers@FreeBSD.org, jdp@polstra.com, jgreco@brasil.moneng.mei.com,
        scrappy@ki.net
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>> 	on system 1 with 32MB RAM: the kernel panics with a double fault
>
>This is, I think, expected behaviour for a page which is not present but
>for which a kmem mapping exists.  This happens because the /kernel file
>is mapped to /dev/kmem.

Not in FreeBSD.  /kernel is an ordinary, unmapped file.

>If you try this with a different file (one without an established mapping),
>what happens?

Same.  It was a bug in i586_copyout.

>
>> 	on system 2 with 8MB RAM: read returns -1.

This worked because it's an i486.  The memory size was irrelevant.  This
shows why everyone should include full information information in bug
reports.

Bruce