From owner-freebsd-current  Mon Nov 11 05:02:05 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA12494
          for current-outgoing; Mon, 11 Nov 1996 05:02:05 -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 FAA12488;
          Mon, 11 Nov 1996 05:01:59 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA12713; Mon, 11 Nov 1996 23:56:32 +1100
Date: Mon, 11 Nov 1996 23:56:32 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199611111256.XAA12713@godzilla.zeta.org.au>
To: current@freebsd.org
Subject: panic in kvtop for bad maddr
Cc: dyson@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I tried putting `bootdev' (0xa0500004 = some slice on sd0a) in npx0's
id_maddr.  This failed because kvtop() is called on id_maddr just to
print its physical address (after id_maddr has been converted from a
physical address to a virtual address).  The bug seems to be that
kvtop() only works for valid addresses and id_maddr is invalid if it
wasn't originally between 0xa0000 and 0xfffff.  Config and userconfig
don't restrict the address.

Bruce