From owner-freebsd-bugs  Fri Jan 19 04:17:07 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA11425
          for bugs-outgoing; Fri, 19 Jan 1996 04:17:07 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA11415
          Fri, 19 Jan 1996 04:16:47 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id XAA03994; Fri, 19 Jan 1996 23:05:44 +1100
Date: Fri, 19 Jan 1996 23:05:44 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199601191205.XAA03994@godzilla.zeta.org.au>
To: gtc@aloft.att.com, jkh@time.cdrom.com
Subject: Re: panic: vm_bounce_alloc during initial installation (writing disk info)
Cc: bugs@freebsd.org, jkh@freebsd.org
Sender: owner-bugs@freebsd.org
Precedence: bulk

>> And my answer was yes - my partition size *is* just over 500MB.
>> The location of the partition, which might be significant, is at the end
>> of a 4GB disk.  If I recall, however, I believe the end of the partition was
>> just _under_ the 4GB boundary.

This may be caused by garbage block numbers in (or for) the extended
partition tables.  I think preposterously large values are caught
early enough but negative ones aren't.  Negative ones are unlikely
to causes as much damage as slightly wrong ones (which can't be
checked for) so it's not clear that they are worth checking.

Bruce