From owner-freebsd-amd64@FreeBSD.ORG  Fri Oct 14 09:07:20 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: amd64@freebsd.org
Delivered-To: freebsd-amd64@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 37DAB16A41F;
	Fri, 14 Oct 2005 09:07:20 +0000 (GMT)
	(envelope-from jd@ugcs.caltech.edu)
Received: from hurl.ugcs.caltech.edu (hurl.ugcs.caltech.edu [131.215.176.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 870D243D46;
	Fri, 14 Oct 2005 09:07:19 +0000 (GMT)
	(envelope-from jd@ugcs.caltech.edu)
Received: by livecd.ugcs.caltech.edu (Postfix, from userid 3640)
	id 9916F1C3BAF; Wed, 12 Oct 2005 19:54:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by livecd.ugcs.caltech.edu (Postfix) with ESMTP
	id 83E5D1C3B98; Wed, 12 Oct 2005 19:54:45 -0700 (PDT)
Date: Wed, 12 Oct 2005 19:54:45 -0700 (PDT)
From: Jon Dama <jd@ugcs.caltech.edu>
To: freebsd-current@freebsd.org
Message-ID: <Pine.LNX.4.53.0510121947090.18368@hurl.ugcs.caltech.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: amd64@freebsd.org
Subject: [6.0b5/AMD64] ls /otherdir/devfs induces panic
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2005 09:07:20 -0000


The following sequence induces an instant panic:

1) machine just up, no load
2) mount_devfs devfs /test/dev
3) chroot /test /bin/sh
4) ls /dev
*PANIC*

panic: kmem_malloc(-1905729536): kmem_map too small: 6881290 total
allocated

Dumping 8191 MB (3 chunks)
  chunk 0: 1MB (156 pages)

   ( dump fails to finish )


Kernel: GENERIC AMD64 6.0 Beta 5


I am aware of the VM_KMEM_SIZE_MAX kernel setting, but thought I'd drop a
line on the list now because kmem_malloc(-1905729536) seems rather unusual
to me.

Thanks,

   Jon