From owner-freebsd-questions Sat May 9 21:01:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09532 for freebsd-questions-outgoing; Sat, 9 May 1998 21:01:25 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09507 for ; Sat, 9 May 1998 21:01:17 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA02676; Sat, 9 May 1998 20:55:45 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002670; Sun May 10 03:55:43 1998 Date: Sat, 9 May 1998 20:55:36 -0700 (PDT) From: Julian Elischer To: "Arnold J. Rimmer" cc: freebsd-questions@FreeBSD.ORG Subject: Re: 64 meg bug In-Reply-To: <35552188.21D5@wna-linknet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well an upgrade might help.. since 2.2.2 there has been 2.2.5 and 2.2.6 of course. On Sat, 9 May 1998, Arnold J. Rimmer wrote: > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message