From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 9 13:22:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9897416A41F for ; Tue, 9 Aug 2005 13:22:24 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D5C343D5A for ; Tue, 9 Aug 2005 13:22:24 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wproxy.gmail.com with SMTP id i22so1219562wra for ; Tue, 09 Aug 2005 06:22:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WP6onOm8xMzKaTLLrcwnlyUJcE1YWNRzSoPJG9GRREb1MpV2jqeKZxAhQap81a6Oam0zyLBYF6rxABJ85BLJFz54e+LevtPuknFGGfo/ZtzoEu3cH0F7hsqCTjQSoX7eZXXO02pIUmKR/04wvBPzjiFkgPJytcRS2Nx5yD2IRo8= Received: by 10.54.36.64 with SMTP id j64mr5505370wrj; Tue, 09 Aug 2005 06:22:23 -0700 (PDT) Received: by 10.54.144.11 with HTTP; Tue, 9 Aug 2005 06:22:23 -0700 (PDT) Message-ID: Date: Tue, 9 Aug 2005 15:22:23 +0200 From: Claus Guttesen To: Mialon Pierre-Gilles In-Reply-To: <200508091431.56773.pierre-gilles@netaktiv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200508091431.56773.pierre-gilles@netaktiv.com> Cc: freebsd-amd64@freebsd.org Subject: Re: No dual cpu on S 2882 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 13:22:24 -0000 > I try to use AMD64 on a heavy loaded web server, it always crashe= s when the > load grow up, with no signal, it just reboot... >=20 > What can I do to see it working ? Should I change to FreeBSD i386= ? The only > issue I found was to use only one cpu ... But this server needs both of = them > to work correctly ... >=20 > options SCHED_ULE # Improved scheduler Change this line to SCHED_4BSD instead. regards Claus