From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 2 17:35:04 2003 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 7084116A4CE for ; Tue, 2 Dec 2003 17:35:04 -0800 (PST) Received: from oak.FernUni-Hagen.de (oak.fernuni-hagen.de [132.176.114.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5188343FD7 for ; Tue, 2 Dec 2003 17:35:03 -0800 (PST) (envelope-from q5480035@mailstore.FernUni-Hagen.de) Received: from amavis by oak.FernUni-Hagen.de with scanned-ok (Exim 4.04) id 1ARLuw-0000fC-00 for freebsd-amd64@freebsd.org; Wed, 03 Dec 2003 02:35:02 +0100 Received: from mailstore.fernuni-hagen.de ([132.176.114.185]) by oak.FernUni-Hagen.de with esmtp (Exim 4.04) id 1ARLup-0000ej-00 for freebsd-amd64@freebsd.org; Wed, 03 Dec 2003 02:34:55 +0100 Received: from [217.0.105.7] (account q5480035 HELO oranje.my.domain) by mailstore.fernuni-hagen.de (CommuniGate Pro SMTP 4.0.6) with ESMTP id 2960503 for freebsd-amd64@FreeBSD.org; Wed, 03 Dec 2003 02:34:54 +0100 To: freebsd-amd64@FreeBSD.org References: <200312030008.hB308MdX094585@freefall.freebsd.org> Message-ID: From: Marc van Woerkom Organization: =?iso-8859-1?Q?FernUniversit=E4t_in_Hagen?= Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <200312030008.hB308MdX094585@freefall.freebsd.org> User-Agent: Opera7.23/FreeBSD M2 build 516 X-Virus-Scanned: by AMaViS perl-11 Subject: Cheap amd64 system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Wed, 03 Dec 2003 01:35:04 -0000 X-Original-Date: Wed, 03 Dec 2003 02:34:14 +0100 X-List-Received-Date: Wed, 03 Dec 2003 01:35:04 -0000 Hi, I would love to join development, is there cheap hardware available already? E.g. is it possible to take my old amd-k7 box and just replace mainboard and perhaps ram to have a usable amd64 system? How much money must I save at least? Is it necessary to put in more than 4gigs of RAM, to test the system adequatley? Regards, Marc From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 27 13:03:07 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 DC60816A4CE for ; Tue, 27 Jan 2004 13:03:07 -0800 (PST) Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id B331B43D46 for ; Tue, 27 Jan 2004 13:02:27 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with asmtp (Exim 4.30) id 1AlaKP-0006BV-PH; Tue, 27 Jan 2004 22:00:57 +0100 Received: from gef79.g.pppool.de ([80.185.239.121] helo=peedub.jennejohn.org) by mx3.freenet.de with esmtp (TLSv1:AES256-SHA:256) (Exim 4.30 #3) id 1AlaKO-0005uZ-Pt; Tue, 27 Jan 2004 22:00:57 +0100 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id i0RL0tFw006309; Tue, 27 Jan 2004 22:00:55 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200401272100.i0RL0tFw006309@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Marc van Woerkom In-Reply-To: Message from Marc van Woerkom Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jan 2004 22:00:55 +0100 From: Gary Jennejohn cc: freebsd-amd64@FreeBSD.org Subject: Re: Cheap amd64 system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 21:03:08 -0000 Marc van Woerkom writes: > I would love to join development, is there cheap hardware > available already? > Depends on what you buy. Cheap is a socket 754 box with an AMD64 3000+ (only 512MB of cache and 2GHz clock). > E.g. is it possible to take my old amd-k7 box and > just replace mainboard and perhaps ram to have > a usable amd64 system? > That's what I did. In fact, I'm still using some of my old PC2100 RAM in the box since the Infineon DDR400 DIMM I bought runs at CL3 and is slow as molasses. I did some tests and noticed only a few percentage points speed increase using the Infineon DIMM by itself. Since I wanted more memory I just stuck an old DIMM in with the new one. > How much money must I save at least? > I also had to buy a new power supply since my old one didn't have the funky 4-pole connector on it which all modern motherboards seem to require (AFAIK mostly to support the ridiculously power-hungry graphics cards which no normal person would want to use anyway). I payed about 450 Euros a few weeks ago for mobo, CPU and PSU. YMMV. > Is it necessary to put in more than 4gigs of RAM, > to test the system adequatley? > No. What really needs work, like 32 bit emulation, doesn't require a lot of memory. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:13: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 4B79516A4CE for ; Thu, 29 Jan 2004 05:13:24 -0800 (PST) Received: from tor-adm1.nbc.attcanada.ca (tor-adm1.business.allstream.net [207.181.89.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00C4443D5A for ; Thu, 29 Jan 2004 05:13:18 -0800 (PST) (envelope-from taob@risc.org) Received: from tor-adm1.nbc.attcanada.ca (localhost [127.0.0.1]) i0TDDGwH026372 for ; Thu, 29 Jan 2004 08:13:16 -0500 (EST) Received: from localhost (ncc0070@localhost)i0TDDGKF026369 for ; Thu, 29 Jan 2004 08:13:16 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.attcanada.ca: ncc0070 owned process doing -bs Date: Thu, 29 Jan 2004 08:13:16 -0500 (EST) From: Brian Tao X-Sender: ncc0070@tor-adm1.nbc.attcanada.ca To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: New AMD64 owner 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, 29 Jan 2004 13:13:24 -0000 First time posting to this list, although I've been running FreeBSD since the 1.1.5.1/2.0 days. After four years without a decent workstation at home, I finally took delivery of a dual Opteron 244 Tyan Tiger K8W system. I've got a few questions that I think I have the answers to, but wanted to confirm I'm going down the right path, since this architecture is still pretty new. AMD64 CPU's are supposed to have "seamless" backwards compatibility with 32-bit x86 code... I've confirmed this by watching Windows 98 boot up on my new system (it was what the integrator had installed to do some burn-in testing, presumably). If this is the case, why am I seeing references to broken ia32 compatibility? Shouldn't that "just work"? Or is this a kernel/loader issue with a 64-bit aware install? Related to the previous question: should I be able to install either freebsd-i386 or freebsd-amd64, and both will work? Obviously the i386 install will run in 32-bit mode, but at least it will run (and act as a really fast Intel box, I'm hoping). Or is there something inherent in the kernel or boot process that forces me to run freebsd-amd64, and cannot utilize the 32-bit compatibility of the CPU? The Tyan motherboard has an onboard Silicon Image 3114 S-ATA adapter. I have two WD Raptor drives attached. The aforementioned Windows 98 appears to boot and recognize the drives just fine (this is only booting to the command prompt, so there are no third-party drivers being loaded, AFAICT). This leads me to believe that the BIOS or the S-ATA adapter itself is able to dumb itself down to look like a normal IDE drive. However, when I tried to boot the 5.2-RELEASE installer, it was not able to find any drives. I noticed that Soren recently committed a change to support the 3114's, but that doesn't help me if I can't get FreeBSD on the damn disks in the first place. ;-) So I popped over to current.freebsd.org to see if I could grab a newer ISO (post-Jan 17) with the right SATA drivers. Latest successful build is Jan 24, so I'm hoping that will work. I don't see an amd64 directory tree there though, which goes back to my earlier question about doing an i386 binary install on an amd64 platform. Is it possible to subsequently do a source build upgrade to amd64? Or do we not have the tools to do that yet? Thanks for your patience... I'm looking forward to helping improve freebsd-amd64! -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:26:17 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 3213F16A4CE for ; Thu, 29 Jan 2004 05:26:17 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A09AB43D39 for ; Thu, 29 Jan 2004 05:26:00 -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 i0TDPwZk027942; Thu, 29 Jan 2004 14:25:59 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Thu, 29 Jan 2004 14:23:31 +0100 User-Agent: KMail/1.6.50 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200401291423.13666.adridg@cs.kun.nl> Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: New AMD64 owner 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, 29 Jan 2004 13:26:17 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 29 January 2004 14:13, Brian Tao wrote: > installed to do some burn-in testing, presumably). If this is the > case, why am I seeing references to broken ia32 compatibility? > Shouldn't that "just work"? Or is this a kernel/loader issue with a > 64-bit aware install? It's a kernel/loader issue, mostly. The stack layout is very different in 64 bit mode than in 32 bit mode (or so I gather from messages from DAvid & James). This means that when running 32 bit apps, the stack needs to be treated differently, and the kernel doesn't do that right (yet). > Related to the previous question: should I be able to install > either freebsd-i386 or freebsd-amd64, and both will work? Obviously Well, i386 will work. amd64 YMMV. > the i386 install will run in 32-bit mode, but at least it will run > (and act as a really fast Intel box, I'm hoping). Or is there It's been said several times on this list that running an amd64 as an i386 works quite well and _is_ really fast. I can't confirm that, though. > The Tyan motherboard has an onboard Silicon Image 3114 S-ATA > adapter. I have two WD Raptor drives attached. The aforementioned SATA seems to be the primary source of woe on this list right now. Check the archives a little. For me, with a consumer-grade asus k8v, everything just worked. - -- pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot If the door is ajar, can we fill it with door-jamb? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAGQlTdqzuAf6io/4RAnAqAJ0cE6YtQ99gbh1wfDxnN0kjaJ1lhwCfTzbh saxmorQNUDjbEFNFY2eSMNc= =dED6 -----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:31: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 2DC0D16A4CE for ; Thu, 29 Jan 2004 05:31:26 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0344643D62 for ; Thu, 29 Jan 2004 05:31:11 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id IAA05523 for ; Thu, 29 Jan 2004 08:31:11 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Thu, 29 Jan 2004 08:30:03 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Thu, 29 Jan 2004 08:30:02 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: New AMD64 owner 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, 29 Jan 2004 13:31:26 -0000 What about the ACPI issues? I emailed about those a few days ago, and I have seen other questions, too. Are these a real problem, or am I too concerned? Tom -----Original Message----- From: Adriaan de Groot [mailto:adridg@cs.kun.nl] Sent: 29 January, 2004 08:24 To: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner SATA seems to be the primary source of woe on this list right now. Check the archives a little. For me, with a consumer-grade asus k8v, everything just worked. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:35: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 E955C16A4CE for ; Thu, 29 Jan 2004 05:35:26 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4019043D39 for ; Thu, 29 Jan 2004 05:35:25 -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 i0TDZOZk000553; Thu, 29 Jan 2004 14:35:24 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Thu, 29 Jan 2004 14:35:20 +0100 User-Agent: KMail/1.6.50 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200401291435.21000.adridg@cs.kun.nl> Subject: Re: ACPI errors in dmesg.boot 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, 29 Jan 2004 13:35:27 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 25 January 2004 22:25, Haapanen, Tom wrote: > I now have the server successfully running 5.2-RELEASE, and at least basic > things look to be working fine. However, dmesg.boot shows a lot of ACPI > errors (see end of message). Should I turn off ACPI somewhere? Ignore t= he > errors? Do something else? > acpi0: on motherboard > ACPI-1287: *** Error: Method execution failed > [\\_SB_.PCI0.SBRG.HPET._STA <\\_SB_.PCI0.SBRG.HPET._STA> ] (Node > 0xffffff0000c26d80), AE_AML_REGION_LIMIT > ACPI-0175: *** Error: Method execution failed I used to get all kinds of ACPI errors when this system was new(november).= =20 They never caused any harm as far as I could tell, and their number has=20 decreased while following -CURRENT, until no the only one left is: pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 -=20 AE_NOT_FOUND I don't think it's much to worry about. But then, I'm on consumer-grade amd= 64=20 working on KDE, not the heavy stuff. =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot If the door is ajar, can we fill it with door-jamb? =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAGQwYdqzuAf6io/4RAuuXAJ9Z3jCqyiPR6jDzM2Qp7DUEfBVY/wCfQBsU zo+eqkZaucsjEUqpdF0zmaY=3D =3DM69J =2D----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:38: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 18EDB16A4CE for ; Thu, 29 Jan 2004 05:38:33 -0800 (PST) Received: from tor-adm1.nbc.attcanada.ca (tor-adm1.business.allstream.net [207.181.89.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF62443D3F for ; Thu, 29 Jan 2004 05:38:31 -0800 (PST) (envelope-from taob@risc.org) Received: from tor-adm1.nbc.attcanada.ca (localhost [127.0.0.1]) i0TDcSwH026976; Thu, 29 Jan 2004 08:38:28 -0500 (EST) Received: from localhost (ncc0070@localhost)i0TDcRMI026973; Thu, 29 Jan 2004 08:38:27 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.attcanada.ca: ncc0070 owned process doing -bs Date: Thu, 29 Jan 2004 08:38:27 -0500 (EST) From: Brian Tao X-Sender: ncc0070@tor-adm1.nbc.attcanada.ca To: Adriaan de Groot In-Reply-To: <200401291423.13666.adridg@cs.kun.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner 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, 29 Jan 2004 13:38:33 -0000 On Thu, 29 Jan 2004, Adriaan de Groot wrote: > > It's a kernel/loader issue, mostly. The stack layout is very > different in 64 bit mode than in 32 bit mode (or so I gather from > messages from DAvid & James). This means that when running 32 bit > apps, the stack needs to be treated differently, and the kernel > doesn't do that right (yet). Right, so really more of an issue on our side having kernel/loader functionality catch up to what the hardware should be capable of. > It's been said several times on this list that running an amd64 as > an i386 works quite well and _is_ really fast. I can't confirm that, > though. That's great... I don't *need* a 64-bit environment right now, but I figured since I'm dropping the cash on a system like this, I better buy something that'll last me a few years... okay, i386 it is then, at least for now. > SATA seems to be the primary source of woe on this list right now. > Check the archives a little. For me, with a consumer-grade asus k8v, > everything just worked. Soren committed a 3114-related patch to the atapci stuff very recently (like less than 2 weeks ago, I think), so I'll have to investigate that. I suppose at the very least, I can hook up any old IDE drive, install/boot from that, then look at getting the SATA stuff working. Thanks for your comments. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:42: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 ACEAE16A4CE for ; Thu, 29 Jan 2004 05:42:47 -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 F238543D4C for ; Thu, 29 Jan 2004 05:42:45 -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 i0TDgio8009656 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 29 Jan 2004 07:42:44 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i0TDgipC009653; Thu, 29 Jan 2004 07:42:44 -0600 (CST) Date: Thu, 29 Jan 2004 07:42:44 -0600 (CST) Message-Id: <200401291342.i0TDgipC009653@bigtex.jrv.org> From: James Van Artsdalen To: tomh@waterloo.equitrac.com In-reply-to: (tomh@waterloo.equitrac.com) References: cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner 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, 29 Jan 2004 13:42:47 -0000 > From: "Haapanen, Tom" > Date: Thu, 29 Jan 2004 08:30:02 -0500 > > What about the ACPI issues? I emailed about those a few days ago, and I > have seen other questions, too. Are these a real problem, or am I too > concerned? I have been ignoring these for a couple of months and have not been struck down by lightning from above. There have been reports of a couple of devices not working that sounded to me like potential IOAPIC/IRQ/etc mapping problems caused by using bad data from ACPI tables (whether the BIOS had a bogus table or FreeBSD a bogus parser is unknown to me). This is rare. In short, if it seems to work, it probably does. If it doesn't work, try turning off ACPI in the BIOS. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 05:46:22 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 DF45016A4CE for ; Thu, 29 Jan 2004 05:46:22 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DC4843D1D for ; Thu, 29 Jan 2004 05:46:20 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id IAA06116 for ; Thu, 29 Jan 2004 08:46:19 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Thu, 29 Jan 2004 08:45:12 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Thu, 29 Jan 2004 08:45:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: New AMD64 owner 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, 29 Jan 2004 13:46:23 -0000 Is there any real downside in turning off ACPI? Especially for a server that will be running 24x7? Tom -----Original Message----- From: James Van Artsdalen [mailto:james-freebsd-amd64@jrv.org] Sent: 29 January, 2004 08:43 To: tomh@waterloo.equitrac.com Cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner > From: "Haapanen, Tom" > Date: Thu, 29 Jan 2004 08:30:02 -0500 > > What about the ACPI issues? I emailed about those a few days ago, and > I have seen other questions, too. Are these a real problem, or am I > too concerned? I have been ignoring these for a couple of months and have not been struck down by lightning from above. There have been reports of a couple of devices not working that sounded to me like potential IOAPIC/IRQ/etc mapping problems caused by using bad data from ACPI tables (whether the BIOS had a bogus table or FreeBSD a bogus parser is unknown to me). This is rare. In short, if it seems to work, it probably does. If it doesn't work, try turning off ACPI in the BIOS. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 06:04: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 35E1E16A4CE for ; Thu, 29 Jan 2004 06:04:18 -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 3D14A43D3F for ; Thu, 29 Jan 2004 06:04:13 -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 i0TE4Co8010297 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 29 Jan 2004 08:04:12 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i0TE4Co1010294; Thu, 29 Jan 2004 08:04:12 -0600 (CST) Date: Thu, 29 Jan 2004 08:04:12 -0600 (CST) Message-Id: <200401291404.i0TE4Co1010294@bigtex.jrv.org> From: James Van Artsdalen To: tomh@waterloo.equitrac.com In-reply-to: (tomh@waterloo.equitrac.com) References: cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner 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, 29 Jan 2004 14:04:18 -0000 > From: "Haapanen, Tom" > Date: Thu, 29 Jan 2004 08:45:11 -0500 > > Is there any real downside in turning off ACPI? Especially for a server > that will be running 24x7? If it seems to work then turning off ACPI has no important downside. "Seems to work" means that you can access a disk drive or talk over a network: I don't expect any subtle failure modes. My familiarity with this is from the BIOS side, and about five years old, but I think FreeBSD can get all of the data it needs to configure the IRQ/IOAPIC from the MP tables. ACPI probably isn't required. The bigger question is whether the MP table data is reliable. I believe Windows uses ACPI exclusively if available, so once BIOS vendor X has ACPI everything else becomes untested and unreliable. (vendors generally don't test anything the current version of Windows doesn't use, so ACPI in FreeBSD is preferred even if theoretically unnecessary). I see no reason not to deploy a FreeBSD/AMD64 server right now, after the hardware is burned in, and if all of the apps run 64-bit. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 07:10: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 E3E4816A4CE for ; Thu, 29 Jan 2004 07:10:39 -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 135E943D1D for ; Thu, 29 Jan 2004 07:10:37 -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 i0TFAao8012286 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 29 Jan 2004 09:10:36 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i0TFAZU3012283; Thu, 29 Jan 2004 09:10:35 -0600 (CST) Date: Thu, 29 Jan 2004 09:10:35 -0600 (CST) Message-Id: <200401291510.i0TFAZU3012283@bigtex.jrv.org> From: James Van Artsdalen To: taob@risc.org In-reply-to: (message from Brian Tao on Thu, 29 Jan 2004 08:13:16 -0500 (EST)) References: cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner 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, 29 Jan 2004 15:10:40 -0000 > Date: Thu, 29 Jan 2004 08:13:16 -0500 (EST) > From: Brian Tao > AMD64 CPU's are supposed to have "seamless" backwards > compatibility with 32-bit x86 code... I've confirmed this by watching > Windows 98 boot up on my new system (it was what the integrator had > installed to do some burn-in testing, presumably). If this is the > case, why am I seeing references to broken ia32 compatibility? > Shouldn't that "just work"? Or is this a kernel/loader issue with a > 64-bit aware install? The AMD64 processors start up in an Intel x86 compatible mode. If nobody puts it in 64-bit mode then it will stay x86 compatible. Once FreeBSD puts the processor in 64-bit mode things are a little different. Now 32-bit must be run with special provisions. The situation is very analogous to the early 32-bit operating systems running 16-bit software. I'm not sure what the issues blocking 32-bit software in FreeBSD/AMD64 are. The kernel needs a 32-bit syscall & thunk layer, various kernel calls need to know about the constricted address space, the loader and shared lib linker need to know, and the build process needs to know to compile both 32-bit and 64-bit versions of the shared libraries, etc. There are a lot of details. Some are no doubt done: I don't know if Peter has given a status report or stated where others might be able to help. > Related to the previous question: should I be able to install > either freebsd-i386 or freebsd-amd64, and both will work? Obviously > the i386 install will run in 32-bit mode, but at least it will run > (and act as a really fast Intel box, I'm hoping) Yes, either work, and as an x86 it is as fast as any Intel x86. It is a myth that AMD64 competes with the Itanic. That is beside the point. The AMD64 chips are designed to beat the Xeon and Pentiums, because that is where the money is. There is no money to be made by building a chip that sinks Itanic, but there certainly is by beating Xeon/P-4, and AMD knows it. A lot of AMD64 architecture tradeoffs are best understood by realizing that AMD64 is focused squarely on Intel's 32-bit market, with any 64-bit/server wins icing on the cake but not the site of the real battle for a profit. Nowhere that I know of has AMD sacrificed 32-bit functionality or performance to get even one iota of 64-bit advantage. (for that matter having 64-bit pointers and integers is minor to me compared to adding the extra int & float registers) > The Tyan motherboard has an onboard Silicon Image 3114 S-ATA > adapter. I have two WD Raptor drives attached. The aforementioned > Windows 98 appears to boot and recognize the drives just fine (this is > only booting to the command prompt, so there are no third-party > drivers being loaded, AFAICT). This leads me to believe that the BIOS > or the S-ATA adapter itself is able to dumb itself down to look like a > normal IDE drive. Win9x is probably booting in compatibility mode. There is some magic called the Real Mode Mapper that switches the processor back to real mode, does BIOS calls in real mode, and then switches back to protected mode. In any case, testing Win9x in this way doesn't really tell you anything about a disk controller with an option ROM unless you look carefully to see how Win9x is accessing the drive. > Is it possible to subsequently do a source build upgrade to amd64? > Or do we not have the tools to do that yet? I think Peter has said he has no plans to try to do an upgrade-in-place from a 32-bit to 64-bit FreeBSD environment. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 08:56: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 3261416A4CE for ; Thu, 29 Jan 2004 08:56:40 -0800 (PST) Received: from convex.cs.unb.ca (convex.cs.unb.ca [131.202.244.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5775C43D1D for ; Thu, 29 Jan 2004 08:56:34 -0800 (PST) (envelope-from bremner-dated-1076000193.ff74f5@convex.cs.unb.ca) Received: from bremner by convex.cs.unb.ca with local (Exim 4.24; FreeBSD) id 1AmFSz-0007CP-Ij for freebsd-amd64@freebsd.org; Thu, 29 Jan 2004 12:56:33 -0400 Received: by convex.cs.unb.ca (tmda-sendmail, from uid 1266); Thu, 29 Jan 2004 12:56:33 -0400 (AST) Received: from bremner (helo=convex.cs.unb.ca.unb.ca) by convex.cs.unb.ca with local-esmtp (Exim 4.24; FreeBSD) id 1AmFSy-0007CG-PP for freebsd-amd64@freebsd.org; Thu, 29 Jan 2004 12:56:32 -0400 Date: Thu, 29 Jan 2004 12:56:32 -0400 Message-ID: <0tvfmu3d8f.wl@nohost.unb.ca> To: freebsd-amd64@freebsd.org References: <0twu7e8w51.wl@nohost.unb.ca> User-Agent: SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: message/rfc822 From: David Bremner X-Delivery-Agent: TMDA/0.87 (Carry Back) X-TMDA-Fingerprint: 4u5GLoR/6k0yIp69LOH9r1vT/Xs X-Primary-Address: bremner@unb.ca X-Tmda-Bare: David Bremner Sender: David Bremner Subject: Forward: perl 5 extensions on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Bremner List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 16:56:40 -0000 Envelope-to: bremner@convex.cs.unb.ca Delivery-date: Mon, 26 Jan 2004 13:20:52 -0400 Delivered-To: freebsd-ports@freebsd.org Date: Mon, 26 Jan 2004 13:20:10 -0400 Message-ID: <0twu7e8w51.wl@nohost.unb.ca> To: freebsd-ports@freebsd.org User-Agent: SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 14) (Reasonable Discussion) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII From: David Bremner X-Delivery-Agent: TMDA/0.87 (Carry Back) X-TMDA-Fingerprint: Xnv+dsPt6mXLgQFuZixBYBMxIGk X-Primary-Address: bremner@unb.ca Subject: perl 5 extensions on AMD64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Bremner List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: owner-freebsd-ports@freebsd.org Errors-To: owner-freebsd-ports@freebsd.org X-UNB-MailScanner-Information: Please contact the ISP for more information X-UNB-VirusScanner: Found to be clean X-UNB-SpamDetails: not spam, SpamAssassin (score=0, required 5) I have just discovered (Hi Kris!) that a port I made does not work on AMD64 A quick look at the bento error logs reveals several p5-* ports with the same fatal error c -O -pipe -fpic -DPIC -shared -Wl,-x,-soname,libplperl.so.0 plperl.o eloglvl.o SPI.o -L../../../src/port -Wl,-E -L/usr/local/lib /usr/local/lib/perl5/5.6.1/mach/auto/DynaLoader/DynaLoader.a -L/usr/local/lib/perl5/5.6.1/mach/CORE -lperl -lm -lc -lcrypt -lutil -R/usr/local/lib -o libplperl.so.0 /usr/bin/ld: /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a(perl.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a: could not read symbols: Bad value gmake: *** [libplperl.so.0] Error 1 gmake: Leaving directory `/tmp/a/ports/databases/p5-postgresql-plperl/work/postgresql-7.4.1/src/pl/plperl' *** Error code 2 To this non-expert observer, that suggest that the perl 5 extension mechanism is not working write on AMD64. Can anyone point to a p5-* port, that 1) works on AMD64 2) makes a shared library for an extension. (oh, same question for IA64 I guess, although I have not trawled the logs). _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 09:09:07 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 1A63916A4CE for ; Thu, 29 Jan 2004 09:09:07 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id C415C43D41 for ; Thu, 29 Jan 2004 09:09:05 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id MAA14706 for ; Thu, 29 Jan 2004 12:09:05 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Thu, 29 Jan 2004 12:07:58 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Thu, 29 Jan 2004 12:07:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: RE: Forward: perl 5 extensions 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: Thu, 29 Jan 2004 17:09:07 -0000 A number of perl5 modules, including DBI and DBD::mysql, use shared libraries. I installed these from CPAN, and they are working fine on my amd64 system. Tom From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 10:54:30 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 D287616A4CE for ; Thu, 29 Jan 2004 10:54:30 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7186A43D2F for ; Thu, 29 Jan 2004 10:54:27 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0TIsQA0093437; Thu, 29 Jan 2004 10:54:26 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0TIsQip093436; Thu, 29 Jan 2004 10:54:26 -0800 (PST) (envelope-from obrien) Date: Thu, 29 Jan 2004 10:54:26 -0800 From: "David O'Brien" To: Brian Tao Message-ID: <20040129185426.GA93242@dragon.nuxi.com> References: 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: New AMD64 owner 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: Thu, 29 Jan 2004 18:54:31 -0000 On Thu, Jan 29, 2004 at 08:13:16AM -0500, Brian Tao wrote: > AMD64 CPU's are supposed to have "seamless" backwards > compatibility with 32-bit x86 code... I've confirmed this by watching > Windows 98 boot up on my new system (it was what the integrator had > installed to do some burn-in testing, presumably). If this is the > case, why am I seeing references to broken ia32 compatibility? > Shouldn't that "just work"? Or is this a kernel/loader issue with a > 64-bit aware install? It is a CPU mode issue. If you think back to your brand new i386 and Windows 95, the CPU was switched back into real mode when you ran a MS-Windows 3.1 program. Along with MS-Windows 95 doing "Thunking" for system services. The "seemless" in AMD64 is the same that you saw when the i386 first came out -- it ran 16-bit Real Mode code just fine. In fact it was the fastest 16-bit x86 machine in the world at the time. Simply extend that again to 64-bit and you get the idea behind AMD64. So now the issue you're refering to is how can one run 32-bit code under a 64-bit OS. Issues are that the kernel must support system calls being made by these 32-bit programs -- so one needs syscall translation. If you look at the function call ABI between 32-bit x64 and AMD64 you'll see how things are very different and have to converted from one to the other. Same reason you can't just run a Linux 32-bit x86 binary under FreeBSD/i386 before someone wrote the /sys/compat/linux bits which handle system call translation and other things that are specific to Linux and different from FreeBSD. > Related to the previous question: should I be able to install > either freebsd-i386 or freebsd-amd64, and both will work? Yes -- assuming you are talking about dual-booting. My FreeBSD/i386 build machine is actually an Athlon64 machine that is run purely and only in 32-bit mode. Athlon64 is the fastest 32-bit x86 machine in the world today. > the i386 install will run in 32-bit mode, but at least it will run > (and act as a really fast Intel box, I'm hoping). Correct. > Or is there > something inherent in the kernel or boot process that forces me to run > freebsd-amd64, and cannot utilize the 32-bit compatibility of the CPU? You are mixing machine capabilities, with OS capabilities. Please think back to the 8088/80286 -> i386 transition. > normal IDE drive. However, when I tried to boot the 5.2-RELEASE > installer, it was not able to find any drives. I noticed that Soren > recently committed a change to support the 3114's, but that doesn't > help me if I can't get FreeBSD on the damn disks in the first place. ;-) I will make a new snapshot w/in a week that will have SoS's Si3114 change in it. > Is it possible to subsequently do a source build upgrade to amd64? Or > do we not have the tools to do that yet? No, not at this time. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 11:02: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 76EF416A4CE for ; Thu, 29 Jan 2004 11:02:52 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB5C343D1F for ; Thu, 29 Jan 2004 11:02:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0TJ2nA0093609; Thu, 29 Jan 2004 11:02:50 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0TJ2npn093608; Thu, 29 Jan 2004 11:02:49 -0800 (PST) (envelope-from obrien) Date: Thu, 29 Jan 2004 11:02:48 -0800 From: "David O'Brien" To: James Van Artsdalen Message-ID: <20040129190248.GC93242@dragon.nuxi.com> References: <200401291510.i0TFAZU3012283@bigtex.jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401291510.i0TFAZU3012283@bigtex.jrv.org> 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: New AMD64 owner 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: Thu, 29 Jan 2004 19:02:52 -0000 On Thu, Jan 29, 2004 at 09:10:35AM -0600, James Van Artsdalen wrote: > The AMD64 processors start up in an Intel x86 compatible mode. > If nobody puts it in 64-bit mode then it will stay x86 compatible. Not quite, unless you call the Intel i386 (and Pentium's) as x86 compatible. All this is simply operating modes: 16-bit real mode, 32-bit real mode (used by the BIOS), 32-bit protected mode; and now added to the list is 64-bit protected mode. > Yes, either work, and as an x86 it is as fast as any Intel x86. Faster. 8-) > A lot of AMD64 architecture tradeoffs are best understood by realizing > that AMD64 is focused squarely on Intel's 32-bit market, with any > 64-bit/server wins icing on the cake but not the site of the real > battle for a profit. Not quite -- AMD definitely wants to penetrate the 64-bit data center market. BUT, AMD isn't walking away from the markets Athlon already plays in. > Nowhere that I know of has AMD sacrificed 32-bit > functionality or performance to get even one iota of 64-bit advantage. Correct. > Win9x is probably booting in compatibility mode. There is some magic > called the Real Mode Mapper that switches the processor back to real > mode, does BIOS calls in real mode, and then switches back to > protected mode. In any case, testing Win9x in this way doesn't really > tell you anything about a disk controller with an option ROM unless > you look carefully to see how Win9x is accessing the drive. Correct. If you try to install MS-Win64, you'd have to go find an Si3114 driver. Win 9x "cheats" as it is still a 16-bit OS that can do BIOS calls at the very lowest core. > I think Peter has said he has no plans to try to do an upgrade-in-place > from a 32-bit to 64-bit FreeBSD environment. It all depends on what someone commits to the 'make world' mechanism. It is all of our choice to make this work as is anything else in FreeBSD'ville. The question is who has the "itch" and will spend the effort to "scratch" it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 11: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 2C4F016A4CF for ; Thu, 29 Jan 2004 11:33:08 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B5F343D55 for ; Thu, 29 Jan 2004 11:32:54 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0TJWmA0094143; Thu, 29 Jan 2004 11:32:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0TJWmT7094142; Thu, 29 Jan 2004 11:32:48 -0800 (PST) (envelope-from obrien) Date: Thu, 29 Jan 2004 11:32:48 -0800 From: "David O'Brien" To: Paul Sturm Message-ID: <20040129193248.GF93242@dragon.nuxi.com> References: <000601c3e282$0aefcf20$efaf4b44@paulsapt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c3e282$0aefcf20$efaf4b44@paulsapt> 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: K8S Pro/Adaptec 2100S panic 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: Thu, 29 Jan 2004 19:33:08 -0000 On Sat, Jan 24, 2004 at 07:57:44AM -0600, Paul Sturm wrote: > I am experiencing the same problem with the Adaptec 2015S ZCR RAID. asr > works fine in the 32 bit builds (4.9 and 5.2). I don't quite follow you. You are using the 2015S ZCR in 32-bit or 64-bit FreeBSD? It should work with FreeBSD/i386 on Opteron HW. asr(4) isn't 64-bit clean and thus asr(4) devices aren't supported in the FreeBSD/amd64 OS. From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 29 14:21:00 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 E99B416A4CE; Thu, 29 Jan 2004 14:21:00 -0800 (PST) Received: from tor-adm1.nbc.attcanada.ca (tor-adm1.business.allstream.net [207.181.89.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE1A43D58; Thu, 29 Jan 2004 14:20:59 -0800 (PST) (envelope-from taob@risc.org) Received: from tor-adm1.nbc.attcanada.ca (localhost [127.0.0.1]) i0TMKmwH014804; Thu, 29 Jan 2004 17:20:48 -0500 (EST) Received: from localhost (ncc0070@localhost)i0TMKlMP014801; Thu, 29 Jan 2004 17:20:47 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.attcanada.ca: ncc0070 owned process doing -bs Date: Thu, 29 Jan 2004 17:20:47 -0500 (EST) From: Brian Tao X-Sender: ncc0070@tor-adm1.nbc.attcanada.ca To: "David O'Brien" In-Reply-To: <20040129185426.GA93242@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: New AMD64 owner 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, 29 Jan 2004 22:21:01 -0000 On Thu, 29 Jan 2004, David O'Brien wrote: > > It is a CPU mode issue. If you think back to your brand new i386 > and Windows 95, the CPU was switched back into real mode when you > ran a MS-Windows 3.1 program. Along with MS-Windows 95 doing > "Thunking" for system services. Ah, gotcha... I had not thought about the parallels between this and the 16-to-32 transition. Cool, things make a lot more sense when I think about it that way. > Yes -- assuming you are talking about dual-booting. My FreeBSD/i386 > build machine is actually an Athlon64 machine that is run purely and > only in 32-bit mode. Athlon64 is the fastest 32-bit x86 machine in > the world today. Damn right. :) -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 30 06:00: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 1BB9A16A4CE; Fri, 30 Jan 2004 06:00:36 -0800 (PST) Received: from fed1mtao02.cox.net (fed1mtao02.cox.net [68.6.19.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED23843D2D; Fri, 30 Jan 2004 06:00:34 -0800 (PST) (envelope-from xcas@cox.net) Received: from cox.net ([68.2.134.143]) by fed1mtao02.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040130140035.DLCS23539.fed1mtao02.cox.net@cox.net>; Fri, 30 Jan 2004 09:00:35 -0500 Message-ID: <401A63C8.60600@cox.net> Date: Fri, 30 Jan 2004 07:01:44 -0700 From: "Greg J." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Greg J." References: <4019F169.7080708@cox.net> In-Reply-To: <4019F169.7080708@cox.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org cc: Kris Kennaway Subject: Re: mounting msdos partitions buggy? 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, 30 Jan 2004 14:00:36 -0000 Greg J. wrote: > > Have you verified that your FAT partition is not corrupted by running > > fsck_msdos against it? > > fsck_msdosfs doesn't even seem to recognize it.. I know there's nothing > wrong with the partition. > > I even did a clean install of FreeBSD & Win2k... and moved the fat32 > partition to another drive. But I still get the same behaviour. > > localhost# fsck_msdosfs /dev/ad1s5 > ** /dev/ad1s5 > backup doesn't compare to primary bootblock > localhost# mount -t msdos /dev/ad1s5 /msdos > localhost# fsck_msdosfs /msdos > ** /msdos (NO WRITE) > Invalid signature in boot block: ffff Ok.. I installed the i386 version & all is fine.. so it seems to be the amd64 version that has trouble with non-UFS/UFS2 partitions. For the people on the amd64 mailing list.. has anyone ran into where copying/moving/creating files to/on a MSDOS partition results in the filename being renamed to where the last character of the filename is added twice? example: cp /etc/rc.conf /msdos (would end up as 'rc.conff' in /msdos) then.. if you tried to rename it back to rc.conf in /msdos.. it would say the file already exists when it doesn't. From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 30 06:16:07 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 3BCA316A4CE; Fri, 30 Jan 2004 06:16:07 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1268243D1D; Fri, 30 Jan 2004 06:16:04 -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 i0UEG1kr027240; Fri, 30 Jan 2004 15:16:01 +0100 (MET) Date: Fri, 30 Jan 2004 15:16:01 +0100 (MET) From: Adriaan de Groot To: "Greg J." In-Reply-To: <401A63C8.60600@cox.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org cc: Kris Kennaway Subject: Re: mounting msdos partitions buggy? 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: Fri, 30 Jan 2004 14:16:07 -0000 On Fri, 30 Jan 2004, Greg J. wrote: > For the people on the amd64 mailing list.. has anyone ran into where > copying/moving/creating files to/on a MSDOS partition results in the > filename being renamed to where the last character of the filename is > added twice? Yes, I see that all the time on my USB pendrive (FAT12, I guess) and USB SD-card reader. I can read files normally, but FBSD creates them with the last file character doubled. I hadn't bothered to report it yet. -- 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 Fri Jan 30 22:29:17 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 4329416A4CE for ; Fri, 30 Jan 2004 22:29:17 -0800 (PST) Received: from mps3.plala.or.jp (c146240.vh.plala.or.jp [210.150.146.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2709443D1F for ; Fri, 30 Jan 2004 22:29:15 -0800 (PST) (envelope-from hiroshi-n@iname.com) Received: from msvc2.plala.or.jp ([172.23.8.210]) by mps3.plala.or.jp with SMTP id <20040131062914.KITS231.mps3.plala.or.jp@msvc2.plala.or.jp> for ; Sat, 31 Jan 2004 15:29:14 +0900 Received: ( 3096 invoked from network); 31 Jan 2004 15:29:08 +0900 Received: from unknown (HELO msc1.plala.or.jp) (172.23.8.24) by msvc2 with SMTP; 31 Jan 2004 15:28:58 +0900 Received: from [192.168.254.102] ([220.220.99.201]) by msc1.plala.or.jp with ESMTP id <20040131062857.RSI15780.msc1.plala.or.jp@[192.168.254.102]> for ; Sat, 31 Jan 2004 15:28:57 +0900 Mime-Version: 1.0 X-Sender: h-nak@sea.plala.or.jp@secure.plala.or.jp X-Mailer: QUALCOMM MacOS X Eudora Version 6J-Jr3 Message-Id: Date: Sat, 31 Jan 2004 15:28:57 +0900 To: freebsd-amd64@freebsd.org From: hiroshi-n@iname.com Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: XFree86 build 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, 31 Jan 2004 06:29:17 -0000 Hi, I installed FreeBSD 5.2 (amd64) from ISO image, then tried to build XFree86 4.3.99.902 from source. ( my video card is Radeon 9600XT and not supported by the default installation. ) But compilation failed while compiling FreeType/lib/ttcalc.c in function 'Order64'. - CARD64 is undefined I had no problem in building XFree86 for Linux 64 (Fedora ), FreeBSD i386 Are there any required modification to the header/source/make files ? --------------- Hiroshi Nakamoto From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 30 22:36: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 CC3BA16A4CE for ; Fri, 30 Jan 2004 22:36:26 -0800 (PST) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0CC043D2F for ; Fri, 30 Jan 2004 22:36:25 -0800 (PST) (envelope-from techsupport@thejemreport.com) Received: from [192.168.0.163] (roc-66-66-218-250.rochester.rr.com [66.66.218.250]) by smtp-relay.omnis.com (Postfix) with ESMTP id EE0618836BE for ; Fri, 30 Jan 2004 22:36:24 -0800 (PST) From: Jem Matzan To: FreeBSD/AMD64 list In-Reply-To: References: Content-Type: text/plain Message-Id: <1075530947.840.2.camel@.rochester.rr.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 31 Jan 2004 01:35:47 -0500 Content-Transfer-Encoding: 7bit Subject: Re: XFree86 build 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, 31 Jan 2004 06:36:26 -0000 On Sat, 2004-01-31 at 01:28, hiroshi-n@iname.com wrote: > Hi, > > I installed FreeBSD 5.2 (amd64) from ISO image, then tried to build > XFree86 4.3.99.902 from source. > ( my video card is Radeon 9600XT and not supported by the default > installation. ) > > But compilation failed while compiling FreeType/lib/ttcalc.c in > function 'Order64'. - CARD64 is undefined > > I had no problem in building XFree86 for Linux 64 (Fedora ), FreeBSD i386 > > Are there any required modification to the header/source/make files ? > > --------------- > Hiroshi Nakamoto What's in your /etc/make.conf? I have CPUTYPE?=?x86_64 for the CPU type, and CFLAGS are set to -0 -pipe. Occasionally for some builds (KDE for instance) I have to add -fPIC to get everything to compile properly. I don't know if these settings are "right," but they work for me. -- Jem Matzan From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 30 23:48: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 0C6BF16A4CE for ; Fri, 30 Jan 2004 23:48:34 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8183A43D31 for ; Fri, 30 Jan 2004 23:48:31 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0V7mUA0018709; Fri, 30 Jan 2004 23:48:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0V7mUNk018708; Fri, 30 Jan 2004 23:48:30 -0800 (PST) (envelope-from obrien) Date: Fri, 30 Jan 2004 23:48:30 -0800 From: "David O'Brien" To: Jem Matzan Message-ID: <20040131074830.GA18624@dragon.nuxi.com> References: <1075530947.840.2.camel@.rochester.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1075530947.840.2.camel@.rochester.rr.com> 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 list Subject: Re: XFree86 build 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: Sat, 31 Jan 2004 07:48:34 -0000 On Sat, Jan 31, 2004 at 01:35:47AM -0500, Jem Matzan wrote: > What's in your /etc/make.conf? I have CPUTYPE?=?x86_64 for the CPU > type, That is so totally wrong, I don't know where the idea could have come from. There is a single AMD64 implimentation at this time, so there are no choices (or things to tweak). x86_64 is Linux's bastardized spelling of "AMD64". > and CFLAGS are set to -0 -pipe. Occasionally for some builds (KDE > for instance) I have to add -fPIC to get everything to compile properly. > I don't know if these settings are "right," but they work for me. Yes, -fPIC must be used for shared libraries, etc... From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 30 23:49:20 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 6432716A4CE for ; Fri, 30 Jan 2004 23:49:20 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B48FA43D31 for ; Fri, 30 Jan 2004 23:49:17 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0V7nHA0018721; Fri, 30 Jan 2004 23:49:17 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0V7nG4s018720; Fri, 30 Jan 2004 23:49:16 -0800 (PST) (envelope-from obrien) Date: Fri, 30 Jan 2004 23:49:16 -0800 From: "David O'Brien" To: hiroshi-n@iname.com Message-ID: <20040131074916.GB18624@dragon.nuxi.com> References: 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: XFree86 build 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: Sat, 31 Jan 2004 07:49:20 -0000 On Sat, Jan 31, 2004 at 03:28:57PM +0900, hiroshi-n@iname.com wrote: > I installed FreeBSD 5.2 (amd64) from ISO image, then tried to build > XFree86 4.3.99.902 from source. > ( my video card is Radeon 9600XT and not supported by the default > installation. ) > > But compilation failed while compiling FreeType/lib/ttcalc.c in > function 'Order64'. - CARD64 is undefined > > I had no problem in building XFree86 for Linux 64 (Fedora ), FreeBSD i386 > > Are there any required modification to the header/source/make files ? Probably, but none that we know of. If you could track it down and post a patch to this list, it would be helpful. :-) From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 30 23:56: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 634C716A4CE for ; Fri, 30 Jan 2004 23:56:04 -0800 (PST) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95E8F43D1D for ; Fri, 30 Jan 2004 23:56:03 -0800 (PST) (envelope-from techsupport@thejemreport.com) Received: from [192.168.0.163] (roc-66-66-218-250.rochester.rr.com [66.66.218.250]) by smtp-relay.omnis.com (Postfix) with ESMTP id CBBBB1880A22 for ; Fri, 30 Jan 2004 23:56:02 -0800 (PST) From: Jem Matzan To: FreeBSD/AMD64 list In-Reply-To: <20040131074830.GA18624@dragon.nuxi.com> References: <1075530947.840.2.camel@.rochester.rr.com> <20040131074830.GA18624@dragon.nuxi.com> Content-Type: text/plain Message-Id: <1075535725.1189.4.camel@.rochester.rr.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 31 Jan 2004 02:55:25 -0500 Content-Transfer-Encoding: 7bit Subject: Re: XFree86 build 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, 31 Jan 2004 07:56:04 -0000 On Sat, 2004-01-31 at 02:48, David O'Brien wrote: > On Sat, Jan 31, 2004 at 01:35:47AM -0500, Jem Matzan wrote: > > What's in your /etc/make.conf? I have CPUTYPE?=?x86_64 for the CPU > > type, > > That is so totally wrong, I don't know where the idea could have come > from. There is a single AMD64 implimentation at this time, so there are > no choices (or things to tweak). x86_64 is Linux's bastardized spelling > of "AMD64". Hey that's wonderful, but do you have a suggestion as to what the CPUTYPE should be? -- Jem Matzan From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 00:00:41 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 2AEFE16A4CE for ; Sat, 31 Jan 2004 00:00:41 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E827243D2D for ; Sat, 31 Jan 2004 00:00:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0V80dA0018921; Sat, 31 Jan 2004 00:00:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0V80cO3018920; Sat, 31 Jan 2004 00:00:38 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Jan 2004 00:00:38 -0800 From: "David O'Brien" To: Jem Matzan Message-ID: <20040131080038.GE18624@dragon.nuxi.com> References: <1075530947.840.2.camel@.rochester.rr.com> <20040131074830.GA18624@dragon.nuxi.com> <1075535725.1189.4.camel@.rochester.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1075535725.1189.4.camel@.rochester.rr.com> 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 list Subject: Re: XFree86 build 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: Sat, 31 Jan 2004 08:00:41 -0000 On Sat, Jan 31, 2004 at 02:55:25AM -0500, Jem Matzan wrote: > On Sat, 2004-01-31 at 02:48, David O'Brien wrote: > > On Sat, Jan 31, 2004 at 01:35:47AM -0500, Jem Matzan wrote: > > > What's in your /etc/make.conf? I have CPUTYPE?=?x86_64 for the CPU > > > type, > > > > That is so totally wrong, I don't know where the idea could have come > > from. There is a single AMD64 implimentation at this time, so there are > > no choices (or things to tweak). x86_64 is Linux's bastardized spelling > > of "AMD64". > > Hey that's wonderful, but do you have a suggestion as to what the > CPUTYPE should be? Yes, don't set it. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 01:05: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 EBF4616A4CE for ; Sat, 31 Jan 2004 01:05:57 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00EE043D31 for ; Sat, 31 Jan 2004 01:05:57 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0V95uA0020708; Sat, 31 Jan 2004 01:05:56 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0V95txX020707; Sat, 31 Jan 2004 01:05:55 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Jan 2004 01:05:55 -0800 From: "David O'Brien" To: sethbc@sethbc.org Message-ID: <20040131090555.GI18624@dragon.nuxi.com> References: <49414.128.253.186.248.1074552149.squirrel@sethbc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49414.128.253.186.248.1074552149.squirrel@sethbc.org> 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: gdb and/or gaim on amd64 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: Sat, 31 Jan 2004 09:05:58 -0000 On Mon, Jan 19, 2004 at 05:42:29PM -0500, sethbc@sethbc.org wrote: > Anyway, its really hard to debug this stuff without a debugger though, i > was wondering what the status was of a gdb-6.0 based debugger. I think i > saw that Peter had a binary going, but it was never released. You can build it from stock FSF GDB sources. The gdb6 port is still a WIP due to the amount of effort it is taking porting all our custom cruft from GDB 5.2 to GDB 6.1. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 01:13: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 0F6BB16A4CE for ; Sat, 31 Jan 2004 01:13:47 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED11E43D2F for ; Sat, 31 Jan 2004 01:13:43 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i0V9DgA0020780; Sat, 31 Jan 2004 01:13:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i0V9DgEa020779; Sat, 31 Jan 2004 01:13:42 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Jan 2004 01:13:41 -0800 From: "David O'Brien" To: sethbc@sethbc.org Message-ID: <20040131091341.GJ18624@dragon.nuxi.com> References: <49202.128.253.186.248.1074541973.squirrel@sethbc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49202.128.253.186.248.1074541973.squirrel@sethbc.org> 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: DRM/DRI Support for ATI Cards 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: Sat, 31 Jan 2004 09:13:47 -0000 On Mon, Jan 19, 2004 at 02:52:53PM -0500, sethbc@sethbc.org wrote: > I was wondering if anyone has tried to build the DRM module for the ATI Kernel modules aren't supported yet on AMD64. There are both toolchain and potential kernel issues. Modules aren't too far off. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 08:11:20 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 2D02E16A4CE; Sat, 31 Jan 2004 08:11:20 -0800 (PST) Received: from eterna.binary.net (eterna.binary.net [216.229.0.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14A4243D39; Sat, 31 Jan 2004 08:11:19 -0800 (PST) (envelope-from yura@binary.net) Received: from matrix.binary.net (matrix.binary.net [216.229.0.2]) by eterna.binary.net (Postfix) with ESMTP id 65DDCB466E; Sat, 31 Jan 2004 10:11:18 -0600 (CST) Received: by matrix.binary.net (Postfix, from userid 100) id 3911110293A; Sat, 31 Jan 2004 10:11:18 -0600 (CST) Date: Sat, 31 Jan 2004 10:11:18 -0600 From: Yura Socolov To: David O'Brien Message-ID: <20040131161118.GA63733@binary.net> References: <20040131074916.GB18624@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040131074916.GB18624@dragon.nuxi.com> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: XFree86 build 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, 31 Jan 2004 16:11:20 -0000 On Sat, Jan 31, 2004 at 03:28:57PM +0900, hiroshi-n@iname.com wrote: > > I installed FreeBSD 5.2 (amd64) from ISO image, then tried to build > > XFree86 4.3.99.902 from source. > > ( my video card is Radeon 9600XT and not supported by the default > > installation. ) > > > > But compilation failed while compiling FreeType/lib/ttcalc.c in I just compiled XFree from ports on a fresh install of 5.2, cvsup'ed to 5.2-RELENG as of yesterday. Compiled and works without a single thing to complain about or anything to tweak. The port compiles version 4.3.0, not sure if that's what you want, but since it works fine, you might want it. I also have a Radeon card, 7000 though. Works like a charm with vesa driver, not ati driver. Btw, try that with your card, perhaps you don't even need to compile anything. -- -- Yura Socolov FP: A7192ABD96E15F5 19AB21E60C34109 -- http://users.binary.net/yura/ -- -- Opinions and views in this message are my own and my own only. -- -- "Two wrongs don't make a right... and three rights make a left." -- TRACON From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 08:24:25 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 637D716A4CE; Sat, 31 Jan 2004 08:24:25 -0800 (PST) Received: from fed1mtao08.cox.net (fed1mtao08.cox.net [68.6.19.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7590043D31; Sat, 31 Jan 2004 08:24:24 -0800 (PST) (envelope-from xcas@cox.net) Received: from localhost.bsd-unix.org ([68.2.134.143]) by fed1mtao08.cox.netSMTP <20040131162422.VQNP5698.fed1mtao08.cox.net@localhost.bsd-unix.org>; Sat, 31 Jan 2004 11:24:22 -0500 Date: Sat, 31 Jan 2004 09:25:34 -0700 From: "Greg J." To: Tim Robbins Message-Id: <20040131092534.0ba836b2.xcas@cox.net> In-Reply-To: <20040131152608.GA28862@cat.robbins.dropbear.id.au> References: <20040128075639.32890e82.xcas@cox.net> <20040131152608.GA28862@cat.robbins.dropbear.id.au> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; amd64-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: mounting msdos partitions buggy? 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, 31 Jan 2004 16:24:25 -0000 On Sun, 1 Feb 2004 02:26:08 +1100 Tim Robbins wrote: > Try this patch. I'm pretty sure that the problem is that an int * is > bogusly cast to a size_t * in a few places in msdosfs_conv.c, > but I don't have an amd64 system myself, so I haven't been able to > test it. That did the trick.. thanks. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 09:34:49 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 35F5016A4CE for ; Sat, 31 Jan 2004 09:34:49 -0800 (PST) Received: from amsfep16-int.chello.nl (amsfep16-int.chello.nl [213.46.243.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78FD343D5D for ; Sat, 31 Jan 2004 09:34:47 -0800 (PST) (envelope-from girgen@pingpong.net) Received: from palle.girgensohn.se ([213.89.137.38]) by amsfep16-int.chello.nlESMTP <20040131173446.ORZS1937.amsfep16-int.chello.nl@palle.girgensohn.se>; Sat, 31 Jan 2004 18:34:46 +0100 Received: from localhost (localhost [127.0.0.1]) by palle.girgensohn.se (8.12.9p2/8.12.9) with ESMTP id i0VHYjQY098931; Sat, 31 Jan 2004 18:34:45 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Sat, 31 Jan 2004 18:34:45 +0100 From: Palle Girgensohn To: amd64@freebsd.org Message-ID: <125210000.1075570485@palle.girgensohn.se> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========5C6BFA260705BFB80F6E==========" Subject: please try this patch for: postgresql-libpq++-4.0_1 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, 31 Jan 2004 17:34:49 -0000 --==========5C6BFA260705BFB80F6E========== Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Can someone on amd64 try this patch by putting it in ports/databases/postgresql-libpq++/files and try building the port? It's supposed to fix this problem: Thanks, Palle --==========5C6BFA260705BFB80F6E========== Content-Type: application/octet-stream; name=patch-Makefile Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=patch-Makefile; size=1228 ZGlmZiAtdSAvaG9tZS9naXJnZW4vcG9ydHMvdXNyL2xvY2FsL3BvcnRzL2RhdGFiYXNlcy9wb3N0 Z3Jlc3FsLWxpYnBxKysvd29yay9saWJwcSsrLTQuMC9NYWtlZmlsZX4gL2hvbWUvZ2lyZ2VuL3Bv cnRzL3Vzci9sb2NhbC9wb3J0cy9kYXRhYmFzZXMvcG9zdGdyZXNxbC1saWJwcSsrL3dvcmsvbGli cHErKy00LjAvTWFrZWZpbGUKLS0tIC9ob21lL2dpcmdlbi9wb3J0cy91c3IvbG9jYWwvcG9ydHMv ZGF0YWJhc2VzL3Bvc3RncmVzcWwtbGlicHErKy93b3JrL2xpYnBxKystNC4wL01ha2VmaWxlfglT YXQgSmFuIDMxIDE4OjAzOjE4IDIwMDQKKysrIC9ob21lL2dpcmdlbi9wb3J0cy91c3IvbG9jYWwv cG9ydHMvZGF0YWJhc2VzL3Bvc3RncmVzcWwtbGlicHErKy93b3JrL2xpYnBxKystNC4wL01ha2Vm aWxlCVNhdCBKYW4gMzEgMTg6MDM6MTggMjAwNApAQCAtMjAsNyArMjAsNyBAQAogT0JKUz0gcGdj b25uZWN0aW9uLm8gcGdkYXRhYmFzZS5vIHBndHJhbnNkYi5vIHBnY3Vyc29yZGIubyBwZ2xvYmpl Y3QubwogTElCUEdYWEhFQURFUlMgPSBwZ2Nvbm5lY3Rpb24uaCBwZ2RhdGFiYXNlLmggcGd0cmFu c2RiLmggcGdjdXJzb3JkYi5oIHBnbG9iamVjdC5oCiAKLVNIQVJFRD0gLWZwaWMgLXNoYXJlZCAt V2wsLXgsLXNvbmFtZSwkKFRBUkdFVCkuc28uJChTT19NQUpPUl9WRVJTSU9OKSAtV2wsLXJwYXRo LCQoUE9TVEdSRVNfSE9NRSkvbGliCitTSEFSRUQ9IC1mcGljIC1mUElDIC1zaGFyZWQgLVdsLC14 LC1zb25hbWUsJChUQVJHRVQpLnNvLiQoU09fTUFKT1JfVkVSU0lPTikgLVdsLC1ycGF0aCwkKFBP U1RHUkVTX0hPTUUpL2xpYgogc29uYW1lPSQoVEFSR0VUKS5zby4kKFNPX01BSk9SX1ZFUlNJT04p LiQoU09fTUlOT1JfVkVSU0lPTikKIAogYWxsOiAgJChzb25hbWUpCg== --==========5C6BFA260705BFB80F6E==========-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 09:46: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 CD9AC16A4CE for ; Sat, 31 Jan 2004 09:46:36 -0800 (PST) Received: from amsfep20-int.chello.nl (amsfep12-int.chello.nl [213.46.243.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F7BD43D5E for ; Sat, 31 Jan 2004 09:46:02 -0800 (PST) (envelope-from girgen@pingpong.net) Received: from palle.girgensohn.se ([213.89.137.38]) by amsfep20-int.chello.nlESMTP <20040131171649.SPCB1492.amsfep20-int.chello.nl@palle.girgensohn.se>; Sat, 31 Jan 2004 18:16:49 +0100 Received: from localhost (localhost [127.0.0.1]) by palle.girgensohn.se (8.12.9p2/8.12.9) with ESMTP id i0VHGmQY098698; Sat, 31 Jan 2004 18:16:48 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Sat, 31 Jan 2004 18:16:48 +0100 From: Palle Girgensohn To: amd64@freebsd.org Message-ID: <106670000.1075569408@palle.girgensohn.se> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========117E9A9806CF319BA57F==========" Subject: please try this patch for: p5-postgresql-plperl-7.4.1 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, 31 Jan 2004 17:46:36 -0000 --==========117E9A9806CF319BA57F========== Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Can someone on amd64 please try this patch for databases/p5-postgresql-plperl. It's supposed to fix this problem: Thanks, Palle --==========117E9A9806CF319BA57F========== Content-Type: application/octet-stream; name="p5-postgresql-plperl.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="p5-postgresql-plperl.diff"; size=1122 SW5kZXg6IGZpbGVzL3BhdGNoLXNyYy1tYWtlZmlsZXMtTWFrZWZpbGUuZnJlZWJzZAo9PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09ClJDUyBmaWxlOiAvbWlzYy9uY3ZzL3BvcnRzL2RhdGFiYXNlcy9wNS1wb3N0Z3Jlc3FsLXBs cGVybC9maWxlcy9wYXRjaC1zcmMtbWFrZWZpbGVzLU1ha2VmaWxlLmZyZWVic2QsdgpyZXRyaWV2 aW5nIHJldmlzaW9uIDEuMQpkaWZmIC11IC1yMS4xIHBhdGNoLXNyYy1tYWtlZmlsZXMtTWFrZWZp bGUuZnJlZWJzZAotLS0gZmlsZXMvcGF0Y2gtc3JjLW1ha2VmaWxlcy1NYWtlZmlsZS5mcmVlYnNk CTQgU2VwIDIwMDMgMTI6NDc6NDcgLTAwMDAJMS4xCisrKyBmaWxlcy9wYXRjaC1zcmMtbWFrZWZp bGVzLU1ha2VmaWxlLmZyZWVic2QJMzEgSmFuIDIwMDQgMTY6NTM6MzUgLTAwMDAKQEAgLTEsNSAr MSwxNCBAQAogLS0tIHNyYy9tYWtlZmlsZXMvTWFrZWZpbGUuZnJlZWJzZC5vcmlnCVdlZCBBdWcg MjkgMjE6MTQ6NDAgMjAwMQotKysrIHNyYy9tYWtlZmlsZXMvTWFrZWZpbGUuZnJlZWJzZAlNb24g U2VwICAxIDEwOjE2OjI2IDIwMDMKKysrKyBzcmMvbWFrZWZpbGVzL01ha2VmaWxlLmZyZWVic2QJ U2F0IEphbiAzMSAxNzo1MToyNSAyMDA0CitAQCAtNyw3ICs3LDcgQEAKKyBlbmRpZgorIAorIERM U1VGRklYID0gLnNvCistQ0ZMQUdTX1NMID0gLWZwaWMgLURQSUMKKytDRkxBR1NfU0wgPSAtZnBp YyAtRFBJQyAtZlBJQworIAorICUuc286ICUubworIGlmZGVmIEVMRl9TWVNURU0KIEBAIC0yMywz ICsyMyw1IEBACiAgZW5kaWYKICAK --==========117E9A9806CF319BA57F==========-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 11:30: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 1EF3016A4D5 for ; Sat, 31 Jan 2004 11:30:45 -0800 (PST) Received: from fed1mtao01.cox.net (fed1mtao01.cox.net [68.6.19.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DC7143D1F for ; Sat, 31 Jan 2004 11:30:42 -0800 (PST) (envelope-from xcas@cox.net) Received: from cox.net ([68.2.134.143]) by fed1mtao01.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040131193042.XBMP244.fed1mtao01.cox.net@cox.net>; Sat, 31 Jan 2004 14:30:42 -0500 Message-ID: <401C02A9.5030506@cox.net> Date: Sat, 31 Jan 2004 12:31:53 -0700 From: "Greg J." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adriaan de Groot , freebsd-amd64@freebsd.org References: <200401311932.37140.adridg@cs.kun.nl> In-Reply-To: <200401311932.37140.adridg@cs.kun.nl> Content-Type: multipart/mixed; boundary="------------090407090401070707040008" Subject: Re: msdosfs patch 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, 31 Jan 2004 19:30:45 -0000 This is a multi-part message in MIME format. --------------090407090401070707040008 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Adriaan de Groot wrote: > Hi Greg, > > Since Tim didn't mail his patch to the amd64 list, perhaps you could re-post > it there? oops.. I thought Tim's patch went to the freebsd-amd64 list as well.. sorry. It's attached to this email. :) --------------090407090401070707040008 Content-Type: text/plain; name="patch-msdosfs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch-msdosfs" Index: direntry.h =================================================================== RCS file: /home/ncvs/src/sys/fs/msdosfs/direntry.h,v retrieving revision 1.19 diff -u -u -r1.19 direntry.h --- direntry.h 26 Dec 2003 17:24:37 -0000 1.19 +++ direntry.h 31 Jan 2004 15:22:11 -0000 @@ -144,14 +144,14 @@ void dos2unixtime(u_int dd, u_int dt, u_int dh, struct timespec *tsp); int dos2unixfn(u_char dn[11], u_char *un, int lower, struct msdosfsmount *pmp); -int unix2dosfn(const u_char *un, u_char dn[12], int unlen, u_int gen, +int unix2dosfn(const u_char *un, u_char dn[12], size_t unlen, u_int gen, struct msdosfsmount *pmp); -int unix2winfn(const u_char *un, int unlen, struct winentry *wep, int cnt, +int unix2winfn(const u_char *un, size_t unlen, struct winentry *wep, int cnt, int chksum, struct msdosfsmount *pmp); -int winChkName(const u_char *un, int unlen, int chksum, +int winChkName(const u_char *un, size_t unlen, int chksum, struct msdosfsmount *pmp); int win2unixfn(struct winentry *wep, int chksum, struct msdosfsmount *pmp); u_int8_t winChksum(u_int8_t *name); -int winSlotCnt(const u_char *un, int unlen, struct msdosfsmount *pmp); -int winLenFixup(const u_char *un, int unlen); +int winSlotCnt(const u_char *un, size_t unlen, struct msdosfsmount *pmp); +size_t winLenFixup(const u_char *un, size_t unlen); #endif /* _KERNEL */ Index: msdosfs_conv.c =================================================================== RCS file: /home/ncvs/src/sys/fs/msdosfs/msdosfs_conv.c,v retrieving revision 1.36 diff -u -u -r1.36 msdosfs_conv.c --- msdosfs_conv.c 26 Dec 2003 17:24:37 -0000 1.36 +++ msdosfs_conv.c 31 Jan 2004 15:21:44 -0000 @@ -95,7 +95,7 @@ static u_short lastddate; static u_short lastdtime; -static int mbsadjpos(const char **, int, int, int, int, void *handle); +static int mbsadjpos(const char **, size_t, size_t, int, int, void *handle); static u_int16_t dos2unixchr(const u_char **, size_t *, int, struct msdosfsmount *); static u_int16_t unix2doschr(const u_char **, size_t *, struct msdosfsmount *); static u_int16_t win2unixchr(u_int16_t, struct msdosfsmount *); @@ -421,7 +421,7 @@ int lower; struct msdosfsmount *pmp; { - int i; + size_t i; int thislong = 0; u_int16_t c; @@ -438,7 +438,7 @@ * Copy the name portion into the unix filename string. */ for (i = 8; i > 0 && *dn != ' ';) { - c = dos2unixchr((const u_char **)&dn, (size_t *)&i, lower, pmp); + c = dos2unixchr((const u_char **)&dn, &i, lower, pmp); if (c & 0xff00) { *un++ = c >> 8; thislong++; @@ -456,7 +456,7 @@ *un++ = '.'; thislong++; for (i = 3; i > 0 && *dn != ' ';) { - c = dos2unixchr((const u_char **)&dn, (size_t *)&i, lower, pmp); + c = dos2unixchr((const u_char **)&dn, &i, lower, pmp); if (c & 0xff00) { *un++ = c >> 8; thislong++; @@ -485,11 +485,12 @@ unix2dosfn(un, dn, unlen, gen, pmp) const u_char *un; u_char dn[12]; - int unlen; + size_t unlen; u_int gen; struct msdosfsmount *pmp; { - int i, j, l; + ssize_t i, j; + int l; int conv = 1; const u_char *cp, *dp, *dp1; u_char gentext[6], *wcp; @@ -531,7 +532,7 @@ * Filenames with some characters are not allowed! */ for (cp = un, i = unlen; i > 0;) - if (unix2doschr(&cp, (size_t *)&i, pmp) == 0) + if (unix2doschr(&cp, &i, pmp) == 0) return 0; /* @@ -569,7 +570,7 @@ else l = unlen - (dp - un); for (cp = dp, i = l, j = 8; i > 0 && j < 11; j++) { - c = unix2doschr(&cp, (size_t *)&i, pmp); + c = unix2doschr(&cp, &i, pmp); if (c & 0xff00) { dn[j] = c >> 8; if (++j < 11) { @@ -606,7 +607,7 @@ * Now convert the rest of the name */ for (i = dp - un, j = 0; un < dp && j < 8; j++) { - c = unix2doschr(&un, (size_t *)&i, pmp); + c = unix2doschr(&un, &i, pmp); if (c & 0xff00) { dn[j] = c >> 8; if (++j < 8) { @@ -701,7 +702,7 @@ int unix2winfn(un, unlen, wep, cnt, chksum, pmp) const u_char *un; - int unlen; + size_t unlen; struct winentry *wep; int cnt; int chksum; @@ -737,21 +738,21 @@ */ end = 0; for (wcp = wep->wePart1, i = sizeof(wep->wePart1)/2; --i >= 0 && !end;) { - code = unix2winchr(&un, (size_t *)&unlen, 0, pmp); + code = unix2winchr(&un, &unlen, 0, pmp); *wcp++ = code; *wcp++ = code >> 8; if (!code) end = WIN_LAST; } for (wcp = wep->wePart2, i = sizeof(wep->wePart2)/2; --i >= 0 && !end;) { - code = unix2winchr(&un, (size_t *)&unlen, 0, pmp); + code = unix2winchr(&un, &unlen, 0, pmp); *wcp++ = code; *wcp++ = code >> 8; if (!code) end = WIN_LAST; } for (wcp = wep->wePart3, i = sizeof(wep->wePart3)/2; --i >= 0 && !end;) { - code = unix2winchr(&un, (size_t *)&unlen, 0, pmp); + code = unix2winchr(&un, &unlen, 0, pmp); *wcp++ = code; *wcp++ = code >> 8; if (!code) @@ -770,11 +771,11 @@ int winChkName(un, unlen, chksum, pmp) const u_char *un; - int unlen; + size_t unlen; int chksum; struct msdosfsmount *pmp; { - int len; + size_t len; u_int16_t c1, c2; u_char *np; struct dirent dirbuf; @@ -804,8 +805,8 @@ * to look up or create files in case sensitive even when * it's a long file name. */ - c1 = unix2winchr((const u_char **)&np, (size_t *)&len, LCASE_BASE, pmp); - c2 = unix2winchr(&un, (size_t *)&unlen, LCASE_BASE, pmp); + c1 = unix2winchr((const u_char **)&np, &len, LCASE_BASE, pmp); + c2 = unix2winchr(&un, &unlen, LCASE_BASE, pmp); if (c1 != c2) return -2; } @@ -928,7 +929,7 @@ int winSlotCnt(un, unlen, pmp) const u_char *un; - int unlen; + size_t unlen; struct msdosfsmount *pmp; { size_t wlen; @@ -939,7 +940,7 @@ if (pmp->pm_flags & MSDOSFSMNT_KICONV && msdosfs_iconv) { wlen = WIN_MAXLEN * 2; wnp = wn; - msdosfs_iconv->conv(pmp->pm_u2w, (const char **)&un, (size_t *)&unlen, &wnp, &wlen); + msdosfs_iconv->conv(pmp->pm_u2w, (const char **)&un, &unlen, &wnp, &wlen); if (unlen > 0) return 0; return howmany(WIN_MAXLEN - wlen/2, WIN_CHARS); @@ -953,10 +954,10 @@ /* * Determine the number of bytes neccesary for Win95 names */ -int +size_t winLenFixup(un, unlen) const u_char* un; - int unlen; + size_t unlen; { for (un += unlen; unlen > 0; unlen--) if (*--un != ' ' && *un != '.') @@ -970,14 +971,14 @@ * inlen or outlen. */ static int -mbsadjpos(const char **instr, int inlen, int outlen, int weight, int flag, void *handle) +mbsadjpos(const char **instr, size_t inlen, size_t outlen, int weight, int flag, void *handle) { char *outp, outstr[outlen * weight + 1]; if (flag & MSDOSFSMNT_KICONV && msdosfs_iconv) { outp = outstr; outlen *= weight; - msdosfs_iconv->conv(handle, instr, (size_t *)&inlen, &outp, (size_t *)&outlen); + msdosfs_iconv->conv(handle, instr, &inlen, &outp, &outlen); return (inlen); } --------------090407090401070707040008-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 11:31: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 895D616A4CE for ; Sat, 31 Jan 2004 11:31:08 -0800 (PST) Received: from curacao.n2it.nl (62-177-157-186.bbeyond.nl [62.177.157.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09FAF43D1F for ; Sat, 31 Jan 2004 11:31:07 -0800 (PST) (envelope-from billsf@curacao.n2it.nl) Received: by curacao.n2it.nl (Postfix, from userid 1000) id A2E3F2108; Sat, 31 Jan 2004 20:31:05 +0100 (CET) Date: Sat, 31 Jan 2004 20:31:05 +0100 From: Bill Squire To: freebsd-amd64@freebsd.org Message-ID: <20040131193105.GA21759@curacao.n2it.nl> References: <1075530947.840.2.camel@.rochester.rr.com> <20040131074830.GA18624@dragon.nuxi.com> <1075535725.1189.4.camel@.rochester.rr.com> <20040131080038.GE18624@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040131080038.GE18624@dragon.nuxi.com> User-Agent: Mutt/1.4.1i Subject: Re: XFree86 build 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, 31 Jan 2004 19:31:08 -0000 On Sat, Jan 31, 2004 at 12:00:38AM -0800, David O'Brien wrote: > On Sat, Jan 31, 2004 at 02:55:25AM -0500, Jem Matzan wrote: > > On Sat, 2004-01-31 at 02:48, David O'Brien wrote: > > > On Sat, Jan 31, 2004 at 01:35:47AM -0500, Jem Matzan wrote: > > > > What's in your /etc/make.conf? I have CPUTYPE?=?x86_64 for the CPU > > > > type, > > > > > > That is so totally wrong, I don't know where the idea could have come > > > from. There is a single AMD64 implimentation at this time, so there are > > > no choices (or things to tweak). x86_64 is Linux's bastardized spelling > > > of "AMD64". > > > > Hey that's wonderful, but do you have a suggestion as to what the > > CPUTYPE should be? > > Yes, don't set it. Here is a question for David or anybody: CPUTYPE?=. is therefore correct? (or nothing at all?) The two settings below have worked well for some time now. Is this wrong too? CPUTYPE?= amd64 TARGET_ARCH?= amd64 Is there any chance of setting compatibility for "Linux's bastardized spelling" of 'amd64' at the top level? (In /etc/make.conf ?) This is still one (if not the most) common trivial patch in the ports. CXXFLAGS+= -fPIC -DPIC seems to always work. The Linux people say: "It's a workaround -- don't. Placing -fPIC in CFLAGS= sometimes causes the compiler to bomb, while not having it to make some some libs (in the right Makefile) will cause the linker to bomb with a very Linux like "x86_64_32" in the error message. What gives? It certainly is "amd64", but "HAMMER" is still used to ID the "amd64" in the kernel conf? Certainly I like what I have, but if there is one and only one "amd64", calling it by atleast three names looks like trouble. Bill From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 12:12: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 D126216A4CE; Sat, 31 Jan 2004 12:12:36 -0800 (PST) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFF7443D2F; Sat, 31 Jan 2004 12:12:34 -0800 (PST) (envelope-from tilman@arved.de) Received: from huckfinn-xl1.arved.de (localhost [127.0.0.1]) i0VKCWH6007893; Sat, 31 Jan 2004 21:12:33 +0100 (CET) (envelope-from tilman@arved.de) Received: (from tilman@localhost) by huckfinn-xl1.arved.de (8.12.11/8.12.6/Submit) id i0VKCWFF007892; Sat, 31 Jan 2004 21:12:32 +0100 (CET) X-Authentication-Warning: huckfinn-xl1.arved.de: tilman set sender to tilman@arved.de using -f Date: Sat, 31 Jan 2004 21:12:32 +0100 From: Tilman Linneweh To: Palle Girgensohn Message-ID: <20040131201232.GA65933@huckfinn.arved.de> References: <106670000.1075569408@palle.girgensohn.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/NwG7NuG0/W8LcLh" Content-Disposition: inline In-Reply-To: <106670000.1075569408@palle.girgensohn.se> User-Agent: Mutt/1.4.1i cc: amd64@freebsd.org cc: perl@freebsd.org Subject: Re: please try this patch for: p5-postgresql-plperl-7.4.1 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, 31 Jan 2004 20:12:37 -0000 --/NwG7NuG0/W8LcLh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Palle Girgensohn [Sat, Jan 31, 2004 at 06:16:48PM +0100]: > Hi, >=20 > Can someone on amd64 please try this patch for=20 > databases/p5-postgresql-plperl. >=20 > It's supposed to fix this problem: > .1.log> No, the problem is this file: /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a IMHO, this needs to be fixed by the perl Maintainers. regards tilman --/NwG7NuG0/W8LcLh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAHAwufCLDn4B6xToRAt3WAJsFFIgdpVn+LZBMK+9o1hx269Zg5ACdGbFv hHZrCVpA7zmXyN7zIPQachM= =JxV0 -----END PGP SIGNATURE----- --/NwG7NuG0/W8LcLh-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 12:53: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 831EE16A4CE; Sat, 31 Jan 2004 12:53:26 -0800 (PST) Received: from amsfep15-int.chello.nl (amsfep15-int.chello.nl [213.46.243.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2990443D1F; Sat, 31 Jan 2004 12:53:24 -0800 (PST) (envelope-from girgen@pingpong.net) Received: from palle.girgensohn.se ([213.89.137.38]) by amsfep15-int.chello.nlESMTP <20040131205322.IYRB25541.amsfep15-int.chello.nl@palle.girgensohn.se>; Sat, 31 Jan 2004 21:53:22 +0100 Received: from localhost (localhost [127.0.0.1]) by palle.girgensohn.se (8.12.9p2/8.12.9) with ESMTP id i0VKrIQY091927; Sat, 31 Jan 2004 21:53:21 +0100 (CET) (envelope-from girgen@pingpong.net) Date: Sat, 31 Jan 2004 21:53:18 +0100 From: Palle Girgensohn To: Tilman Linneweh Message-ID: <205980000.1075582398@palle.girgensohn.se> In-Reply-To: <20040131201232.GA65933@huckfinn.arved.de> References: <106670000.1075569408@palle.girgensohn.se> <20040131201232.GA65933@huckfinn.arved.de> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline cc: amd64@freebsd.org cc: perl@freebsd.org Subject: Re: please try this patch for: p5-postgresql-plperl-7.4.1 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, 31 Jan 2004 20:53:26 -0000 --On l=F6rdag, januari 31, 2004 21.12.32 +0100 Tilman Linneweh=20 wrote: > * Palle Girgensohn [Sat, Jan 31, 2004 at 06:16:48PM +0100]: >> Hi, >> >> Can someone on amd64 please try this patch for >> databases/p5-postgresql-plperl. >> >> It's supposed to fix this problem: >> > 7.4 .1.log> > > No, the problem is this file: > /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a > > IMHO, this needs to be fixed by the perl Maintainers. True, I didn't read carefully enough. This needs to be fixed in the perl=20 code. Still, perhaps it will end up still beeing needed once the libperl.a=20 is rebuilt. We'll know once perl is fixed. /Palle From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 12:54:00 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 82E2916A4CE for ; Sat, 31 Jan 2004 12:54:00 -0800 (PST) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0038E43D41 for ; Sat, 31 Jan 2004 12:53:58 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 3591 invoked from network); 31 Jan 2004 20:53:58 -0000 Received: from dsl017-045-168.spk4.dsl.speakeasy.net (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 31 Jan 2004 20:53:58 -0000 Received: from hydrogen.funkthat.com (pkdapa@localhost.funkthat.com [127.0.0.1])i0VKrvj2071536; Sat, 31 Jan 2004 12:53:57 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id i0VKrt9G071535; Sat, 31 Jan 2004 12:53:55 -0800 (PST) Date: Sat, 31 Jan 2004 12:53:55 -0800 From: John-Mark Gurney To: "Greg J." Message-ID: <20040131205355.GY74366@funkthat.com> Mail-Followup-To: "Greg J." , Adriaan de Groot , freebsd-amd64@freebsd.org References: <200401311932.37140.adridg@cs.kun.nl> <401C02A9.5030506@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <401C02A9.5030506@cox.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: Adriaan de Groot cc: freebsd-amd64@freebsd.org Subject: Re: msdosfs patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2004 20:54:00 -0000 Greg J. wrote this message on Sat, Jan 31, 2004 at 12:31 -0700: > >Since Tim didn't mail his patch to the amd64 list, perhaps you could > >re-post it there? > oops.. I thought Tim's patch went to the freebsd-amd64 list as well.. > sorry. It's attached to this email. :) looks good, though was this (mis)spelling of size_t intentional? [...] > static u_int16_t unix2doschr(const u_char **, size_t *, struct msdosfsmount *); [...] > - int i, j, l; > + ssize_t i, j; > + int l; > int conv = 1; > const u_char *cp, *dp, *dp1; > u_char gentext[6], *wcp; > @@ -531,7 +532,7 @@ > * Filenames with some characters are not allowed! > */ > for (cp = un, i = unlen; i > 0;) > - if (unix2doschr(&cp, (size_t *)&i, pmp) == 0) > + if (unix2doschr(&cp, &i, pmp) == 0) > return 0; > > /* -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 21:13: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 AB1A816A4CE; Sat, 31 Jan 2004 21:13:23 -0800 (PST) Received: from fed1mtao07.cox.net (fed1mtao07.cox.net [68.6.19.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E83F43D41; Sat, 31 Jan 2004 21:13:22 -0800 (PST) (envelope-from xcas@cox.net) Received: from cox.net ([68.2.134.143]) by fed1mtao07.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040201051320.EDQA11482.fed1mtao07.cox.net@cox.net>; Sun, 1 Feb 2004 00:13:20 -0500 Message-ID: <401C8B3A.6030300@cox.net> Date: Sat, 31 Jan 2004 22:14:34 -0700 From: "Greg J." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tim Robbins References: <200401311932.37140.adridg@cs.kun.nl> <401C02A9.5030506@cox.net> <20040131205355.GY74366@funkthat.com> In-Reply-To: <20040131205355.GY74366@funkthat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Adriaan de Groot cc: John-Mark Gurney cc: freebsd-amd64@freebsd.org Subject: Re: msdosfs patch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 05:13:23 -0000 John-Mark Gurney wrote: > Greg J. wrote this message on Sat, Jan 31, 2004 at 12:31 -0700: > >>>Since Tim didn't mail his patch to the amd64 list, perhaps you could >>>re-post it there? >> >>oops.. I thought Tim's patch went to the freebsd-amd64 list as well.. >>sorry. It's attached to this email. :) > > > looks good, though was this (mis)spelling of size_t intentional? > > [...] > >> static u_int16_t unix2doschr(const u_char **, size_t *, struct msdosfsmount *); > > [...] > >>- int i, j, l; >>+ ssize_t i, j; >>+ int l; >> int conv = 1; >> const u_char *cp, *dp, *dp1; >> u_char gentext[6], *wcp; >>@@ -531,7 +532,7 @@ >> * Filenames with some characters are not allowed! >> */ >> for (cp = un, i = unlen; i > 0;) >>- if (unix2doschr(&cp, (size_t *)&i, pmp) == 0) >>+ if (unix2doschr(&cp, &i, pmp) == 0) >> return 0; >> >> /* > > I'm no C expert.. but I'm guessin that (ssize_t) is a typo.. funny how it still works? From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 21:40:17 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 DBCCE16A4CE; Sat, 31 Jan 2004 21:40:17 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F2E743D2F; Sat, 31 Jan 2004 21:40:16 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i115diA0058659; Sat, 31 Jan 2004 21:39: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 i115dbmv058658; Sat, 31 Jan 2004 21:39:37 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Jan 2004 21:39:37 -0800 From: "David O'Brien" To: "Greg J." Message-ID: <20040201053937.GA58573@dragon.nuxi.com> References: <200401311932.37140.adridg@cs.kun.nl> <401C02A9.5030506@cox.net> <20040131205355.GY74366@funkthat.com> <401C8B3A.6030300@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <401C8B3A.6030300@cox.net> 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: Adriaan de Groot cc: John-Mark Gurney cc: freebsd-amd64@freebsd.org cc: Tim Robbins Subject: Re: msdosfs patch 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: Sun, 01 Feb 2004 05:40:18 -0000 On Sat, Jan 31, 2004 at 10:14:34PM -0700, Greg J. wrote: > >>+ ssize_t i, j; ... > >>- if (unix2doschr(&cp, (size_t *)&i, pmp) == 0) ... > I'm no C expert.. but I'm guessin that (ssize_t) is a typo.. funny how > it still works? ssize_t is signed size_t, an ISO-C type. One of the above is probably a typo - the question is did Tim want a signed or unsigned type. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 31 21:49: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 0EA3116A4CE for ; Sat, 31 Jan 2004 21:49:08 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03D2743D1D for ; Sat, 31 Jan 2004 21:49:05 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i115mxA0058810; Sat, 31 Jan 2004 21:48:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i115mu0s058809; Sat, 31 Jan 2004 21:48:56 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Jan 2004 21:48:56 -0800 From: "David O'Brien" To: Bill Squire Message-ID: <20040201054856.GB58573@dragon.nuxi.com> References: <1075530947.840.2.camel@.rochester.rr.com> <20040131074830.GA18624@dragon.nuxi.com> <1075535725.1189.4.camel@.rochester.rr.com> <20040131080038.GE18624@dragon.nuxi.com> <20040131193105.GA21759@curacao.n2it.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040131193105.GA21759@curacao.n2it.nl> 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: XFree86 build 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: Sun, 01 Feb 2004 05:49:08 -0000 On Sat, Jan 31, 2004 at 08:31:05PM +0100, Bill Squire wrote: > On Sat, Jan 31, 2004 at 12:00:38AM -0800, David O'Brien wrote: > > On Sat, Jan 31, 2004 at 02:55:25AM -0500, Jem Matzan wrote: > > > On Sat, 2004-01-31 at 02:48, David O'Brien wrote: > > > > On Sat, Jan 31, 2004 at 01:35:47AM -0500, Jem Matzan wrote: > > > > > What's in your /etc/make.conf? I have CPUTYPE?=?x86_64 for the CPU > > > > > type, > > > > > > > > That is so totally wrong, I don't know where the idea could have come > > > > from. There is a single AMD64 implimentation at this time, so there are > > > > no choices (or things to tweak). x86_64 is Linux's bastardized spelling > > > > of "AMD64". > > > > > > Hey that's wonderful, but do you have a suggestion as to what the > > > CPUTYPE should be? > > > > Yes, don't set it. > > Here is a question for David or anybody: > > CPUTYPE?=. is therefore correct? (or nothing at all?) That is still setting it -- to ".". Don't set it, don't have it anywhere, a grep of CPUTYPE of /etc/make.conf should show nothing. There is no need for it -- please think about what CPUTYPE is for? It isn't to tell the compiler on your Alpha system you want to generate sparc64 code. It is to tell the compiler which generation of a family you have, and what member of a CPU family to opimize for. There is a single AMD64 cpu so far -- K8. Since there is but one, there is nothing to tell the compiler -- it already knows everything there is to know. > The two settings below have worked well for some time now. Is this wrong > too? > > CPUTYPE?= amd64 > TARGET_ARCH?= amd64 Don't set TARGET_ARCH unless you are doing a cross-build. > Is there any chance of setting compatibility for "Linux's bastardized > spelling" of 'amd64' at the top level? (In /etc/make.conf ?) No, I personally will kill any proliferation of that bastardized spelling. > This is still one (if not the most) common trivial patch in the ports. Please show explicity where you are needing to specify it. With Kris and Co.'s /usr/ports/Templates the need should be minimal. > Placing -fPIC in CFLAGS= sometimes causes the compiler to bomb, while not > having it to make some some libs (in the right Makefile) will cause the > linker to bomb with a very Linux like "x86_64_32" in the error message. SPECIFICS please. It sounds like you are talking about relocations, but we need the specific details. > What gives? It certainly is "amd64", but "HAMMER" is still used to ID the > "amd64" in the kernel conf? Certainly I like what I have, but if there is > one and only one "amd64", calling it by atleast three names looks like > trouble. Hammer is the internal AMD code name for AMD64, it existed years before the term "AMD64" did. In GENERIC it tells the CPU family member. Maybe we should change it, but many of us like it. The kernel has place holders for future CPU families, like K9 and K10. From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 04:35:42 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 065F816A4CE for ; Sun, 1 Feb 2004 04:35:42 -0800 (PST) Received: from fed1mtao05.cox.net (fed1mtao05.cox.net [68.6.19.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 228FC43D2F for ; Sun, 1 Feb 2004 04:35:41 -0800 (PST) (envelope-from xcas@cox.net) Received: from localhost.bsd-unix.org ([68.2.134.143]) by fed1mtao05.cox.netSMTP <20040201123541.HXZM9536.fed1mtao05.cox.net@localhost.bsd-unix.org>; Sun, 1 Feb 2004 07:35:41 -0500 Date: Sun, 1 Feb 2004 05:36:53 -0700 From: "Greg J." To: Palle Girgensohn Message-Id: <20040201053653.1d92dd4d.xcas@cox.net> In-Reply-To: <106670000.1075569408@palle.girgensohn.se> References: <106670000.1075569408@palle.girgensohn.se> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; amd64-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: amd64@freebsd.org Subject: Re: please try this patch for: p5-postgresql-plperl-7.4.1 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: Sun, 01 Feb 2004 12:35:42 -0000 On Sat, 31 Jan 2004 18:16:48 +0100 Palle Girgensohn wrote: > Hi, > > Can someone on amd64 please try this patch for > databases/p5-postgresql-plperl. > > It's supposed to fix this problem: > rl-7.4.1.log> > > Thanks, > Palle > Worked. From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 04:36: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 D6E2D16A4CE for ; Sun, 1 Feb 2004 04:36:50 -0800 (PST) Received: from fed1mtao04.cox.net (fed1mtao04.cox.net [68.6.19.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id C024443D53 for ; Sun, 1 Feb 2004 04:36:47 -0800 (PST) (envelope-from xcas@cox.net) Received: from localhost.bsd-unix.org ([68.2.134.143]) by fed1mtao04.cox.netSMTP <20040201123647.FOFH29509.fed1mtao04.cox.net@localhost.bsd-unix.org>; Sun, 1 Feb 2004 07:36:47 -0500 Date: Sun, 1 Feb 2004 05:37:59 -0700 From: "Greg J." To: Palle Girgensohn Message-Id: <20040201053759.7dbed7b2.xcas@cox.net> In-Reply-To: <125210000.1075570485@palle.girgensohn.se> References: <125210000.1075570485@palle.girgensohn.se> X-Mailer: Sylpheed version 0.9.9 (GTK+ 1.2.10; amd64-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: amd64@freebsd.org Subject: Re: please try this patch for: postgresql-libpq++-4.0_1 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: Sun, 01 Feb 2004 12:36:51 -0000 On Sat, 31 Jan 2004 18:34:45 +0100 Palle Girgensohn wrote: > Hi, > > Can someone on amd64 try this patch by putting it in > ports/databases/postgresql-libpq++/files and try building the port? > > It's supposed to fix this problem: > -4.0_1.log> > > Thanks, > Palle > Didn't work. localhost# make ===> Extracting for postgresql-libpq++-4.0_1 >> Checksum OK for postgresql/libpq++-4.0.tar.gz. ===> Patching for postgresql-libpq++-4.0_1 ===> Applying FreeBSD patches for postgresql-libpq++-4.0_1 /usr/bin/sed -i.bak "s,/usr/local/pgsql,/usr/local,; s,^CFLAGS.*,CFLAGS=-O -pipe ,; s,\...SO_MINOR_VERSION.,,; s,\(\-[IL]\)[^/]*,\\1/usr/local," /usr/ports/databases/postgresql-libpq++/work/libpq++-4.0/Makefile ===> postgresql-libpq++-4.0_1 depends on executable: gmake - found ===> postgresql-libpq++-4.0_1 depends on shared library: pq.3 - found ===> Configuring for postgresql-libpq++-4.0_1 ===> Building for postgresql-libpq++-4.0_1 g++ -c -O -pipe -DHAVE_NAMESPACE_STD -DHAVE_CXX_STRING_HEADER -DDLLIMPORT="" -I/usr/local/include pgconnection.cc g++ -c -O -pipe -DHAVE_NAMESPACE_STD -DHAVE_CXX_STRING_HEADER -DDLLIMPORT="" -I/usr/local/include pgdatabase.cc g++ -c -O -pipe -DHAVE_NAMESPACE_STD -DHAVE_CXX_STRING_HEADER -DDLLIMPORT="" -I/usr/local/include pgtransdb.cc g++ -c -O -pipe -DHAVE_NAMESPACE_STD -DHAVE_CXX_STRING_HEADER -DDLLIMPORT="" -I/usr/local/include pgcursordb.cc g++ -c -O -pipe -DHAVE_NAMESPACE_STD -DHAVE_CXX_STRING_HEADER -DDLLIMPORT="" -I/usr/local/include pglobject.cc g++ -O -pipe pgconnection.o pgdatabase.o pgtransdb.o pgcursordb.o pglobject.o -L/usr/local/lib -lpq -fpic -fPIC -shared -Wl,-x,-soname,libpq++.so.4 -Wl,-rpath,/usr/local/lib -o libpq++.so.4 /usr/bin/ld: pgconnection.o: relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC pgconnection.o: could not read symbols: Bad value gmake: *** [libpq++.so.4] Error 1 *** Error code 2 Stop in /usr/ports/databases/postgresql-libpq++. localhost# From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 15:19:17 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 8730316A4CE for ; Sun, 1 Feb 2004 15:19:17 -0800 (PST) Received: from xyzzy.wireless.snsonline.net (office-fw.iexec.net.au [210.18.210.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E28F43D41 for ; Sun, 1 Feb 2004 15:19:15 -0800 (PST) (envelope-from msergeant@snsonline.net) Received: from xyzzy.wireless.snsonline.net (localhost [127.0.0.1]) i11NJYAM075778 for ; Mon, 2 Feb 2004 09:19:34 +1000 (EST) (envelope-from msergeant@snsonline.net) Received: (from msergeant@localhost)i11NJXT3075777 for amd64@freebsd.org; Mon, 2 Feb 2004 09:19:33 +1000 (EST) (envelope-from msergeant@snsonline.net) X-Authentication-Warning: xyzzy.wireless.snsonline.net: msergeant set sender to msergeant@snsonline.net using -f From: Mark Sergeant To: amd64@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-JMSEZoWMAf34LF0sXdaP" Organization: SNSOnline Technical Services Message-Id: <1075677572.1308.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 02 Feb 2004 09:19:33 +1000 Subject: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 23:19:17 -0000 --=-JMSEZoWMAf34LF0sXdaP Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Howdy all, I've just installed 5.2-RELEASE-AMD64 on a dual opteron 248 machine, with the following specs : Tyan Thunder Motherboard 2 x Opteron 248 2 x 1GB sticks PC 2700 ECC ram adaptec scsi raid card. raid 5 array + 1 hot spare. Motherboard has onboard video, dual intel gigabit nics (bge). The output from the dmesg can be found on www.snsonline.net/~sarge/amd64_dmesg.txt=20 The last freeze I had it was a panic, but the majority of the time the machine completely locks up. Any help people can give me would be much appreciated, I can't even do a build world as it fails within 5 minutes of kicking off the buildworld. Cheers, --=20 Mark Sergeant SNSOnline Technical Services --=-JMSEZoWMAf34LF0sXdaP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAHYmEbS4ZEpHb8t0RAtO7AJ9JDOMDG6CjQRXXIlf2fv4/gBTB3wCfQmzG raY8H0PlfylTrgHVNFVblKU= =sLhw -----END PGP SIGNATURE----- --=-JMSEZoWMAf34LF0sXdaP-- From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 15:35: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 F2BEB16A4CE for ; Sun, 1 Feb 2004 15:35:46 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2837D43D2D for ; Sun, 1 Feb 2004 15:35:45 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id SAA06578 for ; Sun, 1 Feb 2004 18:35:44 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Sun, 1 Feb 2004 18:34:17 -0500 Message-ID: From: "Haapanen, Tom" To: amd64@freebsd.org Date: Sun, 1 Feb 2004 18:34:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 23:35:47 -0000 Which Thunder model? K8S, K8S Pro, K8SR, K8W? I run a K8S Pro with dual 244s (couldn't find any 246s and the 248s were just too dear for me) and 2 GB ... and I started off with an Adaptec 2100S RAID, but had consistent panics when booting. Apparently the aac driver isn't exactly 64-bit clean. I switched to a used HP NetRAID 3Si (aka AMI MegaRAID 438), and the server has run beatifully since then. Now running an Opteron database server for our production web site! P.S. For best performance, I think you really want to run 4x 512 MB. Running with two DIMMs means either you only get 64-bit memory access (not 128-bit) or else you need to put both DIMMs into the CPU1 memory slots (which means CPU2 will have to access those through hypertransport). Tom -----Original Message----- From: Mark Sergeant [mailto:msergeant@snsonline.net] Sent: Sunday 01 February 2004 18:20 To: amd64@freebsd.org Subject: Dual processor, AMD 64 machine freezing. Howdy all, I've just installed 5.2-RELEASE-AMD64 on a dual opteron 248 machine, with the following specs : Tyan Thunder Motherboard 2 x Opteron 248 2 x 1GB sticks PC 2700 ECC ram adaptec scsi raid card. raid 5 array + 1 hot spare. Motherboard has onboard video, dual intel gigabit nics (bge). The output from the dmesg can be found on www.snsonline.net/~sarge/amd64_dmesg.txt The last freeze I had it was a panic, but the majority of the time the machine completely locks up. Any help people can give me would be much appreciated, I can't even do a build world as it fails within 5 minutes of kicking off the buildworld. Cheers, -- Mark Sergeant SNSOnline Technical Services From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 15:42:29 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 3EB9216A4CF for ; Sun, 1 Feb 2004 15:42:29 -0800 (PST) Received: from natrium.plan-ix.de (natrium.plan-ix.de [212.37.39.36]) by mx1.FreeBSD.org (Postfix) with SMTP id 3F3BC43D83 for ; Sun, 1 Feb 2004 15:41:34 -0800 (PST) (envelope-from braukmann@tse-online.de) Received: (qmail 29360 invoked from network); 1 Feb 2004 23:40:56 -0000 Received: from p50824382.dip0.t-ipconnect.de (HELO ?192.168.225.100?) (braukmann%tse-online.de@80.130.67.130) by natrium.plan-ix.de with SMTP; 1 Feb 2004 23:40:56 -0000 Date: Mon, 02 Feb 2004 00:40:56 +0100 From: Andreas Braukmann To: Mark Sergeant Message-ID: <1067800000.1075678856@cage.int.unixxinu.de> In-Reply-To: <1075677572.1308.8.camel@localhost> References: <1075677572.1308.8.camel@localhost> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 23:42:29 -0000 On 02/02/04 09:19:33 +1000 Mark Sergeant wrote: > I've just installed 5.2-RELEASE-AMD64 on a dual opteron 248 machine, > with the following specs : > > Tyan Thunder Motherboard Which model? There are several Thunder K8 Boards out there. K8S, K8S Pro, K8W, etc. Furthermore: which BIOS Release? I had trouble with all but the initial BIOS-Release for my Thunder K8S (2880) Boards under i386-stable and i386-current concerning interrupt routing issues (with and without ACPI). I hope testing the various BIOS revisions under amd64-current really soon. > 2 x Opteron 248 > 2 x 1GB sticks PC 2700 ECC ram > adaptec scsi raid card. > raid 5 array + 1 hot spare. > Motherboard has onboard video, dual intel gigabit nics (bge). Intel or Broadcom? The "intel" nics would be em(4), the Broadcom nics would be bge(4). The Thunder K8S comes with dual bge(4). >From the dmesg-output your board looks like the K8S (2880). You may try to downgrade your BIOS to V1.07. > The last freeze I had it was a panic, but the majority of the time the > machine completely locks up. Any help people can give me would be much > appreciated, I can't even do a build world as it fails within 5 minutes > of kicking off the buildworld. Looks quite like an interrupt storm. Do you mind showing the mptable output? My boards where rock-stable with complete unconfigured nics; since the culprit was a misrouted interrupt for the broadcoms. Sometimes doing an ifconfig was sufficient to "halt" the machine, sometimes I had to initiate a ftp transfer or other means to generate some network traffic. -Andreas From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 15:52:11 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 D6BD016A4CE for ; Sun, 1 Feb 2004 15:52:11 -0800 (PST) Received: from natrium.plan-ix.de (natrium.plan-ix.de [212.37.39.36]) by mx1.FreeBSD.org (Postfix) with SMTP id AEE6243D53 for ; Sun, 1 Feb 2004 15:51:40 -0800 (PST) (envelope-from braukmann@tse-online.de) Received: (qmail 29475 invoked from network); 1 Feb 2004 23:51:34 -0000 Received: from p50824382.dip0.t-ipconnect.de (HELO ?192.168.225.100?) (braukmann%tse-online.de@80.130.67.130) by natrium.plan-ix.de with SMTP; 1 Feb 2004 23:51:34 -0000 Date: Mon, 02 Feb 2004 00:51:34 +0100 From: Andreas Braukmann To: "Haapanen, Tom" Message-ID: <1071900000.1075679494@cage.int.unixxinu.de> In-Reply-To: References: X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: amd64@freebsd.org Subject: RE: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 23:52:12 -0000 On 02/01/04 18:34:10 -0500 Haapanen, Tom wrote: > I run a K8S Pro with dual 244s (couldn't find any 246s and the 248s were > just too dear for me) and 2 GB ... and I started off with an Adaptec 2100S > RAID, but had consistent panics when booting. Apparently the aac driver > isn't exactly 64-bit clean. The 2100S isn't driven by aac(4) but by asr(4). The asr-driver is in fact not 64-bit clean (as Scott Long stated multiple times :-/). The aac-driver is perfectly fine with the 64 bits (for me). It survives heavy i/o load without a hitch. I ran quite a bunch of tests (parallel bonnie++ spreaded over multiple raid volumes and multiple file systems, postmark, etc.) with my 2200S, 2120S and 5400S. > P.S. For best performance, I think you really want to run 4x 512 MB. > Running with two DIMMs means either you only get 64-bit memory access (not > 128-bit) or else you need to put both DIMMs into the CPU1 memory slots > (which means CPU2 will have to access those through hypertransport). Thats theory. ;-) Since the allocators don't know about the numa-like architecture memory would be accessed through hyptertransport (statistically) more or less "half of the time". (CPU0 ---> HT ---> MEM1 ; CPU1 ---> HT ---> MEM0) -Andreas From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 16:21:20 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 E2DFA16A4CE for ; Sun, 1 Feb 2004 16:21:20 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 958E943D5A for ; Sun, 1 Feb 2004 16:21:06 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id TAA08278 for ; Sun, 1 Feb 2004 19:21:06 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Sun, 1 Feb 2004 19:19:39 -0500 Message-ID: From: "Haapanen, Tom" To: amd64@freebsd.org Date: Sun, 1 Feb 2004 19:19:34 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 00:21:21 -0000 Whoops ... looks like I got my aac and asr mixed up! Sorry about that ... As for the memory allocation ... is that something that FreeBSD *could* do in the future? Would that fit in with the kernel architecture? And if that's not the case today, is there any advantage to balancing the memory between the two CPUs? Tom -----Original Message----- From: Andreas Braukmann [mailto:braukmann@tse-online.de] Sent: Sunday 01 February 2004 18:52 To: Haapanen, Tom Cc: amd64@freebsd.org Subject: RE: Dual processor, AMD 64 machine freezing. On 02/01/04 18:34:10 -0500 Haapanen, Tom wrote: > I run a K8S Pro with dual 244s (couldn't find any 246s and the 248s > were just too dear for me) and 2 GB ... and I started off with an > Adaptec 2100S RAID, but had consistent panics when booting. > Apparently the aac driver isn't exactly 64-bit clean. The 2100S isn't driven by aac(4) but by asr(4). The asr-driver is in fact not 64-bit clean (as Scott Long stated multiple times :-/). The aac-driver is perfectly fine with the 64 bits (for me). It survives heavy i/o load without a hitch. I ran quite a bunch of tests (parallel bonnie++ spreaded over multiple raid volumes and multiple file systems, postmark, etc.) with my 2200S, 2120S and 5400S. > P.S. For best performance, I think you really want to run 4x 512 MB. > Running with two DIMMs means either you only get 64-bit memory access > (not > 128-bit) or else you need to put both DIMMs into the CPU1 memory slots > (which means CPU2 will have to access those through hypertransport). Thats theory. ;-) Since the allocators don't know about the numa-like architecture memory would be accessed through hyptertransport (statistically) more or less "half of the time". (CPU0 ---> HT ---> MEM1 ; CPU1 ---> HT ---> MEM0) -Andreas From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 16:24:30 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 1331916A4CE for ; Sun, 1 Feb 2004 16:24:30 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BC9643D73 for ; Sun, 1 Feb 2004 16:24:20 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id TAA08393 for ; Sun, 1 Feb 2004 19:24:15 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Sun, 1 Feb 2004 19:22:49 -0500 Message-ID: From: "Haapanen, Tom" To: amd64@freebsd.org Date: Sun, 1 Feb 2004 19:22:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 00:24:30 -0000 K8S Pro includes two Broadcom (bge) NICs and one Intel (fxp) NIC. I run with bge0, and so far no problems (knock on wood). Tom -----Original Message----- From: Andreas Braukmann [mailto:braukmann@tse-online.de] Sent: Sunday 01 February 2004 18:41 To: Mark Sergeant Cc: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. > Motherboard has onboard video, dual intel gigabit nics (bge). Intel or Broadcom? The "intel" nics would be em(4), the Broadcom nics would be bge(4). The Thunder K8S comes with dual bge(4). [...] My boards where rock-stable with complete unconfigured nics; since the culprit was a misrouted interrupt for the broadcoms. Sometimes doing an ifconfig was sufficient to "halt" the machine, sometimes I had to initiate a ftp transfer or other means to generate some network traffic. -Andreas _______________________________________________ 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 1 16:49:10 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 047FA16A4CE for ; Sun, 1 Feb 2004 16:49:10 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD93743D54 for ; Sun, 1 Feb 2004 16:49:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i120n7A0094870; Sun, 1 Feb 2004 16:49:07 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i120n62U094869; Sun, 1 Feb 2004 16:49:06 -0800 (PST) (envelope-from obrien) Date: Sun, 1 Feb 2004 16:49:06 -0800 From: "David O'Brien" To: "Haapanen, Tom" Message-ID: <20040202004906.GA60117@dragon.nuxi.com> References: 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: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. 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, 02 Feb 2004 00:49:10 -0000 [ Tom, PLEASE don't top-post -- it looses context in follow ups ] On Sun, Feb 01, 2004 at 06:34:10PM -0500, Haapanen, Tom wrote: > P.S. For best performance, I think you really want to run 4x 512 MB. > Running with two DIMMs means either you only get 64-bit memory access (not > 128-bit) or else you need to put both DIMMs into the CPU1 memory slots > (which means CPU2 will have to access those through hypertransport). ... > From: Mark Sergeant [mailto:msergeant@snsonline.net] > 2 x 1GB sticks PC 2700 ECC ram Tom is very correct -- you want to populate memory in pairs per CPU. This is so you can use both channels of the DDR memory controller. If you only put one DIMM per CPU, you're missing 1/2 your potential bandwidth. Consult your motherboard manual to determine which DIMM slots make up a pairing, not all motherboards are the same. Also, you want to spread your memory out across all your CPU's to get max performance. Look in the freebsd-amd64 archives for where I've detailed it more. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 16:53:30 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 21EE816A4CE for ; Sun, 1 Feb 2004 16:53:30 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4AE043D2D for ; Sun, 1 Feb 2004 16:53:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i120rSA0094939; Sun, 1 Feb 2004 16:53:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i120rQte094934; Sun, 1 Feb 2004 16:53:26 -0800 (PST) (envelope-from obrien) Date: Sun, 1 Feb 2004 16:53:26 -0800 From: "David O'Brien" To: Andreas Braukmann Message-ID: <20040202005326.GB60117@dragon.nuxi.com> References: <1071900000.1075679494@cage.int.unixxinu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1071900000.1075679494@cage.int.unixxinu.de> 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: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. 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, 02 Feb 2004 00:53:30 -0000 On Mon, Feb 02, 2004 at 12:51:34AM +0100, Andreas Braukmann wrote: > > P.S. For best performance, I think you really want to run 4x 512 MB. > > Running with two DIMMs means either you only get 64-bit memory access (not > > 128-bit) or else you need to put both DIMMs into the CPU1 memory slots > > (which means CPU2 will have to access those through hypertransport). > > Thats theory. ;-) > Since the allocators don't know about the numa-like architecture > memory would be accessed through hyptertransport (statistically) > more or less "half of the time". (CPU0 ---> HT ---> MEM1 ; > CPU1 ---> HT ---> MEM0) Its not theory, its fact -- even w/o a NUMA aware OS. Statistically, 1/2 the accesses by a CPU are to local memory, 1/2 to distant memory. If you put all them memory on a single CPU then you've got two processors trying to access memory, saturating the memory controller on the single CPU with memory -- thus giving you less BW. Your diagram above leaves out the memory controller (and its request buffer). -- -- David (obrien@FreeBSD.org) P.S. I work at AMD From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 17:10:18 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 ACD5216A4CE for ; Sun, 1 Feb 2004 17:10:18 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A48E343D55 for ; Sun, 1 Feb 2004 17:10:16 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i121AGFR013973 for ; Sun, 1 Feb 2004 17:10: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 i121AG8U013972; Sun, 1 Feb 2004 17:10:16 -0800 (PST) (envelope-from gnats) Resent-Date: Sun, 1 Feb 2004 17:10:16 -0800 (PST) Resent-Message-Id: <200402020110.i121AG8U013972@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, Sebastian Blum Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F378516A4CE for ; Sun, 1 Feb 2004 17:02:33 -0800 (PST) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DF6C43D1F for ; Sun, 1 Feb 2004 17:02:33 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i1212WdL013516 for ; Sun, 1 Feb 2004 17:02:32 -0800 (PST) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.10/8.12.10/Submit) id i1212WkW013515; Sun, 1 Feb 2004 17:02:32 -0800 (PST) (envelope-from nobody) Message-Id: <200402020102.i1212WkW013515@www.freebsd.org> Date: Sun, 1 Feb 2004 17:02:32 -0800 (PST) From: Sebastian Blum To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.0 Subject: amd64/62239: GDT8514RZ freezes System after a few Minutes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 01:10:18 -0000 >Number: 62239 >Category: amd64 >Synopsis: GDT8514RZ freezes System after a few Minutes >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 01 17:10:16 PST 2004 >Closed-Date: >Last-Modified: >Originator: Sebastian Blum >Release: 5.2 >Organization: >Environment: FreeBSD wilson.office.ableton.com 5.2-RELEASE FreeBSD 5.2-RELEASE #1: Mon Feb 2 01:54:44 CET 2004 root@wilson.office.ableton.com:/usr/src/sys/amd64/compile/TEST amd64 >Description: System freezes after running 10-15 Minutes. >How-To-Repeat: Just wait 10-15 Minutes >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 17:19: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 7A6D916A4CE for ; Sun, 1 Feb 2004 17:19:24 -0800 (PST) Received: from xyzzy.wireless.snsonline.net (office-fw.iexec.net.au [210.18.210.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B6F243D2D for ; Sun, 1 Feb 2004 17:19:22 -0800 (PST) (envelope-from msergeant@iexec.com.au) Received: from xyzzy.wireless.snsonline.net (localhost [127.0.0.1]) i121JaAM083747 for ; Mon, 2 Feb 2004 11:19:36 +1000 (EST) (envelope-from msergeant@iexec.com.au) Received: (from msergeant@localhost)i121JZFA083746 for amd64@freebsd.org; Mon, 2 Feb 2004 11:19:35 +1000 (EST) (envelope-from msergeant@iexec.com.au) X-Authentication-Warning: xyzzy.wireless.snsonline.net: msergeant set sender to msergeant@iexec.com.au using -f From: Mark Sergeant To: amd64@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uBixTccRthvd+eEt8SRO" Organization: iExec.com.au Corporate Internet Solutions Message-Id: <1075684775.1308.24.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 02 Feb 2004 11:19:35 +1000 Subject: [Fwd: Re: Dual processor, AMD 64 machine freezing.] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 01:19:24 -0000 --=-uBixTccRthvd+eEt8SRO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable It should be noted that I was able to do a make world & kernel without the machine hanging on the local console. When I rebooted the machine and typed ifconfig the machine again hung so this seems to be pointing to network issues for sure. What are the thoughts on dropping in an fxp0 card. Cheers, Mark -----Forwarded Message----- > From: Mark Sergeant > To: Andreas Braukmann > Subject: Re: Dual processor, AMD 64 machine freezing. > Date: Mon, 02 Feb 2004 10:00:23 +1000 >=20 > On Mon, 2004-02-02 at 09:40, Andreas Braukmann wrote: > > On 02/02/04 09:19:33 +1000 Mark Sergeant wrote: > > > I've just installed 5.2-RELEASE-AMD64 on a dual opteron 248 machine, > > > with the following specs : > > >=20 > > > Tyan Thunder Motherboard > >=20 > > Which model? There are several Thunder K8 Boards out there. > > K8S, K8S Pro, K8W, etc.=20 >=20 > K8S 2880 > >=20 > > Furthermore: which BIOS Release? > > I had trouble with all but the initial BIOS-Release for my > > Thunder K8S (2880) Boards under i386-stable and i386-current > > concerning interrupt routing issues (with and without ACPI). > > I hope testing the various BIOS revisions under amd64-current > > really soon. > >=20 > > > 2 x Opteron 248 > > > 2 x 1GB sticks PC 2700 ECC ram > > > adaptec scsi raid card. > > > raid 5 array + 1 hot spare. > > > Motherboard has onboard video, dual intel gigabit nics (bge). > >=20 > > Intel or Broadcom? The "intel" nics would be em(4), the Broadcom > > nics would be bge(4). The Thunder K8S comes with dual bge(4). > > >From the dmesg-output your board looks like the K8S (2880). > > You may try to downgrade your BIOS to V1.07. >=20 > My mistake, I looked at the chip on the motherboard and it said intel > gigabit, these are broadcom's which I have had trouble with previously > with an smp setup. I've got the v1.07 bios installed at the moment. >=20 > >=20 > > > The last freeze I had it was a panic, but the majority of the time th= e > > > machine completely locks up. Any help people can give me would be muc= h > > > appreciated, I can't even do a build world as it fails within 5 minut= es > > > of kicking off the buildworld. > >=20 > > Looks quite like an interrupt storm. > >=20 > > Do you mind showing the mptable output? >=20 > http://www.snsonline.net/~sarge/mptable.out >=20 > >=20 > > My boards where rock-stable with complete unconfigured nics; since > > the culprit was a misrouted interrupt for the broadcoms. Sometimes > > doing an ifconfig was sufficient to "halt" the machine, sometimes > > I had to initiate a ftp transfer or other means to generate some > > network traffic. > >=20 >=20 > I do have to agree that this seems to be a problem with the onboard > nics, I'm contemplating dropping in an fxp0 nic, but I do really need > the onboard gigs :/ >=20 > > -Andreas --=20 Mark Sergeant iExec.com.au Corporate Internet Solutions --=-uBixTccRthvd+eEt8SRO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAHaWnWD+Xz176H/0RAutvAKC6qSWh3FvZFOa88bOyHYee3zHLegCfTnCv oZe7B7nzFWpaEWZkM7vbYrM= =3aVl -----END PGP SIGNATURE----- --=-uBixTccRthvd+eEt8SRO-- From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 18:06:17 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 3CC4116A4CE for ; Sun, 1 Feb 2004 18:06:17 -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 18FB443D48 for ; Sun, 1 Feb 2004 18:06:15 -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 i1226Do8036118 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 1 Feb 2004 20:06:13 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i1226DVH036115; Sun, 1 Feb 2004 20:06:13 -0600 (CST) Date: Sun, 1 Feb 2004 20:06:13 -0600 (CST) Message-Id: <200402020206.i1226DVH036115@bigtex.jrv.org> From: James Van Artsdalen To: msergeant@snsonline.net In-reply-to: <1075677572.1308.8.camel@localhost> (message from Mark Sergeant on Mon, 02 Feb 2004 09:19:33 +1000) References: <1075677572.1308.8.camel@localhost> cc: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 02:06:17 -0000 > From: Mark Sergeant > Date: Mon, 02 Feb 2004 09:19:33 +1000 > > I've just installed 5.2-RELEASE-AMD64 on a dual opteron 248 machine, > with the following specs : > > Tyan Thunder Motherboard > 2 x Opteron 248 > 2 x 1GB sticks PC 2700 ECC ram > adaptec scsi raid card. > raid 5 array + 1 hot spare. > Motherboard has onboard video, dual intel gigabit nics (bge). Is any of the hardware new or has it all been burned in together? From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 18: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 9F1C816A4CE for ; Sun, 1 Feb 2004 18:08:24 -0800 (PST) Received: from xyzzy.wireless.snsonline.net (office-fw.iexec.net.au [210.18.210.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DE8643D1D for ; Sun, 1 Feb 2004 18:08:22 -0800 (PST) (envelope-from msergeant@snsonline.net) Received: from xyzzy.wireless.snsonline.net (localhost [127.0.0.1]) i1228gAM083989; Mon, 2 Feb 2004 12:08:42 +1000 (EST) (envelope-from msergeant@snsonline.net) Received: (from msergeant@localhost)i1228eOl083988; Mon, 2 Feb 2004 12:08:40 +1000 (EST) (envelope-from msergeant@snsonline.net) X-Authentication-Warning: xyzzy.wireless.snsonline.net: msergeant set sender to msergeant@snsonline.net using -f From: Mark Sergeant To: James Van Artsdalen In-Reply-To: <200402020206.i1226DVH036115@bigtex.jrv.org> References: <1075677572.1308.8.camel@localhost> <200402020206.i1226DVH036115@bigtex.jrv.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-KSjhwhoh5dx5gjxaK+F7" Organization: SNSOnline Technical Services Message-Id: <1075687720.1308.28.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 02 Feb 2004 12:08:40 +1000 cc: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 02:08:24 -0000 --=-KSjhwhoh5dx5gjxaK+F7 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hardware is all brand new, just built the box and then built the raid array, then installed the OS. Now when trying to get stuff happening over the network it's freezing up, no good for something that is meant to be in production at the end of the day. Especially as a db server. On Mon, 2004-02-02 at 12:06, James Van Artsdalen wrote: > > From: Mark Sergeant > > Date: Mon, 02 Feb 2004 09:19:33 +1000 > >=20 > > I've just installed 5.2-RELEASE-AMD64 on a dual opteron 248 machine, > > with the following specs : > >=20 > > Tyan Thunder Motherboard > > 2 x Opteron 248 > > 2 x 1GB sticks PC 2700 ECC ram > > adaptec scsi raid card. > > raid 5 array + 1 hot spare. > > Motherboard has onboard video, dual intel gigabit nics (bge). >=20 > Is any of the hardware new or has it all been burned in together? --=20 Mark Sergeant SNSOnline Technical Services --=-KSjhwhoh5dx5gjxaK+F7 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAHbEnbS4ZEpHb8t0RAtY0AJ9DooLBHKPL1aGJsqCGqWJ5uj/pfQCggdBp 64WBmu1A0BHcYprjHpCtzPM= =HClU -----END PGP SIGNATURE----- --=-KSjhwhoh5dx5gjxaK+F7-- From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 1 18:47: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 DAC2E16A4CE for ; Sun, 1 Feb 2004 18:47:02 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B2B443D3F for ; Sun, 1 Feb 2004 18:47:01 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id VAA13204 for ; Sun, 1 Feb 2004 21:47:01 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Sun, 1 Feb 2004 21:45:35 -0500 Message-ID: From: "Haapanen, Tom" To: amd64@freebsd.org Date: Sun, 1 Feb 2004 21:45:29 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 02:47:03 -0000 David O'Brien wrote: > Its not theory, its fact -- even w/o a NUMA aware OS. Statistically, 1/2 > the accesses by a CPU are to local memory, 1/2 to distant memory. If > you put all them memory on a single CPU then you've got two > processors trying to access memory, saturating the memory controller > on the single CPU with memory -- thus giving you less BW. Your diagram > above leaves out the memory controller (and its request buffer). But isn't that (the 50-50 CPU memory access split) assuming that there is no CPU-awareness in memory allocation? Suppose that I have process/thread X running on CPU 1, and the OS kernel is clever enough to allocate physical pages located on CPU 1's memory bank whenever thread X requests new memory. In that scenario, wouldn't it be reasonable to assume that more than 50% of memory accesses are local? Of course, having processes and/or threads that have CPU affinity would help a whole lot, too. Is this ... (a) an incorrect assumption; or (b) impractical to implement, given virtual memory etc.? Tom From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 01:56:54 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 6471016A4CE for ; Mon, 2 Feb 2004 01:56:54 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60ED843D45 for ; Mon, 2 Feb 2004 01:56:53 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i129uqA0025099 for ; Mon, 2 Feb 2004 01:56:52 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i129uqwq025098 for freebsd-amd64@freebsd.org; Mon, 2 Feb 2004 01:56:52 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Feb 2004 01:56:52 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20040202095652.GA25017@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Subject: (FWD) FreeBSD 5.2.1-RC available 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, 02 Feb 2004 09:56:54 -0000 Note 5.2.1 also adds the Silicon Image 3114 SATA support needed to install on a SATA drive in many Opteron systems. -- David ----- Forwarded message from Scott Long ----- Date: Mon, 02 Feb 2004 02:16:22 -0700 Based on user feedback from the FreeBSD 5.2 release, we have decided to make several targeted improvements to the RELENG_5_2 branch and re-release it as FreeBSD 5.2.1. The complete list of changes can be found in the release notes, but the major items are: - many improvements and fixes to the ATA driver - new kdeadmin3 package to address the 'KUser' problem - fixes to several network drivers, IPSec, NFSv4, and NNS. - fix for the cd bootloader code to handle USB cdrom drives. ----- End forwarded message ----- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:06: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 81FF816A4CE for ; Mon, 2 Feb 2004 02:06:36 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3FD243D58 for ; Mon, 2 Feb 2004 02:06:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i12A6WA0025275; Mon, 2 Feb 2004 02:06:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i12A6WVJ025274; Mon, 2 Feb 2004 02:06:32 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Feb 2004 02:06:32 -0800 From: "David O'Brien" To: "Haapanen, Tom" Message-ID: <20040202100632.GA25194@dragon.nuxi.com> References: 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: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: 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, 02 Feb 2004 10:06:36 -0000 On Sun, Feb 01, 2004 at 09:45:29PM -0500, Haapanen, Tom wrote: > David O'Brien wrote: > > Its not theory, its fact -- even w/o a NUMA aware OS. Statistically, 1/2 > > the accesses by a CPU are to local memory, 1/2 to distant memory. If > > you put all them memory on a single CPU then you've got two > > processors trying to access memory, saturating the memory controller > > on the single CPU with memory -- thus giving you less BW. Your diagram > > above leaves out the memory controller (and its request buffer). > > But isn't that (the 50-50 CPU memory access split) assuming that there is no > CPU-awareness in memory allocation? Yes. > Suppose that I have process/thread X running on CPU 1, and the OS kernel is > clever enough to allocate physical pages located on CPU 1's memory bank > whenever thread X requests new memory. In that scenario, wouldn't it be > reasonable to assume that more than 50% of memory accesses are local? Yes. However, this part of this thread started with the assumption that the OS was not NUMA aware. (unless I misread eariler emails) > Of course, having processes and/or threads that have CPU affinity would help > a whole lot, too. > > Is this ... > (a) an incorrect assumption; or > (b) impractical to implement, given virtual memory etc.? Not impractical -- Linux for AMD64 has NUMA support. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:13:37 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 887BD16A4CE; Mon, 2 Feb 2004 02:13:37 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6AAD43D1F; Mon, 2 Feb 2004 02:13:36 -0800 (PST) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) i12ADaFR017920; Mon, 2 Feb 2004 02:13:36 -0800 (PST) (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i12ADaOG017916; Mon, 2 Feb 2004 02:13:36 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Feb 2004 02:13:36 -0800 (PST) From: "David E. O'Brien" Message-Id: <200402021013.i12ADaOG017916@freefall.freebsd.org> To: basti@ableton.com, obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/62239: GDT8514RZ freezes System after a few Minutes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 10:13:37 -0000 Synopsis: GDT8514RZ freezes System after a few Minutes State-Changed-From-To: open->analyzed State-Changed-By: obrien State-Changed-When: Mon Feb 2 02:10:52 PST 2004 State-Changed-Why: Not enough details to do anything with. Submitter needs to add some details -- starting with what in the world is a "GDT8514RZ"? Also what motherboard do you have? What CPU(s)? What memory? Is the system stable with out the "GDT8514RZ" (what ever it is)? http://www.freebsd.org/cgi/query-pr.cgi?pr=62239 From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:16:15 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 6D8CF16A4CE for ; Mon, 2 Feb 2004 02:16:15 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 712DF43D1D for ; Mon, 2 Feb 2004 02:16:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i12AGBA0025533; Mon, 2 Feb 2004 02:16:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i12AGBIm025532; Mon, 2 Feb 2004 02:16:11 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Feb 2004 02:16:11 -0800 From: "David O'Brien" To: Mark Sergeant Message-ID: <20040202101611.GD25194@dragon.nuxi.com> References: <1075684775.1308.24.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1075684775.1308.24.camel@localhost> 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: amd64@freebsd.org Subject: Re: [Fwd: Re: Dual processor, AMD 64 machine freezing.] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: 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, 02 Feb 2004 10:16:15 -0000 On Mon, Feb 02, 2004 at 11:19:35AM +1000, Mark Sergeant wrote: > It should be noted that I was able to do a make world & kernel without > the machine hanging on the local console. When I rebooted the machine > and typed ifconfig the machine again hung so this seems to be pointing > to network issues for sure. [ context lost to top posting :-( ] I don't think you mentioned, what kernel are you running? 5.2-RELEASE, or 5.2-CURRENT? From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:20:13 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 6A9E716A4CE for ; Mon, 2 Feb 2004 02:20:13 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88A4B43D31 for ; Mon, 2 Feb 2004 02:20:12 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i12AKCFR018038 for ; Mon, 2 Feb 2004 02:20:12 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i12AKCfu018037; Mon, 2 Feb 2004 02:20:12 -0800 (PST) (envelope-from gnats) Date: Mon, 2 Feb 2004 02:20:12 -0800 (PST) Message-Id: <200402021020.i12AKCfu018037@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "David O'Brien" Subject: Re: amd64/62239: GDT8514RZ freezes System after a few Minutes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David O'Brien List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 10:20:13 -0000 The following reply was made to PR amd64/62239; it has been noted by GNATS. From: "David O'Brien" To: Sebastian Blum Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/62239: GDT8514RZ freezes System after a few Minutes Date: Mon, 2 Feb 2004 02:10:39 -0800 On Sun, Feb 01, 2004 at 05:02:32PM -0800, Sebastian Blum wrote: > >Number: 62239 > >Category: amd64 > >Synopsis: GDT8514RZ freezes System after a few Minutes Please add some detail. What in the world is a "GDT8514RZ"? What motherboard do you have? What CPU(s)? What memory? Is the system stable with out the "GDT8514RZ" (what ever it is)? From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:33: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 DDC6216A4CE for ; Mon, 2 Feb 2004 02:33:47 -0800 (PST) Received: from xyzzy.wireless.snsonline.net (xyzzy.snsonline.net [210.18.214.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90D8043D2D for ; Mon, 2 Feb 2004 02:33:45 -0800 (PST) (envelope-from msergeant@iexec.com.au) Received: from xyzzy.wireless.snsonline.net (localhost [127.0.0.1]) i12AY172002245 for ; Mon, 2 Feb 2004 20:34:03 +1000 (EST) (envelope-from msergeant@iexec.com.au) Received: (from msergeant@localhost)i12AXxjo002244 for amd64@freebsd.org; Mon, 2 Feb 2004 20:33:59 +1000 (EST) (envelope-from msergeant@iexec.com.au) X-Authentication-Warning: xyzzy.wireless.snsonline.net: msergeant set sender to msergeant@iexec.com.au using -f From: Mark Sergeant To: amd64@freebsd.org In-Reply-To: <20040202101611.GD25194@dragon.nuxi.com> References: <1075684775.1308.24.camel@localhost> <20040202101611.GD25194@dragon.nuxi.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-etjE3ev4kWM6KPWgPtN5" Organization: iExec.com.au Corporate Internet Solutions Message-Id: <1075718039.1297.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 02 Feb 2004 20:33:59 +1000 Subject: Re: [Fwd: Re: Dual processor, AMD 64 machine freezing.] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 10:33:48 -0000 --=-etjE3ev4kWM6KPWgPtN5 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-02-02 at 20:16, David O'Brien wrote: > On Mon, Feb 02, 2004 at 11:19:35AM +1000, Mark Sergeant wrote: > > It should be noted that I was able to do a make world & kernel without > > the machine hanging on the local console. When I rebooted the machine > > and typed ifconfig the machine again hung so this seems to be pointing > > to network issues for sure. >=20 > [ context lost to top posting :-( ] >=20 > I don't think you mentioned, what kernel are you running? 5.2-RELEASE, > or 5.2-CURRENT? 5.2-RELEASE I was running, as mentioned in my dmesg. The reason for the top post was due to the fact it was forwarded, the rest was done with context throughout the forwarded post. I've since reverted to 5.2-RELEASE-P1 using the i386 installation as even after disabling the onboard nics lockups were still being experienced. The machine would also panic on the init 6 / reboot / shutdown -r now, command being issued. It should be noted no problems have been experienced using -i386 instead of -amd64. Cheers, --=20 Mark Sergeant iExec.com.au Corporate Internet Solutions --=-etjE3ev4kWM6KPWgPtN5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAHieWWD+Xz176H/0RAixeAJwLr+cdhl/nDBBp/tzMyexRB79PjgCg7lCC 726yGhy5pPdHo0y3MhxJDKo= =1TEX -----END PGP SIGNATURE----- --=-etjE3ev4kWM6KPWgPtN5-- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:42:31 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 5B9E116A4CE for ; Mon, 2 Feb 2004 02:42:31 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8563F43D3F for ; Mon, 2 Feb 2004 02:42:29 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id FAA01809 for ; Mon, 2 Feb 2004 05:42:28 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Mon, 2 Feb 2004 05:41:02 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Mon, 2 Feb 2004 05:40:59 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: amd64/62239: GDT8514RZ freezes System after a few Minutes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 10:42:31 -0000 David O'Brien wrote: > Please add some detail. What in the world is a "GDT8514RZ"? > What motherboard do you have? What CPU(s)? What memory? > Is the system stable with out the "GDT8514RZ" (what ever it is)? As far as I know, the GDT8514RZ is a RAID controller from ICP -- I think it uses the iir driver. I saw that some other people had freezing problems with it with FreeBSD/i386 when using RAID 4 or RAID 5, so this may have nothing to do with amd64. My web search also indicated that beta controller firmware from ICP may fix this issue. Tom From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 02:44: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 6365A16A4CE for ; Mon, 2 Feb 2004 02:44:50 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 579F043D45 for ; Mon, 2 Feb 2004 02:44:49 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id FAA01911 for ; Mon, 2 Feb 2004 05:44:49 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Mon, 2 Feb 2004 05:43:23 -0500 Message-ID: From: "Haapanen, Tom" To: "'amd64@freebsd.org'" Date: Mon, 2 Feb 2004 05:43:15 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: RE: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 10:44:50 -0000 David O'Brien wrote: > Not impractical -- Linux for AMD64 has NUMA support. So the follow-up question -- you must be expecting this already: is NUMA support on the roadmap for FreeBSD/amd64? Tom From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 03:45: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 D153516A4CE; Mon, 2 Feb 2004 03:45:33 -0800 (PST) Received: from smtp.helinet.de (smtp.helinet.de [212.37.38.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B86D43D2F; Mon, 2 Feb 2004 03:45:29 -0800 (PST) (envelope-from braukmann@tse-online.de) Date: Mon, 02 Feb 2004 12:45:18 +0100 From: Andreas Braukmann To: obrien@freebsd.org Message-ID: <2147483647.1075725918@[192.168.111.140]> In-Reply-To: <20040202005326.GB60117@dragon.nuxi.com> References: <20040202005326.GB60117@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030314-p2 (Debian) at helinet.de cc: amd64@freebsd.org Subject: Re: Dual processor, AMD 64 machine freezing. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 11:45:33 -0000 --On Sonntag, 1. Februar 2004 16:53 Uhr -0800 David O'Brien wrote: > On Mon, Feb 02, 2004 at 12:51:34AM +0100, Andreas Braukmann wrote: >> > P.S. For best performance, I think you really want to run 4x 512 MB. >> > Running with two DIMMs means either you only get 64-bit memory access (not >> > 128-bit) or else you need to put both DIMMs into the CPU1 memory slots >> > (which means CPU2 will have to access those through hypertransport). >> >> That's theory. ;-) >> Since the allocators don't know about the numa-like architecture >> memory would be accessed through hyptertransport (statistically) >> more or less "half of the time". (CPU0 ---> HT ---> MEM1 ; >> CPU1 ---> HT ---> MEM0) > > Its not theory, its fact -- even w/o a NUMA aware OS. Statistically, 1/2 > the accesses by a CPU are to local memory, 1/2 to distant memory. If you > put all them memory on a single CPU then you've got two processors trying > to access memory, saturating the memory controller on the single CPU with > memory -- thus giving you less BW. You are right, of course. I have two nearly identical systems. One is equipped with two 1 GByte Dimms both connected to CPU0, the second is equipped with four 512 MByte Dimms (2 at CPU0 and 2 at CPU1). My "real world" benchmarks (no micro- benchmarking involved) showed, that the system with memory on both CPUs performs minimal better (<< 5%) than the system having its complete RAM on one CPU. Choosing a configuration that allows to make use of both memory controller channels (even using only one CPU's controller) pays of significantly (20% - 30%). Especially for the K8S (having only 4 + 2 DIMM-slots) I would rather buy 2 * 1 GByte Dimms (to be able to simply add two more). > Your diagram above leaves out the memory controller (and its request buffer). Point taken. My remark was over simplified and not to the point. -Andreas From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 03:51:51 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 D3CDD16A4CE for ; Mon, 2 Feb 2004 03:51:51 -0800 (PST) Received: from smtp.helinet.de (smtp.helinet.de [212.37.38.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1342843D45 for ; Mon, 2 Feb 2004 03:51:46 -0800 (PST) (envelope-from braukmann@tse-online.de) Date: Mon, 02 Feb 2004 12:51:39 +0100 From: Andreas Braukmann To: Mark Sergeant Message-ID: <2147483647.1075726299@[192.168.111.140]> In-Reply-To: <1075684775.1308.24.camel@localhost> References: <1075684775.1308.24.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030314-p2 (Debian) at helinet.de cc: amd64@freebsd.org Subject: Re: [Fwd: Re: Dual processor, AMD 64 machine freezing.] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 11:51:52 -0000 --On Montag, 2. Februar 2004 11:19 Uhr +1000 Mark Sergeant wrote: > It should be noted that I was able to do a make world & kernel without > the machine hanging on the local console. When I rebooted the machine > and typed ifconfig the machine again hung so this seems to be pointing > to network issues for sure. What are the thoughts on dropping in an fxp0 > card. You should be able to get the interrupt routing right by en- and disabling "the right"[tm] devices in the BIOS-setup. I don't have access to my machines right now, but if I remember correctly, it was best to just leave all devices enabled. Don't even think about switching the (S-)ATA devices or the SCSI devices off. I may have some time for BIOS/K8S/amd64 experiments in the later evening (living in GMT+0100). -Andreas From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 11:02: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 838DE16A4CF for ; Mon, 2 Feb 2004 11:02:16 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D4E543D6A for ; Mon, 2 Feb 2004 11:01:42 -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 i12J1XFR020470 for ; Mon, 2 Feb 2004 11:01:33 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i12J1X8s020464 for freebsd-amd64@freebsd.org; Mon, 2 Feb 2004 11:01:33 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 2 Feb 2004 11:01:33 -0800 (PST) Message-Id: <200402021901.i12J1X8s020464@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 19:02:16 -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 685C616A4DD for ; Mon, 2 Feb 2004 11:50:15 -0800 (PST) Received: from hotmail.com (bay13-dav14.bay13.hotmail.com [64.4.31.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 228E443D1F for ; Mon, 2 Feb 2004 11:50:14 -0800 (PST) (envelope-from ginofontana@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 2 Feb 2004 11:50:13 -0800 Received: from 81.240.34.22 by bay13-dav14.bay13.hotmail.com with DAV; Mon, 02 Feb 2004 19:50:13 +0000 X-Originating-IP: [81.240.34.22] X-Originating-Email: [ginofontana@hotmail.com] X-Sender: ginofontana@hotmail.com From: "gino fontana" To: Date: Mon, 2 Feb 2004 20:50:10 +0100 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 Message-ID: X-OriginalArrivalTime: 02 Feb 2004 19:50:13.0948 (UTC) FILETIME=[C631AFC0:01C3E9C5] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: ou telecharger X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 19:50:15 -0000 ou t=E9l=E9charger un systeme freebsdd pour un amd 2400xp+ merci From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 12:09:22 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 1FBD916A4CE for ; Mon, 2 Feb 2004 12:09:22 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBACD43D5C for ; Mon, 2 Feb 2004 12:09:19 -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 i12K9IRv023559; Mon, 2 Feb 2004 21:09:18 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Mon, 2 Feb 2004 21:09:12 +0100 User-Agent: KMail/1.6.50 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200402022109.18509.adridg@cs.kun.nl> cc: gino fontana Subject: Re: ou telecharger X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 20:09:22 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 02 February 2004 20:50, gino fontana wrote: > ou t=E9l=E9charger un systeme freebsdd pour un amd 2400xp+ Bonsoir, Gino, La liste freebsd-amd64 est une liste en anglais, nous ne pouvons pas t'aide= r=20 en fran=E7ais. H=E9las. Meme qu'un amd 2400xp+ n'est pas un amd64, mais un = amd=20 ordinaire; =E7a veut dire qu'il est un i386 ordinateur. Tu peux t=E9l=E9cha= rger=20 l'ISO de FreeBSD 4.9 =E1 la fichier (?) web ftp://ftp.freebsd.org/pub/FreeB= SD/;=20 il y'a d'informations additionels =E1=20 http://www.freebsd.org/doc/fr_FR.ISO8859-1/books/handbook/mirrors.html (en= =20 fran=E7ais, du tout!) ['ebe, Gino. This list is in english. What's more, an amd 2400xp+ isn't an= =20 AMD64, but an i386. Download FreeBSD here, or RTFH here (in french, even).] =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot The users that I support would double-click on a landmine to see what it di= d. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAHq5udqzuAf6io/4RAjMwAJ95wj/cYZBHcbLQXrlALp7WB8eRcwCdHDdB 9/ihKuz+dXnfLlWGJG4E/Fk=3D =3DvoCL =2D----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 12:20:41 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 8894316A4CE; Mon, 2 Feb 2004 12:20:41 -0800 (PST) Received: from tor-adm1.nbc.attcanada.ca (tor-adm1.business.allstream.net [207.181.89.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB5DC43D3F; Mon, 2 Feb 2004 12:20:39 -0800 (PST) (envelope-from taob@risc.org) Received: from tor-adm1.nbc.attcanada.ca (localhost [127.0.0.1]) i12KKdwH023177; Mon, 2 Feb 2004 15:20:39 -0500 (EST) Received: from localhost (ncc0070@localhost)i12KKc6F023174; Mon, 2 Feb 2004 15:20:38 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.attcanada.ca: ncc0070 owned process doing -bs Date: Mon, 2 Feb 2004 15:20:38 -0500 (EST) From: Brian Tao X-Sender: ncc0070@tor-adm1.nbc.attcanada.ca To: "David O'Brien" In-Reply-To: <20040202095652.GA25017@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: (FWD) FreeBSD 5.2.1-RC available X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 20:20:41 -0000 On Mon, 2 Feb 2004, David O'Brien wrote: > > Note 5.2.1 also adds the Silicon Image 3114 SATA support needed to > install on a SATA drive in many Opteron systems. Sweet... my afternoon meeting at the office has been cancelled, and this is the perfect excuse for me to "work from home" for the rest of the day. ;-) 5.2-CURRENT kernels are panicking on my machine when it tries to probe the S-ATA interfaces on my Tyan Tiger K8W. I need to disable it in the BIOS before I can successfully boot... I'll see if 5.2.1 is any different. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 14:22:46 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 CC3DE16A4CE for ; Mon, 2 Feb 2004 14:22:46 -0800 (PST) Received: from natrium.plan-ix.de (natrium.plan-ix.de [212.37.39.36]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D7AE43D75 for ; Mon, 2 Feb 2004 14:22:08 -0800 (PST) (envelope-from braukmann@tse-online.de) Received: (qmail 67466 invoked from network); 2 Feb 2004 22:22:02 -0000 Received: from unknown (HELO ?192.168.222.11?) (ab%plan-ix.de@212.37.49.203) by natrium.plan-ix.de with SMTP; 2 Feb 2004 22:22:02 -0000 Date: Mon, 02 Feb 2004 23:23:14 +0100 From: Andreas Braukmann To: Mark Sergeant Message-ID: <2147483647.1075764194@[192.168.222.11]> In-Reply-To: <1075684775.1308.24.camel@localhost> References: <1075684775.1308.24.camel@localhost> X-Mailer: Mulberry/3.1.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: amd64@freebsd.org Subject: Re: [Fwd: Re: Dual processor, AMD 64 machine freezing.] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 22:22:46 -0000 --On Montag, 2. Februar 2004 11:19 Uhr +1000 Mark Sergeant wrote: > It should be noted that I was able to do a make world & kernel without > the machine hanging on the local console. hmmmpf. No irq-routing-guru hanging around? > -----Forwarded Message----- >> From: Mark Sergeant >> To: Andreas Braukmann >> Subject: Re: Dual processor, AMD 64 machine freezing. >> > > 2 x Opteron 248 >> > > 2 x 1GB sticks PC 2700 ECC ram >> > > adaptec scsi raid card. >> > > raid 5 array + 1 hot spare. >> > > Motherboard has onboard video, dual intel gigabit nics (bge). That would be the 2880's version without dual scsi (mpt(4))? It might be a hint, that I wasn't able to get the irqs right, if I disabled the scsi devices (bad news for you). As far as your dmesg goes you've disabled the S-ATA controller; you may try to enable it. >> > Do you mind showing the mptable output? >> >> http://www.snsonline.net/~sarge/mptable.out Same BIOS revision, but with SCSI and S-ATA enabled (currently without the aac) running 5.2RC2: mptable: that's quite different from yours. dmesg: dmesg -v would be interesting because of the more detailed information regarding the apic/irq-routing configuration. The problem is, that booting the amd64-kernel in verbose mode produces a lot of ata- and acpi related garbage. -Andreas From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 15:03: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 21DBE16A4CE for ; Mon, 2 Feb 2004 15:03:53 -0800 (PST) Received: from natrium.plan-ix.de (natrium.plan-ix.de [212.37.39.36]) by mx1.FreeBSD.org (Postfix) with SMTP id 539FE43D69 for ; Mon, 2 Feb 2004 15:03:39 -0800 (PST) (envelope-from braukmann@tse-online.de) Received: (qmail 67852 invoked from network); 2 Feb 2004 23:03:38 -0000 Received: from unknown (HELO ?192.168.222.11?) (ab%plan-ix.de@212.37.49.203) by natrium.plan-ix.de with SMTP; 2 Feb 2004 23:03:38 -0000 Date: Tue, 03 Feb 2004 00:04:50 +0100 From: Andreas Braukmann To: Mark Sergeant Message-ID: <2147483647.1075766689@[192.168.222.11]> In-Reply-To: <2147483647.1075764194@[192.168.222.11]> References: <1075684775.1308.24.camel@localhost> <2147483647.1075764194@[192.168.222.11]> X-Mailer: Mulberry/3.1.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: amd64@freebsd.org Subject: Re: [Fwd: Re: Dual processor, AMD 64 machine freezing.] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 23:03:53 -0000 --On Montag, 2. Februar 2004 23:23 Uhr +0100 Andreas Braukmann wrote: [ K8S problems ] >>> http://www.snsonline.net/~sarge/mptable.out > > Same BIOS revision, but with SCSI and S-ATA enabled (currently > without the aac) running 5.2RC2: > > mptable: > > > that's quite different from yours. > > dmesg: > I've put an Adaptec 2120 in the box; the system is stable and mptable and dmesg are as follows: I wasn't able to redo my stress-tests on the machine, yet. My former "test-array" went into production a few weeks ago. (Tyan 2880 K8S, Adaptec 2200S, 2 GByte; running FreeBSD i386 4.9-stable) -Andreas From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 19:10:16 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 6C02C16A4CE for ; Mon, 2 Feb 2004 19:10:16 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBBBE43D46 for ; Mon, 2 Feb 2004 19:10:11 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i133ABFR016064 for ; Mon, 2 Feb 2004 19:10:11 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i133ABWW016063; Mon, 2 Feb 2004 19:10:11 -0800 (PST) (envelope-from gnats) Resent-Date: Mon, 2 Feb 2004 19:10:11 -0800 (PST) Resent-Message-Id: <200402030310.i133ABWW016063@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, Christopher McCrory Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D04A16A4CE for ; Mon, 2 Feb 2004 19:04:23 -0800 (PST) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4443843D1F for ; Mon, 2 Feb 2004 19:04:22 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i1334MdL049808 for ; Mon, 2 Feb 2004 19:04:22 -0800 (PST) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.10/8.12.10/Submit) id i1334M1j049807; Mon, 2 Feb 2004 19:04:22 -0800 (PST) (envelope-from nobody) Message-Id: <200402030304.i1334M1j049807@www.freebsd.org> Date: Mon, 2 Feb 2004 19:04:22 -0800 (PST) From: Christopher McCrory To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.0 Subject: 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: Tue, 03 Feb 2004 03:10:16 -0000 >Number: 62295 >Category: amd64 >Synopsis: ipsec failure on 5.2.1-RC amd64 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 02 19:10:11 PST 2004 >Closed-Date: >Last-Modified: >Originator: Christopher McCrory >Release: 5.2.1-RC >Organization: >Environment: FreeBSD freebsd64 5.2.1-RC FreeBSD 5.2.1-RC #8: Mon Feb 2 10:58:07 PST 2004 root@freebsd64:/usr/obj/usr/src/sys/GENERIC amd64 >Description: linking kernel bf_ecb.o: In function `BF_ecb_encrypt': bf_ecb.o(.text+0x77): undefined reference to `BF_encrypt' bf_ecb.o(.text+0x86): undefined reference to `BF_decrypt' bf_skey.o: In function `BF_set_key': bf_skey.o(.text+0xb7): undefined reference to `BF_encrypt' bf_skey.o(.text+0xeb): undefined reference to `BF_encrypt' des_ecb.o: In function `des_ecb_encrypt': des_ecb.o(.text+0xbc): undefined reference to `des_encrypt1' des_ecb.o: In function `des_ecb3_encrypt': des_ecb.o(.text+0x193): undefined reference to `des_encrypt3' des_ecb.o(.text+0x1a8): undefined reference to `des_decrypt3' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. >How-To-Repeat: add: options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) to kernel config >Fix: ? ? ? >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 20:53:12 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 428EC16A4CE for ; Mon, 2 Feb 2004 20:53:12 -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 366ED43D39 for ; Mon, 2 Feb 2004 20:53:11 -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 i134rAo8006943 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 2 Feb 2004 22:53:10 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i134rAFC006940; Mon, 2 Feb 2004 22:53:10 -0600 (CST) Date: Mon, 2 Feb 2004 22:53:10 -0600 (CST) Message-Id: <200402030453.i134rAFC006940@bigtex.jrv.org> From: James Van Artsdalen To: amd64@freebsd.org Subject: Adaptec 29320? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 04:53:12 -0000 Is anyone using an Adptec 29320? Mine is not working. I suspect is may be a BIOS problem on the Tyan K8W S2885. I also have a Highpoint 1820 that does not work right. If I boot Win64 while the 29320 is plugged in Win64 hangs after logging in. FreeBSD/AMD64 does not crash but does not work either, and the startup log has this: ahd0: port 0-0xff,0-0xff mem 0-0x1fff at device 8.0 on pci2 pcib2: device ahd0 requested unsupported I/O range 0x0-0x0 (decoding 0xf000-0x1fff) ahd0: can't allocate register resources device_probe_and_attach: ahd0 attach returned 12 ahd0: port 0-0xff,0-0xff mem 0-0x1fff at device 8.1 on pci2 pcib2: device ahd0 requested unsupported I/O range 0x0-0x0 (decoding 0xf000-0x1fff) ahd0: can't allocate register resources device_probe_and_attach: ahd0 attach returned 12 The option ROM on the card is not run. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 21:29: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 9778716A4CE; Mon, 2 Feb 2004 21:29:02 -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 1C94F43D39; Mon, 2 Feb 2004 21:29:01 -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 i135T0o8007975 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 2 Feb 2004 23:29:00 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i135T01U007972; Mon, 2 Feb 2004 23:29:00 -0600 (CST) Date: Mon, 2 Feb 2004 23:29:00 -0600 (CST) Message-Id: <200402030529.i135T01U007972@bigtex.jrv.org> From: James Van Artsdalen To: chrismcc+freebsd@freebsd.org In-reply-to: <200402030304.i1334M1j049807@www.freebsd.org> (message from Christopher McCrory on Mon, 2 Feb 2004 19:04:22 -0800 (PST)) References: <200402030304.i1334M1j049807@www.freebsd.org> cc: freebsd-amd64@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: Tue, 03 Feb 2004 05:29:02 -0000 > Date: Mon, 2 Feb 2004 19:04:22 -0800 (PST) > From: Christopher McCrory > > >Synopsis: ipsec failure on 5.2.1-RC amd64 > > bf_ecb.o: In function `BF_ecb_encrypt': > bf_ecb.o(.text+0x77): undefined reference to `BF_encrypt' > bf_ecb.o(.text+0x86): undefined reference to `BF_decrypt' > bf_skey.o: In function `BF_set_key': > bf_skey.o(.text+0xb7): undefined reference to `BF_encrypt' > bf_skey.o(.text+0xeb): undefined reference to `BF_encrypt' > des_ecb.o: In function `des_ecb_encrypt': > des_ecb.o(.text+0xbc): undefined reference to `des_encrypt1' > des_ecb.o: In function `des_ecb3_encrypt': > des_ecb.o(.text+0x193): undefined reference to `des_encrypt3' > des_ecb.o(.text+0x1a8): undefined reference to `des_decrypt3' Please try this and tell me if IPSEC works. I'd also like to know how performance compares to other implementations - I'm wondering if the assembly language optimizations from i386 should be ported to AMD64. --- sys/conf/files.amd64.orig Mon Nov 17 02:58:16 2003 +++ sys/conf/files.amd64 Mon Feb 2 23:08:43 2004 @@ -123,3 +123,10 @@ compat/ia32/ia32_sigtramp.S optional ia32 compat/ia32/ia32_sysvec.c optional ia32 kern/imgact_elf32.c optional ia32 +# +crypto/des/des_ecb.c optional netsmbcrypto +crypto/des/des_enc.c optional netsmbcrypto +crypto/des/des_setkey.c optional netsmbcrypto +crypto/blowfish/bf_enc.c optional crypto +crypto/blowfish/bf_enc.c optional ipsec ipsec_esp +crypto/des/des_enc.c optional ipsec ipsec_esp From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 2 23:09: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 6C57116A4CE for ; Mon, 2 Feb 2004 23:09:09 -0800 (PST) Received: from curacao.n2it.nl (62-177-157-186.bbeyond.nl [62.177.157.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6BC843D39 for ; Mon, 2 Feb 2004 23:09:06 -0800 (PST) (envelope-from billsf@curacao.n2it.nl) Received: by curacao.n2it.nl (Postfix, from userid 1000) id 69D202060; Tue, 3 Feb 2004 08:09:05 +0100 (CET) Date: Tue, 3 Feb 2004 08:09:05 +0100 From: Bill Squire To: freebsd-amd64@freebsd.org Message-ID: <20040203070905.GA18274@curacao.n2it.nl> References: <200402030453.i134rAFC006940@bigtex.jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402030453.i134rAFC006940@bigtex.jrv.org> User-Agent: Mutt/1.4.1i Subject: Re: Adaptec 29320? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 07:09:09 -0000 On Mon, Feb 02, 2004 at 10:53:10PM -0600, James Van Artsdalen wrote: > Is anyone using an Adptec 29320? Mine is not working. > I suspect is may be a BIOS problem on the Tyan K8W S2885. > I also have a Highpoint 1820 that does not work right. Not anymore. It worked for awhile and after a few days it just stopped. Next i was given a PERC 320/DC Adaptec FSA RAID (aac) This was much better but still an Adaptec. I'm using a 29160 now and it is going to go! These cards just don't seem to be up to a busy Unix environment. In all cases the firmware was the latest. (Surprisingly FreeDOS runs quite well on the amd64, and needed to run the flash.exe stuff.) I'm getting a real Cirrus Logic card. These cost a third what Adaptec costs and my experience has only been good with these cheap (smb) cards. I work with servers and most BOFH's swear by them and deplore Adaptec. (Therefore all those 'free' cards to try. ;-) Gladly stump up a hundred Euros or so for piece of mind. > If I boot Win64 while the 29320 is plugged in Win64 hangs after > logging in. FreeBSD/AMD64 does not crash but does not work either, Keep hearing about "Win64". Those few I know who develop on that platform or maintain Windows servers say its quite a farce (remember NT on Alpha?) and keep me clear of it. Are there any real 64bit applications in this M$ distribution? I only ask because I wouldn't mind being able run some of the better offerings from the Windows community like you can do with the FreeBSD on i386. I get the source for several major Windows applications but it all seems so hopelessly 32bit. No, I can't give any out but can suggest you may be surprised what you can get by asking. "Wine64" would indeed be fine. Presently I'm using an Asus K8 motherboard for an Opteron-100 marketed as "Athlon-FX" or something. Not bad for Taiwan, but apparently Taiwan thought amd64 was going to be Windows and therefore some really goofy features. All AMD products seem to work better slightly overclocked. 2250MHz for a 2200MHz chip is perfectly inline with the 3 - 5% rule. When increasing the bus speed, Adaptec cards give out first, then SATA and then the video and so on. Sorry, this is a bit offtopic. > and the startup log has this: > ahd0: port 0-0xff,0-0xff mem 0-0x1fff at device 8.0 on pci2 > pcib2: device ahd0 requested unsupported I/O range 0x0-0x0 (decoding 0xf000-0x1fff) > ahd0: can't allocate register resources > device_probe_and_attach: ahd0 attach returned 12 > ahd0: port 0-0xff,0-0xff mem 0-0x1fff at device 8.1 on pci2 > pcib2: device ahd0 requested unsupported I/O range 0x0-0x0 (decoding 0xf000-0x1fff) > ahd0: can't allocate register resources > device_probe_and_attach: ahd0 attach returned 12 > > The option ROM on the card is not run. This may be mistaken, but I recall stopping something similar to the above in either 'device hints' or 'loader.conf', by stipulating where the DMA would be. Maybe give it a try but i'd suggest a better SCSI host adapter. I'm not trying to bring on flames as this is exactly how i see it and Adaptec sounds good from a salesman. A large wholesaler in Tiel, of all places, that sells me the 'smb' cards also sells Adaptec and says: "Managers like that name". I think that says it all. Highpoint apparently supplies FreeBSD drivers. I hear 3ware works well and Promise seems 'promising' for SATA RAID. (and quite cheap too) Anyone use the Promise SATA 150 TX4 ? From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 3 00:39: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 DBA5216A4CF for ; Tue, 3 Feb 2004 00:39:22 -0800 (PST) Received: from scribble.fsn.hu (scribble.fsn.hu [193.224.40.95]) by mx1.FreeBSD.org (Postfix) with SMTP id C2C3B43D73 for ; Tue, 3 Feb 2004 00:38:49 -0800 (PST) (envelope-from bra@fsn.hu) Received: (qmail 5704 invoked from network); 3 Feb 2004 08:38:47 -0000 Received: from unknown (HELO fsn.hu) (127.0.0.1) by localhost with SMTP; 3 Feb 2004 08:38:47 -0000 Message-ID: <401F5E17.2060306@fsn.hu> Date: Tue, 03 Feb 2004 09:38:47 +0100 From: Attila Nagy Organization: Free Software Network Foundation - http://www.fsn.hu/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: hu, en-us, en MIME-Version: 1.0 To: ports@freebsd.org Content-Type: multipart/mixed; boundary="------------040208030402080904010503" cc: amd64@freebsd.org Subject: [Fwd: Re: jigdo-0.7.0 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: Tue, 03 Feb 2004 08:39:23 -0000 This is a multi-part message in MIME format. --------------040208030402080904010503 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Kris Kennaway wrote: > http://bento.freebsd.org/errorlogs/amd64-5-latest/jigdo-0.7.0.log > Can you please investigate and/or report to the developers? I've attached a patch which should correct the problem. Could you please test it? Thanks, -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone @work: +361 210 1415/127 ISOs: http://www.fsn.hu/?f=download cell.: +3630 306 6758 --------------040208030402080904010503 Content-Type: text/plain; name="patch-aa" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="patch-aa" --- src.orig/mktemplate.cc +++ src/mktemplate.cc @@ -1,4 +1,4 @@ -/* $Id: mktemplate.cc,v 1.92 2003/04/27 15:57:21 richard Exp $ -*- C++ -= *- +/* $Id: mktemplate.cc,v 1.93 2003/05/06 19:12:14 richard Exp $ -*- C++ -= *- __ _ |_) /| Copyright (C) 2001-2002 Richard Atterer | \/=AF| @@ -643,7 +643,7 @@ Paranoid(*data + len <=3D bufferLength); rsum->addBack(buf + *data, len); *data +=3D len; off +=3D len; *n -=3D len; - *rsumBack =3D modAdd(*rsumBack, len, bufferLength); + *rsumBack =3D modAdd(*rsumBack, implicit_cast(len), bufferLe= ngth); Paranoid(off =3D=3D nextEvent || off =3D=3D nextAlignedOff); # if DEBUG for (unsigned i =3D 0; i < len; ++i) { --------------040208030402080904010503-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 3 01:11:28 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 5B56416A4CE for ; Tue, 3 Feb 2004 01:11:28 -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 AA64643D2F for ; Tue, 3 Feb 2004 01:11:26 -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 i139Aso8031890 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Feb 2004 03:10:54 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i139AOpU031887; Tue, 3 Feb 2004 03:10:24 -0600 (CST) Date: Tue, 3 Feb 2004 03:10:24 -0600 (CST) Message-Id: <200402030910.i139AOpU031887@bigtex.jrv.org> From: James Van Artsdalen To: billsf@curacao.n2it.nl In-reply-to: <20040203070905.GA18274@curacao.n2it.nl> (message from Bill Squire on Tue, 3 Feb 2004 08:09:05 +0100) References: <200402030453.i134rAFC006940@bigtex.jrv.org> <20040203070905.GA18274@curacao.n2it.nl> cc: freebsd-amd64@freebsd.org Subject: Re: Adaptec 29320? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 09:11:28 -0000 > Date: Tue, 3 Feb 2004 08:09:05 +0100 > From: Bill Squire > > Keep hearing about "Win64". Those few I know who develop on that platform > or maintain Windows servers say its quite a farce (remember NT on Alpha?) Well, it is Windows. What can I say? 32-bit Windows makes a good X11 server and it's handy to keep one around for clients who might be scared if they saw vi. I keep a matrix of four disks with 32-bit and 64-bit Windows and FreeBSD for testing. It's usually desirable to not report a bug if it happens in all four environments. > Maybe give it a try but i'd suggest a better SCSI host adapter. I'm after a controller that works in all four test environments and can directly address more than 4 GB. I'd prefer serial ATA but there are none yet. SCSI is a last resort. I'm willing to use a different controller. But when two new PCI-X cards fail like this I'm suspicious of the Tyan's AMI BIOS, which I consider suspect. That BIOS might be programming the PCI-X bridge wrongly, hence my curiosity as to whether anyone has gotten the 29320, or any other PCI-X card for that matter, to work in the K8W S2885. > Highpoint apparently supplies FreeBSD > drivers. I hear > 3ware works well and Promise seems 'promising' for SATA RAID. (and > quite cheap too) Anyone use the Promise SATA 150 TX4 ? That HighPoint cannot directly address more than 4 GB of RAM and I have 8 GB. Likewise for Promise. The 3ware driver may not support 3ware's sATA card and in any case that driver doesn't support more 4 GB (requires the use of bound buffers). HighPoint's Rocket Raid-1820 is PCI-X and probably can address the entire memory space. But this is supposedly based on the Marvel chip and what drivers HighPoint has seem to be binary only, useless. SuperMicro's PCI-X sATA supposedly uses the same chip, without the boot ROM. From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 3 01:33: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 5A24616A4CE for ; Tue, 3 Feb 2004 01:33:44 -0800 (PST) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id C24DB43D2F for ; Tue, 3 Feb 2004 01:33:42 -0800 (PST) (envelope-from tilman@arved.de) Received: from huckfinn-xl1.arved.de (localhost [127.0.0.1]) i139XfH6025274; Tue, 3 Feb 2004 10:33:41 +0100 (CET) (envelope-from tilman@arved.de) Received: (from tilman@localhost) by huckfinn-xl1.arved.de (8.12.11/8.12.6/Submit) id i139XfrG025273; Tue, 3 Feb 2004 10:33:41 +0100 (CET) X-Authentication-Warning: huckfinn-xl1.arved.de: tilman set sender to tilman@arved.de using -f Date: Tue, 3 Feb 2004 10:33:40 +0100 From: Tilman Linneweh To: Attila Nagy Message-ID: <20040203093340.GG65933@huckfinn.arved.de> References: <401F5E17.2060306@fsn.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <401F5E17.2060306@fsn.hu> User-Agent: Mutt/1.4.1i cc: amd64@freebsd.org Subject: Re: [Fwd: Re: jigdo-0.7.0 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: Tue, 03 Feb 2004 09:33:44 -0000 * Attila Nagy [Tue, Feb 03, 2004 at 09:38:47AM +0100]: > >http://bento.freebsd.org/errorlogs/amd64-5-latest/jigdo-0.7.0.log > >Can you please investigate and/or report to the developers? > I've attached a patch which should correct the problem. Could you please > test it? > Worked & committed, thanks, tilman From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 3 03:19: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 757C216A4CE for ; Tue, 3 Feb 2004 03:19:19 -0800 (PST) Received: from zukmail04.zreo.compaq.com (zukmail04.zreo.compaq.com [161.114.128.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 625FF43D1F for ; Tue, 3 Feb 2004 03:19:17 -0800 (PST) (envelope-from carla.godinho@hp.com) Received: from reoexg11.emea.cpqcorp.net (reoexg11.emea.cpqcorp.net [16.25.5.9]) by zukmail04.zreo.compaq.com (Postfix) with ESMTP id 6A49F2D01 for ; Tue, 3 Feb 2004 11:19:34 +0000 (GMT) Received: from ptiexc02.emea.cpqcorp.net ([15.178.5.100]) by reoexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673); Tue, 3 Feb 2004 11:19:13 +0000 content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Date: Tue, 3 Feb 2004 11:19:10 -0000 Message-ID: <47E8567372BB7F4E85BDEED048692A9901B85134@ptiexc02.emea.cpqcorp.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Index: AcPqR4smTLCFRcXCRZ6AI45z9ikAmA== From: "Godinho, Carla" To: X-OriginalArrivalTime: 03 Feb 2004 11:19:13.0233 (UTC) FILETIME=[8D659C10:01C3EA47] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 11:19:19 -0000 Hi Fellow, Hope everything is ok all of you! I would like to install on my PC FreeBSD version 4.9 (the stable one). = But I realized that for my Pres=E1rio 7482, which has an AMD Processor, = there is no FreeBSD v4.9 for AMD available. Which version do you = recommend, since I would like to have stable one? Thank you in advance Carla From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 3 03:22: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 52D8B16A4CE for ; Tue, 3 Feb 2004 03:22:18 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9535143D2F for ; Tue, 3 Feb 2004 03:22:16 -0800 (PST) (envelope-from tomh@waterloo.equitrac.com) Received: from syncro.metrics.com ([192.168.96.20]) by omega.metrics.com (8.9.3/8.9.3) with ESMTP id GAA01981 for ; Tue, 3 Feb 2004 06:22:12 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Tue, 3 Feb 2004 06:20:48 -0500 Message-ID: From: "Haapanen, Tom" To: freebsd-amd64@freebsd.org Date: Tue, 3 Feb 2004 06:20:42 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 11:22:18 -0000 Godinho, Carla wrote: > I would like to install on my PC FreeBSD version 4.9 (the stable = one).=20 > But I realized that for my Pres=E1rio 7482, which has an AMD = Processor,=20 > there is no FreeBSD v4.9 for AMD available. Which version do you=20 > recommend, since I would like to have stable one? Carla, Presarios should use the i386 version of FreeBSD -- and that one does = have a 4.9 available. The amd64 version (and mailing list) is for the 64-bit AMD processors: Opteron, Athlon FX and Athlon 64. Tom From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 3 03:39: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 8B54916A4CE for ; Tue, 3 Feb 2004 03:39:06 -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 6241243D1F for ; Tue, 3 Feb 2004 03:39:05 -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 i13Bd4o8041424 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Feb 2004 05:39:04 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i13Bd4kD041421; Tue, 3 Feb 2004 05:39:04 -0600 (CST) Date: Tue, 3 Feb 2004 05:39:04 -0600 (CST) Message-Id: <200402031139.i13Bd4kD041421@bigtex.jrv.org> From: James Van Artsdalen To: tomh@waterloo.equitrac.com In-reply-to: (tomh@waterloo.equitrac.com) References: cc: freebsd-amd64@freebsd.org cc: carla.godinho@hp.com Subject: Re: X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 11:39:06 -0000 > From: "Haapanen, Tom" > Date: Tue, 3 Feb 2004 06:20:42 -0500 > > Godinho, Carla wrote: > > I would like to install on my PC FreeBSD version 4.9 (the stable one). > > But I realized that for my Presário 7482, which has an AMD Processor, > > there is no FreeBSD v4.9 for AMD available. Which version do you > > recommend, since I would like to have stable one? > > Carla, > > Presarios should use the i386 version of FreeBSD -- and that one does have a > 4.9 available. > > The amd64 version (and mailing list) is for the 64-bit AMD processors: > Opteron, Athlon FX and Athlon 64. Her Presario uses a 32-bit-only K6. But HP does sell the Presario 8000Z which does use an Athlon64. Other HP brands also have Athlon64 processors. HP is in the AM64 business, just not the Opteron business. As of today anyway. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 4 01:08:15 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 7F4E316A4CE for ; Wed, 4 Feb 2004 01:08:15 -0800 (PST) Received: from smtp2.su.se (smtp2.su.se [130.237.93.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E03B43D39 for ; Wed, 4 Feb 2004 01:08:12 -0800 (PST) (envelope-from jj@it.su.se) Received: from localhost (smtp2.su.se [127.0.0.1]) by smtp2.su.se (Postfix) with ESMTP id B55F72007AD for ; Wed, 4 Feb 2004 10:08:10 +0100 (CET) Received: from smtp2.su.se ([127.0.0.1]) by localhost (smtp2.su.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29969-12 for ; Wed, 4 Feb 2004 10:08:10 +0100 (CET) Received: from it.su.se (jj.it.su.se [130.237.95.193]) by smtp2.su.se (Postfix) with ESMTP id 9FEAC2000B1 for ; Wed, 4 Feb 2004 10:08:10 +0100 (CET) Message-ID: <4020B672.9080304@it.su.se> Date: Wed, 04 Feb 2004 10:08:02 +0100 From: Janne Johansson Organization: Stockholms Universitet User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040123 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org X-Enigmail-Version: 0.82.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at su.se Subject: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 09:08:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an amd64-3000 on a Abit motherboard, 1G ram, satadisk and it works nice enough on 32-bitmode winxp, but I can't get it to be stable in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes it crash for sure is the /usr/ports/benchmarks/ubench program. It does the cpu-test and prints those results and then when it gets to test "memory speed" in part 2, it always dies on me. Of course, other activities related to recently-installed systems makes it crash too. I thought it could have been the sk-ethernet that was the culprit, since post-installation-stuff for me includes getting bash/emacs, cvs:ing and so on and that 5.2.1RC might fix that, but the ubench program uses no network afaik. So I am wondering, is it the same for other socket754-amd64-users and what can I do? Serial console to pick up crash dumps? Turn on more verbose crash-report stuff somehow? build an even more recent kernel? Turn off smp-support (I have only one cpu) or power-saving stuff in the bios? Turn on Cool-n-quiet (some mhz-altering stuff as I gather) or move from SATA to scsi in case that would be part of the problem? Advice needed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAILZyKWyDo3z7ubcRAn4LAJ4kue4dlTK3FbQz80nxVkugtbQFGgCeMugj usp+7qU9ZurRldIGH9sXBJ4= =+9EN -----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 4 03:51:54 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 064D016A4CE for ; Wed, 4 Feb 2004 03:51:54 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC82B43D3F for ; Wed, 4 Feb 2004 03:51:51 -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 i14BpoRv017370; Wed, 4 Feb 2004 12:51:50 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 4 Feb 2004 12:51:45 +0100 User-Agent: KMail/1.6.50 References: <4020B672.9080304@it.su.se> In-Reply-To: <4020B672.9080304@it.su.se> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200402041251.50129.adridg@cs.kun.nl> cc: Janne Johansson Subject: Re: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 11:51:54 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 04 February 2004 10:08, Janne Johansson wrote: > I have an amd64-3000 on a Abit motherboard, 1G ram, satadisk and it > works nice enough on 32-bitmode winxp, but I can't get it to be stable That's pretty consumer grade - just like what i have (k8vdeluxe, 3200, 1G r= am,=20 sata on the promise controller).=20 > in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes > it crash for sure is the /usr/ports/benchmarks/ubench program. It does Don't run that, it'll just tell you that the system is only marginally fast= er=20 than the athlon XP it replaces.=20 > I thought it could have been the sk-ethernet that was the culprit, since > post-installation-stuff for me includes getting bash/emacs, cvs:ing and sk ethernet was a problem in early snapshots - I started with one of David'= s=20 snapshots from early november, dropped in an xl card (3c509) , cvsupped to= =20 =2D -CURRENT, built that, and all was fine. > Serial console to pick up crash dumps? Turn on more verbose crash-report Serial console is always a good idea. Expesially when things crash under X. > stuff somehow? build an even more recent kernel? Turn off smp-support (I SMP is mandatory in -CURRENT and doesn't affect UP systems. > have only one cpu) or power-saving stuff in the bios? Turn on > Cool-n-quiet (some mhz-altering stuff as I gather) or move from SATA to The power-saving stuff in the BIOS can be very tricky. I had endless lockup= s=20 when C&Q was turned on - nice and quiet, but max. uptime of about 12 hours.= =20 Since I've switched that off again and just let the CPU cooler run at max=20 speed all the time and don't fiddle with memory timings or voltages, it run= s=20 much better. 12:51PM up 14 days, 13:14, 4 users, load averages: 1.35, 1.26, 0.99 Not spectacular, but hey. It means it was 14 days ago that I last accessed = the=20 cdrom, which is a sure-fire way to panic the system. =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot The users that I support would double-click on a landmine to see what it di= d. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAINzWdqzuAf6io/4RAgfPAJ4lrFREhzZj5jP/HF1y0HYoPSQPqQCdEFJB l8BI/ryoE0Yx/7/+ibf1714=3D =3DVihN =2D----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 4 04:07: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 9736F16A4CE for ; Wed, 4 Feb 2004 04:07:23 -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 4F00543D39 for ; Wed, 4 Feb 2004 04:07:22 -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 i14C7Jo8008985 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 4 Feb 2004 06:07:19 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i14C7JGW008982; Wed, 4 Feb 2004 06:07:19 -0600 (CST) Date: Wed, 4 Feb 2004 06:07:19 -0600 (CST) Message-Id: <200402041207.i14C7JGW008982@bigtex.jrv.org> From: James Van Artsdalen To: adridg@cs.kun.nl In-reply-to: <200402041251.50129.adridg@cs.kun.nl> (message from Adriaan de Groot on Wed, 4 Feb 2004 12:51:45 +0100) References: <4020B672.9080304@it.su.se> <200402041251.50129.adridg@cs.kun.nl> cc: jj@it.su.se cc: freebsd-amd64@freebsd.org Subject: Re: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 12:07:23 -0000 > From: Adriaan de Groot > Date: Wed, 4 Feb 2004 12:51:45 +0100 > > > in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes > > it crash for sure is the /usr/ports/benchmarks/ubench program. It does > > Don't run that, it'll just tell you that the system is only marginally faster > than the athlon XP it replaces. I've reproduced Janne's panic with ubench twice. Both show similar outputs from the panic. Panic #3 is proving more elusive: I'm running ubench for the fourth time in a row now waiting for crash #3. This is the 5.2 kernel with SMBFS and such turned on. These are the first two panic's I've seen in two months. panic: vm_page_alloc: free/cache page 0xffffff01faf5db50 was dirty cpuid = 1; Stack backtrace: backtrace() at backtrace+0x17 panic() at panic+0x1d2 vm_page_alloc() at vm_page_alloc+0x2df vm_fault() at vm_fault+0x578 trap_pfault() at trap_pfault+0x100 trap() at trap+0x1be calltrap() at calltrap+0x5 --- trap 0xc, rip = 0x2007f599c, rsp = 0x7fffffffe488, rbp = 0x53 --- Debugger("panic") Stopped at Debugger+0x4c: xchgl %ebx,0x31fdee db> From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 4 13:30:17 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 18B0D16A4CE for ; Wed, 4 Feb 2004 13:30:17 -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 A8B5743D46 for ; Wed, 4 Feb 2004 13:30:15 -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 i14LUCo8029595 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 4 Feb 2004 15:30:12 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i14LUBwd029592; Wed, 4 Feb 2004 15:30:11 -0600 (CST) Date: Wed, 4 Feb 2004 15:30:11 -0600 (CST) Message-Id: <200402042130.i14LUBwd029592@bigtex.jrv.org> From: James Van Artsdalen To: adridg@cs.kun.nl, jj@it.su.se, freebsd-amd64@freebsd.org In-reply-to: <200402041207.i14C7JGW008982@bigtex.jrv.org> (message from James Van Artsdalen on Wed, 4 Feb 2004 06:07:19 -0600 (CST)) References: <4020B672.9080304@it.su.se> <200402041251.50129.adridg@cs.kun.nl> <200402041207.i14C7JGW008982@bigtex.jrv.org> Subject: Re: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 21:30:17 -0000 > Date: Wed, 4 Feb 2004 06:07:19 -0600 (CST) > From: James Van Artsdalen > > > From: Adriaan de Groot > > Date: Wed, 4 Feb 2004 12:51:45 +0100 > > > > > in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes > > > it crash for sure is the /usr/ports/benchmarks/ubench program. It does > > > > Don't run that, it'll just tell you that the system is only marginally faster > > than the athlon XP it replaces. > > I've reproduced Janne's panic with ubench twice. Both show similar > outputs from the panic. Panic #3 is proving more elusive: I'm running > ubench for the fourth time in a row now waiting for crash #3. Unfortunately it appears my case was a false alarm. My Tyan K8W S2885 is not stable unless ECC is turned off in ROM setup. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 4 20:48:28 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 5D6D416A4CE for ; Wed, 4 Feb 2004 20:48:28 -0800 (PST) Received: from nu.binary.net (nu.binary.net [216.229.0.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CD0E43D3F for ; Wed, 4 Feb 2004 20:48:25 -0800 (PST) (envelope-from yura@binary.net) Received: from matrix.binary.net (matrix.binary.net [216.229.0.2]) by nu.binary.net (Postfix) with ESMTP id 57A1B15C94; Wed, 4 Feb 2004 22:48:24 -0600 (CST) Received: by matrix.binary.net (Postfix, from userid 100) id 1E7AD102963; Wed, 4 Feb 2004 22:48:24 -0600 (CST) Date: Wed, 4 Feb 2004 22:48:24 -0600 From: Yura Socolov To: James Van Artsdalen Message-ID: <20040205044824.GA62567@binary.net> References: <4020B672.9080304@it.su.se> <200402041251.50129.adridg@cs.kun.nl> <200402041207.i14C7JGW008982@bigtex.jrv.org> <200402042130.i14LUBwd029592@bigtex.jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402042130.i14LUBwd029592@bigtex.jrv.org> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 04:48:28 -0000 On Wed, Feb 04, 2004 at 03:30:11PM -0600, James Van Artsdalen wrote: > > Date: Wed, 4 Feb 2004 06:07:19 -0600 (CST) > > From: James Van Artsdalen > > > > > From: Adriaan de Groot > > > Date: Wed, 4 Feb 2004 12:51:45 +0100 > > > > > > > in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes > > > > it crash for sure is the /usr/ports/benchmarks/ubench program. It does > > > > > > Don't run that, it'll just tell you that the system is only marginally faster > > > than the athlon XP it replaces. > > > > I've reproduced Janne's panic with ubench twice. Both show similar > > outputs from the panic. Panic #3 is proving more elusive: I'm running > > ubench for the fourth time in a row now waiting for crash #3. > > Unfortunately it appears my case was a false alarm. > My Tyan K8W S2885 is not stable unless ECC is turned off in ROM setup. Likely, i've been running ubench in a continuous loop while doing a make world and transferring large quantities of data to and from the box. No panic, no problems, other than a load avg of 17 at times, but that's ubench's fault. Athlon 64 3K, FIC K8-800T, DDR400. uname/dmesg follows. -- yu FreeBSD 5.2.1-RC #2: Wed Feb 4 21:10:18 EST 2004 yura@kussi.31337.net:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80865000. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1999.79-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500000 real memory = 536805376 (511 MB) avail memory = 500088832 (476 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: port 0x530-0x537 on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: possible interrupts: 20 pcib0: slot 15 INTB routed to irq 20 via \\_SB_.PCI0.ALKA pcib0: possible interrupts: 21 pcib0: slot 16 INTA routed to irq 21 via \\_SB_.PCI0.ALKB pcib0: possible interrupts: 21 pcib0: slot 16 INTA routed to irq 21 via \\_SB_.PCI0.ALKB pcib0: possible interrupts: 21 pcib0: slot 16 INTB routed to irq 21 via \\_SB_.PCI0.ALKB pcib0: possible interrupts: 21 pcib0: slot 16 INTB routed to irq 21 via \\_SB_.PCI0.ALKB pcib0: possible interrupts: 21 pcib0: slot 16 INTC routed to irq 21 via \\_SB_.PCI0.ALKB pcib0: possible interrupts: 22 pcib0: slot 17 INTC routed to irq 22 via \\_SB_.PCI0.ALKC pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 16 pci1: at device 0.0 (no driver attached) pci1: at device 0.1 (no driver attached) ahc0: port 0xb000-0xb0ff mem 0xeb000000-0xeb000fff irq 17 at device 10.0 on pci0 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs fwohci0: port 0xb400-0xb47f mem 0xeb001000-0xeb0017ff irq 16 at device 14.0 on pci0 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:40:ca:07:01:06:4a:fc fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:40:ca:06:4a:fc sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: port 0xcc00-0xccff,0xc800-0xc80f,0xc400-0xc403,0xc000-0xc007,0xbc00-0xbc03,0xb800-0xb807 irq 20 at devi ce 15.0 on pci0 atapci0: [MPSAFE] ata2: at 0xb800 on atapci0 ata2: [MPSAFE] ata3: at 0xc000 on atapci0 ata3: [MPSAFE] atapci1: port 0xd000-0xd00f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci1 ata1: [MPSAFE] uhci0: port 0xd400-0xd41f irq 21 at device 16.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd800-0xd81f irq 21 at device 16.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xdc00-0xdc1f irq 21 at device 16.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xe000-0xe01f irq 21 at device 16.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 16.4 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 pcm0: port 0xe400-0xe4ff irq 22 at device 17.5 on pci0 pcm0: rl0: port 0xe800-0xe8ff mem 0xeb003000-0xeb0030ff irq 17 at device 19.0 on pci0 rl0: Ethernet address: 00:40:ca:6c:96:c8 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 orm0: