From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 25 05:37: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 7B64D16A4CE for ; Sun, 25 Jan 2004 05:37:49 -0800 (PST) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0BF243D46 for ; Sun, 25 Jan 2004 05:37:48 -0800 (PST) (envelope-from ml@fruitbat.demon.co.uk) Received: from pr-webmail-2.demon.net ([194.159.244.50]) by anchor-post-35.mail.demon.net with smtp (Exim 3.35 #1) id 1AkkSR-000FNA-0Z for freebsd-amd64@FreeBSD.org; Sun, 25 Jan 2004 13:37:47 +0000 Received: from fruitbat.demon.co.uk ([195.74.121.82]) by web.mail.demon.net with http; Sun, 25 Jan 2004 13:37:47 +0000 From: ml@fruitbat.demon.co.uk To: freebsd-amd64@FreeBSD.org Date: Sun, 25 Jan 2004 13:37:47 +0000 User-Agent: Demon-WebMail/2.0 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: Subject: malloc() over 4Gb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 13:37:49 -0000 Hi. Could someone clarify whether or not it's possible to malloc() and mmap() chunks of memory > 4Gb in size using FreeBSD/AMD64 and that FreeBSD/AMD64 isn't susceptible to the 4Gb process boundary that 32-bit OSs are restricted by? Thanks in advance! A. -- Alligator Descartes From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 25 13:27: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 B632C16A4CE for ; Sun, 25 Jan 2004 13:27:04 -0800 (PST) Received: from omega.metrics.com (ns.metrics.com [204.138.110.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A9F143D1F for ; Sun, 25 Jan 2004 13:27: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 QAA11510 for ; Sun, 25 Jan 2004 16:27:00 -0500 (EST) Received: by SYNCRO with Internet Mail Service (5.5.2653.19) id ; Sun, 25 Jan 2004 16:25:51 -0500 Message-ID: From: "Haapanen, Tom" To: "'freebsd-amd64@freebsd.org'" Date: Sun, 25 Jan 2004 16:25:49 -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: 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: Sun, 25 Jan 2004 21:27:04 -0000 All right, so I gave up on my Adaptec 2100S RAID controller, and managed to locate a used HP NetRAID 3Si (aka MegaRAID 438). The NetRAID is only U2W (80 MB/s, as I recall?), but FreeBSD/amd64 seems to be much happier with it. 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 the errors? Do something else? Thanks ... Tom FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard 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 [\\_SB_.PCI0.SBRG.HPET._STA <\\_SB_.PCI0.SBRG.HPET._STA> ] (Node 0xffffff0000c26d80), AE_AML_REGION_LIMIT acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.HPET._STA <\\_SB_.PCI0.SBRG.HPET._STA> ] (Node 0xffffff0000c26d80), AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.TMR_._CRS <\\_SB_.PCI0.SBRG.TMR_._CRS> ] (Node 0xffffff0000c3bb00), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.TMR_._CRS <\\_SB_.PCI0.SBRG.TMR_._CRS> ] (Node 0xffffff0000c3bb00), AE_AML_REGION_LIMIT can't fetch resources for \\_SB_.PCI0.SBRG.TMR_ <\\_SB_.PCI0.SBRG.TMR_> - AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.HPET._STA <\\_SB_.PCI0.SBRG.HPET._STA> ] (Node 0xffffff0000c26d80), AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.RTC0._CRS <\\_SB_.PCI0.SBRG.RTC0._CRS> ] (Node 0xffffff0000c3b9c0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.RTC0._CRS <\\_SB_.PCI0.SBRG.RTC0._CRS> ] (Node 0xffffff0000c3b9c0), AE_AML_REGION_LIMIT can't fetch resources for \\_SB_.PCI0.SBRG.RTC0 <\\_SB_.PCI0.SBRG.RTC0> - AE_AML_REGION_LIMIT 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 [\\_SB_.PCI0.SBRG.HPET._STA <\\_SB_.PCI0.SBRG.HPET._STA> ] (Node 0xffffff0000c26d80), AE_AML_REGION_LIMIT acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 26 09:29: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 09CA616A4CE for ; Mon, 26 Jan 2004 09:29:54 -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 6E86443D49 for ; Mon, 26 Jan 2004 09:29:52 -0800 (PST) (envelope-from billsf@curacao.n2it.nl) Received: by curacao.n2it.nl (Postfix, from userid 1000) id 0D0892104; Mon, 26 Jan 2004 18:29:51 +0100 (CET) Date: Mon, 26 Jan 2004 18:29:51 +0100 From: Bill Squire To: freebsd-amd64@freebsd.org Message-ID: <20040126172951.GA79221@curacao.n2it.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: What should be reported and to who? 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, 26 Jan 2004 17:29:54 -0000 It has been mentioned that some ports are trivial while others require rewrites of whole sections of C-code. I'm asking mainly about the first question. Some (many?) ports simply build and work if you comment out the #ONLY_FOR_ARCHS= i386 part of the Makefile as shown. This seems so obvious of a thing to try that I don't see the point in saying anything about it, unless it persists a month or more. Ofcourse if it compiles is not to suggest it works! The most common failures are calling amd64 "x86_64" and using deprecated header files like . Open-motif compiles fine but is broken. This is why 'xpdf' dumps cores like crazy. Compile it with 'gtk' (aka 'gpdf') and it works fine. Any Microsoft code is crazy to port as this is the company that believed it was "i386 forever" and will fall as a result. (If you like tedious tasks, you will disagree.) Octave and Matlab are important to me and they will be 'hacked to work'. Unfortunately Matlab sources cannot be put online until someone enlightened gets in. Bill PS: We want Java! From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 26 09:52: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 615C416A4CE for ; Mon, 26 Jan 2004 09:52:40 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A27D143D49 for ; Mon, 26 Jan 2004 09:52:37 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i0QHqYaT013250; Mon, 26 Jan 2004 09:52:34 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i0QHqYRL013249; Mon, 26 Jan 2004 09:52:34 -0800 Date: Mon, 26 Jan 2004 09:52:34 -0800 From: Brooks Davis To: ml@fruitbat.demon.co.uk Message-ID: <20040126175234.GA28717@Odin.AC.HMC.Edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-amd64@freebsd.org Subject: Re: malloc() over 4Gb X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 17:52:40 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 25, 2004 at 01:37:47PM +0000, ml@fruitbat.demon.co.uk wrote: >=20 > Hi. Could someone clarify whether or not it's possible to malloc() > and mmap() chunks of memory > 4Gb in size using FreeBSD/AMD64 and > that FreeBSD/AMD64 isn't susceptible to the 4Gb process boundary that > 32-bit OSs are restricted by? It works fine (just remember to set your malloc options to aj before mallocing that much memory, it takes a loooong time if you done :-): [9:52am] brooks@brimstone (~): uname -a FreeBSD brimstone 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Jan 6 13:18:20 P= ST 2004 brooks@brimstone:/usr/obj/usr/p4/xname/sys/GENERIC amd64 [9:52am] brooks@brimstone (~): ./a a.out* aeroauth*=20 [9:52am] brooks@brimstone (~): cat foo.c #include #include #include #define GB (1024*1024*1024) int main (int argc, char **argv) { void *foo; printf("Trying to malloc %zd bytes\n", (size_t)7*GB); foo =3D malloc((size_t)7*GB); if (foo !=3D NULL) printf("Success\n"); else printf("failure\n"); } [9:52am] brooks@brimstone (~): gcc -o foo foo.c [9:52am] brooks@brimstone (~): ./foo=20 Trying to malloc 7516192768 bytes Success [9:52am] brooks@brimstone (~):=20 -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAFVPgXY6L6fI4GtQRAk6nAJwIfYpHrkkP6/u5/O59Asu1u6S5tQCfSCCP iftnuUkE/TiN8sDMFIRk51I= =bNFj -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 26 11:02: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 0D91316A4CE for ; Mon, 26 Jan 2004 11:02:57 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B37AF43D66 for ; Mon, 26 Jan 2004 11:01:51 -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 i0QJ1fFR038029 for ; Mon, 26 Jan 2004 11:01:41 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i0QJ1eoK038023 for freebsd-amd64@freebsd.org; Mon, 26 Jan 2004 11:01:40 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 26 Jan 2004 11:01:40 -0800 (PST) Message-Id: <200401261901.i0QJ1eoK038023@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, 26 Jan 2004 19:02:57 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59713 amd64