From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 14 15:29:07 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 BB52016A4CE for ; Sun, 14 Dec 2003 15:29:07 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15F7A43D35 for ; Sun, 14 Dec 2003 15:29:06 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost by pandora.cs.kun.nl id hBENT31o015470 (8.12.10/3.58); Mon, 15 Dec 2003 00:29:03 +0100 (MET) From: Adriaan de Groot To: amd64 freebsd Date: Mon, 15 Dec 2003 00:29:00 +0100 User-Agent: KMail/1.5.94 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200312150029.00388.adridg@cs.kun.nl> Subject: End of pthread troubles in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 23:29:07 -0000 With the most-recent -CURRENT (well, from yesterday or so), and without recompiling ogg123, the libmap.conf switch between libc_r and libkse works fine, so I'd say the threading issues have been thrashed out. Thanks Peter. Only recent panic was while unplugging a USB pendrive, and that's more likely just general USB stack suckage than amd64 specific. -- pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot If the door is ajar, can we fill it with door-jamb? From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 14 15:43:16 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 6058516A4CE for ; Sun, 14 Dec 2003 15:43:16 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26FA043D09 for ; Sun, 14 Dec 2003 15:43:15 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost by pandora.cs.kun.nl id hBENhD1o016449 (8.12.10/3.58); Mon, 15 Dec 2003 00:43:13 +0100 (MET) From: Adriaan de Groot To: amd64 freebsd Date: Mon, 15 Dec 2003 00:43:10 +0100 User-Agent: KMail/1.5.94 References: <200312150029.00388.adridg@cs.kun.nl> In-Reply-To: <200312150029.00388.adridg@cs.kun.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200312150043.10380.adridg@cs.kun.nl> Subject: Re: End of pthread troubles in ogg123 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2003 23:43:16 -0000 On Monday 15 December 2003 00:29, Adriaan de Groot wrote: > With the most-recent -CURRENT (well, from yesterday or so), and without > recompiling ogg123, the libmap.conf switch between libc_r and libkse works > fine, so I'd say the threading issues have been thrashed out. Thanks Peter. Guess I spoke too soon, since ogg123 cored after 9 tracks (instead of after 10 seconds), with console messages x: 2 x: 2 Dec 15 00:38:41 beans kernel: pid 768 (ogg123), uid 1001: exited on signal 11 (core dumped) (gdb) bt #0 0x0000000200eebb48 in pthread_testcancel () from /usr/lib/libkse.so.1 #1 0x0000000200ee3590 in pthread_mutexattr_init () from /usr/lib/libkse.so.1 #2 0x0000000200ee1915 in pthread_mutexattr_init () from /usr/lib/libkse.so.1 That's pretty much (testcancel) where it was crashing previously, (after the stack alignment fixes) as well. From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 14 16:07:24 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 BFF1716A4CE for ; Sun, 14 Dec 2003 16:07:24 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 819C243D1D for ; Sun, 14 Dec 2003 16:07:23 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 4321F2A8DF for ; Sun, 14 Dec 2003 16:07:23 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id EE7A92C1AC for ; Sun, 14 Dec 2003 16:07:22 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.10/8.12.10) with ESMTP id hBF07Mup034465; Sun, 14 Dec 2003 16:07:22 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.10/8.12.10/Submit) id hBF07LBJ034464; Sun, 14 Dec 2003 16:07:21 -0800 (PST) (envelope-from peter) From: Peter Wemm To: Jimmie Houchin , Matt Douhan Date: Sun, 14 Dec 2003 16:07:21 -0800 User-Agent: KMail/1.5.4 References: <3FD87B7C.6050608@texoma.net> In-Reply-To: <3FD87B7C.6050608@texoma.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312141607.21395.peter@wemm.org> cc: amd64 freebsd Subject: Re: SV: Packages/Ports problem 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, 15 Dec 2003 00:07:24 -0000 On Thursday 11 December 2003 06:13 am, Jimmie Houchin wrote: > Matt Douhan wrote: > >>Is there any way to tell what all will get installed when I make > >>something? Or do I need to take care of dependencies myself? > >>I'm used to Debian and Gentoo and not familiar with how FreeBSD handles > >>dependencies and such. > > > > It is handled automatically by the ports system > > Good. :) > > I know FreeBSD was much of the inspiration for the Gentoo main developer. > > >>Peter has cvsup-without-gui on his FreeBSD site. > >>I just haven't been able to get it. > >>To my understanding I currently only have the ftp program on my machine. > >>I don't know how to use it to get the package. > > > > pkg_add -r cvsup-without-gui > > That has failed with something like no such file on server error. > > But I'm about to do a fresh install this afternoon/evening after I redo > my partions and will try again. That would be because the port for cvsup hasn't been finished yet. I do have a hacked up cvsup binary that might be enough to get you going. fetch http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz pkg_add cvsup-without-gui-16.1h.tbz Known problems: you cannot use compression. If you set 'compress' on any of your supfiles, it will crash. -Peter From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 14 17:46:46 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 1263F16A4CE for ; Sun, 14 Dec 2003 17:46:46 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7BBD43D2D for ; Sun, 14 Dec 2003 17:46:44 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 84DD82A8D5 for ; Sun, 14 Dec 2003 17:46:44 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 19EC22C1AC for ; Sun, 14 Dec 2003 17:46:44 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.10/8.12.10) with ESMTP id hBF1khup092983; Sun, 14 Dec 2003 17:46:43 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.10/8.12.10/Submit) id hBF1khBB092982; Sun, 14 Dec 2003 17:46:43 -0800 (PST) (envelope-from peter) From: Peter Wemm To: Jimmie Houchin , amd64 freebsd Date: Sun, 14 Dec 2003 17:46:43 -0800 User-Agent: KMail/1.5.4 References: <3FD92A43.5080205@texoma.net> In-Reply-To: <3FD92A43.5080205@texoma.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312141746.43327.peter@wemm.org> Subject: Re: kernel compile failure 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, 15 Dec 2003 01:46:46 -0000 On Thursday 11 December 2003 06:38 pm, Jimmie Houchin wrote: > Hello, > > I just did a fresh install. > > I edited a configuration for my kernel. > When attempting to compile this kernel I get this error. > I could have very well done something wrong in my configuration to cause > this. > > /usr/src/sys/dev/pst/pst-iop.c: In function 'iop_intr': > /usr/src/sys/dev/pst/pst-iop.c:196 warning: cast to pointer from integer > of different size > /usr/src/sys/dev/pst/pst-iop.c: In function 'iop_done': > /usr/src/sys/dev/pst/pst-iop.c:417 warning: cast to pointer from integer > of different size > /usr/src/sys/dev/pst/pst-iop.c: In function 'iop_queue_wait_msg': > /usr/src/sys/dev/pst/pst-iop.c:434 warning: cast to pointer from integer > of different size > ***Error code 1 > Stop... > Stop... > Stop... > # The pst (promise supertrak) driver is utterly not 64 bit clean. It uses a 32 bit space in the I2O control blocks to point to the freebsd driver data structures. Since the freebsd kernel lives at the top of the 64 bit address space, this does not work too well. > Also... > When reading the NOTES for configuring a kernel it speaks about a ULE > scheduler for SMP systems. > > It says that the BSD scheduler isn't very good for SMP systems. But I > don't find an option for the ULE scheduler. Is it not ready for > primetime on the AMD64? > > Is it still okay to use the BSD scheduler for SMP? Yes. > > And... > In the RAID configuration (I think) it had a Promise SX6000 support. > I have the Promise onboard SATA RAID controller. > I didn't see explicit Promise SATA support but I know it is somewhere > because I and FreeBSD are using it. Is the support coming from the > SX6000 kernel option? The SX6000 is the pst driver above. It might not be *that* hard to update it, but if you ask Soren (sos@freebsd.org) very nicely, he might take a shot at it. > Any help and information greatly appreciated. > > Thanks. > > Jimmie Houchin Cheers, -Peter From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 06:20:32 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 611C816A5CE for ; Mon, 15 Dec 2003 06:20:32 -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 4756D43D31 for ; Mon, 15 Dec 2003 06:20:31 -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 hBFEKUo8098747 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 15 Dec 2003 08:20:30 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id hBFEKTAe098742; Mon, 15 Dec 2003 08:20:29 -0600 (CST) Date: Mon, 15 Dec 2003 08:20:29 -0600 (CST) Message-Id: <200312151420.hBFEKTAe098742@bigtex.jrv.org> From: James Van Artsdalen To: freebsd-amd64@freebsd.org Subject: emacs? 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, 15 Dec 2003 14:20:32 -0000 Is anyone using emacs on x86-64? I did a really lame conf file for emacs 21.3 by copying the ia64 files with a couple of changes, and that didn't work. temacs crashes on the first call to Fmake_symbol () in alloc.c: Program received signal SIGBUS, Bus error. 0x00000000004e4261 in Fmake_symbol (name=6917529027648327624) at alloc.c:2544 2544 p->obarray = Qnil; Anyone already have a working config file? From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 08:40:49 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 78A5916A4CE for ; Mon, 15 Dec 2003 08:40:49 -0800 (PST) Received: from ns.spirit.ee (ns.spirit.ee [82.131.120.70]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C88A43D36 for ; Mon, 15 Dec 2003 08:40:47 -0800 (PST) (envelope-from joel@almic.ee) Received: (qmail 7636 invoked from network); 15 Dec 2003 00:43:43 -0000 Received: from unknown (HELO CHARON) (192.168.0.25) by 192.168.0.254 with SMTP; 15 Dec 2003 00:43:43 -0000 From: "Joel V." To: Date: Mon, 15 Dec 2003 02:40:13 +0200 Message-ID: <000201c3c2a4$07423370$1900a8c0@CHARON> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: 5.2 and amd64 - good enough for a production server? 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, 15 Dec 2003 16:40:49 -0000 Just making sure I understand everything, before I go to my boss and = tell him to buy a 4000$ opteron box. =3D) 1) All the ports are working fine? I can go to /usr/ports/x and make = install clean and I got myself a 64-bit binary working on a 64-bit operating = system? (I'm mainly interested in Apache, qmail, vpopmail, proftpd and samba, = which are quite essential to have.) 2) AMD64 version of 5.2 will support the same amount of hardware than = i368 version? The most important area of support being RAID controllers, for = me at least. (Adaptec SCSI for booting and system disks, 3ware ATA for dedicated backup disks. Oh, and what about RAID management tools?) 3) Last but not least - 32-bit compatibility? I know Linux binary compatibility, both 32-bit and 64-bit is NOT DONE, but when will it be? = Will it take a month, half a year or more? Its not a matter of life and = death, but it would be good to know. And as far as I understand, at this moment = I cannot also run 32-bit FreeBSD binaries from earlier 5.x releases? Please be not offended by my outrageously newbie-esque questions. Take care and thanks in advance! Joel V. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 09:02:44 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 0153416A4CF for ; Mon, 15 Dec 2003 09:02:44 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 744F643D36 for ; Mon, 15 Dec 2003 09:02:41 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 1DD582A8EB for ; Mon, 15 Dec 2003 09:02:41 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id EE4D42C1AF for ; Mon, 15 Dec 2003 09:02:40 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.10/8.12.10) with ESMTP id hBFH2dup052887; Mon, 15 Dec 2003 09:02:39 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.10/8.12.10/Submit) id hBFH2dlE052886; Mon, 15 Dec 2003 09:02:39 -0800 (PST) (envelope-from peter) From: Peter Wemm To: "Joel V." , Date: Mon, 15 Dec 2003 09:02:39 -0800 User-Agent: KMail/1.5.4 References: <000201c3c2a4$07423370$1900a8c0@CHARON> In-Reply-To: <000201c3c2a4$07423370$1900a8c0@CHARON> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312150902.39091.peter@wemm.org> Subject: Re: 5.2 and amd64 - good enough for a production server? 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, 15 Dec 2003 17:02:44 -0000 On Sunday 14 December 2003 04:40 pm, Joel V. wrote: > Just making sure I understand everything, before I go to my boss and tell > him to buy a 4000$ opteron box. =) If you have the time, what I actually suggest is that you get hold of a smaller configuration machine and have a tinker first. That also gives you a place to experiment first before going live with stuff anyway. > 1) All the ports are working fine? I can go to /usr/ports/x and make > install clean and I got myself a 64-bit binary working on a 64-bit > operating system? (I'm mainly interested in Apache, qmail, vpopmail, > proftpd and samba, which are quite essential to have.) All the ports? No. Not all the ports even work on the i386 version of 5.x. It does have a few that are broken because of 64-bit issues, but it isn't all that far behind i386. All the ones that you mentioned above are quite OK for example though. > 2) AMD64 version of 5.2 will support the same amount of hardware than i368 > version? The most important area of support being RAID controllers, for me > at least. (Adaptec SCSI for booting and system disks, 3ware ATA for > dedicated backup disks. Oh, and what about RAID management tools?) The only major chunk of hardware that I know of that has big issues is the Promise SX6000. The driver tries to use a 32 bit field in a hardware data structure to store a 64 bit pointer. Just about everything else works (or can be made to work) though. What raid tools are you looking for? If you mean things like aaccli, 3dmd, etc, I haven't tried them. The 32 bit binaries might work. > 3) Last but not least - 32-bit compatibility? I know Linux binary > compatibility, both 32-bit and 64-bit is NOT DONE, but when will it be? > Will it take a month, half a year or more? Its not a matter of life and > death, but it would be good to know. And as far as I understand, at this > moment I cannot also run 32-bit FreeBSD binaries from earlier 5.x releases? FreeBSD/i386 binary compatability is a bit green at the moment. It works for a good number of smaller userland applications (I use it for the i386 perforce client, for example) but it is not likely to work for system level binaries. ie: you can't yet take an amd64 kernel and boot an installed i386 system with it. However, being able to do this is a definate goal. Or at least run it inside a chroot/jail/etc. cvsup still breaks for reasons that I do not understand... that one has got me completely stumped. The 32 bit emulation code does not have the FreeBSD-3.x and earlier compatability system calls implemented yet. It will not run older 3.x binaries. Certainly not a.out binaries either. I wouldn't like to guestimate a timeline for the linux stuff though. There are a number of things I want to be able to run so it'll happen sometime soon. (eg: acrobat reader) > Please be not offended by my outrageously newbie-esque questions. Dont forget that an opteron machine makes a Damn Fine i386 machine. My personal experiences suggest that an opteron gives an equivalent xeon system a good run for its money. If it turns out you're not ready for 5.x yet, you still can run 4.9/i386 on it, and it'll work very very well. It might seem a bit silly to consider this, but you do have a viable choice. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 09:38:36 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 3136816A4CE for ; Mon, 15 Dec 2003 09:38:36 -0800 (PST) Received: from mail1.texoma.net (mail1.texoma.net [209.151.96.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 0F8A243D2D for ; Mon, 15 Dec 2003 09:38:34 -0800 (PST) (envelope-from jhouchin@texoma.net) Received: (qmail 30007 invoked from network); 15 Dec 2003 17:38:33 -0000 Received: from ppp-151-100-057.texoma.net (HELO texoma.net) (209.151.100.57) by mail1.texoma.net with SMTP; 15 Dec 2003 17:38:33 -0000 Message-ID: <3FDDF2BE.6000009@texoma.net> Date: Mon, 15 Dec 2003 11:43:26 -0600 From: Jimmie Houchin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm References: <3FD92A43.5080205@texoma.net> <200312141746.43327.peter@wemm.org> In-Reply-To: <200312141746.43327.peter@wemm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: amd64 freebsd Subject: Re: kernel compile failure 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, 15 Dec 2003 17:38:36 -0000 Peter Wemm wrote: > On Thursday 11 December 2003 06:38 pm, Jimmie Houchin wrote: Hello Peter, Thanks for the reply. >>And... >>In the RAID configuration (I think) it had a Promise SX6000 support. >>I have the Promise onboard SATA RAID controller. >>I didn't see explicit Promise SATA support but I know it is somewhere >>because I and FreeBSD are using it. Is the support coming from the >>SX6000 kernel option? > > The SX6000 is the pst driver above. It might not be *that* hard to update it, > but if you ask Soren (sos@freebsd.org) very nicely, he might take a shot at > it. Okay. I have the Arima RioWorks HDAMA motherboard, which is to my understanding what, sledge.freebsd.org is running. http://www.rioworks.com/HDAMA.htm It has the Integrated Promise PDC20319 Serial ATA 4 Ports, Supports RAID 0, 1, 10. Booting from the CD and running sysinstall the fdisk program recognizes the drives and the arrays correctly. What kernel module or driver is handling my controller? Any help greatly appreciated. Jimmie Houchin From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 09:40:52 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 02AE016A4CE for ; Mon, 15 Dec 2003 09:40:52 -0800 (PST) Received: from mail1.texoma.net (mail1.texoma.net [209.151.96.16]) by mx1.FreeBSD.org (Postfix) with SMTP id C6F5C43D3C for ; Mon, 15 Dec 2003 09:40:50 -0800 (PST) (envelope-from jhouchin@texoma.net) Received: (qmail 31825 invoked from network); 15 Dec 2003 17:40:50 -0000 Received: from ppp-151-100-057.texoma.net (HELO texoma.net) (209.151.100.57) by mail1.texoma.net with SMTP; 15 Dec 2003 17:40:50 -0000 Message-ID: <3FDDF348.6050002@texoma.net> Date: Mon, 15 Dec 2003 11:45:44 -0600 From: Jimmie Houchin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm References: <3FD87B7C.6050608@texoma.net> <200312141607.21395.peter@wemm.org> In-Reply-To: <200312141607.21395.peter@wemm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: amd64 freebsd Subject: Re: SV: Packages/Ports problem 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, 15 Dec 2003 17:40:52 -0000 Peter Wemm wrote: > On Thursday 11 December 2003 06:13 am, Jimmie Houchin wrote: [snip] >>>>Peter has cvsup-without-gui on his FreeBSD site. >>>>I just haven't been able to get it. >>>>To my understanding I currently only have the ftp program on my machine. >>>>I don't know how to use it to get the package. >>> >>>pkg_add -r cvsup-without-gui >> >>That has failed with something like no such file on server error. >> >>But I'm about to do a fresh install this afternoon/evening after I redo >>my partions and will try again. > > That would be because the port for cvsup hasn't been finished yet. I do have > a hacked up cvsup binary that might be enough to get you going. > > fetch http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz > pkg_add cvsup-without-gui-16.1h.tbz > > Known problems: you cannot use compression. If you set 'compress' on any of > your supfiles, it will crash. Thanks for this information. I'll see about giving it a try later. Jimmie Houchin From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 11:02:24 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 AE91D16A4CE for ; Mon, 15 Dec 2003 11:02:24 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0151943D41 for ; Mon, 15 Dec 2003 11:02:22 -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 hBFJ2LFR040415 for ; Mon, 15 Dec 2003 11:02:21 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBFJ2KFX040409 for freebsd-amd64@freebsd.org; Mon, 15 Dec 2003 11:02:20 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 15 Dec 2003 11:02:20 -0800 (PST) Message-Id: <200312151902.hBFJ2KFX040409@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, 15 Dec 2003 19:02:24 -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 2DF9416A4CE for ; Mon, 15 Dec 2003 13:47:29 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA6B743D36 for ; Mon, 15 Dec 2003 13:47:26 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost by pandora.cs.kun.nl via odin.cs.kun.nl [131.174.33.33] with ESMTP id hBFLlOUZ024518 (8.12.10/3.58); Mon, 15 Dec 2003 22:47:24 +0100 (MET) From: Adriaan de Groot To: Date: Mon, 15 Dec 2003 22:47:17 +0100 User-Agent: KMail/1.5.94 References: <000201c3c2a4$07423370$1900a8c0@CHARON> In-Reply-To: <000201c3c2a4$07423370$1900a8c0@CHARON> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200312152247.17652.adridg@cs.kun.nl> cc: "Joel V." Subject: Re: 5.2 and amd64 - good enough for a production server? 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, 15 Dec 2003 21:47:29 -0000 On Monday 15 December 2003 01:40, Joel V. wrote: > Just making sure I understand everything, before I go to my boss and tell > him to buy a 4000$ opteron box. =) Like Peter said, get a $1000 amd64 box first, to test on. > 1) All the ports are working fine? I can go to /usr/ports/x and make > install clean and I got myself a 64-bit binary working on a 64-bit > operating system? (I'm mainly interested in Apache, qmail, vpopmail, > proftpd and samba, which are quite essential to have.) Things with definite issues that I've run across: lang/gcl - pointers in int madness lang/cmucl - binary-only i386 distribution graphics/acroread - binary only linux i386 distribution Hardly stuff you're likely to run on a big server box, though. Standard workstation fare runs fine as well. -- pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot If the door is ajar, can we fill it with door-jamb? From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 13:57:58 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 8322916A4CE for ; Mon, 15 Dec 2003 13:57:58 -0800 (PST) Received: from mail2.texoma.net (mail2.texoma.net [209.151.96.17]) by mx1.FreeBSD.org (Postfix) with SMTP id A519243D45 for ; Mon, 15 Dec 2003 13:57:49 -0800 (PST) (envelope-from jhouchin@texoma.net) Received: (qmail 15896 invoked from network); 15 Dec 2003 21:57:48 -0000 Received: from ppp-151-100-074.texoma.net (HELO texoma.net) (209.151.100.74) by mail2.texoma.net with SMTP; 15 Dec 2003 21:57:48 -0000 Message-ID: <3FDE2E65.8080407@texoma.net> Date: Mon, 15 Dec 2003 15:57:57 -0600 From: Jimmie Houchin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adriaan de Groot References: <000201c3c2a4$07423370$1900a8c0@CHARON> <200312152247.17652.adridg@cs.kun.nl> In-Reply-To: <200312152247.17652.adridg@cs.kun.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@FreeBSD.org Subject: Re: 5.2 and amd64 - good enough for a production server? 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, 15 Dec 2003 21:57:58 -0000 Adriaan de Groot wrote: [snip] > Things with definite issues that I've run across: > > lang/gcl - pointers in int madness > lang/cmucl - binary-only i386 distribution > graphics/acroread - binary only linux i386 distribution > > Hardly stuff you're likely to run on a big server box, though. Standard > workstation fare runs fine as well. acroread failed to build on my Gentoo AMD64 install as well. However it has gpdf (gnome pdf) Which I recently used to view some PDFs. The instant-workstation port failed to build for me because it required acroread. Maybe the instant-workstation could drop the requirement for acroread and substitute gpdf, xpdf and/or kpdf (or whatever KDE uses) for the PDF reader depending on desktop choice. Just a thought. Jimmie Houchin From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 15 18:25:10 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 BC92016A4CF for ; Mon, 15 Dec 2003 18:25:10 -0800 (PST) Received: from debussy.private.org (25.60.138.210.bn.2iij.net [210.138.60.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA14A43D36 for ; Mon, 15 Dec 2003 18:25:08 -0800 (PST) (envelope-from chat95@mbox.kyoto-inet.or.jp) Received: from localhost (localhost [127.0.0.1]) by debussy.private.org (8.12.10/8.12.10) with ESMTP id hBG2QGhp003058; Tue, 16 Dec 2003 11:26:17 +0900 (JST) (envelope-from chat95@mbox.kyoto-inet.or.jp) Date: Tue, 16 Dec 2003 11:26:16 +0900 (JST) Message-Id: <20031216.112616.730555543.chat95@mbox.kyoto-inet.or.jp> To: joel@almic.ee From: Nakata Maho In-Reply-To: <000201c3c2a4$07423370$1900a8c0@CHARON> References: <000201c3c2a4$07423370$1900a8c0@CHARON> Organization: private X-Mailer: Mew version 3.3 on XEmacs 21.4.14 (Reasonable Discussion) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@FreeBSD.org Subject: Re: 5.2 and amd64 - good enough for a production server? 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, 16 Dec 2003 02:25:10 -0000 Hi, Joel > Just making sure I understand everything, before I go to my boss and tell > him to buy a 4000$ opteron box. =) I've purchased already :) > 3) Last but not least - 32-bit compatibility? I know Linux binary > compatibility, both 32-bit and 64-bit is NOT DONE, but when will it be? Will > it take a month, half a year or more? Its not a matter of life and death, > but it would be good to know. And as far as I understand, at this moment I > cannot also run 32-bit FreeBSD binaries from earlier 5.x releases? 4) and 4.9-RELEASE (i386) doesn't work, hangs while looking for ad0 --maho From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 10:16:46 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 A5C3D16A4CE for ; Tue, 16 Dec 2003 10:16:46 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC9E43D3C for ; Tue, 16 Dec 2003 10:16:45 -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 hBGIGWRm025507; Tue, 16 Dec 2003 10:16:32 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id hBGIGVFn025506; Tue, 16 Dec 2003 10:16:31 -0800 (PST) (envelope-from obrien) Date: Tue, 16 Dec 2003 10:16:31 -0800 From: "David O'Brien" To: Jimmie Houchin Message-ID: <20031216181631.GA25331@dragon.nuxi.com> References: <000201c3c2a4$07423370$1900a8c0@CHARON> <200312152247.17652.adridg@cs.kun.nl> <3FDE2E65.8080407@texoma.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FDE2E65.8080407@texoma.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-BETA 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: freebsd-amd64@FreeBSD.org Subject: Re: 5.2 and amd64 - good enough for a production server? 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: Tue, 16 Dec 2003 18:16:46 -0000 On Mon, Dec 15, 2003 at 03:57:57PM -0600, Jimmie Houchin wrote: > >Things with definite issues that I've run across: ... > >graphics/acroread - binary only linux i386 distribution > >Hardly stuff you're likely to run on a big server box, though. Standard > >workstation fare runs fine as well. > > acroread failed to build on my Gentoo AMD64 install as well. Huh? Acroread is a binary distributed by Adobe. One can only install it, not build it. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 11:16:34 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 267E516A4CE; Tue, 16 Dec 2003 11:16:34 -0800 (PST) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78B2843D1F; Tue, 16 Dec 2003 11:16:14 -0800 (PST) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) hBGJGDv9053853; Tue, 16 Dec 2003 14:16:13 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id hBGJGDDt053852; Tue, 16 Dec 2003 14:16:13 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Date: Tue, 16 Dec 2003 14:16:13 -0500 (EST) Message-Id: <200312161916.hBGJGDDt053852@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, amd64@freebsd.org Precedence: bulk Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2003 19:16:34 -0000 TB --- 2003-12-16 18:09:45 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-12-16 18:09:45 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-12-16 18:09:45 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-12-16 18:13:40 - building world TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2003-12-16 19:14:05 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Dec 16 19:14:05 GMT 2003 [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/an/if_an_isa.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/an/if_an_pccard.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/an/if_an_pci.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/asr/asr.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/ata-all.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=20000 -fno-strict-aliasing -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/ata-queue.c /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/ata-queue.c: In function `ata_completed': /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/dev/ata/ata-queue.c:255: warning: long long int format, u_int64_t arg (arg 2) *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/amd64/amd64/src. TB --- 2003-12-16 19:16:13 - TB --- /usr/bin/make returned exit code 1 TB --- 2003-12-16 19:16:13 - TB --- ERROR: failed to build generic kernel TB --- 2003-12-16 19:16:13 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 12:26:29 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 0714116A4CF for ; Tue, 16 Dec 2003 12:26:29 -0800 (PST) Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.131.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8854743D2D for ; Tue, 16 Dec 2003 12:26:27 -0800 (PST) (envelope-from jlfenton@citlink.net) Received: (qmail 22659 invoked from network); 16 Dec 2003 20:26:26 -0000 Received: from unknown (HELO citlink.net) ([67.136.217.1]) (envelope-sender ) by relay02.roc.ny.frontiernet.net (FrontierMTA 2.3.6) with SMTP for ; 16 Dec 2003 20:26:26 -0000 Message-ID: <3FDF6A79.8050609@citlink.net> Date: Tue, 16 Dec 2003 13:26:33 -0700 From: Joe Fenton User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20031216200054.1086816A564@hub.freebsd.org> In-Reply-To: <20031216200054.1086816A564@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 5.2 and amd64 - good enough for a production server? 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, 16 Dec 2003 20:26:29 -0000 > From: Nakata Maho > Subject: Re: 5.2 and amd64 - good enough for a production server? > > 4) and 4.9-RELEASE (i386) doesn't work, hangs while looking for ad0 Is this when trying to boot? I ran into something that sounds similar on my MSI Master2-FAR Opteron system - when booting, it would start to list the devices, but only show the floppy. It was like it was hanging while looking for the harddrive. Actually, it was hanging while looking for drive B. I had a USB floppy plugged into the system which the BIOS mapped as B. The FreeBSD booter can't handle a USB floppy mapped as B. Unplugging the USB floppy allowed the booter to run properly. I imagine that disabling the BIOS support of the USB floppy would also work. I've debated whether or not to fill out a FreeBSD bug report on this. I haven't seen a report of this in the list, but a few were similar. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 14:06:54 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 B56F016A4CE for ; Tue, 16 Dec 2003 14:06:54 -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 9599143D33 for ; Tue, 16 Dec 2003 14:06:53 -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 hBGM6qo8079696 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Dec 2003 16:06:52 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id hBGM6qmI079693; Tue, 16 Dec 2003 16:06:52 -0600 (CST) Date: Tue, 16 Dec 2003 16:06:52 -0600 (CST) Message-Id: <200312162206.hBGM6qmI079693@bigtex.jrv.org> From: James Van Artsdalen To: freebsd-amd64@freebsd.org Subject: lock order reversal 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, 16 Dec 2003 22:06:54 -0000 2 x Opteron 244 with 8 GB 333 RAM, using the 5.2beta AMD64 ISO. Tyan K8W S2885. This appeared in my log: Dec 16 02:00:37 opteron kernel: lock order reversal Dec 16 02:00:37 opteron kernel: 1st 0xffffff0165ea3c40 vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 Dec 16 02:00:37 opteron kernel: 2nd 0xffffffff807c83e0 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pager.c:1838 Dec 16 02:00:37 opteron kernel: 3rd 0xffffff01f0fc22a0 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:876 Dec 16 02:00:37 opteron kernel: Stack backtrace: The console has another ~ 25 lines of debug info that weren't logged anywhere as far as I can tell. Do I need to write this down by hand for anyone? From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 19:14:37 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 18E3816A4CE; Tue, 16 Dec 2003 19:14:37 -0800 (PST) Received: from mail.cableone.net (scanmail1.cableone.net [24.116.0.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B8743D33; Tue, 16 Dec 2003 19:14:29 -0800 (PST) (envelope-from jhouchin@texoma.net) Received: from texoma.net (unverified [24.116.250.217]) by smail1.cableone.net (SurgeMail 1.5d2) with ESMTP id 2025029 for multiple; Tue, 16 Dec 2003 20:12:36 -0700 Message-ID: <3FDFCA12.4010005@texoma.net> Date: Tue, 16 Dec 2003 21:14:26 -0600 From: Jimmie Houchin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.5) Gecko/20031212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@FreeBSD.org References: <000201c3c2a4$07423370$1900a8c0@CHARON> <200312152247.17652.adridg@cs.kun.nl> <3FDE2E65.8080407@texoma.net> <20031216181631.GA25331@dragon.nuxi.com> In-Reply-To: <20031216181631.GA25331@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: Adriaan de Groot cc: freebsd-amd64@FreeBSD.org Subject: Re: 5.2 and amd64 - good enough for a production server? 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, 17 Dec 2003 03:14:37 -0000 David O'Brien wrote: > On Mon, Dec 15, 2003 at 03:57:57PM -0600, Jimmie Houchin wrote: > >>>Things with definite issues that I've run across: > > ... > >>>graphics/acroread - binary only linux i386 distribution >>>Hardly stuff you're likely to run on a big server box, though. Standard >>>workstation fare runs fine as well. >> >>acroread failed to build on my Gentoo AMD64 install as well. > > > Huh? Acroread is a binary distributed by Adobe. One can only install > it, not build it. You are correct. I forgot. Since on Gentoo all I did was bash # emerge acroread And Gentoo downloaded and installed it, I had forgotten. Most Gentoo is source, and with the exception on a single item I have not knowingly installed a precompiled package. That is two now that you have brought acroread to my remembrance. What I erringly remembered as the build failing was acroread failing to run do to some library issues. Jimmie Houchin From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 16 21:50:01 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 30E5F16A4CE for ; Tue, 16 Dec 2003 21:50:01 -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 3FE3543D33 for ; Tue, 16 Dec 2003 21:49:59 -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 hBH5nwo8096169 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Dec 2003 23:49:58 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id hBH5nwKF096166; Tue, 16 Dec 2003 23:49:58 -0600 (CST) Date: Tue, 16 Dec 2003 23:49:58 -0600 (CST) Message-Id: <200312170549.hBH5nwKF096166@bigtex.jrv.org> From: James Van Artsdalen To: freebsd-amd64@freebsd.org Subject: Re: emacs? 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, 17 Dec 2003 05:50:01 -0000 I got port xemacs-devel to build and run. There are two bugs: 1. An rlimit value is stored 32-bit int, truncating the value and confusing the allocator. This is in the xemacs sources. 2. unexelf.c was only using 32 bit things instead of 64. In this case it is the FreeBSD ports patch file that actually needs to change (these lines aren't present at all in the xemacs distribution). The second change should instead be something like #if sizeof(char *) == 8 or some such. *** mem-limits.h.~1~ Wed Aug 27 12:26:21 2003 --- mem-limits.h Tue Dec 16 22:10:00 2003 *************** *** 108,114 **** static POINTER data_space_start; /* Number of bytes of writable memory we can expect to be able to get */ ! extern unsigned int lim_data; #if defined (HEAP_IN_DATA) && !defined(PDUMP) extern unsigned long static_heap_size; --- 108,114 ---- static POINTER data_space_start; /* Number of bytes of writable memory we can expect to be able to get */ ! extern rlim_t lim_data; #if defined (HEAP_IN_DATA) && !defined(PDUMP) extern unsigned long static_heap_size; *** unexelf.c.~1~ Tue Dec 16 22:02:06 2003 --- unexelf.c Tue Dec 16 22:35:43 2003 *************** *** 475,481 **** # include #endif ! #if defined(__FreeBSD__) && defined(__alpha__) # ifdef __STDC__ # define ElfW(type) Elf64_##type # else --- 475,481 ---- # include #endif ! #if defined(__FreeBSD__) && (defined(__alpha__) || defined(__amd64)) # ifdef __STDC__ # define ElfW(type) Elf64_##type # else From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 17 01:43:00 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 18AEE16A4CE for ; Wed, 17 Dec 2003 01:43:00 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22CA943D50 for ; Wed, 17 Dec 2003 01:42:58 -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 hBH9gtRm036660; Wed, 17 Dec 2003 01:42:55 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id hBH9grrl036654; Wed, 17 Dec 2003 01:42:53 -0800 (PST) (envelope-from obrien) Date: Wed, 17 Dec 2003 01:42:52 -0800 From: "David O'Brien" To: James Van Artsdalen Message-ID: <20031217094252.GA36486@dragon.nuxi.com> References: <200312170549.hBH5nwKF096166@bigtex.jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312170549.hBH5nwKF096166@bigtex.jrv.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-BETA 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: emacs? 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: Wed, 17 Dec 2003 09:43:00 -0000 On Tue, Dec 16, 2003 at 11:49:58PM -0600, James Van Artsdalen wrote: > I got port xemacs-devel to build and run. There are two bugs: Thanks for the patch. Can you please send the diff to the maintainer of the port, gj@FreeBSD.org. Both Peter and myself are vi(ish) users. :-) When you forward your patch to gj, the canonical symbol on FreeBSD to use is "__amd64__" -- David From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 17 04:25: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 3F5A816A4CE for ; Wed, 17 Dec 2003 04:25:04 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6630B43D1D for ; Wed, 17 Dec 2003 04:25:02 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl by wn1.sci.kun.nl id hBHCP1Yj025374 (8.12.10/3.58); Wed, 17 Dec 2003 13:25:01 +0100 (MET) Date: Wed, 17 Dec 2003 13:25:01 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org In-Reply-To: <200312170549.hBH5nwKF096166@bigtex.jrv.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: emacs? 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: Wed, 17 Dec 2003 12:25:04 -0000 On Tue, 16 Dec 2003, James Van Artsdalen wrote: > 2. unexelf.c was only using 32 bit things instead of 64. > In this case it is the FreeBSD ports patch file that actually > needs to change (these lines aren't present at all in the > xemacs distribution). Mmm-hmm. That's pretty much the same kind of things I ran into while porting gcl 2.5.3 (the i386 port compiles and then crashes immediately while bootstrapping). If gcl is still actively maintained it should get the fixes from emacs eventually. Once I've actually got it running I'll post the patches here as well. (Oh, and please please use unidiff (diff -u), since it's so much easier to read.) -- 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 Wed Dec 17 19:02:35 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 6949416A4CF for ; Wed, 17 Dec 2003 19:02:35 -0800 (PST) Received: from priv-edtnes56.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37E4543D2D for ; Wed, 17 Dec 2003 19:02:33 -0800 (PST) (envelope-from fbanks@telus.net) Received: from pig ([142.59.224.37]) by priv-edtnes56.telusplanet.net (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with SMTP id <20031218030232.DBMC12913.priv-edtnes56.telusplanet.net@pig> for ; Wed, 17 Dec 2003 20:02:32 -0700 Message-ID: <000801c3c513$57a5a5b0$f902a8c0@pig> From: "Frank" To: Date: Wed, 17 Dec 2003 20:02:15 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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: Thu, 18 Dec 2003 03:02:35 -0000 From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 18 00:34:17 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 5E9A516A4CE for ; Thu, 18 Dec 2003 00:34: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 C588443D36 for ; Thu, 18 Dec 2003 00:34: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 hBI8YAo8086088 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 02:34:10 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id hBI8YA9S086085; Thu, 18 Dec 2003 02:34:10 -0600 (CST) Date: Thu, 18 Dec 2003 02:34:10 -0600 (CST) Message-Id: <200312180834.hBI8YA9S086085@bigtex.jrv.org> From: James Van Artsdalen To: freebsd-amd64@freebsd.org Subject: port editors/emacs21 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: Thu, 18 Dec 2003 08:34:17 -0000 I got port editors/emacs21 to build and run on Freebsd-5.2-current x86-64. There are three changes: 1. An AMD64 machine file is needed but not present in the emacs21 sources. I derived this file from alpha.h, removed a bunch of obsolete conditional code, and named this file amd64.h. 2. An rlimit value is stored 32-bit int, truncating the value. This is in the emacs21 sources. 3. A configure.in change is needed to recognize target amd64--freebsd. Without this emasc21 tries to compile with machine file "m/.h". This patch changes code created by FreeBSD ports patch file patch-configure.in, not code in the emacs21 base sources. --- src/m/amd64.h~ Wed Dec 31 18:00:00 1969 +++ src/m/amd64.h Thu Dec 18 00:21:51 2003 @@ -0,0 +1,181 @@ +/* machine description file For the amd64 chip. + Copyright (C) 1994, 1997, 1999 Free Software Foundation, Inc. + +This file is part of GNU Emacs. + +GNU Emacs is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GNU Emacs is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GNU Emacs; see the file COPYING. If not, write to +the Free Software Foundation, Inc., 59 Temple Place - Suite 330, +Boston, MA 02111-1307, USA. */ + + +/* The following line tells the configuration script what sort of + operating system this machine is likely to run. + USUAL-OPSYS="note" + +NOTE-START +Use -opsystem=freebsd +NOTE-END + +*/ + +#define BITS_PER_LONG 64 +#define BITS_PER_EMACS_INT 64 +#ifndef _LP64 +#define _LP64 +#endif + +/* Define WORDS_BIG_ENDIAN iff lowest-numbered byte in a word + is the most significant byte. */ + +#undef WORDS_BIG_ENDIAN + +/* Define NO_ARG_ARRAY if you cannot take the address of the first of a + * group of arguments and treat it as an array of the arguments. */ + +#define NO_ARG_ARRAY + +/* Now define a symbol for the cpu type, if your compiler + does not define it automatically: + Ones defined so far include vax, m68000, ns16000, pyramid, + orion, tahoe, APOLLO and many others */ + +/* __amd64__ defined automatically */ + + +/* Use type EMACS_INT rather than a union, to represent Lisp_Object */ +/* This is desirable for most machines. */ + +#define NO_UNION_TYPE + +/* Define the type to use. */ +#define EMACS_INT long +#define EMACS_UINT unsigned long +#define SPECIAL_EMACS_INT + +/* Define EXPLICIT_SIGN_EXTEND if XINT must explicitly sign-extend + the 24-bit bit field into an int. In other words, if bit fields + are always unsigned. + + If you use NO_UNION_TYPE, this flag does not matter. */ + +#undef EXPLICIT_SIGN_EXTEND + +/* Data type of load average, as read out of kmem. */ + +#define LOAD_AVE_TYPE long + +/* Convert that into an integer that is 100 for a load average of 1.0 */ + +#define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE) + +/* Define C_ALLOCA if this machine does not support a true alloca + and the one written in C should be used instead. + Define HAVE_ALLOCA to say that the system provides a properly + working alloca function and it should be used. + Define neither one if an assembler-language alloca + in the file alloca.s should be used. */ + +#define HAVE_ALLOCA + +/* GNU malloc and the relocating allocator do not work together + with X. [Who wrote that?] */ + +/* May 1995: reportedly [Rainer Schoepf ] both the + system and the gnu malloc system work with "alpha-dec-osf3.0" and + "alpha-dec-osf3.2". */ + +/* May 1995: it seems to me [Morten Welinder ] that both + mallocs work with "alpha-dec-osf2.0", but I daren't break anything + right now. Feel free to play if you want. */ + +/* #define SYSTEM_MALLOC */ + +#ifdef __ELF__ +/* With ELF, make sure that all common symbols get allocated to in the + data section. Otherwise, the dump of temacs may miss variables in + the shared library that have been initialized. For example, with + GNU libc, __malloc_initialized would normally be resolved to the + shared library's .bss section, which is fatal. */ +# ifdef __GNUC__ +# define C_SWITCH_MACHINE -fno-common +# else +# error What gives? Fix me if DEC Unix supports ELF now. +# endif +#endif + +#if defined(__OpenBSD__) +#define ORDINARY_LINK +#endif + +#ifdef __ELF__ +#undef UNEXEC +#define UNEXEC unexelf.o +#endif + +#if defined (LINUX) && __GNU_LIBRARY__ - 0 < 6 +/* This controls a conditional in main. */ +#define LINUX_SBRK_BUG +#endif + + +#define PNTR_COMPARISON_TYPE unsigned long + +/* On the 64 bit architecture, we can use 60 bits for addresses */ + +#define VALBITS 60 + + +/* This definition of MARKBIT is necessary because of the comparison of + ARRAY_MARK_FLAG and MARKBIT in an #if in lisp.h, which cpp doesn't like. */ + +/* #define MARKBIT 0x8000000000000000L */ + + +/* Define XINT and XUINT so that they can take arguments of type int */ + +#define XINT(a) (((long) (a) << (BITS_PER_LONG - VALBITS)) >> (BITS_PER_LONG - VALBITS)) +#define XUINT(a) ((long) (a) & VALMASK) + +/* Define XPNTR to avoid or'ing with DATA_SEG_BITS */ + +#define XPNTR(a) XUINT (a) + +#ifndef NOT_C_CODE +/* We need these because pointers are larger than the default ints. */ +#if !defined(__NetBSD__) && !defined(__OpenBSD__) && !defined(__FreeBSD__) +#include +#endif +#endif /* not NOT_C_CODE */ + +/* On the Alpha it's best to avoid including TERMIO since struct + termio and struct termios are mutually incompatible. */ +/* #define NO_TERMIO */ + +#if defined (LINUX) || defined (__NetBSD__) || defined (__OpenBSD__) +# define TEXT_END ({ extern int _etext; &_etext; }) +# ifndef __ELF__ +# define COFF +# define DATA_END ({ extern int _EDATA; &_EDATA; }) +# endif /* notdef __ELF__ */ +#endif + +#if (defined (__NetBSD__) || defined (__OpenBSD__)) && defined (__ELF__) +#define HAVE_TEXT_START +#endif + +/* Many Alpha implementations (e.g. gas 2.8) can't handle DBL_MIN: + they generate code that uses a signaling NaN instead of DBL_MIN. + Define DBL_MIN_REPLACEMENT to be the next value larger than DBL_MIN: + this avoids the assembler bug. */ +/* #define DBL_MIN_REPLACEMENT 2.2250738585072019e-308 */ --- src/mem-limits.h.~1~ Wed Mar 8 12:49:46 2000 +++ src/mem-limits.h Wed Dec 17 03:15:24 2003 @@ -98,7 +98,7 @@ static POINTER data_space_start; /* Number of bytes of writable memory we can expect to be able to get */ -static unsigned long lim_data; +static rlim_t lim_data; #ifdef NO_LIM_DATA static void --- configure.in~ Tue Dec 16 23:54:24 2003 +++ configure.in Thu Dec 18 00:29:35 2003 @@ -184,6 +184,7 @@ opsys=freebsd case "${canonical}" in alpha*-*-freebsd*) machine=alpha ;; + amd64-*-freebsd*) machine=amd64 ;; i[3456]86-*-freebsd*) machine=intel386 ;; sparc64-*-freebsd*) machine=sparc ;; esac From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 18 17:31:54 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 65DF616A4CE for ; Thu, 18 Dec 2003 17:31:54 -0800 (PST) Received: from mail.via.net (mail.via.net [209.81.9.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C42D43D3F for ; Thu, 18 Dec 2003 17:31:53 -0800 (PST) (envelope-from joe@via.net) Received: from [209.81.2.10] (monk.via.net [209.81.2.10]) by mail.via.net (8.12.9p1/8.12.7) with ESMTP id hBJ1TpEa064395 for ; Thu, 18 Dec 2003 17:29:51 -0800 (PST) (envelope-from joe@via.net) User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Thu, 18 Dec 2003 17:32:09 -0800 From: joe mcguckin To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Current Status ? 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, 19 Dec 2003 01:31:54 -0000 Hi Folks. What's the current status of AMD64? Does FreeBSD run native 64 bit? How stable is it? Is there a preferred motherboard or system vendor? Thanks! Joe From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 18 18:42:08 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 93E3F16A4CE for ; Thu, 18 Dec 2003 18:42:08 -0800 (PST) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id A302243D45 for ; Thu, 18 Dec 2003 18:42:07 -0800 (PST) (envelope-from peter@yahoo-inc.com) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 72F1C881E; Thu, 18 Dec 2003 18:42:07 -0800 (PST) From: Peter Wemm To: joe mcguckin , Date: Thu, 18 Dec 2003 18:42:07 -0800 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312181842.07079.peter@wemm.org> Subject: Re: Current Status ? 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, 19 Dec 2003 02:42:08 -0000 On Thursday 18 December 2003 05:32 pm, joe mcguckin wrote: > Hi Folks. > > What's the current status of AMD64? Does FreeBSD run native 64 bit? > How stable is it? Generally its in pretty good shape. We're looking for a formal tier-1 release for 5.2. You can grab the release candidates already. > Is there a preferred motherboard or system vendor? There are none that I know of that we don't run on. However, at this stage, avoid the nVidia nForce based boards like the plague. There is something very funny going on with the APIC on that chipset. I have an Asus SK8N at home and I turn off the IO apic mode in the bios. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 19 13:21:42 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 7A12E16A4CE for ; Fri, 19 Dec 2003 13:21:42 -0800 (PST) Received: from relay4.san1.attens.com (relay4.san2.attens.com [192.215.81.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 594F243D48 for ; Fri, 19 Dec 2003 13:21:38 -0800 (PST) (envelope-from dfn@novaknet.net) Received: from novaknet.net (chi-30-a-14.chi.dsl.cerfnet.com [209.187.84.14]) by relay4.san1.attens.com (8.11.6/8.9.3) with ESMTP id hBJLLas04523 for ; Fri, 19 Dec 2003 21:21:37 GMT Message-ID: <3FE36BDD.5070509@novaknet.net> Date: Fri, 19 Dec 2003 15:21:33 -0600 From: "Donald F. Novak" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Sucess with 5.1 but not 5.2 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, 19 Dec 2003 21:21:42 -0000 Got a new Emachines T6000 AMD64. 5.1 works fine thanks. 5.2 has problems. Have not dug into it yet. Emachines does not help very much! Will continue to work with 5.2. Don From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 19 14:31:32 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 7BF1F16A4CE for ; Fri, 19 Dec 2003 14:31:32 -0800 (PST) Received: from colo2.RCousins.com (colo2.rcousins.com [198.144.196.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2E3843D31 for ; Fri, 19 Dec 2003 14:31:31 -0800 (PST) (envelope-from rec@RCousins.com) Received: from RCousins.com (unknown [10.0.2.5]) by colo2.RCousins.com (Postfix) with ESMTP id 4C9BE117071 for ; Fri, 19 Dec 2003 14:31:31 -0800 (PST) Message-ID: <3FE37C45.9060309@RCousins.com> Date: Fri, 19 Dec 2003 14:31:33 -0800 From: Robert Cousins User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Analog interface support 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, 19 Dec 2003 22:31:32 -0000 Does anyone know about any ADC cards which are supported under this release? I've got an application where I'd love to sample an analog signal at about 30 Hz. My looking things over shows no obvious cards on the list. Suggestions appreciated. Thanx Bob Cousins From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 20 16:19:03 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 576BC16A4CE for ; Sat, 20 Dec 2003 16:19:03 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC9943D4C for ; Sat, 20 Dec 2003 16:19:02 -0800 (PST) (envelope-from freebsduser@comcast.net) Received: from 204.127.197.113 ([204.127.197.113]) by comcast.net (rwcrmhc12) with SMTP id <20031221001902014000libie>; Sun, 21 Dec 2003 00:19:02 +0000 Received: from [12.225.143.41] by 204.127.197.113; Sun, 21 Dec 2003 00:19:01 +0000 From: freebsduser@comcast.net To: freebsd-amd64@freebsd.org Date: Sun, 21 Dec 2003 00:19:01 +0000 Message-Id: <122120030019.15135.4953@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 27 2003) X-Authenticated-Sender: ZnJlZWJzZHVzZXJAY29tY2FzdC5uZXQ= Subject: Boot floppy panic 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, 21 Dec 2003 00:19:03 -0000 Trying to use the boot floppies kern.flp and mfsroot.flp on an Opteron 246 with an Asus SK8N mobo, 1 gb dual channel memory and such. After inserting the MFS root it seems to scoot along fine until.... Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x58:0x207c stack pointer = 0x10:0xf80 frame pointer = 0x10:0x0 = DPL 0, pres 1, def32 0, gran 0 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 9 panic: general protection fault Uptime: 1s