From owner-freebsd-bugs  Thu Jan 18 10:33:45 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA23928
          for bugs-outgoing; Thu, 18 Jan 1996 10:33:45 -0800 (PST)
Received: from gw2.att.com (gw2.att.com [192.20.239.134])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA23923
          Thu, 18 Jan 1996 10:33:42 -0800 (PST)
Received: from aloft.UUCP by ig1.att.att.com id AA24154; Thu, 18 Jan 96 13:31:01 EST
From: gtc@aloft.att.com (gary.corcoran)
To: gtc@aloft.att.com, jkh@time.cdrom.com
Cc: bugs@freebsd.org, jkh@freebsd.org
Received: from stargazer (stargazer.cnet.att.com) by aloft (4.1/DCS-aloft-M3.1)
	id AA13507; Thu, 18 Jan 96 13:32:36 EST
Received: by stargazer (4.1/DCS-aloft_client-S2.1)
	id AA08896; Thu, 18 Jan 96 13:32:34 EST
Date: Thu, 18 Jan 96 13:32:34 EST
Original-From: aloft!gtc (gary.corcoran)
Message-Id: <9601181832.AA08896@stargazer>
Original-To: aloft!gtc, time.cdrom.com!jkh
Subject: Re: panic: vm_bounce_alloc during initial installation (writing disk info)
Original-Cc: freebsd.org!bugs, freebsd.org!jkh
Sender: owner-bugs@freebsd.org
Precedence: bulk


Jordan,

Regarding:
=>when I go to commit the changes to disk, I immediately get the following error
=>message (as seen on the debug screen):
=>vm_bounce_alloc: b_bufsize(0x200) < b_bcount(0x1ff0a400) !!
=
=Can you tell me if this ever got resolved?  I'm alarmed somewhat at
=your 2 year tale of woe!

Thank you for not letting this fall through the cracks - since I hadn't
heard back anything after the intial couple of immediate replies, I was
afraid my problem was long forgotten...

But no - my vm_bounce_alloc panic problem during install never was resolved,
and I still haven't been able to install FreeBSD at all.  Back in November, I
received the following email from Bruce Evans, giving a clue to where the
problem might lie:

>This might be caused by a negative block number somehow being passed to
>dscheck().  If this happens, then "truncating" the i/o would actually
>expand the i/o to the size of the partition plus the absolute value of
>the negative block number.  Do you have a (BSD) partition of size
>approximately 0x1ff0a400 bytes (500+ MB)?  Negative block numbers are
>used by the file system code but are not supposed to reach device drivers.

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.

Yes, indeed it has been frustrating that during the past two years, on two
different PCs, I was never able to successfully install FreeBSD.  And this was
even _after_ I had bought the hardware to assemble my new PC *specifically* to
be compatible with what FreeBSD supported!  I'm looking forward to trying out
all the great stuff the FreeBSD community has written and/or ported to the
FreeBSD platform - once I can get it installed!!  :-)

So if someone out there can help me over this "hump", I'd really appreciate
it...   Oh - I just received a phone call from John Dyson, who said he would
try to look into (if he has the time).  Any and all help appreciated, since
(catch-22) I can't look into the problem myself until I get the system
installed...

Thanks,
Gary

gtc@aloft.att.com