Date: Sat, 11 Nov 95 16:24:14 EST From: gtc@aloft.att.com (gary.corcoran) To: bde@zeta.org.au, bugs@freebsd.org, gtc@aloft.att.com, jkh@freebsd.org Subject: Re: panic: vm_bounce_alloc during initial installation (writing disk info) Message-ID: <9511112124.AA01913@stargazer>
next in thread | raw e-mail | index | archive | help
Thanks for the reply. Regarding: >>(10/26 if I recall). When trying to perform the initial installation on my >>machine, after going through all the menus to partition and label the disk, >>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) !! > >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. I believe you're close to the problem: yes - my BSD partition size *is* a bit over 500MB. >Bounce buffers are used because the GENERIC config specifies them and >the `bt' driver handles all BusLogic devices from isa through pci using >much the same code - it requests bounce buffer support for all buses. Okay - that explains that. Thanks for the info. Gary gtc@aloft.att.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9511112124.AA01913>