From owner-freebsd-questions@FreeBSD.ORG Sun Aug 19 06:23:39 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A94CF16A418 for ; Sun, 19 Aug 2007 06:23:39 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [66.92.130.199]) by mx1.freebsd.org (Postfix) with ESMTP id 61ED413C458 for ; Sun, 19 Aug 2007 06:23:39 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.1/8.14.1) with ESMTP id l7J6NZUE008311 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Sun, 19 Aug 2007 01:23:35 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <46C7E1E4.8010004@tundraware.com> Date: Sun, 19 Aug 2007 01:23:32 -0500 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: "failed to create swap_zone" 6.2-STABLE SMP Kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2007 06:23:39 -0000 I note that this problem has appeared in the past and am wondering if there is a resolution: Running 6.2-STABLE on a machine that ran 4.11 flawlessly. I am seeing the message "failed to create swap_zone" right after the 2nd CPU gets enabled on a Dell PowerEdge 1300. The system blows out and reboots therafter. This same configuration works fine on a more modern Intel MOBO with a Pentium D, so I'm guessing the problem is hardware dependent. Booting a generic kernel works fine on the PowerEdge. The source code is latest STABLE as of earlier today. Has anyone else seen this and/or is there a workaround? My exact kernel config is: include SMP options IPFIREWALL options IPDIVERT options VESA # System console options options SC_DISABLE_REBOOT # disable reboot key sequence options SC_HISTORY_SIZE=200 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode # The following options will change the default colors of syscons. options SC_NORM_ATTR="(FG_GREEN|BG_BLACK)" options SC_NORM_REV_ATTR="(FG_YELLOW|BG_GREEN)" options SC_KERNEL_CONS_ATTR="(FG_RED|BG_BLACK)" options SC_KERNEL_CONS_REV_ATTR="(FG_BLACK|BG_RED)" TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/