From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 03:36:29 2005 Return-Path: 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 C041216A4CE; Sun, 1 May 2005 03:36:29 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5714D43D41; Sun, 1 May 2005 03:36:28 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.3/8.13.1/NinthNine) with SMTP id j413aKmZ015593; Sun, 1 May 2005 12:36:24 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 1 May 2005 12:36:20 +0900 (JST) Message-Id: <200505010336.j413aKmZ015593@sakura.ninth-nine.com> From: Norikatsu Shigemura To: Juergen Lock In-Reply-To: <20050430205349.A75283@saturn.kn-bremen.de> References: <20050427210405.A95072@saturn.kn-bremen.de> <20050428210246.A21966@saturn.kn-bremen.de> <200504281514.01411.jkim@niksun.com> <200504290313.18498.jkim@niksun.com> <20050429192851.A47512@saturn.kn-bremen.de> <200504300043.j3U0hAto009242@sakura.ninth-nine.com> <20050430205349.A75283@saturn.kn-bremen.de> X-Mailer: Sylpheed version 1.9.9 (GTK+ 2.6.7; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (sakura.ninth-nine.com [219.127.74.121]); Sun, 01 May 2005 12:36:26 +0900 (JST) cc: freebsd-emulation@FreeBSD.org cc: nork@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: nox@jelal.kn-bremen.de Subject: Re: please test qemu port update X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 03:36:29 -0000 On Sat, 30 Apr 2005 20:53:49 +0200 Juergen Lock wrote: > On Sat, Apr 30, 2005 at 09:43:10AM +0900, Norikatsu Shigemura wrote: > > On Fri, 29 Apr 2005 19:28:51 +0200 > > Juergen Lock wrote: > > > Any commiters here, or should i still send-pr? > > Please send-pr and Cc: nork@. I'll commit it. > Just did that. Oops, forgot to Cc you... > Sorry, No problem. I could catch it. Congratulations PR# 80486! This number is suitable for qemu:-). From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 10:38:33 2005 Return-Path: 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 5CCAD16A4CE for ; Sun, 1 May 2005 10:38:33 +0000 (GMT) Received: from ptb-relay01.plus.net (ptb-relay01.plus.net [212.159.14.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9F2443D31 for ; Sun, 1 May 2005 10:38:32 +0000 (GMT) (envelope-from oliver.schonrock@realtsp.com) Received: from [84.92.66.197] (helo=[192.168.0.12]) by ptb-relay01.plus.net with esmtp (Exim) id 1DSBqJ-0001WL-JL for freebsd-amd64@freebsd.org; Sun, 01 May 2005 11:38:31 +0100 Message-ID: <4274B1AC.80802@realtsp.com> Date: Sun, 01 May 2005 11:38:36 +0100 From: Oliver Schonrock User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FBSD 5.3 + amd64 + php + mysqli extension = segfault X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 10:38:33 -0000 Hi We run 4 FreeBSD servers now and have just built first FBSD server on AMD64. Everything went quite smoothly using the amd64 version of freebsd. until... I tried to use the mysqli extension in php5.0.4 on apache 1.3.33 connecting to mysql-server-4.1.11 (all built from cvsup'd ports tree). in php mysql_connect() works ok, but the mysql_fetch_array() segfaults. this simple php script produces the error every time (via apache or with command line binary): query('select * from user;'); while ($row = $result->fetch_array(MYSQLI_ASSOC)) { print_r($row); } ?> => Segmentation fault (core dumped) the php-mysql (note no 'i') extension works fine. system info: root@pakiri# uname -a FreeBSD pakiri.realtsp.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC amd64 I have reverted to a generic kernel to avoid any issues there (had previously built kernel without unneeded hardware support etc) We have exactly the same applications running on several i386 (AMD Athlon and Intel Pentium) servers. These do not segfault. I have tried de/reinstalling the mysql, php, mysqli builds in many different ways (incl not in combination with mysql extension)...no change. Does anyone have any experiience running FBSD 5.3 + amd64 + php5.0.4 + mysqli extension? Or have any suggestions of how to track this down further? Thanks in advance Oliver From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 11:53:15 2005 Return-Path: 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 1331116A4CE for ; Sun, 1 May 2005 11:53:15 +0000 (GMT) Received: from maltanet.net (mailer2.maltanet.net [194.158.37.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C33B43D1F for ; Sun, 1 May 2005 11:53:13 +0000 (GMT) (envelope-from peterk@maltanet.net) Received: (qmail 4125 invoked by uid 516); 1 May 2005 11:53:16 -0000 Received: from 195.158.85.42 by mailer2.maltanet.net (envelope-from , uid 509) with qmail-scanner-1.25st (perlscan: 1.25st. Clear:RC:1(195.158.85.42):. Processed in 0.313749 secs); 01 May 2005 11:53:16 -0000 Received: from unknown (HELO [195.158.85.42]) ([195.158.85.42]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 1 May 2005 11:53:16 -0000 Message-ID: <4274C324.7060401@maltanet.net> Date: Sun, 01 May 2005 13:53:08 +0200 From: Peter Korsten User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Asus A8N-SLI issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 11:53:15 -0000 Hi, I've been using FreeBSD on and off since version 2.something, but only recently I got an Asus A8N-SLI (not the Deluxe version) and installed 5.3 on it, from the link you get from the download page. There's the ACPI freeze problem, and I've found some references that this will be solved at a later stage. Fair enough. The thing that I wonder about, though, is why the Ethernet port does not get recognised. This is not the same as in the Deluxe version, where I believe there is a different controller from the nForce4 chipset. Oddly enough, it does recognise the nForce4 Firewire controller and proposes to do TCP/IP over it. Could this be an issue of the 'firewall' hardware that this board comes with? X isn't doing a lot either, but I've never found it easy to set that up, so I'll look some more into it. The S-ATA disc is recognised as UDMA33, but at least it knows the correct size of the disc, contrary to some OS from Washington state that I could mention. Thanks for any replies, - Peter From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 14:07:33 2005 Return-Path: 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 A54E516A4CE; Sun, 1 May 2005 14:07:33 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0FAD43D49; Sun, 1 May 2005 14:07:32 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.3/8.13.3) with ESMTP id j41E7WvT084287; Sun, 1 May 2005 10:07:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j41E7Wup088113; Sun, 1 May 2005 10:07:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id EDC8E7306E; Sun, 1 May 2005 10:07:31 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050501140731.EDC8E7306E@freebsd-current.sentex.ca> Date: Sun, 1 May 2005 10:07:31 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 14:07:33 -0000 TB --- 2005-05-01 12:18:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-05-01 12:18:21 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-05-01 12:18:21 - cleaning the object tree TB --- 2005-05-01 12:18:50 - checking out the source tree TB --- 2005-05-01 12:18:50 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-05-01 12:18:50 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-05-01 12:25:33 - building world (CFLAGS=-O2 -pipe) TB --- 2005-05-01 12:25:33 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-01 12:25:33 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-05-01 14:00:32 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-05-01 14:00:32 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-01 14:00:32 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun May 1 14:00:32 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffre estanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_sack.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffre estanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_subr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffre estanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_syncache.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffre estanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_timer.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffre estanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_usrreq.c /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_usrreq.c: In function `tcp_usr_send': /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_usrreq.c:757: error: syntax error before ':' token /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_usrreq.c:622: warning: unused variable `inirw' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-05-01 14:07:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-05-01 14:07:31 - ERROR: failed to build generic kernel TB --- 2005-05-01 14:07:31 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 15:04:16 2005 Return-Path: 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 6802C16A4CE for ; Sun, 1 May 2005 15:04:16 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id B46C543D4C for ; Sun, 1 May 2005 15:04:15 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id AFBDE300161E; Sun, 1 May 2005 15:25:00 +0200 (CEST) Message-ID: <4274D89B.1080102@mail.uni-mainz.de> Date: Sun, 01 May 2005 15:24:43 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050424) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Korsten References: <4274C324.7060401@maltanet.net> In-Reply-To: <4274C324.7060401@maltanet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de cc: freebsd-amd64@freebsd.org Subject: Re: Asus A8N-SLI issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 15:04:16 -0000 Peter Korsten wrote: > Hi, > > I've been using FreeBSD on and off since version 2.something, but only > recently I got an Asus A8N-SLI (not the Deluxe version) and installed > 5.3 on it, from the link you get from the download page. > > There's the ACPI freeze problem, and I've found some references that > this will be solved at a later stage. Fair enough. Can you obtain more specific informations? It is known that nForce4 based chipsets need the option NO_MIXED_MODE to be commented out in the kernel config file! Also you have to define device atpic to make the board properly work. #options NO_MIXED_MODE device atpic > > The thing that I wonder about, though, is why the Ethernet port does not > get recognised. This is not the same as in the Deluxe version, where I > believe there is a different controller from the nForce4 chipset. Oddly > enough, it does recognise the nForce4 Firewire controller and proposes > to do TCP/IP over it. Could this be an issue of the 'firewall' hardware > that this board comes with? The Deluxe-version of this mainboard has an additional Marvel NIC onboard in addition to the nVidia NIC. I guess the non-Deluxe version has only the nForce4-inherent NIC and this NIC is not yet supported by FBSD 5.4 but 6.0-CURRENT has a driver. > > X isn't doing a lot either, but I've never found it easy to set that up, > so I'll look some more into it. I run A8N-SLI Deluxe with a nVidia based 6600 chipset graphics card without problems. There is no acceleration, so expect good 'brute force' 2D performance, but poor 3D performance (due to lack of suitable drivers for amd64/FreeBSD). > > The S-ATA disc is recognised as UDMA33, but at least it knows the > correct size of the disc, contrary to some OS from Washington state that > I could mention. This is the same to me and it is due to the lack of a suitable driver. The kernel does report the controller as a GENERIC type and 'recognizes' the speed as UDMA33, but I do not know whether the hard disk is really driven as a UDMA33 device or is in contrary to the kernel report driven at full speed. Oliver From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 19:42:35 2005 Return-Path: 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 A418516A4CE for ; Sun, 1 May 2005 19:42:35 +0000 (GMT) Received: from ptb-relay01.plus.net (ptb-relay01.plus.net [212.159.14.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E73343D39 for ; Sun, 1 May 2005 19:42:35 +0000 (GMT) (envelope-from oliver.schonrock@realtsp.com) Received: from [84.92.66.197] (helo=[192.168.0.12]) by ptb-relay01.plus.net with esmtp (Exim) id 1DSKKo-0003JE-4n for freebsd-amd64@freebsd.org; Sun, 01 May 2005 20:42:34 +0100 Message-ID: <4275312F.8010800@realtsp.com> Date: Sun, 01 May 2005 20:42:39 +0100 From: Oliver Schonrock User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Fwd: Re: FreeBSD Port: php5-mysqli-5.0.4_1] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 19:42:35 -0000 furher information in reply to Uzi from ports maintainers. -------- Original Message -------- Subject: Re: FreeBSD Port: php5-mysqli-5.0.4_1 Date: Sun, 01 May 2005 16:14:59 +0100 From: Oliver Schonrock To: Uzi Klein CC: ports@freebsd.org References: <4274B75C.2010203@realtsp.com> <4274C11E.4020308@bmby.com> please see below: I apologise for the long email in advance. I have tried to provide information that is as complete as possible. Thanks very much for your help. Oliver Schonrock Uzi Klein wrote: > Oliver Schonrock wrote: > ... > >> Hi >> >> We run 4 FreeBSD servers now and have just built first FBSD server on >> AMD64. Everything went quite smoothly using the amd64 version of freebsd. >> >> until... >> >> I tried to use the mysqli extension in php5.0.4 on apache 1.3.33 >> connecting to mysql-server-4.1.11 (all built from cvsup'd ports tree). >> >> in php mysql_connect() works ok, but the mysql_fetch_array() segfaults. >> >> this simple php script produces the error every time (via apache or >> with command line binary): >> >> > >> $db = new mysqli('localhost', 'root', 'mysqlrootpw', 'mysql'); >> >> $result = $db->query('select * from user;'); >> >> while ($row = $result->fetch_array(MYSQLI_ASSOC)) >> { >> print_r($row); >> } >> >> ?> >> >> => Segmentation fault (core dumped) >> > > I have seen mysql 4.1x dies with queries that runs fine under 4.0x. > Could it be that? not really, since: a) out application/queries are running fine under 4.1.11 on i386 (Athlon and Pentium) hardware b) the trivial select query in the script above should be fine on either server. c) the query above runs fine when I use the mysql extension as in this script: oliver@pakiri$ cat phpmysqltest.php ... gives sensible output without errors. So that would indicate to me that the query is fine for the server, but may be causing the client library to crash when the data is retrieved with mysql_fetch_...(). Both php extensions (mysql and mysqli) are linked against the mysql41-client libraries as this shows: root@pakiri# cd /usr/ports/databases/mysql root@pakiri# make deinstall ===> Deinstalling for databases/mysql41-client ===> Deinstalling mysql-client-4.1.11_1 pkg_delete: package 'mysql-client-4.1.11_1' is required by these other packages and may not be deinstalled (but I'll delete it anyway): mysql-server-4.1.11_1 php5-mysql-5.0.4_1 php5-mysqli-5.0.4_1 pkg_delete: unable to completely remove directory '/usr/local/lib/mysql' pkg_delete: unable to completely remove directory '/usr/local/share/mysql' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) Anyway it is a requirement that both extensions (mysql and mysqli) use the same client libraries as stated here: http://uk.php.net/manual/en/ref.mysql.php and they won't build unless you are using the same client library for both as the makefile checks for this. So my current guess to the source of the problem is somewhere around where the php5-mysqli extension maps the mysql41-client api into php. Does that make sense to you given this info? > What application gives you the sig 11? is it apache or mysql? > > Please attach relevant log files etc. When I run the above script from the command line with: oliver@pakiri$ php phpmysqlitest.php I get the following in /var/log/messages: root@pakiri# tail -f messages May 1 16:27:45 pakiri kernel: pid 91764 (php), uid 1003: exited on signal 11 (core dumped) when I hit that script over the web via apache I get: May 1 16:27:54 pakiri kernel: pid 29441 (httpd), uid 80: exited on signal 11 So I looks like in either case that it is the php binary (or more precisely the php5-mysqli extension) that is causing the "signal 11". I hope this helps in diagnosis. Thanks again. From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 20:48:07 2005 Return-Path: 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 7223216A4CE for ; Sun, 1 May 2005 20:48:07 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5168F43D3F for ; Sun, 1 May 2005 20:48:07 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4A05772DEB; Sun, 1 May 2005 13:48:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 47A2B72DDB for ; Sun, 1 May 2005 13:48:07 -0700 (PDT) Date: Sun, 1 May 2005 13:48:07 -0700 (PDT) From: Doug White To: freebsd-amd64@freebsd.org Message-ID: <20050501134749.X3887@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Opteron deadlock fix committed X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 20:48:07 -0000 Hey folks, Yesterday I committed a workaround for a deadlock condition in RELENG_5 and RELENG_5_4 caused by errata in AMD Opteron and Athlon64 processors. (-CURRENT after April 8 is not affected due to changes in critical sections.) The deadlock appeared under heavy load, particularly with lots of I/O interrupts, in SMP environments on both FreeBSD/amd64 and FreeBSD/i386. Specifically, a spinwait as part of inter-processor TLB flushing triggered Errata 106, which causes the cache on the spinning processor to not update. To workaround the issue we enabled interrupts during the spinwait, which breaks the lock on the cache when an interrupt occurs. AMD also offers a workaround that the BIOS can implement, but not all systems have applied the errata. This workaround will appear in 5.4-RELEASE. In addition, I committed a KDB feature written by Stephen Uphoff (ups) to assist in debugging SMP situations where one processor is stuck with interrupts disabled. Since the regular cpustop IPI won't get through in that case, he implemented an NMI handler to perform the stop. This feature, compiled in with the kernel option KDB_STOP_NMI and activated by debug.kdb.stop_cpus_with_nmi, is available on all current branches and will ship with 5.4-RELEASE. If you have had problems with deadlock conditions on AMD processors in an SMP environment, we urge you to update to the latest RELENG_5, or try the upcoming 5.4-RC4. I want to thank the following individuals for their help in debugging and fixing the deadlock issue: Paul Vixie and Peter Losher at ISC Stephen Uphoff (ups) Alan Cox (alc) John Baldwin (jhb) The rest of the FreeBSD RE team -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 20:49:54 2005 Return-Path: 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 08D7616A4CE for ; Sun, 1 May 2005 20:49:54 +0000 (GMT) Received: from hook.org (dsl-hill-66-18-200-121-cgy.nucleus.com [66.18.200.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CDFD43D1F for ; Sun, 1 May 2005 20:49:53 +0000 (GMT) (envelope-from anselm@hook.org) Received: from webserver.computershop.ca (anselm@localhost [127.0.0.1]) by hook.org (8.12.6/8.12.6) with ESMTP id j41Km25x012986; Sun, 1 May 2005 13:48:02 -0700 (MST) Received: from localhost (anselm@localhost)j41Km1YV019862; Sun, 1 May 2005 13:48:01 -0700 (MST) Date: Sun, 1 May 2005 13:48:01 -0700 (MST) From: Anselm Hook X-X-Sender: To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: matt@offmyserver.com Subject: obsevations re 3 little issues incl. pamd authentication error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 20:49:54 -0000 This is just an observation of three issues or possible bugs in 5.3 stable amd64: 1) pamd authentication error on reinstall of base on freebsd amd64 5.3 I've noticed that if I install freebsd 5.3 stable amd64 from a cdrom, and then go to the sysinstall utility and re-install 'base' that ssh, telnet and other remote login tools stop working. They allow me to enter my password but never actually accept the login. Looking at /var/log/messages shows 'pam.d authentication error'. So my guess is that there is something different between the version of base that is supplied on the 5.3 stable cdrom, and the version of base that the sysinstall utility tries to fetch. And that this difference is possibly something to do with the tools that pam uses. I've run into this a couple of times - once with my server when it arrived from the vendor ( would not allow remote login ) and once just now (I had done a harddrive wipe and re-install of freebsd 5.3 stable amd64 and that had worked, but then later on attempting to install the source tree I had accidentally allowed base to be reinstalled and had managed to recreate the error again). 2) linux binary compat mode does not work as per documentation on amd64 5.3 freebsd on a stock install: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/linuxemu-lbc-install.html does not work. going to /usr/ports/emulators/linux_base-8 (or others) succeeds at all stages except the last - actual installation fails with 'command linux not found'. setting linux_enable=yes in rc.conf and rebooting also fails to show the linux.ko module being loaded ( kldstat does not show it ). i'd been led to believe it might work on amd64 because various sources said that 'linux can be built conveniently on amd64 by using the freebsd ports collection' - for example: http://people.freebsd.org/~tjr/linux32.html perhaps this is because i used the april 30 2005 version of ports linked directly on the freebsd/ports page rather than one supplied with the cdrom. 3) /stand/sysinstall refuses to load sources without installing base again http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html describes a process by which you can use the 'sysinstall' utility to fetch the kernel sources so that you can build a custom kernel. sysinstall refused to fetch the sources without fetching base, although base was already present. fetching base again corrupted the system (as described in bug 1 above). I'm just noting these things because they may be bugs and are little tarpits at the very least. - a From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 20:59:21 2005 Return-Path: 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 90CD316A4CE; Sun, 1 May 2005 20:59:21 +0000 (GMT) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B9E143D1F; Sun, 1 May 2005 20:59:21 +0000 (GMT) (envelope-from ray@redshift.com) Received: from workstation (216-228-19-21.dsl.redshift.com [216.228.19.21]) by outgoing.redshift.com (Postfix) with SMTP id 1E1D79709E; Sun, 1 May 2005 13:59:21 -0700 (PDT) Message-Id: <3.0.1.32.20050501135931.00b23ee0@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Sun, 01 May 2005 13:59:31 -0700 To: freebsd-amd64@freebsd.org From: ray@redshift.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: freebsd-hackers@freebsd.org Subject: AMD64 / EM64T X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 20:59:21 -0000 Hi List, I'm running a cluster over here (15 Xeon's) and need to put a couple of new master database servers on line. I've done some testing with FreeBSD/amd64 but aside from a small increase in performance, haven't really seen anything too dramatic (this is a single Supermicro Xeon 2.40 Ghz vs. a Dual Opteron 246 with a Tyan board). I guess my questions is two fold: 1. Does anyone have any feedback/experience as far as running FreeBSD/amd64 on a dual the Intel Xeon 64 bit EM64T setup? I have tried amd64 on the Opteron machine we have here and it seems to work okay, but it has not been in a production environment yet. I've also never tried it on the EM64T CPU's. Are the EM64T cpu's just as compatible with it as the AMD Opteron's? And are there any pros/cons vs. one or the other? 2. Is the AMD64 branch stable enough for production use or would it make more since to stick to i386 and run that on a faster (although probably not as fast) machine, and avoid 64 bit for the time being. I've heard mixed reviews from our hardware vendor regarding enterprise sites which have jumped on the 64 bit bandwagon too soon and regretted it. If anyone has any feelings or comments as far as if the amd64 works well on the EM64T CPU's and/or if the general consensus is that the AMD64 branch is as stable and production ready as the i386 branch - I would certainly enjoy hearing comments/suggestions from members of the list. For me, I'm not looking to squeeze every possible ounce of performance out of the machines - stability is the first priority, then speed (as much as possible while staying with something fairly standard and tested) is the next concern. Thanks! Ray cc: cross post to hackers as well... I know, I know... :) From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 21:15:27 2005 Return-Path: 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 52FF916A4CE for ; Sun, 1 May 2005 21:15:27 +0000 (GMT) Received: from bgo1smout1.broadpark.no (bgo1smout1.broadpark.no [217.13.4.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id C753643D2F for ; Sun, 1 May 2005 21:15:26 +0000 (GMT) (envelope-from des@des.no) Received: from bgo1sminn1.broadpark.no ([217.13.4.93]) by bgo1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFT006PBXG3MP60@bgo1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 01 May 2005 23:09:39 +0200 (CEST) Received: from dsa.des.no ([80.203.228.37]) by bgo1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IFT00HDUXR7A960@bgo1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 01 May 2005 23:16:19 +0200 (CEST) Received: by dsa.des.no (Pony Express, from userid 666) id 1D17145535; Sun, 01 May 2005 23:15:25 +0200 (CEST) Received: from xps.des.no (xps.des.no [10.0.0.12]) by dsa.des.no (Pony Express) with ESMTP id A0EF8453D1; Sun, 01 May 2005 23:15:20 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 798B733C39; Sun, 01 May 2005 23:15:20 +0200 (CEST) Date: Sun, 01 May 2005 23:15:20 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) In-reply-to: To: Anselm Hook Message-id: <86mzre8x7b.fsf@xps.des.no> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dsa.des.no References: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.0.2 X-Spam-Level: cc: matt@offmyserver.com cc: freebsd-amd64@freebsd.org Subject: Re: obsevations re 3 little issues incl. pamd authentication error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 21:15:27 -0000 Anselm Hook writes: > I've noticed that if I install freebsd 5.3 stable amd64 from a cdrom, and > then go to the sysinstall utility and re-install 'base' that ssh, telnet > and other remote login tools stop working. They allow me to enter my > password but never actually accept the login. Looking at > /var/log/messages shows 'pam.d authentication error'. reinstalling 'base' overwrites your password database. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 21:20:30 2005 Return-Path: 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 8985016A4CE for ; Sun, 1 May 2005 21:20:30 +0000 (GMT) Received: from hook.org (dsl-hill-66-18-200-121-cgy.nucleus.com [66.18.200.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 290CA43D2D for ; Sun, 1 May 2005 21:20:30 +0000 (GMT) (envelope-from anselm@hook.org) Received: from webserver.computershop.ca (anselm@localhost [127.0.0.1]) by hook.org (8.12.6/8.12.6) with ESMTP id j41LIR5x021757; Sun, 1 May 2005 14:18:27 -0700 (MST) Received: from localhost (anselm@localhost)j41LIRZA011026; Sun, 1 May 2005 14:18:27 -0700 (MST) Date: Sun, 1 May 2005 14:18:26 -0700 (MST) From: Anselm Hook X-X-Sender: To: =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <86mzre8x7b.fsf@xps.des.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: matt@offmyserver.com cc: freebsd-amd64@freebsd.org Subject: Re: obsevations re 3 little issues incl. pamd authentication error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 21:20:30 -0000 Sorry, I should have clarified that even after re-creating accounts from the console - remote ssh logins were not allowed ( nor ssh username@localhost for that matter ). Something 'changes' - and pamd absolutely no longer works after overlaying base on top of the version provided from the cdrom. Also, I should clarify that I did not disable remote login for root or other users. - a On Sun, 1 May 2005, [iso-8859-1] Dag-Erling Sm=F8rgrav wrote: > Anselm Hook writes: > > I've noticed that if I install freebsd 5.3 stable amd64 from a cdrom, a= nd > > then go to the sysinstall utility and re-install 'base' that ssh, telne= t > > and other remote login tools stop working. They allow me to enter my > > password but never actually accept the login. Looking at > > /var/log/messages shows 'pam.d authentication error'. > > reinstalling 'base' overwrites your password database. > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > > From owner-freebsd-amd64@FreeBSD.ORG Sun May 1 22:06:16 2005 Return-Path: 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 DA42516A4CE for ; Sun, 1 May 2005 22:06:16 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA57F43D1D for ; Sun, 1 May 2005 22:06:16 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C73FF51432; Sun, 1 May 2005 15:06:15 -0700 (PDT) Date: Sun, 1 May 2005 15:06:14 -0700 From: Kris Kennaway To: amd64@FreeBSD.org Message-ID: <20050501220614.GA50235@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: 32GB/device swap limit on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 22:06:17 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Looks like amd64 has the following limit, which is the same as on i386: WARNING: reducing size to maximum of 67108864 blocks per swap unit Can this be easily fixed on amd64? Kris --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCdVLVWry0BWjoQKURAn6tAKCkXTIDwEWASnMQxwEMZFE9Ywo8pwCg/Vgd dh2nuJpEaN7YIFWF7McnEn0= =WJu+ -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 07:42:29 2005 Return-Path: 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 EDCB516A4CE; Mon, 2 May 2005 07:42:29 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF06F43D1D; Mon, 2 May 2005 07:42:29 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 8ED3A2A8DA; Mon, 2 May 2005 00:42:29 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 27E80E2B3; Mon, 2 May 2005 00:42:29 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.3/8.13.1) with ESMTP id j427gSGo014947; Mon, 2 May 2005 00:42:28 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.3/8.13.1/Submit) id j427gMcW014946; Mon, 2 May 2005 00:42:22 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Mon, 2 May 2005 00:42:22 -0700 User-Agent: KMail/1.8 References: <20050501220614.GA50235@xor.obsecurity.org> In-Reply-To: <20050501220614.GA50235@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505020042.22898.peter@wemm.org> cc: amd64@freebsd.org cc: Kris Kennaway Subject: Re: 32GB/device swap limit on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 07:42:30 -0000 On Sunday 01 May 2005 03:06 pm, Kris Kennaway wrote: > Looks like amd64 has the following limit, which is the same as on > i386: > > WARNING: reducing size to maximum of 67108864 blocks per swap unit > > Can this be easily fixed on amd64? > > Kris This looks like its a subr_blist.c problem: /* * If we go beyond this, we get overflows in the radix * tree bitmap code. */ mblocks = 0x40000000 / BLIST_META_RADIX; if (nblks > mblocks) { printf("WARNING: reducing size to maximum of %lu blocks per swap unit\n", mblocks); nblks = mblocks; } sys/blist.h:#define BLIST_META_RADIX 16 -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 07:42:29 2005 Return-Path: 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 EDCB516A4CE; Mon, 2 May 2005 07:42:29 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF06F43D1D; Mon, 2 May 2005 07:42:29 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 8ED3A2A8DA; Mon, 2 May 2005 00:42:29 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 27E80E2B3; Mon, 2 May 2005 00:42:29 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.3/8.13.1) with ESMTP id j427gSGo014947; Mon, 2 May 2005 00:42:28 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.3/8.13.1/Submit) id j427gMcW014946; Mon, 2 May 2005 00:42:22 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Mon, 2 May 2005 00:42:22 -0700 User-Agent: KMail/1.8 References: <20050501220614.GA50235@xor.obsecurity.org> In-Reply-To: <20050501220614.GA50235@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505020042.22898.peter@wemm.org> cc: amd64@freebsd.org cc: Kris Kennaway Subject: Re: 32GB/device swap limit on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 07:42:30 -0000 On Sunday 01 May 2005 03:06 pm, Kris Kennaway wrote: > Looks like amd64 has the following limit, which is the same as on > i386: > > WARNING: reducing size to maximum of 67108864 blocks per swap unit > > Can this be easily fixed on amd64? > > Kris This looks like its a subr_blist.c problem: /* * If we go beyond this, we get overflows in the radix * tree bitmap code. */ mblocks = 0x40000000 / BLIST_META_RADIX; if (nblks > mblocks) { printf("WARNING: reducing size to maximum of %lu blocks per swap unit\n", mblocks); nblks = mblocks; } sys/blist.h:#define BLIST_META_RADIX 16 -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 07:50:02 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F64916A4CE for ; Mon, 2 May 2005 07:50:02 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D2943D3F for ; Mon, 2 May 2005 07:50:02 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j427o2oc093101 for ; Mon, 2 May 2005 07:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j427o1Q0093100; Mon, 2 May 2005 07:50:01 GMT (envelope-from gnats) Resent-Date: Mon, 2 May 2005 07:50:01 GMT Resent-Message-Id: <200505020750.j427o1Q0093100@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Adam Gregoire" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F29916A4CE for ; Mon, 2 May 2005 07:49:27 +0000 (GMT) Received: from mail.psychoholics.org (www.psychoholics.org [64.185.102.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C37B43D46 for ; Mon, 2 May 2005 07:49:27 +0000 (GMT) (envelope-from ebola@psychoholics.org) Received: from S010600deadc0de00 (S010600deadc0de00.su.shawcable.net [24.109.50.181]) by mail.psychoholics.org (Postfix) with ESMTP id 0FBF8157173 for ; Mon, 2 May 2005 02:25:15 -0700 (PDT) Message-Id: <1115020166.0@S010600deadc0de00> Date: Mon, 2 May 2005 03:49:26 -0400 From: "Adam Gregoire" To: "FreeBSD gnats submit" X-Send-Pr-Version: gtk-send-pr 0.4.5 Subject: amd64/80527: Jamboree fails to compile(linking with dbus) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 07:50:02 -0000 >Number: 80527 >Category: amd64 >Synopsis: Jamboree fails to compile(linking with dbus) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon May 02 07:50:01 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Adam Gregoire >Release: FreeBSD 6.0-CURRENT amd64 >Organization: >Environment: System: FreeBSD 6.0-CURRENT #71: Sun May 1 04:24:04 EDT 2005 root@S010600deadc0de00:/usr/obj/usr/src/sys/OPTMZD >Description: cc -O2 -fno-strict-aliasing -pipe -march=athlon64 -o jamboree player.o expr.o limiter.o main.o main-window.o song.o source-model.o source-view.o stock-icons.o utils.o volume-button.o eggtreemultidnd.o gsequence.o string-utils.o source.o source-database.o source-proxy.o source-playlist.o source-smart-playlist.o sources-view.o sources-xml.o smart-playlist-dialog.o tag-reader.o bacon-message-connection.o jamboree-marshal.o dbus.o -Wl,--export-dynamic -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/lib -L/usr/X11R6/lib -pthread -lgtk-x11-2.0 -lgnomeui-2 -lSM -lICE -lglade-2.0 -lesd -lgstreamer-0.8 -lgstcontrol-0.8 -lgstgconf-0.8 -ldbus-1 -ldbus-glib-1 -lgdbm dbus.o(.text+0x5b): In function `jamboree_dbus_init_service': : undefined reference to `dbus_bus_acquire_service' dbus.o(.text+0x4aa): In function `message_append_song': : undefined reference to `dbus_message_append_iter_init' dbus.o(.text+0x4b7): In function `message_append_song': : undefined reference to `dbus_message_iter_append_dict' dbus.o(.text+0x4c6): In function `message_append_song': : undefined reference to `dbus_message_iter_append_dict_key' dbus.o(.text+0x4db): In function `message_append_song': : undefined reference to `dbus_message_iter_append_string' dbus.o(.text+0x4ea): In function `message_append_song': : undefined reference to `dbus_message_iter_append_dict_key' dbus.o(.text+0x4ff): In function `message_append_song': : undefined reference to `dbus_message_iter_append_string' dbus.o(.text+0x50e): In function `message_append_song': : undefined reference to `dbus_message_iter_append_dict_key' dbus.o(.text+0x523): In function `message_append_song': : undefined reference to `dbus_message_iter_append_string' dbus.o(.text+0x532): In function `message_append_song': : undefined reference to `dbus_message_iter_append_dict_key' dbus.o(.text+0x546): In function `message_append_song': : undefined reference to `dbus_message_iter_append_int32' gmake[2]: *** [jamboree] Error 1 gmake[2]: Leaving directory `/usr/ports/audio/jamboree/work/jamboree-0.5/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/audio/jamboree/work/jamboree-0.5' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/audio/jamboree. *** Error code 1 Stop in /usr/ports/audio/jamboree. >How-To-Repeat: Compile Jamboree on amd64(others?). >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 10:38:02 2005 Return-Path: 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 1186516A4CE for ; Mon, 2 May 2005 10:38:02 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60EEB43D49 for ; Mon, 2 May 2005 10:38:01 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by zproxy.gmail.com with SMTP id 34so2264723nzf for ; Mon, 02 May 2005 03:38:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=g+FsClPgiGEoVtvLy43wOM5CJkfoT5kge3d6bFhQqHSz71s5/z4N4CimAUTxBO7PZWuLYDik62ExDzNJcSj9rKz36Js3iuCpJwEYGSlidu4Yq3nlaefacIHETXCd+Rnv/JGZFnqR3Gx8Foy+WPrRwyce4/Zt72b1f4TW6xMwr38= Received: by 10.36.9.6 with SMTP id 6mr507544nzi; Mon, 02 May 2005 03:38:01 -0700 (PDT) Received: by 10.36.68.7 with HTTP; Mon, 2 May 2005 03:38:01 -0700 (PDT) Message-ID: <28edec3c050502033811804428@mail.gmail.com> Date: Mon, 2 May 2005 18:38:01 +0800 From: "Mars G. Miro" To: freebsd-emulation@freebsd.org, freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Recent qemu port still doesn't build on amd64, SMB dependency? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Mars G. Miro" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 10:38:02 -0000 Bombs in here: gmake[1]: Entering directory `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' gcc34 -Wall -O2 -g -fno-strict-aliasing -I. -I/usr/ports/emulators/qemu/work/qemu-0.7.0/target-i386 -I/usr/ports/emulators/qemu/work/qemu-0.7.0 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE -DSMBD=3D\"/usr/local/sbin/smbd\" -I/usr/ports/emulators/qemu/work/qemu-0.7.0/fpu -I/usr/ports/emulators/qemu/work/qemu-0.7.0/slirp -c -o vl.o /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c In file included from /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat.h:394, from /usr/ports/emulators/qemu/work/qemu-0.7.0/target-i386/cpu.h:41, from /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.h:73, from /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:24: /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:39: error: `FE_RM' undeclared here (not in a function) /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:39: error: enumerator value for `float_round_down' not integer constant /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:40: error: `FE_RP' undeclared here (not in a function) /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:40: error: enumerator value for `float_round_up' not integer constant /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:42: error: `FE_RZ' undeclared here (not in a function) /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:42: error: enumerator value for `float_round_to_zero' not integer constant /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: In function `init_timers': /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:982: warning: label `use_itimer' defined but not used /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: In function `loadmodules': /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:1622: warning: implicit declaration of function `kldload' /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: At top level: /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:910: warning: 'start_rtc_timer' defined but not used gmake[1]: *** [vl.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' gmake: *** [all] Error 1 *** Error code 2 Stop in /usr/ports/emulators/qemu. tart_rtc_timer' defined but not used gmake[1]: *** [vl.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' gmake: *** [all] Error 1 *** Error code 2 Stop in /usr/ports/emulators/qemu. I'm guessing it's qemu's hard dependency on samba, yes? I'll see if installing samba makes it not bomb. Matsalams ;-) cheers mars From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 11:01:50 2005 Return-Path: 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 8734916A4DB for ; Mon, 2 May 2005 11:01:50 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC2843D45 for ; Mon, 2 May 2005 11:01:50 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j42B1okj030163 for ; Mon, 2 May 2005 11:01:50 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j42B1nWc030156 for freebsd-amd64@freebsd.org; Mon, 2 May 2005 11:01:49 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 2 May 2005 11:01:49 GMT Message-Id: <200505021101.j42B1nWc030156@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 11:01:50 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh 24 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/13] ports/75015 amd64 cvsup on amd64 with runsocks (socks5) cor o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 o [2005/02/13] amd64/77470 amd64 Using of cyrillic filenames conversion le o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/02] amd64/80527 amd64 Jamboree fails to compile(linking with db 12 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 18:25:28 2005 Return-Path: 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 4773516A4CE for ; Mon, 2 May 2005 18:25:28 +0000 (GMT) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10B4043D1D for ; Mon, 2 May 2005 18:25:28 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13880 invoked from network); 2 May 2005 18:25:27 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 2 May 2005 18:25:27 -0000 Received: from [10.50.41.242] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j42IPMDm085629; Mon, 2 May 2005 14:25:22 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 2 May 2005 14:04:29 -0400 User-Agent: KMail/1.8 References: <20050501134749.X3887@carver.gumbysoft.com> In-Reply-To: <20050501134749.X3887@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505021404.30212.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: Opteron deadlock fix committed X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 18:25:28 -0000 On Sunday 01 May 2005 04:48 pm, Doug White wrote: > Hey folks, > > Yesterday I committed a workaround for a deadlock condition in RELENG_5 > and RELENG_5_4 caused by errata in AMD Opteron and Athlon64 processors. > (-CURRENT after April 8 is not affected due to changes in critical > sections.) Actually, current is still busted because even though critical sections don't disable interrupts, spin locks still do, and we do the spin loop in the TLB shootdowns with the smp_ipi_mtx spin lock held. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon May 2 22:09:40 2005 Return-Path: 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 D12E816A4CE; Mon, 2 May 2005 22:09:40 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B3E43D39; Mon, 2 May 2005 22:09:39 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j42MAPmd071196; Mon, 2 May 2005 18:10:26 -0400 (EDT) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, "Mars G. Miro" Date: Mon, 2 May 2005 18:09:25 -0400 User-Agent: KMail/1.6.2 References: <28edec3c050502033811804428@mail.gmail.com> In-Reply-To: <28edec3c050502033811804428@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200505021809.25799.jkim@niksun.com> X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on anuket.mj.niksun.com X-Virus-Status: Clean cc: freebsd-emulation@freebsd.org Subject: Re: Recent qemu port still doesn't build on amd64, SMB dependency? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 22:09:41 -0000 On Monday 02 May 2005 06:38 am, Mars G. Miro wrote: > Bombs in here: > gmake[1]: Entering directory > `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' > gcc34 -Wall -O2 -g -fno-strict-aliasing -I. > -I/usr/ports/emulators/qemu/work/qemu-0.7.0/target-i386 > -I/usr/ports/emulators/qemu/work/qemu-0.7.0 -D_GNU_SOURCE > -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE > -DSMBD=\"/usr/local/sbin/smbd\" > -I/usr/ports/emulators/qemu/work/qemu-0.7.0/fpu > -I/usr/ports/emulators/qemu/work/qemu-0.7.0/slirp -c -o vl.o > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c > In file included from > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat.h:394, > from > /usr/ports/emulators/qemu/work/qemu-0.7.0/target-i386/cpu.h:41, > from > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.h:73, from > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:24: > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:39 >: error: `FE_RM' undeclared here (not in a function) > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:39 >: error: enumerator value for `float_round_down' not integer > constant > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:40 >: error: `FE_RP' undeclared here (not in a function) > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:40 >: error: enumerator value for `float_round_up' not integer constant > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:42 >: error: `FE_RZ' undeclared here (not in a function) > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:42 >: error: enumerator value for `float_round_to_zero' not integer > constant /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: In > function `init_timers': > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:982: warning: label > `use_itimer' defined but not used > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: In function > `loadmodules': /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:1622: > warning: implicit declaration of function `kldload' > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: At top level: > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:910: warning: > 'start_rtc_timer' defined but not used > gmake[1]: *** [vl.o] Error 1 > gmake[1]: Leaving directory > `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' > gmake: *** [all] Error 1 > *** Error code 2 > > Stop in /usr/ports/emulators/qemu. > tart_rtc_timer' defined but not used > gmake[1]: *** [vl.o] Error 1 > gmake[1]: Leaving directory > `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' > gmake: *** [all] Error 1 > *** Error code 2 > > Stop in /usr/ports/emulators/qemu. > > I'm guessing it's qemu's hard dependency on samba, yes? > > I'll see if installing samba makes it not bomb. Actually there are two missing patches, namely patch-fbsd and patch-libmath from the original PR. You can get them from the PR itself. http://docs.freebsd.org/cgi/mid.cgi?200504301849.j3UIng675264 FYI, committer's aware of the issue already. Jung-uk Kim > Matsalams ;-) > > > > cheers > mars From owner-freebsd-amd64@FreeBSD.ORG Tue May 3 18:27:57 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A886316A4CE; Tue, 3 May 2005 18:27:57 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5286143D46; Tue, 3 May 2005 18:27:57 +0000 (GMT) (envelope-from arved@FreeBSD.org) Received: from freefall.freebsd.org (arved@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j43IRond043662; Tue, 3 May 2005 18:27:50 GMT (envelope-from arved@freefall.freebsd.org) Received: (from arved@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j43IRouC043658; Tue, 3 May 2005 18:27:50 GMT (envelope-from arved) Date: Tue, 3 May 2005 18:27:50 GMT From: Tilman Linneweh Message-Id: <200505031827.j43IRouC043658@freefall.freebsd.org> To: arved@FreeBSD.org, freebsd-amd64@FreeBSD.org, jylefort@FreeBSD.org Subject: Re: ports/80527: Jamboree fails to compile(linking with dbus) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 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, 03 May 2005 18:27:57 -0000 Synopsis: Jamboree fails to compile(linking with dbus) Responsible-Changed-From-To: freebsd-amd64->jylefort Responsible-Changed-By: arved Responsible-Changed-When: Tue May 3 18:27:14 GMT 2005 Responsible-Changed-Why: Over to maintainer http://www.freebsd.org/cgi/query-pr.cgi?pr=80527 From owner-freebsd-amd64@FreeBSD.ORG Tue May 3 20:48:44 2005 Return-Path: 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 5998616A4CF for ; Tue, 3 May 2005 20:48:44 +0000 (GMT) Received: from hotmail.com (bay16-f36.bay16.hotmail.com [65.54.186.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 325FA43D49 for ; Tue, 3 May 2005 20:48:44 +0000 (GMT) (envelope-from clcchu@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 3 May 2005 13:48:54 -0700 Message-ID: Received: from 210.6.198.238 by by16fd.bay16.hotmail.msn.com with HTTP; Tue, 03 May 2005 20:48:53 GMT X-Originating-IP: [210.6.198.238] X-Originating-Email: [clcchu@hotmail.com] X-Sender: clcchu@hotmail.com From: "Clarence Chu" To: freebsd-amd64@FreeBSD.org Date: Wed, 04 May 2005 04:48:53 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 03 May 2005 20:48:54.0434 (UTC) FILETIME=[84EF3820:01C55021] Subject: Any LiveCD of freebsd/x86_64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 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, 03 May 2005 20:48:44 -0000 am just curious if there's any liveCD of freebsd/x86_64 to test whether a box is capable of running freebsd/x86_64 instead of having the system to be installed. if there's such a beast, please kindly let me know of any download URL. at best it includes X11, jdk1.5.0p1_1, audio drivers and be compatible with both amd64 and em64t. that should save us a lot of time in hunting for compatible mainboards, display drivers, network drivers, em64t/amd64 compatibility of jdk-1.5.0, etc. best wishes, clarence chu _________________________________________________________________ FREE Pocket Business English, ACT NOW! http://www.linguaphonegroup.com/BannerTrack.asp?EMSCode=MSN03-08ETFJ-0211E From owner-freebsd-amd64@FreeBSD.ORG Wed May 4 00:37:00 2005 Return-Path: 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 2D2BE16A4D4 for ; Wed, 4 May 2005 00:37:00 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3738F43D72 for ; Wed, 4 May 2005 00:36:59 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id B3A3778C64 for ; Tue, 3 May 2005 20:39:18 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63160-02 for ; Tue, 3 May 2005 20:39:15 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id DECEC78C72 for ; Tue, 3 May 2005 20:39:14 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id B1B1133C60; Tue, 3 May 2005 20:37:06 -0400 (EDT) Date: Tue, 3 May 2005 20:37:06 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050504003706.GM20610@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: Any LiveCD of freebsd/x86_64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 00:37:00 -0000 Thus spake Clarence Chu (clcchu@hotmail.com) [03/05/05 16:51]: : and be compatible with both amd64 and em64t. that should save us : a lot of time in hunting for compatible mainboards, display drivers, network : drivers, em64t/amd64 compatibility of jdk-1.5.0, etc. I can't say much on the rest of your request, but it seems that everyone who's run java/jdk15 has done so with some difficulty in compiling, but smashing success once it gets going. I myself haven't had a single problem with it, though I only use it lightly on a daily basis. - Damian From owner-freebsd-amd64@FreeBSD.ORG Wed May 4 08:09:43 2005 Return-Path: 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 AF6DE16A4CE for ; Wed, 4 May 2005 08:09:43 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8797743D58 for ; Wed, 4 May 2005 08:09:43 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 660A1F1944 for ; Wed, 4 May 2005 01:09:04 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00717-03 for ; Wed, 4 May 2005 01:09:03 -0700 (PDT) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 2862DF193E for ; Wed, 4 May 2005 01:09:03 -0700 (PDT) From: Sean McNeil To: amd64@freebsd.org Content-Type: text/plain Date: Wed, 04 May 2005 01:09:02 -0700 Message-Id: <1115194142.2110.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: CD burning broken again (crash) on 5.4-STABLE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 08:09:43 -0000 Not sure when this broke again, but I am getting a panic when I try to use nautilus cd burner again: May 3 23:45:05 server kernel: Fatal trap 9: general protection fault while in kernel mode May 3 23:45:05 server kernel: instruction pointer = 0x8:0xffffffff801fb919 May 3 23:45:05 server kernel: stack pointer = 0x10:0xffffffffb1b71b80 May 3 23:45:05 server kernel: frame pointer = 0x10:0xffffffffb1b71bb0 May 3 23:45:05 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b May 3 23:45:05 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 May 3 23:45:05 server kernel: processor eflags = interrupt enabled, resume, IOPL = 0 May 3 23:45:05 server kernel: current process = 6 (thread taskq) May 3 23:45:05 server kernel: trap number = 9 May 3 23:45:05 server kernel: panic: general protection fault May 3 23:45:05 server kernel: KDB: enter: panic May 3 23:45:05 server kernel: ... kernel.debug shows: (gdb) l *0xffffffff801fb919 0xffffffff801fb919 is in ata_completed (/usr/src/sys/dev/ata/ata-queue.c:401). 396 397 ATA_DEBUG_RQ(request, "completed callback/wakeup"); 398 399 /* get results back to the initiator */ 400 if (request->callback) 401 (request->callback)(request); 402 else 403 sema_post(&request->done); 404 405 ata_start(ch); From owner-freebsd-amd64@FreeBSD.ORG Wed May 4 14:37:23 2005 Return-Path: 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 DE3E016A4CE for ; Wed, 4 May 2005 14:37:23 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78C6143D7E for ; Wed, 4 May 2005 14:37:23 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DTKzp-0002s4-1w for amd64@freebsd.org; Wed, 04 May 2005 17:37:05 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 May 2005 17:37:04 +0300 From: Danny Braniss Message-ID: Subject: EM64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 14:37:24 -0000 Hi, Im trying to boot an Intel/Blade/EM64, and it's panicking very early in the boot with: ... stopped at resource_list_find+0xb: cmpl %esi,0xb(%rax) now, since the keyboard is USB, i can't do much :-( any way i can get the USB keyboard working? or better, get it to finish booting? similar problems with 5.4 (for x86). any From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 01:13:53 2005 Return-Path: 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 3F8C116A4CE for ; Thu, 5 May 2005 01:13:53 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE3A43D4C for ; Thu, 5 May 2005 01:13:52 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by zproxy.gmail.com with SMTP id 34so68001nzf for ; Wed, 04 May 2005 18:12:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rusaDci4m2Fu9VRuKyGGS+cf4PmSOmahZwUpGYIR/uqS4bTrW1c/j/OZOesCGlq/dfTBuhwRxyXq+ANvSpTCM3woI/4C+bBrIHFIIQhRFfP7imf+AuJzPzcdQ9sRRKse4cMvwK+Kde7ZUUXRvLIpilsIHZXBJQ2s7c0PDezlNs0= Received: by 10.36.8.17 with SMTP id 17mr269558nzh; Wed, 04 May 2005 17:46:13 -0700 (PDT) Received: by 10.36.68.7 with HTTP; Wed, 4 May 2005 17:46:12 -0700 (PDT) Message-ID: <28edec3c05050417466ba52c16@mail.gmail.com> Date: Thu, 5 May 2005 08:46:12 +0800 From: "Mars G. Miro" To: Jung-uk Kim , nork@freebsd.org In-Reply-To: <200505021809.25799.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <28edec3c050502033811804428@mail.gmail.com> <200505021809.25799.jkim@niksun.com> cc: freebsd-emulation@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Recent qemu port still doesn't build on amd64, SMB dependency? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Mars G. Miro" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 01:13:53 -0000 On 5/3/05, Jung-uk Kim wrote: > On Monday 02 May 2005 06:38 am, Mars G. Miro wrote: > > Bombs in here: > > gmake[1]: Entering directory > > `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' > > gcc34 -Wall -O2 -g -fno-strict-aliasing -I. > > -I/usr/ports/emulators/qemu/work/qemu-0.7.0/target-i386 > > -I/usr/ports/emulators/qemu/work/qemu-0.7.0 -D_GNU_SOURCE > > -D_FILE_OFFSET_BITS=3D64 -D_LARGEFILE_SOURCE > > -DSMBD=3D\"/usr/local/sbin/smbd\" > > -I/usr/ports/emulators/qemu/work/qemu-0.7.0/fpu > > -I/usr/ports/emulators/qemu/work/qemu-0.7.0/slirp -c -o vl.o > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c > > In file included from > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat.h:394, > > from > > /usr/ports/emulators/qemu/work/qemu-0.7.0/target-i386/cpu.h:41, > > from > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.h:73, from > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:24: > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:39 > >: error: `FE_RM' undeclared here (not in a function) > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:39 > >: error: enumerator value for `float_round_down' not integer > > constant > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:40 > >: error: `FE_RP' undeclared here (not in a function) > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:40 > >: error: enumerator value for `float_round_up' not integer constant > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:42 > >: error: `FE_RZ' undeclared here (not in a function) > > /usr/ports/emulators/qemu/work/qemu-0.7.0/fpu/softfloat-native.h:42 > >: error: enumerator value for `float_round_to_zero' not integer > > constant /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: In > > function `init_timers': > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:982: warning: label > > `use_itimer' defined but not used > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: In function > > `loadmodules': /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:1622: > > warning: implicit declaration of function `kldload' > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c: At top level: > > /usr/ports/emulators/qemu/work/qemu-0.7.0/vl.c:910: warning: > > 'start_rtc_timer' defined but not used > > gmake[1]: *** [vl.o] Error 1 > > gmake[1]: Leaving directory > > `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' > > gmake: *** [all] Error 1 > > *** Error code 2 > > > > Stop in /usr/ports/emulators/qemu. > > tart_rtc_timer' defined but not used > > gmake[1]: *** [vl.o] Error 1 > > gmake[1]: Leaving directory > > `/usr/ports/emulators/qemu/work/qemu-0.7.0/i386-softmmu' > > gmake: *** [all] Error 1 > > *** Error code 2 > > > > Stop in /usr/ports/emulators/qemu. > > > > I'm guessing it's qemu's hard dependency on samba, yes? > > > > I'll see if installing samba makes it not bomb. >=20 > Actually there are two missing patches, namely patch-fbsd and=20 > patch-libmath from the original PR. You can get them from the PR=20 > itself. >=20 > http://docs.freebsd.org/cgi/mid.cgi?200504301849.j3UIng675264 >=20 > FYI, committer's aware of the issue already. >=20 And the recent commits now builds the port w/o errors. Thanks ;-) > Jung-uk Kim >=20 > > Matsalams ;-) > > > > > > > > cheers > > mars >=20 cheers mars From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 08:44:32 2005 Return-Path: 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 3482916A4CE; Thu, 5 May 2005 08:44:32 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1F7043D53; Thu, 5 May 2005 08:44:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.3/8.13.3) with ESMTP id j458iUSM072174; Thu, 5 May 2005 04:44:31 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id j458iTkB043371; Thu, 5 May 2005 04:44:30 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A12D07306E; Thu, 5 May 2005 04:44:28 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050505084428.A12D07306E@freebsd-current.sentex.ca> Date: Thu, 5 May 2005 04:44:28 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on smarthost2.sentex.ca X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on clamscanner1 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 08:44:32 -0000 TB --- 2005-05-05 06:38:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-05-05 06:38:25 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-05-05 06:38:25 - cleaning the object tree TB --- 2005-05-05 06:38:58 - checking out the source tree TB --- 2005-05-05 06:38:58 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-05-05 06:38:58 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-05-05 06:45:47 - building world (CFLAGS=-O2 -pipe) TB --- 2005-05-05 06:45:47 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-05 06:45:47 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-05-05 08:31:54 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-05-05 08:31:54 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-05 08:31:54 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu May 5 08:31:54 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] touch export_syms awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/modules/my/../../conf/kmod_syms.awk if_my.ko.debug export_syms | xargs -J% objcopy % if_my.ko.debug objcopy --strip-debug if_my.ko.debug if_my.ko ===> ndis (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -fno-omit-frame-pointer -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_pe.c cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -fno-omit-frame-pointer -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c: In function `NdisMFreeSharedMemory': /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c:1710: warning: long long unsigned int format, uint64_t arg (arg 3) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-05-05 08:44:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-05-05 08:44:28 - ERROR: failed to build generic kernel TB --- 2005-05-05 08:44:28 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 09:09:35 2005 Return-Path: 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 4768D16A4CE; Thu, 5 May 2005 09:09:35 +0000 (GMT) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85EE543DA1; Thu, 5 May 2005 09:09:33 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: from beastie.frontfree.net (unknown [219.239.99.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 58FA9EB22AD; Thu, 5 May 2005 17:09:21 +0800 (CST) Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 5896A1312B0; Thu, 5 May 2005 17:09:14 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38007-18; Thu, 5 May 2005 17:09:08 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 7E54813113D; Thu, 5 May 2005 17:09:07 +0800 (CST) Date: Thu, 5 May 2005 17:09:07 +0800 From: Xin LI To: FreeBSD Tinderbox Message-ID: <20050505090907.GA41071@frontfree.net> References: <20050505084428.A12D07306E@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline In-Reply-To: <20050505084428.A12D07306E@freebsd-current.sentex.ca> User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #15: Wed Dec 15 10:43:16 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: amd64@freebsd.org cc: wpaul@FreeBSD.org cc: current@freebsd.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 09:09:35 -0000 --gatW/ieO32f1wygP Content-Type: multipart/mixed; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 05, 2005 at 04:44:28AM -0400, FreeBSD Tinderbox wrote: > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdi= nc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURREN= T/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../= include -finline-limit=3D8000 -fno-common -g -fno-omit-frame-pointer -I/tin= derbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/= GENERIC -mcmodel=3Dkernel -mno-red-zone -mfpmath=3D387 -mno-sse -mno-sse2 = -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreesta= nding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissi= ng-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st= d=3Dc99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat= /ndis/subr_pe.c > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdi= nc -I- -include /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURREN= T/amd64/amd64/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../= include -finline-limit=3D8000 -fno-common -g -fno-omit-frame-pointer -I/tin= derbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/= GENERIC -mcmodel=3Dkernel -mno-red-zone -mfpmath=3D387 -mno-sse -mno-sse2 = -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreesta= nding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissi= ng-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st= d=3Dc99 -c /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat= /ndis/subr_ndis.c > /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/sub= r_ndis.c: In function `NdisMFreeSharedMemory': > /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/sub= r_ndis.c:1710: warning: long long unsigned int format, uint64_t arg (arg 3) Maybe we should make use of the PRIx64 macro? (see patch attached) Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch-ndis Content-Transfer-Encoding: quoted-printable Index: subr_ndis.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/compat/ndis/subr_ndis.c,v retrieving revision 1.87 diff -u -r1.87 subr_ndis.c --- subr_ndis.c 5 May 2005 04:16:13 -0000 1.87 +++ subr_ndis.c 5 May 2005 09:02:54 -0000 @@ -90,6 +90,7 @@ #include #include =20 +#include #include =20 #include @@ -1706,7 +1707,8 @@ =20 if (sh =3D=3D NULL) { printf("NDIS: buggy driver tried to free " - "invalid shared memory: vaddr: %p paddr: 0x%qx\n", + "invalid shared memory: vaddr: %p paddr: " + "0x%" PRIx64 "\n", vaddr, paddr.np_quad); return; } --LZvS9be/3tNcYl/X-- --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCeeKz/cVsHxFZiIoRApKTAJ9ng9EnapbWyieIUpFW5FcHmkaf6gCbBEcY pQVNjnnij3u/qeN1KBHGfWQ= =tVFz -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 10:52:46 2005 Return-Path: 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 EDFAF16A4CE; Thu, 5 May 2005 10:52:46 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62D7643D82; Thu, 5 May 2005 10:52:46 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])j45AqirI025686; Thu, 5 May 2005 20:52:44 +1000 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) j45AqcRL011214; Thu, 5 May 2005 20:52:43 +1000 Date: Thu, 5 May 2005 20:52:39 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Xin LI In-Reply-To: <20050505090907.GA41071@frontfree.net> Message-ID: <20050505204235.L7880@delplex.bde.org> References: <20050505084428.A12D07306E@freebsd-current.sentex.ca> <20050505090907.GA41071@frontfree.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: amd64@FreeBSD.org cc: wpaul@FreeBSD.org cc: FreeBSD Tinderbox cc: current@FreeBSD.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 10:52:47 -0000 On Thu, 5 May 2005, Xin LI wrote: > On Thu, May 05, 2005 at 04:44:28AM -0400, FreeBSD Tinderbox wrote: >> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c: In function `NdisMFreeSharedMemory': >> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c:1710: warning: long long unsigned int format, uint64_t arg (arg 3) > > Maybe we should make use of the PRIx64 macro? (see patch attached) No. PRI* is a bug in C99; it should never be used. Just cast the arg to a suitable larger type with a known format (uintmax_t here). (C99 is missing support for better ways; either %I as in sfio (?) or %DWIM where the compiler rewrites the string to match the arg would be better.) Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 13:52:38 2005 Return-Path: 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 C9B2A16A4CE for ; Thu, 5 May 2005 13:52:38 +0000 (GMT) Received: from godzilla.vipstructures.com (godzilla.vipstructures.com [66.195.71.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3C543D97 for ; Thu, 5 May 2005 13:52:38 +0000 (GMT) (envelope-from etoll@vipstructures.com) Received: from localhost (localhost.vipstructures.com [127.0.0.1]) by godzilla.vipstructures.com (Postfix) with ESMTP id 917C42841D for ; Thu, 5 May 2005 09:52:33 -0400 (EDT) Received: from godzilla.vipstructures.com ([127.0.0.1])port 10024) with ESMTP id 33806-10 for ; Thu, 5 May 2005 09:52:33 -0400 (EDT) Received: from mothra.vipstructures.com (mothra.vipstructures.com [192.168.1.3]) by godzilla.vipstructures.com (Postfix) with ESMTP id 58E1E2841C for ; Thu, 5 May 2005 09:52:33 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 May 2005 09:52:33 -0400 Message-ID: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> From: "Toll, Eric" To: X-Antivirus: checked by Norton Anti Virus X-MTA-Mailer: Postfix 2 by Wietse Venema - http://www.postfix.org X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on godzilla.vipstructures.com Subject: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 13:52:38 -0000 I am going to build a new server! (I'm excited) below is my shopping = list, this all started with a desire to have a Raid FreeBSD system. RAID led me to = 3Ware, current offerings from 3Ware were of *only* the 64 Bit PCI flavor, my = current MB didn't have it [Cheep SIS with (1) Athlon XP2400+ with WD PATA IDE 40GB] = So I looked for mainboards that had a 66Mhz 64bit PCI slot, from 3Ware's = hardware compatibility list. Found a good one I hope with the Gigabyte board. So = now I'm thinking instead of FreeBSD 5.3 or 5.4 to go with the FreeBSD-AMD64 = version. Comments welcome, anyone see any issues? Anyone else have a Gigabyte board with (GA-7A8DW AMD 8111/8131)=20 Chipset running AMD-64? Also my video card will be a Geforce 4 Ti 4200 4x AGP, I like to run X = so I can see high res real time logs... =20 8006-2LP KIT ESCALADE 8006-2LP 1 141.47 = 141.47 WD2500SD WD CAVIAR 250GB RAID ED.SATA-3 2 149.98 = 299.96 GA-7A8DW SERVER BOARDAMD 81118131+81 1 340.86 = 340.86 TITAN 550 ANTEC TITAN SERIES 550 CASE 1 209.87 = 209.87 OSA242AUBOX OPTERON DP SERVER 242 PIB-R 2 217.77 = 435.54 KRX3200AK2/1G 1GB KIT(2X512)DDR400 REG HY 1 415.80 = 415.80 Not bad for around $2,000.00 USD Eh? Regards, Eric From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 14:15:03 2005 Return-Path: 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 63C1716A4CF for ; Thu, 5 May 2005 14:15:03 +0000 (GMT) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CDDF43D78 for ; Thu, 5 May 2005 14:15:02 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from stevenp4 ([193.123.241.40]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.0.1.R) with ESMTP id md50001383823.msg for ; Thu, 05 May 2005 15:10:37 +0100 Message-ID: <02c201c5517c$b6f807f0$7f06000a@int.mediasurface.com> From: "Steven Hartland" To: "Toll, Eric" , References: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> Date: Thu, 5 May 2005 15:14:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Thu, 05 May 2005 15:10:37 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 193.123.241.40 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-amd64@FreeBSD.org X-MDAV-Processed: multiplay.co.uk, Thu, 05 May 2005 15:10:38 +0100 Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 14:15:03 -0000 See the thread "Very low disk performance on 5.x" for details about RAID and FreeBSD that was using that MB with 244's and a Highpoint 1820a. Note: With 2 disks your options are very limited RAID 0 or RAID 1 so dont expect both redundency and extra performance. That RAM looks VERY expensive I paid £187 for 2Gb. ----- Original Message ----- From: "Toll, Eric" To: Sent: 05 May 2005 14:52 Subject: Hello 64 World - My proposed 3Ware system I am going to build a new server! (I'm excited) below is my shopping list, this all started with a desire to have a Raid FreeBSD system. RAID led me to 3Ware, current offerings from 3Ware were of *only* the 64 Bit PCI flavor, my current MB didn't have it [Cheep SIS with (1) Athlon XP2400+ with WD PATA IDE 40GB] So I looked for mainboards that had a 66Mhz 64bit PCI slot, from 3Ware's hardware compatibility list. Found a good one I hope with the Gigabyte board. So now I'm thinking instead of FreeBSD 5.3 or 5.4 to go with the FreeBSD-AMD64 version. Comments welcome, anyone see any issues? Anyone else have a Gigabyte board with (GA-7A8DW AMD 8111/8131) Chipset running AMD-64? Also my video card will be a Geforce 4 Ti 4200 4x AGP, I like to run X so I can see high res real time logs... 8006-2LP KIT ESCALADE 8006-2LP 1 141.47 141.47 WD2500SD WD CAVIAR 250GB RAID ED.SATA-3 2 149.98 299.96 GA-7A8DW SERVER BOARDAMD 81118131+81 1 340.86 340.86 TITAN 550 ANTEC TITAN SERIES 550 CASE 1 209.87 209.87 OSA242AUBOX OPTERON DP SERVER 242 PIB-R 2 217.77 435.54 KRX3200AK2/1G 1GB KIT(2X512)DDR400 REG HY 1 415.80 415.80 Not bad for around $2,000.00 USD Eh? Regards, Eric _______________________________________________ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscribe@freebsd.org ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 15:54:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 42D4E16A4CF; Thu, 5 May 2005 15:54:45 +0000 (GMT) In-Reply-To: <20050505204235.L7880@delplex.bde.org> from Bruce Evans at "May 5, 2005 08:52:39 pm" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 5 May 2005 15:54:45 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20050505155445.42D4E16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: amd64@FreeBSD.org cc: current@FreeBSD.org cc: tinderbox@FreeBSD.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 15:54:45 -0000 > On Thu, 5 May 2005, Xin LI wrote: > > > On Thu, May 05, 2005 at 04:44:28AM -0400, FreeBSD Tinderbox wrote: > >> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c: In function `NdisMFreeSharedMemory': > >> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c:1710: warning: long long unsigned int format, uint64_t arg (arg 3) > > > > Maybe we should make use of the PRIx64 macro? (see patch attached) > > No. PRI* is a bug in C99; it should never be used. Just cast the arg to > a suitable larger type with a known format (uintmax_t here). (C99 is > missing support for better ways; either %I as in sfio (?) or %DWIM where > the compiler rewrites the string to match the arg would be better.) > > Bruce I think what you really meant to say was: "Use %jx instead of %qx." Am I right? -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 16:20:00 2005 Return-Path: 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 7B83416A4CE for ; Thu, 5 May 2005 16:20:00 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BC6D43D48 for ; Thu, 5 May 2005 16:20:00 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j45GJtZB001991; Thu, 5 May 2005 09:19:55 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j45GJsKm001990; Thu, 5 May 2005 09:19:54 -0700 (PDT) (envelope-from obrien) Date: Thu, 5 May 2005 09:19:54 -0700 From: "David O'Brien" To: "Toll, Eric" Message-ID: <20050505161954.GB1799@dragon.NUXI.org> References: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@FreeBSD.org Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 16:20:00 -0000 On Thu, May 05, 2005 at 09:52:33AM -0400, Toll, Eric wrote: > I am going to build a new server! (I'm excited) below is my shopping > list, this all started with a desire to have a Raid FreeBSD system. > RAID led me to 3Ware, current offerings from 3Ware were of *only* the > 64 Bit PCI flavor, my current MB didn't have it [Cheep SIS with (1) > Athlon XP2400+ with WD PATA IDE 40GB] So I looked for mainboards that > had a 66Mhz 64bit PCI slot, from 3Ware's hardware compatibility list. > Found a good one I hope with the Gigabyte board. So now I'm thinking > instead of FreeBSD 5.3 or 5.4 to go with the FreeBSD-AMD64 version. > > Comments welcome, anyone see any issues? > > Anyone else have a Gigabyte board with (GA-7A8DW AMD 8111/8131) > Chipset running AMD-64? It is hard to find information about this motherboard at Gigabyte's USA site (since you're mentioning $$). Where have you found to buy it? This motherboard has a 4+0 DIMM configuration, which means you are (1) limited to 4 DIMM's, (2) only get 1/2 the possible memory bandwidth. I'm not saying this is an absolutely terrible thing, but be aware of it. I fear this board won't get good BIOS support - looking at the list of downloadable BIOS updates, I cannot tell what any of them fix. Worse is no confidence Gigabyte will support the new Opteron revision E (90nm) processors, including dual-core ones. I'm not sure why you are looking at an AGP based motherboard for a server. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 16:21:21 2005 Return-Path: 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 A81F316A4CE; Thu, 5 May 2005 16:21:21 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 117F843D6D; Thu, 5 May 2005 16:21:21 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])j45GLKkG029013; Fri, 6 May 2005 02:21:20 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) j45GLHx7019395; Fri, 6 May 2005 02:21:18 +1000 Date: Fri, 6 May 2005 02:21:18 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Bill Paul In-Reply-To: <20050505155445.42D4E16A4CF@hub.freebsd.org> Message-ID: <20050506021433.W4828@epsplex.bde.org> References: <20050505155445.42D4E16A4CF@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: amd64@freebsd.org cc: current@freebsd.org cc: tinderbox@freebsd.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 16:21:21 -0000 On Thu, 5 May 2005, Bill Paul wrote: >> On Thu, 5 May 2005, Xin LI wrote: >> >>> On Thu, May 05, 2005 at 04:44:28AM -0400, FreeBSD Tinderbox wrote: >>>> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c: In function `NdisMFreeSharedMemory': >>>> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c:1710: warning: long long unsigned int format, uint64_t arg (arg 3) >>> >>> Maybe we should make use of the PRIx64 macro? (see patch attached) >> >> No. PRI* is a bug in C99; it should never be used. Just cast the arg to >> a suitable larger type with a known format (uintmax_t here). (C99 is >> missing support for better ways; either %I as in sfio (?) or %DWIM where >> the compiler rewrites the string to match the arg would be better.) > > I think what you really meant to say was: > > "Use %jx instead of %qx." > > Am I right? No, the arg must match the format. %jx matches uintmax_t, but the arg has type uint64_t. uint64_t just happens to be the same as uintmax_t on all supported machines, so using %jx without casting the arg to match gives a latent bug. Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 16:55:43 2005 Return-Path: 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 42E3416A4D5; Thu, 5 May 2005 16:55:43 +0000 (GMT) Received: from godzilla.vipstructures.com (godzilla.vipstructures.com [66.195.71.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E05D43D9D; Thu, 5 May 2005 16:55:42 +0000 (GMT) (envelope-from etoll@vipstructures.com) Received: from localhost (localhost.vipstructures.com [127.0.0.1]) by godzilla.vipstructures.com (Postfix) with ESMTP id 17CB02841C; Thu, 5 May 2005 12:55:37 -0400 (EDT) Received: from godzilla.vipstructures.com ([127.0.0.1])port 10024) with ESMTP id 35033-05; Thu, 5 May 2005 12:55:36 -0400 (EDT) Received: from mothra.vipstructures.com (mothra.vipstructures.com [192.168.1.3]) by godzilla.vipstructures.com (Postfix) with ESMTP id A39C42841D; Thu, 5 May 2005 12:55:36 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 May 2005 12:55:36 -0400 Message-ID: <9BC86C67C3AF7646B9C5382020457A944E4D20@VIP10-WIN2K> From: "Toll, Eric" To: X-Antivirus: checked by Norton Anti Virus X-MTA-Mailer: Postfix 2 by Wietse Venema - http://www.postfix.org X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on godzilla.vipstructures.com cc: David O'Brien Subject: RE: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 16:55:43 -0000 =20 > >=20 > > Anyone else have a Gigabyte board with (GA-7A8DW AMD 8111/8131)=20 > > Chipset running AMD-64? >=20 > It is hard to find information about this motherboard at=20 > Gigabyte's USA > site (since you're mentioning $$). Where have you found to buy it? It's listed under the server/workstation boards: http://www.giga-byte.com/Server/Products/Products_ServerBoard_GA-7A8DW.ht= m# > This motherboard has a 4+0 DIMM configuration, which means=20 > you are (1) limited to 4 DIMM's, (2) only get 1/2 the=20 > possible memory bandwidth. I'm not saying this is an=20 > absolutely terrible thing, but be aware of it. Thanks for pointing that out. Can you offer a replacement model? What = MB/RAM setup do you have? {and how much $ was it?} I'd like it to be able to run Dual Opteron 242's (as they're cheep) and = have a 66MHZ 64BIT PCI slot, and (1) AGP slot. What do you or anyone else = recommend?? I couldn't find much else that had these features that was on the 3Ware = tested list. Am I crazy for going to this length? :) As it is the memory must be ECC Registered, and I opted for the Kingston = which is: .. a kit of two 64M x 72-bit (512MB) DDR400 CL2.5 SDRAM Synchronous = DRAM) registered ECC memory modules. Total kit capacity is 1GB. The components = on each module include eighteen 32M x 8-bit (8M x 8-bit x 4 Bank) DDR400 SDRAM = in TSOP packages. Each 184-pin DIMM uses gold contact fingers and requires +2.6V Bleading edge technology costs so much. I have only $2,000.00 USD to = spend. I thought what I came up with wasn't that bad price wise, I already own = the Nvidia GeForce 4 Ti4200. (Gainward GS) 3Ware recommended the WD SATA = drives (RAID Edition) and the mainboard as it's on their certified list, which = was updated March of this year. 8006-2LP KIT ESCALADE 8006-2LP 1 141.47 = 141.47 WD2500SD WD CAVIAR 250GB RAID SATA-3 2 149.98 = 299.96 GA-7A8DW SERVER BOARDAMD 81118131+81 1 340.86 = 340.86 TITAN 550 TITAN SERIES 550 1 209.87 = 209.87 OSA242AUBOX OPTERON DP SERVER 242 PIB-R 2 217.77 = 435.54 KRX3200AK2/1G 1GB KIT(2X512)DDR400 REG HY 1 415.80 = 415.80 BTW these items all come from Insight.com, and all are in stock (I get better than Web price) > I fear this board won't get good BIOS support - looking at=20 > the list of downloadable BIOS updates, I cannot tell what any=20 > of them fix. Worse is no confidence Gigabyte will support=20 > the new Opteron revision E (90nm) processors, including=20 > dual-core ones. That's OK I guess, I will have this system for the next 6 years. The = dual Opteron 242's I want to get are 1.6Ghz each and at least are based on = the "new" 64bit technology from AMD. I would never pull out those (2) 242's and = replace them with something better, I'd build a whole new system again. >=20 > I'm not sure why you are looking at an AGP based motherboard=20 > for a server. To me X Windows is sooo sexy. I *love* the GL screensaveers, I also = like to watch my logs in realtime. (e.g. tail -F /var/log/maillog ...)I'll be = running 1280x1024x32 color with the Nvidia accelerated driver via a 19' NEC CRT. = Even now the OpenGL screen savers only use 3%-10% of my CPU. Have you ever = seen "Endgame" run at 45fps? In best GL mode. I love X11 (or is it X.org = now) DNS & WWW logs I like watch on screen realtime. So to me having a server = motherboard with an AGP port is very important. Will I be able to do this [the above] with AMD-64 FreeBSD? Nothings been purchased yet, so I appreciate any steering you may be = able to provide. Kind Regards, Eric From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 17:02:04 2005 Return-Path: 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 659D016A4CE for ; Thu, 5 May 2005 17:02:04 +0000 (GMT) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F3343D76; Thu, 5 May 2005 17:02:03 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from stevenp4 ([193.123.241.40]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.0.1.R) with ESMTP id md50001384267.msg; Thu, 05 May 2005 17:57:44 +0100 Message-ID: <034101c55194$1178db70$7f06000a@int.mediasurface.com> From: "Steven Hartland" To: , "Toll, Eric" References: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> <20050505161954.GB1799@dragon.NUXI.org> Date: Thu, 5 May 2005 18:01:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Thu, 05 May 2005 17:57:44 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 193.123.241.40 X-Return-Path: killing@multiplay.co.uk X-MDAV-Processed: multiplay.co.uk, Thu, 05 May 2005 17:57:45 +0100 cc: freebsd-amd64@FreeBSD.org Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 17:02:04 -0000 ----- Original Message ----- From: "David O'Brien" > It is hard to find information about this motherboard at Gigabyte's USA > site (since you're mentioning $$). Where have you found to buy it? > This motherboard has a 4+0 DIMM configuration, which means you are (1) > limited to 4 DIMM's, (2) only get 1/2 the possible memory bandwidth. I'm > not saying this is an absolutely terrible thing, but be aware of it. Interesting out of curiosity what memory bandwidth would you expect on a test say ubench for a machine of this spec if it supported full memory bandwidth? Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 17:04:49 2005 Return-Path: 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 C436216A4CE for ; Thu, 5 May 2005 17:04:49 +0000 (GMT) Received: from godzilla.vipstructures.com (godzilla.vipstructures.com [66.195.71.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 920D343DA1 for ; Thu, 5 May 2005 17:04:49 +0000 (GMT) (envelope-from etoll@vipstructures.com) Received: from localhost (localhost.vipstructures.com [127.0.0.1]) by godzilla.vipstructures.com (Postfix) with ESMTP id 495A328420 for ; Thu, 5 May 2005 13:04:44 -0400 (EDT) Received: from godzilla.vipstructures.com ([127.0.0.1])port 10024) with ESMTP id 35257-02 for ; Thu, 5 May 2005 13:04:43 -0400 (EDT) Received: from mothra.vipstructures.com (mothra.vipstructures.com [192.168.1.3]) by godzilla.vipstructures.com (Postfix) with ESMTP id E2F6A2841D for ; Thu, 5 May 2005 13:04:43 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 May 2005 13:04:43 -0400 Message-ID: <9BC86C67C3AF7646B9C5382020457A9456E8D6@VIP10-WIN2K> From: "Toll, Eric" To: "Steven Hartland" , X-Antivirus: checked by Norton Anti Virus X-MTA-Mailer: Postfix 2 by Wietse Venema - http://www.postfix.org X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on godzilla.vipstructures.com cc: freebsd-amd64@FreeBSD.org Subject: RE: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 17:04:49 -0000 > > It is hard to find information about this motherboard at=20 > Gigabyte's USA > > site (since you're mentioning $$). Where have you found to buy it? > > This motherboard has a 4+0 DIMM configuration, which means=20 > you are (1)=20 > > limited to 4 DIMM's, (2) only get 1/2 the possible memory=20 > bandwidth. =20 > > I'm not saying this is an absolutely terrible thing, but be=20 > aware of it. >=20 > Interesting out of curiosity what memory bandwidth would you=20 > expect on a test say ubench for a machine of this spec if it=20 > supported full memory bandwidth? >=20 > Steve >=20 Steve: What are you running for a Mainboard? Also If you'd like to = share the manufacture and part number of those (2) 1Gb DDR sticks you have I'd be appreciative. Are we talking about DDR2 memory here {above}? Regards, Eric From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 18:08:23 2005 Return-Path: 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 5634216A4CE for ; Thu, 5 May 2005 18:08:23 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6F9643D92 for ; Thu, 5 May 2005 18:08:22 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id BC721F7ED for ; Thu, 5 May 2005 12:08:21 -0600 (MDT) Date: Thu, 5 May 2005 12:08:21 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050505120821.07ac715b.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: to interleave or not to interleave... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 18:08:23 -0000 Hello: Searching for enlightenment and I'm not a memory guru nor kernel hacker here so could use some help understanding this. System is a Tyan B2882T26 w/ a pair of 246's. I've two 1GB sticks of Corsair ECC Registered memory onhand. Question is whether it would be "best" to: 1) put both cpu0 dimm slots 1 & 2 2) put 1 in dimm slot 1 of each cpu If I understand correctly, config 1 results in 128 bit interleaved while config 2 results in 64 bit non-interleaved. (config 1 leaves cpu 0 as memory "controller" for cup 1?). I've read some stuff where interleaved results in faster access but also can have "miss" penalaties. Any explanations on where one strategy is better than other appreciated. Thanks for the insights. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 18:22:14 2005 Return-Path: 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 A419516A4CE for ; Thu, 5 May 2005 18:22:14 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3FB043DB3 for ; Thu, 5 May 2005 18:22:13 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 1EB8F78C79 for ; Thu, 5 May 2005 14:24:31 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24238-09 for ; Thu, 5 May 2005 14:24:24 -0400 (EDT) Received: from dementia.afflictions.org (unknown [172.19.206.152]) by pandora.afflictions.org (Postfix) with ESMTP id CFDFB78C64 for ; Thu, 5 May 2005 14:24:17 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 4BE5833C96; Thu, 5 May 2005 13:38:53 -0400 (EDT) Date: Thu, 5 May 2005 13:38:53 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050505173853.GA92282@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <9BC86C67C3AF7646B9C5382020457A944E4D20@VIP10-WIN2K> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9BC86C67C3AF7646B9C5382020457A944E4D20@VIP10-WIN2K> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 18:22:14 -0000 Thus spake Toll, Eric (etoll@vipstructures.com) [05/05/05 12:58]: : To me X Windows is sooo sexy. I *love* the GL screensaveers, I also like to : watch my logs in realtime. (e.g. tail -F /var/log/maillog ...)I'll be running : 1280x1024x32 color with the Nvidia accelerated driver via a 19' NEC CRT. Even : now the OpenGL screen savers only use 3%-10% of my CPU. Have you ever seen : "Endgame" run at 45fps? In best GL mode. I love X11 (or is it X.org now) DNS & : WWW logs I like watch on screen realtime. So to me having a server motherboard : with an AGP port is very important. : : Will I be able to do this [the above] with AMD-64 FreeBSD? Nope. The nVidia accelerated driver doesn't support AMD64 yet. There's been murmurings of a driver in development, but I've not heard from them yet (three e-mails to their support team and counting). You can check the archives of this list for details. That being said, the nv driver still works great, even though it doesn't have hardware 3D support. It's not much for games, but it can still to 1600x1200x32 without much trouble. From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 19:25:01 2005 Return-Path: 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 54D2D16A4CE for ; Thu, 5 May 2005 19:25:01 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0315C43DC0 for ; Thu, 5 May 2005 19:25:01 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j45JOt8h005081; Thu, 5 May 2005 12:24:55 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j45JOtYg005080; Thu, 5 May 2005 12:24:55 -0700 (PDT) (envelope-from obrien) Date: Thu, 5 May 2005 12:24:55 -0700 From: "David O'Brien" To: Ken Gunderson Message-ID: <20050505192455.GC1799@dragon.NUXI.org> References: <20050505120821.07ac715b.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050505120821.07ac715b.kgunders@teamcool.net> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: to interleave or not to interleave... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 19:25:01 -0000 On Thu, May 05, 2005 at 12:08:21PM -0600, Ken Gunderson wrote: > Searching for enlightenment and I'm not a memory guru nor kernel hacker > here so could use some help understanding this. System is a Tyan > B2882T26 w/ a pair of 246's. This uses the Tyan s2882 motherboard, which is really what the question centers around. > I've two 1GB sticks of Corsair ECC > Registered memory onhand. Question is whether it would be "best" to: > > 1) put both cpu0 dimm slots 1 & 2 > 2) put 1 in dimm slot 1 of each cpu > If I understand correctly, config 1 results in 128 bit interleaved while > config 2 results in 64 bit non-interleaved. (config 1 leaves cpu 0 as > memory "controller" for cup 1?). Correct. Using both of your DIMMs in one CPU means you do 128-bit (dual-channel) memory accesses, but your 2nd memory controller is idle. And you are guarenteed the 2nd CPU will always go across the Hypertransport link for memory accesses. Putting one DIMM in each CPU means you only do 64-bit (single-channel) memory accesses, but you are able to have both memory controllers active. > I've read some stuff where > interleaved results in faster access but also can have "miss" > penalaties. Any explanations on where one strategy is better than > other appreciated. This is a hard question to answer. The real answer is to get another 2 DIMM's. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 19:39:20 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 2120B16A4CF; Thu, 5 May 2005 19:39:20 +0000 (GMT) In-Reply-To: <20050506021433.W4828@epsplex.bde.org> from Bruce Evans at "May 6, 2005 02:21:18 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 5 May 2005 19:39:20 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20050505193920.2120B16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: amd64@freebsd.org cc: current@freebsd.org cc: tinderbox@freebsd.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 19:39:20 -0000 > On Thu, 5 May 2005, Bill Paul wrote: > > >> On Thu, 5 May 2005, Xin LI wrote: > >> > >>> On Thu, May 05, 2005 at 04:44:28AM -0400, FreeBSD Tinderbox wrote: > >>>> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c: In function `NdisMFreeSharedMemory': > >>>> /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ndis/../../compat/ndis/subr_ndis.c:1710: warning: long long unsigned int format, uint64_t arg (arg 3) > >>> > >>> Maybe we should make use of the PRIx64 macro? (see patch attached) > >> > >> No. PRI* is a bug in C99; it should never be used. Just cast the arg to > >> a suitable larger type with a known format (uintmax_t here). (C99 is > >> missing support for better ways; either %I as in sfio (?) or %DWIM where > >> the compiler rewrites the string to match the arg would be better.) > > > > I think what you really meant to say was: > > > > "Use %jx instead of %qx." > > > > Am I right? > > No, the arg must match the format. %jx matches uintmax_t, but the arg has > type uint64_t. uint64_t just happens to be the same as uintmax_t on all > supported machines, so using %jx without casting the arg to match gives a > latent bug. > > Bruce So what you really, _really_ meant to say was: "Cast the argument to uintmax_t _and_ use %jx instead of %qx." Am I right? -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 19:57:28 2005 Return-Path: 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 00C8C16A4CF for ; Thu, 5 May 2005 19:57:28 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B0B743D72 for ; Thu, 5 May 2005 19:57:27 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id B1ACEF7B3 for ; Thu, 5 May 2005 13:57:26 -0600 (MDT) Date: Thu, 5 May 2005 13:57:25 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050505135725.1edb08f7.kgunders@teamcool.net> In-Reply-To: <20050505192455.GC1799@dragon.NUXI.org> References: <20050505120821.07ac715b.kgunders@teamcool.net> <20050505192455.GC1799@dragon.NUXI.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: to interleave or not to interleave... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 19:57:28 -0000 On Thu, 5 May 2005 12:24:55 -0700 "David O'Brien" wrote: > On Thu, May 05, 2005 at 12:08:21PM -0600, Ken Gunderson wrote: > > Searching for enlightenment and I'm not a memory guru nor kernel hacker > > here so could use some help understanding this. System is a Tyan > > B2882T26 w/ a pair of 246's. > > This uses the Tyan s2882 motherboard, which is really what the question > centers around. Yes;-) > > I've two 1GB sticks of Corsair ECC > > Registered memory onhand. Question is whether it would be "best" to: > > > > 1) put both cpu0 dimm slots 1 & 2 > > 2) put 1 in dimm slot 1 of each cpu > > If I understand correctly, config 1 results in 128 bit interleaved while > > config 2 results in 64 bit non-interleaved. (config 1 leaves cpu 0 as > > memory "controller" for cup 1?). > > Correct. Thanks. Glad to see I got at least that part of it right...;-P > Using both of your DIMMs in one CPU means you do 128-bit (dual-channel) > memory accesses, but your 2nd memory controller is idle. And you are > guarenteed the 2nd CPU will always go across the Hypertransport link for > memory accesses. > Putting one DIMM in each CPU means you only do 64-bit (single-channel) > memory accesses, but you are able to have both memory controllers active. > > > > I've read some stuff where > > interleaved results in faster access but also can have "miss" > > penalaties. Any explanations on where one strategy is better than > > other appreciated. > > This is a hard question to answer. > The real answer is to get another 2 DIMM's. It wasn't in the budget though and wanted to maintain good future expandability, so went with the 2 x 1GB config (system was already over budget and I was concerned about adding another $350 to the price tag). Maybe my bad though... I figured the 128 bit interleaved must be superior, else they wouldn't have the option. But reading some stuff here (that I don't completely understand) , as well as a couple other places, talk about downsides to the strategy. It seems in my situation is a six of one and half dozen of the other? If it's any help, the server will do web, email, and some application server duties (e.g. Zope, JBoss, Tomcat, etc. Not sure which yet). Envision some light db ala PostgreSQL feeding the app server. Either way I don't think this puppy is going to see enough load to even begin to stress it. I'd just like to do the best I can with options at hand. Thanks David. Much appreciated. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 21:17:07 2005 Return-Path: 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 0FF1116A4CE for ; Thu, 5 May 2005 21:17:07 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D6D343D88 for ; Thu, 5 May 2005 21:17:06 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.12.10/5.2) with ESMTP id j45LH1UL009171 for ; Thu, 5 May 2005 23:17:01 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Thu, 5 May 2005 23:17:00 +0200 User-Agent: KMail/1.8.50 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505052317.00951.groot@kde.org> X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Subject: Recommendations, redux X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 21:17:07 -0000 What with all the recommendations threads going on recently, I've gone and mislaid the URL to the page that's collecting them. Could someone refresh my memory? See, I'm now suddenly in the position to have to shop for a server (and that means figuring out what I _want_, anyway), and I find myself in unfamiliar territory. Desktops are fairly straightfoward, I think: Via KT800 chipset and all is fine; both my Asus K8V-SE Deluxe and Gigabyte Ga-K8VT800 work out of the box, including RAID mirroring on the Via 82xx controller (both boards) or the Promise controller in the K8V-SE. Fill two of the 3 DIMM slots with decent RAM and you're off. Servers, well, I'm out of my depth there. Consider SATA-RAID (I'm still a sucker for non-SCSI solutions). From Scott Long's message of apr. 19th, I can't tell if the Adaptec 2410SA is supported .. er, the hardware notes say it uses aac(4) which is safe. Spectacularly much cheaper are things like HighPoint Rocket RAID and Promise FastTrak (There's the difference in PCI bus to take into account there, to account for the price difference). Neither are mentioned on the hardware notes page. Neither is Silicon Image stuff, like the 3112 (used in some Intel SATA-RAID cards). Oddly enough, local retailers list FreeBSD as a supported OS for the HighPoint -- I guess that's just i386 then (confirmed by the i386 HW notes). At the risk of becoming _too_ specific, can anyone recommend a retailer for dual opteron systems in the Benelux? One who might understand the notion of running FBSD on such a machine? Most of the server retailers I can find online just push HP or IBM boxes with precious little information about what's inside the box or what works. -- These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 21:19:15 2005 Return-Path: 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 191DB16A4CE for ; Thu, 5 May 2005 21:19:15 +0000 (GMT) Received: from maltanet.net (mailer1.maltanet.net [194.158.37.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1B4F43D70 for ; Thu, 5 May 2005 21:19:13 +0000 (GMT) (envelope-from peterk@maltanet.net) Received: (qmail 11750 invoked by uid 515); 5 May 2005 21:27:59 -0000 Received: from unknown (HELO [195.158.82.156]) ([195.158.82.156]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 5 May 2005 21:27:58 -0000 Message-ID: <427A8DD0.4020200@maltanet.net> Date: Thu, 05 May 2005 23:19:12 +0200 From: Peter Korsten User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Toll, Eric" , freebsd-amd64@FreeBSD.org References: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> In-Reply-To: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 21:19:15 -0000 Toll, Eric wrote: > 8006-2LP KIT ESCALADE 8006-2LP 1 141.47 141.47 > WD2500SD WD CAVIAR 250GB RAID ED.SATA-3 2 149.98 299.96 > GA-7A8DW SERVER BOARDAMD 81118131+81 1 340.86 340.86 > TITAN 550 ANTEC TITAN SERIES 550 CASE 1 209.87 209.87 > OSA242AUBOX OPTERON DP SERVER 242 PIB-R 2 217.77 435.54 > KRX3200AK2/1G 1GB KIT(2X512)DDR400 REG HY 1 415.80 415.80 > > Not bad for around $2,000.00 USD Eh? My Athlon64 2.2 GHz system with 1 GB RAM, a simple CD-ROM, Asus A8N-SLI motherboard, Asus Extreme 6800 GT PCIe video card, 200 GB Seagate Barracuda S-ATA, some Antec case and a wireless Logitech desktop set me back 1275 euro. And that was 455 euro for the video card. Admittedly, I tried to keep that a budget system (I kid ye not). But how about waiting a bit and getting a dual core AMD chip? - Peter From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 21:22:11 2005 Return-Path: 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 BEE6A16A4CE for ; Thu, 5 May 2005 21:22:11 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 508B543D39 for ; Thu, 5 May 2005 21:22:11 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 7F26CF7B3 for ; Thu, 5 May 2005 15:22:10 -0600 (MDT) Date: Thu, 5 May 2005 15:22:10 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050505152210.582dc016.kgunders@teamcool.net> In-Reply-To: <427A8DD0.4020200@maltanet.net> References: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> <427A8DD0.4020200@maltanet.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 21:22:11 -0000 On Thu, 05 May 2005 23:19:12 +0200 Peter Korsten wrote: > Toll, Eric wrote: > > > 8006-2LP KIT ESCALADE 8006-2LP 1 141.47 141.47 > > WD2500SD WD CAVIAR 250GB RAID ED.SATA-3 2 149.98 299.96 > > GA-7A8DW SERVER BOARDAMD 81118131+81 1 340.86 340.86 > > TITAN 550 ANTEC TITAN SERIES 550 CASE 1 209.87 209.87 > > OSA242AUBOX OPTERON DP SERVER 242 PIB-R 2 217.77 435.54 > > KRX3200AK2/1G 1GB KIT(2X512)DDR400 REG HY 1 415.80 415.80 > > > > Not bad for around $2,000.00 USD Eh? > > My Athlon64 2.2 GHz system with 1 GB RAM, a simple CD-ROM, Asus A8N-SLI > motherboard, Asus Extreme 6800 GT PCIe video card, 200 GB Seagate > Barracuda S-ATA, some Antec case and a wireless Logitech desktop set me > back 1275 euro. And that was 455 euro for the video card. > > Admittedly, I tried to keep that a budget system (I kid ye not). But how > about waiting a bit and getting a dual core AMD chip? Loverly, but have you priced those puppies?? I suspect we're gonna have to wait for more than a bit for them to get down to w/in reason for all but the high end guys... -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Thu May 5 21:27:13 2005 Return-Path: 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 AEE1216A4CE for ; Thu, 5 May 2005 21:27:13 +0000 (GMT) Received: from maltanet.net (mailer2.maltanet.net [194.158.37.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9039B43DB7 for ; Thu, 5 May 2005 21:27:12 +0000 (GMT) (envelope-from peterk@maltanet.net) Received: (qmail 18429 invoked by uid 516); 5 May 2005 21:27:16 -0000 Received: from 195.158.82.156 by mailer2.maltanet.net (envelope-from , uid 509) with qmail-scanner-1.25st (perlscan: 1.25st. Clear:RC:1(195.158.82.156):. Processed in 0.291596 secs); 05 May 2005 21:27:16 -0000 Received: from unknown (HELO [195.158.82.156]) ([195.158.82.156]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 5 May 2005 21:27:16 -0000 Message-ID: <427A8FB1.40308@maltanet.net> Date: Thu, 05 May 2005 23:27:13 +0200 From: Peter Korsten User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <9BC86C67C3AF7646B9C5382020457A9456E8CF@VIP10-WIN2K> <427A8DD0.4020200@maltanet.net> <20050505152210.582dc016.kgunders@teamcool.net> In-Reply-To: <20050505152210.582dc016.kgunders@teamcool.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2005 21:27:13 -0000 Ken Gunderson wrote: >>Admittedly, I tried to keep that a budget system (I kid ye not). But how >>about waiting a bit and getting a dual core AMD chip? > > Loverly, but have you priced those puppies?? I suspect we're gonna > have to wait for more than a bit for them to get down to w/in reason > for all but the high end guys... No, haven't checked them yet. This computer is still so new, it smells like it just came out of the box. My wife would kill me if I would mention upgrading. :) And it does 120 fps in Counter-Strike: Source at 1024x768 and everything maxed out... it's fast enough for now. - Peter From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 02:01:10 2005 Return-Path: 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 8CFD816A4CE for ; Fri, 6 May 2005 02:01:10 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEB3D43D96 for ; Fri, 6 May 2005 02:01:09 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 4EC7478C70 for ; Thu, 5 May 2005 22:03:36 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80025-08 for ; Thu, 5 May 2005 22:03:31 -0400 (EDT) Received: from dementia.afflictions.org (unknown [172.19.206.152]) by pandora.afflictions.org (Postfix) with ESMTP id 9D7FA78C5F for ; Thu, 5 May 2005 22:03:30 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 8F27F33C79; Thu, 5 May 2005 22:01:02 -0400 (EDT) Date: Thu, 5 May 2005 22:01:02 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050506020102.GA83574@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Tyan K8WE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 02:01:10 -0000 After all the speculation on boards recently, and the hubbub about avoiding and not avoiding nForce-based motherboards, I found myself in posession of the Tyan K8WE. I'll leave generic hardware impressions aside, and focus on the functionality... (note that all this has been posted to ): The board actually works surprisingly well. I was expecting to have a much bigger headache getting everything up and going. 5.3 *does* seem to work a little bit better for some reason (I originally thought ACPI regression, but I'm currently running RELENG_5 cvsup'ed this afternoon with ACPI). The on-board nVidia BGE controllers *DO NOT WORK* with ports/nvnet. You *will* need to have a PCI (/PCI-X) Ethernet card to use networking. I'm currently using an Intel 82550 Pro/100 card in a PCI-X slot just fine. My sound drivers from opensound.com don't work. That's something I'll chase down with them. I cannot boot into single-user mode in 5.4. The box just doesn't take input from the keyboard (I haven't tried serial console) when specifying the root shell to use. Oddly, hitting CTRL+ALT+DEL will successfully reboot the machine (i.e. FreeBSD will go through its shutdown process). Other than that, the board works quite well. It took me most of the day to get it going, and I'm still not /convinced/ there's no ACPI issues hanging around, but there's no complaints in the dmesg, and everything's working fine. It's done a few buildworlds (and currently rebuilding firefox) under the current RELENG_5 build, so it seems to be moderately stable. - Damian From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 06:04:27 2005 Return-Path: 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 85E7016A4CE for ; Fri, 6 May 2005 06:04:27 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2412443D7C for ; Fri, 6 May 2005 06:04:27 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DTvwo-000P0g-4f for freebsd-amd64@freebsd.org; Fri, 06 May 2005 09:04:26 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 May 2005 09:04:25 +0300 From: Danny Braniss Message-ID: Subject: max Gb of phys. memory? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 06:04:27 -0000 hi all, I need to set up a box with 'allot' of phys. memory. so far im finding that the amount of memory is per cpu, ie: 8Gb per cpu Appart from the 'efficiency' view (memory bandwith), are there other conciderations? danny From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 13:20:01 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDB4516A4D3 for ; Fri, 6 May 2005 13:20:01 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9996943D46 for ; Fri, 6 May 2005 13:20:01 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j46DK1Uw091195 for ; Fri, 6 May 2005 13:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j46DK1PC091194; Fri, 6 May 2005 13:20:01 GMT (envelope-from gnats) Resent-Date: Fri, 6 May 2005 13:20:01 GMT Resent-Message-Id: <200505061320.j46DK1PC091194@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Niall Douglas Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B7D016A4D3 for ; Fri, 6 May 2005 13:16:56 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED5BE43D2D for ; Fri, 6 May 2005 13:16:55 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j46DGtdr014136 for ; Fri, 6 May 2005 13:16:55 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j46DGtRk014134; Fri, 6 May 2005 13:16:55 GMT (envelope-from nobody) Message-Id: <200505061316.j46DGtRk014134@www.freebsd.org> Date: Fri, 6 May 2005 13:16:55 GMT From: Niall Douglas To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/80691: amd64 kernel hangs on load X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 13:20:02 -0000 >Number: 80691 >Category: amd64 >Synopsis: amd64 kernel hangs on load >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 06 13:20:01 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Niall Douglas >Release: 5.4 RC4, 6.0 snapshot 2 >Organization: >Environment: Can't get as far as issuing a uname >Description: Attempting to install from CD amd64 FreeBSD 5.3, 5.4 RC4 or 6.0 on my Athlon 64 laptop causes the kernel to hang just after the loader prompt, irrespective of whether I disable ACPI, enable debug mode or any other option on the menu. Linux for amd64 works just fine. i386 FreeBSD works just fine, just not amd64 FreeBSD. Spec is: Clevo D400J, Mobile Athlon 3400 with VIA K8M800 chipset and S3 Unichrome graphics. It has 1Gb of RAM and is pretty new - I bought it a few weeks ago. It's a pretty vanilla athlon64 laptop. It does NOT have a floppy drive. >How-To-Repeat: Just try installing any FreeBSD mentioned above on this kind of laptop. It hangs on kernel load. >Fix: Is it possible that Mobile Athlon 64's are not supported? It's definitely an Athlon NOT a Sempron as I have x64 Linux running on it too. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 15:17:17 2005 Return-Path: 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 B5A3A16A4D3 for ; Fri, 6 May 2005 15:17:17 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8683B43D46 for ; Fri, 6 May 2005 15:17:17 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j46FGwx6024604; Fri, 6 May 2005 08:16:58 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j46FGvtf024603; Fri, 6 May 2005 08:16:57 -0700 (PDT) (envelope-from obrien) Date: Fri, 6 May 2005 08:16:57 -0700 From: "David O'Brien" To: Danny Braniss Message-ID: <20050506151657.GA24493@dragon.NUXI.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: max Gb of phys. memory? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 15:17:17 -0000 On Fri, May 06, 2005 at 09:04:25AM +0300, Danny Braniss wrote: > I need to set up a box with 'allot' of phys. memory. so far > im finding that the amount of memory is per cpu, ie: 8Gb per cpu You have 4 or 8 DIMM sockets per CPU, depending on the motherboard. That is the only limit pertaining to the CPU. Some motherboards can handle 4GB DIMM's, others 2GB DIMM's, yet others only 1GB DIMM's. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 15:44:12 2005 Return-Path: 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 D1C7816A4D4; Fri, 6 May 2005 15:44:12 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 843B243D9B; Fri, 6 May 2005 15:44:12 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DU4zr-0009fb-M7; Fri, 06 May 2005 18:44:11 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-amd64@freebsd.org In-Reply-To: Message from "David O'Brien" <20050506151657.GA24493@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 May 2005 18:44:11 +0300 From: Danny Braniss Message-ID: Subject: Re: max Gb of phys. memory? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 15:44:12 -0000 > On Fri, May 06, 2005 at 09:04:25AM +0300, Danny Braniss wrote: > > I need to set up a box with 'allot' of phys. memory. so far > > im finding that the amount of memory is per cpu, ie: 8Gb per cpu > > You have 4 or 8 DIMM sockets per CPU, depending on the motherboard. > That is the only limit pertaining to the CPU. Some motherboards can > handle 4GB DIMM's, others 2GB DIMM's, yet others only 1GB DIMM's. ok, i guess i havet to refrase question this is a dual cpu amd board, http://www.sun.com/servers/entry/v20z/specificati ons.jsp under Main Memory, it says: ... (4 dimm slots per processor ...) so Q: can ONE process, take advantage of more than 8Gb? btw, i had such a box last week, and run 5.4 very nicely - appart from being a bit noisy, which i was informed is fixed in the newer boxes :-) danny From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 15:47:50 2005 Return-Path: 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 DE1C816A4D4 for ; Fri, 6 May 2005 15:47:50 +0000 (GMT) Received: from godzilla.vipstructures.com (godzilla.vipstructures.com [66.195.71.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1C4A43D99 for ; Fri, 6 May 2005 15:47:49 +0000 (GMT) (envelope-from etoll@vipstructures.com) Received: from localhost (localhost.vipstructures.com [127.0.0.1]) by godzilla.vipstructures.com (Postfix) with ESMTP id 5084E2841F for ; Fri, 6 May 2005 11:47:49 -0400 (EDT) Received: from godzilla.vipstructures.com ([127.0.0.1])port 10024) with ESMTP id 45554-03 for ; Fri, 6 May 2005 11:47:49 -0400 (EDT) Received: from mothra.vipstructures.com (mothra.vipstructures.com [192.168.1.3]) by godzilla.vipstructures.com (Postfix) with ESMTP id 06EA42841D for ; Fri, 6 May 2005 11:47:49 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C55252.F4360E4B" Date: Fri, 6 May 2005 11:47:48 -0400 Message-ID: <9BC86C67C3AF7646B9C5382020457A9456E8DF@VIP10-WIN2K> From: "Toll, Eric" To: X-Antivirus: checked by Norton Anti Virus X-MTA-Mailer: Postfix 2 by Wietse Venema - http://www.postfix.org X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on godzilla.vipstructures.com X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: RE: max Gb of phys. memory? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 15:47:51 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C55252.F4360E4B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: owner-freebsd-amd64@freebsd.org=20 > [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of David O'Brien > Sent: Friday, May 06, 2005 11:17 AM > To: Danny Braniss > Cc: freebsd-amd64@freebsd.org > Subject: Re: max Gb of phys. memory? >=20 > On Fri, May 06, 2005 at 09:04:25AM +0300, Danny Braniss wrote: > > I need to set up a box with 'allot' of phys. memory. so far im=20 > > finding that the amount of memory is per cpu, ie: 8Gb per cpu >=20 > You have 4 or 8 DIMM sockets per CPU, depending on the motherboard. > That is the only limit pertaining to the CPU. Some=20 > motherboards can handle 4GB DIMM's, others 2GB DIMM's, yet=20 > others only 1GB DIMM's. >=20 > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ One of the expensive Tyan boards I looked at supported 16Gb Ram, so I = can safely assume that the AMD-64 version will use all of this memeory? (8 DIMM = slots x 2Gb ea) I'm assuming the limit would be hardware limited as FreeBSD-AMD64 should = support 128Gb Ram?? As for my FreeBSD box, {which I only got some of the components in = today!} it will only have 1Gb for starters. (see attached) Boy that Kingston Registered ECC DDR400 1Gb kit was fine = looking, black heat sync's and gold plated contacts. It was like $450 USD for the = 1Gb Kit, but it was in stock, and I didn't want to go to the ends of = the earth to skimp... The last thing I wanted to worry about was poor = memory quality. Eric =20 ------_=_NextPart_001_01C55252.F4360E4B-- From owner-freebsd-amd64@FreeBSD.ORG Fri May 6 23:52:17 2005 Return-Path: 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 D668F16A4D4 for ; Fri, 6 May 2005 23:52:17 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 021B043D9E for ; Fri, 6 May 2005 23:52:17 +0000 (GMT) (envelope-from davidviii@gmx.de) Received: (qmail invoked by alias); 06 May 2005 23:52:15 -0000 Received: from dsl-082-082-189-236.arcor-ip.net (EHLO localhost) [82.82.189.236] by mail.gmx.net (mp001) with SMTP; 07 May 2005 01:52:15 +0200 X-Authenticated: #18680655 To: freebsd-amd64@freebsd.org From: David Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Sat, 07 May 2005 01:54:53 +0200 Message-ID: User-Agent: Opera M2/7.54 (Win32, build 3870) X-Y-GMX-Trusted: 0 Subject: X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 23:52:18 -0000 -- Erbärmlich ist jener Schüler, der seinen Meister nicht übertrifft. (Leonardo Da Vinci) From owner-freebsd-amd64@FreeBSD.ORG Sat May 7 18:24:38 2005 Return-Path: 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 E6FD916A4DB for ; Sat, 7 May 2005 18:24:38 +0000 (GMT) Received: from netcoop.nl (netcoop.nl [62.148.165.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C43A43D8C for ; Sat, 7 May 2005 18:24:37 +0000 (GMT) (envelope-from andreas@heijdendael.nl) Received: by netcoop.nl (Postfix, from userid 33) id 9211F141C4; Sat, 7 May 2005 20:26:05 +0200 (CEST) Received: from 84.119.155.61 (SquirrelMail authenticated user andreas.heijdendael.nl) by mail.netcoop.nl with HTTP; Sat, 7 May 2005 20:26:05 +0200 (CEST) Message-ID: <3845.84.119.155.61.1115490365.squirrel@mail.netcoop.nl> Date: Sat, 7 May 2005 20:26:05 +0200 (CEST) From: andreas@heijdendael.nl To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Weird keybaord issue in releng_5 (5.4-Stable) on Asus K8V Deluxe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2005 18:24:39 -0000 Hi there, Just installed FreeBSD 5.3 from the CD, had some trouble doing it over the network because of DHCP quirks in the sk driver (that's my 'feeling') but ok, it's running now. As I want an updated system I started following the manual to do a full makeworld and get my system up to date. Everything goes fine, compiling the kernel in 7 minutes, world in 51. What more could I wish for? The problem starts after make installkernel and the subsequent reboot into single usermode. The kernel boots just fine and finally prompts for the location of your favourite shell or hit enter for /bin/sh. Hitting enter results in nothing. All keys except the caps-lock, scroll-loc and num-loc (which seem to be unaffected, the lights start burning when pressing them) refuse to do anything. So the only option I have at that point is a forcefull reboot, reboot into the old kernel (which works just fine) and redo the whole thing (except the make buildworld). The GENERIC config file states: # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse Seems pretty allright to me. less /sys/conf/newvers.sh comes up with 5.4 stable (check what version is actually CVSup-ed when using RELENG_5 in cvsupfile). Done that before so that's not an issue either. Unfortunately I cannot give you the output of /var/run/boot/dmesg since it is being overwritten every time you boot and since my keyboard doesn't work I can't move it out of the way. Booting with debug messages would be an option but I don't know how to switch it on from the bootprompt. I'll go search fot that in a minute. In the meantime I hope somebody else here has had the same problem and fixed it. Or knows a workaround (don't have a USB keyboard so that's not an option (-; ) Thanks a lot already!! Greetings, Andreas ps: System is ASUS k8V Deluxe, no exotic hardware or memory configuration, just a hell of a lot USB devices (which all work fine). Running stock kernel from installation CD now. (FreeBSD amd64bsd 5.3-RELEASE FreeBSD 5.3-RELEASE) From owner-freebsd-amd64@FreeBSD.ORG Sat May 7 18:35:30 2005 Return-Path: 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 6A9B516A4DB for ; Sat, 7 May 2005 18:35:30 +0000 (GMT) Received: from hex.athame.co.uk (guru164.netsonic.fi [194.29.193.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 161AD43D96 for ; Sat, 7 May 2005 18:35:30 +0000 (GMT) (envelope-from andy@athame.co.uk) Received: from ping.int.athame.co.uk ([192.168.1.8]) by hex.athame.co.uk with esmtp (Exim 4.50 (FreeBSD)) id 1DUU96-000HdC-H2; Sat, 07 May 2005 21:35:24 +0300 From: Andy Fawcett To: freebsd-amd64@freebsd.org Date: Sat, 7 May 2005 21:35:53 +0300 User-Agent: KMail/1.8 References: <3845.84.119.155.61.1115490365.squirrel@mail.netcoop.nl> In-Reply-To: <3845.84.119.155.61.1115490365.squirrel@mail.netcoop.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505072135.54355.andy@athame.co.uk> Subject: Re: Weird keybaord issue in releng_5 (5.4-Stable) on Asus K8V Deluxe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2005 18:35:30 -0000 On Saturday 07 May 2005 21:26, andreas@heijdendael.nl wrote: > Hi there, > > The kernel boots just fine > and finally prompts for the location of your favourite shell or hit > enter for /bin/sh. Hitting enter results in nothing. All keys except > the caps-lock, scroll-loc and num-loc (which seem to be unaffected, > the lights start burning when pressing them) refuse to do anything. You just hit a problem in relemg_5 that was announced to the -stable list yesterday. See Ken Smith's post entitled "HEADS-UP: Problem with RELENG_5{_4}" A fix is being worked on. In the meantime, you're probably safer sticking with the old setup for now. -- Andy Fawcett | andy@athame.co.uk | tap@kde.org "In an open world without walls and fences, | tap@lspace.org we wouldn't need Windows and Gates." -- anon | tap@fruitsalad.org From owner-freebsd-amd64@FreeBSD.ORG Sat May 7 19:47:04 2005 Return-Path: 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 21BA516A4DD for ; Sat, 7 May 2005 19:47:04 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9836A43D91 for ; Sat, 7 May 2005 19:47:03 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so639867rng for ; Sat, 07 May 2005 12:47:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nfLjQOodGRmTOWGSUIbHFHeMOAtr8Jrur+KgQPH7Sb4QEHG6hJOJC+bkI01UQns989pE5i2WkJh1GrUm/c3bleSRNGOAI2Aq2BTM0k0ui6QHnu3mRIIN2LDSyZ1f0dShoYbig1aMjAZVZsTBrJ3PoQ3ibn2l53E14rZheiHFa9o= Received: by 10.38.151.37 with SMTP id y37mr746456rnd; Sat, 07 May 2005 12:47:03 -0700 (PDT) Received: by 10.38.149.53 with HTTP; Sat, 7 May 2005 12:47:03 -0700 (PDT) Message-ID: Date: Sat, 7 May 2005 21:47:03 +0200 From: Claus Guttesen To: "andreas@heijdendael.nl" In-Reply-To: <3845.84.119.155.61.1115490365.squirrel@mail.netcoop.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <3845.84.119.155.61.1115490365.squirrel@mail.netcoop.nl> cc: freebsd-amd64@freebsd.org Subject: Re: Weird keybaord issue in releng_5 (5.4-Stable) on Asus K8V Deluxe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Claus Guttesen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2005 19:47:04 -0000 > As I want an updated system I started following the manual to do a full > makeworld and get my system up to date. Everything goes fine, compiling > the kernel in 7 minutes, world in 51. What more could I wish for? The > problem starts after make installkernel and the subsequent reboot into > single usermode. The kernel boots just fine and finally prompts for the > location of your favourite shell or hit enter for /bin/sh. Hitting enter > results in nothing. All keys except the caps-lock, scroll-loc and num-loc Problems are reported related to the tty-code introduced to fix some problems late in the 5-4-release-process. There is work going on to resolve the issue. regards Claus