From owner-freebsd-hackers  Sat Aug 24 20:27:12 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA27763
          for hackers-outgoing; Sat, 24 Aug 1996 20:27:12 -0700 (PDT)
Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA27752;
          Sat, 24 Aug 1996 20:27:09 -0700 (PDT)
Received: (from tinguely@localhost) by plains.nodak.edu (8.7.5/8.7.3) id WAA26323; Sat, 24 Aug 1996 22:27:02 -0500 (CDT)
Date: Sat, 24 Aug 1996 22:27:02 -0500 (CDT)
From: Mark Tinguely <tinguely@plains.nodak.edu>
Message-Id: <199608250327.WAA26323@plains.nodak.edu>
To: FreeBSD-hackers@freebsd.org, dchapes@zeus.leitch.com
Subject: Re: kernel vm_page_alloc_contig() can indirectly cause kernel page faults
Cc: davidg@freebsd.org
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I reported this panic last summer when I started writing the Meteor driver.
THe work around I used wast to start the allocation starting at the
first Meg mark, at that time I speculated it was treating the low memory
and the first meg as being contiguous even though there is a memory
hole between them. Starting contiguous allocation at/after the first
meg never caused anymore panics, so I left it at that.

--mark.