From owner-freebsd-stable Fri Aug 30 0:52:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AFAB37B400 for ; Fri, 30 Aug 2002 00:52:48 -0700 (PDT) Received: from nextgeneration.speedroad.net (nextgeneration.speedroad.net [195.139.232.50]) by mx1.FreeBSD.org (Postfix) with SMTP id 0F52143E88 for ; Fri, 30 Aug 2002 00:52:32 -0700 (PDT) (envelope-from arnvid@karstad.org) Received: (qmail 3631 invoked by uid 1010); 30 Aug 2002 07:51:04 -0000 Received: from unknown (HELO ?192.168.0.119?) (213.236.217.67) by mail.speedroad.net with SMTP; 30 Aug 2002 07:51:04 -0000 Date: Fri, 30 Aug 2002 09:50:59 +0200 From: Arnvid Karstad To: freebsd-stable@freebsd.org Subject: Problems with FreeBSD - causing zalloc to return 0 ?! Organization: Int Message-Id: <20020830094151.41DC.ARNVID@karstad.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.04 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiya all, We've been troubled by "Fatal trap 12"'s for a little while now. The machine was running 4.6 perfectly, until I decided to try a cvs up to RELENG_4_6 about a week ago. Then it started to crash alot, we went back to RELENG_4. And there were no problems there. But then we decided to send in an error report http://www.freebsd.org/cgi/query-pr.cgi?pr=42046 and went back to RELENG_4_6.... After going through alot of testing, kernel testing, and other funny things we decided to end the testing and go back to RELENG_4... Voila... The problems where now resident in that CVS Tag also. We have found a working workaround by adding the following to the kernel config: options INVARIANTS options INVARIANT_SUPPORT running the kernel with GENERIC instead of our custom kernel makes the system panic alot faster. It would seem that zalloc return's 0 when it shouldn't be able to do that. There are more incidents like this at several other machines that were upgraded at the same time. Anyone know of a better workaround than using INVARIANTS? Mvh/Best regards, Arnvid L. Karstad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message