From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 07:36:13 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7756716A41F for ; Sun, 29 May 2005 07:36:13 +0000 (GMT) (envelope-from xxjack12xx@doramail.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FD5543D1F for ; Sun, 29 May 2005 07:36:13 +0000 (GMT) (envelope-from xxjack12xx@doramail.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id DCA781800130 for ; Sun, 29 May 2005 07:36:12 +0000 (GMT) X-OB-Received: from unknown (205.158.62.133) by wfilter.us4.outblaze.com; 29 May 2005 07:36:12 -0000 Received: by ws5-3.us4.outblaze.com (Postfix, from userid 1001) id D18CF23D02; Sun, 29 May 2005 07:36:12 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; A1.17; B2.12; Q2.03) Received: from [66.245.242.52] by ws5-3.us4.outblaze.com with http for xxjack12xx@doramail.com; Sat, 28 May 2005 23:36:12 -0800 X-Mailer: doramail.com webmail From: "Jack L." To: freebsd-amd64@FreeBSD.org, freebsd-current@FreeBSD.org Date: Sat, 28 May 2005 23:36:12 -0800 X-Originating-Ip: 66.245.242.52 X-Originating-Server: ws5-3.us4.outblaze.com Message-Id: <20050529073612.D18CF23D02@ws5-3.us4.outblaze.com> Cc: Subject: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 07:36:13 -0000 Hi, I am currently using a Intel EM64T processor (Intel Pentium 4 640 3.2gh= z). Is this a AMD64 platform or i386 platform? ~Jack~ --=20 _______________________________________________ Get your free email from www.doramail.com with 30 Megs of disk space in web= hosting and e-mail storage! Powered by Outblaze From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 07:51:26 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D9BE16A41C for ; Sun, 29 May 2005 07:51:26 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: from salvador.pacific.net.sg (salvador.pacific.net.sg [203.120.90.219]) by mx1.FreeBSD.org (Postfix) with SMTP id 96F2743D1F for ; Sun, 29 May 2005 07:51:25 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 27864 invoked from network); 29 May 2005 07:51:23 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by salvador with SMTP; 29 May 2005 07:51:23 -0000 Received: from [192.168.0.107] ([210.24.246.101]) by maxwell2.pacific.net.sg with ESMTP id <20050529075123.OKZW1130.maxwell2.pacific.net.sg@[192.168.0.107]>; Sun, 29 May 2005 15:51:23 +0800 Message-ID: <4299743B.5070105@pacific.net.sg> Date: Sun, 29 May 2005 15:50:19 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050514) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jack L." References: <20050529073612.D18CF23D02@ws5-3.us4.outblaze.com> In-Reply-To: <20050529073612.D18CF23D02@ws5-3.us4.outblaze.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 07:51:26 -0000 Hi, Jack L. wrote: > Hi, I am currently using a Intel EM64T processor (Intel Pentium 4 640 3.2ghz). Is this a AMD64 platform or i386 platform? > You can run both on it. Only AMD64 gives you the 64 bit extensions. Erich From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 08:00:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2CC716A41C for ; Sun, 29 May 2005 08:00:29 +0000 (GMT) (envelope-from xxjack12xx@doramail.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CCB43D48 for ; Sun, 29 May 2005 08:00:29 +0000 (GMT) (envelope-from xxjack12xx@doramail.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 777D118001C1 for ; Sun, 29 May 2005 08:00:29 +0000 (GMT) X-OB-Received: from unknown (205.158.62.156) by wfilter.us4.outblaze.com; 29 May 2005 08:00:29 -0000 Received: by ws5-7.us4.outblaze.com (Postfix, from userid 1001) id 687192B2B86; Sun, 29 May 2005 08:00:29 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; A1.17; B2.12; Q2.03) Received: from [66.245.242.52] by ws5-7.us4.outblaze.com with http for xxjack12xx@doramail.com; Sun, 29 May 2005 00:00:29 -0800 X-Mailer: doramail.com webmail From: "Jack L." To: "Erich Dollansky" Date: Sun, 29 May 2005 00:00:29 -0800 X-Originating-Ip: 66.245.242.52 X-Originating-Server: ws5-7.us4.outblaze.com Message-Id: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> Cc: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 08:00:29 -0000 ----- Original Message ----- From: "Erich Dollansky" To: "Jack L." Subject: Re: Intel EM64T Processor Platform Date: Sun, 29 May 2005 15:50:19 +0800 >=20 > Hi, >=20 >=20 > Jack L. wrote: > > Hi, I am currently using a Intel EM64T processor (Intel Pentium 4=20 > > 640 3.2ghz). Is this a AMD64 platform or i386 platform? > > > You can run both on it. >=20 > Only AMD64 gives you the 64 bit extensions. >=20 > Erich What cpu type should I use for make.conf and the kernel if I want to use th= e AMD64 platform? ~Jack~ --=20 _______________________________________________ Get your free email from www.doramail.com with 30 Megs of disk space in web= hosting and e-mail storage! Powered by Outblaze From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 08:14:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7513216A41C; Sun, 29 May 2005 08:14:47 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id E115443D1F; Sun, 29 May 2005 08:14:46 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr15.xs4all.nl (8.13.3/8.13.3) with ESMTP id j4T8EhNX019200; Sun, 29 May 2005 10:14:43 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id EC0616287; Sun, 29 May 2005 10:14:42 +0200 (CEST) Date: Sun, 29 May 2005 10:14:42 +0200 From: Roland Smith To: "Jack L." Message-ID: <20050529081442.GA99205@slackbox.xs4all.nl> Mail-Followup-To: "Jack L." , Erich Dollansky , freebsd-current@freebsd.org, freebsd-amd64@freebsd.org References: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 08:14:47 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 29, 2005 at 12:00:29AM -0800, Jack L. wrote: >=20 > > Only AMD64 gives you the 64 bit extensions. > >=20 > > Erich=20 > What cpu type should I use for make.conf and the kernel if I want to > use the AMD64 platform? You do not need to have anything special in make.conf, and the GENERIC kernel for amd64 contains the necessary 'machine' and 'cpu' paramaters. However, if you want to use the amd64 version, you should install that from CD, not the i386 version. I'm not sure if it is even possible to convert (recompile) an existing install from i386 to amd64. This has been discussed on the amd64 mailinglist before. Check the archives. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCmXnyEnfvsMMhpyURAr/8AJ91C2rS6Ckk+cUNS7ILaiM0B4D8xwCffxA7 1xlmmj0FGn9J55t1p+/fL3w= =T2gA -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 08:43:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CF3616A41C for ; Sun, 29 May 2005 08:43:40 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-144-221-242.jan.bellsouth.net [70.144.221.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A29F43D1F for ; Sun, 29 May 2005 08:43:39 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id F38AC21050; Sun, 29 May 2005 03:43:37 -0500 (CDT) Date: Sun, 29 May 2005 03:43:37 -0500 From: "Matthew D. Fuller" To: "Jack L." , Erich Dollansky , freebsd-amd64@freebsd.org Message-ID: <20050529084337.GA61696@over-yonder.net> References: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> <20050529081442.GA99205@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050529081442.GA99205@slackbox.xs4all.nl> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 08:43:40 -0000 On Sun, May 29, 2005 at 10:14:42AM +0200 I heard the voice of Roland Smith, and lo! it spake thus: > > I'm not sure if it is even possible to convert (recompile) an > existing install from i386 to amd64. I did it on 5.3-RELEASE, since amd64 doesn't have install floppies. The process went something like: - Cross-build the world and kernel (TARGET_ARCH=amd64). - Temporarily appropriate your swap partition, newfs it, mount it on /mnt. - Do an installworld and installkernel DESTDIR=/mnt. - Reboot and fiddle around in the boot loader to set the right rootdev to boot off that partition. I can't remember which param needs tweaking... - Mount your regular partitions under /mnt (you may have to make symlinks for src and obj to get it to work right). - Do another installworld and installkernel onto /mnt (this /mnt now being your real filesystems). - Boot normally. Reclaim your swap partition. Some notes: - These installworlds may need to be done with make -k, since there's some weirdness I came across. - You may have to do another buildworld/installworld afterward, just to make sure everything is clean. The cross-build, for instance, didn't seem to build the i386 compatibility libraries and dynamic loader. And there's the errors that made me -k the installworlds... A fairly long process, but not too difficult. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 09:52:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3B5116A41C for ; Sun, 29 May 2005 09:52:01 +0000 (GMT) (envelope-from xxjack12xx@doramail.com) Received: from webmail-outgoing.us4.outblaze.com (webmail-outgoing.us4.outblaze.com [205.158.62.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id B382643D1D for ; Sun, 29 May 2005 09:52:01 +0000 (GMT) (envelope-from xxjack12xx@doramail.com) Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 1558C18001B3 for ; Sun, 29 May 2005 09:52:01 +0000 (GMT) X-OB-Received: from unknown (205.158.62.86) by wfilter.us4.outblaze.com; 29 May 2005 09:52:00 -0000 Received: by ws5-4.us4.outblaze.com (Postfix, from userid 1001) id A464523EF70; Sun, 29 May 2005 09:52:00 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; A1.17; B2.12; Q2.03) Received: from [66.245.242.199] by ws5-4.us4.outblaze.com with http for xxjack12xx@doramail.com; Sun, 29 May 2005 01:52:00 -0800 X-Mailer: doramail.com webmail From: "Jack L." To: "Matthew D. Fuller" , "Erich Dollansky" , freebsd-amd64@freebsd.org Date: Sun, 29 May 2005 01:52:00 -0800 X-Originating-Ip: 66.245.242.199 X-Originating-Server: ws5-4.us4.outblaze.com Message-Id: <20050529095200.A464523EF70@ws5-4.us4.outblaze.com> Cc: Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 09:52:02 -0000 I just tried installing from cd, got a kernel panic, going to try doing the= steps you mentioned below in a few. Do the old ports still work or will th= ey all need to be recompiled? ----- Original Message ----- From: "Matthew D. Fuller" To: "Jack L." , "Erich Dollansky" , freebsd-amd64@freebsd.org Subject: Re: Intel EM64T Processor Platform Date: Sun, 29 May 2005 03:43:37 -0500 >=20 > On Sun, May 29, 2005 at 10:14:42AM +0200 I heard the voice of > Roland Smith, and lo! it spake thus: > > > > I'm not sure if it is even possible to convert (recompile) an > > existing install from i386 to amd64. >=20 > I did it on 5.3-RELEASE, since amd64 doesn't have install floppies. > The process went something like: >=20 > - Cross-build the world and kernel (TARGET_ARCH=3Damd64). > - Temporarily appropriate your swap partition, newfs it, mount it on > /mnt. > - Do an installworld and installkernel DESTDIR=3D/mnt. > - Reboot and fiddle around in the boot loader to set the right rootdev > to boot off that partition. I can't remember which param needs > tweaking... > - Mount your regular partitions under /mnt (you may have to make > symlinks for src and obj to get it to work right). > - Do another installworld and installkernel onto /mnt (this /mnt now > being your real filesystems). > - Boot normally. Reclaim your swap partition. >=20 > Some notes: > - These installworlds may need to be done with make -k, since there's > some weirdness I came across. > - You may have to do another buildworld/installworld afterward, just > to make sure everything is clean. The cross-build, for instance, > didn't seem to build the i386 compatibility libraries and dynamic > loader. And there's the errors that made me -k the installworlds... >=20 > A fairly long process, but not too difficult. >=20 >=20 > -- > Matthew Fuller (MF4839) | fullermd@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. ~Jack~ --=20 _______________________________________________ Get your free email from www.doramail.com with 30 Megs of disk space in web= hosting and e-mail storage! Powered by Outblaze From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 17:50:57 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8370916A41C; Sun, 29 May 2005 17:50:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 291B943D48; Sun, 29 May 2005 17:50:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 60E195148D; Sun, 29 May 2005 10:50:56 -0700 (PDT) Date: Sun, 29 May 2005 10:50:56 -0700 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050529175056.GA99318@xor.obsecurity.org> References: <20050510223636.GA49927@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <20050510223636.GA49927@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: amd64@FreeBSD.org, current@FreeBSD.org Subject: Re: Fatal trap 12 in exec_copyout_strings() X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 17:50:57 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 10, 2005 at 03:36:36PM -0700, Kris Kennaway wrote: > Got this on a dual amd64 with 8GB RAM running 6.0 from last week: >=20 > Fatal trap 12: page fault while in kernel mode > cpuid =3D 1; apic id =3D 01 > fault virtual address =3D 0xffffffffa9cdc000 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xffffffff8037759f > stack pointer =3D 0x10:0xffffffffba1637d0 > frame pointer =3D 0x10:0xffffffffba163820 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 52247 (sh) > [thread pid 52247 tid 100149 ] > Stopped at exec_copyout_strings+0x12f: > db> wh > Tracing pid 52247 tid 100149 td 0xffffff016e5724c0 > exec_copyout_strings() at exec_copyout_strings+0x12f > do_execve() at do_execve+0x39a > kern_execve() at kern_execve+0xab > execve() at execve+0x49 > syscall() at syscall+0x382 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (59, FreeBSD ELF64, execve), rip =3D 0x80090622c, rsp =3D 0x7= fffffffe058, rbp =3D 0xffffffff --- > db> I've got this panic twice more since. Kris --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCmgEAWry0BWjoQKURAphtAJ9Wu0+6Vyp3rttgYtox6tSSeNBJ8ACgvYNw OlxxIVonDW8aa5+FmSSJ4p4= =1Zw0 -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-amd64@FreeBSD.ORG Sun May 29 23:45:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 008D316A41C for ; Sun, 29 May 2005 23:45:58 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-152-70-73.jan.bellsouth.net [70.152.70.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA08E43D1D for ; Sun, 29 May 2005 23:45:58 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id A49D521020; Sun, 29 May 2005 18:45:56 -0500 (CDT) Date: Sun, 29 May 2005 18:45:56 -0500 From: "Matthew D. Fuller" To: "Jack L." Message-ID: <20050529234555.GA2528@over-yonder.net> References: <20050529095200.A464523EF70@ws5-4.us4.outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050529095200.A464523EF70@ws5-4.us4.outblaze.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: freebsd-amd64@freebsd.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2005 23:45:59 -0000 On Sun, May 29, 2005 at 01:52:00AM -0800 I heard the voice of Jack L., and lo! it spake thus: > > I just tried installing from cd, got a kernel panic, going to try > doing the steps you mentioned below in a few. Do the old ports still > work or will they all need to be recompiled? In theory, after you do the second build to get the lib32 compat stuff (or maybe that's correctly done in the cross-build now; I dunno), they should all Just Work(tm). CVSup was the only port I had installed, though. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 00:07:39 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D374516A41C; Mon, 30 May 2005 00:07:39 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6231E43D1D; Mon, 30 May 2005 00:07:39 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j4U086pH079062; Sun, 29 May 2005 20:08:06 -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 j4U07cjn044054; Sun, 29 May 2005 20:07:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4708F7306E; Sun, 29 May 2005 20:07:38 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050530000738.4708F7306E@freebsd-current.sentex.ca> Date: Sun, 29 May 2005 20:07:38 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 00:07:40 -0000 TB --- 2005-05-29 23:48:30 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-05-29 23:48:30 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-05-29 23:48:30 - cleaning the object tree TB --- 2005-05-29 23:49:05 - checking out the source tree TB --- 2005-05-29 23:49:05 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-05-29 23:49:05 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-05-29 23:55:04 - building world (CFLAGS=-O2 -pipe) TB --- 2005-05-29 23:55:04 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-29 23:55:04 - /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 [...] ln -fs /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/lib/libbsdxml.so.1 /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/usr/lib/libbsdxml.so sh /tinderbox/CURRENT/amd64/amd64/src/tools/install.sh -C -o root -g wheel -m 444 bsdxml.h /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/usr/include ===> lib/libkvm (depend,all,install) rm -f .depend mkdep -f .depend -a -DLIBC_SCCS -I/tinderbox/CURRENT/amd64/amd64/src/lib/libkvm /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm.c /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm_amd64.c /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm_file.c /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm_getloadavg.c /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm_getswapinfo.c /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm_proc.c In file included from /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm/kvm_proc.c:67: /home/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/tmp/usr/include/sys/sysent.h:35:23: bsm/audit.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/libkvm. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-05-30 00:07:38 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-05-30 00:07:38 - ERROR: failed to build world TB --- 2005-05-30 00:07:38 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 10:22:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8302316A41C; Mon, 30 May 2005 10:22:58 +0000 (GMT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.snsonline.net (icarus.snsonline.net [210.18.214.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id B073C43D58; Mon, 30 May 2005 10:22:57 +0000 (GMT) (envelope-from msergeant@snsonline.net) Received: from [127.0.0.1] (localhost [127.0.0.1]) by xyzzy.local (Postfix) with ESMTP id 4D2D3114355; Mon, 30 May 2005 13:59:53 +1000 (EST) Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mark Sergeant Date: Mon, 30 May 2005 13:59:51 +1000 To: freebsd-stable@FreeBSD.ORG X-Mailer: Apple Mail (2.730) Cc: freebsd-amd64@freebsd.org Subject: Named 9.3.1 caching problem AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 10:22:58 -0000 I've got a very unusual problem running a bind caching name server on AMD64. I've tried FreeBSD-5.4-p1 and 5.4-STABLE and nothing has helped. Named goes into a "crash" state once hit hits approx 120M of memory in use, at which point it chews 100% cpu and doesn't respond to any futher queries. If anyone has any idea on how I can fix this it would be much appreciated as it's a production system. The folliowing are the relevant config details ... system details FreeBSD zeus 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri May 27 08:50:14 EST 2005 root@zeus:/usr/obj/usr/src/sys/ZEUS amd64 dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #0: Fri May 27 08:50:14 EST 2005 root@zeus:/usr/obj/usr/src/sys/ZEUS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 250 (2392.55-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2146893824 (2047 MB) avail memory = 2062729216 (1967 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard netsmb_dev: loaded acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0x8080-0x80ff,0x8000-0x807f, 0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xfb100000-0xfb100fff irq 19 at device 0.0 on pci1 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfb101000-0xfb101fff irq 19 at device 0.1 on pci1 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f, 0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfd000000-0xfd00ffff,0xfd010000-0xfd01ffff irq 24 at device 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:25:1e:1b:ec bge1: mem 0xfd020000-0xfd02ffff,0xfd030000-0xfd03ffff irq 25 at device 1.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:11:25:1e:1b:ed pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x3000-0x300f mem 0xfd800000-0xfdffffff irq 28 at device 3.0 on pci3 twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 pci0: at device 11.1 (no driver attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console orm0: at iomem 0xcb000-0xcbfff,0xc9800-0xcafff, 0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: vendor 0x1267 product 0x0103, rev 1.10/1.00, addr 2, iclass 3/1 kbd0 at ukbd0 uhid0: vendor 0x1267 product 0x0103, rev 1.10/1.00, addr 2, iclass 3/1 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled acd0: CDROM at ata1-master PIO4 twed0: on twe0 twed0: 76323MB (156310528 sectors) SMP: AP CPU #1 Launched! named.conf options { directory "/etc/namedb"; pid-file "/var/run/named/pid"; dump-file "/var/dump/named_dump.db"; statistics-file "/var/stats/named.stats"; recursive-clients 2000; listen-on { 127.0.0.1; x.x.x.x; }; datasize 512M; max-cache-size 512M; }; logging { channel misc_logfile { file "/var/log/misc.log" versions 3 size 10M; severity info; print-category yes; print-severity yes; print-time yes; }; channel config_logfile { file "/var/log/config.log" versions 3 size 10M; severity info; print-category yes; print-severity yes; print-time yes; }; channel security_logfile { file "/var/log/security.log" versions 3 size 10M; severity info; print-category yes; print-severity yes; print-time yes; }; channel xfer_logfile { file "/var/log/xfer.log" versions 3 size 10M; severity info; print-category yes; print-severity yes; print-time yes; }; category default { misc_logfile; }; category config { config_logfile; }; category lame-servers { null; }; category notify { xfer_logfile; }; category queries { null; }; category security { security_logfile; }; category update { xfer_logfile; }; category xfer-in { xfer_logfile; }; category xfer-out { xfer_logfile; }; }; zone "." { type hint; file "named.root"; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "master/localhost.rev"; }; // RFC 3152 zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARP A" { type master; file "master/localhost-v6.rev"; }; // RFC 1886 -- deprecated zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT " { type master; file "master/localhost-v6.rev"; }; From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 11:01:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8027316A421 for ; Mon, 30 May 2005 11:01:51 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 541AC43D53 for ; Mon, 30 May 2005 11:01:51 +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 j4UB1pWY029951 for ; Mon, 30 May 2005 11:01:51 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4UB1oGR029944 for freebsd-amd64@freebsd.org; Mon, 30 May 2005 11:01:50 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 30 May 2005 11:01:50 GMT Message-Id: <200505301101.j4UB1oGR029944@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 11:01:51 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access 2 problems 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 o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load a [2005/05/10] amd64/80839 amd64 RELEASE 5.4 / libc: make buildworld fails o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/19] amd64/81272 amd64 JDK 1.5 port doesn't build. p [2005/05/19] amd64/81279 amd64 /usr/games/random returns every line o [2005/05/20] amd64/81325 amd64 KLD if_ath.ko: depends on ath_hal - not a 30 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 [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/11] amd64/80885 amd64 OpenGL hardware accel dont work on FreeBS o [2005/05/16] amd64/81089 amd64 FreeBSD 5.4 released version can not use 12 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 15:05:27 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBBC616A41C for ; Mon, 30 May 2005 15:05:27 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96C6B43D49 for ; Mon, 30 May 2005 15:05: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 22D9BF7C8 for ; Mon, 30 May 2005 09:05:26 -0600 (MDT) Date: Mon, 30 May 2005 09:05:25 -0600 From: Ken Gunderson To: freebsd-amd64@FreeBSD.org Message-Id: <20050530090525.246b0c35.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.11 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 15:05:27 -0000 Hello: On larger systems sporting several gigs of ram, what it the recommended swap scheme? I'm aware of the 2x ram rule of thumb and also that this rule is considered "old school" by many. And of course that you need at least as much swap as ram if you want to get a full dump... But other than that it seems we pretty much don't want/need to be swapping at all on modern machines. Curious what folks are doing in the modern world with larger systems. TIA -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 15:21:31 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F308016A41C; Mon, 30 May 2005 15:21:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A523C43D1D; Mon, 30 May 2005 15:21:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j4UFLvRo012272; Mon, 30 May 2005 11:21:58 -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 j4UFLTX4004601; Mon, 30 May 2005 11:21:29 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3289D7306E; Mon, 30 May 2005 11:21:29 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050530152129.3289D7306E@freebsd-current.sentex.ca> Date: Mon, 30 May 2005 11:21:29 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 15:21:31 -0000 TB --- 2005-05-30 13:10:27 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-05-30 13:10:27 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-05-30 13:10:27 - cleaning the object tree TB --- 2005-05-30 13:10:33 - checking out the source tree TB --- 2005-05-30 13:10:33 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-05-30 13:10:33 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-05-30 13:16:39 - building world (CFLAGS=-O2 -pipe) TB --- 2005-05-30 13:16:39 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-30 13:16:39 - /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-30 14:53:23 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-05-30 14:53:23 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-30 14:53:23 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon May 30 14:53:23 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 >>> Kernel build for GENERIC completed on Mon May 30 15:09:06 UTC 2005 TB --- 2005-05-30 15:09:06 - generating LINT kernel config TB --- 2005-05-30 15:09:06 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-05-30 15:09:06 - /usr/bin/make -B LINT TB --- 2005-05-30 15:09:06 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-05-30 15:09:06 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-05-30 15:09:06 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon May 30 15:09:06 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 -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-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c:122: error: `vga_pxlmouse_planar' undeclared here (not in a function) /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c:122: error: initializer element is not constant /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c:122: error: (near initialization for `egarndrsw.draw_mouse') /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c: In function `vga_rndrinit': /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c:511: error: `vga_pxlmouse_direct' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c:511: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/sys/dev/syscons/scvgarndr.c:511: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-05-30 15:21:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-05-30 15:21:29 - ERROR: failed to build lint kernel TB --- 2005-05-30 15:21:29 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 19:26:16 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5417216A41C for ; Mon, 30 May 2005 19:26:16 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC90C43D53 for ; Mon, 30 May 2005 19:26:15 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A47C6.dip.t-dialin.net [84.154.71.198]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j4UJQD8o027893 for ; Mon, 30 May 2005 21:26:13 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j4UJQAm0003098 for ; Mon, 30 May 2005 21:26:10 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.3/8.13.3) with ESMTP id j4UJQADJ018138 for ; Mon, 30 May 2005 21:26:10 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200505301926.j4UJQADJ018138@fire.jhs.private> to: amd64@freebsd.org From: "Julian Stacey" Organization: http://berklix.com Munich Unix, BSD, Internet Consultancy User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com/~jhs/ Date: Mon, 30 May 2005 21:26:10 +0200 Sender: jhs@flat.berklix.net Cc: Subject: Re. make cores on 5.4-RELEASE amd64 but not on i386, need a maintainer. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 19:26:16 -0000 FYI amd64 people: 5.4-RELEASE & 5.0-stable make on amd64 have a bug which results in: "Segmentation fault" (on my particular own Makefile, not on /usr/src). Upgrading make to current fixes it. Detail on current@ thread Message-id: <200505301502.j4UF28Ls027504@fire.jhs.private> http://lists.freebsd.org/pipermail/freebsd-current/2005-May/050704.html Follow up: If any, to current@ rather than amd64@ here please, (for all I know it may not even be amd64 specific, I just know it doesnt manifest on i386). - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 20:00:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6867C16A41F for ; Mon, 30 May 2005 20:00:46 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBC5143D48 for ; Mon, 30 May 2005 20:00:45 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so1577713rng for ; Mon, 30 May 2005 13:00:45 -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=sOdmAx65B5wAnvxdIfDsfcJYx0/bJB+OdqC2W2jP9Av4jFvupricrx81n6beiFNr5BcMykn1SYZM4Ok85oBiFuWhkieKSUTFVGZyCE4PJBemoCRVx5m7J9Ua/2HSb4S5jwfT6ah7f6wQqSpwSsRx/Hvv2ZgBMCRmhOF5jwqcPkM= Received: by 10.38.90.71 with SMTP id n71mr6363491rnb; Mon, 30 May 2005 13:00:45 -0700 (PDT) Received: by 10.38.149.57 with HTTP; Mon, 30 May 2005 13:00:45 -0700 (PDT) Message-ID: Date: Mon, 30 May 2005 22:00:45 +0200 From: Claus Guttesen To: freebsd-stable@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 Cc: Subject: isp and amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 30 May 2005 20:00:46 -0000 Hi. Had a buggy raidbox so when I had some downtime I phased in an Dell PE 2850 using the amd64-port and two qlogic 2300-hba's. No problem getting the server up but after some minutes after doing the background-fsck it simply rebooted. I had an i386-ditto which I then phased in instead which works (after almost two hours :-). Is the isp-driver not yet fully 4 GB-compliant? regards Claus From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 22:38:44 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 494A716A41C for ; Mon, 30 May 2005 22:38:44 +0000 (GMT) (envelope-from mr.skoe@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C84BF43D48 for ; Mon, 30 May 2005 22:38:43 +0000 (GMT) (envelope-from mr.skoe@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so1616073nzp for ; Mon, 30 May 2005 15:38:43 -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=IfQS8tGI0B8pBOwQqHxkELDBvpd5vD6n1TfXnMLWAPjMNc6d+lsBKBa7Nc/hafqp8y38eocNL+dQk/aHq8LI2gD3xY62jlNdML7mERJk9kMzZ6aHrd2mc0pT6AjlKIkWaaYop3wv9rHuDH1DdSImCr0LsmVLYoYUZUJCYdA2AMY= Received: by 10.36.4.7 with SMTP id 7mr1997427nzd; Mon, 30 May 2005 15:38:43 -0700 (PDT) Received: by 10.36.5.2 with HTTP; Mon, 30 May 2005 15:38:43 -0700 (PDT) Message-ID: Date: Tue, 31 May 2005 08:38:43 +1000 From: Mathew Schofield To: 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: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mathew Schofield List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 22:38:44 -0000 Is the AMD64 Version of FreeBSD Significantly faster then the i386 version? I am using Windows XP 64 Bit atm and it is *incredibly* faster then the 32 bit version. I am just curious to if FreeBSD's AMD64 Version is snappy and ... any good? --=20 This is a private letter and only the intended people may read this message. You may not store, quote or publish this document for any purposes. The data/information held within this message are for private use, and no one may disclose it. There are no guarentees that the information disclosed is accurate, or that the links/attached files will not be contaminated with Viruses. You use all links, and all attachments, at your own free will and thus risk. You have been warned. From owner-freebsd-amd64@FreeBSD.ORG Mon May 30 23:11:57 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58A5316A41C for ; Mon, 30 May 2005 23:11:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1335A43D49 for ; Mon, 30 May 2005 23:11:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 824F851F72; Mon, 30 May 2005 16:11:56 -0700 (PDT) Date: Mon, 30 May 2005 16:11:55 -0700 From: Kris Kennaway To: Ken Gunderson Message-ID: <20050530231155.GA43641@xor.obsecurity.org> References: <20050530090525.246b0c35.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20050530090525.246b0c35.kgunders@teamcool.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2005 23:11:57 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 30, 2005 at 09:05:25AM -0600, Ken Gunderson wrote: > Hello: >=20 > On larger systems sporting several gigs of ram, what it the recommended > swap scheme? I'm aware of the 2x ram rule of thumb and also that this > rule is considered "old school" by many. And of course that you need > at least as much swap as ram if you want to get a full dump... > But other than that it seems we pretty much don't want/need to be > swapping at all on modern machines. Curious what folks are doing in the > modern world with larger systems. I'd recommend as much swap as RAM (allowing for future expansion if you think you might one day add more RAM). You'll kick yourself if one day this machine encounters a FreeBSD bug and no-one is able to help you because you can't dump it. Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCm526Wry0BWjoQKURAoqHAKDuIhY5riYFgLcgL5dpwvykD0s0CACgqcc5 aun0tpzwYq9dd2RJYzsYzOw= =d65i -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 00:14:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA6B416A41C for ; Tue, 31 May 2005 00:14:42 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EBAA43D1D for ; Tue, 31 May 2005 00:14:42 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.0.2.R) with ESMTP id md50001447873.msg for ; Tue, 31 May 2005 01:09:55 +0100 Message-ID: <002001c56575$afdbe510$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Mathew Schofield" , References: Date: Tue, 31 May 2005 01:14:14 +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, Tue, 31 May 2005 01:09:55 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-amd64@freebsd.org X-MDAV-Processed: multiplay.co.uk, Tue, 31 May 2005 01:09:55 +0100 Cc: Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 00:14:43 -0000 You "incredibly" faster is more than likely due to a clean install as 64bit vs 32bit for the base OS makes very little difference and is actually slower in some parts. The speed of 64bit vs 32bit depends on the application used. Their are no hard and fast rules Steve ----- Original Message ----- From: "Mathew Schofield" Is the AMD64 Version of FreeBSD Significantly faster then the i386 version? I am using Windows XP 64 Bit atm and it is *incredibly* faster then the 32 bit version. I am just curious to if FreeBSD's AMD64 Version is snappy and ... any good? ================================================ 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 Tue May 31 00:53:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 318E116A41C for ; Tue, 31 May 2005 00:53:37 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC35443D49 for ; Tue, 31 May 2005 00:53:36 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 0247B78C75 for ; Mon, 30 May 2005 20:54:01 -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 10163-07 for ; Mon, 30 May 2005 20:53:54 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pandora.afflictions.org (Postfix) with ESMTP id 3A62C78C6D for ; Mon, 30 May 2005 20:53:54 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 4A2EF33C7B; Mon, 30 May 2005 20:53:26 -0400 (EDT) Date: Mon, 30 May 2005 20:53:26 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050531005326.GE28607@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <200505251317.22128.nb_root@videotron.ca> <429514AF.5000306@roq.com> <20050526155612.GA38421@xor.obsecurity.org> <2302.172.16.0.199.1117123959.squirrel@172.16.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2302.172.16.0.199.1117123959.squirrel@172.16.0.1> 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: amd64 optimized gcc? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 00:53:37 -0000 Thus spake Mike Jakubik (mikej@rogers.com) [26/05/05 12:13]: : > Google for 'placebo effect' :-) Unfortunately, leet optimization flags : > do not measurably effect everyday system performance, only specific : > CPU-intensive operations. : : Tell that to the Gentoo people :) "HOLY COW I'M TOTALLY GOING SO FAST OH F***" (My favourite bug report, ever.) From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 00:56:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF48316A41C for ; Tue, 31 May 2005 00:56:03 +0000 (GMT) (envelope-from ray@redshift.com) Received: from outgoing.redshift.com (outgoing.redshift.com [207.177.231.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D41843D49 for ; Tue, 31 May 2005 00:56:03 +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 52C1297066; Mon, 30 May 2005 17:56:03 -0700 (PDT) Message-Id: <3.0.1.32.20050530175629.00a77268@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Mon, 30 May 2005 17:56:29 -0700 To: Mathew Schofield , freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 00:56:03 -0000 Depends on what you are doing. I have tested i386 running on a single Xeon 2.4ghz against a dual AMD 246 opteron running FreeBSD AMD64. In some cases, the AMD is faster, in other cases the Xeon is faster. >From what I have seen, the AMD's strong point is running MySQL select very fast as compared to the Xeon. In my case, it may relate to some other variable, or it may be MySQL using the two physical CPU's better then the Intel's two logical. For the most part, (at least with the two machines I used above), they were pretty evenly matched. When I first started testing the AMD machine with FreeBSD AMD64, I was expecting some huge difference - but so far I haven't really seen it. Ray At 08:38 AM 5/31/2005 +1000, Mathew Schofield wrote: | Is the AMD64 Version of FreeBSD Significantly faster then the i386 | version? I am using Windows XP 64 Bit atm and it is *incredibly* | faster then the 32 bit version. I am just curious to if FreeBSD's | AMD64 Version is snappy and ... any good? | | -- | This is a private letter and only the intended people may read this | message. You may not store, quote or publish this document for any | purposes. The data/information held within this message are for | private use, and no one may disclose it. There are no guarentees that | the information disclosed is accurate, or that the links/attached | files will not be contaminated with Viruses. You use all links, and | all attachments, at your own free will and thus risk. You have been | warned. | _______________________________________________ | 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" | | From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 01:48:23 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1F7316A41C for ; Tue, 31 May 2005 01:48:22 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D0743D49 for ; Tue, 31 May 2005 01:48:22 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j4V1mLrI013059; Tue, 31 May 2005 11:48:21 +1000 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j4V1mIqB030835; Tue, 31 May 2005 11:48:20 +1000 Date: Tue, 31 May 2005 11:48:19 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Ken Gunderson In-Reply-To: <20050530090525.246b0c35.kgunders@teamcool.net> Message-ID: <20050531113955.D91505@delplex.bde.org> References: <20050530090525.246b0c35.kgunders@teamcool.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 01:48:23 -0000 On Mon, 30 May 2005, Ken Gunderson wrote: > On larger systems sporting several gigs of ram, what it the recommended > swap scheme? I'm aware of the 2x ram rule of thumb and also that this > rule is considered "old school" by many. I don't use any except on machines with <= 64MB of RAM. > And of course that you need > at least as much swap as ram if you want to get a full dump... Of course not. The dump can be written to any disk device that you don't care about overwriting. > But other than that it seems we pretty much don't want/need to be > swapping at all on modern machines. Curious what folks are doing in the > modern world with larger systems. Swap is still needed if you run bloatware or lots of processes. The only significant differences between a machine with 3*N bytes of RAM and one with N bytes of RAM and 2*N bytes of swap are that the former costs more and is much faster if all of the allocated (RAM+swap) memory is actually used. Bruce From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 02:42:10 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B436116A41C for ; Tue, 31 May 2005 02:42:10 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id A087443D4C for ; Tue, 31 May 2005 02:42:09 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 09A7085666; Tue, 31 May 2005 12:12:07 +0930 (CST) Date: Tue, 31 May 2005 12:12:07 +0930 From: Greg 'groggy' Lehey To: Bruce Evans Message-ID: <20050531024206.GK10912@wantadilla.lemis.com> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050531113955.D91505@delplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/0P/MvzTfyTu5j9Q" Content-Disposition: inline In-Reply-To: <20050531113955.D91505@delplex.bde.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 02:42:10 -0000 --/0P/MvzTfyTu5j9Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 31 May 2005 at 11:48:19 +1000, Bruce Evans wrote: > On Mon, 30 May 2005, Ken Gunderson wrote: >> And of course that you need at least as much swap as ram if you >> want to get a full dump... > > Of course not. The dump can be written to any disk device that you > don't care about overwriting. Sure. And, apart from swap, what would that be? Why not use it for swap while you're not dumping to it? Greg -- See complete headers for address and phone numbers. --/0P/MvzTfyTu5j9Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCm87+IubykFB6QiMRArOYAJ91p5b1YIvwkRvLGDuWR9vTHldpYACfZrNQ eg+JlHs5rZcypp2XoQXCWh8= =iMyq -----END PGP SIGNATURE----- --/0P/MvzTfyTu5j9Q-- From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 03:18:05 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D09EC16A41C for ; Tue, 31 May 2005 03:18:05 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: from sarajevo.pacific.net.sg (sarajevo.pacific.net.sg [203.120.90.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 07F8543D1D for ; Tue, 31 May 2005 03:18:04 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 23316 invoked from network); 31 May 2005 03:18:03 -0000 Received: from unknown (HELO maxwell6.pacific.net.sg) (203.120.90.212) by sarajevo with SMTP; 31 May 2005 03:18:03 -0000 Received: from [192.168.0.107] ([210.24.246.101]) by maxwell6.pacific.net.sg with ESMTP id <20050531031802.RUZX1233.maxwell6.pacific.net.sg@[192.168.0.107]>; Tue, 31 May 2005 11:18:02 +0800 Message-ID: <429BD75A.2080304@pacific.net.sg> Date: Tue, 31 May 2005 11:17:46 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050514) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20050530090525.246b0c35.kgunders@teamcool.net> In-Reply-To: <20050530090525.246b0c35.kgunders@teamcool.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 03:18:05 -0000 Hi, Ken Gunderson wrote: > Hello: > > On larger systems sporting several gigs of ram, what it the recommended > swap scheme? I'm aware of the 2x ram rule of thumb and also that this > rule is considered "old school" by many. And of course that you need > at least as much swap as ram if you want to get a full dump... > But other than that it seems we pretty much don't want/need to be > swapping at all on modern machines. Curious what folks are doing in the > modern world with larger systems. > It is still the same old problem. How much memory will be needed when the maximum number of users are working with the maximum number of applications. The 2x RAM is a good compromise between speed and effort. You do not need any swap space if you never expect it to be used. But keep in mind that your machine might crash in this case if it gets loaded to that maximum once. Swapping has a nice side effect. The machine becomes slower when it starts. Users see then that something is wrong and at least stop starting new programs. Erich From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 03:18:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1913716A41C for ; Tue, 31 May 2005 03:18:47 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id B07D243D1D for ; Tue, 31 May 2005 03:18:46 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j4V3IguQ010591; Mon, 30 May 2005 23:18:42 -0400 Date: Mon, 30 May 2005 23:18:41 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: ray@redshift.com In-Reply-To: <3.0.1.32.20050530175629.00a77268@pop.redshift.com> Message-ID: <20050530231640.T58656@zoraida.natserv.net> References: <3.0.1.32.20050530175629.00a77268@pop.redshift.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 03:18:47 -0000 On Mon, 30 May 2005 ray@redshift.com wrote: > Depends on what you are doing. All the reports I have read from several lists, including some non FreeBSD ones, seems to show AMD64 doing significantly better on data intensive operations. In a PostgreSQL list I read reports of 1.5 to 2.0 times the performance of Intel CPU of the same speed. From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 03:35:42 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 606A516A41C; Tue, 31 May 2005 03:35:42 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0BE943D49; Tue, 31 May 2005 03:35:41 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j4V3ZerI026599; Tue, 31 May 2005 13:35:40 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j4V3ZbqB014478; Tue, 31 May 2005 13:35:38 +1000 Date: Tue, 31 May 2005 13:35:38 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: "Greg 'groggy' Lehey" In-Reply-To: <20050531024206.GK10912@wantadilla.lemis.com> Message-ID: <20050531133318.R1603@epsplex.bde.org> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050531113955.D91505@delplex.bde.org> <20050531024206.GK10912@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 03:35:42 -0000 On Tue, 31 May 2005, Greg 'groggy' Lehey wrote: > On Tuesday, 31 May 2005 at 11:48:19 +1000, Bruce Evans wrote: >> On Mon, 30 May 2005, Ken Gunderson wrote: >>> And of course that you need at least as much swap as ram if you >>> want to get a full dump... >> >> Of course not. The dump can be written to any disk device that you >> don't care about overwriting. > > Sure. And, apart from swap, what would that be? Why not use it for > swap while you're not dumping to it? Because if swap is configured than it might be used. Bruce From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 03:40:13 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FF3416A41C for ; Tue, 31 May 2005 03:40:13 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 657C643D49 for ; Tue, 31 May 2005 03:40:12 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id EAB168569D; Tue, 31 May 2005 13:10:09 +0930 (CST) Date: Tue, 31 May 2005 13:10:09 +0930 From: Greg 'groggy' Lehey To: Bruce Evans Message-ID: <20050531034009.GM10912@wantadilla.lemis.com> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050531113955.D91505@delplex.bde.org> <20050531024206.GK10912@wantadilla.lemis.com> <20050531133318.R1603@epsplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aiCxlS1GuupXjEh3" Content-Disposition: inline In-Reply-To: <20050531133318.R1603@epsplex.bde.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 03:40:13 -0000 --aiCxlS1GuupXjEh3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 31 May 2005 at 13:35:38 +1000, Bruce Evans wrote: > On Tue, 31 May 2005, Greg 'groggy' Lehey wrote: > >> On Tuesday, 31 May 2005 at 11:48:19 +1000, Bruce Evans wrote: >>> On Mon, 30 May 2005, Ken Gunderson wrote: >>>> And of course that you need at least as much swap as ram if you >>>> want to get a full dump... >>> >>> Of course not. The dump can be written to any disk device that you >>> don't care about overwriting. >> >> Sure. And, apart from swap, what would that be? Why not use it >> for swap while you're not dumping to it? > > Because if swap is configured than it might be used. Well, I said "use", not "configure". Greg -- The virus contained in this message was not detected. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. --aiCxlS1GuupXjEh3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCm9yZIubykFB6QiMRAtRSAJ4x9N4YWg0Pf/vlM4RgxACarRkCjACgkKIu J7Oxi8H+YQhspjmjKUehLL0= =Zn6H -----END PGP SIGNATURE----- --aiCxlS1GuupXjEh3-- From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 04:00:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A8C116A41C; Tue, 31 May 2005 04:00:59 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02C0B43D1D; Tue, 31 May 2005 04:00:58 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (localhost [127.0.0.1]) by lexi.siliconlandmark.com (8.13.3/8.13.3) with ESMTP id j4V40iDO015209; Tue, 31 May 2005 00:00:44 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost) by lexi.siliconlandmark.com (8.13.3/8.13.3/Submit) with ESMTP id j4V40iFl015206; Tue, 31 May 2005 00:00:44 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: lexi.siliconlandmark.com: andy owned process doing -bs Date: Tue, 31 May 2005 00:00:44 -0400 (EDT) From: Andre Guibert de Bruet To: Roland Smith In-Reply-To: <20050529081442.GA99205@slackbox.xs4all.nl> Message-ID: <20050530235253.W69811@lexi.siliconlandmark.com> References: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> <20050529081442.GA99205@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Information: Please contact the ISP for more information X-SL-MailScanner: Found to be clean X-SL-SpamCheck: not spam, SpamAssassin (score=-2.544, required 6, autolearn=not spam, AWL 0.06, BAYES_00 -2.60) X-MailScanner-From: andy@siliconlandmark.com Cc: "Jack L." , freebsd-amd64@freebsd.org, freebsd-current@freebsd.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 04:00:59 -0000 On Sun, 29 May 2005, Roland Smith wrote: > On Sun, May 29, 2005 at 12:00:29AM -0800, Jack L. wrote: >> >> What cpu type should I use for make.conf and the kernel if I want to >> use the AMD64 platform? > > You do not need to have anything special in make.conf, and the GENERIC > kernel for amd64 contains the necessary 'machine' and 'cpu' paramaters. This is not entirely correct. Sure, your system will run without anything special in make.conf; But if you want decent performance, you probably want to set CPUTYPE to "nocona" in order to get a build that is tailored to your cpu (SSE3, etc). More information on what that CPUTYPE enables is available in /usr/share/mk/bsd.cpu.mk. Cheers, Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * Tormenting bytes since 1980. */ From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 07:31:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 344FB16A41C for ; Tue, 31 May 2005 07:31:50 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from www1.brozs.net (mail.brozs.net [82.67.204.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EC5D43D54 for ; Tue, 31 May 2005 07:31:48 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from localhost (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id 8BEEB457C for ; Tue, 31 May 2005 09:29:51 +0200 (CEST) Received: from www1.brozs.net ([127.0.0.1]) by localhost (www1.brozs.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35001-05 for ; Tue, 31 May 2005 09:29:50 +0200 (CEST) Received: from webmail.brozs.net (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id 5F85244A7 for ; Tue, 31 May 2005 09:29:50 +0200 (CEST) Received: from 217.119.178.19 (SquirrelMail authenticated user tfagart@brozs.net); by webmail.brozs.net with HTTP; Tue, 31 May 2005 09:29:50 +0200 (CEST) Message-ID: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> Date: Tue, 31 May 2005 09:29:50 +0200 (CEST) From: tfagart@brozs.net To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at brozs.net Subject: [CPU temperature] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 07:31:50 -0000 Hello, After having done my upgrade to 5.4Release I've noticed that the the CPU temperature of my box is 10 degré celsius higher than it was before with 5.3R. I haven't changed anything in terms of number of running process, and nothing for me could explain this increase. Also I've done the same test with i386 release, and there's no such a behaviour. One of my friend is having the same type of issue with different hardware (but still AMD64). The tool I'm using to monitor tempertature is xmbmon-205_1 + Cacti Software FreeBSD www 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #43: Fri May 20 16:17:04 CEST 2005 root@www:/usr/src/sys/amd64/compile/TOM amd64 ww1# pciconf -lv agp0@pci0:0:0: class=0x060000 card=0x80a31043 chip=0x31881106 rev=0x01 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'Apollo K8HTB CPU to PCI Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb1881106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'Apollo K8HTB CPU to AGP 2.0/3.0 Bridge' class = bridge subclass = PCI-PCI fwohci0@pci0:7:0: class=0x0c0010 card=0x808a1043 chip=0x30441106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller' class = serial bus subclass = FireWire atapci0@pci0:8:0: class=0x010400 card=0x80f51043 chip=0x3373105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20378? FastTrak RAID Controller' class = mass storage subclass = RAID bktr0@pci0:9:0: class=0x040000 card=0x13eb0070 chip=0x036e109e rev=0x02 hdr=0x00 vendor = 'Brooktree Corporation' device = 'Bt878 MediaStream Controller' class = multimedia subclass = video none0@pci0:9:1: class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 hdr=0x00 vendor = 'Brooktree Corporation' device = 'Bt878/Fusion878A Video Capture (Audio Section)' class = multimedia skc0@pci0:10:0: class=0x020000 card=0x811a1043 chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated PHY' class = network subclass = ethernet ahc0@pci0:11:0: class=0x010000 card=0xa1809005 chip=0x00109005 rev=0x00 hdr=0x00 vendor = 'Adaptec Inc' device = 'AHA-2940U2W/U2B AHA-2950U2W Ultra2 SCSI Controller' class = mass storage subclass = SCSI none1@pci0:12:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet pcm0@pci0:13:0: class=0x040100 card=0x80271102 chip=0x00021102 rev=0x06 hdr=0x00 vendor = 'Creative Labs' device = 'EMU10000 Sound Blaster Live! (Also Live! 5.1) - OEM from DELL - CT4780' class = multimedia subclass = audio emujoy0@pci0:13:1: class=0x098000 card=0x00201102 chip=0x70021102 rev=0x06 hdr=0x00 vendor = 'Creative Labs' device = 'EMU10000 Game Port' class = input device xl0@pci0:14:0: class=0x020000 card=0x905510b7 chip=0x905510b7 rev=0x24 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC' class = network subclass = ethernet atapci1@pci0:15:0: class=0x010400 card=0x80ed1043 chip=0x31491106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = '??? SATA RAID Controller' class = mass storage subclass = RAID atapci2@pci0:15:1: class=0x01018a card=0x80ed1043 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' class = mass storage subclass = ATA uhci0@pci0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci1@pci0:16:1: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci2@pci0:16:2: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci3@pci0:16:3: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB ehci0@pci0:16:4: class=0x0c0320 card=0x80ed1043 chip=0x31041106 rev=0x86 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6202 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB isab0@pci0:17:0: class=0x060100 card=0x80ed1043 chip=0x32271106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 PCI-to-ISA Bridge' class = bridge subclass = PCI-ISA hostb0@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb1@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb2@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb3@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI drm0@pci1:0:0: class=0x030000 card=0x00021787 chip=0x51591002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'RV100 Radeon 7000 / Radeon VE' class = display subclass = VGA Do you have any clue for this increase ? Thanks Thomas From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 10:41:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1910B16A41C for ; Tue, 31 May 2005 10:41:26 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id B29DE43D53 for ; Tue, 31 May 2005 10:41:25 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so1745095rne for ; Tue, 31 May 2005 03:41:24 -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=ePd3Abv9kPMNiUqXaFceHp4Q71g4lMtyqh/JzeZAoEmrOup2bpNQMIuh+VvShc1MFKIOKFqSEmGIGKhyqXERcb6EXgM8xtvl7sddH9uzieHQbfFDkIxCOL7cOIi74uV30PFripaGgyxW0mOsHNCd3GGs+gn2NMnsU1EXboAPcGw= Received: by 10.38.11.27 with SMTP id 27mr1837591rnk; Tue, 31 May 2005 03:41:24 -0700 (PDT) Received: by 10.38.209.31 with HTTP; Tue, 31 May 2005 03:41:24 -0700 (PDT) Message-ID: <84dead720505310341671bac00@mail.gmail.com> Date: Tue, 31 May 2005 16:11:24 +0530 From: Joseph Koshy To: "tfagart@brozs.net" In-Reply-To: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> Cc: freebsd-amd64@freebsd.org Subject: Re: [CPU temperature] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joseph Koshy List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 10:41:26 -0000 > I haven't changed anything in terms of number of running=20 > process, and nothing for me could explain this increase. Is the machine substantially less idle than before? Would you have vmstat outputs (or equivalent) to compare? --=20 FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 10:48:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2A1416A41C for ; Tue, 31 May 2005 10:48:22 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from www1.brozs.net (mail.brozs.net [82.67.204.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A38E43D48 for ; Tue, 31 May 2005 10:48:21 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from localhost (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id 49F45454A; Tue, 31 May 2005 12:46:25 +0200 (CEST) Received: from www1.brozs.net ([127.0.0.1]) by localhost (www1.brozs.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42472-04; Tue, 31 May 2005 12:46:24 +0200 (CEST) Received: from webmail.brozs.net (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id BCDC94391; Tue, 31 May 2005 12:46:24 +0200 (CEST) Received: from 217.119.178.19 (SquirrelMail authenticated user tfagart@brozs.net); by webmail.brozs.net with HTTP; Tue, 31 May 2005 12:46:24 +0200 (CEST) Message-ID: <18417.217.119.178.19.1117536384.squirrel@217.119.178.19> In-Reply-To: <84dead720505310341671bac00@mail.gmail.com> References: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> <84dead720505310341671bac00@mail.gmail.com> Date: Tue, 31 May 2005 12:46:24 +0200 (CEST) From: tfagart@brozs.net To: "Joseph Koshy" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at brozs.net Cc: freebsd-amd64@freebsd.org Subject: Re: [CPU temperature] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 10:48:23 -0000 >> I haven't changed anything in terms of number of running >> process, and nothing for me could explain this increase. > > Is the machine substantially less idle than before? Would you > have vmstat outputs (or equivalent) to compare? I can't compare it, because now I only got a 5.4-amd64 running But here's the vmstat output from the actual box www1# vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad4 ad10 in sy cs us sy id 1 6 0 422056 90920 1044 0 0 0 1029 2 0 0 1294 1226 442 5 2 93 What I can provide is vmstat in 5.3-i386 if useful. Thanks > > -- > FreeBSD Volunteer, http://people.freebsd.org/~jkoshy > From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 12:15:15 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C293A16A41C for ; Tue, 31 May 2005 12:15:15 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F00643D48 for ; Tue, 31 May 2005 12:15:15 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 79AEA4CFE6; Tue, 31 May 2005 12:15:48 +0000 (GMT) Received: from [192.168.46.52] (ppp166-27.static.internode.on.net [150.101.166.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by p4.roq.com (Postfix) with ESMTP id 98DC24CB49; Tue, 31 May 2005 12:15:47 +0000 (GMT) Message-ID: <429C3EEE.60609@roq.com> Date: Tue, 31 May 2005 20:39:42 +1000 From: Michael VInce User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.8) Gecko/20050524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mathew Schofield References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 12:15:15 -0000 Mathew Schofield wrote: >Is the AMD64 Version of FreeBSD Significantly faster then the i386 >version? I am using Windows XP 64 Bit atm and it is *incredibly* >faster then the 32 bit version. I am just curious to if FreeBSD's >AMD64 Version is snappy and ... any good? > > > I think your '*incredibly*' is a bit over the top in description of performance. Hardware benchmarking web sites like www.anandtech.com have done extensive benchmarking on MS windows have have reported mixed results, some things have been faster some have been slower, over all it is faster. Here is a good example 64bit version of the game Far Cry in WinXP64 , its not server benchmark but none the less http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2411&p=2 on Intel EMT64 this game was 8 frames per sec faster. on the AMD64 it was 6 fps faster From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 12:17:34 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FBD716A41C; Tue, 31 May 2005 12:17:34 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1455343D1D; Tue, 31 May 2005 12:17:33 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd25.aul.t-online.de by mailout08.sul.t-online.com with smtp id 1Dd5ga-0005pV-01; Tue, 31 May 2005 14:17:32 +0200 Received: from fw.reifenberger.com (TQJ26cZ6YeqPU40VjsUU0frAfWZmv3I1yGWS-vNtk2PZa1IFjaiAUI@[84.152.58.75]) by fwd25.sul.t-online.de with esmtp id 1Dd5gQ-1R8awK0; Tue, 31 May 2005 14:17:22 +0200 Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.3/8.13.3/Submit) with ESMTP id j4VCH2fK088391; Tue, 31 May 2005 14:17:02 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Tue, 31 May 2005 14:17:02 +0200 (CEST) From: Michael Reifenberger To: peter@freebsd.org Message-ID: <20050531133608.J87922@fw.reifenberger.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: TQJ26cZ6YeqPU40VjsUU0frAfWZmv3I1yGWS-vNtk2PZa1IFjaiAUI@t-dialin.net X-TOI-MSGID: 46c90e0b-d644-4710-bc97-e057a2ea120e Cc: amd64@freebsd.org Subject: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 12:17:34 -0000 Hi, as it seems we are building the amd64 loader in i386 compatible mode (compiling -m32...) This breaks the building of testmain in sys/boot/ficl at least as -m32 doesnt seem to be well supported until now on amd64. Wouldn't is be possible to switch to 64bit long mode in the boot0 loader and building the /boot/loader using the amd64 native formats? (Like the way we switch to protected mode in btx) (I'm trying to use and upgrade our ficl loader BTW) BTW2: Our sys/boot hierarchy isn't very intuitive to start with... Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 14:20:39 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 982B016A41C for ; Tue, 31 May 2005 14:20:39 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5155F43D49 for ; Tue, 31 May 2005 14:20:36 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 4A97FB85A for ; Tue, 31 May 2005 10:20:36 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v730) In-Reply-To: <20050530231640.T58656@zoraida.natserv.net> References: <3.0.1.32.20050530175629.00a77268@pop.redshift.com> <20050530231640.T58656@zoraida.natserv.net> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2--344402113; protocol="application/pkcs7-signature" Message-Id: <5B67FDFF-B537-4BA9-8145-898EA08437D6@khera.org> From: Vivek Khera Date: Tue, 31 May 2005 10:20:34 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.730) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 14:20:39 -0000 --Apple-Mail-2--344402113 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 30, 2005, at 11:18 PM, Francisco Reyes wrote: > All the reports I have read from several lists, including some non > FreeBSD ones, seems to show AMD64 doing significantly better on > data intensive operations. > > In a PostgreSQL list I read reports of 1.5 to 2.0 times the > performance of Intel CPU of the same speed. > I'll confirm this with PostgreSQL. I have a 1-year old Dell 2650 with a 14-disk RAID array that cannot keep up with replication coming from a dual opteron with a 6 disk RAID array. The replica doesn't even need to do any data intergrity checking (foreign keys) which are quite expensive. For normal regular server usage, though, I don't see a need for opteron. the intel emt64 Xeon system I have is kind of mediocre, too, running FreeBSD/amd64, but I think that's just because it is a Dell :-) Vivek Khera, Ph.D. +1-301-869-4449 x806 --Apple-Mail-2--344402113-- From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 14:32:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9102416A41C for ; Tue, 31 May 2005 14:32:56 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5014B43D1D for ; Tue, 31 May 2005 14:32:56 +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 j4VEWtI2080206; Tue, 31 May 2005 07:32: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 j4VEWsu3080205; Tue, 31 May 2005 07:32:54 -0700 (PDT) (envelope-from obrien) Date: Tue, 31 May 2005 07:32:54 -0700 From: "David O'Brien" To: Michael Reifenberger Message-ID: <20050531143254.GC9158@dragon.NUXI.org> References: <20050531133608.J87922@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050531133608.J87922@fw.reifenberger.com> 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: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 31 May 2005 14:32:56 -0000 On Tue, May 31, 2005 at 02:17:02PM +0200, Michael Reifenberger wrote: > Hi, > as it seems we are building the amd64 loader in i386 compatible > mode (compiling -m32...) > This breaks the building of testmain in sys/boot/ficl at least > as -m32 doesnt seem to be well supported until now on amd64. Are you sure (cd /sys/boot/ficl ; make testmain) works on 32-bit systems? It fails on my 6-CURRENT system (though for a different reason). > Wouldn't is be possible to switch to 64bit long mode in the > boot0 loader Ha!! We can only have 1 sector worth of code in boot0. At this point we only have a few bytes of free code space. No where near enough to do the long mode switch. > (I'm trying to use and upgrade our ficl loader BTW) One is able to use and upgrade one's ficl loader loader on AMD64 just fine. So what is the real problem you are hitting? > BTW2: Our sys/boot hierarchy isn't very intuitive to start with... You can thank the bozo boot requirements of the PeeCee architecture for that. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 14:37:38 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0199316A41C for ; Tue, 31 May 2005 14:37:38 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF0CF43D49 for ; Tue, 31 May 2005 14:37:37 +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 j4VEbbMA080316; Tue, 31 May 2005 07:37:37 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j4VEbavG080313; Tue, 31 May 2005 07:37:36 -0700 (PDT) (envelope-from obrien) Date: Tue, 31 May 2005 07:37:36 -0700 From: "David O'Brien" To: Ken Gunderson , freebsd-amd64@FreeBSD.org Message-ID: <20050531143736.GD9158@dragon.NUXI.org> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050530231155.GA43641@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050530231155.GA43641@xor.obsecurity.org> 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: Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 31 May 2005 14:37:38 -0000 On Mon, May 30, 2005 at 04:11:55PM -0700, Kris Kennaway wrote: > On Mon, May 30, 2005 at 09:05:25AM -0600, Ken Gunderson wrote: > > On larger systems sporting several gigs of ram, what it the recommended > > swap scheme? I'm aware of the 2x ram rule of thumb and also that this > > rule is considered "old school" by many. And of course that you need > > at least as much swap as ram if you want to get a full dump... .. > > I'd recommend as much swap as RAM (allowing for future expansion if > you think you might one day add more RAM). Plus some space for dump headers, etc.. On an 4-32GB machines I use RAM+2MB. I'm sure the dump headers is smaller, but if it grew one day... -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 14:42:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EE1F16A41C; Tue, 31 May 2005 14:42:45 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 463BA43D48; Tue, 31 May 2005 14:42:45 +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 j4VEgfAf080483; Tue, 31 May 2005 07:42:41 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j4VEgfgU080482; Tue, 31 May 2005 07:42:41 -0700 (PDT) (envelope-from obrien) Date: Tue, 31 May 2005 07:42:40 -0700 From: "David O'Brien" To: Andre Guibert de Bruet Message-ID: <20050531144240.GE9158@dragon.NUXI.org> Mail-Followup-To: freebsd-amd64@freebsd.org, Andre Guibert de Bruet , Roland Smith , "Jack L." , freebsd-current@freebsd.org References: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> <20050529081442.GA99205@slackbox.xs4all.nl> <20050530235253.W69811@lexi.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050530235253.W69811@lexi.siliconlandmark.com> 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: "Jack L." , freebsd-amd64@freebsd.org, freebsd-current@freebsd.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 31 May 2005 14:42:45 -0000 On Tue, May 31, 2005 at 12:00:44AM -0400, Andre Guibert de Bruet wrote: > On Sun, 29 May 2005, Roland Smith wrote: > >On Sun, May 29, 2005 at 12:00:29AM -0800, Jack L. wrote: > >> > >>What cpu type should I use for make.conf and the kernel if I want to > >>use the AMD64 platform? > > > >You do not need to have anything special in make.conf, and the GENERIC > >kernel for amd64 contains the necessary 'machine' and 'cpu' paramaters. > > This is not entirely correct. Sure, your system will run without anything > special in make.conf; But if you want decent performance, you probably > want to set CPUTYPE to "nocona" in order to get a build that is tailored > to your cpu (SSE3, etc). More information on what that CPUTYPE enables is > available in /usr/share/mk/bsd.cpu.mk. You're saying that one doesn't get decent performance on a Nocona with stock GCC code generation? While one may get noticeably better performance with CPUTYPE=nocona, I doubt it is a huge difference. What I'm saying is, I sure one will have decent performance with a stock FreeBSD/amd64 install. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 14:44:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F4316A422 for ; Tue, 31 May 2005 14:44:34 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id B491943D49 for ; Tue, 31 May 2005 14:44:33 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j4VEiW8N021575; Tue, 31 May 2005 10:44:32 -0400 Date: Tue, 31 May 2005 10:44:32 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: Vivek Khera In-Reply-To: <5B67FDFF-B537-4BA9-8145-898EA08437D6@khera.org> Message-ID: <20050531103930.N67364@zoraida.natserv.net> References: <3.0.1.32.20050530175629.00a77268@pop.redshift.com> <20050530231640.T58656@zoraida.natserv.net> <5B67FDFF-B537-4BA9-8145-898EA08437D6@khera.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 14:44:34 -0000 On Tue, 31 May 2005, Vivek Khera wrote: > I'll confirm this with PostgreSQL. I have a 1-year old Dell 2650 with a > 14-disk RAID array that cannot keep up with replication coming from a dual > opteron with a 6 disk RAID array. What are you using for replication? Compared to i386 how much memory is PostgreSQL and other apps using? On another thread I asked about memory usage was told that apps in AMD64 mode seemed to be taking twice as much memory. I would be very interesting in reading about PostgreSQL memory usage in FreeBSD AMD64. > For normal regular server usage, though, I don't see a need for opteron. I wonder other data intensive apps (ie image/audio editing) how they would do in Fbsd-AMD64. Also I wonder if it's an advantage only when large amounts of data are moving or lots of data in general. For example a busy news server or email server. From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 15:06:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0DE316A41C for ; Tue, 31 May 2005 15:06:53 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EEA043D1D for ; Tue, 31 May 2005 15:06:53 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd19.aul.t-online.de by mailout10.sul.t-online.com with smtp id 1Dd8KR-0007Ue-02; Tue, 31 May 2005 17:06:51 +0200 Received: from fw.reifenberger.com (VO886cZGwejgi-+Cvz3RVA5gMe61MxEwE9UfQx9T1+bf4bxI-I1s4c@[84.152.58.75]) by fwd19.sul.t-online.de with esmtp id 1Dd8KI-24rKxE0; Tue, 31 May 2005 17:06:42 +0200 Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.3/8.13.3/Submit) with ESMTP id j4VF6LIu089188 for ; Tue, 31 May 2005 17:06:21 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Tue, 31 May 2005 17:06:21 +0200 (CEST) From: Michael Reifenberger To: freebsd-amd64@freebsd.org In-Reply-To: <20050531143254.GC9158@dragon.NUXI.org> Message-ID: <20050531165558.L88820@fw.reifenberger.com> References: <20050531133608.J87922@fw.reifenberger.com> <20050531143254.GC9158@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: VO886cZGwejgi-+Cvz3RVA5gMe61MxEwE9UfQx9T1+bf4bxI-I1s4c@t-dialin.net X-TOI-MSGID: c825e2d1-32d4-4e05-b9c3-e16ffb1ee278 Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 15:06:53 -0000 On Tue, 31 May 2005, David O'Brien wrote: ... >> mode (compiling -m32...) >> This breaks the building of testmain in sys/boot/ficl at least >> as -m32 doesnt seem to be well supported until now on amd64. > > Are you sure (cd /sys/boot/ficl ; make testmain) works on 32-bit systems? > It fails on my 6-CURRENT system (though for a different reason). > No. As it seems boot/ficl contains code which relys on i386/loader stuff. Its not self contained as it should be. >> Wouldn't is be possible to switch to 64bit long mode in the >> boot0 loader > > Ha!! We can only have 1 sector worth of code in boot0. At this point we > only have a few bytes of free code space. No where near enough to do the > long mode switch. > Sorry. I didnt meant boot0 but btx. I do know that boot0 is too small. But btx is already switching to protected mode so it should be possible to switch to 64bit mode too. >> (I'm trying to use and upgrade our ficl loader BTW) > > One is able to use and upgrade one's ficl loader loader on AMD64 just > fine. So what is the real problem you are hitting? > I'm trying to upgrade ficl3 to ficl4 (mainly due to being able to use compressed softwords). Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 15:39:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93E6316A41C for ; Tue, 31 May 2005 15:39:54 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 593C143D53 for ; Tue, 31 May 2005 15:39:54 +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 j4VFdrmU081578; Tue, 31 May 2005 08:39:53 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j4VFdqe6081576; Tue, 31 May 2005 08:39:52 -0700 (PDT) (envelope-from obrien) Date: Tue, 31 May 2005 08:39:52 -0700 From: "David O'Brien" To: Michael Reifenberger Message-ID: <20050531153952.GF9158@dragon.NUXI.org> References: <20050531133608.J87922@fw.reifenberger.com> <20050531143254.GC9158@dragon.NUXI.org> <20050531165558.L88820@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050531165558.L88820@fw.reifenberger.com> 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: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 15:39:54 -0000 On Tue, May 31, 2005 at 05:06:21PM +0200, Michael Reifenberger wrote: > On Tue, 31 May 2005, David O'Brien wrote: > >>(I'm trying to use and upgrade our ficl loader BTW) > > > >One is able to use and upgrade one's ficl loader loader on AMD64 just > >fine. So what is the real problem you are hitting? > > I'm trying to upgrade ficl3 to ficl4 (mainly due to being able to > use compressed softwords). Ah. Do you have patches I can look at? (send off-list) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 15:46:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAEFA16A41C; Tue, 31 May 2005 15:46:36 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88EE643D49; Tue, 31 May 2005 15:46:36 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd35.aul.t-online.de by mailout10.sul.t-online.com with smtp id 1Dd8wt-0003nY-00; Tue, 31 May 2005 17:46:35 +0200 Received: from fw.reifenberger.com (Vaz0UcZTwen48TLDSIboExpJZp2dEAY-jMU924A5lZkRoCn88h6RYd@[84.152.58.75]) by fwd35.sul.t-online.de with esmtp id 1Dd8we-1D6pFI0; Tue, 31 May 2005 17:46:20 +0200 Received: from localhost (mike@localhost) by fw.reifenberger.com (8.13.3/8.13.3/Submit) with ESMTP id j4VFjxtK089565; Tue, 31 May 2005 17:45:59 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Tue, 31 May 2005 17:45:59 +0200 (CEST) From: Michael Reifenberger To: "David O'Brien" In-Reply-To: <20050531153952.GF9158@dragon.NUXI.org> Message-ID: <20050531174119.E89518@fw.reifenberger.com> References: <20050531133608.J87922@fw.reifenberger.com> <20050531143254.GC9158@dragon.NUXI.org> <20050531165558.L88820@fw.reifenberger.com> <20050531153952.GF9158@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: Vaz0UcZTwen48TLDSIboExpJZp2dEAY-jMU924A5lZkRoCn88h6RYd@t-dialin.net X-TOI-MSGID: 3c7233a1-e1f8-4238-b87c-388ae2e36f4f Cc: freebsd-amd64@freebsd.org Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 15:46:37 -0000 On Tue, 31 May 2005, David O'Brien wrote: ... >> I'm trying to upgrade ficl3 to ficl4 (mainly due to being able to >> use compressed softwords). > > Ah. > Do you have patches I can look at? (send off-list) > Not yet. I just started. I'm currently stuck with learning the FreeBSD way of booting and linking... Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 17:14:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7D5716A41C for ; Tue, 31 May 2005 17:14:30 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6054D43D1D for ; Tue, 31 May 2005 17:14:30 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id B98AAB862 for ; Tue, 31 May 2005 13:14:29 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v730) In-Reply-To: <20050531103930.N67364@zoraida.natserv.net> References: <3.0.1.32.20050530175629.00a77268@pop.redshift.com> <20050530231640.T58656@zoraida.natserv.net> <5B67FDFF-B537-4BA9-8145-898EA08437D6@khera.org> <20050531103930.N67364@zoraida.natserv.net> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3--333968198; protocol="application/pkcs7-signature" Message-Id: From: Vivek Khera Date: Tue, 31 May 2005 13:14:28 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.730) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: AMD64 Faster? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 17:14:30 -0000 --Apple-Mail-3--333968198 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 31, 2005, at 10:44 AM, Francisco Reyes wrote: > On Tue, 31 May 2005, Vivek Khera wrote: > > >> I'll confirm this with PostgreSQL. I have a 1-year old Dell 2650 >> with a 14-disk RAID array that cannot keep up with replication >> coming from a dual opteron with a 6 disk RAID array. >> > > What are you using for replication? > slony-I (see /usr/ports/database/slony1) > Compared to i386 how much memory is PostgreSQL and other apps using? > On another thread I asked about memory usage was told that apps in > AMD64 mode seemed to be taking twice as much memory. I would be > very interesting in reading about PostgreSQL memory usage in > FreeBSD AMD64. > About the same. The only thing really bigger in amd64 world is pointer size, and unless all you're building is a datastructure that has no data (ie just pointers) you're not gonna double your size... > >> For normal regular server usage, though, I don't see a need for >> opteron. >> > > I wonder other data intensive apps (ie image/audio editing) how > they would do in Fbsd-AMD64. Also I wonder if it's an advantage > only when large amounts of data are moving or lots of data in > general. For example a busy news server or email server. > I think anything that is slinging lots of bits to a disk will benefit, or anything that moves a lot of memory. The I/O on these puppies is just wicked fast. Vivek Khera, Ph.D. +1-301-869-4449 x806 --Apple-Mail-3--333968198-- From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 17:35:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6787A16A41F for ; Tue, 31 May 2005 17:35:00 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 087ED43D4C for ; Tue, 31 May 2005 17:34:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j4VHg3iX011400; Tue, 31 May 2005 11:42:04 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <429C9FD4.7040706@samsco.org> Date: Tue, 31 May 2005 11:33:08 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050531133608.J87922@fw.reifenberger.com> <20050531143254.GC9158@dragon.NUXI.org> In-Reply-To: <20050531143254.GC9158@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Michael Reifenberger Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 17:35:00 -0000 David O'Brien wrote: > On Tue, May 31, 2005 at 02:17:02PM +0200, Michael Reifenberger wrote: > >>Hi, >>as it seems we are building the amd64 loader in i386 compatible >>mode (compiling -m32...) >>This breaks the building of testmain in sys/boot/ficl at least >>as -m32 doesnt seem to be well supported until now on amd64. > > > Are you sure (cd /sys/boot/ficl ; make testmain) works on 32-bit systems? > It fails on my 6-CURRENT system (though for a different reason). > See the instructions that I posted recently. You __MUST__ do a 'make clean' first. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 18:24:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA9F216A41C; Tue, 31 May 2005 18:24:29 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3701B43D48; Tue, 31 May 2005 18:24:29 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (localhost [127.0.0.1]) by lexi.siliconlandmark.com (8.13.3/8.13.3) with ESMTP id j4VIOMIn024343; Tue, 31 May 2005 14:24:22 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost) by lexi.siliconlandmark.com (8.13.3/8.13.3/Submit) with ESMTP id j4VIOMK7024340; Tue, 31 May 2005 14:24:22 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: lexi.siliconlandmark.com: andy owned process doing -bs Date: Tue, 31 May 2005 14:24:22 -0400 (EDT) From: Andre Guibert de Bruet To: freebsd-amd64@freebsd.org In-Reply-To: <20050531144240.GE9158@dragon.NUXI.org> Message-ID: <20050531141130.Q69811@lexi.siliconlandmark.com> References: <20050529080029.687192B2B86@ws5-7.us4.outblaze.com> <20050529081442.GA99205@slackbox.xs4all.nl> <20050530235253.W69811@lexi.siliconlandmark.com> <20050531144240.GE9158@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Information: Please contact the ISP for more information X-SL-MailScanner: Found to be clean X-SL-SpamCheck: not spam, SpamAssassin (score=-2.542, required 6, autolearn=not spam, AWL 0.06, BAYES_00 -2.60) X-MailScanner-From: andy@siliconlandmark.com Cc: "Jack L." , freebsd-current@freebsd.org Subject: Re: Intel EM64T Processor Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 18:24:29 -0000 On Tue, 31 May 2005, David O'Brien wrote: > On Tue, May 31, 2005 at 12:00:44AM -0400, Andre Guibert de Bruet wrote: >> On Sun, 29 May 2005, Roland Smith wrote: >>> On Sun, May 29, 2005 at 12:00:29AM -0800, Jack L. wrote: >>>> >>>> What cpu type should I use for make.conf and the kernel if I want to >>>> use the AMD64 platform? >>> >>> You do not need to have anything special in make.conf, and the GENERIC >>> kernel for amd64 contains the necessary 'machine' and 'cpu' paramaters. >> >> This is not entirely correct. Sure, your system will run without anything >> special in make.conf; But if you want decent performance, you probably >> want to set CPUTYPE to "nocona" in order to get a build that is tailored >> to your cpu (SSE3, etc). More information on what that CPUTYPE enables is >> available in /usr/share/mk/bsd.cpu.mk. > > You're saying that one doesn't get decent performance on a Nocona with > stock GCC code generation? While one may get noticeably better > performance with CPUTYPE=nocona, I doubt it is a huge difference. What > I'm saying is, I sure one will have decent performance with a stock > FreeBSD/amd64 install. >From the testing that I performed on my desktop a few months back, the interactive performance was noticeably better under heavy IO. I have since switched the machine back to i386 mode because of vm-related panics (Which in all honesty, were most probably caused by the state of current at the time). Having just 4GB of memory in the system, the lack of EM64T has not really been that big of an issue (Even though the system is only reporting 3.5GB). The hardware that I ran all of this on is detailed in the following dmesg: http://bling.properkernel.com/freebsd/boot-v.txt Cheers, Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * Tormenting bytes since 1980. */ From owner-freebsd-amd64@FreeBSD.ORG Tue May 31 20:56:52 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D97916A41C for ; Tue, 31 May 2005 20:56:52 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF9DE43D1D for ; Tue, 31 May 2005 20:56:51 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10267 invoked from network); 31 May 2005 20:56:51 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender ) by mail24.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 31 May 2005 20:56:51 -0000 Received: from [10.50.41.231] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j4VKujHs064468; Tue, 31 May 2005 16:56:46 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Tue, 31 May 2005 16:56:49 -0400 User-Agent: KMail/1.8 References: <20050531133608.J87922@fw.reifenberger.com> <20050531143254.GC9158@dragon.NUXI.org> <20050531165558.L88820@fw.reifenberger.com> In-Reply-To: <20050531165558.L88820@fw.reifenberger.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505311656.50288.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 Cc: Michael Reifenberger Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 20:56:52 -0000 On Tuesday 31 May 2005 11:06 am, Michael Reifenberger wrote: > On Tue, 31 May 2005, David O'Brien wrote: > > Ha!! We can only have 1 sector worth of code in boot0. At this point we > > only have a few bytes of free code space. No where near enough to do the > > long mode switch. > > Sorry. I didnt meant boot0 but btx. I do know that boot0 is too small. > But btx is already switching to protected mode so it should be possible > to switch to 64bit mode too. Note that the loader uses the BIOS (via virtual 8086 mode) to do all the disk I/O, etc. Since long mode doesn't support vm86 mode, you'd end up with a loader that couldn't do any I/O to load the kernel, etc. unless you started including device drivers for all the different storage and networking hardware, etc. A 64-bit loader really isn't feasible unless your 64-bit machine includes firmware that you can use from 64-bit mode like EFI on ia64 or OFW on sparc. You probably want to stick with a 32-bit loader on amd64 for now. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 00:05:38 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C976E16A41C for ; Wed, 1 Jun 2005 00:05:38 +0000 (GMT) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DCCA43D1F for ; Wed, 1 Jun 2005 00:05:37 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id C7175856A1; Wed, 1 Jun 2005 09:35:35 +0930 (CST) Date: Wed, 1 Jun 2005 09:35:35 +0930 From: Greg 'groggy' Lehey To: freebsd-amd64@FreeBSD.org Message-ID: <20050601000535.GE35959@wantadilla.lemis.com> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050530231155.GA43641@xor.obsecurity.org> <20050531143736.GD9158@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HeFlAV5LIbMFYYuh" Content-Disposition: inline In-Reply-To: <20050531143736.GD9158@dragon.NUXI.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 00:05:38 -0000 --HeFlAV5LIbMFYYuh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 31 May 2005 at 7:37:36 -0700, David O'Brien wrote: > On Mon, May 30, 2005 at 04:11:55PM -0700, Kris Kennaway wrote: >> On Mon, May 30, 2005 at 09:05:25AM -0600, Ken Gunderson wrote: >>> On larger systems sporting several gigs of ram, what it the recommended >>> swap scheme? I'm aware of the 2x ram rule of thumb and also that this >>> rule is considered "old school" by many. And of course that you need >>> at least as much swap as ram if you want to get a full dump... > .. >> >> I'd recommend as much swap as RAM (allowing for future expansion if >> you think you might one day add more RAM). It's interesting that nobody except bde has paid much attention to the obvious fact that the more RAM you have, the less swap you use. So adding more RAM is only relevant in the scenario below: > Plus some space for dump headers, etc.. > On an 4-32GB machines I use RAM+2MB. I'm sure the dump headers is > smaller, but if it grew one day... Heh. I've always danced around this value too. We discussed it at BSDCan last month; we didn't come to a firm conclusion either, but it seems to be either 4 kB (probably) or 16 kB, repeated at beginning and end. So currently you'd get by with 32 kB more than memory size. I personally use twice the memory size + 1 MB. Nothing to do with the old rule of thumb; the chance that I'll double the memory in any given box is real, and reallocating dump partitions is a pain. Greg -- The virus contained in this message was not detected. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. --HeFlAV5LIbMFYYuh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCnPvPIubykFB6QiMRAtucAJ9BuK+QhVvV5RNzhyri1LO4sEcAOACgpzRX itnipLqcCKbdBpmuMBTS8i0= =dAAV -----END PGP SIGNATURE----- --HeFlAV5LIbMFYYuh-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 01:31:20 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C601416A41C; Wed, 1 Jun 2005 01:31:20 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-144-206-250.jan.bellsouth.net [70.144.206.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A77A43D4C; Wed, 1 Jun 2005 01:31:20 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id B764421028; Tue, 31 May 2005 20:31:18 -0500 (CDT) Date: Tue, 31 May 2005 20:31:18 -0500 From: "Matthew D. Fuller" To: Greg 'groggy' Lehey Message-ID: <20050601013118.GA25846@over-yonder.net> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050530231155.GA43641@xor.obsecurity.org> <20050531143736.GD9158@dragon.NUXI.org> <20050601000535.GE35959@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050601000535.GE35959@wantadilla.lemis.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: freebsd-amd64@FreeBSD.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 01:31:20 -0000 On Wed, Jun 01, 2005 at 09:35:35AM +0930 I heard the voice of Greg 'groggy' Lehey, and lo! it spake thus: > > It's interesting that nobody except bde has paid much attention to > the obvious fact that the more RAM you have, the less swap you use. I'm not sure that's obvious. Think of it as a sort of Parkinson's Law 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 06:56:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D22C716A41C for ; Wed, 1 Jun 2005 06:56:03 +0000 (GMT) (envelope-from michiel@boland.org) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5814443D1D for ; Wed, 1 Jun 2005 06:56:02 +0000 (GMT) (envelope-from michiel@boland.org) Received: from brakkenstein.nijmegen.internl.net by neerbosch.nijmegen.internl.net via brakkenstein.nijmegen.internl.net [217.149.193.41] with ESMTP for id j516u1Wj005686 (8.13.2/1.4); Wed, 1 Jun 2005 08:56:01 +0200 (MET DST) Received: from localhost by brakkenstein.nijmegen.internl.net via mboland@localhost with ESMTP for id j516u1qM011908 (8.13.2/2.02); Wed, 1 Jun 2005 08:56:01 +0200 (MEST) X-Authentication-Warning: brakkenstein.nijmegen.internl.net: mboland owned process doing -bs Date: Wed, 1 Jun 2005 08:55:59 +0200 (MEST) From: Michiel Boland To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: ELF interpreter not found during heavy lifting X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 06:56:03 -0000 Hi. I was doing some silly stress-tests like the following while [ 1 = 1 ] do time sh ./convert-all.sh done convert-all.sh does this: for a in * do convert -scale 90% $a ../out/$a & done wait In other words, it starts a number of concurrent ImageMagick 'convert' processes. At the moment I am trying to run 720 converts simultaneously. If I start the test after a fresh reboot, I get tons of errors like the following: ELF interpreter /libexec/ld-elf.so.1 not found Abort trap but if I interrupt the test, and re-start it, things go ahead as normal. Unfortuntately after 16 or so runs of convert-all.sh, the ELF errors reappear. Who has any idea why this is? Hardware is a sun fire v20z with 2 opteron 250 CPUs and 4G mem. I am using 5.4-STABLE from last week with a GENERIC kernel, except for the addition of SMP. Cheers Michiel From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 09:21:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 146DB16A41C for ; Wed, 1 Jun 2005 09:21:47 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C8E43D1D for ; Wed, 1 Jun 2005 09:21:46 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 2FD3B1F080; Wed, 1 Jun 2005 11:21:45 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 0BB0E6762; Wed, 1 Jun 2005 11:21:45 +0200 (CEST) Date: Wed, 1 Jun 2005 11:21:44 +0200 From: Marc Olzheim To: Michiel Boland Message-ID: <20050601092144.GA61602@stack.nl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: ELF interpreter not found during heavy lifting X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 09:21:47 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 01, 2005 at 08:55:59AM +0200, Michiel Boland wrote: > If I start the test after a fresh reboot, I get tons of errors like the= =20 > following: >=20 > ELF interpreter /libexec/ld-elf.so.1 not found > Abort trap >=20 > but if I interrupt the test, and re-start it, things go ahead as normal.= =20 > Unfortuntately after 16 or so runs of convert-all.sh, the ELF errors=20 > reappear. >=20 > Who has any idea why this is? Probably out of filedescriptors or something similar. See your dmesg to be sure. Marc --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCnX4oezjnobFOgrERAolvAKCEavg8ycyqFHz14oQemmyGjuWR9ACgoesm ChKmSIUADRYMFiOwAUKHAnU= =WOJv -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 09:55:18 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61D0216A41C; Wed, 1 Jun 2005 09:55:18 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from smtp.cegetel.net (mf00.sitadelle.com [212.94.174.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C4A043D4C; Wed, 1 Jun 2005 09:55:17 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [172.16.142.1] (213-223-184-193.dti.cegetel.net [213.223.184.193]) by smtp.cegetel.net (Postfix) with ESMTP id 686991A43ED; Wed, 1 Jun 2005 11:54:17 +0200 (CEST) Message-ID: <429D860A.5000608@club-internet.fr> Date: Wed, 01 Jun 2005 11:55:22 +0200 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050208 X-Accept-Language: fr-fr, fr, en-us, en, ja MIME-Version: 1.0 To: freebsd-alpha@freebsd.org, freebsd-amd64@freebsd.org, freebsd-ia64@freebs.org, freebsd-ppc@freebsd.org X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8B06B2DDF39FC59C5F43C12C" Content-Transfer-Encoding: 8bit Cc: Subject: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 09:55:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8B06B2DDF39FC59C5F43C12C Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi everyone, I made a patch that should fix portability issues of ReiserFS but I don't have access to all platforms supported by FreeBSD. I tested it on sparc64 and Olivier Houchard tried it on arm. I would like to know if someone could test it and report any success or failure? The patch is against latest -CURRENT and should be applied at toplevel source tree (eg. /usr/src). It can be found at: http://www.dumbbell.fr/projects/reiserfs/files/reiserfs-MI-c.patch Thanks in advance! -- Jean-SĂŠbastien PĂŠdron http://www.dumbbell.fr/ PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc --------------enig8B06B2DDF39FC59C5F43C12C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCnYYKa+xGJsFYOlMRAmcmAJ9tRv0IsKa89zWczHk9fEQnKcr4VACg1625 LLcX1/J7mpNOFb9++NmgJNE= =x6GK -----END PGP SIGNATURE----- --------------enig8B06B2DDF39FC59C5F43C12C-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 11:09:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB0F316A41C; Wed, 1 Jun 2005 11:09:20 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 550A043D54; Wed, 1 Jun 2005 11:09:20 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout2.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j51B9IkG004368; Wed, 1 Jun 2005 21:09:18 +1000 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j51B9FqB016780; Wed, 1 Jun 2005 21:09:16 +1000 Date: Wed, 1 Jun 2005 21:09:16 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: "Greg 'groggy' Lehey" In-Reply-To: <20050531034009.GM10912@wantadilla.lemis.com> Message-ID: <20050601204959.R95875@delplex.bde.org> References: <20050530090525.246b0c35.kgunders@teamcool.net> <20050531113955.D91505@delplex.bde.org> <20050531024206.GK10912@wantadilla.lemis.com> <20050531133318.R1603@epsplex.bde.org> <20050531034009.GM10912@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: swap sizing X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 11:09:20 -0000 On Tue, 31 May 2005, Greg 'groggy' Lehey wrote: > On Tuesday, 31 May 2005 at 13:35:38 +1000, Bruce Evans wrote: >> On Tue, 31 May 2005, Greg 'groggy' Lehey wrote: >> >>> On Tuesday, 31 May 2005 at 11:48:19 +1000, Bruce Evans wrote: >>>> On Mon, 30 May 2005, Ken Gunderson wrote: >>>>> And of course that you need at least as much swap as ram if you >>>>> want to get a full dump... >>>> >>>> Of course not. The dump can be written to any disk device that you >>>> don't care about overwriting. >>> >>> Sure. And, apart from swap, what would that be? Why not use it >>> for swap while you're not dumping to it? >> >> Because if swap is configured than it might be used. > > Well, I said "use", not "configure". If it is configured, then its use will be decided by the vm system. I think I know better than the vm system whether its use is useful on my systems. The vm system can only adjust for transient loads better but I think I have enough memory for transients to not be a problem. (I normally have hundreds of MB to spare and this gets used for disk caching; transiently it is used for programs and the disk cache gets depleted a bit.) Bruce From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 13:52:51 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD18E16A41C; Wed, 1 Jun 2005 13:52:51 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7644443D54; Wed, 1 Jun 2005 13:52:51 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j51DrJic020838; Wed, 1 Jun 2005 09:53:19 -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 j51Dqo7C058015; Wed, 1 Jun 2005 09:52:50 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1A98A7306E; Wed, 1 Jun 2005 09:52:50 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050601135250.1A98A7306E@freebsd-current.sentex.ca> Date: Wed, 1 Jun 2005 09:52:50 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 13:52:51 -0000 TB --- 2005-06-01 12:02:51 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-06-01 12:02:51 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-06-01 12:02:51 - cleaning the object tree TB --- 2005-06-01 12:03:27 - checking out the source tree TB --- 2005-06-01 12:03:27 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-06-01 12:03:27 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-06-01 12:09:38 - building world (CFLAGS=-O2 -pipe) TB --- 2005-06-01 12:09:38 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-06-01 12:09:38 - /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-06-01 13:45:38 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-06-01 13:45:38 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-06-01 13:45:38 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Jun 1 13:45:38 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/ip_id.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/in_pcb.c /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/in_pcb.c: In function `in_pcbdisconnect': /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/in_pcb.c:696: error: `pcbinfo' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/in_pcb.c:696: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/in_pcb.c:696: error: for each function it appears in.) /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/in_pcb.c: In function `in_pcbdetach': /tinderbox/CURRENT/amd64/amd64/src/sys/netinet/in_pcb.c:716: error: `pcbinfo' undeclared (first use in this function) *** 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-06-01 13:52:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-06-01 13:52:49 - ERROR: failed to build generic kernel TB --- 2005-06-01 13:52:49 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 13:55:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 127F516A41C; Wed, 1 Jun 2005 13:55:53 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC11843D1D; Wed, 1 Jun 2005 13:55:52 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [192.168.1.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id BF1923F294; Wed, 1 Jun 2005 15:55:50 +0200 (CEST) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 584D527C; Wed, 1 Jun 2005 15:55:50 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 455CC265; Wed, 1 Jun 2005 15:55:50 +0200 (CEST) Date: Wed, 1 Jun 2005 15:55:50 +0200 (CEST) From: Sten Spans To: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= In-Reply-To: <429D860A.5000608@club-internet.fr> Message-ID: References: <429D860A.5000608@club-internet.fr> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-1117634150=:28761" Cc: freebsd-ia64@freebs.org, freebsd-amd64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 13:55:53 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-851401618-1117634150=:28761 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; format=flowed Content-Transfer-Encoding: 8BIT On Wed, 1 Jun 2005, [UTF-8] Jean-SĂŠbastien PĂŠdron wrote: > Hi everyone, > > I made a patch that should fix portability issues of ReiserFS but I > don't have access to all platforms supported by FreeBSD. I tested it on > sparc64 and Olivier Houchard tried it on arm. > > I would like to know if someone could test it and report any success or > failure? > > The patch is against latest -CURRENT and should be applied at toplevel > source tree (eg. /usr/src). It can be found at: > http://www.dumbbell.fr/projects/reiserfs/files/reiserfs-MI-c.patch > > Thanks in advance! A sample reiserfs image would be nice for testing. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem ---559023410-851401618-1117634150=:28761-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 17:09:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DDEA16A41C; Wed, 1 Jun 2005 17:09:50 +0000 (GMT) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 557CB43D49; Wed, 1 Jun 2005 17:09:50 +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 28CBD2A8F6; Wed, 1 Jun 2005 10:09:50 -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 C75CAE2B3; Wed, 1 Jun 2005 10:09:49 -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 j51H9mN5025936; Wed, 1 Jun 2005 10:09:48 -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 j51H9mjJ025935; Wed, 1 Jun 2005 10:09:48 -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: Wed, 1 Jun 2005 10:09:47 -0700 User-Agent: KMail/1.8 References: <20050531133608.J87922@fw.reifenberger.com> <20050531165558.L88820@fw.reifenberger.com> <200505311656.50288.jhb@FreeBSD.org> In-Reply-To: <200505311656.50288.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506011009.48460.peter@wemm.org> Cc: Michael Reifenberger Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 17:09:50 -0000 On Tuesday 31 May 2005 01:56 pm, John Baldwin wrote: > On Tuesday 31 May 2005 11:06 am, Michael Reifenberger wrote: > > On Tue, 31 May 2005, David O'Brien wrote: > > > Ha!! We can only have 1 sector worth of code in boot0. At this > > > point we only have a few bytes of free code space. No where near > > > enough to do the long mode switch. > > > > Sorry. I didnt meant boot0 but btx. I do know that boot0 is too > > small. But btx is already switching to protected mode so it should > > be possible to switch to 64bit mode too. > > Note that the loader uses the BIOS (via virtual 8086 mode) to do all > the disk I/O, etc. Since long mode doesn't support vm86 mode, you'd > end up with a loader that couldn't do any I/O to load the kernel, > etc. unless you started including device drivers for all the > different storage and networking hardware, etc. A 64-bit loader > really isn't feasible unless your 64-bit machine includes firmware > that you can use from 64-bit mode like EFI on ia64 or OFW on sparc. > You probably want to stick with a 32-bit loader on amd64 for now. Yes, there are a lot of good reasons to do it the way it is done, but this is the killer reason. We simply cannot do vm86 or bios calls from a 64 bit loader, period. Other "good" reasons, besides the above: * We don't need to maintain a seperate loader code base * We can load test kernels with an existing loader on a FreeBSD/i386 system (and run from a ramdisk or miniroot) * We would need to maintain 32 bit code to do bios calls anyway, even if we did switch between 32 bit and 64 bit mode on the fly. If we have a complete 32 bit BTX environment, we get massive complexity for little benefit. Disadvantages: * The build is a bit hokey. As was pointed out, the ficl test tools don't build in isolation. * We can't load kernels that are larger than 4GB or into memory above the 4GB memory mark. This actually doesn't matter that much because the kernel runs in virtual address space. Now if somebody wanted to move the kernel to the 16MB mark instead of the 2/4MB mark, that could have some benefits because we'd lose less of the 16MB ISA bounce buffer memory by holding the kernel there. The floppy drive controller is the only thing these days that has issues with that on 64 bit systems. On the other hand, maybe we should implement the code that uses the chipset specific DMA registers to allow the ISA DMA controllers to address to the entire 4GB address space. That would make life easier for the floppy controller. -- 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 Wed Jun 1 18:29:15 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDB8216A41C; Wed, 1 Jun 2005 18:29:15 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from kraid.nerim.net (smtp-103-wednesday.nerim.net [62.4.16.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8669543D1D; Wed, 1 Jun 2005 18:29:15 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [192.168.1.20] (dumbbell.net1.nerim.net [80.65.225.171]) by kraid.nerim.net (Postfix) with ESMTP id 3EF7240F05; Wed, 1 Jun 2005 20:29:12 +0200 (CEST) Message-ID: <429DFEA1.8000004@club-internet.fr> Date: Wed, 01 Jun 2005 20:29:53 +0200 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050503) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sten Spans References: <429D860A.5000608@club-internet.fr> In-Reply-To: X-Enigmail-Version: 0.91.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8271B62ABA2B670E7E0A1703" Cc: freebsd-ppc@freebsd.org, freebsd-amd64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 18:29:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8271B62ABA2B670E7E0A1703 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sten Spans wrote: > A sample reiserfs image would be nice for testing. You're right, an image is available here (14 Mb compressed): http://people.freebsd.org/~dumbbell/reiserfs/images/REISERFS.bz2 --=20 Jean-S=C3=A9bastien P=C3=A9dron http://www.dumbbell.fr/ PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc --------------enig8271B62ABA2B670E7E0A1703 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCnf6wa+xGJsFYOlMRAg8CAJ98kKzh1g5VUfbJpbwHWSe6oj9vBQCeKYUR vqgmi1EuQoSKC5u8E3MMFvk= =gDRR -----END PGP SIGNATURE----- --------------enig8271B62ABA2B670E7E0A1703-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 22:05:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84B7C16A41C for ; Wed, 1 Jun 2005 22:05:34 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: from shinzon.blueboard.cz (shinzon.blueboard.cz [217.11.249.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C6AD43D1D for ; Wed, 1 Jun 2005 22:05:32 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 35881 invoked by uid 89); 1 Jun 2005 22:05:30 -0000 Received: by simscan 1.1.0 ppid: 35873, pid: 35876, t: 3.4278s scanners: clamav: 0.83/m:30/d:757 spam: 3.0.2 Received: from unknown (HELO ?10.15.141.2?) (tomas@blueboard.cz@217.11.239.237) by shinzon.blueboard.cz with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jun 2005 22:05:27 -0000 Message-ID: <429E3149.8030101@hosting50.cz> Date: Thu, 02 Jun 2005 00:06:01 +0200 From: Tomas Randa User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050528) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> In-Reply-To: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on shinzon.blueboard.cz X-Spam-Level: X-Spam-Status: No, score=-3.7 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.3 Subject: Re: [CPU temperature] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 22:05:34 -0000 Hello, I had problems with cooling my AMD64/Socket 754/3200+ under 5.4. But Athlon 64 support CoolNQuiet (PowerNow K8) which is implanted into current as cpufreq - "device cpufreq" in kernel configuration and then powerd_enable="YES" in rc.conf. Without cpufreq I had about 60˚ with my quiet cooling, now I have 38˚, because my desktop system don`t have heavy load. Tomas Randa tfagart@brozs.net wrote: >Hello, > >After having done my upgrade to 5.4Release I've noticed that the the CPU >temperature of my box is 10 degrĂŠ celsius higher than it was before with >5.3R. >I haven't changed anything in terms of number of running process, and >nothing for me could explain this increase. > >Also I've done the same test with i386 release, and there's no such a >behaviour. > >One of my friend is having the same type of issue with different hardware >(but still AMD64). > >The tool I'm using to monitor tempertature is xmbmon-205_1 + Cacti >Software > >FreeBSD www 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #43: Fri May 20 16:17:04 >CEST 2005 root@www:/usr/src/sys/amd64/compile/TOM amd64 > >ww1# pciconf -lv >agp0@pci0:0:0: class=0x060000 card=0x80a31043 chip=0x31881106 rev=0x01 >hdr=0x00 vendor = 'VIA Technologies Inc' > device = 'Apollo K8HTB CPU to PCI Bridge' > class = bridge > subclass = HOST-PCI >pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb1881106 rev=0x00 >hdr=0x01 vendor = 'VIA Technologies Inc' > device = 'Apollo K8HTB CPU to AGP 2.0/3.0 Bridge' > class = bridge > subclass = PCI-PCI >fwohci0@pci0:7:0: class=0x0c0010 card=0x808a1043 chip=0x30441106 rev=0x80 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller' > class = serial bus > subclass = FireWire >atapci0@pci0:8:0: class=0x010400 card=0x80f51043 chip=0x3373105a rev=0x02 >hdr=0x00 > vendor = 'Promise Technology Inc' > device = 'PDC20378? FastTrak RAID Controller' > class = mass storage > subclass = RAID >bktr0@pci0:9:0: class=0x040000 card=0x13eb0070 chip=0x036e109e rev=0x02 >hdr=0x00 vendor = 'Brooktree Corporation' > device = 'Bt878 MediaStream Controller' > class = multimedia > subclass = video >none0@pci0:9:1: class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 >hdr=0x00 vendor = 'Brooktree Corporation' > device = 'Bt878/Fusion878A Video Capture (Audio Section)' > class = multimedia >skc0@pci0:10:0: class=0x020000 card=0x811a1043 chip=0x432011ab rev=0x13 >hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology >Ltd)' > device = '88E8001 Gigabit 32-bit Ethernet Controller with Integrated >PHY' > class = network > subclass = ethernet >ahc0@pci0:11:0: class=0x010000 card=0xa1809005 chip=0x00109005 rev=0x00 >hdr=0x00 vendor = 'Adaptec Inc' > device = 'AHA-2940U2W/U2B AHA-2950U2W Ultra2 SCSI Controller' > class = mass storage > subclass = SCSI >none1@pci0:12:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 > >hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5213 802.11a/b/g Wireless Adapter' > class = network > subclass = ethernet >pcm0@pci0:13:0: class=0x040100 card=0x80271102 chip=0x00021102 rev=0x06 >hdr=0x00 vendor = 'Creative Labs' > device = 'EMU10000 Sound Blaster Live! (Also Live! 5.1) - OEM from >DELL - CT4780' > class = multimedia > subclass = audio >emujoy0@pci0:13:1: class=0x098000 card=0x00201102 chip=0x70021102 rev=0x06 >hdr=0x00 > vendor = 'Creative Labs' > device = 'EMU10000 Game Port' > class = input device >xl0@pci0:14:0: class=0x020000 card=0x905510b7 chip=0x905510b7 rev=0x24 >hdr=0x00 vendor = '3COM Corp, Networking Division' > device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC' > class = network > subclass = ethernet >atapci1@pci0:15:0: class=0x010400 card=0x80ed1043 chip=0x31491106 rev=0x80 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = '??? SATA RAID Controller' > class = mass storage > subclass = RAID >atapci2@pci0:15:1: class=0x01018a card=0x80ed1043 chip=0x05711106 rev=0x06 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' > class = mass storage > subclass = ATA >uhci0@pci0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' > class = serial bus > subclass = USB >uhci1@pci0:16:1: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' > class = serial bus > subclass = USB >uhci2@pci0:16:2: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' > class = serial bus > subclass = USB >uhci3@pci0:16:3: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' > class = serial bus > subclass = USB >ehci0@pci0:16:4: class=0x0c0320 card=0x80ed1043 chip=0x31041106 rev=0x86 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT6202 USB 2.0 Enhanced Host Controller' > class = serial bus > subclass = USB >isab0@pci0:17:0: class=0x060100 card=0x80ed1043 chip=0x32271106 rev=0x00 >hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT8237 PCI-to-ISA Bridge' > class = bridge > subclass = PCI-ISA >hostb0@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 >hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' > class = bridge > subclass = HOST-PCI >hostb1@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 >hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon 64 / Opteron Address Map' > class = bridge > subclass = HOST-PCI >hostb2@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 >hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon 64 / Opteron DRAM Controller' > class = bridge > subclass = HOST-PCI >hostb3@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 >hdr=0x00 > vendor = 'Advanced Micro Devices (AMD)' > device = 'Athlon 64 / Opteron Miscellaneous Control' > class = bridge > subclass = HOST-PCI >drm0@pci1:0:0: class=0x030000 card=0x00021787 chip=0x51591002 rev=0x00 >hdr=0x00 > vendor = 'ATI Technologies Inc.' > device = 'RV100 Radeon 7000 / Radeon VE' > class = display > subclass = VGA > > >Do you have any clue for this increase ? > >Thanks > >Thomas > > >_______________________________________________ >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" > > From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 1 22:33:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A0CF16A41C; Wed, 1 Jun 2005 22:33:23 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E33843D48; Wed, 1 Jun 2005 22:33:20 +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 j51MXgaS053209; Wed, 1 Jun 2005 18:33:43 -0400 (EDT) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Wed, 1 Jun 2005 18:33:12 -0400 User-Agent: KMail/1.6.2 References: <429D860A.5000608@club-internet.fr> <429DFEA1.8000004@club-internet.fr> In-Reply-To: <429DFEA1.8000004@club-internet.fr> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <200506011833.12686.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.85.1/906/Wed Jun 1 17:38:56 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-ia64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 22:33:23 -0000 On Wednesday 01 June 2005 02:29 pm, Jean-SĂŠbastien PĂŠdron wrote: > Sten Spans wrote: > > A sample reiserfs image would be nice for testing. > > You're right, an image is available here (14 Mb compressed): > http://people.freebsd.org/~dumbbell/reiserfs/images/REISERFS.bz2 I was able to mount and read it on amd64 but I had to modify src/sys/modules/reiserfs/Makefile a bit (I will explain it later). beastie# bunzip2 REISERFS.bz2 beastie# mdconfig -a -t vnode -f REISERFS -u 0 beastie# mount_reiserfs /dev/md0 /mnt beastie# ls -l /mnt total 8056 drwxr-xr-x 2 root wheel 96 8 6 2004 Evanescence drwxr-xr-x 5 1000 1000 120 9 1 2004 GNUstep -rw-r--r-- 1 1000 1000 4548644 8 23 2004 Shrek.mp3 lrwxrwxrwx 1 root wheel 27 9 1 2004 dir_symlink -> GNUstep/Library/WindowMaker lrwxrwxrwx 1 root wheel 41 9 1 2004 evanesnce.mp3 -> Evanescence/Evanescence - My Immortal.mp3 -rw-r--r-- 2 1000 1000 3176 9 1 2004 file_hardlink lrwxrwxrwx 1 root wheel 23 9 1 2004 file_symlink -> GNUstep/Defaults/WPrefs -r-xr-xr-x 1 root wheel 3680076 10 28 2004 ls -rw-r--r-- 1 root wheel 70 8 6 2004 motd beastie# cat /mnt/motd Linux yui 2.4.26 #1 SMP Tue Jun 15 11:04:53 CEST 2004 i686 GNU/Linux beastie# uname -a FreeBSD beastie.xxx.xxx.xxx 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Wed Jun 1 17:22:23 EDT 2005 jkim@beastie.xxx.xxx.xxx:/usr/src/sys/amd64/compile/BEASTIE amd64 beastie# umount /mnt beastie# mdconfig -d -u 0 The kernel module doesn't load because of an amd64-specific GCC 3.4 optimization bug. To work around: Index: Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/reiserfs/Makefile,v retrieving revision 1.1 diff -u -r1.1 Makefile --- Makefile 24 May 2005 12:30:13 -0000 1.1 +++ Makefile 1 Jun 2005 22:22:52 -0000 @@ -8,4 +8,8 @@ reiserfs_namei.c reiserfs_prints.c reiserfs_stree.c \ reiserfs_vfsops.c reiserfs_vnops.c +.if ${MACHINE_ARCH} == "amd64" +CFLAGS+= -minline-all-stringops +.endif + .include Without this, I get: link_elf_obj: symbol memset undefined kldload: Unsupported file type Note: 'Unsupported file type' is somewhat misleading here. It just means linker failed to find a symbol, in this case. For more information about the GCC bug, follow the thread: http://docs.freebsd.org/cgi/mid.cgi?IDTR9T00.LMF Thanks a lot for your work! Jung-uk Kim * Postscript: Is it legal to redistribute your MP3 files? ;-) From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 08:26:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ACC116A41C; Thu, 2 Jun 2005 08:26:19 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA75943D1F; Thu, 2 Jun 2005 08:26:18 +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 j528QHhW036196; Thu, 2 Jun 2005 01:26:17 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j528QFXV036195; Thu, 2 Jun 2005 01:26:15 -0700 (PDT) (envelope-from obrien) Date: Thu, 2 Jun 2005 01:26:15 -0700 From: "David O'Brien" To: Jung-uk Kim Message-ID: <20050602082615.GA36096@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Jung-uk Kim , freebsd-amd64@freebsd.org, freebsd-ia64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ppc@freebsd.org References: <429D860A.5000608@club-internet.fr> <429DFEA1.8000004@club-internet.fr> <200506011833.12686.jkim@niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506011833.12686.jkim@niksun.com> 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-ppc@freebsd.org, freebsd-alpha@freebsd.org, freebsd-amd64@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@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, 02 Jun 2005 08:26:19 -0000 On Wed, Jun 01, 2005 at 06:33:12PM -0400, Jung-uk Kim wrote: > The kernel module doesn't load because of an amd64-specific GCC 3.4 > optimization bug. To work around: > > Index: Makefile > =================================================================== > RCS file: /home/ncvs/src/sys/modules/reiserfs/Makefile,v > retrieving revision 1.1 > diff -u -r1.1 Makefile > --- Makefile 24 May 2005 12:30:13 -0000 1.1 > +++ Makefile 1 Jun 2005 22:22:52 -0000 > @@ -8,4 +8,8 @@ > reiserfs_namei.c reiserfs_prints.c reiserfs_stree.c \ > reiserfs_vfsops.c reiserfs_vnops.c > > +.if ${MACHINE_ARCH} == "amd64" > +CFLAGS+= -minline-all-stringops > +.endif > + Unfortunately we really don't like to put this type of CFLAGS in non-*.mk files. Since we know the GCC 3.4.2 compiler bugs will be fixed, I suggest we just document this issue and be happy that otherwise the code is ready to go on FreeBSD/amd64. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 08:29:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FE9416A41C for ; Thu, 2 Jun 2005 08:29:27 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4616943D55 for ; Thu, 2 Jun 2005 08:29:27 +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 j528TQ6B036309; Thu, 2 Jun 2005 01:29:26 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j528TPnl036308; Thu, 2 Jun 2005 01:29:25 -0700 (PDT) (envelope-from obrien) Date: Thu, 2 Jun 2005 01:29:25 -0700 From: "David O'Brien" To: Peter Wemm Message-ID: <20050602082925.GB36096@dragon.NUXI.org> References: <20050531133608.J87922@fw.reifenberger.com> <20050531165558.L88820@fw.reifenberger.com> <200505311656.50288.jhb@FreeBSD.org> <200506011009.48460.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506011009.48460.peter@wemm.org> 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: Michael Reifenberger , freebsd-amd64@freebsd.org Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@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, 02 Jun 2005 08:29:27 -0000 On Wed, Jun 01, 2005 at 10:09:47AM -0700, Peter Wemm wrote: > Yes, there are a lot of good reasons to do it the way it is done, but > this is the killer reason. We simply cannot do vm86 or bios calls from > a 64 bit loader, period. > > Other "good" reasons, besides the above: > * We don't need to maintain a seperate loader code base > * We can load test kernels with an existing loader on a FreeBSD/i386 > system (and run from a ramdisk or miniroot) > * We would need to maintain 32 bit code to do bios calls anyway, even if > we did switch between 32 bit and 64 bit mode on the fly. If we have a > complete 32 bit BTX environment, we get massive complexity for little > benefit. I personally am very happy with the way we handle switching into long mode and loading 64-bit kernels today. :-) I think the current advantages list > disadvantages list. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 12:38:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4827116A41C; Thu, 2 Jun 2005 12:38:32 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from smtp.cegetel.net (mf00.sitadelle.com [212.94.174.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B35DC43D1F; Thu, 2 Jun 2005 12:38:31 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [172.16.142.1] (213-223-184-201.dti.cegetel.net [213.223.184.201]) by smtp.cegetel.net (Postfix) with ESMTP id 69B7A1A42AA; Thu, 2 Jun 2005 14:38:27 +0200 (CEST) Message-ID: <429EFDC1.6040905@club-internet.fr> Date: Thu, 02 Jun 2005 14:38:25 +0200 From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050208 X-Accept-Language: fr-fr, fr, en-us, en, ja MIME-Version: 1.0 To: obrien@freebsd.org References: <429D860A.5000608@club-internet.fr> <429DFEA1.8000004@club-internet.fr> <200506011833.12686.jkim@niksun.com> <20050602082615.GA36096@dragon.NUXI.org> In-Reply-To: <20050602082615.GA36096@dragon.NUXI.org> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC6997053FA7B93B9E39A6752" Content-Transfer-Encoding: 8bit Cc: freebsd-ia64@freebsd.org, freebsd-ppc@freebsd.org, freebsd-amd64@freebsd.org, freebsd-alpha@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 12:38:32 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC6997053FA7B93B9E39A6752 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit David O'Brien wrote: > On Wed, Jun 01, 2005 at 06:33:12PM -0400, Jung-uk Kim wrote: > >>The kernel module doesn't load because of an amd64-specific GCC 3.4 >>optimization bug. To work around: >> >>Index: Makefile >>=================================================================== >>RCS file: /home/ncvs/src/sys/modules/reiserfs/Makefile,v >>retrieving revision 1.1 >>diff -u -r1.1 Makefile >>--- Makefile 24 May 2005 12:30:13 -0000 1.1 >>+++ Makefile 1 Jun 2005 22:22:52 -0000 >>@@ -8,4 +8,8 @@ >> reiserfs_namei.c reiserfs_prints.c reiserfs_stree.c \ >> reiserfs_vfsops.c reiserfs_vnops.c >> >>+.if ${MACHINE_ARCH} == "amd64" >>+CFLAGS+= -minline-all-stringops >>+.endif >>+ > > Unfortunately we really don't like to put this type of CFLAGS in non-*.mk > files. Since we know the GCC 3.4.2 compiler bugs will be fixed, I > suggest we just document this issue and be happy that otherwise the code > is ready to go on FreeBSD/amd64. Thank you Jung-Ku and David for your feedback. Olivier Houchard could test it on amd64 too and found another workaround for this same issue. The problem come from this macro: #define INITIALIZE_PATH(var) \ struct path var = { ILLEGAL_PATH_ELEMENT_OFFSET, } where gcc generates a call to memset(). By replacing it with: #define INITIALIZE_PATH(var) \ struct path var; \ bzero(&var); \ var.path_length = ILLEGAL_PATH_ELEMENT_OFFSET it works. I can add this (in favor of the CFLAGS workaround) and document it. When a fixed gcc will be in the tree, it'll be removed. -- Jean-Sébastien Pédron http://www.dumbbell.fr/ PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc --------------enigC6997053FA7B93B9E39A6752 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCnv3Ja+xGJsFYOlMRAqrpAJ4ze67ysxFGJVNSX5YGdIbTos3tEwCeODRC GAXpNeLbN2Y3+IvvmxJaLao= =A2AX -----END PGP SIGNATURE----- --------------enigC6997053FA7B93B9E39A6752-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 13:09:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3D3916A41C for ; Thu, 2 Jun 2005 13:09:01 +0000 (GMT) (envelope-from etoll@vipstructures.com) Received: from rodan.vipstructures.com (rodan.vipstructures.com [66.195.71.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96FA843D1D for ; Thu, 2 Jun 2005 13:09:01 +0000 (GMT) (envelope-from etoll@vipstructures.com) Received: from localhost (localhost.vipstructures.com [127.0.0.1]) by rodan.vipstructures.com (Postfix) with ESMTP id D0ADC1EE828 for ; Thu, 2 Jun 2005 09:09:00 -0400 (EDT) Received: from mothra.vipstructures.com (mothra.vipstructures.com [192.168.1.3]) by rodan.vipstructures.com (Postfix) with ESMTP id A35A31EE824 for ; Thu, 2 Jun 2005 09:09:00 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 2 Jun 2005 09:08:55 -0400 Message-ID: <9BC86C67C3AF7646B9C5382020457A944E4D51@VIP10-WIN2K> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problem with the command mail Thread-index: AcVndDn7FvK7GpodSki8RMkYl0vxhg== From: "Toll, Eric" To: Subject: Problem with the command mail X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 13:09:02 -0000 Greetings all, I have a problem with my AMD64 FreeBSD server which is: FreeBSD rodan.vipstructures.com 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Fri May 13 12:55:54 EDT 2005 eric@rodan.vipstructures.com:/u sr/obj/usr/src/sys/HAMMER amd64 When I used the command 'mail' the system does NOTHING. I don't know what I did or did not do to break this. System is running Postfix flawlessly. System can also run sendmail with out any issues. Below is a paste from my term session. [eric@rodan]/home/eric(100): su Password: You have mail. [root@rodan]/home/eric(101)# mail [root@rodan]/home/eric(102)# mailq Mail queue is empty [root@rodan]/home/eric(103)# which mail /usr/bin/mail [root@rodan]/home/eric(104)# When I login as root, system tells me I have mail, yet the file /var/mail/root is empty. Any pointers or tips would be greatly apprecaited.=20 TIA Eric From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 13:56:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D674316A41C for ; Thu, 2 Jun 2005 13:56:50 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from www1.brozs.net (mail.brozs.net [82.67.204.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D14243D5C for ; Thu, 2 Jun 2005 13:56:49 +0000 (GMT) (envelope-from tfagart@brozs.net) Received: from localhost (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id 2A793454B; Thu, 2 Jun 2005 15:29:11 +0200 (CEST) Received: from www1.brozs.net ([127.0.0.1]) by localhost (www1.brozs.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20945-04; Thu, 2 Jun 2005 15:29:10 +0200 (CEST) Received: from webmail.brozs.net (localhost.brozs.net [127.0.0.1]) by www1.brozs.net (Postfix) with ESMTP id E761C4548; Thu, 2 Jun 2005 15:29:09 +0200 (CEST) Received: from 217.119.178.19 (SquirrelMail authenticated user tfagart@brozs.net); by webmail.brozs.net with HTTP; Thu, 2 Jun 2005 15:29:09 +0200 (CEST) Message-ID: <32734.217.119.178.19.1117718949.squirrel@217.119.178.19> In-Reply-To: <429E3149.8030101@hosting50.cz> References: <5979.217.119.178.19.1117524590.squirrel@217.119.178.19> <429E3149.8030101@hosting50.cz> Date: Thu, 2 Jun 2005 15:29:09 +0200 (CEST) From: tfagart@brozs.net To: "Tomas Randa" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at brozs.net Cc: freebsd-amd64@freebsd.org Subject: Re: [CPU temperature] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 13:56:51 -0000 Thanks for the information, but is there any other solutions for Stable release ? > Hello, > > I had problems with cooling my AMD64/Socket 754/3200+ under 5.4. But > Athlon 64 support CoolNQuiet (PowerNow K8) which is implanted into > current as cpufreq - "device cpufreq" in kernel configuration and then > powerd_enable="YES" in rc.conf. > Without cpufreq I had about 60˚ with my quiet cooling, now I have 38˚, > because my desktop system don`t have heavy load. > > Tomas Randa > > tfagart@brozs.net wrote: > >>Hello, >> >>After having done my upgrade to 5.4Release I've noticed that the the CPU >>temperature of my box is 10 degrĂŠ celsius higher than it was before with >>5.3R. >>I haven't changed anything in terms of number of running process, and >>nothing for me could explain this increase. >> >>Also I've done the same test with i386 release, and there's no such a >>behaviour. >> >>One of my friend is having the same type of issue with different hardware >>(but still AMD64). >> >>The tool I'm using to monitor tempertature is xmbmon-205_1 + Cacti >>Software >> >>FreeBSD www 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #43: Fri May 20 >> 16:17:04 >>CEST 2005 root@www:/usr/src/sys/amd64/compile/TOM amd64 >> >>ww1# pciconf -lv >>agp0@pci0:0:0: class=0x060000 card=0x80a31043 chip=0x31881106 rev=0x01 >>hdr=0x00 vendor = 'VIA Technologies Inc' >> device = 'Apollo K8HTB CPU to PCI Bridge' >> class = bridge >> subclass = HOST-PCI >>pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb1881106 rev=0x00 >>hdr=0x01 vendor = 'VIA Technologies Inc' >> device = 'Apollo K8HTB CPU to AGP 2.0/3.0 Bridge' >> class = bridge >> subclass = PCI-PCI >>fwohci0@pci0:7:0: class=0x0c0010 card=0x808a1043 chip=0x30441106 rev=0x80 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller' >> class = serial bus >> subclass = FireWire >>atapci0@pci0:8:0: class=0x010400 card=0x80f51043 chip=0x3373105a rev=0x02 >>hdr=0x00 >> vendor = 'Promise Technology Inc' >> device = 'PDC20378? FastTrak RAID Controller' >> class = mass storage >> subclass = RAID >>bktr0@pci0:9:0: class=0x040000 card=0x13eb0070 chip=0x036e109e rev=0x02 >>hdr=0x00 vendor = 'Brooktree Corporation' >> device = 'Bt878 MediaStream Controller' >> class = multimedia >> subclass = video >>none0@pci0:9:1: class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 >>hdr=0x00 vendor = 'Brooktree Corporation' >> device = 'Bt878/Fusion878A Video Capture (Audio Section)' >> class = multimedia >>skc0@pci0:10:0: class=0x020000 card=0x811a1043 chip=0x432011ab rev=0x13 >>hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology >>Ltd)' >> device = '88E8001 Gigabit 32-bit Ethernet Controller with >> Integrated >>PHY' >> class = network >> subclass = ethernet >>ahc0@pci0:11:0: class=0x010000 card=0xa1809005 chip=0x00109005 rev=0x00 >>hdr=0x00 vendor = 'Adaptec Inc' >> device = 'AHA-2940U2W/U2B AHA-2950U2W Ultra2 SCSI Controller' >> class = mass storage >> subclass = SCSI >>none1@pci0:12:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 >> >>hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR5213 802.11a/b/g Wireless Adapter' >> class = network >> subclass = ethernet >>pcm0@pci0:13:0: class=0x040100 card=0x80271102 chip=0x00021102 rev=0x06 >>hdr=0x00 vendor = 'Creative Labs' >> device = 'EMU10000 Sound Blaster Live! (Also Live! 5.1) - OEM from >>DELL - CT4780' >> class = multimedia >> subclass = audio >>emujoy0@pci0:13:1: class=0x098000 card=0x00201102 chip=0x70021102 >> rev=0x06 >>hdr=0x00 >> vendor = 'Creative Labs' >> device = 'EMU10000 Game Port' >> class = input device >>xl0@pci0:14:0: class=0x020000 card=0x905510b7 chip=0x905510b7 rev=0x24 >>hdr=0x00 vendor = '3COM Corp, Networking Division' >> device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC' >> class = network >> subclass = ethernet >>atapci1@pci0:15:0: class=0x010400 card=0x80ed1043 chip=0x31491106 >> rev=0x80 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = '??? SATA RAID Controller' >> class = mass storage >> subclass = RAID >>atapci2@pci0:15:1: class=0x01018a card=0x80ed1043 chip=0x05711106 >> rev=0x06 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' >> class = mass storage >> subclass = ATA >>uhci0@pci0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' >> class = serial bus >> subclass = USB >>uhci1@pci0:16:1: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' >> class = serial bus >> subclass = USB >>uhci2@pci0:16:2: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' >> class = serial bus >> subclass = USB >>uhci3@pci0:16:3: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' >> class = serial bus >> subclass = USB >>ehci0@pci0:16:4: class=0x0c0320 card=0x80ed1043 chip=0x31041106 rev=0x86 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT6202 USB 2.0 Enhanced Host Controller' >> class = serial bus >> subclass = USB >>isab0@pci0:17:0: class=0x060100 card=0x80ed1043 chip=0x32271106 rev=0x00 >>hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT8237 PCI-to-ISA Bridge' >> class = bridge >> subclass = PCI-ISA >>hostb0@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 >>hdr=0x00 >> vendor = 'Advanced Micro Devices (AMD)' >> device = 'Athlon 64 / Opteron HyperTransport Technology >> Configuration' >> class = bridge >> subclass = HOST-PCI >>hostb1@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 >>hdr=0x00 >> vendor = 'Advanced Micro Devices (AMD)' >> device = 'Athlon 64 / Opteron Address Map' >> class = bridge >> subclass = HOST-PCI >>hostb2@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 >>hdr=0x00 >> vendor = 'Advanced Micro Devices (AMD)' >> device = 'Athlon 64 / Opteron DRAM Controller' >> class = bridge >> subclass = HOST-PCI >>hostb3@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 >>hdr=0x00 >> vendor = 'Advanced Micro Devices (AMD)' >> device = 'Athlon 64 / Opteron Miscellaneous Control' >> class = bridge >> subclass = HOST-PCI >>drm0@pci1:0:0: class=0x030000 card=0x00021787 chip=0x51591002 rev=0x00 >>hdr=0x00 >> vendor = 'ATI Technologies Inc.' >> device = 'RV100 Radeon 7000 / Radeon VE' >> class = display >> subclass = VGA >> >> >>Do you have any clue for this increase ? >> >>Thanks >> >>Thomas >> >> >>_______________________________________________ >>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" >> >> > > _______________________________________________ > 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" > From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 15:32:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4212A16A41C; Thu, 2 Jun 2005 15:32:37 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C014A43D1F; Thu, 2 Jun 2005 15:32:34 +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 j52FX2LR069613; Thu, 2 Jun 2005 11:33:03 -0400 (EDT) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: =?utf-8?q?Jean-S=C3=A9bastien_P=C3=A9dron?= Date: Thu, 2 Jun 2005 11:32:29 -0400 User-Agent: KMail/1.6.2 References: <429D860A.5000608@club-internet.fr> <20050602082615.GA36096@dragon.NUXI.org> <429EFDC1.6040905@club-internet.fr> In-Reply-To: <429EFDC1.6040905@club-internet.fr> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <200506021132.29814.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.85.1/906/Wed Jun 1 17:38:56 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org, freebsd-ia64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 15:32:37 -0000 On Thursday 02 June 2005 08:38 am, Jean-SĂŠbastien PĂŠdron wrote: > David O'Brien wrote: > > On Wed, Jun 01, 2005 at 06:33:12PM -0400, Jung-uk Kim wrote: > >>The kernel module doesn't load because of an amd64-specific GCC > >> 3.4 optimization bug. To work around: > >> > >>Index: Makefile > >>================================================================= > >>== RCS file: /home/ncvs/src/sys/modules/reiserfs/Makefile,v > >> retrieving revision 1.1 > >>diff -u -r1.1 Makefile > >>--- Makefile 24 May 2005 12:30:13 -0000 1.1 > >>+++ Makefile 1 Jun 2005 22:22:52 -0000 > >>@@ -8,4 +8,8 @@ > >> reiserfs_namei.c reiserfs_prints.c reiserfs_stree.c \ > >> reiserfs_vfsops.c reiserfs_vnops.c > >> > >>+.if ${MACHINE_ARCH} == "amd64" > >>+CFLAGS+= -minline-all-stringops > >>+.endif > >>+ > > > > Unfortunately we really don't like to put this type of CFLAGS in > > non-*.mk files. Yeah, I agree. That's ugly. > > Since we know the GCC 3.4.2 compiler bugs will be fixed, I suggest > > we just document this issue and be happy that otherwise the code > > is ready to go on FreeBSD/amd64. Will it be fixed? That's good news. Do you know if there's GCC PR? > Thank you Jung-Ku and David for your feedback. ------- Jung-uk ;-) > Olivier Houchard could test it on amd64 too and found another > workaround for this same issue. Cool. It's good to hear that it was found. > The problem come from this macro: > #define INITIALIZE_PATH(var) \ > struct path var = { ILLEGAL_PATH_ELEMENT_OFFSET, } > where gcc generates a call to memset(). By replacing it with: > #define INITIALIZE_PATH(var) \ > struct path var; \ > bzero(&var); \ ------------ bzero(&var, sizeof(struct path)); > var.path_length = ILLEGAL_PATH_ELEMENT_OFFSET > it works. Yes, it works (after the above fix). > I can add this (in favor of the CFLAGS workaround) and document it. > When a fixed gcc will be in the tree, it'll be removed. Please do so. Thanks again, Jung-uk Kim > -- > Jean-SĂŠbastien PĂŠdron > http://www.dumbbell.fr/ > > PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 16:03:49 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EEBF16A41C; Thu, 2 Jun 2005 16:03:49 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from smtp.cegetel.net (mf00.sitadelle.com [212.94.174.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F24743D48; Thu, 2 Jun 2005 16:03:49 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [172.16.142.1] (213-223-184-193.dti.cegetel.net [213.223.184.193]) by smtp.cegetel.net (Postfix) with ESMTP id 9C0BB1A447F; Thu, 2 Jun 2005 18:03:46 +0200 (CEST) Message-ID: <429F2DD8.7060700@club-internet.fr> Date: Thu, 02 Jun 2005 18:03:36 +0200 From: =?UTF-8?B?SmVhbi1Tw6liYXN0aWVuIFDDqWRyb24=?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050208 X-Accept-Language: fr-fr, fr, en-us, en, ja MIME-Version: 1.0 To: Jung-uk Kim , freebsd-ppc@FreeBSD.org, freebsd-alpha@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ia64@FreeBSD.org References: <429D860A.5000608@club-internet.fr> <20050602082615.GA36096@dragon.NUXI.org> <429EFDC1.6040905@club-internet.fr> <200506021132.29814.jkim@niksun.com> In-Reply-To: <200506021132.29814.jkim@niksun.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1DB757AD300B6BB2E060F4F5" Content-Transfer-Encoding: 8bit Cc: Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 16:03:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1DB757AD300B6BB2E060F4F5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Jung-uk Kim wrote: >>Thank you Jung-Ku and David for your feedback. > > ------- > Jung-uk ;-) Oops, sorry for this, Jung-uk :) >>The problem come from this macro: >>#define INITIALIZE_PATH(var) \ >> struct path var = { ILLEGAL_PATH_ELEMENT_OFFSET, } >>where gcc generates a call to memset(). By replacing it with: >>#define INITIALIZE_PATH(var) \ >> struct path var; \ >> bzero(&var); \ > > ------------ > bzero(&var, sizeof(struct path)); > >> var.path_length = ILLEGAL_PATH_ELEMENT_OFFSET >>it works. > > Yes, it works (after the above fix). I just wrote this code from memory, Olivier's fix was right at the beginning. -- Jean-SĂŠbastien PĂŠdron http://www.dumbbell.fr/ PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc --------------enig1DB757AD300B6BB2E060F4F5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCny3pa+xGJsFYOlMRAol+AKCSuL/Lwhn6zWpKHEyfh6hZt7apgwCdG5m1 c1PnHQDMh7liszhVloDF7ic= =D8Lg -----END PGP SIGNATURE----- --------------enig1DB757AD300B6BB2E060F4F5-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 16:40:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B41A16A41C; Thu, 2 Jun 2005 16:40:34 +0000 (GMT) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04ACF43D1D; Thu, 2 Jun 2005 16:40:33 +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 C29822A8DA; Thu, 2 Jun 2005 09:40:33 -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 74FF5E2B3; Thu, 2 Jun 2005 09:40:33 -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 j52GeW9Z053592; Thu, 2 Jun 2005 09:40:32 -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 j52GeW6o053591; Thu, 2 Jun 2005 09:40:32 -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: obrien@freebsd.org Date: Thu, 2 Jun 2005 09:40:31 -0700 User-Agent: KMail/1.8 References: <20050531133608.J87922@fw.reifenberger.com> <200506011009.48460.peter@wemm.org> <20050602082925.GB36096@dragon.NUXI.org> In-Reply-To: <20050602082925.GB36096@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506020940.32312.peter@wemm.org> Cc: Michael Reifenberger , freebsd-amd64@freebsd.org Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 16:40:34 -0000 On Thursday 02 June 2005 01:29 am, David O'Brien wrote: > On Wed, Jun 01, 2005 at 10:09:47AM -0700, Peter Wemm wrote: > > Yes, there are a lot of good reasons to do it the way it is done, > > but this is the killer reason. We simply cannot do vm86 or bios > > calls from a 64 bit loader, period. > > > > Other "good" reasons, besides the above: > > * We don't need to maintain a seperate loader code base > > * We can load test kernels with an existing loader on a > > FreeBSD/i386 system (and run from a ramdisk or miniroot) > > * We would need to maintain 32 bit code to do bios calls anyway, > > even if we did switch between 32 bit and 64 bit mode on the fly. > > If we have a complete 32 bit BTX environment, we get massive > > complexity for little benefit. > > I personally am very happy with the way we handle switching into long > mode and loading 64-bit kernels today. :-) I think the current > advantages list > disadvantages list. BTW: I especially like sys/amd64/amd64/locore.s versus sys/i386/i386/locore.s -- 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 Thu Jun 2 20:55:37 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A887916A41C for ; Thu, 2 Jun 2005 20:55:37 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56BAC43D5C for ; Thu, 2 Jun 2005 20:55:37 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from ranger.anduin.net ([81.0.162.52] helo=[192.168.1.110]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1Ddwj1-000I8h-TU for amd64@freebsd.org; Thu, 02 Jun 2005 22:55:36 +0200 Mime-Version: 1.0 (Apple Message framework v730) Content-Transfer-Encoding: 7bit Message-Id: <0845B29D-400C-4408-9473-960273D88078@anduin.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: amd64@freebsd.org From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Thu, 2 Jun 2005 22:55:04 +0200 X-Mailer: Apple Mail (2.730) Cc: Subject: Strange console output - scary X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 20:55:37 -0000 Hi, When putting some quite significant stress on the system (namely by forwarding about a thousand mails at once through exim, triggering spamassassin and clamav scans and stuff), also including swapping and loads of processes fighting over the CPUs, I start getting the following output on my serial console. The box seems unresponsive for a while, but does come back once the load/swapping lessens. This is a dual opteron on a Tyan S2882 mainboard, 1GB memory, ultra320 scsi disk on the onboard adaptec controller plus a pair of SATA drives in gmirror (raid-1) on the onboard SiI controller. Swap is on the SCSI drive. Could this be related to the panic I saw in my earlier messages (5.4- panic)? /Eirik KDB: stack backtrace: getdirtybuf() at getdirtybuf+0x1bb flush_deplist() at flush_deplist+0x57 flush_inodedep_deps() at flush_inodedep_deps+0x89 softdep_sync_metadata() at softdep_sync_metadata+0x66 ffs_fsync() at ffs_fsync+0x315 fsync() at fsync+0x158 syscall() at syscall+0x233 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (95, FreeBSD ELF64, fsync), rip = 0x801490100, rsp = 0x7fffffffae08, rbp = 0x5f17b8 --- KDB: stack backtrace: getdirtybuf() at getdirtybuf+0x1bb flush_deplist() at flush_deplist+0x57 flush_inodedep_deps() at flush_inodedep_deps+0x89 softdep_sync_metadata() at softdep_sync_metadata+0x66 ffs_fsync() at ffs_fsync+0x315 fsync() at fsync+0x158 syscall() at syscall+0x233 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (95, FreeBSD ELF64, fsync), rip = 0x80079c100, rsp = 0x7fffffffe7b8, rbp = 0x50f070 --- KDB: stack backtrace: getdirtybuf() at getdirtybuf+0x1bb flush_deplist() at flush_deplist+0x57 flush_inodedep_deps() at flush_inodedep_deps+0x89 softdep_sync_metadata() at softdep_sync_metadata+0x66 ffs_fsync() at ffs_fsync+0x315 fsync() at fsync+0x158 syscall() at syscall+0x233 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (95, FreeBSD ELF64, fsync), rip = 0x801490100, rsp = 0x7fffffffae08, rbp = 0x5f17b8 --- Limiting closed port RST response from 472 to 200 packets/sec KDB: stack backtrace: getdirtybuf() at getdirtybuf+0x1bb flush_deplist() at flush_deplist+0x57 flush_inodedep_deps() at flush_inodedep_deps+0x89 softdep_sync_metadata() at softdep_sync_metadata+0x66 ffs_fsync() at ffs_fsync+0x315 fsync() at fsync+0x158 syscall() at syscall+0x233 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (95, FreeBSD ELF64, fsync), rip = 0x801490100, rsp = 0x7fffffffd918, rbp = 0x5eb310 --- From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 2 22:46:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5009B16A41C for ; Thu, 2 Jun 2005 22:46:21 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C60F543D48 for ; Thu, 2 Jun 2005 22:46:20 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j52Mr1wU029751; Thu, 2 Jun 2005 16:53:03 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <429F8BC4.7010900@samsco.org> Date: Thu, 02 Jun 2005 16:44:20 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm References: <20050531133608.J87922@fw.reifenberger.com> <20050531165558.L88820@fw.reifenberger.com> <200505311656.50288.jhb@FreeBSD.org> <200506011009.48460.peter@wemm.org> In-Reply-To: <200506011009.48460.peter@wemm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Michael Reifenberger , freebsd-amd64@freebsd.org Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 22:46:21 -0000 Peter Wemm wrote: > On Tuesday 31 May 2005 01:56 pm, John Baldwin wrote: > >>On Tuesday 31 May 2005 11:06 am, Michael Reifenberger wrote: >> >>>On Tue, 31 May 2005, David O'Brien wrote: >>> >>>>Ha!! We can only have 1 sector worth of code in boot0. At this >>>>point we only have a few bytes of free code space. No where near >>>>enough to do the long mode switch. >>> >>>Sorry. I didnt meant boot0 but btx. I do know that boot0 is too >>>small. But btx is already switching to protected mode so it should >>>be possible to switch to 64bit mode too. >> >>Note that the loader uses the BIOS (via virtual 8086 mode) to do all >>the disk I/O, etc. Since long mode doesn't support vm86 mode, you'd >>end up with a loader that couldn't do any I/O to load the kernel, >>etc. unless you started including device drivers for all the >>different storage and networking hardware, etc. A 64-bit loader >>really isn't feasible unless your 64-bit machine includes firmware >>that you can use from 64-bit mode like EFI on ia64 or OFW on sparc. >>You probably want to stick with a 32-bit loader on amd64 for now. > > > Yes, there are a lot of good reasons to do it the way it is done, but > this is the killer reason. We simply cannot do vm86 or bios calls from > a 64 bit loader, period. > > Other "good" reasons, besides the above: > * We don't need to maintain a seperate loader code base > * We can load test kernels with an existing loader on a FreeBSD/i386 > system (and run from a ramdisk or miniroot) > * We would need to maintain 32 bit code to do bios calls anyway, even if > we did switch between 32 bit and 64 bit mode on the fly. If we have a > complete 32 bit BTX environment, we get massive complexity for little > benefit. > I'm trying to come up with a good joke about writing OFW-style drivers in 4th, but I'm having a hard time not cracking up too hard while I type =-D Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 01:28:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9463616A41C; Fri, 3 Jun 2005 01:28:08 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38D7B43D4C; Fri, 3 Jun 2005 01:28:08 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j531S1Er016217; Thu, 2 Jun 2005 21:28:03 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <429D860A.5000608@club-internet.fr> References: <429D860A.5000608@club-internet.fr> Date: Thu, 2 Jun 2005 21:28:00 -0400 To: =?iso-8859-1?Q?Jean=2DS=E9bastien_P=E9dron?= , freebsd-alpha@freebsd.org, freebsd-amd64@freebsd.org, freebsd-ia64@freebs.org, freebsd-ppc@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.2 Cc: Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 01:28:08 -0000 At 11:55 AM +0200 6/1/05, Jean-S=E9bastien P=E9dron wrote: >Hi everyone, > >I made a patch that should fix portability issues of ReiserFS but I >don't have access to all platforms supported by FreeBSD. I tested it >on sparc64 and Olivier Houchard tried it on arm. > >I would like to know if someone could test it and report any success >or failure? I tried it on PowerPC. Following the instructions given by Jung-uk Kim , it looks like it is working okay for me: (68) # mdconfig -a -t vnode -f REISERFS -u 0 (69) # mount_reiserfs /dev/md0 /mnt (70) # ls -l /mnt total 8056 drwxr-xr-x 2 root wheel 96 Aug 6 2004 Evanescence/ drwxr-xr-x 5 1000 1000 120 Sep 1 2004 GNUstep/ -rw-r--r-- 1 1000 1000 4548644 Aug 23 2004 Shrek.mp3 lrwxrwxrwx 1 root wheel 27 Sep 1 2004=20 dir_symlink@ -> GNUstep/Library/WindowMaker lrwxrwxrwx 1 root wheel 41 Sep 1 2004=20 evanesnce.mp3@ -> Evanescence/Evanescence - My=20 Immortal.mp3 -rw-r--r-- 2 1000 1000 3176 Sep 1 2004 file_hardlink lrwxrwxrwx 1 root wheel 23 Sep 1 2004=20 file_symlink@ -> GNUstep/Defaults/WPrefs -r-xr-xr-x 1 root wheel 3680076 Oct 28 2004 ls* -rw-r--r-- 1 root wheel 70 Aug 6 2004 motd (71) # ls -lL /mnt total 16605 drwxr-xr-x 2 root wheel 96 Aug 6 2004 Evanescence/ drwxr-xr-x 5 1000 1000 120 Sep 1 2004 GNUstep/ -rw-r--r-- 1 1000 1000 4548644 Aug 23 2004 Shrek.mp3 drwxr-xr-x 9 1000 1000 1528 Sep 1 2004 dir_symlink/ -rw-r--r-- 1 root wheel 8737899 Aug 6 2004 evanesnce.mp3 -rw-r--r-- 2 1000 1000 3176 Sep 1 2004 file_hardlink -rw-r--r-- 1 1000 1000 424 Sep 1 2004 file_symlink -r-xr-xr-x 1 root wheel 3680076 Oct 28 2004 ls* -rw-r--r-- 1 root wheel 70 Aug 6 2004 motd (72) # mount /dev/ad0s5 on / (ufs, local) devfs on /dev (devfs, local) /dev/md0 on /mnt (reiserfs, local, read-only) (73) # umount /mnt (74) # mdconfig -d -u 0 Let me know if there's anything else I should test with it. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 06:43:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18F1616A41C for ; Fri, 3 Jun 2005 06:43:46 +0000 (GMT) (envelope-from vitos.laszlo@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id B231643D1D for ; Fri, 3 Jun 2005 06:43:45 +0000 (GMT) (envelope-from vitos.laszlo@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so614798wri for ; Thu, 02 Jun 2005 23:43:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:organization:to:subject:date:user-agent:mime-version:content-type:message-id; b=CdwU6TYMLB0RUeVjUYmXhbTDnJF64jBJ3dAT2J9w2H0bl5ndozC09mrStiBAjcQqbEgamRG41g1fZUpib3OcBtnwM7Z9H59pqtL1b9KVJJI9xlt/Cd+qpAiTN1t+A25P7Qy1A1prEqp1ijN/qWAoz9j7v/Urjp1XTlJ9jqE++iI= Received: by 10.54.39.69 with SMTP id m69mr1035614wrm; Thu, 02 Jun 2005 23:43:45 -0700 (PDT) Received: from laca.evol.ro ([193.230.202.166]) by mx.gmail.com with ESMTP id d6sm1012854wra.2005.06.02.23.43.44; Thu, 02 Jun 2005 23:43:45 -0700 (PDT) From: Laszlo Vitos Organization: - To: freebsd-amd64@freebsd.org Date: Fri, 3 Jun 2005 09:43:40 +0300 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_cw/nCs4APN9Fnxh" Message-Id: <200506030943.40215.vitos.laszlo@gmail.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: top showing incorrect CPU and WCPU on amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 06:43:46 -0000 --Boundary-00=_cw/nCs4APN9Fnxh Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, I observed a strange behavior of top on FreeBSD 5.4-RELEASE on AMD64. It seems like the CPU and WCPU columns in top are an average over the running time of a process. A small test program confirmed this. It sleeps for 2 seconds, then goes over a few iterations of: hogs the cpu in a loop, then sleeps again for a few seconds. The result: CPU and WCPU never reach 100%, nor 0%, they are growing/shrinking in small increments during the process' run time, depending on whether the process is sleeping or looping. Attached is the test program. Can anyone confirm whether this is the expected behavior (and if so, why?)? Thanks in advance, laca --Boundary-00=_cw/nCs4APN9Fnxh-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 07:07:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9222C16A41C for ; Fri, 3 Jun 2005 07:07:45 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D65E43D49 for ; Fri, 3 Jun 2005 07:07:45 +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 j5377c9H065965; Fri, 3 Jun 2005 00:07:38 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j5377bpV065964; Fri, 3 Jun 2005 00:07:37 -0700 (PDT) (envelope-from obrien) Date: Fri, 3 Jun 2005 00:07:37 -0700 From: "David O'Brien" To: "Toll, Eric" Message-ID: <20050603070737.GB65772@dragon.NUXI.org> References: <9BC86C67C3AF7646B9C5382020457A944E4D2A@VIP10-WIN2K> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9BC86C67C3AF7646B9C5382020457A944E4D2A@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: Damian Gerow , freebsd-amd64@freebsd.org Subject: Re: Hello 64 World - My proposed 3Ware system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@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, 03 Jun 2005 07:07:45 -0000 On Mon, May 09, 2005 at 01:17:19PM -0400, Toll, Eric wrote: > I installed my memory in 128Bit mode using banks 2 and 3, I'm not sure > what the difference is really, just that 128Bit mode sounded better > than 64 Mode. Anyone have a benchmark that I can compare to? Ubench? Boot memtest86+ (memtest.org) and you can see a nieve (but usable) BW benchmark result. You'll definately see a difference between single-channel (64-bit) vs. double-channel (128-bit) configurations. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 07:10:04 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 EE7A316A41C for ; Fri, 3 Jun 2005 07:10:04 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD21243D48 for ; Fri, 3 Jun 2005 07:10:03 +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 j537A2x0081623 for ; Fri, 3 Jun 2005 07:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j537A2BM081622; Fri, 3 Jun 2005 07:10:02 GMT (envelope-from gnats) Resent-Date: Fri, 3 Jun 2005 07:10:02 GMT Resent-Message-Id: <200506030710.j537A2BM081622@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, who cares Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D90816A41C for ; Fri, 3 Jun 2005 07:02:53 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6843943D54 for ; Fri, 3 Jun 2005 07:02:52 +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 j5372p7I032011 for ; Fri, 3 Jun 2005 07:02:51 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j5372pZK032009; Fri, 3 Jun 2005 07:02:51 GMT (envelope-from nobody) Message-Id: <200506030702.j5372pZK032009@www.freebsd.org> Date: Fri, 3 Jun 2005 07:02:51 GMT From: who cares To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/81823: ports/astro/boinc-setiathome never compiled on amd64 & -DWITHOUT_X11 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 07:10:05 -0000 >Number: 81823 >Category: amd64 >Synopsis: ports/astro/boinc-setiathome never compiled on amd64 & -DWITHOUT_X11 >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: Fri Jun 03 07:10:02 GMT 2005 >Closed-Date: >Last-Modified: >Originator: who cares >Release: 5.4-STABLE >Organization: nobody >Environment: FreeBSD athlon 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri May 27 17:07:45 CEST 2005 root@athlon:/usr/src/sys/amd64/compile/ATHLON64 amd64 >Description: Port astro/boinc-setiathome never compiled on amd64 & -DWITHOUT_X11 for last six month. Seems to still use X11 dependencies. root@amd64 > make -DWITHOUT_X11 ===> Building for boinc-setiathome-4.07.20050601 gmake all-recursive gmake[1]: Entering directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc' Making all in client gmake[2]: Entering directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc/client' if c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -O -pipe -DHAVE_CONFIG_H -DTEXT_UI -DNDEBUG -DCLIENT -include ../config.h -I../db -I/usr/local/include/BOINC -D_THREAD_SAFE -pthread -I/usr/X11R6/include -I/usr/local/include -MT seti_boinc-main.o -MD -MP -MF ".deps/seti_boinc-main.Tpo" -c -o seti_boinc-main.o `test -f 'main.cpp' || echo './'`main.cpp; \ then mv -f ".deps/seti_boinc-main.Tpo" ".deps/seti_boinc-main.Po"; else rm -f ".deps/seti_boinc-main.Tpo"; exit 1; fi In file included from :8: ./../config.h:403:23: std_fixes.h: No such file or directory main.cpp:45:25: diagnostics.h: No such file or directory main.cpp:46:18: util.h: No such file or directory In file included from ../db/sqlrow.h:26, from ../db/db_table.h:26, from seti_header.h:33, from s_util.h:105, from main.cpp:47: ./db/xml_util.h:55:27: error_numbers.h: No such file or directory In file included from ../db/sqlrow.h:26, from ../db/db_table.h:26, from seti_header.h:33, from s_util.h:105, from main.cpp:47: ./db/xml_util.h: In function `std::vector > xml_decode_field(const std::string&, const char*)': ./db/xml_util.h:846: error: `ERR_XML_PARSE' undeclared (first use this function) ./db/xml_util.h:846: error: (Each undeclared identifier is reported only once for each function it appears in.) main.cpp:48:23: boinc_api.h: No such file or directory main.cpp: In function `int main(int, char**)': main.cpp:201: error: `BOINC_DIAG_DUMPCALLSTACKENABLED' undeclared (first use this function) main.cpp:202: error: `BOINC_DIAG_HEAPCHECKENABLED' undeclared (first use this function) main.cpp:203: error: `BOINC_DIAG_TRACETOSTDERR' undeclared (first use this function) main.cpp:204: error: `BOINC_DIAG_REDIRECTSTDERR' undeclared (first use this function) main.cpp:206: error: `boinc_init_diagnostics' undeclared (first use this function) main.cpp:226: error: `boinc_init' undeclared (first use this function) gmake[2]: *** [seti_boinc-main.o] Error 1 gmake[2]: Leaving directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc/client' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/astro/boinc-setiathome/work/seti_boinc' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/astro/boinc-setiathome. >How-To-Repeat: cd /usr/ports/astro/boinc-setiathome make -DWITHOUT_X11 >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 07:36:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B02A616A41C for ; Fri, 3 Jun 2005 07:36:11 +0000 (GMT) (envelope-from peter@wemm.org) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A4A43D1F for ; Fri, 3 Jun 2005 07:36:11 +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 4B9B22A8FB for ; Fri, 3 Jun 2005 00:36:11 -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 0014DE2B3 for ; Fri, 3 Jun 2005 00:36:10 -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 j537aAmw070636; Fri, 3 Jun 2005 00:36:10 -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 j537a2tO070633; Fri, 3 Jun 2005 00:36:02 -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: Scott Long Date: Fri, 3 Jun 2005 00:36:00 -0700 User-Agent: KMail/1.8 References: <20050531133608.J87922@fw.reifenberger.com> <200506011009.48460.peter@wemm.org> <429F8BC4.7010900@samsco.org> In-Reply-To: <429F8BC4.7010900@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506030036.01929.peter@wemm.org> Cc: Michael Reifenberger , freebsd-amd64@freebsd.org Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 07:36:11 -0000 On Thursday 02 June 2005 03:44 pm, Scott Long wrote: > Peter Wemm wrote: > > On Tuesday 31 May 2005 01:56 pm, John Baldwin wrote: > >>On Tuesday 31 May 2005 11:06 am, Michael Reifenberger wrote: > >>>On Tue, 31 May 2005, David O'Brien wrote: > >>>>Ha!! We can only have 1 sector worth of code in boot0. At this > >>>>point we only have a few bytes of free code space. No where near > >>>>enough to do the long mode switch. > >>> > >>>Sorry. I didnt meant boot0 but btx. I do know that boot0 is too > >>>small. But btx is already switching to protected mode so it should > >>>be possible to switch to 64bit mode too. > >> > >>Note that the loader uses the BIOS (via virtual 8086 mode) to do > >> all the disk I/O, etc. Since long mode doesn't support vm86 mode, > >> you'd end up with a loader that couldn't do any I/O to load the > >> kernel, etc. unless you started including device drivers for all > >> the different storage and networking hardware, etc. A 64-bit > >> loader really isn't feasible unless your 64-bit machine includes > >> firmware that you can use from 64-bit mode like EFI on ia64 or OFW > >> on sparc. You probably want to stick with a 32-bit loader on amd64 > >> for now. > > > > Yes, there are a lot of good reasons to do it the way it is done, > > but this is the killer reason. We simply cannot do vm86 or bios > > calls from a 64 bit loader, period. > > > > Other "good" reasons, besides the above: > > * We don't need to maintain a seperate loader code base > > * We can load test kernels with an existing loader on a > > FreeBSD/i386 system (and run from a ramdisk or miniroot) > > * We would need to maintain 32 bit code to do bios calls anyway, > > even if we did switch between 32 bit and 64 bit mode on the fly. > > If we have a complete 32 bit BTX environment, we get massive > > complexity for little benefit. > > I'm trying to come up with a good joke about writing OFW-style > drivers in 4th, but I'm having a hard time not cracking up too hard > while I type =-D Actually, we could embed a 64 bit linux kernel in there and use their drivers in order to chain load the freebsd kernel.. That would solve the bios problem. :-) -- 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 Fri Jun 3 09:32:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86B5C16A41C for ; Fri, 3 Jun 2005 09:32:01 +0000 (GMT) (envelope-from mr.skoe@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3477343D53 for ; Fri, 3 Jun 2005 09:32:01 +0000 (GMT) (envelope-from mr.skoe@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so888617nzp for ; Fri, 03 Jun 2005 02:32:00 -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:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dAh9t85EZEDx83qBKpquW0PqiEDV0TF36lLDQ6hBPJWl5iWS0a3KGgnsTugDtwYOcFmD8eyMY+EF1PRaFGgH4RuhXZrT1ORWBIzHRJQek8l5fzH+vfmOqZYT3QweeP3bH0rBsnJKLt0qvwt0AX13paq2Bj7Ryo7OyDlB/9EFZLE= Received: by 10.36.222.74 with SMTP id u74mr721196nzg; Fri, 03 Jun 2005 02:32:00 -0700 (PDT) Received: by 10.36.5.2 with HTTP; Fri, 3 Jun 2005 02:32:00 -0700 (PDT) Message-ID: Date: Fri, 3 Jun 2005 19:32:00 +1000 From: Mathew Schofield To: freebsd-amd64@freebsd.org In-Reply-To: <200506030036.01929.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050531133608.J87922@fw.reifenberger.com> <200506011009.48460.peter@wemm.org> <429F8BC4.7010900@samsco.org> <200506030036.01929.peter@wemm.org> Subject: Re: 64bit loader X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mathew Schofield List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 09:32:01 -0000 On 6/3/05, Peter Wemm wrote: > On Thursday 02 June 2005 03:44 pm, Scott Long wrote: > > Peter Wemm wrote: > > > On Tuesday 31 May 2005 01:56 pm, John Baldwin wrote: > > >>On Tuesday 31 May 2005 11:06 am, Michael Reifenberger wrote: > > >>>On Tue, 31 May 2005, David O'Brien wrote: > > >>>>Ha!! We can only have 1 sector worth of code in boot0. At this > > >>>>point we only have a few bytes of free code space. No where near > > >>>>enough to do the long mode switch. > > >>> > > >>>Sorry. I didnt meant boot0 but btx. I do know that boot0 is too > > >>>small. But btx is already switching to protected mode so it should > > >>>be possible to switch to 64bit mode too. > > >> > > >>Note that the loader uses the BIOS (via virtual 8086 mode) to do > > >> all the disk I/O, etc. Since long mode doesn't support vm86 mode, > > >> you'd end up with a loader that couldn't do any I/O to load the > > >> kernel, etc. unless you started including device drivers for all > > >> the different storage and networking hardware, etc. A 64-bit > > >> loader really isn't feasible unless your 64-bit machine includes > > >> firmware that you can use from 64-bit mode like EFI on ia64 or OFW > > >> on sparc. You probably want to stick with a 32-bit loader on amd64 > > >> for now. > > > > > > Yes, there are a lot of good reasons to do it the way it is done, > > > but this is the killer reason. We simply cannot do vm86 or bios > > > calls from a 64 bit loader, period. > > > > > > Other "good" reasons, besides the above: > > > * We don't need to maintain a seperate loader code base > > > * We can load test kernels with an existing loader on a > > > FreeBSD/i386 system (and run from a ramdisk or miniroot) > > > * We would need to maintain 32 bit code to do bios calls anyway, > > > even if we did switch between 32 bit and 64 bit mode on the fly. > > > If we have a complete 32 bit BTX environment, we get massive > > > complexity for little benefit. > > > > I'm trying to come up with a good joke about writing OFW-style > > drivers in 4th, but I'm having a hard time not cracking up too hard > > while I type =3D-D >=20 > Actually, we could embed a 64 bit linux kernel in there and use their > drivers in order to chain load the freebsd kernel.. That would solve > the bios problem. :-) That is the joke...Right? o_O --=20 This is a private letter and only the intended people may read this message. You may not store, quote or publish this document for any purposes. The data/information held within this message are for private use, and no one may disclose it. There are no guarentees that the information disclosed is accurate, or that the links/attached files will not be contaminated with Viruses. You use all links, and all attachments, at your own free will and thus risk. You have been warned. From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 11:53:33 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A14AD16A41C; Fri, 3 Jun 2005 11:53:33 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from smtp.cegetel.net (mf00.sitadelle.com [212.94.174.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2340443D53; Fri, 3 Jun 2005 11:53:33 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [172.16.142.1] (213-223-184-193.dti.cegetel.net [213.223.184.193]) by smtp.cegetel.net (Postfix) with ESMTP id 2D7311A4366; Fri, 3 Jun 2005 13:53:32 +0200 (CEST) Message-ID: <42A044BF.5060300@club-internet.fr> Date: Fri, 03 Jun 2005 13:53:35 +0200 From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20050208 X-Accept-Language: fr-fr, fr, en-us, en, ja MIME-Version: 1.0 To: Garance A Drosihn References: <429D860A.5000608@club-internet.fr> In-Reply-To: X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC93B43DEC3CE0C76439FB576" Content-Transfer-Encoding: 8bit Cc: freebsd-ia64@freebs.org, freebsd-amd64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 11:53:33 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC93B43DEC3CE0C76439FB576 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Garance A Drosihn wrote: > At 11:55 AM +0200 6/1/05, Jean-Sébastien Pédron wrote: > >> Hi everyone, >> >> I made a patch that should fix portability issues of ReiserFS but I >> don't have access to all platforms supported by FreeBSD. I tested it >> on sparc64 and Olivier Houchard tried it on arm. >> >> I would like to know if someone could test it and report any success >> or failure? > > > I tried it on PowerPC. Following the instructions given by > Jung-uk Kim , it looks like it is working okay > for me: Did you try withtout Jung-uk Kim's workaround? > Let me know if there's anything else I should test with it. Thank you for your tests. You may try this with `motd' (small file which fits inside a block, with its metadata): . cp motd /tmp (mmap(2)) . compare md5 of motd and /tmp/motd (read(2)) You may do it again with `ls' which spans multiple bocks (these two files are stored differently in ReiserFS). -- Jean-Sébastien Pédron http://www.dumbbell.fr/ PGP Key: http://www.dumbbell.fr/pgp/pubkey.asc --------------enigC93B43DEC3CE0C76439FB576 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCoETDa+xGJsFYOlMRAqw/AKC5HzkArCJaP2qrXbs/aJ2mKSPKWQCgsWn3 ZO0dwqqtbmmA8B/HjPIpVZk= =EGUU -----END PGP SIGNATURE----- --------------enigC93B43DEC3CE0C76439FB576-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 18:40:06 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 7A3D316A429 for ; Fri, 3 Jun 2005 18:40:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52E6443D49 for ; Fri, 3 Jun 2005 18:40:06 +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 j53Ie6rt077176 for ; Fri, 3 Jun 2005 18:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j53Ie5Gf077175; Fri, 3 Jun 2005 18:40:05 GMT (envelope-from gnats) Date: Fri, 3 Jun 2005 18:40:05 GMT Message-Id: <200506031840.j53Ie5Gf077175@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Roland Smith Cc: Subject: Re: amd64/81823: ports/astro/boinc-setiathome never compiled on amd64 & -DWITHOUT_X11 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roland Smith List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 18:40:06 -0000 The following reply was made to PR amd64/81823; it has been noted by GNATS. From: Roland Smith To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: amd64/81823: ports/astro/boinc-setiathome never compiled on amd64 & -DWITHOUT_X11 Date: Fri, 3 Jun 2005 20:33:54 +0200 --NKoe5XOeduwbEQHU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It works fine here:=20 FreeBSD slackbox.xs4all.nl 5.4-STABLE FreeBSD 5.4-STABLE #6: Tue May 17 19:19:12 CEST 2005 root@slackbox.xs4all.nl:/usr/obj/usr/src/sys/RFS amd64 Note that the build fails in boinc-client, not boinc-setiathome. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --NKoe5XOeduwbEQHU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCoKKSEnfvsMMhpyURAidGAKCRdM/cqwfYB3jLcHRHqQGtcvqihQCeNWD/ sgBNTCUYGZq6Rk6b83JpqKw= =z200 -----END PGP SIGNATURE----- --NKoe5XOeduwbEQHU-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 18:55:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 481D216A41C; Fri, 3 Jun 2005 18:55:43 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E810A43D1D; Fri, 3 Jun 2005 18:55:42 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j53Itb5s029260; Fri, 3 Jun 2005 14:55:38 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <42A044BF.5060300@club-internet.fr> References: <429D860A.5000608@club-internet.fr> <42A044BF.5060300@club-internet.fr> Date: Fri, 3 Jun 2005 14:55:36 -0400 To: =?iso-8859-1?Q?Jean=2DS=E9bastien_P=E9dron?= From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.2 Cc: freebsd-ia64@freebs.org, freebsd-amd64@freebsd.org, freebsd-alpha@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: [CALL FOR TESTERS] ReiserFS on non-i386 hardware patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 18:55:43 -0000 At 1:53 PM +0200 6/3/05, Jean-S=E9bastien P=E9dron wrote: >Garance A Drosihn wrote: >>At 11:55 AM +0200 6/1/05, Jean-S=E9bastien P=E9dron wrote: >> >>>Hi everyone, >>> >>>I made a patch that should fix portability issues of ReiserFS but I >>>don't have access to all platforms supported by FreeBSD. I tested it >>>on sparc64 and Olivier Houchard tried it on arm. >>> >>>I would like to know if someone could test it and report any success >>>or failure? >> >> >>I tried it on PowerPC. Following the instructions given by >>Jung-uk Kim , it looks like it is working okay >>for me: > >Did you try withtout Jung-uk Kim's workaround? The only thing I applied was your original patch, and then added "options REISERFS" to my custom kernel configuration. Note that PPC is still a 32-bit architecture on FreeBSD, so I wouldn't see anything which was a 64-bit issue. >>Let me know if there's anything else I should test with it. > >... try this with `motd' (small file which fits inside a block, >with its metadata): > . cp motd /tmp (mmap(2)) > . compare md5 of motd and /tmp/motd (read(2)) >You may do it again with `ls' which spans multiple bocks (these >two files are stored differently in ReiserFS). (90) cd /mnt (91) cp motd /tmp (92) cp evanesnce.mp3 /tmp (93) cp ls /tmp (94) md5 -r evanesnce.mp3 ls motd f431f46c2c3bae9b94172691a667eada evanesnce.mp3 c9ea68636b3bea3b5cac8205fd4417ef ls 2ffa53790de34b7561f5661fb7f22a1d motd (95) cd /tmp (96) md5 -r evanesnce.mp3 ls motd f431f46c2c3bae9b94172691a667eada evanesnce.mp3 c9ea68636b3bea3b5cac8205fd4417ef ls 2ffa53790de34b7561f5661fb7f22a1d motd -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 21:25:33 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C904416A41C for ; Fri, 3 Jun 2005 21:25:33 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE6443D1F for ; Fri, 3 Jun 2005 21:25:32 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j53LPVMh050166 for ; Sat, 4 Jun 2005 00:25:31 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 91128-15 for ; Sat, 4 Jun 2005 00:25:30 +0300 (EEST) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id j53LPT09050163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 4 Jun 2005 00:25:30 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.3/8.13.3) id j53LPt3O094241 for amd64@freebsd.org; Sat, 4 Jun 2005 00:25:55 +0300 (EEST) (envelope-from ru) Date: Sat, 4 Jun 2005 00:25:55 +0300 From: Ruslan Ermilov To: amd64@freebsd.org Message-ID: <20050603212555.GB36509@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7ZAtKRhVyVSsbBD2" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: Subject: device speaker X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 21:25:33 -0000 --7ZAtKRhVyVSsbBD2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Any reason not to enable "device speaker" on amd64? I just tried compiling and kldloading the module, and spkrtest(8) was quite happy and loud about it. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --7ZAtKRhVyVSsbBD2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCoMrjqRfpzJluFF4RAr3zAJ9ZUMEzUaVooaBosVr9am+2DWFVPQCgkO8g jtL8IGwt+vtXvWULKBrDdpI= =UOjW -----END PGP SIGNATURE----- --7ZAtKRhVyVSsbBD2-- From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 3 21:28:36 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05B5A16A41C for ; Fri, 3 Jun 2005 21:28:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id B009043D49 for ; Fri, 3 Jun 2005 21:28:35 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 678D151294; Fri, 3 Jun 2005 17:28:33 -0400 (EDT) Date: Fri, 3 Jun 2005 17:28:33 -0400 From: Kris Kennaway To: Eirik ?verby Message-ID: <20050603212833.GA69841@xor.obsecurity.org> References: <0845B29D-400C-4408-9473-960273D88078@anduin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <0845B29D-400C-4408-9473-960273D88078@anduin.net> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org Subject: Re: Strange console output - scary X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2005 21:28:36 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 02, 2005 at 10:55:04PM +0200, Eirik ?verby wrote: > Hi, >=20 > When putting some quite significant stress on the system (namely by =20 > forwarding about a thousand mails at once through exim, triggering =20 > spamassassin and clamav scans and stuff), also including swapping and =20 > loads of processes fighting over the CPUs, I start getting the =20 > following output on my serial console. > The box seems unresponsive for a while, but does come back once the =20 > load/swapping lessens. >=20 > This is a dual opteron on a Tyan S2882 mainboard, 1GB memory, =20 > ultra320 scsi disk on the onboard adaptec controller plus a pair of =20 > SATA drives in gmirror (raid-1) on the onboard SiI controller. Swap =20 > is on the SCSI drive. >=20 > Could this be related to the panic I saw in my earlier messages (5.4-=20 > panic)? See recent discussion of this condition on freebsd-stable. Kris --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCoMuBWry0BWjoQKURAs5uAJwL1EYlb+eW0g/mhjMzNfT7AEVi1QCgjQpP Z8OdAgxggBFpQGAxfj/SoPE= =f+zY -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 4 04:50:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F075E16A41C for ; Sat, 4 Jun 2005 04:50:31 +0000 (GMT) (envelope-from mixicek@seznam.cz) Received: from email.seznam.cz (mx1.seznam.cz [212.80.76.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 2811243D1D for ; Sat, 4 Jun 2005 04:50:28 +0000 (GMT) (envelope-from mixicek@seznam.cz) Received: (qmail 11769 invoked by uid 0); 4 Jun 2005 04:50:26 -0000 Date: Sat, 04 Jun 2005 06:50:24 +0200 (CEST) Cc: To: freebsd-amd64@freebsd.org From: =?us-ascii?Q?Ladislav=20x?= Received: from [68.100.137.203] by apollo.go.seznam.cz with HTTP for mixicek@seznam.cz; Sat, 4 Jun 2005 6:46:42 +0200 (CEST) Mime-Version: 1.0 Message-Id: <121.311-9209-1359530429-1117860624@seznam.cz> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Abuse: helpdesk@seznam.cz X-Seznam-User: mixicek@seznam.cz Subject: Problem with compilation p5-vpopmail on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?us-ascii?Q?Ladislav=20x?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2005 04:50:32 -0000 Hello. I have problem durning compilation p5-vpopmail. Can you help me, please? Thank you. Sincerely Ladislav Jerabek ----------------------------------------------------------------------------- port_install: vpopmail installed as (vpopmail-5.4.10_1). ports_check_age: Ports file is current (enough). running: make install clean===> Building for p5-vpopmail-0.08 rm -f blib/arch/auto/vpopmail/vpopmail.so LD_RUN_PATH="/usr/local/lib/mysql:/usr/lib" cc -shared -L/usr/local/lib vpopmail.o -o blib/arch/auto/vpopmail/vpopmail.so -L/usr/local/vpopmail/lib -lvpopmail -L/usr/local/lib/mysql -lmysqlclient -lz -lm -lcrypt /usr/bin/ld: /usr/local/vpopmail/lib/libvpopmail.a(vpopmail.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/local/vpopmail/lib/libvpopmail.a: could not read symbols: Bad value *** Error code 1 Stop in /usr/ports/mail/p5-vpopmail/work/vpopmail-0.08. *** Error code 1 Stop in /usr/ports/mail/p5-vpopmail. syscmd: make install clean syscmd: result: 256 port_install: p5-vpopmail FAILED FATAL FAILURE: Install of p5-vpopmail failed. Please fix and try again. at /usr/local/lib/perl5/site_perl/5.8.6/Mail/Toaster/Setup.pm line 5249 ------------------------------------------------------------------------------- ____________________________________________________________ http://www.listicka.cz From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 4 06:34:49 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C39716A41C for ; Sat, 4 Jun 2005 06:34:49 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C2D743D1F for ; Sat, 4 Jun 2005 06:34:48 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-1) with ESMTP id j546YlT4025786; Sat, 4 Jun 2005 16:34:47 +1000 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j546YjAT030687; Sat, 4 Jun 2005 16:34:46 +1000 Date: Sat, 4 Jun 2005 16:34:47 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Laszlo Vitos In-Reply-To: <200506030943.40215.vitos.laszlo@gmail.com> Message-ID: <20050604162348.V5146@delplex.bde.org> References: <200506030943.40215.vitos.laszlo@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: top showing incorrect CPU and WCPU on amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2005 06:34:49 -0000 On Fri, 3 Jun 2005, Laszlo Vitos wrote: > I observed a strange behavior of top on FreeBSD 5.4-RELEASE on AMD64. It seems > like the CPU and WCPU columns in top are an average over the running time of > a process. A small test program confirmed this. It sleeps for 2 seconds, then > goes over a few iterations of: hogs the cpu in a loop, then sleeps again for > a few seconds. > The result: CPU and WCPU never reach 100%, nor 0%, they are growing/shrinking > in small increments during the process' run time, depending on whether the > process is sleeping or looping. > Attached is the test program. Can anyone confirm whether this is the expected > behavior (and if so, why?)? No test program is attached :-). I think this is the expected beviour. CPU is a long-term average. Thus if a process runs for half the time and sleeps for half the time, its CPU will be about 50%. It won't be exactly 50% since more weight is given to recent history. WCPU is mostly bogus. It is an attempt to undo the weighting but not enough history is kept to do this correctly and the history which is used is close to being garbage. Bruce From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 4 20:36:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B335B16A41C for ; Sat, 4 Jun 2005 20:36:38 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5085043D49 for ; Sat, 4 Jun 2005 20:36:38 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j54Kab18019093 for ; Sat, 4 Jun 2005 16:36:37 -0400 Date: Sat, 4 Jun 2005 16:36:37 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: FreeBSD amd64 List Message-ID: <20050604162834.Q67665@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Gigabyte GA-K8NS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2005 20:36:38 -0000 Anyone got Fbsd-AMD64 working with Gigabyte GA-K8NS motherboard? The list of working motherboards lists the GA-K8NS PRO, but looking at their specs they have different LAN chipset. My local computer shop sent me the GA-K8NS (without the pro) by mistake and I am trying to decide if to send it back. I don't care much about the network card not getting recognized, but it seems the RAID is not recognized. I even tried to install the i386 FreeBSD and it didn't recognize the RAID either. :-( From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 4 22:19:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16A5C16A41C for ; Sat, 4 Jun 2005 22:19:25 +0000 (GMT) (envelope-from lists@natserv.com) Received: from mail1.acecape.com (mail1.acecape.com [66.114.74.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEDFD43D4C for ; Sat, 4 Jun 2005 22:19:24 +0000 (GMT) (envelope-from lists@natserv.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mail1.acecape.com (8.12.11/8.12.11) with ESMTP id j54MJNl1011010 for ; Sat, 4 Jun 2005 18:19:23 -0400 Date: Sat, 4 Jun 2005 18:19:23 -0400 (EDT) From: Francisco Reyes X-X-Sender: fran@zoraida.natserv.net To: FreeBSD amd64 List Message-ID: <20050604163642.O67665@zoraida.natserv.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: AMD64 Disc 1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2005 22:19:25 -0000 Although my first attempt at installing AMD64 failed because the vendor sent me the wrong motherboard I was wondering.. does the AMD64 install looks any different than the i386? I made 2 CDs one AMD64 and one i386. They both looked pretty identical. It got me wondering if I had mistakenly copied the i386 twice by mistake.