From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 26 09:31:15 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 3016216A4B3; Sun, 26 Oct 2003 09:31:15 -0800 (PST) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BEBC43F3F; Sun, 26 Oct 2003 09:31:14 -0800 (PST) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h9QHVDv9016548; Sun, 26 Oct 2003 12:31: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 h9QHVDrS016547; Sun, 26 Oct 2003 12:31:13 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Date: Sun, 26 Oct 2003 12:31:13 -0500 (EST) Message-Id: <200310261731.h9QHVDrS016547@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: Sun, 26 Oct 2003 17:31:15 -0000 TB --- 2003-10-26 17:16:11 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2003-10-26 17:16:11 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-10-26 17:16:11 - 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-10-26 17:18:02 - 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: populating /home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include >>> stage 4.2: building libraries [...] rpcgen -C -c -o yppasswd_private_xdr.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/../../usr.sbin/rpc.yppasswdd/yppasswd_private.x rm -f .depend mkdep -f .depend -a -I. /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_connect.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_error.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_free.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_new.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_passwd.c yp_clnt.c yppasswd_xdr.c yppasswd_clnt.c yppasswd_private_clnt.c yppasswd_private_xdr.c echo libypclnt.so.1: /home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/lib/librpcsvc.a >> .depend cc -O -pipe -I. -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_connect.c In file included from /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt/ypclnt_connect.c:45: /home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/rpcsvc/ypclnt.h:81: warning: `struct ypmaplist' declared inside parameter list /home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/rpcsvc/ypclnt.h:81: warning: its scope is only this definition or declaration, which is probably not what you want *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libypclnt. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. TB --- 2003-10-26 17:31:13 - TB --- /usr/bin/make returned exit code 1 TB --- 2003-10-26 17:31:13 - TB --- ERROR: failed to build world TB --- 2003-10-26 17:31:13 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 26 11:58:55 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 1B2F316A4BF for ; Sun, 26 Oct 2003 11:58:55 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0277143FB1 for ; Sun, 26 Oct 2003 11:58:54 -0800 (PST) (envelope-from RonDzierwa@comcast.net) Received: from comcast.net (esx132dhcp973.essex01.md.comcast.net[68.33.135.205]) by comcast.net (sccrmhc11) with SMTP id <2003102619585301100c2qsbe> (Authid: rondzierwa); Sun, 26 Oct 2003 19:58:53 +0000 Message-ID: <3F9C2791.4FB262E0@comcast.net> Date: Sun, 26 Oct 2003 14:59:13 -0500 From: Ron Dzierwa Organization: Innovative Engineering, Inc. X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: join 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, 26 Oct 2003 19:58:55 -0000 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 26 12:11: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 639C516A4B3 for ; Sun, 26 Oct 2003 12:11:58 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF79543FB1 for ; Sun, 26 Oct 2003 12:11:57 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id DD38C2A7EA for ; Sun, 26 Oct 2003 12:11:57 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: amd64@freebsd.org Date: Sun, 26 Oct 2003 12:11:57 -0800 From: Peter Wemm Message-Id: <20031026201157.DD38C2A7EA@canning.wemm.org> Subject: cvsup for 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, 26 Oct 2003 20:11:58 -0000 In case anybody is interested: http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz This is in pkg_add format. A couple of MAJOR caveats are in order: * It is built against 5.1-current, *after* the last ABI bump. It will not work on 5.1-RELEASE. I do not know if it works on David's snapshot or not. * The ezm3 package is not a happy camper. I'm still suprised that these binaries work at all. Obviously, be careful with these. I've had to do some really shameful hacks to get it to compile, including crippling some of the sorting. This might have negative affects elsewhere that I haven't found yet. YMMV. No warranty. Do not use to control nuclear power plants or life support equipment. * Stream compression does *NOT* seem to work at this point - it reports a zlib error at startup, so do not use the 'compress' keyword. * There is an X11 version there in my homedir, but it doesn't work. 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 Oct 27 11:01:45 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 796B216A4B3 for ; Mon, 27 Oct 2003 11:01:45 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5366A43FCB for ; Mon, 27 Oct 2003 11:01:36 -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.9/8.12.9) with ESMTP id h9RJ1aFY056617 for ; Mon, 27 Oct 2003 11:01:36 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h9RJ1ZrS056611 for freebsd-amd64@freebsd.org; Mon, 27 Oct 2003 11:01:35 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Oct 2003 11:01:35 -0800 (PST) Message-Id: <200310271901.h9RJ1ZrS056611@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, 27 Oct 2003 19:01:45 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/09/26] amd64/57250 amd64 Broken PTRACE_GETFPREGS and PTRACE_SETFPR 1 problem total. From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 27 11:56: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 A4CD716A4B3 for ; Mon, 27 Oct 2003 11:56:00 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D85E43FE3 for ; Mon, 27 Oct 2003 11:55:57 -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 for id h9RJts6G003471 (8.12.10/3.58); Mon, 27 Oct 2003 20:55:55 +0100 (MET) From: Adriaan de Groot To: amd64@freebsd.org Date: Mon, 27 Oct 2003 20:55:54 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310272055.54288.adridg@cs.kun.nl> Subject: bootstrapping 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, 27 Oct 2003 19:56:00 -0000 So, while I'm waiting for my K8V to be RMA'ed, I'm thinking about how to go about integrating this amd64 box into my network and getting it running. I gather there's no really working cvsup, and David's snapshot build from way back is (a) from wayback (b) unstable under load. I've got several running systems, both -STABLE and -CURRENT, with cvsupped /usr/src's. The /usr/src's are NFS exported, and I've got a spare cheap-ass NIC (yes, an RTL 8029). Supposing I boot a 4-STABLE drive with rl(4) in place in an amd64 box - what do I need to do to get it up to speed (heck, let's make it a 5-CURRENT drive, since we've got the 4-to-5 upgrade otherwise as well). - do I need to cvsup anything special? extra branches? are all the sources for all the architectures normally in a /usr/src/sys? - does X "just build" then? Getting all this (and the machine) together ought to take me a while, and I promise to be quite while that happens :) [ade] From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 27 12:54:48 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 5705116A4B3 for ; Mon, 27 Oct 2003 12:54:48 -0800 (PST) Received: from postoffice9.mail.cornell.edu (postoffice9.mail.cornell.edu [132.236.56.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D74E43FE0 for ; Mon, 27 Oct 2003 12:54:43 -0800 (PST) (envelope-from sbc28@cornell.edu) Received: from cwm (r102798.resnet.cornell.edu [128.253.186.154]) h9RKsepW027435; Mon, 27 Oct 2003 15:54:40 -0500 (EST) From: "Seth Chandler" To: "'Adriaan de Groot'" , Date: Mon, 27 Oct 2003 15:54:42 -0500 Message-ID: <000001c39ccc$8bdfb060$9abafd80@cwm> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <200310272055.54288.adridg@cs.kun.nl> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: RE: bootstrapping 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, 27 Oct 2003 20:54:48 -0000 I installed off of the FreeBSD 5.1-RELEASE CD, and copyed a /usr/src and /usr/ports tree to my AMD64 box. I did a make buildworld and a make buildkernel KERNCONF=GENERIC(actually I disabled the -CURRENT debugging in my own config file, but otherwise its exactly the same), then installed both and rebooted. I downloaded his cvsup snapshot, and added it. It seems to run fine for me actually, I just used my regular supfile (with ports-all and src-all), except without compress. I built a number of ports, and have had varying degrees of success. Ports that worked: x11/XFree86-4 www/apache2 lang/php4 (WITH_APACHE2="yes") some mail server stuff (postfix, courier-imap, spamassassin, procmail) perl 5.8.0 portupgrade (and ruby I guess :-P) postgresql (though I havn't done any testing, I just know it builds) sudo/screen/wget/bash2/zsh and of course vim :-) obviously most of these things are going to 'just work' because it's a standard *nix environment. Ports that needed some tweaking or didn't work completely: Samba-devel (3.0.0, I posted about this on the list earlier, so see the follow-ups to that) Mysql appeared to cause some weird kernel traps (trap 9, though I don't have the message available right now), but it ran (mostly) Ports that don't work Obviously ezm3/cvsup don't build from scratch Gnome2 and kde 3 aren't happy, I know one of them didn't like a library that wasn't built with -fPIC, I think that it was an XFree library though, I don't really remember. I'm sure there are a number of others that won't work without emulation (i.e. packages we don't' have the source code for), and anything that uses x86 assembly code will probably not work either :-) seth -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of Adriaan de Groot Sent: Monday, October 27, 2003 2:56 PM To: amd64@freebsd.org Subject: bootstrapping So, while I'm waiting for my K8V to be RMA'ed, I'm thinking about how to go about integrating this amd64 box into my network and getting it running. I gather there's no really working cvsup, and David's snapshot build from way back is (a) from wayback (b) unstable under load. I've got several running systems, both -STABLE and -CURRENT, with cvsupped /usr/src's. The /usr/src's are NFS exported, and I've got a spare cheap-ass NIC (yes, an RTL 8029). Supposing I boot a 4-STABLE drive with rl(4) in place in an amd64 box - what do I need to do to get it up to speed (heck, let's make it a 5-CURRENT drive, since we've got the 4-to-5 upgrade otherwise as well). - do I need to cvsup anything special? extra branches? are all the sources for all the architectures normally in a /usr/src/sys? - does X "just build" then? Getting all this (and the machine) together ought to take me a while, and I promise to be quite while that happens :) [ade] _______________________________________________ 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 Mon Oct 27 16:45:26 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 E7F6C16A513 for ; Mon, 27 Oct 2003 16:45:20 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDB42445CB for ; Mon, 27 Oct 2003 16:40:00 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id B39572A7EA; Mon, 27 Oct 2003 16:40:00 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Adriaan de Groot In-Reply-To: <200310272055.54288.adridg@cs.kun.nl> Date: Mon, 27 Oct 2003 16:40:00 -0800 From: Peter Wemm Message-Id: <20031028004000.B39572A7EA@canning.wemm.org> cc: amd64@freebsd.org Subject: Re: bootstrapping 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, 28 Oct 2003 00:45:26 -0000 Adriaan de Groot wrote: > So, while I'm waiting for my K8V to be RMA'ed, I'm thinking about how to go > about integrating this amd64 box into my network and getting it running. I > gather there's no really working cvsup, and David's snapshot build from way > back is (a) from wayback (b) unstable under load. cvsup works for for text mode. Just dont try using the GUI. Personally, I've installed about 6 or 7 amd64 systems over the last two weeks. I've taken 5.1-RELEASE cdrom, built a new kernel, rebooted with that, and then done a buildworld/installworld/mergemaster. It might be possible to upgrade in-place from an i386 release to amd64, but I have never tried it. I expect it would be rather exciting since we try and do things like run #!/bin/sh in scripts in the middle of installworld. So, if /bin/sh becomes an amd64 binary while you're running your i386 kernel, it will not work very well. > I've got several running systems, both -STABLE and -CURRENT, with cvsupped > /usr/src's. The /usr/src's are NFS exported, and I've got a spare cheap-ass > NIC (yes, an RTL 8029). Supposing I boot a 4-STABLE drive with rl(4) in place > in an amd64 box - what do I need to do to get it up to speed (heck, let's > make it a 5-CURRENT drive, since we've got the 4-to-5 upgrade otherwise as > well). > > - do I need to cvsup anything special? extra branches? are all the sources fo r > all the architectures normally in a /usr/src/sys? Start with a working amd64 system, and do whatever it takes to update to a -current kernel. If that means using rsync from another box, tar, cp -r over nfs, whatever, then thats what is needed. Just get a fresh /usr/src/sys and build a kernel and boot it. Then you should be on a stable footing to finish the world build. BTW; Dont use 'buildkernel' for the first step. Use config manually and restart the kernel build if it crashes in the middle. > - does X "just build" then? Yes, builds and installs and actually works. (He says as he types on an XFree86-4.3.0 port built on amd64). kde3 etc have build problems over a disagreement about which shared libs are supposed to be there. The same problem exists on i386, but it isn't fatal there. i386 can do impure shared libs (text relocations which defeat the "shared" part of the shared objects), amd64 cannot. > Getting all this (and the machine) together ought to take me a while, and I > promise to be quite while that happens :) It should be quite an adventure. If it'll help get started, I'm happy to take a generic kernel and matching libc.so.5 and put it somewhere so that folks starting from 5.1-REL or David's snapshot have an easier time getting started. That will be enough to be able to run cvsup and do a full buildworld and go from there. 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 Tue Oct 28 07:50: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 A1AF616A4CF for ; Tue, 28 Oct 2003 07:50:03 -0800 (PST) Received: from mail.ststelecom.com (ns2.ststelecom.com [216.82.101.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 24D2F43F3F for ; Tue, 28 Oct 2003 07:50:02 -0800 (PST) (envelope-from eric@fnordsystems.com) Received: (qmail 73873 invoked by uid 85); 28 Oct 2003 15:50:58 -0000 Received: from eric@fnordsystems.com by server4.saturnbandwidth.net by uid 82 with qmail-scanner-1.16 (spamassassin: 2.50. Clear:SA:0(-6.6/5.0):. Processed in 0.359496 secs); 28 Oct 2003 15:50:58 -0000 X-Qmail-Scanner-Mail-From: eric@fnordsystems.com via server4.saturnbandwidth.net X-Qmail-Scanner: 1.16 (Clear:SA:0(-6.6/5.0):. Processed in 0.359496 secs) Received: from unknown (HELO laptop.fnordsystems.com) (12.229.247.20) by 0 with SMTP; 28 Oct 2003 15:50:57 -0000 Message-Id: <5.2.0.9.2.20031028074313.03fe4670@216.82.101.6> X-Sender: eric@fnordsystems.com@216.82.101.6 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 28 Oct 2003 07:47:38 -0800 To: amd64-list@redhat.com From: Eric Kuhnke Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Status: No, hits=-6.6 required=5.0 tests=BAYES_01 version=2.53 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) cc: amd64@freebsd.org Subject: Opterons drop 30% in price today 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, 28 Oct 2003 15:50:03 -0000 As a reaction to Intel's price drop two days ago, AMD has dropped pricing on the 24x series of Opterons by approximately 30%. The 2.0GHz unit has not changed, but the 1.4, 1.6 and 1.8 are now 30% less expensive: http://www.heise.de/newsticker/data/ciw-27.10.03-001/ Old Intel prices: 3.2/800BX P4/3.2G 800MHZ 478PIN 512K BOX $581.00 3.06/533BX P4/3.06 533MHZ 478PIN 512K BOX $362.00 3.0/800BX P4/3.0G 800MHZ 478PIN 512K BOX $385.00 2.8/800BX P4/2.8G 800MHZ 478PIN 512K BOX $271.00 2.8/533BX P4/2.8G 533MHZ 478PIN 512K BX $254.00 New Intel prices: P4/3.2-478/800(512K) NA/409 P4/3.0-478/800(512K) NA/275 P4/3.06G-478/533(512K) NA/264 P4/2.8G-478/800(512K) 242/217 http://pc.watch.impress.co.jp/docs/2003/1028/pa_cphdd.htm From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 28 11:18:30 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 6994616A4CE for ; Tue, 28 Oct 2003 11:18:30 -0800 (PST) Received: from colo2.RCousins.com (colo2.rcousins.com [198.144.196.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id C547243F85 for ; Tue, 28 Oct 2003 11:18:29 -0800 (PST) (envelope-from rec@RCousins.com) Received: from RCousins.com (unknown [10.0.2.5]) by colo2.RCousins.com (Postfix) with ESMTP id 60C70117043 for ; Tue, 28 Oct 2003 11:18:29 -0800 (PST) Message-ID: <3F9EC10E.70403@RCousins.com> Date: Tue, 28 Oct 2003 11:18:38 -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: Timing of Amd64 & FreeBSD 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: Tue, 28 Oct 2003 19:18:30 -0000 Does anyone have a good estimate of when 5.2 will be released? Checking the Todo list shows that things are still a goodly ways off. Also, at the fast rate at which AMD64 is maturing, how long before it will be essentially as feature rich and port rich as i386? From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 28 11:46: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 2722916A4CE for ; Tue, 28 Oct 2003 11:46:08 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE6243F85 for ; Tue, 28 Oct 2003 11:46: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.9/8.12.9) with ESMTP id h9SJk6JC050626; Tue, 28 Oct 2003 11:46:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h9SJk5Nv050625; Tue, 28 Oct 2003 11:46:05 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Oct 2003 11:46:05 -0800 From: "David O'Brien" To: Robert Cousins Message-ID: <20031028194605.GA50559@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.1-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: Timing of Amd64 & FreeBSD 5.2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org, freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2003 19:46:08 -0000 On Tue, Oct 28, 2003 at 11:18:38AM -0800, Robert Cousins wrote: > Does anyone have a good estimate of when 5.2 will be released? > Checking the Todo list shows that things are still a goodly ways off. > > Also, at the fast rate at which AMD64 is maturing, how long before > it will be essentially as feature rich and port rich as i386? It is pretty close today. The largest things missing that a user may notice are SMP support (don't matter to Athlon64 users), Linux AMD64 compatability (not too many commercial Linux AMD64 apps at this time), complete FreeBSD/i386 compatability, complete Linux i386 compatability. Over the past month, FreeBSD/AMD64 has been more stable than FreeBSD/i386. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 28 12:06:09 2003 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 9F7FA16A4CE; Tue, 28 Oct 2003 12:06:09 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B128743FBF; Tue, 28 Oct 2003 12:06:08 -0800 (PST) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h9SK68FY039872; Tue, 28 Oct 2003 12:06:08 -0800 (PST) (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h9SK683V039868; Tue, 28 Oct 2003 12:06:08 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Oct 2003 12:06:08 -0800 (PST) From: "David E. O'Brien" Message-Id: <200310282006.h9SK683V039868@freefall.freebsd.org> To: obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org, obrien@FreeBSD.org Subject: Re: amd64/57250: Broken PTRACE_GETFPREGS and PTRACE_SETFPREGS 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, 28 Oct 2003 20:06:09 -0000 Synopsis: Broken PTRACE_GETFPREGS and PTRACE_SETFPREGS Responsible-Changed-From-To: freebsd-amd64->obrien Responsible-Changed-By: obrien Responsible-Changed-When: Tue Oct 28 12:05:52 PST 2003 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=57250 From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 28 12:13:27 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 4407516A4CE for ; Tue, 28 Oct 2003 12:13:27 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F7043F3F for ; Tue, 28 Oct 2003 12:13:26 -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.9/8.12.9) with ESMTP id h9SKDIJC051184; Tue, 28 Oct 2003 12:13:19 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h9SKDHgF051183; Tue, 28 Oct 2003 12:13:17 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Oct 2003 12:13:17 -0800 From: "David O'Brien" To: Adriaan de Groot Message-ID: <20031028201317.GD50559@dragon.nuxi.com> References: <200310272055.54288.adridg@cs.kun.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200310272055.54288.adridg@cs.kun.nl> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.1-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: bootstrapping 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, 28 Oct 2003 20:13:27 -0000 On Mon, Oct 27, 2003 at 08:55:54PM +0100, Adriaan de Groot wrote: > gather there's no really working cvsup, and David's snapshot build from way > back is (a) from wayback (b) unstable under load. I'll start a new snapshot build now. Can you wait 2 days? > I've got several running systems, both -STABLE and -CURRENT, with cvsupped > /usr/src's. The /usr/src's are NFS exported, and I've got a spare cheap-ass > NIC (yes, an RTL 8029). Supposing I boot a 4-STABLE drive with rl(4) in > place in an amd64 box - what do I need to do to get it up to speed > (heck, let's make it a 5-CURRENT drive, since we've got the 4-to-5 > upgrade otherwise as well). That will work fine (32-bit FreeBSD). My FreeBSD/i386 5-CURRENT reference system is now an Athlon64, and is my fastest "i386" box now. From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 28 13:37:28 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 012DF16A4CE; Tue, 28 Oct 2003 13:37:28 -0800 (PST) Received: from smtp-relay1.barrysworld.com (ns1.barrysworld.com [213.221.172.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1D8E43F75; Tue, 28 Oct 2003 13:37:26 -0800 (PST) (envelope-from killing@barrysworld.com) Received: from [213.221.181.50] (helo=barrysworld.com) by smtp-relay1.barrysworld.com with esmtp (Exim 4.24) id 1AEbW8-00057e-IB; Tue, 28 Oct 2003 21:36:44 +0000 Received: from vader [212.135.219.179] by barrysworld.com with ESMTP (SMTPD32-7.15) id A17A49800AC; Tue, 28 Oct 2003 21:36:58 +0000 Message-ID: <002a01c39d9b$8fb94000$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: , , "Robert Cousins" References: <20031028194605.GA50559@dragon.nuxi.com> Date: Tue, 28 Oct 2003 21:36:34 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-amd64@freebsd.org Subject: Re: Timing of Amd64 & FreeBSD 5.2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Steven Hartland List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2003 21:37:28 -0000 I must say I'd like to see linux AMD64 support make the grade before 5.2 so we can make use of the hlds_l amd64 compile :) ----- Original Message ----- From: "David O'Brien" > The largest things missing that a user may notice are SMP support (don't > matter to Athlon64 users), Linux AMD64 compatability (not too many > commercial Linux AMD64 apps at this time), complete FreeBSD/i386 > compatability, complete Linux i386 compatability. From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 29 23:14:27 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 46CFE16A4CE; Wed, 29 Oct 2003 23:14:27 -0800 (PST) Received: from everest.sethbc.org (r107647.resnet.cornell.edu [128.253.186.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8565D43FDF; Wed, 29 Oct 2003 23:14:26 -0800 (PST) (envelope-from sethbc@sethbc.org) Received: from cwm (r102798.resnet.cornell.edu [128.253.186.154]) by everest.sethbc.org (Postfix) with ESMTP id AE6052843B; Thu, 30 Oct 2003 02:14:25 -0500 (EST) From: "Seth Chandler" To: "'Steven Hartland'" , , , "'Robert Cousins'" Date: Thu, 30 Oct 2003 02:14:30 -0500 Message-ID: <000c01c39eb5$76513ad0$9abafd80@cwm> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <002a01c39d9b$8fb94000$b3db87d4@multiplay.co.uk> Subject: RE: Timing of Amd64 & FreeBSD 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: Thu, 30 Oct 2003 07:14:27 -0000 Is there some sort of checklist for amd64 making Tier 1 for 5.2-RELEASE? I was under the impression that amd64 already met the requirements for a tier 1 platform. seth -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of Steven Hartland Sent: Tuesday, October 28, 2003 4:37 PM To: obrien@freebsd.org; freebsd-amd64@freebsd.org; Robert Cousins Cc: freebsd-amd64@freebsd.org Subject: Re: Timing of Amd64 & FreeBSD 5.2 I must say I'd like to see linux AMD64 support make the grade before 5.2 so we can make use of the hlds_l amd64 compile :) ----- Original Message ----- From: "David O'Brien" > The largest things missing that a user may notice are SMP support (don't > matter to Athlon64 users), Linux AMD64 compatability (not too many > commercial Linux AMD64 apps at this time), complete FreeBSD/i386 > compatability, complete Linux i386 compatability. _______________________________________________ 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 Fri Oct 31 13:00:51 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 49AFE16A4D0 for ; Fri, 31 Oct 2003 13:00:51 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0583D43FAF for ; Fri, 31 Oct 2003 13:00:50 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost.ebn.kun.nl by pandora.cs.kun.nl via odin.cs.kun.nl [131.174.33.33] with ESMTP for id h9VL0R6G026312 (8.12.10/3.58); Fri, 31 Oct 2003 22:00:40 +0100 (MET) From: Adriaan de Groot To: amd64@freebsd.org Date: Fri, 31 Oct 2003 22:00:06 +0100 User-Agent: KMail/1.5.2 References: <200310272055.54288.adridg@cs.kun.nl> <20031028201317.GD50559@dragon.nuxi.com> In-Reply-To: <20031028201317.GD50559@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310312200.06633.adridg@cs.kun.nl> Subject: Re: bootstrapping 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, 31 Oct 2003 21:00:51 -0000 On Tuesday 28 October 2003 21:13, David O'Brien wrote: > On Mon, Oct 27, 2003 at 08:55:54PM +0100, Adriaan de Groot wrote: > > gather there's no really working cvsup, and David's snapshot build from > > way back is (a) from wayback (b) unstable under load. > > I'll start a new snapshot build now. Can you wait 2 days? I am, like, patience incarnate. > That will work fine (32-bit FreeBSD). My FreeBSD/i386 5-CURRENT > reference system is now an Athlon64, and is my fastest "i386" box now. So I got a new board, discovered that the Zalman cooler didn't fit right and improvised with motherboard standoffs, and now it's time for me to start asking n00b questions again. My cvsup of -CURRENT is fetching src/sys/i4b now, it'll be a while before I'm ready to compile a kernel ... In the meantime I'm still using David's previous snapshot build, with a 3Com 3C905 for networking and an old 2G PATA HDD to start from. I'm wondering about the promise fasttrack 378 RAID controller. I picked up one (1) SATA drive, and stuck it to the promise connectors. While the controller sees the drive on bootup, once the kernel boots (and reports ata[234] on atapci1) there's no devices there to speak of. Is this a normal phenomenon? A driver issue? Have I been a moron to think that a RAID controller can also act like a plain ata bus? Well, it'll all come out in the wash, once the kernel builds. Only 16M of cvsup to go .. From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 31 13:30:56 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 378BE16A4CF for ; Fri, 31 Oct 2003 13:30:56 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1FEF43F85 for ; Fri, 31 Oct 2003 13:30:54 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost.ebn.kun.nl by pandora.cs.kun.nl via odin.cs.kun.nl [131.174.33.33] with ESMTP for id h9VLUW6G029901 (8.12.10/3.58); Fri, 31 Oct 2003 22:30:45 +0100 (MET) From: Adriaan de Groot To: amd64@freebsd.org Date: Fri, 31 Oct 2003 22:30:09 +0100 User-Agent: KMail/1.5.2 References: <200310272055.54288.adridg@cs.kun.nl> <20031028201317.GD50559@dragon.nuxi.com> <200310312200.06633.adridg@cs.kun.nl> In-Reply-To: <200310312200.06633.adridg@cs.kun.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310312230.09619.adridg@cs.kun.nl> Subject: Re: bootstrapping 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, 31 Oct 2003 21:30:56 -0000 On Friday 31 October 2003 22:00, Adriaan de Groot wrote: > I'm wondering about the promise fasttrack 378 RAID controller. I picked up > one (1) SATA drive, and stuck it to the promise connectors. While the > controller sees the drive on bootup, once the kernel boots (and reports > ata[234] on atapci1) there's no devices there to speak of. Is this a normal > phenomenon? A driver issue? Have I been a moron to think that a RAID > controller can also act like a plain ata bus? This was just me being foolish. The new slimmer cable doesn't obviate the need for a 4-pin molex power connector. Doing newfs on the drive, though, gets me a GPF panic, Stopped at getdirtybuf+0x2d: decl %eax. Guess it's NFS mount then for the sources. From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 31 14:17: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 4724416A4CE for ; Fri, 31 Oct 2003 14:17:37 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEE0743FA3 for ; Fri, 31 Oct 2003 14:17:36 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id B0B7D2A8FB; Fri, 31 Oct 2003 14:17:36 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Adriaan de Groot In-Reply-To: <200310312200.06633.adridg@cs.kun.nl> Date: Fri, 31 Oct 2003 14:17:36 -0800 From: Peter Wemm Message-Id: <20031031221736.B0B7D2A8FB@canning.wemm.org> cc: amd64@freebsd.org Subject: Re: bootstrapping 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, 31 Oct 2003 22:17:37 -0000 Adriaan de Groot wrote: > I'm wondering about the promise fasttrack 378 RAID controller. I picked up on e > (1) SATA drive, and stuck it to the promise connectors. While the controller > sees the drive on bootup, once the kernel boots (and reports ata[234] on > atapci1) there's no devices there to speak of. Is this a normal phenomenon? A > driver issue? Have I been a moron to think that a RAID controller can also > act like a plain ata bus? There is a seperate ataraid driver in FreeBSD.. # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA raid devices device atapicd # ATAPI CDROM drives The 378 looks like this when its in raid mode: atapci0: port 0xdc00-0xdc7f,0xec00-0xec0f,0x9000-0x903f mem 0xcf800000-0xcf81ffff,0xcf900000-0xcf900fff irq 5 at device 8.0 on pci0 ata2: at 0xcf900000 on atapci0 ata3: at 0xcf900000 on atapci0 ata4: at 0xcf900000 on atapci0 ad0: 117246MB [238216/16/63] at ata2-master UDMA133 ad1: 117246MB [238216/16/63] at ata3-master UDMA133 ar0: 117246MB [14946/255/63] status: READY subdisks: disk0 READY on ad0 at ata2-master disk1 READY on ad1 at ata3-master Mounting root from ufs:/dev/ar0s1a Yes, its just a normal IDE controller. If my memory serves me correctly (ie: I'm not going to reboot to find out :-), there is a bios setting so you can set the promise controller into 'RAID' or 'IDE' mode. It only affects booting. Once you've booted, its a software raid, so the OS has to know how to read the metadata and pretend its a raid again. 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 Fri Oct 31 14:58: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 B22A616A4CE for ; Fri, 31 Oct 2003 14:58:08 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93BCF43F93 for ; Fri, 31 Oct 2003 14:58:07 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost.ebn.kun.nl by pandora.cs.kun.nl via odin.cs.kun.nl [131.174.33.33] with ESMTP for id h9VMw26G011723 (8.12.10/3.58); Fri, 31 Oct 2003 23:58:03 +0100 (MET) From: Adriaan de Groot To: amd64@freebsd.org Date: Fri, 31 Oct 2003 23:57:42 +0100 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200310312355.30349.adridg@cs.kun.nl> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: fyi: bootstrapped 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, 31 Oct 2003 22:58:08 -0000 Jaja, lots of noise on the list because of me. Here's my dmesg from a freshly booted machine (Asus K8V Deluxe), with 5-CURRENT cvsupped this evening, with the GENERIC config edited only to change the machine name. There's a couple of things that worry me in the dmesg output, which I've marked with ### in the output. ACPI debug layer 0x0 debug level 0x0 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sat Nov 1 05:56:17 GMT 2003 root@beans.ebn.kun.nl:/usr/src/sys/amd64/compile/BEANS Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8090f000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.57-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500000 real memory = 1072889856 (1023 MB) avail memory = 1008889856 (962 MB) Pentium Pro MTRR support enabled acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_FOUND ### This was around a while ago already. it was worrying then, said, um .. pci1: on pcib1 atapci0: port 0xbc00-0xbc7f,0xcc00-0xcc0f,0xdc00-0xdc3f mem 0xcf800000-0xcf81ffff,0xcf900000-0xcf900fff irq 11 at device 8.0 on pci0 atapci0: [MPSAFE] ata2: at 0xcf900000 on atapci0 ata2: [MPSAFE] ata3: at 0xcf900000 on atapci0 ata3: [MPSAFE] ata4: at 0xcf900000 on atapci0 ata4: [MPSAFE] skc0: <3Com 3C940 Gigabit Ethernet> port 0xec00-0xecff mem 0xcfa00000-0xcfa03fff irq 10 at device 10.0 on pci0 skc0: 3Com Gigabit LOM (3C940) sk0: on skc0 sk0: Ethernet address: 00:0c:6e:b3:3f:38 malloc() of "512" with the following non-sleepable locks held: exclusive sleep mutex skc0 (network driver) r = 0 (0xffffff0000bcba70) locked @ pci/if_sk.c:1292 miibus0: on sk0 e1000phy0: on miibus0 lock order reversal 1st 0xffffff0000bcba70 skc0 (network driver) @ pci/if_sk.c:651 2nd 0xffffffff8077d540 kernel environment (kernel environment) @ kern/kern_environment.c:288 Stack backtrace: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto ### Looks like spinlocks with a potential problem xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xb000-0xb07f mem 0xcfc00000-0xcfc0007f irq 10 at device 12.0 on pci0 xl0: Ethernet address: 00:01:02:b3:de:a6 miibus1: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 13.0 (no driver attached) atapci1: port 0xd000-0xd0ff,0xd400-0xd40f,0xd800-0xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 10 at device 15.0 on pci0 atapci1: [MPSAFE] ### Impressive. I had it disabled in the BIOS. ata5: at 0xe800 on atapci1 ata5: [MPSAFE] ata6: at 0xe000 on atapci1 ata6: [MPSAFE] atapci2: port 0xfc00-0xfc0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci2 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci2 ata1: [MPSAFE] uhci0: port 0xb400-0xb41f irq 5 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 uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 ### All my ports do this, even the ones with devices attached that ### subsequently function just fine (like the keyboard and mouse). ### Also, I have the orts set to USB 2.0, I'd expect that to be reported, no? ums0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 ukbd0: Logitech Logitech USB Keyboard, rev 1.10/15.00, addr 3, iclass 3/1 kbd0 at ukbd0 uhci1: port 0xb800-0xb81f irq 5 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 uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 uhci2: port 0xc000-0xc01f irq 10 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 uhub2: port error, restarting port 1 uhub2: port error, giving up port 1 uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 uhci3: port 0xc400-0xc41f irq 10 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 uhub3: port error, restarting port 1 uhub3: port error, giving up port 1 uhub3: port error, restarting port 2 uhub3: port error, giving up port 2 pci0: at device 16.4 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 pcm0: port 0xc800-0xc8ff irq 11 at device 17.5 on pci0 pcm0: fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold 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 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x2f8-0x2ff irq 3 on acpi0 sio0: type 16550A sio1: configured irq 4 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 npx0: on motherboard npx0: INT 16 interface orm0: