Date: Thu, 09 Nov 95 18:16:19 -0500 From: "gary.corcoran" <gtc@aloft.att.com> To: bugs@freebsd.org, jkh@freebsd.org Subject: panic: vm_bounce_alloc during initial installation (writing disk info) Message-ID: <9511092316.AA11356@stargazer>
next in thread | raw e-mail | index | archive | help
I sent mail on this subject a few months ago (July) and never heard anything back on my report. We were having some email problems back then, so I don't know if my report never reached anyone - or - if you replied but I never received the reply. Nevertheless: I first saw this problem trying to install version 2.0.5, and I am still seeing the same problem when trying to install the latest 2.1 SNAP (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) !! and nothing gets written to the disk (I *am* glad it doesn't trash my disk!). Turning on the new "debug flag" did not yield any additional information. My environment is: Pentium 90 (AMI Titan II EISA/PCI motherboard, one CPU installed) BT946C BusLogic PCI bus-mastering SCSI controller Greater than 1GB disk translation enabled (out of necessity) 4G SCSI disk - using third DOS partition for FreeBSD 32MB memory I am a hacker and would try to track this down myself - but I'm in a catch-22 here: I can't edit and recompile the system until I get the system installed! So any help with this critical problem would be appreciated. I'll be happy to try any new versions you come up with that you think will address this problem. One of the problems may be that bounce buffers shouldn't really be used on my machine, given that I've got a 32-bit bus-mastering SCSI controller (this is probably related to kernel problem #378). But even if it does want to use bounce buffers during install "just to be safe", that's okay - but the panic is not... BTW - the installation program *does* find and identify my BT946C controller. Personal note: I've been trying to get FreeBSD installed on one of my machines for over two years now, and have never been successful! When I bought the hardware for my new Pentium machine, I specifically checked to make sure that the pieces (e.g. the SCSI controller) were currently supported by FreeBSD, and thought that installation would be a breeze with the "right" hardware! But of course, being a software practitioner myself, I know that code is never easy (that's why they call it CODE!). So, as you might presume by the fact that I'm *still* trying to install FreeBSD after more than two years, I *really* would like to get it going one of these days! I realize that all the development work for FreeBSD is "spare time" from volunteers, and that someone may not get around to fixing this "immediately". But I do consider this to be a "critical" problem (at least for me!) because I can't even get the system installed - and I must not be the only person seeing this problem... So, because of our recent unreliability of email, and the fact that this mail may not even be read until someone has some "spare time", I would appreciate at least a simple "ack" that a FreeBSD org. person has seen this email... Thank you! Gary Corcoran gtc@aloft.att.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9511092316.AA11356>