From owner-freebsd-current Wed Nov 15 19:38:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id D559137B479; Wed, 15 Nov 2000 19:38:29 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.0/8.11.0) with ESMTP id eAG3cTG72325; Wed, 15 Nov 2000 22:38:29 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200011160338.eAG3cTG72325@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: Does floppies work with 384MByte RAM ? References: <3822.974328625@critter> In-reply-to: Your message of "Wed, 15 Nov 2000 23:50:25 +0100." <3822.974328625@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Nov 2000 22:38:29 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have two reports about machines with 384MB RAM panicing when > the floppies are accessed. I don't have the message right now > except for a report that "it said something about bouncebuffers" I apologize for the vagueness of this response, but perhaps it might help shed some light. I've got a Dell dual-Pentium-III XEON system at work that I was running -current on. Some time ago (didn't notice when exactly, sigh) when building new kernels, I started getting isa_dmainit(foo, bar) failed messages during the booting process for both the fdc device as well as my CS423x sound device. A cursory examination revealed that this was while trying to allocate bounce buffers for both the floppy and sound device DMA channels. On a lark, I rebuilt a kernel with MAXMEM=(256*1024) (the system has 512M of memory installed), and the isa_dmainit() failures stopped happening. Recently, I installed 4.1.1-STABLE on this machine because, well, I needed a stable system and didn't need to track the -current bleeding edge. It's probably hard for me currently to reproduce this problem myself right now. I'd suggest the MAXMEM hack to see if this mirrors my experience. Certainly this system was working just fine until sometime around the SMPNG milestone; but I can't really attribute the failure to any particular change. Again, sorry for the lack of detail; hope this might provide a hint. louie > Can somebody with 384MB ram check if the floppy works under > current ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message