From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 15 00:04:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F83916A4CE for ; Sun, 15 Feb 2004 00:04:19 -0800 (PST) Received: from mail.massarenti.com (host238-109.pool8017.interbusiness.it [80.17.109.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7A8A43D1F for ; Sun, 15 Feb 2004 00:04:17 -0800 (PST) (envelope-from freebsd64@massarenti.com) Received: by mail.massarenti.com (Postfix, from userid 527) id 669E76F639; Sun, 15 Feb 2004 08:49:59 +0100 (CET) Received: from ts (ts.massarenti.com [192.168.1.201]) by mail.massarenti.com (Postfix) with SMTP id 03EE56F5AC; Sun, 15 Feb 2004 08:49:58 +0100 (CET) Message-ID: <002201c3f39a$6d4cf8e0$c901a8c0@ts> From: "Luca Massarenti" To: References: Date: Sun, 15 Feb 2004 09:05:07 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 cc: freebsd-amd64@freebsd.org Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2004 08:04:19 -0000 As you can see I'me not a java expert!!! Which platform do you suggest to use ? and is amd processors a good choice for this kind of application? and if you have to implement this kind of application what HW and OS would you use? Consider the fact you can choose any kind of HW and SW (Unix-like of course !!!!) Luca ----- Original Message ----- From: "Adriaan de Groot" To: "Luca Massarenti" Cc: Sent: Saturday, February 14, 2004 11:26 PM Subject: Re: which motherboard and which chipset? > Ciao, Luca, > > On Sat, 14 Feb 2004, Luca Massarenti wrote: > > I want to start installing freebsd on amd based server and in particular > > using opteron cpu. > > > > I want to install an application server which run a java application for > > about 80 clients > > > > Which chipset is best and is best tested? > > Before you ask that question you should probably ask: does Java run at all > under FreeBSD on amd64? Also remember that there is a native FreeBSD JSK > version 1.3 - no 1.4 or 1.5. Running Linux binaries is, as yet, not > possible. So first check if the platform can support what you need. > > > Which mainboard is considered the best? > > What about dual processors? > > Take a look at the archives of this list (via > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 ), there's lot of > hardware mentioned. I think a lot depends on how much memory you need to > support your users: Athlon64 boards (single CPU) tend to top out at 4G > theoretical and 3G practical (like my Asus k8v, with 3 slots so I could > stick 3G of DDR266 in it) ; Opteron boards for single CPU with 4 slots top > out at 8G theoretical (4x2G Registered), but I hear tales of an sk8n > supporting only 3.5G. Dual boards run up to 8 slots, for 16G of memory. > > > I have the possibility to choose between via and nvidia and between asus and > > MSI. > > That sounds very much like you're limiting yourself to single CPU systems > (although MSI makes the k8t master2, with 2 CPUs and 4 memory slots, and > the k8dm, which looks like the kind of 4+2 dimm solution that is said to > be dodgy). > > You state you want to use an opteron processor, that's socket 940, and > limiting your choices to those two manufacturers and chipsets. Hm. That > throws out the MSI k8d, since that's an amd chipset. That leaves the k8t > master (not the neo, since it's socket 754) and asus sk8n (nvidia) or > sk8v (via). > > Maybe you already knew all that. I don't recall any of those systems being > mentioned here on the list - but again, check the archives. I'll tell you > that my own asus k8v w/ 1G and using SATA drives works just fine - for one > user, at least. > > _______________________________________________ > 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 Sun Feb 15 10:59:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DBEF16A4CE for ; Sun, 15 Feb 2004 10:59:24 -0800 (PST) Received: from mail.drunkencomputing.de (ratz.drunkencomputing.de [195.244.235.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E9D843D1F for ; Sun, 15 Feb 2004 10:59:24 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: from localhost (localhost [127.0.0.1]) by mail.drunkencomputing.de (Postfix) with ESMTP id 59A7D8B4F5 for ; Sun, 15 Feb 2004 19:58:13 +0100 (CET) Received: from mail.drunkencomputing.de ([127.0.0.1])port 10024) with ESMTP id 45992-03 for ; Sun, 15 Feb 2004 19:58:12 +0100 (CET) Received: from [10.0.1.2] (c-24-30-48-121.mw.client2.attbi.com [24.30.48.121]) by mail.drunkencomputing.de (Postfix) with ESMTP id 93B4C8B4F0 for ; Sun, 15 Feb 2004 19:58:05 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@freebsd.org From: Hendrik Scholz Date: Sun, 15 Feb 2004 13:58:52 -0500 X-Mailer: Apple Mail (2.612) X-Virus-Scanned: by amavisd-new at drunkencomputing.de Subject: gdb howto? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2004 18:59:24 -0000 Hi! I've tried to compile multiple different versions of gdb (cvs snapshot, checked out from cvs, ...) but none of the compiled since most of them already complaint about amd64-unknown-freebsd5.2.1. Could anyone please say which version/tarball(URL?) definitly works. Thanks a lot, Hendrik P.S. I've added my three different boards to the SMP board list. -- Hendrik Scholz - hscholz@raisdorf.net - http://www.raisdorf.net/ cell phone: 404-606-5324 (US) 0160-1570-272 (DE) From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 15 12:54:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FA0C16A4CE for ; Sun, 15 Feb 2004 12:54:44 -0800 (PST) Received: from walton.kettenis.dyndns.org (e115144.upc-e.chello.nl [213.93.115.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id B070243D1D for ; Sun, 15 Feb 2004 12:54:43 -0800 (PST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2])i1FKsfeA000268; Sun, 15 Feb 2004 21:54:41 +0100 (CET) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) i1FKsfs4005639; Sun, 15 Feb 2004 21:54:41 +0100 (CET) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost)i1FKsZX3005636; Sun, 15 Feb 2004 21:54:35 +0100 (CET) Date: Sun, 15 Feb 2004 21:54:35 +0100 (CET) Message-Id: <200402152054.i1FKsZX3005636@elgar.kettenis.dyndns.org> From: Mark Kettenis To: hscholz@raisdorf.net In-reply-to: (message from Hendrik Scholz on Sun, 15 Feb 2004 13:58:52 -0500) References: cc: freebsd-amd64@freebsd.org Subject: Re: gdb howto? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2004 20:54:44 -0000 From: Hendrik Scholz Date: Sun, 15 Feb 2004 13:58:52 -0500 Hi! I've tried to compile multiple different versions of gdb (cvs snapshot, checked out from cvs, ...) but none of the compiled since most of them already complaint about amd64-unknown-freebsd5.2.1. Please try to configure with --target=x86_64-unknown-freebsd5.2.1 This should work with GDB 6.0 and beyond, including snapshots and a freshly checked out CVS tree. Mark From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 00:04:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15CCC16A4CE for ; Mon, 16 Feb 2004 00:04:13 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00D0143D1F for ; Mon, 16 Feb 2004 00:04:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.10) with ESMTP id i1G84COJ057573; Mon, 16 Feb 2004 00:04:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i1G848OR057568; Mon, 16 Feb 2004 00:04:08 -0800 (PST) (envelope-from obrien) Date: Mon, 16 Feb 2004 00:04:08 -0800 From: "David O'Brien" To: Luca Massarenti Message-ID: <20040216080408.GE54371@dragon.nuxi.com> References: <002c01c3f312$947a26a0$c901a8c0@ts> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002c01c3f312$947a26a0$c901a8c0@ts> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-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 cc: freebsd-amd64@freebsd.org Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 08:04:13 -0000 On Sat, Feb 14, 2004 at 04:52:42PM +0100, Luca Massarenti wrote: > Which chipset is best and is best tested? ... > Generally I like asus MB and nvidia chipset very much but I have never > installed unix-like operating system on amd processors. nVidia nForce3 [for AMD64] chipsets are very problematic for Unix(BSD)/Linux. I would avoid them if you want to run a non-MS-Windows operating system. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 00:04:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16E0B16A4CF for ; Mon, 16 Feb 2004 00:04:19 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 001C743D1F for ; Mon, 16 Feb 2004 00:04:18 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.10) with ESMTP id i1G82iOJ057515; Mon, 16 Feb 2004 00:02:44 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i1G82e1c057513; Mon, 16 Feb 2004 00:02:40 -0800 (PST) (envelope-from obrien) Date: Mon, 16 Feb 2004 00:02:40 -0800 From: "David O'Brien" To: adridg@cs.kun.nl Message-ID: <20040216080240.GD54371@dragon.nuxi.com> References: <002c01c3f312$947a26a0$c901a8c0@ts> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-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 cc: Luca Massarenti cc: freebsd-amd64@freebsd.org Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 08:04:19 -0000 On Sat, Feb 14, 2004 at 11:26:06PM +0100, Adriaan de Groot wrote: > Take a look at the archives of this list (via > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 ), there's lot of > hardware mentioned. I think a lot depends on how much memory you need to > support your users: Athlon64 boards (single CPU) tend to top out at 4G > theoretical and 3G practical (like my Asus k8v, with 3 slots so I could > stick 3G of DDR266 in it) ; Opteron boards for single CPU with 4 slots top > out at 8G theoretical (4x2G Registered), but I hear tales of an sk8n > supporting only 3.5G. Dual boards run up to 8 slots, for 16G of memory. Not just SK8N's. Just about every AMD64 mobo will "loose" physical memory from 3.5-4GB. So one would get 17.5GB in your example of 8x2GB DIMM's. The reasons have been explained in this list before. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 00:07:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9693316A4CE for ; Mon, 16 Feb 2004 00:07:38 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 822B843D1D for ; Mon, 16 Feb 2004 00:07:38 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.10) with ESMTP id i1G864OJ057589; Mon, 16 Feb 2004 00:06:04 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i1G863Z9057588; Mon, 16 Feb 2004 00:06:03 -0800 (PST) (envelope-from obrien) Date: Mon, 16 Feb 2004 00:06:02 -0800 From: "David O'Brien" To: Luca Massarenti Message-ID: <20040216080602.GF54371@dragon.nuxi.com> References: <002201c3f39a$6d4cf8e0$c901a8c0@ts> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002201c3f39a$6d4cf8e0$c901a8c0@ts> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-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 cc: adridg@cs.kun.nl cc: freebsd-amd64@freebsd.org Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 16 Feb 2004 08:07:38 -0000 On Sun, Feb 15, 2004 at 09:05:07AM +0100, Luca Massarenti wrote: > As you can see I'me not a java expert!!! > Which platform do you suggest to use ? > and is amd processors a good choice for this kind of application? Yes AMD64 CPU+mobo is a excelent choice for this kind of application. The question is should you run a 32-bit or 64-bit FreeBSD right now. Since you want to run Java bits, that pretty much means 32-bit FreeBSD right now. Don't forget that AMD64 is the fastest 32-bit x86 processor also. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 02:20:53 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E64D16A4CE; Mon, 16 Feb 2004 02:20:53 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84C0E43D1D; Mon, 16 Feb 2004 02:20:53 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A49367303A; Mon, 16 Feb 2004 05:20:52 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040216102052.A49367303A@freebsd-current.sentex.ca> Date: Mon, 16 Feb 2004 05:20:52 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 10:20:53 -0000 TB --- 2004-02-16 09:34:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-16 09:34:43 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-16 09:34:43 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-16 09:39:07 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp as --defsym FLAGS=0x80 --defsym SIOPRT=0x3f8 --defsym SIOFMT=0x3 --defsym SIOSPD=9600 --32 -o boot2.o boot2.s cc -Os -fno-guess-branch-probability -fomit-frame-pointer -mno-align-long-strings -mrtd -DUFS1_AND_UFS2 -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2/../../common -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -ffreestanding -mpreferred-stack-boundary=2 -m32 -c /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2/sio.S /var/tmp//ccOozpmP.s: Assembler messages: /var/tmp//ccOozpmP.s:84: Error: undefined symbol `SIOSPD' in operation setting `SIO_DIV' /var/tmp//ccOozpmP.s:35: Error: undefined symbol `SIO_FMT' in operation /var/tmp//ccOozpmP.s:39: Error: value of 000000000001c200 too large for field of 2 bytes at 000000000000000d *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-16 10:20:52 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-16 10:20:52 - TB --- ERROR: failed to build world TB --- 2004-02-16 10:20:52 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 06:00:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8D7216A4CE for ; Mon, 16 Feb 2004 06:00:40 -0800 (PST) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77DAC43D1D for ; Mon, 16 Feb 2004 06:00:40 -0800 (PST) (envelope-from ml@fruitbat.demon.co.uk) Received: from pr-webmail-2.demon.net ([194.159.244.50]) by anchor-post-31.mail.demon.net with smtp (Exim 3.35 #1) id 1AsjId-0007tY-0V; Mon, 16 Feb 2004 14:00:39 +0000 Received: from fruitbat.demon.co.uk ([195.74.121.82]) by web.mail.demon.net with http; Mon, 16 Feb 2004 14:00:39 +0000 From: ml@fruitbat.demon.co.uk To: "Brooks Davis" In-Reply-To: <20040126175234.GA28717@Odin.AC.HMC.Edu> Date: Mon, 16 Feb 2004 14:00:39 +0000 User-Agent: Demon-WebMail/2.0 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: cc: freebsd-amd64@freebsd.org Subject: Re: malloc() over 4Gb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 14:00:41 -0000 brooks@one-eyed-alien.net wrote: > On Sun, Jan 25, 2004 at 01:37:47PM +0000, ml@fruitbat.demon.co.uk wrote: > > Hi. Could someone clarify whether or not it's possible to malloc() > > and mmap() chunks of memory > 4Gb in size using FreeBSD/AMD64 and > > that FreeBSD/AMD64 isn't susceptible to the 4Gb process boundary that > > 32-bit OSs are restricted by? > > It works fine (just remember to set your malloc options to aj before > mallocing that much memory, it takes a loooong time if you done :-): > [9:52am] brooks@brimstone (~): uname -a > FreeBSD brimstone 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Jan 6 13:18:20 P= > ST 2004 brooks@brimstone:/usr/obj/usr/p4/xname/sys/GENERIC amd64 > [9:52am] brooks@brimstone (~): ./a > a.out* aeroauth*=20 > [9:52am] brooks@brimstone (~): cat foo.c > #include > #include > #include > #define GB (1024*1024*1024) > int > main (int argc, char **argv) > { > void *foo; > printf("Trying to malloc %zd bytesn", (size_t)7*GB); foo =3D malloc((size_t)7*GB); > foo =3D malloc((size_t)7*GB); if (foo !=3D NULL) > if (foo !=3D NULL) > printf("Successn"); else > else > printf("failuren");} > } > [9:52am] brooks@brimstone (~): gcc -o foo foo.c > [9:52am] brooks@brimstone (~): ./foo=20 > Trying to malloc 7516192768 bytes > Success > [9:52am] brooks@brimstone (~):=20 Hi. Thanks for that information! I went out and bought the box and it does indeed seem to malloc() over 4Gb. However, if you change the allocation from 7*GB to 8*GB in your sample program, it still keels over inside malloc()! Do you know if there's any sort of 8Gb clamp in this OS?! Cheers! > -- Brooks A. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 11:01:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1B6516A4CE for ; Mon, 16 Feb 2004 11:01:40 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE59243D1D for ; Mon, 16 Feb 2004 11:01:40 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id i1GJ1ebv034158 for ; Mon, 16 Feb 2004 11:01:40 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1GJ1e6Y034152 for freebsd-amd64@freebsd.org; Mon, 16 Feb 2004 11:01:40 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 16 Feb 2004 11:01:40 -0800 (PST) Message-Id: <200402161901.i1GJ1e6Y034152@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 19:01:41 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59713 amd64 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 515AC16A4CE; Mon, 16 Feb 2004 11:51:01 -0800 (PST) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2214543D1F; Mon, 16 Feb 2004 11:51:01 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 519011378D; Mon, 16 Feb 2004 20:50:57 +0100 (CET) Date: Mon, 16 Feb 2004 20:51:02 +0100 (CET) From: Gerald Pfeifer To: David O'Brien In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Alexander Kabaev cc: amd64@FreeBSD.org Subject: Re: AMD64 and lang/gcc3x on -CURRENT X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 19:51:01 -0000 David, Kan, AMD64 guys? On Wed, 11 Feb 2004, Gerald Pfeifer wrote: > would you mind having a look at these? > > http://bento.freebsd.org/errorlogs/amd64-5-latest/gcc-3.2.3_1.log > http://bento.freebsd.org/errorlogs/amd64-5-latest/gcc-3.3.3_20040202.log Currently all GCC 3.x ports seem to be broken with this failure mode: *** Configuration amd64-portbld-freebsd5.2 not supported Configure in /tmp/a/ports/lang/gcc33/work/build/gcc failed, exiting. and my gut tells me someone renamed x86_64 to amd64 somewhere without making proper adjustment in upstream packages or something like that. This is a heads up that I will shortly mark all affected GCC ports BROKEN, unless someone steps forward and fixes this (not by hacking the port, but by submitting proper patches upstream, if needed). Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/ From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 13:28:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41CE016A4CE for ; Mon, 16 Feb 2004 13:28:44 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0A4E43D1F for ; Mon, 16 Feb 2004 13:28:43 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1GLSfni008963; Mon, 16 Feb 2004 22:28:41 +0100 (MET) Date: Mon, 16 Feb 2004 22:28:41 +0100 (MET) From: Adriaan de Groot To: Gerald Pfeifer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: amd64@FreeBSD.org Subject: Re: AMD64 and lang/gcc3x on -CURRENT X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 21:28:44 -0000 On Mon, 16 Feb 2004, Gerald Pfeifer wrote: > *** Configuration amd64-portbld-freebsd5.2 not supported > Configure in /tmp/a/ports/lang/gcc33/work/build/gcc failed, exiting. > > and my gut tells me someone renamed x86_64 to amd64 somewhere without > making proper adjustment in upstream packages or something like that. >From things David and/or Peter have written I've gathered the following: 1) AMD didn't give the platform an official name till fairly late 2) Some folks chose amd64 3) Later the muttonheads at the FSF chose x86_64 > This is a heads up that I will shortly mark all affected GCC ports BROKEN, > unless someone steps forward and fixes this (not by hacking the port, but > by submitting proper patches upstream, if needed). I think hacking the port is the only way, since there's such a fundamental disagreement in what the platform is called (this same problem shows up in lots of software packages, BTW, like OpenAFS). From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 13:48:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A11716A4CE; Mon, 16 Feb 2004 13:48:13 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1114943D2D; Mon, 16 Feb 2004 13:48:13 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 8F1AE7303A; Mon, 16 Feb 2004 16:48:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040216214812.8F1AE7303A@freebsd-current.sentex.ca> Date: Mon, 16 Feb 2004 16:48:12 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 21:48:13 -0000 TB --- 2004-02-16 21:02:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-16 21:02:09 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-16 21:02:09 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-16 21:06:32 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp as --defsym FLAGS=0x80 --defsym SIOPRT=0x3f8 --defsym SIOFMT=0x3 --defsym SIOSPD=9600 --32 -o boot2.o boot2.s cc -Os -fno-guess-branch-probability -fomit-frame-pointer -mno-align-long-strings -mrtd -DUFS1_AND_UFS2 -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2/../../common -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -ffreestanding -mpreferred-stack-boundary=2 -m32 -c /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2/sio.S /var/tmp//ccmQQsuJ.s: Assembler messages: /var/tmp//ccmQQsuJ.s:84: Error: undefined symbol `SIOSPD' in operation setting `SIO_DIV' /var/tmp//ccmQQsuJ.s:35: Error: undefined symbol `SIO_FMT' in operation /var/tmp//ccmQQsuJ.s:39: Error: value of 000000000001c200 too large for field of 2 bytes at 000000000000000d *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/boot2. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys/boot. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sys. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-16 21:48:12 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-16 21:48:12 - TB --- ERROR: failed to build world TB --- 2004-02-16 21:48:12 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 15:19:26 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8983C16A4CE; Mon, 16 Feb 2004 15:19:26 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FA9B43D2D; Mon, 16 Feb 2004 15:19:26 -0800 (PST) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) i1GNJQbv076882; Mon, 16 Feb 2004 15:19:26 -0800 (PST) (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1GNJQd4076878; Mon, 16 Feb 2004 15:19:26 -0800 (PST) (envelope-from obrien) Date: Mon, 16 Feb 2004 15:19:26 -0800 (PST) From: "David E. O'Brien" Message-Id: <200402162319.i1GNJQd4076878@freefall.freebsd.org> To: obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org, obrien@FreeBSD.org Subject: Re: amd64/62295: ipsec failure on 5.2.1-RC amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 23:19:26 -0000 Synopsis: ipsec failure on 5.2.1-RC amd64 Responsible-Changed-From-To: freebsd-amd64->obrien Responsible-Changed-By: obrien Responsible-Changed-When: Mon Feb 16 15:19:16 PST 2004 Responsible-Changed-Why: I'll commit this. http://www.freebsd.org/cgi/query-pr.cgi?pr=62295 From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 15:51:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 108A716A4CE for ; Mon, 16 Feb 2004 15:51:55 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F211943D2D for ; Mon, 16 Feb 2004 15:51:54 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.10) with ESMTP id i1GNpsOJ091188; Mon, 16 Feb 2004 15:51:54 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i1GNprZC091187; Mon, 16 Feb 2004 15:51:53 -0800 (PST) (envelope-from obrien) Date: Mon, 16 Feb 2004 15:51:53 -0800 From: "David O'Brien" To: ml@fruitbat.demon.co.uk Message-ID: <20040216235153.GC89536@dragon.nuxi.com> References: <20040126175234.GA28717@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-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 cc: freebsd-amd64@freebsd.org Subject: Re: malloc() over 4Gb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 23:51:55 -0000 On Mon, Feb 16, 2004 at 02:00:39PM +0000, ml@fruitbat.demon.co.uk wrote: > I went out and bought the box and it does indeed seem to malloc() over > 4Gb. However, if you change the allocation from 7*GB to 8*GB in your > sample program, it still keels over inside malloc()! Define 'keels over'. Details please. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 16 16:47:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D44016A4CE for ; Mon, 16 Feb 2004 16:47:52 -0800 (PST) Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2CD743D1F for ; Mon, 16 Feb 2004 16:47:51 -0800 (PST) (envelope-from james@bigtex.jrv.org) Received: from bigtex.jrv.org (localhost [127.0.0.1]) by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i1H0loo8046759 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 16 Feb 2004 18:47:50 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i1H0loCW046756; Mon, 16 Feb 2004 18:47:50 -0600 (CST) Date: Mon, 16 Feb 2004 18:47:50 -0600 (CST) Message-Id: <200402170047.i1H0loCW046756@bigtex.jrv.org> From: James Van Artsdalen To: ml@fruitbat.demon.co.uk In-reply-to: (ml@fruitbat.demon.co.uk) References: cc: freebsd-amd64@freebsd.org Subject: Re: malloc() over 4Gb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 00:47:52 -0000 > From: ml@fruitbat.demon.co.uk > Date: Mon, 16 Feb 2004 14:00:39 +0000 > > I went out and bought the box and it does indeed seem to malloc() over > 4Gb. However, if you change the allocation from 7*GB to 8*GB in your > sample program, it still keels over inside malloc()! > > Do you know if there's any sort of 8Gb clamp in this OS?! Cheers! What does ulimit -d say? From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 00:21:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16B7116A4CE for ; Tue, 17 Feb 2004 00:21:23 -0800 (PST) Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3BE343D2D for ; Tue, 17 Feb 2004 00:21:22 -0800 (PST) (envelope-from ml@fruitbat.demon.co.uk) Received: from pr-webmail-1.demon.net ([194.159.244.51]) by anchor-post-34.mail.demon.net with smtp (Exim 3.35 #1) id 1At0Tq-000OYe-0Y for freebsd-amd64@freebsd.org; Tue, 17 Feb 2004 08:21:22 +0000 Received: from fruitbat.demon.co.uk ([195.74.121.82]) by web.mail.demon.net with http; Tue, 17 Feb 2004 08:21:22 +0000 From: ml@fruitbat.demon.co.uk To: freebsd-amd64@freebsd.org In-Reply-To: <20040216235153.GC89536@dragon.nuxi.com> Date: Tue, 17 Feb 2004 08:21:22 +0000 User-Agent: Demon-WebMail/2.0 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: Subject: Re: malloc() over 4Gb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 08:21:23 -0000 obrien@freebsd.org wrote: > On Mon, Feb 16, 2004 at 02:00:39PM +0000, ml@fruitbat.demon.co.uk wrote: > > I went out and bought the box and it does indeed seem to malloc() over > > 4Gb. However, if you change the allocation from 7*GB to 8*GB in your > > sample program, it still keels over inside malloc()! > > Define 'keels over'. Details please. I could have been clearer, yes.... With the GENERIC kernel, attempting to malloc 8Gb of RAM causes a SIGSEGV deep within malloc(). The stack trace indicates it crashes in tcflow() which is called by malloc(). However, I've found MAXDSIZ in the kernel which was set to 8192*1024*1024. As a result, I've built a new kernel resetting that to 32768*1024*1024 and that seems to work fine now. That said, I'm pretty certain malloc() ain't supposed to crash when MAXDSIZ is hit. I'd expect a NULL to be returned. All this fun and games on 5.2-RELEASE for AMD64. > -- David (obrien@FreeBSD.org) Regards, A. From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 01:33:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8350016A4CE for ; Tue, 17 Feb 2004 01:33:08 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D38443D2D for ; Tue, 17 Feb 2004 01:33:08 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1H9X7ni019302 for ; Tue, 17 Feb 2004 10:33:07 +0100 (MET) Date: Tue, 17 Feb 2004 10:33:07 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: The return of threading errors in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 09:33:08 -0000 Since a couple of weeks again, on -CURRENT, ogg123 has started bus erroring and segfaulting again, just like it was back in november before Peter's stack fixes. The "backtrace" is: (gdb) bt #0 0x0000000200f19320 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x0000000200f10d68 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x0000000200f0f0ed in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #3 0xd0d0d0d0d0d0d0d0 in ?? () so that's totally useless; I've just finished complete upgrade cycle with FreeBSD beans.ebn.kun.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Feb 16 08:12:04 CET 2004 root@beans.ebn.kun.nl:/usr/obj/mnt/sys/CURRENT/src/sys/GENERIC amd64 and done a portupgrade -acf, so things ought to be clean. The problem doesn't trigger as often or as easily as it used to - I'm trying libc_r now to see if that makes a difference, as well. From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 01:47:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F83716A4DC for ; Tue, 17 Feb 2004 01:47:52 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D2C643D1D for ; Tue, 17 Feb 2004 01:47:51 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1H9loni027798 for ; Tue, 17 Feb 2004 10:47:50 +0100 (MET) Date: Tue, 17 Feb 2004 10:47:50 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: The return of threading errors in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 09:47:52 -0000 libc_r seems better behaved; possibly unrelated, I did just get a lock order reversal, with this trace (1st fell off the screen, sorry): 2nd 0xffffffff807dcca0 swap_pager swhash (swap_pager swhash) @ /mnt/sys/CURRENT /src/sys/vm/swap_pager.c:1822 3rd 0xffffff003e0e8700 vm object (vm object) @ /mnt/sys/CURRENT/src/sys/vm/uma_ core.c:886 Stack backtrace: backtrace() at backtrace+0x17 witness_checkorder() at witness_checkorder+0x678 _mtx_lock_flags() at _mtx_lock_flags+0x80 obj_alloc() at obj_alloc+0x41 slab_zalloc() at slab_zalloc+0xa2 uma_zone_slab() at uma_zone_slab+0xd5 uma_zalloc_internal() at uma_zalloc_internal+0x3c uma_zalloc_arg() at uma_zalloc_arg+0x3a6 swp_pager_meta_build() at swp_pager_meta_build+0x14b swap_pager_putpages() at swap_pager_putpages+0x2f3 default_pager_putpages() at default_pager_putpages+0xa vm_pageout_flush() at vm_pageout_flush+0x15e vm_pageout_clean() at vm_pageout_clean+0x292 vm_pageout_scan() at vm_pageout_scan+0x65f vm_pageout() at vm_pageout+0x377 fork_exit() at fork_exit+0xd9 fork_trampoline() at fork_trampoline+0xe -- Adriaan de Groot adridg@cs.kun.nl Kamer A6020 024-3652272 GPG Key Fingerprint 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE http://www.cs.kun.nl/~adridg/research/ From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 11:29:53 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04F4416A4CE for ; Tue, 17 Feb 2004 11:29:53 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id F35A943D1D for ; Tue, 17 Feb 2004 11:29:52 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id D32992A8EC for ; Tue, 17 Feb 2004 11:29:52 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 495FD2C1AF for ; Tue, 17 Feb 2004 11:29:52 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.11/8.12.10) with ESMTP id i1HJTpPE082607; Tue, 17 Feb 2004 11:29:51 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.11/8.12.10/Submit) id i1HJTgiM082606; Tue, 17 Feb 2004 11:29:42 -0800 (PST) (envelope-from peter) From: Peter Wemm To: adridg@cs.kun.nl, Adriaan de Groot , freebsd-amd64@freebsd.org Date: Tue, 17 Feb 2004 11:29:42 -0800 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402171129.42641.peter@wemm.org> Subject: Re: The return of threading errors in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 19:29:53 -0000 On Tuesday 17 February 2004 01:33 am, Adriaan de Groot wrote: > Since a couple of weeks again, on -CURRENT, ogg123 has started bus > erroring and segfaulting again, just like it was back in november > before Peter's stack fixes. The "backtrace" is: > > (gdb) bt > #0 0x0000000200f19320 in pthread_testcancel () from > /usr/lib/libpthread.so.1 > #1 0x0000000200f10d68 in pthread_mutexattr_init () > from /usr/lib/libpthread.so.1 > #2 0x0000000200f0f0ed in pthread_mutexattr_init () > from /usr/lib/libpthread.so.1 > #3 0xd0d0d0d0d0d0d0d0 in ?? () > > so that's totally useless; I've just finished complete upgrade cycle > with > > FreeBSD beans.ebn.kun.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Feb > 16 08:12:04 CET 2004 > root@beans.ebn.kun.nl:/usr/obj/mnt/sys/CURRENT/src/sys/GENERIC amd64 > > and done a portupgrade -acf, so things ought to be clean. > > The problem doesn't trigger as often or as easily as it used to - I'm > trying libc_r now to see if that makes a difference, as well. I'm currently suspicious of the implementation of signal delivery and return handling for unrelated reasons. It is possible that its also affecting this. I'm trying to diagnose/fix an i386 binary problem and it looks like something might be missing in the MD code thats needed for interaction with KSE, or something could be wrong with the ERESTART handling. Anyway, I'll look into this again. BTW; can somebody point me to a .ogg file I can test with? BTW2: the last time I asked for a .ogg file, I got sent a livejournal recording from one of the committers' sisters.. it was very scary. :-) -- 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 Tue Feb 17 12:04:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F9AC16A4CE for ; Tue, 17 Feb 2004 12:04:47 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A9BC43D2D for ; Tue, 17 Feb 2004 12:04:47 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i1HK332h002487; Tue, 17 Feb 2004 12:03:03 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i1HK338p002486; Tue, 17 Feb 2004 12:03:03 -0800 Date: Tue, 17 Feb 2004 12:03:03 -0800 From: Brooks Davis To: Peter Wemm Message-ID: <20040217200302.GA32426@Odin.AC.HMC.Edu> References: <200402171129.42641.peter@wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <200402171129.42641.peter@wemm.org> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: adridg@cs.kun.nl cc: freebsd-amd64@freebsd.org Subject: Re: The return of threading errors in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 20:04:47 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 17, 2004 at 11:29:42AM -0800, Peter Wemm wrote: > I'm currently suspicious of the implementation of signal delivery and=20 > return handling for unrelated reasons. It is possible that its also=20 > affecting this. I'm trying to diagnose/fix an i386 binary problem and=20 > it looks like something might be missing in the MD code thats needed=20 > for interaction with KSE, or something could be wrong with the ERESTART= =20 > handling. Anyway, I'll look into this again. >=20 > BTW; can somebody point me to a .ogg file I can test with? =20 There are several samples on the vorbis website: http://www.vorbis.com/music.psp -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAMnN1XY6L6fI4GtQRAtkkAKC9lILVQpfC7XtTWLLGUYxFUbWEhACgzbw3 xHkeZ6kGeUNjzPdSD4L+VOQ= =kTLd -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 12:33:05 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA52B16A4D1 for ; Tue, 17 Feb 2004 12:33:05 -0800 (PST) Received: from chaos.fxp.org (chaos.fxp.org [209.251.159.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F36943D2D for ; Tue, 17 Feb 2004 12:33:05 -0800 (PST) (envelope-from jedgar@fxp.org) Received: by chaos.fxp.org (Postfix, from userid 1000) id 9C9F448C; Tue, 17 Feb 2004 15:33:01 -0500 (EST) Date: Tue, 17 Feb 2004 15:33:01 -0500 From: Chris Faulhaber To: freebsd-amd64@freebsd.org Message-ID: <20040217203301.GA34440@chaos.fxp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: socket() Subject: FreeBSD vs eMachines M6805 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 20:33:05 -0000 Has anyone tried FreeBSD on an eMachines M6805 laptop? I am about to purchase one but have not seen anyone mention trying out FreeBSD on it. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 13:18:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A1A716A4CE for ; Tue, 17 Feb 2004 13:18:52 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EB1643D1D for ; Tue, 17 Feb 2004 13:18:52 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i1HLIp6B006709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 Feb 2004 16:18:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i1HLIkPT051850; Tue, 17 Feb 2004 16:18:46 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16434.34102.544869.558732@grasshopper.cs.duke.edu> Date: Tue, 17 Feb 2004 16:18:46 -0500 (EST) To: freebsd-amd64@freebsd.org In-Reply-To: <20040216080408.GE54371@dragon.nuxi.com> References: <002c01c3f312$947a26a0$c901a8c0@ts> <20040216080408.GE54371@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 21:18:52 -0000 David O'Brien writes: > nVidia nForce3 [for AMD64] chipsets are very problematic for > Unix(BSD)/Linux. I would avoid them if you want to run a non-MS-Windows > operating system. Whew. Just in time, I was just about to order an SK8N. What do you suggest for a solid single-CPU socket-940 board which will use ECC memory? Asus SK8V? I'm ordering a new number-cruncher for my wife... Hopefully, I'll get to play with it some too ;) Drew From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 14:14:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84F3616A4CF for ; Tue, 17 Feb 2004 14:14:08 -0800 (PST) Received: from omega.metrics.com (internal.metrics.com [204.138.110.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDA8643D2D for ; Tue, 17 Feb 2004 14:14:06 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.12.9/8.12.9) with ESMTP id i1HMFwIa028161 for ; Tue, 17 Feb 2004 17:15:58 -0500 (EST) (envelope-from tomh@waterloo.equitrac.com) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id <1NMAN5LK>; Tue, 17 Feb 2004 17:12:39 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Tue, 17 Feb 2004 17:12:28 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 22:14:08 -0000 > Whew. Just in time, I was just about to order an SK8N. What do you > suggest for a solid single-CPU socket-940 board which will use ECC > memory? Asus SK8V? Tyan K8W or K8WS? Tom From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 17 16:08:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B26F16A4CE for ; Tue, 17 Feb 2004 16:08:24 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4FF543D1D for ; Tue, 17 Feb 2004 16:08:23 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i1I08N6B029696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 Feb 2004 19:08:23 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i1I08IWn051981; Tue, 17 Feb 2004 19:08:18 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16434.44274.200375.8454@grasshopper.cs.duke.edu> Date: Tue, 17 Feb 2004 19:08:18 -0500 (EST) To: freebsd-amd64@freebsd.org In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: RE: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 00:08:24 -0000 Haapanen, Tom writes: > > Whew. Just in time, I was just about to order an SK8N. What do you > > suggest for a solid single-CPU socket-940 board which will use ECC > > memory? Asus SK8V? > > Tyan K8W or K8WS? Thanks. But are you saying the VIA K8T800 chipset is flakey too, and I should only consider AMD-8000 based boards? Just from scanning the last month or so of archives, it looks like the bad hardware is pretty evenly distributed across chipsets, but perhaps that's not enough perspective. I'm new here, after all.. Thanks, Drew From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 00:37:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D36A816A4CE for ; Wed, 18 Feb 2004 00:37:36 -0800 (PST) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3F4143D2D for ; Wed, 18 Feb 2004 00:37:36 -0800 (PST) (envelope-from gerald@pfeifer.com) Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id EAE7D1378D; Wed, 18 Feb 2004 09:37:34 +0100 (CET) Date: Wed, 18 Feb 2004 09:37:36 +0100 (CET) From: Gerald Pfeifer To: adridg@cs.kun.nl In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: amd64@FreeBSD.org Subject: Re: AMD64 and lang/gcc3x on -CURRENT X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 08:37:36 -0000 On Mon, 16 Feb 2004, Adriaan de Groot wrote: > On Mon, 16 Feb 2004, Gerald Pfeifer wrote: >> *** Configuration amd64-portbld-freebsd5.2 not supported >> Configure in /tmp/a/ports/lang/gcc33/work/build/gcc failed, exiting. >> and my gut tells me someone renamed x86_64 to amd64 somewhere without >> making proper adjustment in upstream packages or something like that. > > From things David and/or Peter have written I've gathered the following: > > 1) AMD didn't give the platform an official name till fairly late > 2) Some folks chose amd64 > 3) Later the muttonheads at the FSF chose x86_64 And right they were. See yesterdays press announcement by Intel. Plus, the FSF tools had support for x86_64 before AMD announced their marketing names (AMD64, Opteron, Athlon64,...), as far as I know. >> This is a heads up that I will shortly mark all affected GCC ports BROKEN, >> unless someone steps forward and fixes this (not by hacking the port, but >> by submitting proper patches upstream, if needed). > I think hacking the port is the only way, since there's such a fundamental > disagreement in what the platform is called (this same problem shows up in > lots of software packages, BTW, like OpenAFS). Yes, but these changes should be submitted back upstream to the FSF, at least for the GCC 3.3, 3.4 and mainline branches which are still open for patches, not kept as FreeBSD-local patches. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/ From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 03:30:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA6D16A4CE for ; Wed, 18 Feb 2004 03:30:13 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13B8343D1D for ; Wed, 18 Feb 2004 03:30:13 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/3.61) with ESMTP id i1IBUBCU021996 for ; Wed, 18 Feb 2004 12:30:11 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 18 Feb 2004 12:30:08 +0100 User-Agent: KMail/1.6.51 References: <200402171129.42641.peter@wemm.org> In-Reply-To: <200402171129.42641.peter@wemm.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200402181230.11078.adridg@cs.kun.nl> Subject: Re: The return of threading errors in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 11:30:13 -0000 On Tuesday 17 February 2004 20:29, you wrote: > On Tuesday 17 February 2004 01:33 am, Adriaan de Groot wrote: > > The problem doesn't trigger as often or as easily as it used to - I'm > > trying libc_r now to see if that makes a difference, as well. > > I'm currently suspicious of the implementation of signal delivery and > return handling for unrelated reasons. It is possible that its also libc_r seems solid as a rock; libpthread can play ok for a while but seems = to=20 bail as soon as there is some load on the system. libpth doesn't work at al= l,=20 missing a pthread_push_create symbol. Any gdb trickery I can use on the cor= e=20 files to get more useful information out of them over the short bt? =2D-=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot Would you like a freem? From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 05:06:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5091C16A4CE for ; Wed, 18 Feb 2004 05:06:52 -0800 (PST) Received: from omega.metrics.com (internal.metrics.com [204.138.110.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02B3743D1D for ; Wed, 18 Feb 2004 05:06:52 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.12.9/8.12.9) with ESMTP id i1ID8eIa046555 for ; Wed, 18 Feb 2004 08:08:41 -0500 (EST) (envelope-from tomh@waterloo.equitrac.com) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id <1NMAN6N4>; Wed, 18 Feb 2004 08:05:24 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Wed, 18 Feb 2004 08:05:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Flag: NO X-Scanned-By: milter-spamc/0.14.238 (omega [192.168.96.200]); pass=YES; Wed, 18 Feb 2004 08:08:41 -0500 X-Spam-Status: NO, hits=0.00 required=5.00 X-Spam-Level: Subject: RE: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 13:06:52 -0000 Andrew Gallatin: > Thanks. But are you saying the VIA K8T800 chipset is flakey too, and I > should only consider AMD-8000 based boards? Just from scanning the > last month or so of archives, it looks like the bad hardware is pretty > evenly distributed across chipsets, but perhaps that's not enough > perspective. I'm new here, after all.. Absolutely not saying that. I don't have any experience with K8T800-based boards at all. But many people have been highly successful with the Tyan boards (I have been running a K8S Pro-based server in production for more than two weeks now, and the mysqld process is approaching 100 hours of CPU time.) So I am only suggesting them as an option ... Tom From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 07:22:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BA3516A4CF for ; Wed, 18 Feb 2004 07:22:34 -0800 (PST) Received: from mail.silzer.net (unknown [66.207.215.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58D3543D1D for ; Wed, 18 Feb 2004 07:22:34 -0800 (PST) (envelope-from fbsd@silzer.net) Received: by mail.silzer.net (Postfix, from userid 91) id 90A934C2A8; Wed, 18 Feb 2004 10:22:33 -0500 (EST) Received: from [192.168.1.99] (ti-book.int.silzer.net [192.168.1.99]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.silzer.net (Postfix) with ESMTP id 10E104C296 for ; Wed, 18 Feb 2004 10:22:26 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: <16434.44274.200375.8454@grasshopper.cs.duke.edu> References: <16434.44274.200375.8454@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <42E6A174-6226-11D8-98F7-000393921E22@silzer.net> Content-Transfer-Encoding: 7bit From: Scott Silzer Date: Wed, 18 Feb 2004 10:22:27 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.612) X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on kitty.silzer.net X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 15:22:34 -0000 Seams like an appropriate thread to ask so has any one had any experience with the Arima/Accelertech ATO2161-A ? http://www.accelertech.com/motherboard.php Scott Silzer On Feb 17, 2004, at 19:08, Andrew Gallatin wrote: > > Haapanen, Tom writes: >>> Whew. Just in time, I was just about to order an SK8N. What do you >>> suggest for a solid single-CPU socket-940 board which will use ECC >>> memory? Asus SK8V? >> >> Tyan K8W or K8WS? > > > Thanks. But are you saying the VIA K8T800 chipset is flakey too, and > I should only consider AMD-8000 based boards? Just from scanning the > last month or so of archives, it looks like the bad hardware is pretty > evenly distributed across chipsets, but perhaps that's not enough > perspective. I'm new here, after all.. > > Thanks, > > Drew > _______________________________________________ > 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 Feb 18 13:37:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F372A16A4D4; Wed, 18 Feb 2004 13:37:05 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9D1043D1D; Wed, 18 Feb 2004 13:37:05 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 6BD217303A; Wed, 18 Feb 2004 16:37:05 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040218213705.6BD217303A@freebsd-current.sentex.ca> Date: Wed, 18 Feb 2004 16:37:05 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 21:37:06 -0000 TB --- 2004-02-18 20:50:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-18 20:50:32 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-18 20:50:32 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-18 20:55:03 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. [...] ===> usr.bin/false cc -O -pipe -c /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin/false/false.c cc -O -pipe -o false false.o gzip -cn /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin/false/false.1 > false.1.gz ===> usr.bin/fetch cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin/fetch/fetch.c /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin/fetch/fetch.c: In function `stat_bytes': /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin/fetch/fetch.c:158: warning: int format, different type arg (arg 4) *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin/fetch. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/usr.bin. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-18 21:37:05 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-18 21:37:05 - TB --- ERROR: failed to build world TB --- 2004-02-18 21:37:05 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 14:52:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E340816A4CE for ; Wed, 18 Feb 2004 14:52:52 -0800 (PST) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B42043D2D for ; Wed, 18 Feb 2004 14:52:52 -0800 (PST) (envelope-from higgsr@rpi.edu) Received: from webmail.rpi.edu (webmail.rpi.edu [128.113.26.21]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i1IMqpnH005247 for ; Wed, 18 Feb 2004 17:52:51 -0500 Message-Id: <200402182252.i1IMqpnH005247@smtp2.server.rpi.edu> Content-Type: text/plain Content-Disposition: inline To: freebsd-amd64@freebsd.org From: higgsr@rpi.edu X-Originating-Ip: 66.65.223.198 Mime-Version: 1.0 Date: Wed, 18 Feb 2004 17:52:51 EST X-Mailer: EMUmail 4.00 X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Contents of freebsd-amd64 Digest, Vol 37, Issue 3 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: higgsr@rpi.edu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 22:52:53 -0000 > David O'Brien writes: > > > nVidia nForce3 [for AMD64] chipsets are very problematic for > > Unix(BSD)/Linux. I would avoid them if you want to run a > non-MS-Windows > > operating system. > > Whew. Just in time, I was just about to order an SK8N. What do you > suggest for a solid single-CPU socket-940 board which will use ECC > memory? Asus SK8V? > > I'm ordering a new number-cruncher for my wife... > Hopefully, I'll get to play with it some too ;) > > Drew FWIW, I have an SK8N running -current. I added a PCI ethernet card and disabled ACPI. The SATA even works! I have tried to use the USB, Firewire, etc. Ray From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 18 15:10:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 112F516A4D0 for ; Wed, 18 Feb 2004 15:10:02 -0800 (PST) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABE9143D2F for ; Wed, 18 Feb 2004 15:10:01 -0800 (PST) (envelope-from higgsr@rpi.edu) Received: from webmail.rpi.edu (webmail.rpi.edu [128.113.26.21]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i1INA0nH008104 for ; Wed, 18 Feb 2004 18:10:01 -0500 Message-Id: <200402182310.i1INA0nH008104@smtp2.server.rpi.edu> Content-Type: text/plain Content-Disposition: inline To: freebsd-amd64@freebsd.org From: higgsr@rpi.edu X-Originating-Ip: 66.65.223.198 Mime-Version: 1.0 Date: Wed, 18 Feb 2004 18:10:00 EST X-Mailer: EMUmail 4.00 X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Contents of freebsd-amd64 Digest, Vol 37, Issue 3 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: higgsr@rpi.edu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 23:10:02 -0000 > I have tried to use the USB, Firewire, etc. I meant to say "have not". Ray From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 02:33:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58EB216A4CE; Thu, 19 Feb 2004 02:33:57 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA2343D2D; Thu, 19 Feb 2004 02:33:57 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 928EA7303A; Thu, 19 Feb 2004 05:33:56 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040219103356.928EA7303A@freebsd-current.sentex.ca> Date: Thu, 19 Feb 2004 05:33:56 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 10:33:57 -0000 TB --- 2004-02-19 09:35:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-19 09:35:54 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-19 09:35:54 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-19 09:40:26 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. TB --- 2004-02-19 10:27:46 - building generic kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Feb 19 10:27:46 GMT 2004 >>> Kernel build for GENERIC completed on Thu Feb 19 10:33:55 GMT 2004 TB --- 2004-02-19 10:33:55 - generating LINT kernel config TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- /usr/bin/make -B LINT TB --- 2004-02-19 10:33:55 - building LINT kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Feb 19 10:33:55 GMT 2004 -------------------------------------------------------------- ===> LINT mkdir -p /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys cd /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf; PATH=/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/games:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys/LINT /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf/LINT FYI: static unit limits for vcoda are set: NVCODA=4 config: Error: device "cy" is unknown config: 1 errors WARNING: kernel contains GPL contaminated ext2fs filesystem *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-19 10:33:56 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-19 10:33:56 - TB --- ERROR: failed to build lint kernel TB --- 2004-02-19 10:33:56 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 06:37:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8825E16A4CE; Thu, 19 Feb 2004 06:37:34 -0800 (PST) Received: from mail.takas.lt (mail-src.takas.lt [212.59.31.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79FBC43D1F; Thu, 19 Feb 2004 06:37:31 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: from mail pickup service by mail.takas.lt with Microsoft SMTPSVC; Thu, 19 Feb 2004 16:37:26 +0200 Received: from mx2.freebsd.org ([216.136.204.119]) by mail.takas.lt with Microsoft SMTPSVC(5.0.2195.5329); Thu, 19 Feb 2004 15:14:54 +0200 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 611A1577E4; Thu, 19 Feb 2004 05:14:41 -0800 (PST) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 65E2516A532; Thu, 19 Feb 2004 05:14:33 -0800 (PST) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58EB216A4CE; Thu, 19 Feb 2004 02:33:57 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA2343D2D; Thu, 19 Feb 2004 02:33:57 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 928EA7303A; Thu, 19 Feb 2004 05:33:56 -0500 (EST) From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040219103356.928EA7303A@freebsd-current.sentex.ca> Date: Thu, 19 Feb 2004 05:33:56 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-OriginalArrivalTime: 19 Feb 2004 13:14:54.0575 (UTC) FILETIME=[5D5E57F0:01C3F6EA] Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 14:37:34 -0000 TB --- 2004-02-19 09:35:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-19 09:35:54 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-19 09:35:54 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-19 09:40:26 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. TB --- 2004-02-19 10:27:46 - building generic kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Feb 19 10:27:46 GMT 2004 >>> Kernel build for GENERIC completed on Thu Feb 19 10:33:55 GMT 2004 TB --- 2004-02-19 10:33:55 - generating LINT kernel config TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- /usr/bin/make -B LINT TB --- 2004-02-19 10:33:55 - building LINT kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Feb 19 10:33:55 GMT 2004 -------------------------------------------------------------- ===> LINT mkdir -p /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys cd /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf; PATH=/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/games:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys/LINT /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf/LINT FYI: static unit limits for vcoda are set: NVCODA=4 config: Error: device "cy" is unknown config: 1 errors WARNING: kernel contains GPL contaminated ext2fs filesystem *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-19 10:33:56 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-19 10:33:56 - TB --- ERROR: failed to build lint kernel TB --- 2004-02-19 10:33:56 - tinderbox aborted _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 08:41:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF3B916A4CE for ; Thu, 19 Feb 2004 08:41:18 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7858A43D2D for ; Thu, 19 Feb 2004 08:41:18 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/3.62) with ESMTP id i1JGfHfB013828 for ; Thu, 19 Feb 2004 17:41:17 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Thu, 19 Feb 2004 17:41:15 +0100 User-Agent: KMail/1.6.51 MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-Id: <200402191741.16824.adridg@cs.kun.nl> Subject: XFig running? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 16:41:19 -0000 I just tried to compile xfig from ports, and while it builds fine, it then= =20 segfaults on startup inside libXpm.so. It goes like this: (gdb) bt #0 0x00000002008b4dae in PutPixel32 (ximage=3D0x7e8100, x=3D63, y=3D63, pixel=3D6369863) at create.c:1826 #1 0x00000002008b60e8 in ParseAndPutPixels (data=3D0x7fffffffd980, width= =3D64, height=3D64, ncolors=3D253, cpp=3D2, colorTable=3D0x7e1000, hashtable=3D0x7fffffffd860, image=3D0x7e8100, image_pixels=3D0x7e6000, shapeimage=3D0x0, shape_pixels=3D0x7e6800) at create.c:2391 #2 0x00000002008b58a1 in xpmParseDataAndCreate (display=3D0x74b000, data=3D0x7fffffffd980, image_return=3D0x7fffffffde98, shapeimage_return=3D0x7fffffffde90, image=3D0x7fffffffde10, info=3D0x7fffffffddd0, attributes=3D0x723660) at create.c:2158 #3 0x00000002008bd4cd in XpmCreateImageFromData (display=3D0x74b000, data=3D0x663180, image_return=3D0x7fffffffde98, shapeimage_return=3D0x7fffffffde90, attributes=3D0x723660) at CrIFrDat.= c:63 #4 0x00000002008bc66f in XpmCreatePixmapFromData (display=3D0x74b000, d=3D33554910, data=3D0x663180, pixmap_return=3D0x71e230, shapemask_return=3D0x7fffffffdee8, attributes=3D0x723660) at CrPFrDat.c= :57 #5 0x000000000045b605 in set_xpm_icon () at main.c:1787 #6 0x00000000004592a7 in main (argc=3D1, argv=3D0x7fffffffe7c0) at main.c:= 1089 Weirdly, adding a printf() in PutPixel32 in libXpm just makes it work - tho= ugh=20 slowly. I've mucked about a little, changing the code in subtle ways, but i= t=20 just keeps bailing. I get the vague feeling the compiler is falling over=20 trying to discombobulate the casts in that function. Anyway, does anyone have a working xfig?=20 =2D-=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot Would you like a freem? From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 19 12:24:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5C8516A4CE; Thu, 19 Feb 2004 12:24:13 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABE2F43D1D; Thu, 19 Feb 2004 12:24:13 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 45F037303A; Thu, 19 Feb 2004 15:24:13 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040219202413.45F037303A@freebsd-current.sentex.ca> Date: Thu, 19 Feb 2004 15:24:13 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 20:24:13 -0000 TB --- 2004-02-19 20:13:34 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-19 20:13:34 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-19 20:13:34 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-19 20:14:49 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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 [...] ===> lib/libnetgraph rm -f .depend mkdep -f .depend -a /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/sock.c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/msg.c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/debug.c cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/sock.c cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/msg.c cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/debug.c In file included from /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/debug.c:65: /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netgraph/ng_ether.h:71: error: syntax error before "hook_p" *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-19 20:24:13 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-19 20:24:13 - TB --- ERROR: failed to build world TB --- 2004-02-19 20:24:13 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 00:40:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2794F16A4CE; Fri, 20 Feb 2004 00:40:01 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D7EB43D1F; Fri, 20 Feb 2004 00:40:01 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9306C7303A; Fri, 20 Feb 2004 03:40:00 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040220084000.9306C7303A@freebsd-current.sentex.ca> Date: Fri, 20 Feb 2004 03:40:00 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2004 08:40:01 -0000 TB --- 2004-02-20 08:23:28 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-20 08:23:28 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-20 08:23:28 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-20 08:29:30 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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 [...] ===> lib/libnetgraph rm -f .depend mkdep -f .depend -a /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/sock.c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/msg.c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/debug.c cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/sock.c cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/msg.c cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/debug.c In file included from /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph/debug.c:65: /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netgraph/ng_ether.h:71: error: syntax error before "hook_p" *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/lib/libnetgraph. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-20 08:40:00 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-20 08:40:00 - TB --- ERROR: failed to build world TB --- 2004-02-20 08:40:00 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 04:56:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 233AA16A4CE for ; Fri, 20 Feb 2004 04:56:57 -0800 (PST) Received: from hermes.ukrtel.com (hermes.ukrtel.com [194.242.53.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53F1943D1D for ; Fri, 20 Feb 2004 04:56:56 -0800 (PST) (envelope-from anar@kiev.farlep.net) Received: from anar (paradigma.ukrtel.com [194.242.53.46]) by hermes.ukrtel.com (8.12.9/8.12.6) with SMTP id i1KCuQW6003583 for ; Fri, 20 Feb 2004 14:56:26 +0200 Message-ID: <001001c3f7b1$03cfd4d0$3201010a@anar> From: "Alishov Anar" To: Date: Fri, 20 Feb 2004 14:56:47 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: TROUBLE With Controller SIL 3114 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2004 12:56:57 -0000 Hello. I have trouble with Serial ATA, Please help. The problem is: I have Motherboard with controller Sil 3114 for ATA and SATA(RAID/no = RAID). 2 Opteron 242 proccessor, on FreeBSD 5.2-CURRENT OS. 4 HDD WD250 - as one RAID Set 0+1, I try and without raid to test how = it's can be So, when the kernel is boot ,the system was found Sil 3114 Controller = after it, system looking for devices but it's call the error. DMSEG: atapci0: port = 0xe000-0xe00f,0xe080-0xe083,0xe400-0xe407,0xe480-0xe483,0xec00-0xec07 = mem 0xfeafe c00-0xfeafefff irq 9 at device 5.0 on pci3 . . . ad2: 6149MB [13328/15/63] at ata1-master = UDMA33 ata2-master: FAILURE - ATA_IDENTIFY no interrupt ata2-master: FAILURE - ATA_IDENTIFY status=3D51 = error=3D4 LBA=3D0 ata2-master: FAILURE - ATA_IDENTIFY no interrupt ata2-master: FAILURE - ATA_IDENTIFY status=3Dd1 = error=3Dd1 LBA=3D0 ata3-master: FAILURE - ATA_IDENTIFY no interrupt ata3-master: FAILURE - ATA_IDENTIFY status=3D51 = error=3D4 LBA=3D0 ata3-master: FAILURE - ATA_IDENTIFY no interrupt ata3-master: FAILURE - ATA_IDENTIFY status=3Dd1 = error=3Dd1 LBA=3D0 Mounting root from ufs:/dev/ad2s1a stray irq7 Maybe someone have any ideas. From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 14:20:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5CDF16A4CE; Fri, 20 Feb 2004 14:20:24 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99C5543D31; Fri, 20 Feb 2004 14:20:24 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0353C7303A; Fri, 20 Feb 2004 17:20:23 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040220222023.0353C7303A@freebsd-current.sentex.ca> Date: Fri, 20 Feb 2004 17:20:23 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2004 22:20:24 -0000 TB --- 2004-02-20 21:22:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-20 21:22:36 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-20 21:22:36 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-20 21:27:10 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. TB --- 2004-02-20 22:14:00 - building generic kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Feb 20 22:14:00 GMT 2004 >>> Kernel build for GENERIC completed on Fri Feb 20 22:20:22 GMT 2004 TB --- 2004-02-20 22:20:22 - generating LINT kernel config TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- /usr/bin/make -B LINT TB --- 2004-02-20 22:20:23 - building LINT kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Feb 20 22:20:23 GMT 2004 -------------------------------------------------------------- ===> LINT mkdir -p /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys cd /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf; PATH=/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/games:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys/LINT /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf/LINT FYI: static unit limits for vcoda are set: NVCODA=4 config: Error: device "cy" is unknown config: 1 errors WARNING: kernel contains GPL contaminated ext2fs filesystem *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-20 22:20:23 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-20 22:20:23 - TB --- ERROR: failed to build lint kernel TB --- 2004-02-20 22:20:23 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 18:33:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F373316A4CE for ; Fri, 20 Feb 2004 18:33:15 -0800 (PST) Received: from mail.ebit.ca (ebit.ca [207.136.103.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCBEC43D1F for ; Fri, 20 Feb 2004 18:33:15 -0800 (PST) (envelope-from jason+lists.freebsd@lixfeld.ca) Received: from [192.168.100.66] (trek.lixfeld.ca [216.7.194.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.ebit.ca (Postfix) with ESMTP id AA3453C8016 for ; Fri, 20 Feb 2004 21:35:22 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v613) Content-Transfer-Encoding: 7bit Message-Id: <48780481-6416-11D8-8485-000A95989E4A@lixfeld.ca> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@freebsd.org From: Jason Lixfeld Date: Fri, 20 Feb 2004 21:33:07 -0500 X-Mailer: Apple Mail (2.613) Subject: amd64 + ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 02:33:16 -0000 Just how many ports "don't" work with AMD64? :) cvsup doesn't, so I tried the one at http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz It installed fine, but when I try to run it against my supfile, I get: bash-2.05b# cvsup -g -L 2 /usr/local/etc/cvsup/stable-supfile Parsing supfile "/usr/local/etc/cvsup/stable-supfile" Connecting to cvsup2.FreeBSD.org Connected to cvsup2.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running TreeList failed: Network write failure: Input/output error: zlib error 4294967291 Will retry at 21:29:57 ^C bash-2.05b# Grr.. Ok, so I check the deps and it needs ezm3-1.1. so I go to install that: bash-2.05b# cd /usr/ports/lang/ezm3/ bash-2.05b# make ===> ezm3-1.1 is only for alpha i386 sparc64, and you are running amd64. bash-2.05b# *gak!* I give up! Any suggestions or light reading?! :) From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 20 18:48:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3525A16A4CE for ; Fri, 20 Feb 2004 18:48:14 -0800 (PST) Received: from www.digitaleclipse.com (ip-64-139-49-201.sjc.megapath.net [64.139.49.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2359B43D1F for ; Fri, 20 Feb 2004 18:48:14 -0800 (PST) (envelope-from jeremym@www.digitaleclipse.com) Received: (from root@localhost) by www.digitaleclipse.com (8.12.10/8.11.4) id i1L2mDe1075701 for freebsd-amd64@freebsd.org; Fri, 20 Feb 2004 18:48:13 -0800 (PST) (envelope-from jeremym@www.digitaleclipse.com) Received: from www.digitaleclipse.com (localhost [127.0.0.1]) i1L2mAZG075675; Fri, 20 Feb 2004 18:48:10 -0800 (PST) (envelope-from jeremym@www.digitaleclipse.com) Received: (from jeremym@localhost) by www.digitaleclipse.com (8.12.10/8.12.10/Submit) id i1L2mAHI075674; Fri, 20 Feb 2004 18:48:10 -0800 (PST) (envelope-from jeremym) Date: Fri, 20 Feb 2004 18:48:10 -0800 From: Jeremy Mika To: Jason Lixfeld Message-ID: <20040221024810.GA75578@www.digitaleclipse.com> References: <48780481-6416-11D8-8485-000A95989E4A@lixfeld.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48780481-6416-11D8-8485-000A95989E4A@lixfeld.ca> User-Agent: Mutt/1.4i X-Virus-Scanned: by AMaViS perl-11 cc: freebsd-amd64@freebsd.org Subject: Re: amd64 + ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 02:48:14 -0000 Make sure to disable compression in your supfile. ...from ports-supfile # If your network link is a T1 or faster, comment out the following line. *default compress On Fri, Feb 20, 2004 at 09:33:07PM -0500, Jason Lixfeld wrote: > Just how many ports "don't" work with AMD64? :) > > cvsup doesn't, so I tried the one at > http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz It > installed fine, but when I try to run it against my supfile, I get: > > bash-2.05b# cvsup -g -L 2 /usr/local/etc/cvsup/stable-supfile > Parsing supfile "/usr/local/etc/cvsup/stable-supfile" > Connecting to cvsup2.FreeBSD.org > Connected to cvsup2.FreeBSD.org > Server software version: SNAP_16_1h > Negotiating file attribute support > Exchanging collection information > Establishing multiplexed-mode data connection > Running > TreeList failed: Network write failure: Input/output error: zlib error > 4294967291 > Will retry at 21:29:57 > > ^C > bash-2.05b# > > Grr.. Ok, so I check the deps and it needs ezm3-1.1. so I go to > install that: > > bash-2.05b# cd /usr/ports/lang/ezm3/ > bash-2.05b# make > ===> ezm3-1.1 is only for alpha i386 sparc64, and you are running > amd64. > bash-2.05b# > > *gak!* > > I give up! > > Any suggestions or light reading?! :) > > _______________________________________________ > 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 Sat Feb 21 00:17:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B260D16A4CE for ; Sat, 21 Feb 2004 00:17:09 -0800 (PST) Received: from mail.ebit.ca (ebit.ca [207.136.103.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B9A543D1F for ; Sat, 21 Feb 2004 00:17:09 -0800 (PST) (envelope-from jason+lists.freebsd@lixfeld.ca) Received: from [192.168.100.66] (trek.lixfeld.ca [216.7.194.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.ebit.ca (Postfix) with ESMTP id B10E33C8013 for ; Sat, 21 Feb 2004 03:19:18 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v613) Content-Transfer-Encoding: 7bit Message-Id: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@freebsd.org From: Jason Lixfeld Date: Sat, 21 Feb 2004 03:17:02 -0500 X-Mailer: Apple Mail (2.613) Subject: AMD64 + Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 08:17:09 -0000 Just how many ports "don't" work with AMD64? :) cvsup doesn't, so I tried the one at http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz It installed fine, but when I try to run it against my supfile, I get: bash-2.05b# cvsup -g -L 2 /usr/local/etc/cvsup/stable-supfile Parsing supfile "/usr/local/etc/cvsup/stable-supfile" Connecting to cvsup2.FreeBSD.org Connected to cvsup2.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running TreeList failed: Network write failure: Input/output error: zlib error 4294967291 Will retry at 21:29:57 ^C bash-2.05b# Grr.. Ok, so I check the deps and it needs ezm3-1.1. so I go to install that: bash-2.05b# cd /usr/ports/lang/ezm3/ bash-2.05b# make ===> ezm3-1.1 is only for alpha i386 sparc64, and you are running amd64. bash-2.05b# *gak!* I give up! Any suggestions or light reading?! :) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 01:23:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FA5D16A4CE for ; Sat, 21 Feb 2004 01:23:43 -0800 (PST) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6434943D1F for ; Sat, 21 Feb 2004 01:23:42 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from localhost.invalid (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.10/8.12.10) with ESMTP id i1L9I20w007268; Sat, 21 Feb 2004 10:18:03 +0100 (CET) From: Thierry Herbelot To: freebsd-amd64@freebsd.org Date: Sat, 21 Feb 2004 10:23:31 +0100 User-Agent: KMail/1.6 References: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> In-Reply-To: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200402211023.31588.thierry@herbelot.com> Subject: Re: AMD64 + Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: thierry@herbelot.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 09:23:43 -0000 Le Saturday 21 February 2004 09:17, Jason Lixfeld a écrit : > bash-2.05b# cd /usr/ports/lang/ezm3/ > bash-2.05b# make > ===> ezm3-1.1 is only for alpha i386 sparc64, and you are running > amd64. > bash-2.05b# > > *gak!* > > I give up! > > Any suggestions or light reading?! :) you can always install freebsd for i386 and dual boot between IA32 and AMD64 TfH From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 02:42:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0D4516A4CE; Sat, 21 Feb 2004 02:42:01 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id C609843D1F; Sat, 21 Feb 2004 02:42:01 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3507F7303A; Sat, 21 Feb 2004 05:42:01 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040221104201.3507F7303A@freebsd-current.sentex.ca> Date: Sat, 21 Feb 2004 05:42:01 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 10:42:02 -0000 TB --- 2004-02-21 09:43:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-21 09:43:56 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-21 09:43:56 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-21 09:48:32 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. TB --- 2004-02-21 10:35:51 - building generic kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Feb 21 10:35:51 GMT 2004 >>> Kernel build for GENERIC completed on Sat Feb 21 10:42:00 GMT 2004 TB --- 2004-02-21 10:42:00 - generating LINT kernel config TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- /usr/bin/make -B LINT TB --- 2004-02-21 10:42:00 - building LINT kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Feb 21 10:42:00 GMT 2004 -------------------------------------------------------------- ===> LINT mkdir -p /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys cd /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf; PATH=/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/games:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys/LINT /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf/LINT FYI: static unit limits for vcoda are set: NVCODA=4 config: Error: device "cy" is unknown config: 1 errors WARNING: kernel contains GPL contaminated ext2fs filesystem *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-21 10:42:00 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-21 10:42:00 - TB --- ERROR: failed to build lint kernel TB --- 2004-02-21 10:42:00 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 10:49:33 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EC8116A4CE for ; Sat, 21 Feb 2004 10:49:33 -0800 (PST) Received: from mailhost.Mathematik.Uni-Marburg.de (pc12577.Mathematik.Uni-Marburg.DE [137.248.123.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A3CA43D1D for ; Sat, 21 Feb 2004 10:49:32 -0800 (PST) (envelope-from engel@mathematik.uni-marburg.de) Received: from www.mathematik.uni-marburg.de (durban [137.248.123.2]) i1LInVO24596 for ; Sat, 21 Feb 2004 19:49:31 +0100 Received: from 217.84.183.218 (SquirrelMail authenticated user engel) by www.mathematik.uni-marburg.de with HTTP; Sat, 21 Feb 2004 19:49:31 +0100 (CET) Message-ID: <49543.217.84.183.218.1077389371.squirrel@www.mathematik.uni-marburg.de> Date: Sat, 21 Feb 2004 19:49:31 +0100 (CET) From: engel@Mathematik.Uni-Marburg.de To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Building (cross) gcc 3.3 on AMD64 fails X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 18:49:33 -0000 Hi, I'm running FreeBSD 5.2.1RC on an Athlon 64 3000+ machine (Gigabyte GA-K8VT800 with VIA 8T800 chipset). When I try to build a gcc/g++ cross compiler (3.3.2/3.3.3) on the machine for a mips64el-elf target, the build fails with the following error (in configure after "checking for main in -lunwind... no"): *** Configuration amd64-unknown-freebsd5.2.1 not supported When I try to build the native compiler /usr/ports/lang/gcc33, I get the equivalent message. Are there any patches required to compile gcc 3.3 on AMD64? regards, Michael Engel From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 11:47:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E50816A4CE for ; Sat, 21 Feb 2004 11:47:19 -0800 (PST) Received: from mail.wvfiber.com (mail.wvfiber.com [63.223.7.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4624143D1D for ; Sat, 21 Feb 2004 11:47:19 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: by mail.wvfiber.com (Postfix, from userid 65534) id 2910B37550; Sat, 21 Feb 2004 14:47:15 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.wvfiber.com (Postfix) with ESMTP id 924A237542 for ; Sat, 21 Feb 2004 14:46:44 -0500 (EST) Received: from [10.0.1.2] (c-24-30-48-121.mw.client2.attbi.com [24.30.48.121]) by mail.wvfiber.com (Postfix) with ESMTP id 5CFFD3750C for ; Sat, 21 Feb 2004 14:46:44 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: From: Hendrik Scholz Date: Sat, 21 Feb 2004 14:47:11 -0500 X-Mailer: Apple Mail (2.612) X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-5.1 required=5.0 tests=AWL,BAYES_01,USER_AGENT_APPLEMAIL version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: CFLAGS+= -fPIC per default? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 19:47:19 -0000 Hi! I'm just fixing a bunch of ports reported broken on amd64 by bento. Most of these errors are related to a common linker problem: ld: foo.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC Passing -fPIC via CFLAGS fixes the problem in 80% of the cases (the remaining ports need proper CFLAGS handling in the third party application). Adding CFLAGS= -fPIC to /etc/make.conf may be a local solution but are there any drawbacks by adding something like .if ${ARCH} == "amd64" CFLAGS+= -fPIC .endif to ports/Mk/bsd.port.mk? Remaining apps that need fixing then can be patched properly without the amd64 statement, thus making future additions easier, i.e. when the yet-to-be-announced 128Bit architecture needs -fVANILLA_COKE to compile stuff a similar statement can be added to bsd.port.mk and all the ports running on amd64 should automatically be fixed on the new arch. Just my $0.02, Hendrik -- Hendrik Scholz - hscholz@raisdorf.net - http://www.raisdorf.net/ cell phone: 404-606-5324 (US) 0160-1570-272 (DE) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 11:51:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F420616A4CE for ; Sat, 21 Feb 2004 11:51:55 -0800 (PST) Received: from mail.wvfiber.com (mail.wvfiber.com [63.223.7.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB9BB43D2D for ; Sat, 21 Feb 2004 11:51:55 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: by mail.wvfiber.com (Postfix, from userid 65534) id BA0D137A96; Sat, 21 Feb 2004 14:51:54 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.wvfiber.com (Postfix) with ESMTP id 2D33C37A98; Sat, 21 Feb 2004 14:51:23 -0500 (EST) Received: from [10.0.1.2] (c-24-30-48-121.mw.client2.attbi.com [24.30.48.121]) by mail.wvfiber.com (Postfix) with ESMTP id E6F9237A7F; Sat, 21 Feb 2004 14:51:22 -0500 (EST) In-Reply-To: <49543.217.84.183.218.1077389371.squirrel@www.mathematik.uni-marburg.de> References: <49543.217.84.183.218.1077389371.squirrel@www.mathematik.uni-marburg.de> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <63F43F34-64A7-11D8-ACAA-000A95BAD088@raisdorf.net> Content-Transfer-Encoding: 7bit From: Hendrik Scholz Date: Sat, 21 Feb 2004 14:51:50 -0500 To: engel@Mathematik.Uni-Marburg.de X-Mailer: Apple Mail (2.612) X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_APPLEMAIL version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-amd64@freebsd.org Subject: Re: Building (cross) gcc 3.3 on AMD64 fails X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 19:51:56 -0000 Hi! On Feb 21, 2004, at 1:49 PM, engel@Mathematik.Uni-Marburg.de wrote: > *** Configuration amd64-unknown-freebsd5.2.1 not supported Unfortunatly there are no CONFIGURE_HOST and CONFIGURE_BUILD variables like CONFIGURE_TARGET. Try adding x86_64-portbld-freebsd${OSREL} as --host and --build CONFIGURE_ARGS Hendrik -- Hendrik Scholz - hscholz@raisdorf.net - http://www.raisdorf.net/ cell phone: 404-606-5324 (US) 0160-1570-272 (DE) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 12:23:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4220F16A4CE for ; Sat, 21 Feb 2004 12:23:50 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C18F43D1F for ; Sat, 21 Feb 2004 12:23:50 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id DEFDB2A8EC for ; Sat, 21 Feb 2004 12:23:49 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (unknown [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 572382C1AC for ; Sat, 21 Feb 2004 12:23:49 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.11/8.12.10) with ESMTP id i1LKNmIP066648; Sat, 21 Feb 2004 12:23:48 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.11/8.12.10/Submit) id i1LKNhg9066647; Sat, 21 Feb 2004 12:23:43 -0800 (PST) (envelope-from peter) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Sat, 21 Feb 2004 12:23:43 -0800 User-Agent: KMail/1.6 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402211223.43589.peter@wemm.org> Subject: Re: CFLAGS+= -fPIC per default? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 20:23:50 -0000 On Saturday 21 February 2004 11:47 am, Hendrik Scholz wrote: > Adding CFLAGS= -fPIC to /etc/make.conf may be a local solution but > are there any drawbacks by adding something like > .if ${ARCH} == "amd64" > CFLAGS+= -fPIC > .endif > > to ports/Mk/bsd.port.mk? No.. please don't. Although the AMD64 platform supports PIC addressing modes directly, it is still a penalty. (Although thankfully, its nowhere near as expensive as it is on i386!) For example, in libc when built in PIC mode: #ifdef PIC movq PIC_GOT(HIDENAME(curbrk)),%rdx movq (%rdx),%rax #else movq HIDENAME(curbrk)(%rip),%rax #endif The problem is that we can't be sure that everything will be in +/- 31 bit offsets of each other. This means that PIC objects have to do indirect memory references that aren't required in no-pic mode. I386 also loses a general purpose register (%ebx) which is why -fpic is more expensive there. But even though we don't lose a register, its still a cost because of the extra global-offset-table memory references. Footnote: you just made me wonder about some of these ifdefs.. We shouldn't need them for intra-object references like this. I'll have to go and look again. -- 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 Sat Feb 21 12:31:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AB9016A4CE for ; Sat, 21 Feb 2004 12:31:04 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0424D43D1F for ; Sat, 21 Feb 2004 12:31:04 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id BF65B2A8EC for ; Sat, 21 Feb 2004 12:31:03 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (unknown [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 2F6022C1AC for ; Sat, 21 Feb 2004 12:31:03 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.11/8.12.10) with ESMTP id i1LKV316066721; Sat, 21 Feb 2004 12:31:03 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.11/8.12.10/Submit) id i1LKUvCD066717; Sat, 21 Feb 2004 12:30:57 -0800 (PST) (envelope-from peter) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Sat, 21 Feb 2004 12:30:57 -0800 User-Agent: KMail/1.6 References: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> In-Reply-To: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402211230.57825.peter@wemm.org> Subject: Re: AMD64 + Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 20:31:04 -0000 On Saturday 21 February 2004 12:17 am, Jason Lixfeld wrote: > Just how many ports "don't" work with AMD64? :) > > cvsup doesn't, so I tried the one at > http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz It > installed fine, but when I try to run it against my supfile, I get: > > bash-2.05b# cvsup -g -L 2 /usr/local/etc/cvsup/stable-supfile > Parsing supfile "/usr/local/etc/cvsup/stable-supfile" > Connecting to cvsup2.FreeBSD.org > Connected to cvsup2.FreeBSD.org > Server software version: SNAP_16_1h > Negotiating file attribute support > Exchanging collection information > Establishing multiplexed-mode data connection > Running > TreeList failed: Network write failure: Input/output error: zlib > error 4294967291 > Will retry at 21:29:57 > > ^C > bash-2.05b# > > Grr.. Ok, so I check the deps and it needs ezm3-1.1. so I go to > install that: > > bash-2.05b# cd /usr/ports/lang/ezm3/ > bash-2.05b# make > ===> ezm3-1.1 is only for alpha i386 sparc64, and you are running > amd64. > bash-2.05b# > > *gak!* > > I give up! > > Any suggestions or light reading?! :) Have a look at http://people.freebsd.org/~peter/ezm3-amd64/ There are a mountain of diffs and hacks to try and get ezm3 to work with gcc on amd64. There is enough there to enable you to produce the same binary in the package you downloaded. ie: it will blow up with that zlib error. Be sure to put the boot-ezm3-1.1-FBSD_AMD64.tar.bs2 into your /usr/ports/distfiles/ezm3/ directory because its not in John's dist area that the port knows about. As has been mentioned, don't use compress. I know this is a PITA, but I haven't figured out a way around it. The error code is 0xffffffffb which is -5. For zlib, that translates to 'buffer error'. In other words, the callback hooks for zlib in cvsup are not working right. I'd welcome you to try and fix them. :-) -- 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 Sat Feb 21 13:19:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 865E216A4E1; Sat, 21 Feb 2004 13:19:45 -0800 (PST) Received: from mail.atl.us.wormulon.net (unknown [63.223.8.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D08F43D1D; Sat, 21 Feb 2004 13:19:45 -0800 (PST) (envelope-from hscholz@slurmcan.wormulon.net) Received: from localhost (unknown [63.223.8.130]) by mail.atl.us.wormulon.net (Postfix) with ESMTP id 5517A5D878; Sat, 21 Feb 2004 16:20:22 -0500 (EST) Received: from mail.atl.us.wormulon.net ([63.223.8.130]) by localhost (plant.wormulon.net [63.223.8.130]) (amavisd-new, port 10024) with ESMTP id 53207-10; Sat, 21 Feb 2004 16:20:21 -0500 (EST) Received: from slurmcan.wormulon.net (unknown [63.223.7.6]) by mail.atl.us.wormulon.net (Postfix) with ESMTP id 4F0CF5D80B; Sat, 21 Feb 2004 16:20:21 -0500 (EST) Received: by slurmcan.wormulon.net (Postfix, from userid 1001) id F423939845; Sat, 21 Feb 2004 16:20:05 -0500 (EST) To: FreeBSD-gnats-submit@freebsd.org From: Hendrik Scholz X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: <20040221212005.F423939845@slurmcan.wormulon.net> Date: Sat, 21 Feb 2004 16:20:05 -0500 (EST) X-Virus-Scanned: turning SPAM into Slurm since 2003 (wormulon.net) cc: freebsd-amd64@freebsd.org Subject: ti(4) broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Hendrik Scholz List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 21:19:45 -0000 >Submitter-Id: current-users >Originator: Hendrik Scholz >Organization: >Confidential: no >Synopsis: ti(4) broken on amd64 >Severity: non-critical >Priority: low >Category: amd64 >Class: sw-bug >Release: FreeBSD 5.2.1-RC amd64 >Environment: System: FreeBSD slurmcan.wormulon.net 5.2.1-RC FreeBSD 5.2.1-RC #0: Sat Jan 31 12:38:34 GMT 2004 root@ngoc.NUXI.com:/usr/obj/usr/src/sys/GENERIC amd64 >Description: >Description: ti0: mem 0xfc8bc000-0xfc8bffff irq 28 at device 1.0 on pci1 ti0: Ethernet address: 00:60:cf:20:6b:a6 (full dmesg at http://dump.wormulon.net/dmesg/MSI_K8D/dmesg.txt) $ ifconfig ti0 ti0: flags=8843 mtu 1500 options=1b inet6 fe80::260:cfff:fe20:6ba6%ti0 prefixlen 64 scopeid 0x1 inet 63.223.8.203 netmask 0xffffff00 broadcast 63.223.8.255 ether 00:60:cf:20:6b:a6 media: Ethernet autoselect (1000baseSX ) status: active TCP based protocols (ssh) work but scp is very slow and sometimes the connection is dropped due to bad packets. ICMP just misses a bunch of packets: $ ping 63.223.8.133 PING 63.223.8.133 (63.223.8.133): 56 data bytes 64 bytes from 63.223.8.133: icmp_seq=1 ttl=64 time=0.277 ms 64 bytes from 63.223.8.133: icmp_seq=3 ttl=64 time=0.200 ms .. 11 packets transmitted, 8 packets received, 27% packet loss round-trip min/avg/max/stddev = 0.200/0.260/0.316/0.039 ms $ Doing a tcpdump on the host itself reveals: 63.223.8.203 > 63.223.8.34: icmp: echo request (ttl 64, id 29322, len 84, bad cksum 0!) 63.223.8.34 > 63.223.8.203: icmp: echo reply (ttl 128, id 42958, len 84) truncated-ip - 70 bytes missing! 63.223.7.6.22 > 24.30.48.121.1921: P 4294962720:4294962784(64) ack 4294964481 win 33304 (DF) [tos 0x10] (ttl 64, id 29087, len 116, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 7760:7792(32) ack 1185 win 33304 (DF) [tos 0x10] (ttl 64, id 29247, len 84, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 7760:7792(32) ack 1185 win 33304 (DF) [tos 0x10] (ttl 64, id 29247, len 84, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 3808:3840(32) ack 289 win 33304 (DF) [tos 0x10] (ttl 64, id 28931, len 84, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 4294959456:4294959488(32) ack 4294965025 win 33304 (DF) [tos 0x10] (ttl 64, id 28359, len 84, bad cksum 0!) the target sees this: 63.223.8.203 > 63.223.8.34: icmp: echo request (ttl 64, id 29269, len 84) 63.223.8.34 > 63.223.8.203: icmp: echo reply (ttl 128, id 42940, len 84, bad cksum 0!) 63.223.8.203 > 63.223.8.34: icmp: echo request (ttl 64, id 29272, len 84) 63.223.8.34 > 63.223.8.203: icmp: echo reply (ttl 128, id 42943, len 84, bad cksum 0!) ... bad chksum is ok since its a broadcom card with enabled TXCSUM: bge0: flags=8843 mtu 1500 options=1b inet 63.223.8.34 netmask 0xffffff00 broadcast 63.223.8.255 Let's get back to the first tcpdump: - received packets are missing data (arp is always ok!) - the bpf sees packets that belong to another interface $ route get 63.223.7.6 route to: unknown63223007006.ibis7.net destination: 63.223.7.0 mask: 255.255.255.224 interface: bge1 bge1 is used as main interface and the ssh session runs on this interface. - amount of missing data reported by tcpdump for packets from other interface are somewhat static: 6 (very uncommon), 38, 54, 70 Bytes (all for ssh PSH packets) - filtered traffic on host with ti(4): $ tcpdump -ntvi ti0 not arp and not host 63.223.7.6 (outgoing request and the matching incoming reply) 63.223.8.203 > 63.223.8.133: icmp: echo request (ttl 64, id 32019, len 84, bad cksum 0!) 85:54:6e:39:6e:e2 e1:72:44:af:9e:9d d67f 60: 06f0 381a ff4e cd44 c5f0 bef7 d65f f8b0 bf1d a26b 4b19 9ce1 ddb7 85ab fef3 6f09 c73e c2cf 2f04 a8da 0a85 c241 c9e2 16Bytes (MAC + MAC + 08:00) + 46 Bytes data = 62 Bytes The reply packet should be 84 Bytes long. I reproduced this problem on two different Opteron Systems running 5.2.1-RC/amd64 with two different ti cards (same Alteon type) and different cables. The same configuration runs fine on FreeBSD/i386. Hendrik >How-To-Repeat: >Fix: From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 13:20:17 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1895E16A4CF for ; Sat, 21 Feb 2004 13:20:17 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FBF043D1D for ; Sat, 21 Feb 2004 13:20:17 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i1LLKGbv063879 for ; Sat, 21 Feb 2004 13:20:16 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1LLKG7c063878; Sat, 21 Feb 2004 13:20:16 -0800 (PST) (envelope-from gnats) Resent-Date: Sat, 21 Feb 2004 13:20:16 -0800 (PST) Resent-Message-Id: <200402212120.i1LLKG7c063878@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, Hendrik Scholz Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 865E216A4E1; Sat, 21 Feb 2004 13:19:45 -0800 (PST) Received: from mail.atl.us.wormulon.net (unknown [63.223.8.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D08F43D1D; Sat, 21 Feb 2004 13:19:45 -0800 (PST) (envelope-from hscholz@slurmcan.wormulon.net) Received: from localhost (unknown [63.223.8.130]) by mail.atl.us.wormulon.net (Postfix) with ESMTP id 5517A5D878; Sat, 21 Feb 2004 16:20:22 -0500 (EST) Received: from mail.atl.us.wormulon.net ([63.223.8.130]) by localhost (plant.wormulon.net [63.223.8.130]) (amavisd-new, port 10024) with ESMTP id 53207-10; Sat, 21 Feb 2004 16:20:21 -0500 (EST) Received: from slurmcan.wormulon.net (unknown [63.223.7.6]) by mail.atl.us.wormulon.net (Postfix) with ESMTP id 4F0CF5D80B; Sat, 21 Feb 2004 16:20:21 -0500 (EST) Received: by slurmcan.wormulon.net (Postfix, from userid 1001) id F423939845; Sat, 21 Feb 2004 16:20:05 -0500 (EST) Message-Id: <20040221212005.F423939845@slurmcan.wormulon.net> Date: Sat, 21 Feb 2004 16:20:05 -0500 (EST) From: Hendrik Scholz To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 cc: freebsd-amd64@FreeBSD.org Subject: amd64/63188: ti(4) broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Hendrik Scholz List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 21:20:17 -0000 >Number: 63188 >Category: amd64 >Synopsis: ti(4) broken on amd64 >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: Sat Feb 21 13:20:16 PST 2004 >Closed-Date: >Last-Modified: >Originator: Hendrik Scholz >Release: FreeBSD 5.2.1-RC amd64 >Organization: >Environment: System: FreeBSD slurmcan.wormulon.net 5.2.1-RC FreeBSD 5.2.1-RC #0: Sat Jan 31 12:38:34 GMT 2004 root@ngoc.NUXI.com:/usr/obj/usr/src/sys/GENERIC amd64 >Description: ti0: mem 0xfc8bc000-0xfc8bffff irq 28 at device 1.0 on pci1 ti0: Ethernet address: 00:60:cf:20:6b:a6 (full dmesg at http://dump.wormulon.net/dmesg/MSI_K8D/dmesg.txt) $ ifconfig ti0 ti0: flags=8843 mtu 1500 options=1b inet6 fe80::260:cfff:fe20:6ba6%ti0 prefixlen 64 scopeid 0x1 inet 63.223.8.203 netmask 0xffffff00 broadcast 63.223.8.255 ether 00:60:cf:20:6b:a6 media: Ethernet autoselect (1000baseSX ) status: active TCP based protocols (ssh) work but scp is very slow and sometimes the connection is dropped due to bad packets. ICMP just misses a bunch of packets: $ ping 63.223.8.133 PING 63.223.8.133 (63.223.8.133): 56 data bytes 64 bytes from 63.223.8.133: icmp_seq=1 ttl=64 time=0.277 ms 64 bytes from 63.223.8.133: icmp_seq=3 ttl=64 time=0.200 ms .. 11 packets transmitted, 8 packets received, 27% packet loss round-trip min/avg/max/stddev = 0.200/0.260/0.316/0.039 ms $ Doing a tcpdump on the host itself reveals: 63.223.8.203 > 63.223.8.34: icmp: echo request (ttl 64, id 29322, len 84, bad cksum 0!) 63.223.8.34 > 63.223.8.203: icmp: echo reply (ttl 128, id 42958, len 84) truncated-ip - 70 bytes missing! 63.223.7.6.22 > 24.30.48.121.1921: P 4294962720:4294962784(64) ack 4294964481 win 33304 (DF) [tos 0x10] (ttl 64, id 29087, len 116, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 7760:7792(32) ack 1185 win 33304 (DF) [tos 0x10] (ttl 64, id 29247, len 84, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 7760:7792(32) ack 1185 win 33304 (DF) [tos 0x10] (ttl 64, id 29247, len 84, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 3808:3840(32) ack 289 win 33304 (DF) [tos 0x10] (ttl 64, id 28931, len 84, bad cksum 0!) truncated-ip - 38 bytes missing! 63.223.7.6.22 > 24.30.48.121.1850: P 4294959456:4294959488(32) ack 4294965025 win 33304 (DF) [tos 0x10] (ttl 64, id 28359, len 84, bad cksum 0!) the target sees this: 63.223.8.203 > 63.223.8.34: icmp: echo request (ttl 64, id 29269, len 84) 63.223.8.34 > 63.223.8.203: icmp: echo reply (ttl 128, id 42940, len 84, bad cksum 0!) 63.223.8.203 > 63.223.8.34: icmp: echo request (ttl 64, id 29272, len 84) 63.223.8.34 > 63.223.8.203: icmp: echo reply (ttl 128, id 42943, len 84, bad cksum 0!) ... bad chksum is ok since its a broadcom card with enabled TXCSUM: bge0: flags=8843 mtu 1500 options=1b inet 63.223.8.34 netmask 0xffffff00 broadcast 63.223.8.255 Let's get back to the first tcpdump: - received packets are missing data (arp is always ok!) - the bpf sees packets that belong to another interface $ route get 63.223.7.6 route to: unknown63223007006.ibis7.net destination: 63.223.7.0 mask: 255.255.255.224 interface: bge1 bge1 is used as main interface and the ssh session runs on this interface. - amount of missing data reported by tcpdump for packets from other interface are somewhat static: 6 (very uncommon), 38, 54, 70 Bytes (all for ssh PSH packets) - filtered traffic on host with ti(4): $ tcpdump -ntvi ti0 not arp and not host 63.223.7.6 (outgoing request and the matching incoming reply) 63.223.8.203 > 63.223.8.133: icmp: echo request (ttl 64, id 32019, len 84, bad cksum 0!) 85:54:6e:39:6e:e2 e1:72:44:af:9e:9d d67f 60: 06f0 381a ff4e cd44 c5f0 bef7 d65f f8b0 bf1d a26b 4b19 9ce1 ddb7 85ab fef3 6f09 c73e c2cf 2f04 a8da 0a85 c241 c9e2 16Bytes (MAC + MAC + 08:00) + 46 Bytes data = 62 Bytes The reply packet should be 84 Bytes long. I reproduced this problem on two different Opteron Systems running 5.2.1-RC/amd64 with two different ti cards (same Alteon type) and different cables. The same configuration runs fine on FreeBSD/i386. Hendrik >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 13:28:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EABE116A4CE; Sat, 21 Feb 2004 13:28:56 -0800 (PST) Received: from mail.wvfiber.com (mail.wvfiber.com [63.223.7.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id D244243D1D; Sat, 21 Feb 2004 13:28:56 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: by mail.wvfiber.com (Postfix, from userid 65534) id 4C1F037AED; Sat, 21 Feb 2004 16:28:56 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.wvfiber.com (Postfix) with ESMTP id B2E3437AF5; Sat, 21 Feb 2004 16:28:25 -0500 (EST) Received: from [10.0.1.2] (c-24-30-48-121.mw.client2.attbi.com [24.30.48.121]) by mail.wvfiber.com (Postfix) with ESMTP id 71C3C37AF0; Sat, 21 Feb 2004 16:28:25 -0500 (EST) In-Reply-To: <20040221212005.F423939845@slurmcan.wormulon.net> References: <20040221212005.F423939845@slurmcan.wormulon.net> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Hendrik Scholz Date: Sat, 21 Feb 2004 16:28:52 -0500 To: Hendrik Scholz X-Mailer: Apple Mail (2.612) X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-5.3 required=5.0 tests=AWL,BAYES_01,IN_REP_TO,REFERENCES,USER_AGENT_APPLEMAIL version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: FreeBSD-gnats-submit@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: ti(4) broken on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 21:28:57 -0000 Hi! On Feb 21, 2004, at 4:20 PM, Hendrik Scholz wrote: [...] > 16Bytes (MAC + MAC + 08:00) + 46 Bytes data = 62 Bytes Make that 14 Bytes for the ethernet header :) Sorry for the dupe, Hendrik -- Hendrik Scholz - hscholz@raisdorf.net - http://www.raisdorf.net/ cell phone: 404-606-5324 (US) 0160-1570-272 (DE) From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 13:41:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01DC316A4CE for ; Sat, 21 Feb 2004 13:41:47 -0800 (PST) Received: from mail.ebit.ca (ebit.ca [207.136.103.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id DED2343D1D for ; Sat, 21 Feb 2004 13:41:46 -0800 (PST) (envelope-from jason+lists.freebsd@lixfeld.ca) Received: from [192.168.100.66] (trek.lixfeld.ca [216.7.194.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.ebit.ca (Postfix) with ESMTP id 621CB3C8016; Sat, 21 Feb 2004 16:43:56 -0500 (EST) In-Reply-To: <200402211230.57825.peter@wemm.org> References: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> <200402211230.57825.peter@wemm.org> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jason Lixfeld Date: Sat, 21 Feb 2004 16:41:34 -0500 To: Peter Wemm X-Mailer: Apple Mail (2.613) cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 + Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 21:41:47 -0000 On Feb 21, 2004, at 3:30 PM, Peter Wemm wrote: > > Have a look at http://people.freebsd.org/~peter/ezm3-amd64/ > There are a mountain of diffs and hacks to try and get ezm3 to work > with gcc on amd64. There is enough there to enable you to produce the > same binary in the package you downloaded. ie: it will blow up with > that zlib error. Be sure to put the boot-ezm3-1.1-FBSD_AMD64.tar.bs2 > into your /usr/ports/distfiles/ezm3/ directory because its not in > John's dist area that the port knows about. One other thing: http://people.freebsd.org/~peter/ezm3-amd64/ has ezm3-1.1-FBSD_AMD64.tgz. The Makefile calls for ezm3-${PORTVERSION}-${TARGET}-boot.tar.bz2. Just change the Makefile to reflect the filename in ~peter, or am I looking in the wrong place for this file? From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 14:21:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD2AE16A4CE; Sat, 21 Feb 2004 14:21:26 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91C6943D1F; Sat, 21 Feb 2004 14:21:26 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B137C7303A; Sat, 21 Feb 2004 17:21:22 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040221222122.B137C7303A@freebsd-current.sentex.ca> Date: Sat, 21 Feb 2004 17:21:22 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 22:21:26 -0000 TB --- 2004-02-21 21:23:13 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-21 21:23:13 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-21 21:23:13 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-21 21:27:51 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> 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.. TB --- 2004-02-21 22:14:54 - building generic kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Feb 21 22:14:54 GMT 2004 >>> Kernel build for GENERIC completed on Sat Feb 21 22:21:21 GMT 2004 TB --- 2004-02-21 22:21:21 - generating LINT kernel config TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- /usr/bin/make -B LINT TB --- 2004-02-21 22:21:21 - building LINT kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Feb 21 22:21:21 GMT 2004 -------------------------------------------------------------- ===> LINT mkdir -p /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys cd /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf; PATH=/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/legacy/usr/games:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/sbin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/bin:/home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys/LINT /other/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf/LINT FYI: static unit limits for vcoda are set: NVCODA=4 config: Error: device "cy" is unknown config: 1 errors WARNING: kernel contains GPL contaminated ext2fs filesystem *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-21 22:21:22 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-21 22:21:22 - TB --- ERROR: failed to build lint kernel TB --- 2004-02-21 22:21:22 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 14:31:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD29516A4CE for ; Sat, 21 Feb 2004 14:31:03 -0800 (PST) Received: from mail.ebit.ca (ebit.ca [207.136.103.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5B7543D1D for ; Sat, 21 Feb 2004 14:31:03 -0800 (PST) (envelope-from jason+lists.freebsd@lixfeld.ca) Received: from [192.168.100.66] (trek.lixfeld.ca [216.7.194.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.ebit.ca (Postfix) with ESMTP id 67F4F3C8013; Sat, 21 Feb 2004 16:39:50 -0500 (EST) In-Reply-To: <200402211230.57825.peter@wemm.org> References: <5421F6D2-6446-11D8-8485-000A95989E4A@lixfeld.ca> <200402211230.57825.peter@wemm.org> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <249AC6EC-64B6-11D8-8485-000A95989E4A@lixfeld.ca> Content-Transfer-Encoding: 7bit From: Jason Lixfeld Date: Sat, 21 Feb 2004 16:37:26 -0500 To: Peter Wemm X-Mailer: Apple Mail (2.613) cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 + Ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 22:31:03 -0000 On Feb 21, 2004, at 3:30 PM, Peter Wemm wrote: > Have a look at http://people.freebsd.org/~peter/ezm3-amd64/ > There are a mountain of diffs and hacks to try and get ezm3 to work > with gcc on amd64. There is enough there to enable you to produce the > same binary in the package you downloaded. ie: it will blow up with > that zlib error. Be sure to put the boot-ezm3-1.1-FBSD_AMD64.tar.bs2 > into your /usr/ports/distfiles/ezm3/ directory because its not in > John's dist area that the port knows about. Thanks for the pointer. I applied the cvsup patch, no problem and tried to install the ezm3 patch but messed up and kept screwing with it to the point where the Makefile.orig no longer resembled the original from the distribution. I need to look around and find the original Makefile. How does one go about re-downloading the files for one single port? I'd use CVSUP, but... :) > As has been mentioned, don't use compress. I know this is a PITA, but > I > haven't figured out a way around it. The error code is 0xffffffffb > which is -5. For zlib, that translates to 'buffer error'. In other > words, the callback hooks for zlib in cvsup are not working right. I'd > welcome you to try and fix them. :-) Well, I would if I knew how to code! :) > -- > 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 Sat Feb 21 18:59:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB41916A4CE for ; Sat, 21 Feb 2004 18:59:18 -0800 (PST) Received: from mail-in-04.arcor-online.net (mail-in-04.arcor-online.net [151.189.21.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B9B043D1D for ; Sat, 21 Feb 2004 18:59:18 -0800 (PST) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (dsl-213-023-058-162.arcor-ip.net [213.23.58.162]) by mail-in-04.arcor-online.net (Postfix) with ESMTP id 1CF908F7C69 for ; Sun, 22 Feb 2004 03:59:17 +0100 (CET) Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.10/8.12.10) with ESMTP id i1M2xGhw092535 for ; Sun, 22 Feb 2004 03:59:16 +0100 (CET) (envelope-from mailnull@kemoauc.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.10/8.12.10/Submit) id i1M2xGQG092534 for freebsd-amd64@freebsd.org; Sun, 22 Feb 2004 03:59:16 +0100 (CET) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Sun, 22 Feb 2004 02:59:15 +0000 (UTC) Message-ID: References: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-amd64@freebsd.org Subject: Re: CFLAGS+= -fPIC per default? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2004 02:59:18 -0000 Hendrik Scholz wrote: > I'm just fixing a bunch of ports reported broken on amd64 by bento. > Most of these errors are related to a common linker problem: > ld: foo.o: relocation R_X86_64_32 can not be used when making a shared > object; recompile with -fPIC Why are these shared objects not built with -fPIC in the first place? -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 21 19:43:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF58A16A4CE for ; Sat, 21 Feb 2004 19:43:40 -0800 (PST) Received: from mail.wvfiber.com (mail.wvfiber.com [63.223.7.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id C623943D2D for ; Sat, 21 Feb 2004 19:43:40 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: by mail.wvfiber.com (Postfix, from userid 65534) id 2AC2530282; Sat, 21 Feb 2004 22:43:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.wvfiber.com (Postfix) with ESMTP id 7C01C3769A for ; Sat, 21 Feb 2004 22:43:09 -0500 (EST) Received: from [10.0.1.2] (c-24-30-48-121.mw.client2.attbi.com [24.30.48.121]) by mail.wvfiber.com (Postfix) with ESMTP id 41BBD30282 for ; Sat, 21 Feb 2004 22:43:09 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4CC57F17-64E9-11D8-ACAA-000A95BAD088@raisdorf.net> Content-Transfer-Encoding: 7bit From: Hendrik Scholz Date: Sat, 21 Feb 2004 22:43:38 -0500 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.612) X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-5.8 required=5.0 tests=AWL,BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_APPLEMAIL autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: CFLAGS+= -fPIC per default? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2004 03:43:41 -0000 On Feb 21, 2004, at 9:59 PM, Christian Weisgerber wrote: > Why are these shared objects not built with -fPIC in the first place? Ask the authors of the third party applications :) Most architectures don't need -fPIC and/or it slows them down (thanks for the comment Peter!). The ports I've dealt with either use a hand written Makefile without honoring CFLAGS set in the environment or without having -fPIC set since i386 (I guess that is what most of the guys test and run their stuff on) doesn't need it. Ports utilizing GNU configure may check if -fPIC is supported but usually don't set it since it's not needed on the developers system. Btw: Just found this in man gcc on Mac OS 10.3: -fPIC If supported for the target machine, emit position-independent code, suitable for dynamic linking and avoiding any limit on the size of the global offset table. This option makes a difference on the m68k, m88k, and the SPARC. Position-independent code requires special support, and therefore works only on certain machines. -fPIC is the default on Darwin and Mac OS X. This might be the reason why I didn't see all the -fPIC patches in darwinports. Hendrik -- Hendrik Scholz - hscholz@raisdorf.net - http://www.raisdorf.net/ cell phone: 404-606-5324 (US) 0160-1570-272 (DE)