From owner-freebsd-questions Sat May 9 20:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07883 for freebsd-questions-outgoing; Sat, 9 May 1998 20:44:07 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from wna1.wna-linknet.com (root@wna1.wna-linknet.com [208.128.88.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07823 for ; Sat, 9 May 1998 20:43:58 -0700 (PDT) (envelope-from x5gb7uk9@wna-linknet.com) Received: from RED_DWARF (cust142.wna-linknet.com [208.128.88.142]) by wna1.wna-linknet.com (8.8.8/8.8.8) with SMTP id XAA26407 for ; Sat, 9 May 1998 23:43:55 -0400 (EDT) Message-ID: <35552188.21D5@wna-linknet.com> Date: Sat, 09 May 1998 22:39:52 -0500 From: "Arnold J. Rimmer" Reply-To: x5gb7uk9@wna-linknet.com Organization: Jupiter Mining Corporation X-Mailer: Mozilla 3.01Gold (WinNT; U) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: 64 meg bug Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i was/am running 2.2.2. i reconfig'd my kernal to add an ethernet card. after the reconig the box would not boot. i got a panic stating getnewbuf, inconsistent or empty quindex...then it would go to syncing disks 9 9 9 ... then go to auto reboot and repeat the cycle endlessly. a search of mailing list archives revealed this to be to so-called 64 meg bug. the suggested solution was to remove some ram. i did so (32 meg), and lo the problem is solved. question can: is there any other solution and, if i have MORE than 64 meg onboard will the problem recur? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message