From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 17 08:07:18 2005 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 156C016A4CE for ; Sun, 17 Apr 2005 08:07:18 +0000 (GMT) Received: from mvs3.plala.or.jp (c158131.vh.plala.or.jp [210.150.158.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC71A43D31 for ; Sun, 17 Apr 2005 08:07:16 +0000 (GMT) (envelope-from eosny@ruby.plala.or.jp) Received: from [127.0.0.1] ([203.135.228.60]) by mvs3.plala.or.jp with ESMTP id <20050417080715.KKGR17326.mvs3.plala.or.jp@[127.0.0.1]> for ; Sun, 17 Apr 2005 17:07:15 +0900 Date: Sun, 17 Apr 2005 17:07:13 +0900 From: Norio Yamaguchi To: freebsd-amd64@FreeBSD.org X-Mailer-Plugin: BkASPil for Becky!2 Ver.2.043 Message-Id: <20050417150227.A651.EOSNY@ruby.plala.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.20.07 [ja] 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: Sun, 17 Apr 2005 08:07:18 -0000 ************************************************* $B;38}K!@8!J(BNorio Yamaguchi/EOS$B!K(B Email:eosny@ruby.plala.or.jp ************************************************* From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 17 12:58:07 2005 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 CE3AB16A4CE for ; Sun, 17 Apr 2005 12:58:07 +0000 (GMT) Received: from mvs5.plala.or.jp (c158133.vh.plala.or.jp [210.150.158.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9587443D49 for ; Sun, 17 Apr 2005 12:58:06 +0000 (GMT) (envelope-from eosny@ruby.plala.or.jp) Received: from [127.0.0.1] ([218.219.126.72]) by mvs5.plala.or.jp with ESMTP id <20050417125805.FEEP6132.mvs5.plala.or.jp@[127.0.0.1]> for ; Sun, 17 Apr 2005 21:58:05 +0900 Date: Sun, 17 Apr 2005 21:58:04 +0900 From: Norio Yamaguchi To: freebsd-amd64@freebsd.org X-Mailer-Plugin: BkASPil for Becky!2 Ver.2.043 Message-Id: <20050417215540.1BCE.EOSNY@ruby.plala.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.20.07 [ja] 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: Sun, 17 Apr 2005 12:58:07 -0000 ************************************************* $B;38}K!@8!J(BNorio Yamaguchi/EOS$B!K(B Email:eosny@ruby.plala.or.jp ************************************************* From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 17 16:01:09 2005 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 E84A816A4CE for ; Sun, 17 Apr 2005 16:01:09 +0000 (GMT) Received: from panix.homeunix.org (c8d56a0c.cps.virtua.com.br [200.213.106.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31B9343D58 for ; Sun, 17 Apr 2005 16:01:09 +0000 (GMT) (envelope-from pan@panix.homeunix.org) Received: from localhost (localhost [127.0.0.1]) by panix.homeunix.org (Postfix) with ESMTP id 283293F420 for ; Sun, 17 Apr 2005 13:00:59 -0300 (BRT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by panix.homeunix.org (Postfix) with ESMTP id 295D73F41C for ; Sun, 17 Apr 2005 13:00:55 -0300 (BRT) Message-ID: <42628836.8040406@panix.homeunix.org> Date: Sun, 17 Apr 2005 13:00:54 -0300 From: "Carlos F. A. Paniago" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050416 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 X-Virus-Scanned: by amavisd 0.1 Subject: Re: Openoffice2 success on Amd64 linux emu 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, 17 Apr 2005 16:01:10 -0000 I had the same problem and solved it changing the permission of the /compat/linux/tmp to 0777 then normal user worked. This directory is with a strange permissioin and should be fixed in the ports. Paniago -- Nome: Carlos Fernando Assis Paniago Email: pan@panix.homeunix.org e pan@cnpm.embrapa.br Web: http://panix.homeunix.org/ e http://www.cnpm.embrapa.br/ -- From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 17 18:56:34 2005 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 B69BE16A4D6 for ; Sun, 17 Apr 2005 18:56:34 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id B831C43D46 for ; Sun, 17 Apr 2005 18:56:33 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 4132478C62 for ; Sun, 17 Apr 2005 14:57:58 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53514-10 for ; Sun, 17 Apr 2005 14:57:53 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id F2C7878C35 for ; Sun, 17 Apr 2005 14:57:52 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 92E3533C60; Sun, 17 Apr 2005 14:57:26 -0400 (EDT) Date: Sun, 17 Apr 2005 14:57:26 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050417185726.GB51599@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <42628836.8040406@panix.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42628836.8040406@panix.homeunix.org> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: Openoffice2 success on Amd64 linux emu 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, 17 Apr 2005 18:56:34 -0000 Thus spake Carlos F. A. Paniago (pan@panix.homeunix.org) [17/04/05 12:02]: : I had the same problem and solved it changing the permission of the : /compat/linux/tmp to 0777 then normal user worked. This directory is : with a strange permissioin and should be fixed in the ports. It /should/ be 1777, not 0777, for security reasons. From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 17 19:05:09 2005 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 64F6516A4CE; Sun, 17 Apr 2005 19:05:09 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id A003143D4C; Sun, 17 Apr 2005 19:05:08 +0000 (GMT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3HJ56G2039525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 17 Apr 2005 15:05:07 -0400 (EDT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com (smmsp@localhost.video-collage.com [127.0.0.1])j3HJ50jS096701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Apr 2005 15:05:01 -0400 (EDT) (envelope-from mi@corbulon.video-collage.com) Received: (from root@localhost)j3HJ50jK096698; Sun, 17 Apr 2005 15:05:00 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200504171905.j3HJ50jK096698@corbulon.video-collage.com> To: bsdfreak@gmail.com Date: Sun, 17 Apr 2005 15:05:00 -0400 (EDT) In-Reply-To: X-Mailer: ELM [version 2.5 PL7] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: Q cc: freebsd-amd64@freebsd.org cc: Mikhail Teterin cc: net@freebsd.org Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2005 19:05:09 -0000 > > > > > Try using the tarball from here http://www.onthenet.com.au/~q/nvnet > > > > Yes! That -- combined with the > > > > ftp://download1.nvidia.com/XFree86/nforce/1.0-0301/ -- worked! > > .. > > > > Could update the net/nvnet port? When 5.4 gets released, I > > > > imagine plenty of people to be in my position... > > > > > > When 5.4 gets released, we likely will have if_nve(4) MFC'ed already. > > > > Nope. It will be a 5.5 feature. And for that it needs to be merged into 5.x before 5.5-PRERELEASE -- hence into 5.4-STABLE, or "after 5.4 gets released" :-) > The nvnet port works fine for my onboard Ethernet on my Gigabyte > K8NNXP w/Athlon 3200+ CPU. The latest version from Q's site works (!), but seems limited to 100baseTX full-duplex. Even at that nominal speed, the actual data transfers seem limited to 2-3 megabytes/s with occasional latency-spikes :-( I'll try to back-port if_nve manually and see, what happens. -mi From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 06:24:47 2005 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 2207D16A4CE for ; Mon, 18 Apr 2005 06:24:47 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B7C943D2D for ; Mon, 18 Apr 2005 06:24:46 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3I6Of8u085690; Sun, 17 Apr 2005 23:24:41 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3I6OdKk085687; Sun, 17 Apr 2005 23:24:39 -0700 (PDT) (envelope-from obrien) Date: Sun, 17 Apr 2005 23:24:39 -0700 From: "David O'Brien" To: Florent Thoumie Message-ID: <20050418062438.GA85579@dragon.NUXI.org> References: <20050413210855.GA15088@bitsurf.net> <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1113603823.91832.7.camel@cream.xbsd.org> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 06:24:47 -0000 On Sat, Apr 16, 2005 at 12:23:43AM +0200, Florent Thoumie wrote: > Le Friday 15 April 2005 à 14:16 -0700, David O'Brien a écrit : > > On Thu, Apr 14, 2005 at 06:09:04PM -0700, Astrodog wrote: > > > On 4/14/05, David O'Brien wrote: > > > > On Thu, Apr 14, 2005 at 03:14:45PM +0200, Dag-Erling Smrgrav wrote: > > > > > Jung-uk Kim writes: > > > > > > Stay away from nForce chipsets. > > > > > > > > > > Please stop spreading this little piece of disinformation. nForce3 > > > > > motherboards such as the Asus SK8N should work fine. > > > > > > > > DES stop spreading FUD. > > > > > > I think the point to be made here, is that there are SOME specific > > > nforce based boards, that work great, > > > > There are? Which?? The SK8N that DES will respond to my email is > > actually high on the "bizzare issues" list. > > I have an Asus A8N-SLI (nforce4) Motherboard based box running > 5-STABLE for some time now. Issues are : > x ACPI (quite common), I don't have any ACPI issues on any AMD or VIA based chipsets. I'm not saying there isn't at least one VIA-based mobo with bad ACPI issues, but practially every nVidia based motherboard has bad ACPI issues. In fact, I personally don't know of a single nVidia motherboard that doesn't have bad ACPI issues. Do you? > As Dag-Erling said, it'll be good if you were not giving false > information and better (my opinion), as re-amd64@ if you were > trying to get better relationship with Nvidia. Read the archives -- MANY, MANY people thank me for my suggestions. You don't have to follow them. And obviously didn't. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 06:30:13 2005 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 97F1F16A4CE for ; Mon, 18 Apr 2005 06:30:13 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41D1743D41 for ; Mon, 18 Apr 2005 06:30:13 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3I6UB4A085804; Sun, 17 Apr 2005 23:30:12 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3I6U9bq085803; Sun, 17 Apr 2005 23:30:09 -0700 (PDT) (envelope-from obrien) Date: Sun, 17 Apr 2005 23:30:09 -0700 From: "David O'Brien" To: Florent Thoumie Message-ID: <20050418063009.GB85579@dragon.NUXI.org> References: <20050413210855.GA15088@bitsurf.net> <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <20050416114331.GA17943@isis.sigpipe.cz> <1113652517.36786.18.camel@cream.xbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1113652517.36786.18.camel@cream.xbsd.org> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: Roman Neuhauser cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 06:30:13 -0000 On Sat, Apr 16, 2005 at 01:55:17PM +0200, Florent Thoumie wrote: > That makes the box usuable (remove "totally" if it can make you > happier). What is not working for you with your motherboard would be a big issue to many people I know. > My point is that a page with FreeBSD/amd64 status on different > MBs would be much more useful than "Plz stay away from nvidia, > this is crap". Ok, where's the patch to the www.freebsd.org/platforms/amd64.sgml?? People VERY often as me for recomendations. I'm not a walking catalog for every AMD64 motherboard in existance -- I can only speak to the ones I have used and others I know personally use. I know of not a single AMD or VIA chipset based motherboard that has issues. I know of not a single nVidia based motherboard that doesn't have issues. I can only offer the knowledge *I* have when I'm asked. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 07:14:33 2005 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 EE02816A4CE for ; Mon, 18 Apr 2005 07:14:33 +0000 (GMT) Received: from pop-a065c10.pas.sa.earthlink.net (pop-a065c10.pas.sa.earthlink.net [207.217.121.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id A213043D5E for ; Mon, 18 Apr 2005 07:14:33 +0000 (GMT) (envelope-from kwsn@earthlink.net) Received: from dialup-4.240.105.112.dial1.phoenix1.level3.net ([4.240.105.112] helo=jonnyv.kwsn.lan) by pop-a065c10.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DNQSm-00034B-00; Mon, 18 Apr 2005 00:14:33 -0700 From: Jon Kuster To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Mon, 18 Apr 2005 00:14:29 -0700 Message-Id: <1113808469.2757.14.camel@jonnyv.kwsn.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: toby.murray@gmail.com Subject: [Fwd: Re: java crashing when load average is high] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kwsn@earthlink.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 07:14:34 -0000 Forwarding this to -amd64 for a slightly wider audience since I'm not sure if it's a java issue, or an amd64 issue. We've since upgraded to -stable. Thanks, Jon -------- Forwarded Message -------- From: Jon Kuster Reply-To: kwsn@earthlink.net To: Toby Murray Cc: freebsd-java@freebsd.org Subject: Re: java crashing when load average is high Date: Sun, 17 Apr 2005 17:36:30 -0700 On Sun, 2005-04-17 at 14:06 -0500, Toby Murray wrote: > Hi, > > I am working on getting a new server online. It is a Dell Poweredge > with dual HT Xeons and 1GB of RAM. We are running FreeBSD 5.4-RC1 and > java 1.4.2_08. Since I'm also helping Toby get this server online, I should note that we're running the amd64 version of RC1 and the linux-sun-jdk14. FreeBSD ni 5.4-RC1 FreeBSD 5.4-RC1 #0: Thu Apr 14 11:34:58 EDT 2005 ruessda@ni:/usr/obj/usr/src/sys/NISMP amd64 > java version "1.4.2_08" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03) > Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode) > > I have a java program that reads XML files over an HTTP stream and > inserts data from them into a mysql database. After getting java up > and running everything appeared to be working normally at first and > the program ran fine. But then I tried running it while something > else was compiling and the load average was up around 5 or 6. > Suddenly the behavior of the JVM became extremely erratic. > > Sometimes the whole JVM dumps with a signal 11 and leaves the following in dmsg: > kernel trap 12 with interrupts disabled > Other times the program throws random exceptions. I have seen 5 or 6 > different exceptions being thrown at seemingly random places in the > code while parsing the same data. > > A third behavior is for java to go into what appears to be an infinite > loop somewhere. Usually when my program runs, there is one java > thread and one mysql process that each take up ~70% of one CPU. When > things start looping, 2 java processes start sucking up as much CPU as > they can and mysql drops to nothing. This continues until I pull out > the kill -9. > > So to summarize it all: > java works fine if it is the only thing running > If the box is already under load, java malfunctions in one of 3 ways: > Signal 11, random Exception thrown or it starts looping without > getting anything done. > > Any clues? I see several other threads on the list about signal 11 > problems but I didn't see anything about the problems being related to > load. Let me know if you need more info on something. > > Thanks, > Toby From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 07:30:31 2005 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 1D6B116A4CE; Mon, 18 Apr 2005 07:30:31 +0000 (GMT) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F73E43D2F; Mon, 18 Apr 2005 07:30:30 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 45AAD11A4A; Mon, 18 Apr 2005 09:35:55 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41686-09; Mon, 18 Apr 2005 09:35:43 +0200 (CEST) Received: from [192.168.20.107] (ALagny-109-1-6-74.w81-50.abo.wanadoo.fr [81.50.23.74]) by smtp.xbsd.org (Postfix) with ESMTP id DE08C11925; Mon, 18 Apr 2005 09:35:42 +0200 (CEST) Message-ID: <42636203.6020007@xbsd.org> Date: Mon, 18 Apr 2005 09:30:11 +0200 From: Florent Thoumie User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: fr, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050413210855.GA15088@bitsurf.net> <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <20050418062438.GA85579@dragon.NUXI.org> In-Reply-To: <20050418062438.GA85579@dragon.NUXI.org> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at xbsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 18 Apr 2005 07:30:31 -0000 David O'Brien a écrit : > On Sat, Apr 16, 2005 at 12:23:43AM +0200, Florent Thoumie wrote: > >>Le Friday 15 April 2005 � 14:16 -0700, David O'Brien a �crit : >> >>>On Thu, Apr 14, 2005 at 06:09:04PM -0700, Astrodog wrote: >>> >>>>On 4/14/05, David O'Brien wrote: >>>> >>>>>On Thu, Apr 14, 2005 at 03:14:45PM +0200, Dag-Erling Smrgrav wrote: >>>>> >>>>>>Jung-uk Kim writes: >>>>>> >>>>>>>Stay away from nForce chipsets. >>>>>> >>>>>>Please stop spreading this little piece of disinformation. nForce3 >>>>>>motherboards such as the Asus SK8N should work fine. >>>>> >>>>>DES stop spreading FUD. >>>> >>>>I think the point to be made here, is that there are SOME specific >>>>nforce based boards, that work great, >>> >>>There are? Which?? The SK8N that DES will respond to my email is >>>actually high on the "bizzare issues" list. >> >> I have an Asus A8N-SLI (nforce4) Motherboard based box running >> 5-STABLE for some time now. Issues are : >> x ACPI (quite common), > > > I don't have any ACPI issues on any AMD or VIA based chipsets. > I'm not saying there isn't at least one VIA-based mobo with bad ACPI > issues, but practially every nVidia based motherboard has bad ACPI > issues. In fact, I personally don't know of a single nVidia motherboard > that doesn't have bad ACPI issues. Do you? I only used GENERIC kernel which has NO_MIXED_MODE enabled. I'm not really into ACPI/APIC, but it works now with this line commented. >> As Dag-Erling said, it'll be good if you were not giving false >> information and better (my opinion), as re-amd64@ if you were >> trying to get better relationship with Nvidia. > > > Read the archives -- MANY, MANY people thank me for my suggestions. > You don't have to follow them. And obviously didn't. I'm not blaming you for the suggestions you give, but for the way you give them. Note: About the patch to amd64.sgml, I'll contact some doc committers and try to submit you something before I leave for vacation. I guess you'll be pleased to ask people here for feedback about their mobos. -- Florent Thoumie flz@xbsd.org From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 11:01:57 2005 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 2BB6916A4CE for ; Mon, 18 Apr 2005 11:01:57 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B0743D45 for ; Mon, 18 Apr 2005 11:01:56 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3IB1u2T093272 for ; Mon, 18 Apr 2005 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3IB1ug0093267 for freebsd-amd64@freebsd.org; Mon, 18 Apr 2005 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 18 Apr 2005 11:01:56 GMT Message-Id: <200504181101.j3IB1ug0093267@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, 18 Apr 2005 11:01:57 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o 22 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/13] ports/75015 amd64 cvsup on amd64 with runsocks (socks5) cor o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 o [2005/02/13] amd64/77470 amd64 Using of cyrillic filenames conversion le o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build 11 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 17:20:41 2005 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 054EF16A4CE for ; Mon, 18 Apr 2005 17:20:41 +0000 (GMT) Received: from pop-a065c05.pas.sa.earthlink.net (pop-a065c05.pas.sa.earthlink.net [207.217.121.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92E9043D4C for ; Mon, 18 Apr 2005 17:20:40 +0000 (GMT) (envelope-from kwsn@earthlink.net) Received: from dialup-4.240.21.43.dial1.phoenix1.level3.net ([4.240.21.43] helo=jonnyv.kwsn.lan) by pop-a065c05.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DNZvI-0006XJ-00; Mon, 18 Apr 2005 10:20:37 -0700 From: Jon Kuster To: "Ernst W. Winter" In-Reply-To: <20050418130328.A1523@ns3.bsn.com> References: <1113808469.2757.14.camel@jonnyv.kwsn.lan> <20050418130328.A1523@ns3.bsn.com> Content-Type: text/plain Date: Mon, 18 Apr 2005 10:20:34 -0700 Message-Id: <1113844834.2757.22.camel@jonnyv.kwsn.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: toby.murray@gmail.com cc: freebsd-amd64@freebsd.org Subject: Re: [Fwd: Re: java crashing when load average is high] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kwsn@earthlink.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 17:20:41 -0000 On Mon, 2005-04-18 at 13:03 +0200, Ernst W. Winter wrote: > On Mon, 18 Apr 2005, Jon Kuster wrote: > > > Forwarding this to -amd64 for a slightly wider audience since I'm > > not sure if it's a java issue, or an amd64 issue. We've since > > upgraded to -stable. > > > I will try to give some explanation to the text below, from what I > have a experience with something similar. > > > Thanks, > > Jon > > > You're welcome > > Ernst > > > -------- Forwarded Message -------- > > From: Jon Kuster > > Reply-To: kwsn@earthlink.net > > To: Toby Murray > > Cc: freebsd-java@freebsd.org > > Subject: Re: java crashing when load average is high > > Date: Sun, 17 Apr 2005 17:36:30 -0700 > > > > On Sun, 2005-04-17 at 14:06 -0500, Toby Murray wrote: > > > Hi, > > > > > > I am working on getting a new server online. It is a Dell > > > Poweredge with dual HT Xeons and 1GB of RAM. We are running > > > FreeBSD 5.4-RC1 and java 1.4.2_08. > > > > Since I'm also helping Toby get this server online, I should note > > that we're running the amd64 version of RC1 and the > > linux-sun-jdk14. > > > You can also use java 1.5 as it compiles and instlls as well works on > amd64. I have done a "make isntall clean" on 3 machiens so far, There > are some small hitches but you can find it in the newsgroup or mail > me directly. I thought about that, but I haven't been able to get jdk15 to build yet. If you could send me the info about the hitches, that would be great. > > FreeBSD ni 5.4-RC1 FreeBSD 5.4-RC1 #0: Thu Apr 14 11:34:58 EDT 2005 > > ruessda@ni:/usr/obj/usr/src/sys/NISMP amd64 > > > > > java version "1.4.2_08" > > > Java(TM) 2 Runtime Environment, Standard Edition (build > > > 1.4.2_08-b03) Java HotSpot(TM) Client VM (build 1.4.2_08-b03, > > > mixed mode) > > > > > > I have a java program that reads XML files over an HTTP stream > > > and inserts data from them into a mysql database. After getting > > > java up and running everything appeared to be working normally at > > > first and the program ran fine. But then I tried running it > > > while something else was compiling and the load average was up > > > around 5 or 6. Suddenly the behavior of the JVM became extremely > > > erratic. > > > > well we had the same problem with a clients machien here, although it > was php and mysql, it froze the HD complete and no access possible > only switching of the machine. The machine remains responsive, it's just that java acts strangely. > > > > Sometimes the whole JVM dumps with a signal 11 and leaves the > > > following in dmsg: kernel trap 12 with interrupts disabled Other > > > times the program throws random exceptions. I have seen 5 or 6 > > > different exceptions being thrown at seemingly random places in > > > the code while parsing the same data. > > > > > > A third behavior is for java to go into what appears to be an > > > infinite loop somewhere. Usually when my program runs, there is > > > one java thread and one mysql process that each take up ~70% of > > > one CPU. When things start looping, 2 java processes start > > > sucking up as much CPU as they can and mysql drops to nothing. > > > This continues until I pull out the kill -9. > > > > This is what happen as i explained above. > > > > So to summarize it all: java works fine if it is the only thing > > > running If the box is already under load, java malfunctions in > > > one of 3 ways: Signal 11, random Exception thrown or it starts > > > looping without getting anything done. > > > > > > Any clues? I see several other threads on the list about signal > > > 11 problems but I didn't see anything about the problems being > > > related to load. Let me know if you need more info on something. > > > > well the only thing I could suggest is that you check out if it is a > "loop" to mysql, which has happen in our clients case that caused > that behaviour. Otherwise I have no explanation than that. If you eed > more information, then let me know and I send you the email of the > person that handled this. > > > > Thanks, > > > Toby > > Ernst > From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 19:55:22 2005 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 7B91316A4D3 for ; Mon, 18 Apr 2005 19:55:22 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AE1243D2F for ; Mon, 18 Apr 2005 19:55:21 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost01.amcc.com ([192.195.69.30]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IF5RC800.MH3 for ; Mon, 18 Apr 2005 12:55:20 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost01.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005041812552501798 for ; Mon, 18 Apr 2005 12:55:25 -0700 From: "Vinod Kashyap" To: freebsd-amd64@freebsd.org Date: Mon, 18 Apr 2005 12:54:10 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: Subject: New 3ware CLI and 3DM2 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: Mon, 18 Apr 2005 19:55:22 -0000 New FreeBSD amd64 versions of CLI and 3DM2, the management tools for 3ware's 7xxx/8xxx and 9xxx controllers are now available here: http://www.3ware.com/support/downloadnew.asp. These correspond to the recent 9.2 release from 3ware. Please note that these are not official releases, and have not gone through exhaustive testing. However, they are expected to work satisfactorily. Please report any problems to 3ware support. Thanks, Vinod. From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 20:03:43 2005 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 C9BDE16A4CE for ; Mon, 18 Apr 2005 20:03:43 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8284C43D49 for ; Mon, 18 Apr 2005 20:03:43 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 12BBFF7B1 for ; Mon, 18 Apr 2005 14:03:43 -0600 (MDT) Date: Mon, 18 Apr 2005 14:03:42 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050418140342.4c168b72.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: REcomomendations- New to AMD64 Platform 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, 18 Apr 2005 20:03:43 -0000 Hello: I'm a long time FreeBSD useer but with as of yet no experience with the ADM64 platform. Ready to take the plunge but want to make sure I've got my ducks in a row first. I'm considering using a Tyan based barebones, e.g. TA26 which uses their K8S Pro mainboard fleshed out with a couple 246's, ZCR, 2x1 GB DDR333, and some seagate u320 scsi drives. Deployment will be web/ application (maybe some Zope/ Plone/ JBoss/ Jetty/ Tomcat stuff)/ email and database server project. No real heavy lifting on the db side. I've searched through the archives and find that there have been various issues in the past with the Tyan K8SR and K8S Pro boards, but from what I gather they were not necessarily platform specific, e.g. broadcom driver and > 4gb of ram, and have apparently been resolved. These two boards seem to use the same components but in different layouts. Are there any outstanding issues with one vs. the other that I should be aware of? Any feedback/advice greaty appreciated. Thanks. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Mon Apr 18 20:58:09 2005 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 5682816A4CE for ; Mon, 18 Apr 2005 20:58:09 +0000 (GMT) Received: from pop-a065d19.pas.sa.earthlink.net (pop-a065d19.pas.sa.earthlink.net [207.217.121.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4FFE43D31 for ; Mon, 18 Apr 2005 20:58:08 +0000 (GMT) (envelope-from kwsn@earthlink.net) Received: from donald.psp.pas.earthlink.net ([207.217.78.222]) by pop-a065d19.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DNdJm-00078h-00; Mon, 18 Apr 2005 13:58:06 -0700 Message-ID: <29667534.1113857820670.JavaMail.root@donald.psp.pas.earthlink.net> Date: Mon, 18 Apr 2005 13:57:00 -0700 (GMT-07:00) From: Jon Kuster To: "Ernst W. Winter" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Zoo Mail 1.0 cc: toby.murray@gmail.com cc: freebsd-amd64@freebsd.org Subject: Re: [Fwd: Re: java crashing when load average is high] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jon Kuster List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 20:58:09 -0000 -----Original Message----- From: "Ernst W. Winter" Sent: Apr 18, 2005 10:51 AM To: Jon Kuster Subject: Re: [Fwd: Re: java crashing when load average is high] On Mon, 18 Apr 2005, Jon Kuster wrote: > > > > I am working on getting a new server online. It is a Dell > > > > Poweredge with dual HT Xeons and 1GB of RAM. We are running > > > > FreeBSD 5.4-RC1 and java 1.4.2_08. > > > > > > Since I'm also helping Toby get this server online, I should > > > note that we're running the amd64 version of RC1 and the > > > linux-sun-jdk14. > > > > > You can also use java 1.5 as it compiles and instlls as well > > works on amd64. I have done a "make isntall clean" on 3 machiens > > so far, There are some small hitches but you can find it in the > > newsgroup or mail me directly. > o.k, got it. > I thought about that, but I haven't been able to get jdk15 to build > yet. If you could send me the info about the hitches, that would > be great. > well I cvsuupped to the latest, which I wuold recoomend first and then compile the src and kernel and then install it all and then do the port. I have: -----------------------------Snip------------------------------------- Copyright (c) 1992-2005 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.4-STABLE #2: Thu Apr 7 07:30:15 CEST 2005 ewinter@lobo.homeunix.org:/usr/obj/usr/src/sys/lobo -----------------------------Snip------------------------------------- > > > FreeBSD ni 5.4-RC1 FreeBSD 5.4-RC1 #0: Thu Apr 14 11:34:58 EDT > > > 2005 ruessda@ni:/usr/obj/usr/src/sys/NISMP amd64 > > > > > > > I have a java program that reads XML files over an HTTP > > > > stream and inserts data from them into a mysql database. > > > > After getting java up and running everything appeared to be > > > > working normally at first and the program ran fine. But then > > > > I tried running it while something else was compiling and the > > > > load average was up around 5 or 6. Suddenly the behavior of > > > > the JVM became extremely erratic. > > > > > > well we had the same problem with a clients machien here, > > although it was php and mysql, it froze the HD complete and no > > access possible only switching of the machine. > > The machine remains responsive, it's just that java acts strangely. > Still it could be somehting else as that is what we found out about it, so have a look with top. Here the notes I saved: -----------------------------Snip------------------------------------- i had the same problem and solved it executing the last command which caused the error manually. Looks like the error comes because it's a very long command. Just put the command that comes between 'then' and 'fi' in a shell file and execute it manually in the directory work/j2sre/make/java/java (I'm not seating now in my amd64 FreeBSD computer but I think that was the directory). The compilation will go on without any problem if you resume it afterwards with a 'make build'. -- J.V. Jordan Try 'make build |& tee build.out' (if your shell is csh or tcsh) or 'make build 2>&1 | tee build.out' (if sh or bash). After the error comes, edit build.out and you will see the command causing it (takes about two pages). -----------------------------Snip------------------------------------- this was in the amd64 grouop a while ago. you will get also this message: -----------------------------Snip------------------------------------- lobo ewinter 504-->mm .notes/java_compile.txt you need to put this in /etc/fstab linprocfs /compat/linux/proc linprocfs rw 0 0 and then, as root, executing the commands: kldload linprocfs mount /compat/linux/proc -----------------------------Snip------------------------------------- you would have to fallowing in the kernel too: options COMPAT_LINUX32 # for Lunx with i386 ?? options LINPROCFS # for Linux 32bit binaries hoppe that this will be of any use to you. Let me know what will happen when you find out what it really is? Thanks Ernst That gets me farther into the build, but once I restart the build, I eventually end up with 2 javac processes eating as much cpu as they can and not getting anywhere (they ran for more than 10 minutes before I killed them). Once I kill them, 6 more javac's spring to the top of the process list in top. It's looking more and more like we'll have to either rewrite the app or move to a different OS :/ Got any other ideas? Thanks, Jon From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 02:16:30 2005 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 6258516A4CE for ; Tue, 19 Apr 2005 02:16:29 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF7FC43D53 for ; Tue, 19 Apr 2005 02:16:28 +0000 (GMT) (envelope-from rsh.lists@comcast.net) Received: from [192.168.1.11] (tardiss.hsd1.ma.comcast.net[66.30.82.93]) by comcast.net (rwcrmhc13) with ESMTP id <2005041902162801500o08k2e>; Tue, 19 Apr 2005 02:16:28 +0000 Message-ID: <426469F7.3000702@comcast.net> Date: Mon, 18 Apr 2005 22:16:23 -0400 From: Sean User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050330) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20050418140342.4c168b72.kgunders@teamcool.net> In-Reply-To: <20050418140342.4c168b72.kgunders@teamcool.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: REcomomendations- New to AMD64 Platform X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rsh.lists@comcast.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 02:16:30 -0000 Ken Gunderson wrote: > Hello: > > I'm a long time FreeBSD useer but with as of yet no experience with the > ADM64 platform. Ready to take the plunge but want to make sure I've > got my ducks in a row first. > > I'm considering using a Tyan based barebones, e.g. TA26 which uses > their K8S Pro mainboard fleshed out with a couple 246's, ZCR, 2x1 GB > DDR333, and some seagate u320 scsi drives. Deployment will be web/ > application (maybe some Zope/ Plone/ JBoss/ Jetty/ Tomcat stuff)/ email > and database server project. No real heavy lifting on the db side. > > I've searched through the archives and find that there have been > various issues in the past with the Tyan K8SR and K8S Pro boards, but > from what I gather they were not necessarily platform specific, e.g. > broadcom driver and > 4gb of ram, and have apparently been resolved. > These two boards seem to use the same components but in different > layouts. Are there any outstanding issues with one vs. the other that > I should be aware of? > > Any feedback/advice greaty appreciated. Thanks. > I am using a Tyan S2885ANRF motherboard and it has been running great for me. I was having initially problems and such but once I went up to current, it has been running great. Built this system back in December. sean@tardis$ uname -a FreeBSD tardis.mydomain.net 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Jan 28 19:02:44 EST 2005 sean@tardis.mydomain.net:/usr/obj/usr/src/sys/TARDISKERNEL amd64 From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 02:51:23 2005 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 4E86216A4CE for ; Tue, 19 Apr 2005 02:51:23 +0000 (GMT) Received: from web60002.mail.yahoo.com (web60002.mail.yahoo.com [216.109.116.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 9133943D41 for ; Tue, 19 Apr 2005 02:51:22 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 88870 invoked by uid 60001); 19 Apr 2005 02:51:22 -0000 Message-ID: <20050419025122.88868.qmail@web60002.mail.yahoo.com> Received: from [68.223.250.101] by web60002.mail.yahoo.com via HTTP; Mon, 18 Apr 2005 19:51:21 PDT Date: Mon, 18 Apr 2005 19:51:21 -0700 (PDT) From: Tom Shafron To: Ken Gunderson , freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: REcomomendations- New to AMD64 Platform 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, 19 Apr 2005 02:51:23 -0000 I'm running the K8S Pro (2882) with 4x512Mb, 2x246 opteron and it's running great. Been up for about 2 weeks straight as of today without any problems. --- Ken Gunderson wrote: > Hello: > > I'm a long time FreeBSD useer but with as of yet no > experience with the > ADM64 platform. Ready to take the plunge but want > to make sure I've > got my ducks in a row first. > > I'm considering using a Tyan based barebones, e.g. > TA26 which uses > their K8S Pro mainboard fleshed out with a couple > 246's, ZCR, 2x1 GB > DDR333, and some seagate u320 scsi drives. > Deployment will be web/ > application (maybe some Zope/ Plone/ JBoss/ Jetty/ > Tomcat stuff)/ email > and database server project. No real heavy lifting > on the db side. > > I've searched through the archives and find that > there have been > various issues in the past with the Tyan K8SR and > K8S Pro boards, but > from what I gather they were not necessarily > platform specific, e.g. > broadcom driver and > 4gb of ram, and have > apparently been resolved. > These two boards seem to use the same components but > in different > layouts. Are there any outstanding issues with one > vs. the other that > I should be aware of? > > Any feedback/advice greaty appreciated. Thanks. > > -- > Best regards, > > Ken Gunderson > GPG Key-- 9F5179FD > > "Freedom begins between the ears." -- Edward Abbey > > _______________________________________________ > 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" > __________________________________ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 07:56:43 2005 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 B41A616A4CE for ; Tue, 19 Apr 2005 07:56:43 +0000 (GMT) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32ABA43D1F for ; Tue, 19 Apr 2005 07:56:43 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 3736E11A77 for ; Tue, 19 Apr 2005 10:02:14 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88040-07 for ; Tue, 19 Apr 2005 10:02:07 +0200 (CEST) Received: from localhost.localdomain (ALagny-109-1-5-243.w81-50.abo.wanadoo.fr [81.50.6.243]) by smtp.xbsd.org (Postfix) with ESMTP id 7C098119F3 for ; Tue, 19 Apr 2005 10:02:06 +0200 (CEST) From: Florent Thoumie To: FreeBSD-amd64@FreeBSD.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Uwlh6YaxZUDOBu7d1sJK" Date: Tue, 19 Apr 2005 09:56:23 +0200 Message-Id: <1113897383.758.8.camel@innercity> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port X-Virus-Scanned: amavisd-new at xbsd.org Subject: Fwd: cvs commit: www/en/platforms Makefile www/en/platforms/amd64 Makefile motherboards.sgml 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, 19 Apr 2005 07:56:43 -0000 --=-Uwlh6YaxZUDOBu7d1sJK Content-Type: text/plain Content-Transfer-Encoding: quoted-printable pav 2005-04-18 21:12:00 UTC FreeBSD doc repository (ports committer) Modified files: en/platforms Makefile=20 Added files: en/platforms/amd64 Makefile motherboards.sgml=20 Log: New webpage on our website: The amd64 motherboards list. We want to colle= ct information about motherboards for an amd64 platform and how well FreeBSD is running on them. Please direct your submissions directly to this file, to pav or flz, or to www category in GNATS. I expect this page to grow quickly. =20 This mini-project was inspired by endless stream of posts on freebsd-amd6= 4 list asking for hardware suggestions. =20 Created by: flz, mostly Approved by: simon =20 Revision Changes Path 1.10 +3 -2 www/en/platforms/Makefile 1.1 +12 -0 www/en/platforms/amd64/Makefile (new) 1.1 +66 -0 www/en/platforms/amd64/motherboards.sgml (new) --=20 Florent Thoumie flz@xbsd.org --=-Uwlh6YaxZUDOBu7d1sJK Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCZLmnMxEkbVFH3PQRAtMyAJwMl8+gBskz9BuS1liO8ZG++TcZKACfcle3 O4yBEtcFlvWnkKpmdCc1uR8= =b4At -----END PGP SIGNATURE----- --=-Uwlh6YaxZUDOBu7d1sJK-- From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 08:18:04 2005 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 B5D4A16A4CE for ; Tue, 19 Apr 2005 08:18:04 +0000 (GMT) Received: from philemon.caltech.edu (philemon.caltech.edu [131.215.158.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74DB943D2F for ; Tue, 19 Apr 2005 08:18:04 +0000 (GMT) (envelope-from jd@philemon.caltech.edu) Received: from philemon.caltech.edu (localhost.caltech.edu [127.0.0.1]) by philemon.caltech.edu (8.13.1/8.12.9) with ESMTP id j3J8GkEu039457 for ; Tue, 19 Apr 2005 01:16:46 -0700 (PDT) (envelope-from jd@philemon.caltech.edu) Received: (from jd@localhost) by philemon.caltech.edu (8.13.1/8.12.9/Submit) id j3J8GkuH039456 for amd64@freebsd.org; Tue, 19 Apr 2005 01:16:46 -0700 (PDT) Date: Tue, 19 Apr 2005 01:16:46 -0700 From: Jonathan Dama To: amd64@freebsd.org Message-ID: <20050419081646.GD37497@philemon.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [update] 8GB issues, Tyan 2885 K8W 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, 19 Apr 2005 08:18:04 -0000 Several times in the past people have mentioned issues with 8GB of RAM on the Tyan 2885 K8W (including myself). Tyan recently posted a BIOS update (version 2.04) which corrects some issues in earlier BIOSs improperly computing memory timings. To summarize, I had experienced two issues: 1) I had observed panics under minimal load with 8GB with the BIOS autoconfiguring the memory speed. These problems were correctable by manually degrading the RAM speed as was possible with the 2.02 BIOS. Interestingly, memtest86+ did not report issues with the autoconfigured settings. But this perhaps is not surprising because evidence is that timings were marginal--some sticks of memory would work others wouldn't. e.g., I'd see situations were CPU0 seems to handle the 4 stick load but not CPU1. This of course is sensible due to component variation in a marginal configuration. The 2.04 BIOS now properly automatically configures to stable memory settings. *Note the route of this is that you can get to 8GB using 4 double-stacked DIMMs per CPU. We got into a very confusing situation because both single (double density) and double-stacked DIMMs had been purchased and our techs weren't communicating or paying attention to that in their problem reports. 2) The second problem involves the onboard broadcom and silicon images chipset. This problem has only manifested itself under heavy combinations of network and disk access. Unfortunately, I've never gotten a good crash-dump and the problem is hard to reproduce. I do not see similar issues with the em, ahc drivers. Nor did I see similar issues with the broadcom and si hardware under linux I hope this commentary is useful to people. I apologize for not having anything definite to report on #2. But the take away is that nothing is intrinsically wrong with FreeBSD 5-Stable on Tyan K8W (S2885) with 8GB--though something might be lurking in the onboard peripherals. -Jon From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 09:19:20 2005 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 8723016A4CE for ; Tue, 19 Apr 2005 09:19:20 +0000 (GMT) Received: from lib-eth.natur.cuni.cz (lib-eth.natur.cuni.cz [195.113.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF30543D3F for ; Tue, 19 Apr 2005 09:19:19 +0000 (GMT) (envelope-from xdavid@lib-eth.natur.cuni.cz) Received: from lib-eth.natur.cuni.cz (lib-eth.natur.cuni.cz [195.113.56.250]) j3J9JICE436853 for ; Tue, 19 Apr 2005 11:19:18 +0200 (MDT) X-Envelope-From: xdavid@lib-eth.natur.cuni.cz X-Envelope-To: Date: Tue, 19 Apr 2005 11:19:18 +0200 (CEST) From: David Komanek To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: designing new freebsd server for amd64 arch 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, 19 Apr 2005 09:19:20 -0000 Hi all, I am trying to design new machine for FreeBSD running on amd64 platform. I already read officially supported hardware list as well as many discussions concerning hardware for FreeBSD. Still I am not quite sure, what motherboard to choose. I need dual opteron motherboard, which covers (or can be extended by add-on cards) 2x Gb ethernet networking device and scsi raid 5. I read that FreeBSD has problems with asus and msi motherboards, so I decided to use some tyan board. Those with integrated ZCR Adaptec seem to me to be also problematic. What do you suggest based on your experience ? Now I prefer: Tyan Thunder K8WE, S2895A2NRF 2x AMD Opteron 250 Box Adaptec 2130SLP 4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm HP DLT 40/80 2x Gb LAN - I plan use the on-board ones but I am not sure whether - motherboard's nForce chipsets are well supported on amd64 port of FreeBSD - I can install directly to RAID 5 behind the Adaptec 2130SLP and boot from it without the need of installing on a separate SATA drive (or even old ATA ?) - is it possible to attach the HP DLT drive to the same SCSI controller as the RAID5-configured disks ? - how strong power supply should I use for this or similar configuration ? (I expect at least 500W, but what is your experience) Maybe you will suggest to use completely another motherboard - I am open to it too. Thanks in advance, David Komanek Charles University in Prague Prague, CZ From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 09:22:59 2005 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 2B00E16A4CF for ; Tue, 19 Apr 2005 09:22:59 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEEF743D1D for ; Tue, 19 Apr 2005 09:22:58 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from [213.225.74.166] (helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1DNowZ-000OdR-Bt; Tue, 19 Apr 2005 11:22:55 +0200 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Tue, 19 Apr 2005 11:22:53 +0200 From: Eirik =?ISO-8859-1?B?2A==?=verby To: Ken Gunderson , Message-ID: In-Reply-To: <20050418140342.4c168b72.kgunders@teamcool.net> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Re: REcomomendations- New to AMD64 Platform 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, 19 Apr 2005 09:22:59 -0000 Hi, stay away from the ZCR. It's not working in FreeBSD-amd64, and probably won't any time soon (according to the powers that be and who could fix it given time ;) /Eirik On 18-04-05 22:03, "Ken Gunderson" wrote: > Hello: > > I'm a long time FreeBSD useer but with as of yet no experience with the > ADM64 platform. Ready to take the plunge but want to make sure I've > got my ducks in a row first. > > I'm considering using a Tyan based barebones, e.g. TA26 which uses > their K8S Pro mainboard fleshed out with a couple 246's, ZCR, 2x1 GB > DDR333, and some seagate u320 scsi drives. Deployment will be web/ > application (maybe some Zope/ Plone/ JBoss/ Jetty/ Tomcat stuff)/ email > and database server project. No real heavy lifting on the db side. > > I've searched through the archives and find that there have been > various issues in the past with the Tyan K8SR and K8S Pro boards, but > from what I gather they were not necessarily platform specific, e.g. > broadcom driver and > 4gb of ram, and have apparently been resolved. > These two boards seem to use the same components but in different > layouts. Are there any outstanding issues with one vs. the other that > I should be aware of? > > Any feedback/advice greaty appreciated. Thanks. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 09:46:08 2005 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 0378F16A4CE for ; Tue, 19 Apr 2005 09:46:08 +0000 (GMT) Received: from mail.rootwarriors.com (a82-92-95-202.adsl.xs4all.nl [82.92.95.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC47543D1D for ; Tue, 19 Apr 2005 09:46:06 +0000 (GMT) (envelope-from mlambrichs@melange-it.nl) Received: from [127.0.0.1] (develop.home.melange-it.nl [127.0.0.1]) by mail.rootwarriors.com (Postfix) with ESMTP id 4F69F2A6817 for ; Tue, 19 Apr 2005 11:49:00 +0200 (CEST) Message-ID: <4264D40C.9050604@melange-it.nl> Date: Tue, 19 Apr 2005 11:49:00 +0200 From: Marc Lambrichs User-Agent: Mozilla Thunderbird 0.7.3 (X11/20050307) 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: supermicro X6DHP-8G2 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, 19 Apr 2005 09:46:08 -0000 I want to use raid5 on my supermicro 6014P-82R with a X6DHP-8G2 motherboard. So we had to let go of our Adaptec 2010S ZCR card, because it's not supported. What would you recommend to use instead? Cheers, marc From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 13:38:06 2005 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 75AA616A4CE for ; Tue, 19 Apr 2005 13:38:06 +0000 (GMT) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.FreeBSD.org (Postfix) with SMTP id 809B343D4C for ; Tue, 19 Apr 2005 13:38:05 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO 172.16.0.1) (mikej@69.193.222.195 with login) by smtp100.rog.mail.re2.yahoo.com with SMTP; 19 Apr 2005 13:38:04 -0000 Received: from 172.16.0.199 (SquirrelMail authenticated user mikej) by 172.16.0.1 with HTTP; Tue, 19 Apr 2005 09:38:01 -0400 (EDT) Message-ID: <3976.172.16.0.199.1113917881.squirrel@172.16.0.1> In-Reply-To: References: Date: Tue, 19 Apr 2005 09:38:01 -0400 (EDT) From: "Mike Jakubik" To: "David Komanek" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 13:38:06 -0000 On Tue, April 19, 2005 5:19 am, David Komanek said: > > > Now I prefer: > Tyan Thunder K8WE, S2895A2NRF > 2x AMD Opteron 250 Box > Adaptec 2130SLP > 4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm > HP DLT 40/80 > 2x Gb LAN - I plan use the on-board ones > I dont recommend an nForce chipset, specially one this new. Also, prepare for problems with the onboard bge nic card. People are experiencing crashes with it under load, and no one has solved the problem yet. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 14:47:51 2005 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 83B3716A4CE; Tue, 19 Apr 2005 14:47:51 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 657B043D5E; Tue, 19 Apr 2005 14:47:48 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.3/8.13.3) with ESMTP id j3JElh4p018156; Tue, 19 Apr 2005 10:47:43 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j3JElhni045999; Tue, 19 Apr 2005 10:47:43 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 282A27306E; Tue, 19 Apr 2005 10:47:43 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050419144743.282A27306E@freebsd-current.sentex.ca> Date: Tue, 19 Apr 2005 10:47:43 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner1 X-Virus-Status: Clean 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, 19 Apr 2005 14:47:51 -0000 TB --- 2005-04-19 12:57:13 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-19 12:57:13 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-04-19 12:57:13 - checking out the source tree TB --- 2005-04-19 12:57:13 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-04-19 12:57:13 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-04-19 13:03:59 - building world (CFLAGS=-O2 -pipe) TB --- 2005-04-19 13:03:59 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-19 13:03:59 - /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 >>> stage 5.1: building 32 bit shim libraries TB --- 2005-04-19 14:23:13 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-19 14:23:13 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-19 14:23:13 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Apr 19 14:23:13 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Tue Apr 19 14:38:56 UTC 2005 TB --- 2005-04-19 14:38:56 - generating LINT kernel config TB --- 2005-04-19 14:38:56 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-04-19 14:38:56 - /usr/bin/make -B LINT TB --- 2005-04-19 14:38:56 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-19 14:38:56 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-19 14:38:56 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Apr 19 14:38:57 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/gnu/ext2fs/ext2_linux_ialloc.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/gnu/ext2fs/ext2_lookup.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/gnu/ext2fs/ext2_subr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/gnu/ext2fs/ext2_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/gnu/ext2fs/ext2_vnops.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/hwpmc/hwpmc_mod.c /tinderbox/CURRENT/amd64/amd64/src/sys/hwpmc/hwpmc_mod.c: In function `pmc_debugflags_parse': /tinderbox/CURRENT/amd64/amd64/src/sys/hwpmc/hwpmc_mod.c:306: warning: 'e' might be used uninitialized in this function *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-04-19 14:47:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-19 14:47:42 - ERROR: failed to build lint kernel TB --- 2005-04-19 14:47:42 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 14:49:26 2005 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 B075F16A4CE for ; Tue, 19 Apr 2005 14:49:26 +0000 (GMT) Received: from mailserver.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 679AE43D1F for ; Tue, 19 Apr 2005 14:49:25 +0000 (GMT) (envelope-from don@SANDVINE.com) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 19 Apr 2005 10:49:23 -0400 Message-ID: <2BCEB9A37A4D354AA276774EE13FB8C23A6D34@mailserver.sandvine.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: supermicro X6DHP-8G2 Thread-Index: AcVExKBne7EDuCJgT5SL36TwWBaSrgAKhiyg From: "Don Bowman" To: "Marc Lambrichs" , Subject: RE: supermicro X6DHP-8G2 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, 19 Apr 2005 14:49:26 -0000 From: owner-freebsd-amd64@freebsd.org=20 > I want to use raid5 on my supermicro 6014P-82R with a=20 > X6DHP-8G2 motherboard. So we had to let go of our Adaptec=20 > 2010S ZCR card, because it's not supported. What would you=20 > recommend to use instead? I can't speak to the 64-bit cleanness, but the 'amr' [e.g. intel http://www.intel.com/design/servers/buildingblocks/raid.htm] are available in pci-express and work well, monitoring works as well [http://people.freebsd.org/~emoore/MegaRAID_SCSI/] From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 15:03:36 2005 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 7EF1E16A4CE for ; Tue, 19 Apr 2005 15:03:36 +0000 (GMT) Received: from web60003.mail.yahoo.com (web60003.mail.yahoo.com [216.109.116.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E41D143D53 for ; Tue, 19 Apr 2005 15:03:35 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 46906 invoked by uid 60001); 19 Apr 2005 15:03:35 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=donQFrMl+OSOJf5564v5BWqFalSuq+QYCihXJyQgT2BxWjxJTmrqoQASJbWsDlEO4+ZkMhYTc6rtiOy7ZPuXTZF2f3bkPwtG+wcYSL46SUbxZAZMtDtEw9QO/Z2jieiB/3w4ObXuBD6JoFEmRvxes8/aXvMj8Gen4oHOmqQ/DR8= ; Message-ID: <20050419150335.46904.qmail@web60003.mail.yahoo.com> Received: from [65.10.2.50] by web60003.mail.yahoo.com via HTTP; Tue, 19 Apr 2005 08:03:35 PDT Date: Tue, 19 Apr 2005 08:03:35 -0700 (PDT) From: Tom Shafron To: Mike Jakubik , David Komanek In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 15:03:36 -0000 I haven't experienced problems with the onboard bge NICs on my Tyan 2882... but now you have me nervous... do you have a link to people discussing the issues that I can check out? -Tom --- Mike Jakubik wrote: > On Tue, April 19, 2005 5:19 am, David Komanek said: > > > > > > Now I prefer: > > Tyan Thunder K8WE, S2895A2NRF > > 2x AMD Opteron 250 Box > > Adaptec 2130SLP > > 4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 > rpm > > HP DLT 40/80 > > 2x Gb LAN - I plan use the on-board ones > > > > I dont recommend an nForce chipset, specially one > this new. Also, prepare > for problems with the onboard bge nic card. People > are experiencing > crashes with it under load, and no one has solved > the problem yet. > > _______________________________________________ > 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" > __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 15:05:46 2005 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 71BE916A4CE for ; Tue, 19 Apr 2005 15:05:46 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F085443D58 for ; Tue, 19 Apr 2005 15:05:45 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 1A31AF7B1 for ; Tue, 19 Apr 2005 09:05:45 -0600 (MDT) Date: Tue, 19 Apr 2005 09:05:44 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050419090544.048b45c7.kgunders@teamcool.net> In-Reply-To: <20050419025122.88868.qmail@web60002.mail.yahoo.com> References: <20050419025122.88868.qmail@web60002.mail.yahoo.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: REcomomendations- New to AMD64 Platform 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, 19 Apr 2005 15:05:46 -0000 On Mon, 18 Apr 2005 19:51:21 -0700 (PDT) Tom Shafron wrote: > I'm running the K8S Pro (2882) with 4x512Mb, 2x246 > opteron and it's running great. Been up for about 2 > weeks straight as of today without any problems. Thanks. Reports like this are very helpful;-) Are you using a RAID solution? If so, which? I've seen conflicting reports on the ZCR but figured since it's adaptec, they will be resolved in 5.4. Thanks again. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 15:15:47 2005 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 5496C16A4CE for ; Tue, 19 Apr 2005 15:15:47 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E664443D3F for ; Tue, 19 Apr 2005 15:15:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JFHrIp081939; Tue, 19 Apr 2005 09:17:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42651FDC.405@samsco.org> Date: Tue, 19 Apr 2005 09:12:28 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Lambrichs References: <4264D40C.9050604@melange-it.nl> In-Reply-To: <4264D40C.9050604@melange-it.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: supermicro X6DHP-8G2 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, 19 Apr 2005 15:15:47 -0000 Marc Lambrichs wrote: > I want to use raid5 on my supermicro 6014P-82R with a X6DHP-8G2 > motherboard. So we had to let go of our Adaptec 2010S ZCR card, because > it's not supported. What would you recommend to use instead? > > Cheers, > marc > The 2010S is special since it uses the non-64-bit-clean ASR driver. Other Adaptec cards like the 2200 use the AAC driver which is 64-bit clean and is known to work on amd64. The LSI MegaRAID line of cards uses the AMR driver which is also 64-bit clean and known to work. Those are your only two choices for SCSI RAID. One thing to watch out for is that Intel rebrands ZCR cards from both ICP/Vortex and LSI. The driver for the former, IIR, is not 64-bit clean. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 15:17:11 2005 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 078D016A4CE for ; Tue, 19 Apr 2005 15:17:11 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7D3143D3F for ; Tue, 19 Apr 2005 15:17:10 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 41C21F7B3 for ; Tue, 19 Apr 2005 09:17:10 -0600 (MDT) Date: Tue, 19 Apr 2005 09:17:09 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050419091709.4bc580b1.kgunders@teamcool.net> In-Reply-To: <20050419150811.55515.qmail@web60004.mail.yahoo.com> References: <20050419150811.55515.qmail@web60004.mail.yahoo.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: REcomomendations- New to AMD64 Platform 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, 19 Apr 2005 15:17:11 -0000 On Tue, 19 Apr 2005 08:08:11 -0700 (PDT) Tom Shafron wrote: > Nope, using the SATA version of the board. Right now > I have a software RAID (gmirror) running but plan on > upgrading to a hardware solution shortly, doing my > research now... Happen to know the status of gvinum off the top of your head? Vinum was fine under 4.x but last I heard gvinum was long way from ready for prime time but I haven't kept up on this issue. I prefer a hw raid solution but also don't want to add another grand to the server budget. FWIW- I do know that the Intel ROB (raid on board) solutions are supported. So it's a drag there are issues on the AMD64 side, wh/is also Tier 1. Thanks for your input -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 16:15:10 2005 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 9AF6216A4CE for ; Tue, 19 Apr 2005 16:15:10 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20EA243D1D for ; Tue, 19 Apr 2005 16:15:10 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 4E19FF7B1 for ; Tue, 19 Apr 2005 10:15:09 -0600 (MDT) Date: Tue, 19 Apr 2005 10:15:08 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050419101508.74613c99.kgunders@teamcool.net> In-Reply-To: <42651FDC.405@samsco.org> References: <4264D40C.9050604@melange-it.nl> <42651FDC.405@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: supermicro X6DHP-8G2 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, 19 Apr 2005 16:15:10 -0000 On Tue, 19 Apr 2005 09:12:28 -0600 Scott Long wrote: > Marc Lambrichs wrote: > > I want to use raid5 on my supermicro 6014P-82R with a X6DHP-8G2 > > motherboard. So we had to let go of our Adaptec 2010S ZCR card, because > > it's not supported. What would you recommend to use instead? > > > > Cheers, > > marc > > > > The 2010S is special since it uses the non-64-bit-clean ASR driver. > Other Adaptec cards like the 2200 use the AAC driver which is > 64-bit clean and is known to work on amd64. The LSI MegaRAID > line of cards uses the AMR driver which is also 64-bit clean and > known to work. Those are your only two choices for SCSI RAID. > One thing to watch out for is that Intel rebrands ZCR cards from > both ICP/Vortex and LSI. The driver for the former, IIR, is not > 64-bit clean. Thanks for this Scott. Is it safe to conclude that the Adaptec 2130S listed under fbsd hw-amd64 fall under this category since they use same driver? Also safe to assume same for 2130SLP, wh/I don't see listed?? Or is Apdaptec playing chipset games between these models?? -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 16:39:35 2005 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 03CC416A4D0 for ; Tue, 19 Apr 2005 16:39:35 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43E1D43D53 for ; Tue, 19 Apr 2005 16:39:32 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JGfcxO082445; Tue, 19 Apr 2005 10:41:38 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4265337D.8000807@samsco.org> Date: Tue, 19 Apr 2005 10:36:13 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <4264D40C.9050604@melange-it.nl> <42651FDC.405@samsco.org> <20050419101508.74613c99.kgunders@teamcool.net> In-Reply-To: <20050419101508.74613c99.kgunders@teamcool.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: supermicro X6DHP-8G2 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, 19 Apr 2005 16:39:35 -0000 Ken Gunderson wrote: > On Tue, 19 Apr 2005 09:12:28 -0600 > Scott Long wrote: > > >>Marc Lambrichs wrote: >> >>>I want to use raid5 on my supermicro 6014P-82R with a X6DHP-8G2 >>>motherboard. So we had to let go of our Adaptec 2010S ZCR card, because >>>it's not supported. What would you recommend to use instead? >>> >>>Cheers, >>>marc >>> >> >>The 2010S is special since it uses the non-64-bit-clean ASR driver. >>Other Adaptec cards like the 2200 use the AAC driver which is >>64-bit clean and is known to work on amd64. The LSI MegaRAID >>line of cards uses the AMR driver which is also 64-bit clean and >>known to work. Those are your only two choices for SCSI RAID. >>One thing to watch out for is that Intel rebrands ZCR cards from >>both ICP/Vortex and LSI. The driver for the former, IIR, is not >>64-bit clean. > > > Thanks for this Scott. Is it safe to conclude that the Adaptec > 2130S listed under fbsd hw-amd64 fall under this category since they > use same driver? Also safe to assume same for 2130SLP, wh/I don't > see listed?? Or is Apdaptec playing chipset games between these models?? > I believe that the 2130S and 2130SLP are equivalent. I haven't seen the SLP variant, though, and it might have a different PCI ID that the driver doesn't recognise. Fixing that is easy if it is indeed the case. I haven't done a lot of testing with the 2130, but I believe that it should work. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 16:42:54 2005 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 844B916A4CE for ; Tue, 19 Apr 2005 16:42:54 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90B8C43D1D for ; Tue, 19 Apr 2005 16:42:53 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j3JG6x229887 for ; Tue, 19 Apr 2005 12:06:59 -0400 Message-ID: <42652CA3.8020605@infotechfl.com> Date: Tue, 19 Apr 2005 12:06:59 -0400 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> In-Reply-To: <20050419150335.46904.qmail@web60003.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 16:42:54 -0000 Tom, I'm not certain that this is definitively the bge interface, but even in light testing we've had the bge interface mysteriously hang. We had to power the entire server off and then on. Not even a soft reboot fixed the interface. Gary Tom Shafron wrote: > I haven't experienced problems with the onboard bge > NICs on my Tyan 2882... but now you have me nervous... > do you have a link to people discussing the issues > that I can check out? > > -Tom From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 16:45:04 2005 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 A70BF16A4CE for ; Tue, 19 Apr 2005 16:45:04 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 342EB43D55 for ; Tue, 19 Apr 2005 16:45:04 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j3JFWp226651 for ; Tue, 19 Apr 2005 11:32:51 -0400 Message-ID: <426524A2.9000600@infotechfl.com> Date: Tue, 19 Apr 2005 11:32:50 -0400 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <4264D40C.9050604@melange-it.nl> <42651FDC.405@samsco.org> In-Reply-To: <42651FDC.405@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: supermicro X6DHP-8G2 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, 19 Apr 2005 16:45:04 -0000 Scott, I just determined that aaccli is not supported under amd64 for aac based h/w RAID (specifically my Adaptec 2200S RAID controller). Any idea if or how much work will be required for aaccli to be supported under amd64? Thanks, Gary Scott Long wrote: > Marc Lambrichs wrote: > >> I want to use raid5 on my supermicro 6014P-82R with a X6DHP-8G2 >> motherboard. So we had to let go of our Adaptec 2010S ZCR card, >> because it's not supported. What would you recommend to use instead? >> >> Cheers, >> marc >> > > The 2010S is special since it uses the non-64-bit-clean ASR driver. > Other Adaptec cards like the 2200 use the AAC driver which is > 64-bit clean and is known to work on amd64. The LSI MegaRAID > line of cards uses the AMR driver which is also 64-bit clean and > known to work. Those are your only two choices for SCSI RAID. > One thing to watch out for is that Intel rebrands ZCR cards from > both ICP/Vortex and LSI. The driver for the former, IIR, is not > 64-bit clean. > > Scott > _______________________________________________ > 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 Tue Apr 19 16:50:49 2005 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 B9F6216A4CE for ; Tue, 19 Apr 2005 16:50:49 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55E3243D53 for ; Tue, 19 Apr 2005 16:50:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JGqtDV082513; Tue, 19 Apr 2005 10:52:55 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42653622.2070401@samsco.org> Date: Tue, 19 Apr 2005 10:47:30 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Mu1der References: <4264D40C.9050604@melange-it.nl> <42651FDC.405@samsco.org> <426524A2.9000600@infotechfl.com> In-Reply-To: <426524A2.9000600@infotechfl.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: supermicro X6DHP-8G2 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, 19 Apr 2005 16:50:49 -0000 Gary Mu1der wrote: > Scott, > > I just determined that aaccli is not supported under amd64 for aac based > h/w RAID (specifically my Adaptec 2200S RAID controller). > > Any idea if or how much work will be required for aaccli to be supported > under amd64? Hmm, good question. The FreeBSD aaccli that I provided way back when was statically linked against FreeBSD 4.4 libraries, so I guess that our i386 emulation would need to be able to handle that (and specifically some of the quirks in how libc_r worked back then). For fun, you might try compiling a kernel with COMPAT_LINUX32 and AAC_COMPAT_LINUX and running the linux aaccli under it. I can't think of a reason why it wouldn't work, but I haven't tried it myself. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 16:59:44 2005 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 5C73816A4CE for ; Tue, 19 Apr 2005 16:59:44 +0000 (GMT) Received: from web60008.mail.yahoo.com (web60008.mail.yahoo.com [216.109.116.246]) by mx1.FreeBSD.org (Postfix) with SMTP id DF0AA43D45 for ; Tue, 19 Apr 2005 16:59:43 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 17395 invoked by uid 60001); 19 Apr 2005 16:59:43 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=2T2N/zRwZpIkkQ6aWWW1ccEJQ8LBmBqwFeVlx7pI9LIHtm0q6F0CwcKGR86ivstOePi2pdk4kDkXqJ6keSVLYuACf0gdotf670b79QJps/Qn33yr0GQjKBbrfVYiGvoYeRlMfSLeLza9M/qr4umLfc+f5PoYgDrxJ5luCgp1u1s= ; Message-ID: <20050419165943.17392.qmail@web60008.mail.yahoo.com> Received: from [65.10.4.147] by web60008.mail.yahoo.com via HTTP; Tue, 19 Apr 2005 09:59:43 PDT Date: Tue, 19 Apr 2005 09:59:43 -0700 (PDT) From: Tom Shafron To: Gary Mu1der , freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 16:59:44 -0000 How often did this occur for you? What was the use for the light testing (how man connections/sec and Mb/sec)? I'm trying to figure out if the testing I've done would have shown this issue already or not... I haven't gone live with the server yet so have only been using it for beta testing... I did quite a few bursts at about 50Mbps and 1200 conns/sec for about 1 minute at a time and didn't have any problems and since then it's been running at much lower traffic (maybe 1 connection every 30 seconds). It's been up for a couple of weeks with no apparent issues/hangs... but as I said it hasn't been under much strain yet... --- Gary Mu1der wrote: > Tom, > > I'm not certain that this is definitively the bge > interface, but even in > light testing we've had the bge interface > mysteriously hang. We had to > power the entire server off and then on. Not even a > soft reboot fixed > the interface. > > Gary > > Tom Shafron wrote: > > I haven't experienced problems with the onboard > bge > > NICs on my Tyan 2882... but now you have me > nervous... > > do you have a link to people discussing the issues > > that I can check out? > > > > -Tom > _______________________________________________ > 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" > __________________________________ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:05:24 2005 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 07AC516A4CE for ; Tue, 19 Apr 2005 17:05:24 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA48943D54 for ; Tue, 19 Apr 2005 17:05:23 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 2AB0BF7B1 for ; Tue, 19 Apr 2005 11:05:23 -0600 (MDT) Date: Tue, 19 Apr 2005 11:05:22 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050419110522.1978d303.kgunders@teamcool.net> In-Reply-To: <20050419165943.17392.qmail@web60008.mail.yahoo.com> References: <20050419165943.17392.qmail@web60008.mail.yahoo.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 17:05:24 -0000 On Tue, 19 Apr 2005 09:59:43 -0700 (PDT) Tom Shafron wrote: > How often did this occur for you? What was the use > for the light testing (how man connections/sec and > Mb/sec)? I'm trying to figure out if the testing I've > done would have shown this issue already or not... > > I haven't gone live with the server yet so have only > been using it for beta testing... I did quite a few > bursts at about 50Mbps and 1200 conns/sec for about 1 > minute at a time and didn't have any problems and > since then it's been running at much lower traffic > (maybe 1 connection every 30 seconds). It's been up > for a couple of weeks with no apparent issues/hangs... > but as I said it hasn't been under much strain yet... > > --- Gary Mu1der wrote: > > Tom, > > > > I'm not certain that this is definitively the bge > > interface, but even in > > light testing we've had the bge interface > > mysteriously hang. We had to > > power the entire server off and then on. Not even a > > soft reboot fixed > > the interface. > > > > Gary > > > > Tom Shafron wrote: > > > I haven't experienced problems with the onboard > > bge > > > NICs on my Tyan 2882... but now you have me > > nervous... > > > do you have a link to people discussing the issues > > > that I can check out? fwiw- I had some privte correspondence with Vivek, who was having such issues. He moved off the bge and they cleared up. Apparently works pretty well since he informed me that he's ordered a sister machine. The systems in quiestion were doing some heavy db lifting. Think he swithced to Intel NIC. Check the archives earlier this month. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:15:53 2005 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 08C2616A4CE for ; Tue, 19 Apr 2005 17:15:53 +0000 (GMT) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5C9A43D31 for ; Tue, 19 Apr 2005 17:15:52 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [IPv6:2001:960:301:3:a00:20ff:fe85:fa39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id 3D45D3F294; Tue, 19 Apr 2005 19:15:51 +0200 (CEST) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 4E0FF192; Tue, 19 Apr 2005 19:15:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 401EE127; Tue, 19 Apr 2005 19:15:51 +0200 (CEST) Date: Tue, 19 Apr 2005 19:15:51 +0200 (CEST) From: Sten Spans To: Mike Jakubik In-Reply-To: <3976.172.16.0.199.1113917881.squirrel@172.16.0.1> Message-ID: References: <3976.172.16.0.199.1113917881.squirrel@172.16.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 17:15:53 -0000 On Tue, 19 Apr 2005, Mike Jakubik wrote: > On Tue, April 19, 2005 5:19 am, David Komanek said: >> >> >> Now I prefer: >> Tyan Thunder K8WE, S2895A2NRF >> 2x AMD Opteron 250 Box >> Adaptec 2130SLP >> 4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm >> HP DLT 40/80 >> 2x Gb LAN - I plan use the on-board ones >> > > I dont recommend an nForce chipset, specially one this new. Also, prepare > for problems with the onboard bge nic card. People are experiencing > crashes with it under load, and no one has solved the problem yet. This board has nvidia ethernet ports, the second ethernet and pci-e are connected to the second cpu. Afaik fbsd supports the binary nvidia driver for this board with the net/nvnet port and with the nve(4) driver in current ( which also requires the binary blob ). Linux has the forcedeth driver which is gpl, but might be useful for anyone interested in working on an open driver. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:17:27 2005 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 A5AEE16A4CF for ; Tue, 19 Apr 2005 17:17:27 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49BC043D2F for ; Tue, 19 Apr 2005 17:17:27 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3JHHPXg026204; Tue, 19 Apr 2005 10:17:25 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3JHHPJR026203; Tue, 19 Apr 2005 10:17:25 -0700 (PDT) (envelope-from obrien) Date: Tue, 19 Apr 2005 10:17:25 -0700 From: "David O'Brien" To: Tom Shafron Message-ID: <20050419171725.GA26152@dragon.NUXI.org> References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419150335.46904.qmail@web60003.mail.yahoo.com> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 17:17:27 -0000 [ don't top post! ] --- Mike Jakubik wrote: > On Tue, Apr 19, 2005 at 08:03:35AM -0700, Tom Shafron wrote: > > On Tue, April 19, 2005 5:19 am, David Komanek said: > > > Now I prefer: > > > Tyan Thunder K8WE, S2895A2NRF ... > > I dont recommend an nForce chipset, specially one > > this new. Also, prepare > > for problems with the onboard bge nic card. People > > are experiencing > > crashes with it under load, and no one has solved > > the problem yet. > > I haven't experienced problems with the onboard bge > NICs on my Tyan 2882... but now you have me nervous... > do you have a link to people discussing the issues > that I can check out? s2882 != S2895A2NRF. The two are very different and use different Broadcom silicon. There are also problems using Linux on this motherboard. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:27:13 2005 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 1336516A4CE for ; Tue, 19 Apr 2005 17:27:13 +0000 (GMT) Received: from web60004.mail.yahoo.com (web60004.mail.yahoo.com [216.109.116.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 63D9243D53 for ; Tue, 19 Apr 2005 17:27:12 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 4962 invoked by uid 60001); 19 Apr 2005 17:27:11 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=rbom0XLuD4qTokOK6PHmZiQIh4TvATEllLQsslS2adBC/Y9xa0M2TPRisjHNUCMyS4GmlPDqC4wmoKYq8BeUGUW/FibUmm7nbnxxTzWRfsrsWuvZzKVJeJ3WL7uv+oy/TeZxkxSoFeIEVJa8+MqI19V2QXqOozqXD+BxkeR9+1I= ; Message-ID: <20050419172711.4960.qmail@web60004.mail.yahoo.com> Received: from [65.10.4.147] by web60004.mail.yahoo.com via HTTP; Tue, 19 Apr 2005 10:27:11 PDT Date: Tue, 19 Apr 2005 10:27:11 -0700 (PDT) From: Tom Shafron To: obrien@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 17:27:13 -0000 --- David O'Brien wrote: > [ don't top post! ] > > --- Mike Jakubik wrote: > > On Tue, Apr 19, 2005 at 08:03:35AM -0700, Tom > Shafron wrote: > > > On Tue, April 19, 2005 5:19 am, David Komanek > said: > > > > Now I prefer: > > > > Tyan Thunder K8WE, S2895A2NRF > ... > > > I dont recommend an nForce chipset, specially > one > > > this new. Also, prepare > > > for problems with the onboard bge nic card. > People > > > are experiencing > > > crashes with it under load, and no one has > solved > > > the problem yet. > > > > I haven't experienced problems with the onboard > bge > > NICs on my Tyan 2882... but now you have me > nervous... > > do you have a link to people discussing the issues > > that I can check out? > > s2882 != S2895A2NRF. The two are very different and > use different > Broadcom silicon. > > There are also problems using Linux on this > motherboard. > > -- > -- David (obrien@FreeBSD.org) > Sorry about the top posting, new to mailing lists and didn't know the etiquette. Assumed that the broadcoms on both boards were the same, my mistake... Looks like the K8W uses the BCM5703C and the K8S Pro uses the BCM5704C.... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:27:57 2005 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 89FFF16A4CE for ; Tue, 19 Apr 2005 17:27:57 +0000 (GMT) Received: from pigeon.infotechfl.com (mailrelay.infotechfl.com [209.251.147.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E26E843D48 for ; Tue, 19 Apr 2005 17:27:56 +0000 (GMT) (envelope-from gmulder@infotechfl.com) Received: from [172.20.0.75] (gmulder.infotechfl.com [172.20.0.75]) by pigeon.infotechfl.com (8.11.6/8.11.6) with ESMTP id j3JHRt204624; Tue, 19 Apr 2005 13:27:55 -0400 Message-ID: <42653F9B.5070605@infotechfl.com> Date: Tue, 19 Apr 2005 13:27:55 -0400 From: Gary Mu1der User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Shafron References: <20050419165943.17392.qmail@web60008.mail.yahoo.com> In-Reply-To: <20050419165943.17392.qmail@web60008.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 17:27:57 -0000 Tom, As I said, I'm not definitively certain this was the bge interface. ipf was loaded, but was configured to pass all for all interfaces on the system. We were just ssh'd into the system so load was non-existent. A few weeks ago we transferred 20GB of data via rsync to the system with no issues. Established ssh connections were fine, nmap reported that ssh was listening on port 22, but no new ssh connection to the system would complete. Using telnet to connect to port 22 didn't get any response. Rebooting the system didn't fix the problem. We had to power cycle the system before it fixed itself. Gary Tom Shafron wrote: > How often did this occur for you? What was the use > for the light testing (how man connections/sec and > Mb/sec)? I'm trying to figure out if the testing I've > done would have shown this issue already or not... > > I haven't gone live with the server yet so have only > been using it for beta testing... I did quite a few > bursts at about 50Mbps and 1200 conns/sec for about 1 > minute at a time and didn't have any problems and > since then it's been running at much lower traffic > (maybe 1 connection every 30 seconds). It's been up > for a couple of weeks with no apparent issues/hangs... > but as I said it hasn't been under much strain yet... > > --- Gary Mu1der wrote: > >>Tom, >> >>I'm not certain that this is definitively the bge >>interface, but even in >>light testing we've had the bge interface >>mysteriously hang. We had to >>power the entire server off and then on. Not even a >>soft reboot fixed >>the interface. >> >>Gary From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:32:55 2005 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 9E07816A4CE for ; Tue, 19 Apr 2005 17:32:55 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 640BA43D2F for ; Tue, 19 Apr 2005 17:32:55 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3JHWma2026526; Tue, 19 Apr 2005 10:32:48 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3JHWlrX026525; Tue, 19 Apr 2005 10:32:47 -0700 (PDT) (envelope-from obrien) Date: Tue, 19 Apr 2005 10:32:47 -0700 From: "David O'Brien" To: "O. Hartmann" Message-ID: <20050419173247.GB26152@dragon.NUXI.org> References: <20050413210855.GA15088@bitsurf.net> <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <86ekdbdnqh.fsf@xps.des.no> <4260F103.5050309@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4260F103.5050309@mail.uni-mainz.de> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 17:32:55 -0000 On Sat, Apr 16, 2005 at 01:03:31PM +0200, O. Hartmann wrote: > I have ASUS A8N-SLI Deluxe mobo. BIOS revision is 1006. I have no > problems with > ACPI. APIC works with NO_MIXED_MODE commented out in kernel. Disable the NO_MIXED_MODE option is a performance degradation. Bending over and taking it up the a** across all motherboards (which DES has forced on 5.4-RELEASE); makes the ASUS A8N-SLI Deluxe not "perfectly working". So yes people, you CAN get FreeBSD working on nForce-based motherboards. BUT how much do you want to sacrifice?? Degradation performance, not being able to use PowerNow!, not being able to use on-board NIC's, not being able to use on-board sound, etc... Why go thru all this when there is ZERO need to????????????? When one buys a motherboard, they have the choice to pick a motherboard that won't cause you major pain. So why not just do that?? > The only point I would complain about is the still 'GENERIC' > SATA150/SATA300 (switched back to UDMA33) > controller of the nForce4 chipset, but as DES answered me on a prior > posting this is due to a too fresh chipset. Another thing that isn't working for some nForce-based motherboards. Why not buy hardware that is well supported by FreeBSD today? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 17:40:20 2005 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 22F0E16A4CE for ; Tue, 19 Apr 2005 17:40:03 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5938043D49 for ; Tue, 19 Apr 2005 17:40:02 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3JHdvwd026701; Tue, 19 Apr 2005 10:39:57 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3JHdvCc026700; Tue, 19 Apr 2005 10:39:57 -0700 (PDT) (envelope-from obrien) Date: Tue, 19 Apr 2005 10:39:57 -0700 From: "David O'Brien" To: Dag-Erling =?unknown-8bit?Q?Sm=F8rgrav?= Message-ID: <20050419173957.GC26152@dragon.NUXI.org> References: <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <2fd864e050415174048dc579d@mail.gmail.com> <346a802205041519071e4dc609@mail.gmail.com> <4260D654.3060301@mail.uni-mainz.de> <861x9bdlsz.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <861x9bdlsz.fsf@xps.des.no> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: "O. Hartmann" cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 17:40:20 -0000 On Sat, Apr 16, 2005 at 01:05:00PM +0200, Dag-Erling Smrgrav wrote: > "O. Hartmann" writes: > > My question si: how to force nVidia delivering the needed > > informations? It should be an aspect of customer demand. nVidia > > earns money with each sold nForce based motherboard and each GForce > > based graphics card and the better the support, the more they can > > sell. > > Why would they care about FreeBSD users? Unlike Linux, FreeBSD has > approximately zero brainshare in the computer press, and unlike > FreeBSD, Linux runs perfectly well on nForce chipsets. In fact, the > Asus SK8N which David loathes is "Linux-certified". You have NO idea how many hoops Linux jumps thru to run on the Asus SK8N. Let me repeat to you again -- _I_ was the first person to try to run 64-bit Linux on this motherboard. It didn't work. The Linux kernel grew many, many patches to deal with this motherboard and so you should be saying it is only "Linux-certified" for newer versions of Linux. However, I can run older FreeBSD versions on both AMD and VIA baesd motherboards (ie, FreeBSD versions released before the chipsets were produced). What does that tell you?? > If I didn't already know that FreeBSD is perfect and flawless and that > David is the Christ reborn, I'd be tempted to conclude that there is > something wrong with FreeBSD (or David), not with the nForce chipset. If I didn't already know DES was a huge ass.... -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:00:37 2005 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 9A9EC16A4CF for ; Tue, 19 Apr 2005 18:00:37 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D3AC43D39 for ; Tue, 19 Apr 2005 18:00:37 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3JI0bQY088673 for ; Tue, 19 Apr 2005 18:00:37 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3JI0bgM088672; Tue, 19 Apr 2005 18:00:37 GMT (envelope-from gnats) Resent-Date: Tue, 19 Apr 2005 18:00:37 GMT Resent-Message-Id: <200504191800.j3JI0bgM088672@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Florent Thoumie Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BAD216A4CE for ; Tue, 19 Apr 2005 17:50:33 +0000 (GMT) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 608C743D5F for ; Tue, 19 Apr 2005 17:50:32 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 3D1EE11925 for ; Tue, 19 Apr 2005 19:56:11 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94376-02 for ; Tue, 19 Apr 2005 19:55:56 +0200 (CEST) Received: by smtp.xbsd.org (Postfix, from userid 2001) id BF45711A7B; Tue, 19 Apr 2005 19:55:56 +0200 (CEST) Message-Id: <20050419175556.BF45711A7B@smtp.xbsd.org> Date: Tue, 19 Apr 2005 19:55:56 +0200 (CEST) From: Florent Thoumie To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/80114: kldload snd_ich causes interrupt storm when ACPI is enabled X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Florent Thoumie List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 18:00:37 -0000 >Number: 80114 >Category: amd64 >Synopsis: kldload snd_ich causes interrupt storm when ACPI is enabled >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Apr 19 18:00:36 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Florent Thoumie >Release: FreeBSD 5.3-RELEASE i386 >Organization: Xbsd.org >Environment: System: FreeBSD srv1.xbsd.org 5.3-RELEASE FreeBSD 5.3-RELEASE #2: Wed Nov 24 16:35:34 CET 2004 root@gate.xbsd.org:/usr/src/sys/i386/compile/GATE i386 >Description: Here is the trace I got : flz cream> kgdb -c /usr/tmp/vmcore.6 /usr/src/sys/amd64/compile/CREAM/kernel.deb ug [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde fined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". #0 doadump () at pcpu.h:167 167 pcpu.h: No such file or directory. in pcpu.h (gdb) bt #0 doadump () at pcpu.h:167 #1 0x0000000000000000 in ?? () #2 0xffffffff8031ffb7 in boot (howto=260) at ../../../kern/kern_shutdown.c:410 #3 0xffffffff80320696 in panic (fmt=0xffffff0015e02a00 "ÐeÎ\026") at ../../../kern/kern_shutdown.c:566 #4 0xffffffff80484e42 in trap_fatal (frame=0xffffff0015e02a00, eva=18446742974580549072) at ../../../amd64/amd64/trap.c:631 #5 0xffffffff8048515f in trap_pfault (frame=0xffffffff96a1c3c0, usermode=0) at ../../../amd64/amd64/trap.c:554 #6 0xffffffff80485403 in trap (frame= {tf_rdi = -1099500558560, tf_rsi = 4, tf_rdx = 20, tf_rcx = -1099123103672 , tf_r8 = 0, tf_r9 = -1, tf_rax = 3524276224, tf_rbx = -1099500558560, tf_rbp = 0, tf_r10 = 8194, tf_r11 = -2145800080, tf_r12 = 0, tf_r13 = -1, tf_r14 = 4, tf_ r15 = 256, tf_trapno = 12, tf_addr = 3524276232, tf_flags = -2140179872, tf_err = 0, tf_rip = -2144108211, tf_cs = 8, tf_rflags = 66054, tf_rsp = -1767783288, t f_ss = 16}) at ../../../amd64/amd64/trap.c:333 #7 0xffffffff80474d1b in calltrap () at ../../../amd64/amd64/exception.S:171 #8 0xffffff0000a8e720 in ?? () #9 0x0000000000000004 in ?? () #10 0x0000000000000014 in ?? () #11 0xffffff0017286848 in ?? () #12 0x0000000000000000 in ?? () #13 0xffffffffffffffff in ?? () #14 0x00000000d2103000 in ?? () #15 0xffffff0000a8e720 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000002002 in ?? () #18 0xffffffff8019b070 in acpi_sysres_find () at ../../../dev/acpica/acpi.c:960 #19 0x0000000000000000 in ?? () #20 0xffffffffffffffff in ?? () #21 0x0000000000000004 in ?? () #22 0x0000000000000100 in ?? () #23 0x000000000000000c in ?? () #24 0x00000000d2103008 in ?? () #25 0xffffffff806f7260 in kernel_console_ts () #26 0x0000000000000000 in ?? () #27 0xffffffff8033814d in resource_list_find (rl=0x0, type=0, rid=0) at ../../../kern/subr_bus.c:2480 #28 0x0000000000000008 in ?? () #29 0x0000000000010206 in ?? () #30 0xffffffff96a1c488 in ?? () #31 0x0000000000000010 in ?? () #32 0x0000000000000000 in ?? () #33 0xffffffff8019b10b in acpi_alloc_resource (bus=0xffffff0000994c00, child=0xffffff0000a8e600, type=4, rid=0xffffff0017286848, start=0, end=18446744073709551615, count=256, flags=8194) at ../../../dev/acpica/acpi.c:982 #34 0xffffffff802746be in pci_alloc_resource (dev=0x1e, child=0xffffff0000a8e600, type=4, rid=0xffffff0017286848, start=0, end=18446744073709551615, count=0, flags=2) at bus_if.h:262 #35 0xffffffff80335714 in bus_alloc_resource (dev=0xffffff0000a8e600, type=4, rid=0xffffff0017286848, start=0, end=18446744073709551615, count=1, flags=0) at bus_if.h:262 #36 0xffffffff96a9b350 in ?? () #37 0xffffff0000000002 in ?? () #38 0xffffff001ffe5000 in ?? () #39 0x0000000000000001 in ?? () #40 0xffffff0000ad5300 in ?? () #41 0xffffff001ffe5000 in ?? () #42 0xffffffff803148f9 in malloc (size=0, type=0xffffff0000a8e600, flags=-1767259808) at ../../../kern/kern_malloc.c:292 #43 0x00000000005910de in ?? () #44 0x0000000000000043 in ?? () #45 0xffffffff802741fb in pci_read_ivar (dev=0x0, child=0x0, which=11069064, result=0xffffffff803283bc) at ../../../dev/pci/pci.c:1464 #46 0xffffffff80273b00 in pci_print_child (dev=0x5910de, child=0x5910de) at ../../../dev/pci/pci.c:1197 #47 0xffffffff80337a28 in device_attach (dev=0xffffff0000a8e600) at device_if.h:177 #48 0xffffffff80273958 in pci_driver_added (dev=0xffffff0000a8e600, driver=0x5) at ../../../dev/pci/pci.c:1170 #49 0xffffffff8033653c in devclass_add_driver (dc=0xffffff00009b6800, driver=0xffffffff96a9c160) at bus_if.h:183 #50 0xffffffff80339e89 in driver_module_handler (mod=0xffffff0015adb480, what=-1767259808, arg=0x0) at ../../../kern/subr_bus.c:3535 #51 0xffffffff80315fa6 in module_register_init (arg=0x0) at ../../../kern/kern_module.c:121 #52 0xffffffff803124d8 in linker_load_module ( kldname=0xffffff00009e5420 "/boot/kernel/snd_ich.ko", modname=0xffffff0000aaf400 "snd_ich", parent=0x0, verinfo=0x0, lfpp=0xffffffff96a1cb70) at ../../../kern/kern_linker.c:193 #53 0xffffffff80312709 in kldload (td=0xffffff0015e02a00, uap=0xffffffff96a1cbc0) at ../../../kern/kern_linker.c:776 #54 0xffffffff80485b0c in syscall (frame= {tf_rdi = 140737488350808, tf_rsi = 140737488350376, tf_rdx = 1, tf_rcx = 140737488350808, tf_r8 = 4294967295, tf_r9 = 140737488350072, tf_rax = 304, tf_r bx = 0, tf_rbp = 140737488350384, tf_r10 = 4294967295, tf_r11 = 598, tf_r12 = 0, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr = 34366580844, tf_f lags = 0, tf_err = 2, tf_rip = 34366580856, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488350264, tf_ss = 35}) at ../../../amd64/amd64/trap.c:763 #55 0xffffffff80474e58 in Xfast_syscall () at ../../../amd64/amd64/exception.S:248 #56 0x00007fffffffee58 in ?? () #57 0x00007fffffffeca8 in ?? () dmesg is at [1] and kernel configuration is at [2]. Notes: I'm using SCHED_ULE and PREEMPTION. [1] http://people.freebsd.org/~flz/local/dmesg.cream [2] http://people.freebsd.org/~flz/local/CREAM >How-To-Repeat: Boot my box (Asus A8N-SLI Deluxe Motherboard) with ACPI enabled # kldload snd_ich *kaboom* >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:03:15 2005 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 75DE216A4CE; Tue, 19 Apr 2005 18:03:15 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B500343D49; Tue, 19 Apr 2005 18:03:12 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JI5IjW082910; Tue, 19 Apr 2005 12:05:18 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42654719.7030607@samsco.org> Date: Tue, 19 Apr 2005 11:59:53 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050413210855.GA15088@bitsurf.net> <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <86ekdbdnqh.fsf@xps.des.no> <4260F103.5050309@mail.uni-mainz.de> <20050419173247.GB26152@dragon.NUXI.org> In-Reply-To: <20050419173247.GB26152@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: "O. Hartmann" cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 18:03:15 -0000 David O'Brien wrote: > On Sat, Apr 16, 2005 at 01:03:31PM +0200, O. Hartmann wrote: > >>I have ASUS A8N-SLI Deluxe mobo. BIOS revision is 1006. I have no >>problems with >>ACPI. APIC works with NO_MIXED_MODE commented out in kernel. > > > Disable the NO_MIXED_MODE option is a performance degradation. > Bending over and taking it up the a** across all motherboards (which DES > has forced on 5.4-RELEASE); makes the ASUS A8N-SLI Deluxe not "perfectly > working". > According to the APIC maintainer, and according to some quick benchmarks myself, mixed mode has almost no performance impact. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:04:48 2005 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 3535616A4D1; Tue, 19 Apr 2005 18:04:48 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B0C343D45; Tue, 19 Apr 2005 18:04:47 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JI6psf082923; Tue, 19 Apr 2005 12:06:51 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42654776.9010205@samsco.org> Date: Tue, 19 Apr 2005 12:01:26 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <2fd864e050415174048dc579d@mail.gmail.com> <346a802205041519071e4dc609@mail.gmail.com> <4260D654.3060301@mail.uni-mainz.de> <861x9bdlsz.fsf@xps.des.no> <20050419173957.GC26152@dragon.NUXI.org> In-Reply-To: <20050419173957.GC26152@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: "O. Hartmann" cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 18:04:48 -0000 David O'Brien wrote: > On Sat, Apr 16, 2005 at 01:05:00PM +0200, Dag-Erling Smrgrav wrote: > >>"O. Hartmann" writes: >> >>>My question si: how to force nVidia delivering the needed >>>informations? It should be an aspect of customer demand. nVidia >>>earns money with each sold nForce based motherboard and each GForce >>>based graphics card and the better the support, the more they can >>>sell. >> >>Why would they care about FreeBSD users? Unlike Linux, FreeBSD has >>approximately zero brainshare in the computer press, and unlike >>FreeBSD, Linux runs perfectly well on nForce chipsets. In fact, the >>Asus SK8N which David loathes is "Linux-certified". > > > You have NO idea how many hoops Linux jumps thru to run on the Asus SK8N. > Let me repeat to you again -- _I_ was the first person to try to run > 64-bit Linux on this motherboard. It didn't work. The Linux kernel grew > many, many patches to deal with this motherboard and so you should be > saying it is only "Linux-certified" for newer versions of Linux. > > However, I can run older FreeBSD versions on both AMD and VIA baesd > motherboards (ie, FreeBSD versions released before the chipsets were > produced). What does that tell you?? > > >>If I didn't already know that FreeBSD is perfect and flawless and that >>David is the Christ reborn, I'd be tempted to conclude that there is >>something wrong with FreeBSD (or David), not with the nForce chipset. > > > If I didn't already know DES was a huge ass.... > Enough of this junk on this list. DES's proposal for mixed mode in 5.4 has the full support of the RE team, and as I said in another email it has no performance impact while expanding compatibility. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:09:56 2005 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 9BC4916A4CF for ; Tue, 19 Apr 2005 18:09:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B67643D2F for ; Tue, 19 Apr 2005 18:09:56 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1577614wra for ; Tue, 19 Apr 2005 11:09:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UxyAlKSTNlLc8XaAcLqZmRN3hwm6xIuAOdyGtgoL0Fe3vJY9PODgmjlIQmdb8wSgCPp0wPddCb47hnjAxDc8zs0Lw1d2RpqXPX1XoCZ2DpGZ2aqZm3Mxk7Kqb+WTN6YI/m/bglnatWGCFURHkAKRuwRUjFQtE0XIKCnn+2vP1Hk= Received: by 10.54.73.16 with SMTP id v16mr1070224wra; Tue, 19 Apr 2005 11:09:55 -0700 (PDT) Received: by 10.54.40.69 with HTTP; Tue, 19 Apr 2005 11:09:55 -0700 (PDT) Message-ID: <2fd864e0504191109567e435e@mail.gmail.com> Date: Tue, 19 Apr 2005 11:09:55 -0700 From: Astrodog To: obrien@freebsd.org In-Reply-To: <20050419173957.GC26152@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200504131714.20356.jkim@niksun.com> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <2fd864e050415174048dc579d@mail.gmail.com> <346a802205041519071e4dc609@mail.gmail.com> <4260D654.3060301@mail.uni-mainz.de> <861x9bdlsz.fsf@xps.des.no> <20050419173957.GC26152@dragon.NUXI.org> cc: "O. Hartmann" cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 18:09:56 -0000 On 4/19/05, David O'Brien wrote: > On Sat, Apr 16, 2005 at 01:05:00PM +0200, Dag-Erling Smrgrav wrote: > > "O. Hartmann" writes: > > > My question si: how to force nVidia delivering the needed > > > informations? It should be an aspect of customer demand. nVidia > > > earns money with each sold nForce based motherboard and each GForce > > > based graphics card and the better the support, the more they can > > > sell. > > > > Why would they care about FreeBSD users? Unlike Linux, FreeBSD has > > approximately zero brainshare in the computer press, and unlike > > FreeBSD, Linux runs perfectly well on nForce chipsets. In fact, the > > Asus SK8N which David loathes is "Linux-certified". >=20 > You have NO idea how many hoops Linux jumps thru to run on the Asus SK8N. > Let me repeat to you again -- _I_ was the first person to try to run > 64-bit Linux on this motherboard. It didn't work. The Linux kernel grew > many, many patches to deal with this motherboard and so you should be > saying it is only "Linux-certified" for newer versions of Linux. >=20 > However, I can run older FreeBSD versions on both AMD and VIA baesd > motherboards (ie, FreeBSD versions released before the chipsets were > produced). What does that tell you?? >=20 > > If I didn't already know that FreeBSD is perfect and flawless and that > > David is the Christ reborn, I'd be tempted to conclude that there is > > something wrong with FreeBSD (or David), not with the nForce chipset. >=20 > If I didn't already know DES was a huge ass.... >=20 Oddly enough, the motherboard in the R3000Z mobiles, once the keyboard patch, and DSDT table are setup, works great. Its an nForce3 150 based thing. I suspect the problem is more with the BIOS implimentation, than the chipset itself, thus explaining the mixed results everyone is having. I would be extremely hesitant to reccomend nforce3 equipment, simply because a rather large percentage of it doesn't work. Even on this platform (The R3000Zs), there are some pretty ardious steps you have to go through, that involve SSHing in to get DSDT dumps, etc. Certainly reccomending something that causes a performance hit, and limited functionality isn't a great idea, when better, completely functional alternatives exist, for the same price. Not sure its worth anything, but gotta agree with David on this one. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:18:34 2005 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 4A51A16A4CE for ; Tue, 19 Apr 2005 18:18:34 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC4D443D1F for ; Tue, 19 Apr 2005 18:18:33 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3JIIX5n027891; Tue, 19 Apr 2005 11:18:33 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3JIIVlC027890; Tue, 19 Apr 2005 11:18:31 -0700 (PDT) (envelope-from obrien) Date: Tue, 19 Apr 2005 11:18:31 -0700 From: "David O'Brien" To: Scott Long Message-ID: <20050419181831.GA27679@dragon.NUXI.org> References: <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <86ekdbdnqh.fsf@xps.des.no> <4260F103.5050309@mail.uni-mainz.de> <20050419173247.GB26152@dragon.NUXI.org> <42654719.7030607@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42654719.7030607@samsco.org> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: "O. Hartmann" cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 18:18:34 -0000 On Tue, Apr 19, 2005 at 11:59:53AM -0600, Scott Long wrote: > David O'Brien wrote: > >On Sat, Apr 16, 2005 at 01:03:31PM +0200, O. Hartmann wrote: > > > >>I have ASUS A8N-SLI Deluxe mobo. BIOS revision is 1006. I have no > >>problems with > >>ACPI. APIC works with NO_MIXED_MODE commented out in kernel. > > > > > >Disable the NO_MIXED_MODE option is a performance degradation. > >Bending over and taking it up the a** across all motherboards (which DES > >has forced on 5.4-RELEASE); makes the ASUS A8N-SLI Deluxe not "perfectly > >working". > > > > According to the APIC maintainer, and according to some quick benchmarks > myself, mixed mode has almost no performance impact. Maybe with the latest code - if you're talking about before the very recent jhb commits. Peter has said several times there is(was) a performance issue. 'mixed mode' also is (was?) expressly prohibited by the ACPI spec. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:24:35 2005 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 E40E716A4CE; Tue, 19 Apr 2005 18:24:34 +0000 (GMT) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1408543D3F; Tue, 19 Apr 2005 18:24:34 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [213.6.69.88] (A4558.a.pppool.de [213.6.69.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id CD17D300049A; Tue, 19 Apr 2005 20:24:30 +0200 (CEST) Message-ID: <42654CD8.9080509@mail.uni-mainz.de> Date: Tue, 19 Apr 2005 20:24:24 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-AT; rv:1.7.7) Gecko/20050416 X-Accept-Language: de-de, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050413210855.GA15088@bitsurf.net> <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <86ekdbdnqh.fsf@xps.des.no> <4260F103.5050309@mail.uni-mainz.de> <20050419173247.GB26152@dragon.NUXI.org> In-Reply-To: <20050419173247.GB26152@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 18:24:35 -0000 David O'Brien schrieb: >On Sat, Apr 16, 2005 at 01:03:31PM +0200, O. Hartmann wrote: > > >>I have ASUS A8N-SLI Deluxe mobo. BIOS revision is 1006. I have no >>problems with >>ACPI. APIC works with NO_MIXED_MODE commented out in kernel. >> >> > >Disable the NO_MIXED_MODE option is a performance degradation. >Bending over and taking it up the a** across all motherboards (which DES >has forced on 5.4-RELEASE); makes the ASUS A8N-SLI Deluxe not "perfectly >working". > > All right, this answeres an earlier question. Is it legitim to say 'it is not yet perfectly working' or is it a 'it will never perfectly work within the next time'? nForce4 chipset is new and I would not expect immediately support with an existing -RELEASE, but with a matured -STABLE as this will happen with the if_nve driver. >So yes people, you CAN get FreeBSD working on nForce-based motherboards. >BUT how much do you want to sacrifice?? Degradation performance, not >being able to use PowerNow!, not being able to use on-board NIC's, not >being able to use on-board sound, etc... Why go thru all this when there >is ZERO need to????????????? When one buys a motherboard, they have the >choice to pick a motherboard that won't cause you major pain. So why not >just do that?? > > In case I spend the money of my department and I'm in need of a instantly working system, I would do a deeper investigation in what kind of motherboard I'll buy and what motherboard will work with the preferred operating system. Then I may decide obtaining a still working and maybe 'mature' and therefore older mainboard. Otherwise, if it is not desireable building hand crafted servers, I would buy complete solutions and in Germany that means in most cases Linux. For my peronal use and for my science use, I can not buy new hardware within a short range of time, it's not affordable and therefore I would like to have a powerful solution I can get now and that means in many cases new mainboards with less support by actual operation systems of the OpenSource area. Well, this can't be the way if the motherboard is absolutely not working with the desired operating system, but in this case, the A8N-SLI Deluxe works great for me, not in strictu sensu, but in sense of what is possible at this stage of FreeBSD's development. My personal calculation is to get within the next two months a 'perfectly' working hardware with FreeBSD. This may be a faulty thaught ... I know this way isn't a very 'commercial' way, but it is my way of spending money in the future of a futureless object (in sense of the fast aging of hardware/technology). > > > >>The only point I would complain about is the still 'GENERIC' >>SATA150/SATA300 (switched back to UDMA33) >>controller of the nForce4 chipset, but as DES answered me on a prior >>posting this is due to a too fresh chipset. >> >> > >Another thing that isn't working for some nForce-based motherboards. >Why not buy hardware that is well supported by FreeBSD today? > > > Buying 'well supported' hardware NOW means buying hardware from yesterday and as I tried to explain above I do not have the money buying every year new hardware. nForce4-SLI based motherboards seem to me to have the best cost/technology ratio. And they outperform VIA based motherboards in some tests I read about. This in summa is the reason why I decided to buy a nForce4 based platform. The way of the common man and not that of the aces in OS development. O. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 18:25:09 2005 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 62D0516A4CE; Tue, 19 Apr 2005 18:25:09 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5AF643D1D; Tue, 19 Apr 2005 18:25:08 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.21] (rat.samsco.home [192.168.254.21]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3JIREDD083065; Tue, 19 Apr 2005 12:27:14 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42654CAA.10809@samsco.org> Date: Tue, 19 Apr 2005 12:23:38 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <200504131714.20356.jkim@niksun.com> <86fyxt1ovu.fsf@xps.des.no> <20050415005850.GB80903@dragon.NUXI.org> <2fd864e050414180911e4e5be@mail.gmail.com> <20050415211600.GA1473@dragon.NUXI.org> <1113603823.91832.7.camel@cream.xbsd.org> <86ekdbdnqh.fsf@xps.des.no> <4260F103.5050309@mail.uni-mainz.de> <20050419173247.GB26152@dragon.NUXI.org> <42654719.7030607@samsco.org> <20050419181831.GA27679@dragon.NUXI.org> In-Reply-To: <20050419181831.GA27679@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: "O. Hartmann" cc: freebsd-amd64@freebsd.org Subject: Re: Recommendations? 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, 19 Apr 2005 18:25:09 -0000 David O'Brien wrote: > On Tue, Apr 19, 2005 at 11:59:53AM -0600, Scott Long wrote: > >>David O'Brien wrote: >> >>>On Sat, Apr 16, 2005 at 01:03:31PM +0200, O. Hartmann wrote: >>> >>> >>>>I have ASUS A8N-SLI Deluxe mobo. BIOS revision is 1006. I have no >>>>problems with >>>>ACPI. APIC works with NO_MIXED_MODE commented out in kernel. >>> >>> >>>Disable the NO_MIXED_MODE option is a performance degradation. >>>Bending over and taking it up the a** across all motherboards (which DES >>>has forced on 5.4-RELEASE); makes the ASUS A8N-SLI Deluxe not "perfectly >>>working". >>> >> >>According to the APIC maintainer, and according to some quick benchmarks >>myself, mixed mode has almost no performance impact. > > > Maybe with the latest code - if you're talking about before the very > recent jhb commits. Peter has said several times there is(was) a > performance issue. 'mixed mode' also is (was?) expressly prohibited by > the ACPI spec. > Mixed mode had a performance impact back in the 5.1 or 5.2 timeframe when the PIC/APIC code wasn't abstracted like it is now. This applies to 5.3 and 5.4. 6.0 will of course be better since the factors that make mixed mode a consideration are now solved a different way. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:02:53 2005 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 1C1B416A4CE for ; Tue, 19 Apr 2005 20:02:53 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id A32E043D1D for ; Tue, 19 Apr 2005 20:02:50 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.149] (host-149.int.kcilink.com [192.168.7.149]) by yertle.kcilink.com (Postfix) with ESMTP id BB9FCB80D for ; Tue, 19 Apr 2005 16:02:49 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 19 Apr 2005 16:02:47 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.622) Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:02:53 -0000 On Apr 19, 2005, at 5:19 AM, David Komanek wrote: > Now I prefer: > Tyan Thunder K8WE, S2895A2NRF > 2x AMD Opteron 250 Box > Adaptec 2130SLP No experience with these; the LSI 320-2X has been extremely reliable for us. > 4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm If you can push yourself to 15kRPM drives, you'll be happier... > HP DLT 40/80 > 2x Gb LAN - I plan use the on-board ones Run away!!! Run away!!! Run from the onboard bge ethernet! Buy a nice intel dual gigabit ethernet card use that. turn off the bge via the bios. They will lock your system or cause other problems under heavy disk+network load. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:05:09 2005 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 7678016A4CE for ; Tue, 19 Apr 2005 20:05:09 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49D2543D4C for ; Tue, 19 Apr 2005 20:05:09 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.149] (host-149.int.kcilink.com [192.168.7.149]) by yertle.kcilink.com (Postfix) with ESMTP id DEE17B80D for ; Tue, 19 Apr 2005 16:05:08 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: <20050419150335.46904.qmail@web60003.mail.yahoo.com> References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4ca1c184ef042a708644d731f39d92e8@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 19 Apr 2005 16:05:07 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.622) Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:05:09 -0000 On Apr 19, 2005, at 11:03 AM, Tom Shafron wrote: > I haven't experienced problems with the onboard bge > NICs on my Tyan 2882... but now you have me nervous... > do you have a link to people discussing the issues > that I can check out? > See the thread "Tyan k8sr lockups" on this very list from earlier this month. You have to be doing *very* heavy network + very heavy disk i/o at the same time to cause instability. once I replaced it with an intel NIC it has been 100% stable (going on 2 weeks now and ever increasing load) From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:17:09 2005 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 E193216A4CE for ; Tue, 19 Apr 2005 20:17:09 +0000 (GMT) Received: from web60007.mail.yahoo.com (web60007.mail.yahoo.com [216.109.116.245]) by mx1.FreeBSD.org (Postfix) with SMTP id 383A843D60 for ; Tue, 19 Apr 2005 20:17:09 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 59551 invoked by uid 60001); 19 Apr 2005 20:17:08 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=gmgjkhLLmvZOsohhq2nG6CfX/RoG9E0vFAQ+qThtLt7daXq8fQWkxSTh3TEMFud44KhxdaUalo3hMC+iQaXwKh/3i5nyRwdCxDERkQ4j0u0xmWVJ8p+isbRfKGnlvkPlz0QLnw7ZrMu4JaI6oZWyZ6QDcgX9digjVOGH0nfC5NA= ; Message-ID: <20050419201708.59549.qmail@web60007.mail.yahoo.com> Received: from [65.10.4.147] by web60007.mail.yahoo.com via HTTP; Tue, 19 Apr 2005 13:17:08 PDT Date: Tue, 19 Apr 2005 13:17:08 -0700 (PDT) From: Tom Shafron To: Vivek Khera , freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:17:10 -0000 --- Vivek Khera wrote: > > On Apr 19, 2005, at 11:03 AM, Tom Shafron wrote: > > > I haven't experienced problems with the onboard > bge > > NICs on my Tyan 2882... but now you have me > nervous... > > do you have a link to people discussing the issues > > that I can check out? > > > > See the thread "Tyan k8sr lockups" on this very list > from earlier this > month. You have to be doing *very* heavy network + > very heavy disk i/o > at the same time to cause instability. once I > replaced it with an > intel NIC it has been 100% stable (going on 2 weeks > now and ever > increasing load) > What do you consider very heavy load in Mb/s for both network and disk IO traffic? I'd like to bring it up to that level and test how it handles it... __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:19:36 2005 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 288DC16A4CE for ; Tue, 19 Apr 2005 20:19:36 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 465F543D53 for ; Tue, 19 Apr 2005 20:19:35 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@localhost [127.0.0.1]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j3JKOJwj068778; Tue, 19 Apr 2005 16:24:20 -0400 (EDT) (envelope-from ketrien@error404.nls.net) Received: (from ketrien@localhost)j3JKOJOF068777; Tue, 19 Apr 2005 16:24:19 -0400 (EDT) (envelope-from ketrien) Date: Tue, 19 Apr 2005 16:24:19 -0400 From: "Ketrien I. Saihr-Kesenchedra" To: Vivek Khera Message-ID: <20050419202419.GB63598@bahre.achedra.org> Mail-Followup-To: Vivek Khera , freebsd-amd64@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.83/841/Tue Apr 19 12:44:10 2005 on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:19:36 -0000 On Tue, Apr 19, 2005 at 04:02:47PM -0400, Vivek Khera wrote: > > On Apr 19, 2005, at 5:19 AM, David Komanek wrote: > > >Now I prefer: > >Tyan Thunder K8WE, S2895A2NRF > >2x AMD Opteron 250 Box > >Adaptec 2130SLP I missed the start of this thread. Whoops! First of all, don't use the K8WE. Use either the K8SPro or K8SR. The K8SR is very picky about risers, though, so I generally recommend the K8SPro. Honestly, Tyan is not my first choice either. The Iwill DK8S/DK8S2 is better on paper, but I've never been able to find one. > No experience with these; the LSI 320-2X has been extremely reliable > for us. The Adaptec 2130SLP is a big no-no. The driver is not 64-bit clean last I looked. Skip the onboard SCSI and spend the money on an LSI 320-2 or 320-2X. > >4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm > If you can push yourself to 15kRPM drives, you'll be happier... You'll also have heat concerns; case is going to be very important. Generico 4U is not going to cut it, nor will Chenbro. (Major SCSI backplane issues. Not even remotely within specs.) Plus, I believe Hitachi's discontinued the 10K174 line. Definitely go for the 15K's. > Run away!!! Run away!!! Run from the onboard bge ethernet! Buy a nice > intel dual gigabit ethernet card use that. turn off the bge via the > bios. They will lock your system or cause other problems under heavy > disk+network load. Because Tyan clogged the PCI-X bus, the bge can act up in certain situations. I haven't had time+resources to test complaints about bge+320-2X's locking up, but I would bet money that if you took PCIX A down to 100MHz by jumper, it'd at least happen far less frequently. The other complaints, well, I can't find any real merit in them. A K8SPro w/320-2 using the onboard bge has exhibited zero problems under extreme loads. If you're going to be subjecting the box to load with a 320-2X, you'll likely have to put the 320-2X on PCIX B at 66MHz to get it stable. Or get an Iwill. This isn't the first time Tyan's had PCI timing issues, and I'm sure it won't be the last. -ksaihr From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:30:15 2005 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 734C816A4CE for ; Tue, 19 Apr 2005 20:30:15 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF62D43D53 for ; Tue, 19 Apr 2005 20:30:14 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 2D26BF7B1 for ; Tue, 19 Apr 2005 14:30:14 -0600 (MDT) Date: Tue, 19 Apr 2005 14:30:13 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050419143013.47a457ff.kgunders@teamcool.net> In-Reply-To: <4ca1c184ef042a708644d731f39d92e8@khera.org> References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> <4ca1c184ef042a708644d731f39d92e8@khera.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:30:15 -0000 On Tue, 19 Apr 2005 16:05:07 -0400 Vivek Khera wrote: > > On Apr 19, 2005, at 11:03 AM, Tom Shafron wrote: > > > I haven't experienced problems with the onboard bge > > NICs on my Tyan 2882... but now you have me nervous... > > do you have a link to people discussing the issues > > that I can check out? > > > > See the thread "Tyan k8sr lockups" on this very list from earlier this > month. You have to be doing *very* heavy network + very heavy disk i/o > at the same time to cause instability. once I replaced it with an > intel NIC it has been 100% stable (going on 2 weeks now and ever > increasing load) Vivek, could you provide a quick recap? I can't recall if this was a FBSD driver issue or a HW issue w/Tyan? In either case, I assume time should result in a fix? The K8S Pro has a 3rd LAN- good old 10/100. Does anyone know if it's using the same or different driver? My guess would be that it's different and hence should work. If so, a bit of patience should remove immediate need for Intel nics. TIA- -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:41:36 2005 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 1D31016A4CE for ; Tue, 19 Apr 2005 20:41:36 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D41243D39 for ; Tue, 19 Apr 2005 20:41:35 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@localhost [127.0.0.1]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j3JKkKHt068858; Tue, 19 Apr 2005 16:46:20 -0400 (EDT) (envelope-from ketrien@error404.nls.net) Received: (from ketrien@localhost)j3JKkKtI068857; Tue, 19 Apr 2005 16:46:20 -0400 (EDT) (envelope-from ketrien) Date: Tue, 19 Apr 2005 16:46:20 -0400 From: "Ketrien I. Saihr-Kesenchedra" To: Ken Gunderson Message-ID: <20050419204620.GC63598@bahre.achedra.org> Mail-Followup-To: Ken Gunderson , freebsd-amd64@freebsd.org References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> <4ca1c184ef042a708644d731f39d92e8@khera.org> <20050419143013.47a457ff.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419143013.47a457ff.kgunders@teamcool.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.83/841/Tue Apr 19 12:44:10 2005 on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:41:36 -0000 On Tue, Apr 19, 2005 at 02:30:13PM -0600, Ken Gunderson wrote: > The K8S Pro has a 3rd LAN- good old 10/100. Does anyone know if it's > using the same or different driver? My guess would be that it's > different and hence should work. If so, a bit of patience should > remove immediate need for Intel nics. The 10/100 is an i82559 IIRC, using fxp(4). Might be a 558 though. -ksaihr From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:43:25 2005 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 0B3BE16A4CE for ; Tue, 19 Apr 2005 20:43:25 +0000 (GMT) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B34B943D31 for ; Tue, 19 Apr 2005 20:43:24 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [IPv6:2001:960:301:3:a00:20ff:fe85:fa39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id 4D7EB3F294; Tue, 19 Apr 2005 22:43:23 +0200 (CEST) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 53014192; Tue, 19 Apr 2005 22:43:23 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 4793D127; Tue, 19 Apr 2005 22:43:23 +0200 (CEST) Date: Tue, 19 Apr 2005 22:43:23 +0200 (CEST) From: Sten Spans To: Vivek Khera In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:43:25 -0000 On Tue, 19 Apr 2005, Vivek Khera wrote: > > On Apr 19, 2005, at 5:19 AM, David Komanek wrote: > >> Now I prefer: >> Tyan Thunder K8WE, S2895A2NRF >> 2x AMD Opteron 250 Box >> Adaptec 2130SLP > >> HP DLT 40/80 >> 2x Gb LAN - I plan use the on-board ones > > Run away!!! Run away!!! Run from the onboard bge ethernet! Buy a nice intel > dual gigabit ethernet card use that. turn off the bge via the bios. They > will lock your system or cause other problems under heavy disk+network load. K8WE is an nforce4 motherboard, it has nvidia ethernet onboard, not broadcom..... It seems to confuse people who haven't noticed the switch to nforce4 for pci-e support that tyan has made with it's two latest opteron motherboards. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 20:47:15 2005 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 1F48616A4CE for ; Tue, 19 Apr 2005 20:47:15 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id D733843D49 for ; Tue, 19 Apr 2005 20:47:14 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.149] (host-149.int.kcilink.com [192.168.7.149]) by yertle.kcilink.com (Postfix) with ESMTP id 71F66B80D for ; Tue, 19 Apr 2005 16:47:14 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: <20050419201708.59549.qmail@web60007.mail.yahoo.com> References: <20050419201708.59549.qmail@web60007.mail.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Tue, 19 Apr 2005 16:47:12 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.622) Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 20:47:15 -0000 On Apr 19, 2005, at 4:17 PM, Tom Shafron wrote: >> at the same time to cause instability. once I >> replaced it with an >> intel NIC it has been 100% stable (going on 2 weeks >> now and ever >> increasing load) >> > > What do you consider very heavy load in Mb/s for both > network and disk IO traffic? I'd like to bring it up > to that level and test how it handles it... > > not so much sure on the exact numbers, but the database is postgres and it was running some large reports that scanned across many multi-gigabyte tables, at the same time running a pg_dump (backup) across the ethernet to another box on the LAN, and at the same time keeping itself up-to-date using the slony replication engine for postgres. the reports were being run on a remote machine. the only processes running on this box other than the base system stuff (ssh, etc.) is postgres. From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 21:19:01 2005 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 D1F7716A4CE for ; Tue, 19 Apr 2005 21:19:01 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5542543D1F for ; Tue, 19 Apr 2005 21:19:01 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 89476F7B6 for ; Tue, 19 Apr 2005 15:19:00 -0600 (MDT) Date: Tue, 19 Apr 2005 15:19:00 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050419151900.29d0ee57.kgunders@teamcool.net> In-Reply-To: <20050419202419.GB63598@bahre.achedra.org> References: <20050419202419.GB63598@bahre.achedra.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 21:19:02 -0000 On Tue, 19 Apr 2005 16:24:19 -0400 "Ketrien I. Saihr-Kesenchedra" wrote: > On Tue, Apr 19, 2005 at 04:02:47PM -0400, Vivek Khera wrote: > > > > On Apr 19, 2005, at 5:19 AM, David Komanek wrote: > > > > >Now I prefer: > > >Tyan Thunder K8WE, S2895A2NRF > > >2x AMD Opteron 250 Box > > >Adaptec 2130SLP > > I missed the start of this thread. Whoops! > First of all, don't use the K8WE. Use either the K8SPro or K8SR. The K8SR is > very picky about risers, though, so I generally recommend the K8SPro. Honestly, > Tyan is not my first choice either. The Iwill DK8S/DK8S2 is better on paper, > but I've never been able to find one. > > > No experience with these; the LSI 320-2X has been extremely reliable > > for us. > > The Adaptec 2130SLP is a big no-no. The driver is not 64-bit clean last I > looked. Skip the onboard SCSI and spend the money on an LSI 320-2 or 320-2X. > > > >4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm > > If you can push yourself to 15kRPM drives, you'll be happier... I loved IBM drives years ago, but started having too many issues when they started cutting a few too many coreners. The things just started dying prematurely. Hitachi drives also have a fairly bad rep amongst serveral consultants I know. > You'll also have heat concerns; case is going to be very important. Generico > 4U is not going to cut it, nor will Chenbro. (Major SCSI backplane issues. > Not even remotely within specs.) Plus, I believe Hitachi's discontinued the > 10K174 line. Definitely go for the 15K's. > > > Run away!!! Run away!!! Run from the onboard bge ethernet! Buy a nice > > intel dual gigabit ethernet card use that. turn off the bge via the > > bios. They will lock your system or cause other problems under heavy > > disk+network load. > > Because Tyan clogged the PCI-X bus, the bge can act up in certain situations. > I haven't had time+resources to test complaints about bge+320-2X's locking up, > but I would bet money that if you took PCIX A down to 100MHz by jumper, it'd > at least happen far less frequently. The other complaints, well, I can't find > any real merit in them. A K8SPro w/320-2 using the onboard bge has exhibited > zero problems under extreme loads. If you're going to be subjecting the box > to load with a 320-2X, you'll likely have to put the 320-2X on PCIX B at 66MHz > to get it stable. Or get an Iwill. This isn't the first time Tyan's had PCI > timing issues, and I'm sure it won't be the last. To summarize, for the K8S Pro, it seems your suggestion would be to stay away from the pci- x adapters all together?? Which leaves something like the Adaptec 2120 or the LSI 320-1LP (for a 2U rackmount system). Can anyone give me some guidance if either of these has advantages/ disadvantages under fbsd amd64? Thanks for your insights. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 21:39:31 2005 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 72C9716A4CE for ; Tue, 19 Apr 2005 21:39:31 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BEE443D3F for ; Tue, 19 Apr 2005 21:39:30 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@localhost [127.0.0.1]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j3JLiFdN069056; Tue, 19 Apr 2005 17:44:15 -0400 (EDT) (envelope-from ketrien@error404.nls.net) Received: (from ketrien@localhost)j3JLiENT069055; Tue, 19 Apr 2005 17:44:14 -0400 (EDT) (envelope-from ketrien) Date: Tue, 19 Apr 2005 17:44:14 -0400 From: "Ketrien I. Saihr-Kesenchedra" To: Ken Gunderson Message-ID: <20050419214414.GD63598@bahre.achedra.org> Mail-Followup-To: Ken Gunderson , freebsd-amd64@freebsd.org References: <20050419202419.GB63598@bahre.achedra.org> <20050419151900.29d0ee57.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419151900.29d0ee57.kgunders@teamcool.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.83/841/Tue Apr 19 12:44:10 2005 on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 21:39:31 -0000 On Tue, Apr 19, 2005 at 03:19:00PM -0600, Ken Gunderson wrote: > I loved IBM drives years ago, but started having too many issues when > they started cutting a few too many coreners. The things just started > dying prematurely. Hitachi drives also have a fairly bad rep amongst > serveral consultants I know. I'm reminded of a Demotivators poster; "There's good money to be made in prolonging the problem," to paraphrase slightly. e.g., yes, I'm calling them out. Observed and demonstrated statistical failure rates on the Hitachi 10K174 and 15K73 line are typically lower than Seagate and Fujitsu. Except when you get some kid slapping parts together and calling it a box. At which point, all failure rates go out the door, because the whole thing is a ticking time bomb. > To summarize, for the K8S Pro, it seems your suggestion would be to stay > away from the pci- x adapters all together?? Which leaves something > like the Adaptec 2120 or the LSI 320-1LP (for a 2U rackmount system). > Can anyone give me some guidance if either of these has advantages/ > disadvantages under fbsd amd64? No, PCI-X adapters on the A (133MHz) bus, which is where Tyan jammed all the onboard peripherals. This creates major timing migraines, especially at a 133MHz clock. The B bus (66MHz) does not have this problem, which leaves you with anything that can downclock to 66MHz. If it's PCI-X compliant, it can downclock to 66MHz. Hell, the Ultra320-2X can step down to PCI32/33. (I've actually done this for testing.) The catch is that you lose the bus bandwidth you may need for extremely intensive disk I/O. Of course, you really aren't going to be in any trouble until you get up into 1Gbit-2Gbit FC-AL. The 320-2 here does over 100MB/s read and 100MB/s write on 15K73's with RAID1. If you need more than that, you should probably start looking at an Iwill H8501 and it's triple 8131 setup. As far as advantages/disadvantages - last I'd heard, aac(4) is not 64-bit clean, nor is asr(4). Which means you aren't going to be running them on amd64. amr(4) is 64bit clean and >4GB safe, so really, it's the only choice. Well, besides Qlogic FC (isp(4)), but I don't know if anyone's even tested that. -ksaihr From owner-freebsd-amd64@FreeBSD.ORG Tue Apr 19 23:29:06 2005 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 8972416A4CE for ; Tue, 19 Apr 2005 23:29:06 +0000 (GMT) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4A6243D3F for ; Tue, 19 Apr 2005 23:29:05 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.3/8.13.1) with ESMTP id j3JNT3ZE068633; Tue, 19 Apr 2005 16:29:03 -0700 (PDT) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.3/8.13.1/Submit) id j3JNSwQt068632; Tue, 19 Apr 2005 16:28:58 -0700 (PDT) (envelope-from dg@dglawrence.com) Date: Tue, 19 Apr 2005 16:28:58 -0700 From: "David G. Lawrence" To: Ken Gunderson Message-ID: <20050419232858.GN31779@opteron.dglawrence.com> References: <20050419202419.GB63598@bahre.achedra.org> <20050419151900.29d0ee57.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050419151900.29d0ee57.kgunders@teamcool.net> cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 19 Apr 2005 23:29:06 -0000 > > > >4x Hitachi 3.5" 73.4 GB (SCSI Ultra 320),10 000 rpm > > > If you can push yourself to 15kRPM drives, you'll be happier... > > I loved IBM drives years ago, but started having too many issues when > they started cutting a few too many coreners. The things just started > dying prematurely. Hitachi drives also have a fairly bad rep amongst > serveral consultants I know. Tha Hitachi/IBM 7k250 and 7k400 series SATA drives have been working quite well. Very low failure rate and performance is quite good. I have no experience with their recent SCSI drives, however. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 20 06:54:49 2005 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 C89F916A4CE for ; Wed, 20 Apr 2005 06:54:49 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A45F43D31 for ; Wed, 20 Apr 2005 06:54:49 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 804B42A8F6 for ; Tue, 19 Apr 2005 23:54:49 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 2F093E2B3 for ; Tue, 19 Apr 2005 23:54:49 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id j3K6so7W035047; Tue, 19 Apr 2005 23:54:50 -0700 (PDT) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id j3K6sdrx035046; Tue, 19 Apr 2005 23:54:39 -0700 (PDT) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 19 Apr 2005 23:54:39 -0700 User-Agent: KMail/1.7.1 References: <20050416093349.I5888@epsplex.bde.org> <8664yndm6v.fsf@xps.des.no> In-Reply-To: <8664yndm6v.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200504192354.39601.peter@wemm.org> Subject: Re: INCLUDE_CONFIG_FILE broken? 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, 20 Apr 2005 06:54:49 -0000 On Saturday 16 April 2005 03:56 am, Dag-Erling Sm=F8rgrav wrote: > Bruce Evans writes: > > You could just use the existing mechanism __IDSTRING(), preferably > > after fixing it to actually work. (__IDSTRING() generates invalid > > asm if the string has a newline in it. Among other bugs, this > > breaks most uses of __COPYRIGHT().) > > __IDSTRING() places the string in a separate section. By default, > strings(1) only extracts strings from code and data sections, so the > good old 'strings -n 3 kernel | grep \^___' wouldn't work. Not a big > deal, but still a slight POLA breach. True, but 'strings -a' will do the entire file... Or we can do what linux does and insert things into any section we like=20 by using the gas .incbin "filename" construct. I'm not sure if I like that any more than using objcopy to=20 insert a section. =2D-=20 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 Wed Apr 20 13:43:22 2005 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 2AB8C16A4FC for ; Wed, 20 Apr 2005 13:43:22 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id B645743D31 for ; Wed, 20 Apr 2005 13:43:21 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 07899B80D for ; Wed, 20 Apr 2005 09:43:21 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: <20050419143013.47a457ff.kgunders@teamcool.net> References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> <4ca1c184ef042a708644d731f39d92e8@khera.org> <20050419143013.47a457ff.kgunders@teamcool.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0a5e514d6f3a98f9ec88fe21538aec4f@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Wed, 20 Apr 2005 09:43:20 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.622) Subject: Re: designing new freebsd server for amd64 arch 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, 20 Apr 2005 13:43:22 -0000 On Apr 19, 2005, at 4:30 PM, Ken Gunderson wrote: > Vivek, could you provide a quick recap? I can't recall if this was a > FBSD driver issue or a HW issue w/Tyan? In either case, I assume > time should result in a fix? > Undetermined. There was report of a PCI bus timing error on older K8SR boards, but Tyan says those were corrected on or after Rev C. My board is Rev E. For all I know plugging in the NIC into the other PCI bus (the onboard is on one bus, the new one is on the same bus as the LSI RAID card) changed whatever timing problem might have been causing the error. But at this point, to quote an old professor of mine, "I don't know, and I don't care" :-( Vivek Khera, Ph.D. +1-301-869-4449 x806 From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 20 13:51:40 2005 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 BD24916A4CE for ; Wed, 20 Apr 2005 13:51:40 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EC6E43D46 for ; Wed, 20 Apr 2005 13:51:38 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3KDrWsJ088335; Wed, 20 Apr 2005 07:53:33 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42665D9F.1080605@samsco.org> Date: Wed, 20 Apr 2005 07:48:15 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ketrien I. Saihr-Kesenchedra" References: <20050419202419.GB63598@bahre.achedra.org> In-Reply-To: <20050419202419.GB63598@bahre.achedra.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch 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, 20 Apr 2005 13:51:40 -0000 Ketrien I. Saihr-Kesenchedra wrote: > On Tue, Apr 19, 2005 at 04:02:47PM -0400, Vivek Khera wrote: > >>On Apr 19, 2005, at 5:19 AM, David Komanek wrote: >> >> >>>Now I prefer: >>>Tyan Thunder K8WE, S2895A2NRF >>>2x AMD Opteron 250 Box >>>Adaptec 2130SLP > > > I missed the start of this thread. Whoops! > First of all, don't use the K8WE. Use either the K8SPro or K8SR. The K8SR is > very picky about risers, though, so I generally recommend the K8SPro. Honestly, > Tyan is not my first choice either. The Iwill DK8S/DK8S2 is better on paper, > but I've never been able to find one. > > >>No experience with these; the LSI 320-2X has been extremely reliable >>for us. > > > The Adaptec 2130SLP is a big no-no. The driver is not 64-bit clean last I > looked. > This is absolutely false. Please stop spreading this complete rubbish. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 20 15:34:10 2005 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 641BC16A4CF for ; Wed, 20 Apr 2005 15:34:10 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6DB443D48 for ; Wed, 20 Apr 2005 15:34:09 +0000 (GMT) (envelope-from bsdfreak@gmail.com) Received: by zproxy.gmail.com with SMTP id 34so311367nzf for ; Wed, 20 Apr 2005 08:34:09 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a8Q+pIODjym9I5f3OV+2Fpf1PxW/ATjkk0lZWJdzGgs6nCJDGJC1TdqJHJ+evF8vyE+FgsFWAK616tSKH3lUyUj8jjEuiJh9aTIeWBX0nCvUc2qAyDlK9PLaPL+tq/iyN3XEn7z2DGj1FkrjlBpIw9KSe/rqxF1ZAI7PCpEwIUg= Received: by 10.36.12.2 with SMTP id 2mr96088nzl; Wed, 20 Apr 2005 08:34:09 -0700 (PDT) Received: by 10.36.7.11 with HTTP; Wed, 20 Apr 2005 08:34:09 -0700 (PDT) Message-ID: Date: Wed, 20 Apr 2005 11:34:09 -0400 From: Alexander Chamandy To: Mikhail Teterin In-Reply-To: <200504171905.j3HJ50jK096698@corbulon.video-collage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200504171905.j3HJ50jK096698@corbulon.video-collage.com> cc: Q cc: freebsd-amd64@freebsd.org cc: Mikhail Teterin cc: net@freebsd.org Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alexander Chamandy List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 15:34:10 -0000 > The latest version from Q's site works (!), but seems limited to > 100baseTX full-duplex. Even at that nominal speed, the actual data > transfers seem limited to 2-3 megabytes/s with occasional latency-spikes > :-( I just tried the one from Q's site on my Asus K8NNXP nForce MCP3 Networking Adapter (RTL8201L) and it seems to peak at about 7-8MB/s.=20 I haven't had any latency problems.. perhaps this issue is isolated to a certain network adapter? =20 > I'll try to back-port if_nve manually and see, what happens. Let me know, I'd be interested to try it. >=20 > -mi >=20 --=20 Best wishes, Alexander G. Chamandy Webmaster www.bsdfreak.org Your Source For BSD News! From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 20 16:38:39 2005 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 EC72916A4CE for ; Wed, 20 Apr 2005 16:38:39 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D1A143D4C for ; Wed, 20 Apr 2005 16:38:39 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 843CCF7B1 for ; Wed, 20 Apr 2005 10:38:38 -0600 (MDT) Date: Wed, 20 Apr 2005 10:38:38 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050420103838.1b7c4ee7.kgunders@teamcool.net> In-Reply-To: <42665D9F.1080605@samsco.org> References: <20050419202419.GB63598@bahre.achedra.org> <42665D9F.1080605@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: designing new freebsd server for amd64 arch 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, 20 Apr 2005 16:38:40 -0000 On Wed, 20 Apr 2005 07:48:15 -0600 Scott Long wrote: > Ketrien I. Saihr-Kesenchedra wrote: > > On Tue, Apr 19, 2005 at 04:02:47PM -0400, Vivek Khera wrote: > > > >>On Apr 19, 2005, at 5:19 AM, David Komanek wrote: > >> > >> > >>>Now I prefer: > >>>Tyan Thunder K8WE, S2895A2NRF > >>>2x AMD Opteron 250 Box > >>>Adaptec 2130SLP > > > > > > I missed the start of this thread. Whoops! > > First of all, don't use the K8WE. Use either the K8SPro or K8SR. The K8SR is > > very picky about risers, though, so I generally recommend the K8SPro. Honestly, > > Tyan is not my first choice either. The Iwill DK8S/DK8S2 is better on paper, > > but I've never been able to find one. > > > > > >>No experience with these; the LSI 320-2X has been extremely reliable > >>for us. > > > > > > The Adaptec 2130SLP is a big no-no. The driver is not 64-bit clean last I > > looked. > > > > This is absolutely false. Please stop spreading this complete rubbish. >From what I've been able to discern from the archives, it appears the LSI 320 cards are more popular on amd64... Does anyone have experience with the 2130SLP (and/or it's pci counterparts, e.g. the 2120) under amd64, and if so, can you share your experiences, positive or negative? I'm leaning towards the LSI, but my distributor stocks the Adaptecs and all other things being equal it's easier to get everything from under one roof... Thanks for your input;) -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 20 19:04:15 2005 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 89E2F16A4CE; Wed, 20 Apr 2005 19:04:15 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE9B143D53; Wed, 20 Apr 2005 19:04:13 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3KJ4Amq060621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 20 Apr 2005 15:04:11 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11])j3KJ43EG089812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Apr 2005 15:04:04 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.3/8.13.3) with ESMTP id j3KJ3wWo001460; Wed, 20 Apr 2005 15:03:58 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.3/8.13.3/Submit) id j3KJ3v2W001459; Wed, 20 Apr 2005 15:03:57 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Alexander Chamandy Date: Wed, 20 Apr 2005 15:03:57 -0400 User-Agent: KMail/1.7.2 References: <200504171905.j3HJ50jK096698@corbulon.video-collage.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_deqZCNLEC5P7dWN" Message-Id: <200504201503.57630.mi+mx@aldan.algebra.com> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: Q cc: freebsd-amd64@freebsd.org cc: net@freebsd.org Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 19:04:15 -0000 --Boundary-00=_deqZCNLEC5P7dWN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline > > The latest version from Q's site works (!), but seems limited to > > 100baseTX full-duplex. Even at that nominal speed, the actual data > > transfers seem limited to 2-3 megabytes/s with occasional latency-spikes > > > > :-( > I just tried the one from Q's site on my Asus K8NNXP nForce MCP3 > Networking Adapter (RTL8201L) and it seems to peak at about 7-8MB/s. > I haven't had any latency problems.. perhaps this issue is isolated to > a certain network adapter? > > > I'll try to back-port if_nve manually and see, what happens. Well, simply checking out sys/dev/nve, sys/contrib/dev/nve, and sys/modules/nve allowed me to build the if_nve module. Loading if_nve.ko attaches to the interface, but attempts to ifconfig it result in instant panic (page fault). I'm going to guess, there is some assumption the driver makes, that is true on 6.0, but on 5.x So I'm back to net/nvnet's if_nv.ko, which is limping along... nv0: port 0xac00-0xac07 mem 0xff2fe000-0xff2fefff irq 22 at device 5.0 on pci0 nv0: Ethernet address 00:d0:68:06:d8:c0 miibus0: on nv0 My motherboard is IWill's DK8N -- dmesg attached. -mi --Boundary-00=_deqZCNLEC5P7dWN Content-Type: text/plain; charset="iso-8859-1"; name="pandora.dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pandora.dmesg" Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RC2 #0: Sun Apr 10 04:02:23 UTC 2005 root@portnoy.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 244 (1800.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2146697216 (2047 MB) avail memory = 2060873728 (1965 MB) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 ACPI link \\_SB_.LUS0 has invalid initial irq 10, ignoring ACPI link \\_SB_.LKLN has invalid initial irq 5, ignoring ACPI link \\_SB_.LUS1 has invalid initial irq 11, ignoring ACPI link \\_SB_.LUS2 has invalid initial irq 7, ignoring ACPI link \\_SB_.LNKE has invalid initial irq 11, ignoring ACPI link \\_SB_.LNKB has invalid initial irq 10, ignoring ACPI link \\_SB_.LTIE has invalid initial irq 10, ignoring pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xff2fb000-0xff2fbfff irq 22 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xff2fc000-0xff2fcfff irq 21 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered pci0: at device 2.2 (no driver attached) nv0: port 0xac00-0xac07 mem 0xff2fe000-0xff2fefff irq 22 at device 5.0 on pci0 nv0: Ethernet address 00:d0:68:06:d8:c0 miibus0: on nv0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nv0: Ethernet address: 00:d0:68:06:d8:c0 pci0: at device 6.0 (no driver attached) atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xbc00-0xbc0f,0xc000-0xc003,0xc400-0xc407,0xc800-0xc803,0xcc00-0xcc07 irq 21 at device 10.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib1: at device 11.0 on pci0 pci2: on pcib1 pci2: at device 0.0 (no driver attached) pcib2: at device 14.0 on pci0 ACPI link \\_SB_.LNKD has invalid initial irq 10, ignoring ACPI link \\_SB_.LNKC has invalid initial irq 10, ignoring pci1: on pcib2 fwohci0: mem 0xff0f8000-0xff0fbfff,0xff0ff800-0xff0fffff irq 18 at device 6.0 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:00:00:00:01:46:87 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:01:46:87 fwe0: Ethernet address: 02:00:00:01:46:87 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib3: on acpi0 pci3: on pcib3 pcib4: at device 1.0 on pci3 pci5: on pcib4 atapci2: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 mem 0xff5ffc00-0xff5fffff irq 27 at device 3.0 on pci5 ata4: channel #0 on atapci2 ata5: channel #1 on atapci2 ata6: channel #2 on atapci2 ata7: channel #3 on atapci2 pci3: at device 1.1 (no driver attached) pcib5: at device 2.0 on pci3 pci4: on pcib5 amr0: mem 0xfeaf0000-0xfeafffff irq 29 at device 1.0 on pci4 amr0: Firmware 712T, BIOS G116, 64MB RAM pci3: at device 2.1 (no driver attached) acpi_button0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: at iomem 0xc8800-0xccfff,0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1800006080 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master PIO4 ad4: 190782MB [387621/16/63] at ata2-master UDMA33 ad8: 190782MB [387621/16/63] at ata4-master SATA150 amrd0: on amr0 amrd0: 953885MB (1953556480 sectors) RAID 5 (optimal) Mounting root from ufs:/dev/ad8s2a --Boundary-00=_deqZCNLEC5P7dWN-- From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 07:57:55 2005 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 4870B16A4CE for ; Thu, 21 Apr 2005 07:57:55 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 019D843D2D for ; Thu, 21 Apr 2005 07:57:55 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DOWZO-000JZ6-5f for freebsd-amd64@freebsd.org; Thu, 21 Apr 2005 10:57:54 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Apr 2005 10:57:54 +0300 From: Danny Braniss Message-ID: Subject: Noisy SunFire 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, 21 Apr 2005 07:57:55 -0000 hi, does anyone know how to lower the fan speed of this U1? it's a dual opteron running 5.4 but far away from me :-) danny From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 08:47:08 2005 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 CFE7D16A4CE for ; Thu, 21 Apr 2005 08:47:08 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F95643D5A for ; Thu, 21 Apr 2005 08:47:08 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DOXL1-000KTA-BL; Thu, 21 Apr 2005 11:47:07 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Kris Kennaway In-Reply-To: Message from Kris Kennaway <20050330144447.GA83108@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Apr 2005 11:47:07 +0300 From: Danny Braniss Message-ID: cc: freebsd-amd64@freebsd.org Subject: Re: panic: userret: Returning with 1 locks held. 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, 21 Apr 2005 08:47:08 -0000 with the latest kernel, the message changed somewhat, but the panic is still there (this is an amd64): trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff8038e3f5 stack pointer = 0x10:0xffffffffb280e7b0 frame pointer = 0x10:0xffffffffb280e7e0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 241 (sh) [thread pid 241 tid 100071 ] Stopped at _mtx_lock_flags+0x35: cmpq $0x80779d40,0(%rdi) db> tr Tracing pid 241 tid 100071 td 0xffffff007ae25980 _mtx_lock_flags() at _mtx_lock_flags+0x35 exec_map_first_page() at exec_map_first_page+0x60 kern_execve() at kern_execve+0x2a0 execve() at execve+0x5d syscall() at syscall+0x4ab Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090630c, rsp = 0x7fffffffcbf8, rbp = 0 --- db> show lockedvnods Locked vnodes 0xffffff0061a48000: tag union, type VREG usecount 1, writecount 0, refcount 1 mountedhere 0 flags (VV_TEXT) lock type union: EXCL (count 1) by thread 0xffffff007ae25980 (pid 241) vp=0xffffff0061a48000, uppervp=0, lowervp=0xffffff00626187e0 union: lower 0xffffff00626187e0: tag nfs, type VREG usecount 1, writecount 0, refcount 3 mountedhere 0 flags () v_object 0xffffff007c3a87e0 ref 0 pages 1 fileid 47269 fsid 0x900ff01 db> tr 241 Tracing pid 241 tid 100071 td 0xffffff007ae25980 _mtx_lock_flags() at _mtx_lock_flags+0x35 exec_map_first_page() at exec_map_first_page+0x60 kern_execve() at kern_execve+0x2a0 execve() at execve+0x5d syscall() at syscall+0x4ab Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090630c, rsp = 0x7fffffffcbf8, rbp = 0 --- db> From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 09:23:46 2005 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 7DFB716A4CE for ; Thu, 21 Apr 2005 09:23:46 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 297BC43D1F for ; Thu, 21 Apr 2005 09:23:46 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DOXuS-000LIN-LZ; Thu, 21 Apr 2005 12:23:44 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Danny Braniss In-Reply-To: Message from Danny Braniss Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Apr 2005 12:23:44 +0300 From: Danny Braniss Message-ID: cc: freebsd-amd64@freebsd.org cc: Kris Kennaway Subject: Re: panic: userret: Returning with 1 locks held. 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, 21 Apr 2005 09:23:46 -0000 > with the latest kernel, the message changed somewhat, but the panic is > still there (this is an amd64): > > trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff8038e3f5 > stack pointer = 0x10:0xffffffffb280e7b0 > frame pointer = 0x10:0xffffffffb280e7e0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 241 (sh) > [thread pid 241 tid 100071 ] > Stopped at _mtx_lock_flags+0x35: cmpq $0x80779d40,0(%rdi) > db> tr > Tracing pid 241 tid 100071 td 0xffffff007ae25980 > _mtx_lock_flags() at _mtx_lock_flags+0x35 > exec_map_first_page() at exec_map_first_page+0x60 > kern_execve() at kern_execve+0x2a0 > execve() at execve+0x5d > syscall() at syscall+0x4ab > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090630c, rsp = > 0x7fffffffcbf8, rbp = 0 --- > db> show lockedvnods > Locked vnodes > > 0xffffff0061a48000: tag union, type VREG > usecount 1, writecount 0, refcount 1 mountedhere 0 > flags (VV_TEXT) > lock type union: EXCL (count 1) by thread 0xffffff007ae25980 (pid 241) > vp=0xffffff0061a48000, uppervp=0, lowervp=0xffffff00626187e0 > union: lower > 0xffffff00626187e0: tag nfs, type VREG > usecount 1, writecount 0, refcount 3 mountedhere 0 > flags () > v_object 0xffffff007c3a87e0 ref 0 pages 1 > > fileid 47269 fsid 0x900ff01 > db> tr 241 > Tracing pid 241 tid 100071 td 0xffffff007ae25980 > _mtx_lock_flags() at _mtx_lock_flags+0x35 > exec_map_first_page() at exec_map_first_page+0x60 > kern_execve() at kern_execve+0x2a0 > execve() at execve+0x5d > syscall() at syscall+0x4ab > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090630c, rsp = > 0x7fffffffcbf8, rbp = 0 --- > db> > the problem is in the unionfs, not loading the module gets me to the shell's prompt, im now trying i386 ... danny From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 09:34:28 2005 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 4E59116A4CE for ; Thu, 21 Apr 2005 09:34:28 +0000 (GMT) Received: from lib-eth.natur.cuni.cz (lib-eth.natur.cuni.cz [195.113.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44D3D43D55 for ; Thu, 21 Apr 2005 09:34:27 +0000 (GMT) (envelope-from xdavid@lib-eth.natur.cuni.cz) Received: from lib-eth.natur.cuni.cz (lib-eth.natur.cuni.cz [195.113.56.250]) j3L9YPeg474884 for ; Thu, 21 Apr 2005 11:34:25 +0200 (MDT) X-Envelope-From: xdavid@lib-eth.natur.cuni.cz X-Envelope-To: Date: Thu, 21 Apr 2005 11:34:25 +0200 (CEST) From: David Komanek To: freebsd-amd64@freebsd.org In-Reply-To: <0a5e514d6f3a98f9ec88fe21538aec4f@khera.org> Message-ID: References: <20050419150335.46904.qmail@web60003.mail.yahoo.com> <20050419143013.47a457ff.kgunders@teamcool.net> <0a5e514d6f3a98f9ec88fe21538aec4f@khera.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: designing new freebsd server for amd64 arch 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, 21 Apr 2005 09:34:28 -0000 Thanks to all who responded. It seems amd64 architecture has still relatively big problems by the motherboards' manufacturers. I will try do the best regarding your advices and opinions. Sincerely, David Komanek From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 10:07:29 2005 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 64AB616A4CE; Thu, 21 Apr 2005 10:07:29 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4BE643D62; Thu, 21 Apr 2005 10:07:28 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.3/8.13.3) with ESMTP id j3LA7SH5057839; Thu, 21 Apr 2005 06:07:28 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j3LA7Si1076161; Thu, 21 Apr 2005 06:07:28 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D316B7306E; Thu, 21 Apr 2005 06:07:27 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050421100727.D316B7306E@freebsd-current.sentex.ca> Date: Thu, 21 Apr 2005 06:07:27 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner4 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 10:07:29 -0000 TB --- 2005-04-21 08:28:03 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-21 08:28:03 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-04-21 08:28:03 - checking out the source tree TB --- 2005-04-21 08:28:03 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-04-21 08:28:03 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-04-21 08:34:45 - building world (CFLAGS=-O2 -pipe) TB --- 2005-04-21 08:34:45 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-21 08:34:45 - /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 >>> stage 5.1: building 32 bit shim libraries TB --- 2005-04-21 09:47:18 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-21 09:47:18 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-21 09:47:18 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Apr 21 09:47:18 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Thu Apr 21 10:03:08 UTC 2005 TB --- 2005-04-21 10:03:08 - generating LINT kernel config TB --- 2005-04-21 10:03:08 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-04-21 10:03:08 - /usr/bin/make -B LINT TB --- 2005-04-21 10:03:08 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-21 10:03:08 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-21 10:03:08 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Apr 21 10:03:08 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c:45: /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/acpivar.h:425:1: "ACPI_MAX_THREADS" redefined In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acfreebsd.h:128, from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acenv.h:208, from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acpi.h:126, from /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c:43: ./opt_acpi.h:2:1: this is the location of the previous definition *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-04-21 10:07:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-21 10:07:27 - ERROR: failed to build lint kernel TB --- 2005-04-21 10:07:27 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 10:22:21 2005 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 0596B16A4CE; Thu, 21 Apr 2005 10:22:21 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B7DC43D41; Thu, 21 Apr 2005 10:22:19 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1DOYp7-000MI5-CA; Thu, 21 Apr 2005 13:22:17 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Danny Braniss In-Reply-To: Message from Danny Braniss Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Apr 2005 13:22:17 +0300 From: Danny Braniss Message-ID: cc: current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: panic: userret: Returning with 1 locks held. 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, 21 Apr 2005 10:22:21 -0000 (moving this to current, since it's not amd64 specific). the followin is caused if unionfs is loaded, compiled into the kernel works ok (current 6.0): > with the latest kernel, the message changed somewhat, but the panic is > still there (this is an amd64): > > trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff8038e3f5 > stack pointer = 0x10:0xffffffffb280e7b0 > frame pointer = 0x10:0xffffffffb280e7e0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 241 (sh) > [thread pid 241 tid 100071 ] > Stopped at _mtx_lock_flags+0x35: cmpq $0x80779d40,0(%rdi) > db> tr > Tracing pid 241 tid 100071 td 0xffffff007ae25980 > _mtx_lock_flags() at _mtx_lock_flags+0x35 > exec_map_first_page() at exec_map_first_page+0x60 > kern_execve() at kern_execve+0x2a0 > execve() at execve+0x5d > syscall() at syscall+0x4ab > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090630c, rsp = > 0x7fffffffcbf8, rbp = 0 --- > db> show lockedvnods > Locked vnodes > > 0xffffff0061a48000: tag union, type VREG > usecount 1, writecount 0, refcount 1 mountedhere 0 > flags (VV_TEXT) > lock type union: EXCL (count 1) by thread 0xffffff007ae25980 (pid 241) > vp=0xffffff0061a48000, uppervp=0, lowervp=0xffffff00626187e0 > union: lower > 0xffffff00626187e0: tag nfs, type VREG > usecount 1, writecount 0, refcount 3 mountedhere 0 > flags () > v_object 0xffffff007c3a87e0 ref 0 pages 1 > > fileid 47269 fsid 0x900ff01 > db> tr 241 > Tracing pid 241 tid 100071 td 0xffffff007ae25980 > _mtx_lock_flags() at _mtx_lock_flags+0x35 > exec_map_first_page() at exec_map_first_page+0x60 > kern_execve() at kern_execve+0x2a0 > execve() at execve+0x5d > syscall() at syscall+0x4ab > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090630c, rsp = > 0x7fffffffcbf8, rbp = 0 --- > db> > > _______________________________________________ > 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 Thu Apr 21 13:49:23 2005 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 123C916A4CE for ; Thu, 21 Apr 2005 13:49:23 +0000 (GMT) Received: from spartan.ac.BrockU.CA (spartan.ac.BrockU.CA [139.57.65.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F23943D41 for ; Thu, 21 Apr 2005 13:49:22 +0000 (GMT) (envelope-from wrees@BrockU.CA) Received: from [139.57.125.66] ([139.57.125.66]) by spartan.ac.BrockU.CA (8.12.8/8.12.8) with ESMTP id j3LDn7wK009542; Thu, 21 Apr 2005 09:49:07 -0400 Message-ID: <4267AF51.50708@BrockU.CA> Date: Thu, 21 Apr 2005 09:49:05 -0400 From: Warren Rees User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Noisy SunFire 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, 21 Apr 2005 13:49:23 -0000 Hello, If it's an earlier v20z/v40z then no, you can't change the fan speed from the OS (from my experiments anyway). However, the later revisions of the boards have included automatic fan speed control so it'll adjust according to the temperature. I got 4 v20z's next to me (2 of them are the older revisions, and 2 of them are the newer revisions), you eventually learn to tune them out :) Warren Danny Braniss wrote: >hi, > does anyone know how to lower the fan speed of this U1? it's a >dual opteron running 5.4 but far away from me :-) > >danny > > >_______________________________________________ >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" > > -- Warren Rees Library Systems Administrator James A. Gibson Library, Brock University Ph: 905.688.5550 x5033 From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 14:08:25 2005 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 270B116A4CE for ; Thu, 21 Apr 2005 14:08:25 +0000 (GMT) Received: from web60005.mail.yahoo.com (web60005.mail.yahoo.com [216.109.116.228]) by mx1.FreeBSD.org (Postfix) with SMTP id 98B7443D1F for ; Thu, 21 Apr 2005 14:08:24 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 75575 invoked by uid 60001); 21 Apr 2005 14:08:24 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=WG2Su+krtD846sV1RqspfmK6PCpEjvbrhe+CqULwjv6/+zcyFqyxcbhNKejyIxLbYbbZGzN0H9WjhqhfOFFrpMKJG6/dk6gpL9HD3sVzozwHnDZzzoBHNp6fFKJFLqLjhmbi6si4VWd8ikr2EZw5ngwuMyT83lqe65vy3XGK7jE= ; Message-ID: <20050421140823.75573.qmail@web60005.mail.yahoo.com> Received: from [68.212.162.80] by web60005.mail.yahoo.com via HTTP; Thu, 21 Apr 2005 07:08:23 PDT Date: Thu, 21 Apr 2005 07:08:23 -0700 (PDT) From: Tom Shafron To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: RAID card 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, 21 Apr 2005 14:08:25 -0000 Hi all. I'm looking to purchase a SATA RAID card to do Raid 10 (not 01). It should handle 12 hard drives. System: 5.3 Release AMD64 Tyan K8S Pro (2882) 2x246 opteron I'm looking at the 3ware 9500S-12MI (http://www.3ware.com/products/serial_ata9000.asp). Does anyone have any experience with that card on the AMD64? Any other cards you'd recommend that work well with AMD64 (it's gotta support RAID 10 though...)? Thanks! -Tom __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 15:08:22 2005 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 9ADFE16A4CE; Thu, 21 Apr 2005 15:08:22 +0000 (GMT) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3962343D1D; Thu, 21 Apr 2005 15:08:22 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.3/8.13.3) with ESMTP id j3LF7rse075073; Thu, 21 Apr 2005 08:07:53 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.3/8.13.1/Submit) id j3LF7qdj075072; Thu, 21 Apr 2005 08:07:52 -0700 (PDT) (envelope-from obrien) Date: Thu, 21 Apr 2005 08:07:52 -0700 From: "David O'Brien" To: Mikhail Teterin Message-ID: <20050421150752.GA74619@dragon.NUXI.org> References: <200504171905.j3HJ50jK096698@corbulon.video-collage.com> <200504201503.57630.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504201503.57630.mi+mx@aldan.algebra.com> X-Operating-System: FreeBSD 6.0-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 User-Agent: Mutt/1.5.9i cc: Q cc: freebsd-amd64@freebsd.org cc: net@freebsd.org Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 15:08:22 -0000 On Wed, Apr 20, 2005 at 03:03:57PM -0400, Mikhail Teterin wrote: > Well, simply checking out sys/dev/nve, sys/contrib/dev/nve, and > sys/modules/nve allowed me to build the if_nve module. Loading if_nve.ko > attaches to the interface, but attempts to ifconfig it result in instant > panic (page fault). I'm going to guess, there is some assumption the driver > makes, that is true on 6.0, but on 5.x Yes. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 15:54:21 2005 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 39B5C16A4CE; Thu, 21 Apr 2005 15:54:21 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECDB243D1D; Thu, 21 Apr 2005 15:54:19 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j3LFsFYB093407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Apr 2005 11:54:18 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11])j3LFs2Wu004497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 11:54:05 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.3/8.13.3) with ESMTP id j3LFrrAP020163; Thu, 21 Apr 2005 11:53:53 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.3/8.13.3/Submit) id j3LFrqLX020162; Thu, 21 Apr 2005 11:53:52 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f From: Mikhail Teterin Organization: Virtual Estates, Inc. To: obrien@freebsd.org Date: Thu, 21 Apr 2005 11:53:52 -0400 User-Agent: KMail/1.7.2 References: <200504201503.57630.mi+mx@aldan.algebra.com> <20050421150752.GA74619@dragon.NUXI.org> In-Reply-To: <20050421150752.GA74619@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504211153.52676.mi+mx@aldan.algebra.com> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 cc: Q cc: freebsd-amd64@freebsd.org cc: net@freebsd.org Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 15:54:21 -0000 > On Wed, Apr 20, 2005 at 03:03:57PM -0400, Mikhail Teterin wrote: > > Well, simply checking out sys/dev/nve, sys/contrib/dev/nve, and > > sys/modules/nve allowed me to build the if_nve module. Loading if_nve.ko > > attaches to the interface, but attempts to ifconfig it result in instant > > panic (page fault). I'm going to guess, there is some assumption the > > driver makes, that is true on 6.0, but on 5.x > > Yes. How admirably Laconic. I volunteer to test the proper (pre-MFC) patches. The system is unusable at the moment :-( -mi From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 16:18:07 2005 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 4A65916A4CE for ; Thu, 21 Apr 2005 16:18:07 +0000 (GMT) Received: from kuang.no-ip.org (59-104-41-214.adsl.dynamic.seed.net.tw [59.104.41.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 122E243D1F for ; Thu, 21 Apr 2005 16:18:06 +0000 (GMT) (envelope-from root@kuang.no-ip.org) Received: from kuang.no-ip.org (localhost.no-ip.org [127.0.0.1]) by kuang.no-ip.org (8.13.1/8.13.1) with ESMTP id j3LGrwxU034967; Fri, 22 Apr 2005 00:54:01 +0800 (CST) (envelope-from root@kuang.no-ip.org) Received: (from root@localhost) by kuang.no-ip.org (8.13.1/8.13.1/Submit) id j3LGrvD4034966; Fri, 22 Apr 2005 00:53:57 +0800 (CST) (envelope-from root) Date: Fri, 22 Apr 2005 00:53:57 +0800 (CST) Message-Id: <200504211653.j3LGrvD4034966@kuang.no-ip.org> To: freebsd-amd64@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: http://www.freebsd.org/platforms/amd64.html X-Mailer: Lynx, Version 2.8.5rel.1 X-Personal_Name: : pachelbel From: kuangwei@ms6.url.com.tw cc: shaw@keydex.com.tw Subject: http://www.freebsd.org/platforms/amd64.html 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, 21 Apr 2005 16:18:07 -0000 The FreeBSD for AMD-64 bit CPU From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 16:25:00 2005 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 C818C16A4CE for ; Thu, 21 Apr 2005 16:25:00 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3DCE43D49 for ; Thu, 21 Apr 2005 16:24:55 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j3LGQf4u095368 for ; Thu, 21 Apr 2005 10:26:41 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4267D30E.6080902@samsco.org> Date: Thu, 21 Apr 2005 10:21:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-amd64@freebsd.org References: <20050419202419.GB63598@bahre.achedra.org> <20050419151900.29d0ee57.kgunders@teamcool.net> <20050419214414.GD63598@bahre.achedra.org> In-Reply-To: <20050419214414.GD63598@bahre.achedra.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Subject: Re: designing new freebsd server for amd64 arch 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, 21 Apr 2005 16:25:00 -0000 Ketrien I. Saihr-Kesenchedra wrote: [...] > As far as advantages/disadvantages - last I'd heard, aac(4) is not 64-bit > clean Just to be clear to the folks who read this list, this claim is false. Why Ketrien likes to spread it with such strong personal authority is beyond me, and it makes me question whether or not many of the other things that he says are completely accurate. Sorry for lashing out here, but gross FUD and mis-information is quite annoying. Scott From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 17:08:36 2005 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 220A616A4CE for ; Thu, 21 Apr 2005 17:08:36 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAFED43D46 for ; Thu, 21 Apr 2005 17:08:34 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.3/8.13.3) with ESMTP id j3LH8XVX050543; Thu, 21 Apr 2005 19:08:33 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.3/8.13.1) with ESMTP id j3LH8ac5039918; Thu, 21 Apr 2005 19:08:36 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.3/8.13.1/Submit) id j3LH8afd039917; Thu, 21 Apr 2005 19:08:36 +0200 (CEST) (envelope-from ftigeot) Date: Thu, 21 Apr 2005 19:08:36 +0200 From: Francois Tigeot To: Tom Shafron Message-ID: <20050421170836.GB37070@aoi.wolfpond.org> References: <20050421140823.75573.qmail@web60005.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050421140823.75573.qmail@web60005.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: RAID card 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, 21 Apr 2005 17:08:36 -0000 On Thu, Apr 21, 2005 at 07:08:23AM -0700, Tom Shafron wrote: > Hi all. I'm looking to purchase a SATA RAID card to > do Raid 10 (not 01). It should handle 12 hard drives. > > System: > 5.3 Release AMD64 > Tyan K8S Pro (2882) > 2x246 opteron > > I'm looking at the 3ware 9500S-12MI > (http://www.3ware.com/products/serial_ata9000.asp). > > Does anyone have any experience with that card on the > AMD64? Any other cards you'd recommend that work well > with AMD64 (it's gotta support RAID 10 though...)? I have no direct experience with this 3Ware model, but I built some NAS servers with the 8-port version and this Tyan board. They worked nicely with a 64-bit system (and still do). -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 17:13:37 2005 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 C82F616A4CE for ; Thu, 21 Apr 2005 17:13:37 +0000 (GMT) Received: from web60001.mail.yahoo.com (web60001.mail.yahoo.com [216.109.116.224]) by mx1.FreeBSD.org (Postfix) with SMTP id 46A4E43D54 for ; Thu, 21 Apr 2005 17:13:37 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 72499 invoked by uid 60001); 21 Apr 2005 17:13:36 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Yn9ByiNl2OShnrBJMVV7a4CAG7jc9JG80QcaWygq8EvcxmxpKgio2GGq0DqoUW9CXwpxx7kH8r2z69z7cL7N3SbXUoEG/4h+LL/mf5etgJXYvmBfQheS6WrHAFQnQBtIZw1Z65CbiKiHw7PcfMRo0+4Y/pjVFzodgzaDBgA0CVQ= ; Message-ID: <20050421171336.72496.qmail@web60001.mail.yahoo.com> Received: from [65.10.26.30] by web60001.mail.yahoo.com via HTTP; Thu, 21 Apr 2005 10:13:36 PDT Date: Thu, 21 Apr 2005 10:13:36 -0700 (PDT) From: Tom Shafron To: Francois Tigeot In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: RAID card 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, 21 Apr 2005 17:13:37 -0000 Thanks for the feedback... getting some good feedback on private emails too so unless someone has something bad to say about this config I think you all just helped me make my decision. Thanks! -Tom --- Francois Tigeot wrote: > On Thu, Apr 21, 2005 at 07:08:23AM -0700, Tom > Shafron wrote: > > Hi all. I'm looking to purchase a SATA RAID card > to > > do Raid 10 (not 01). It should handle 12 hard > drives. > > > > System: > > 5.3 Release AMD64 > > Tyan K8S Pro (2882) > > 2x246 opteron > > > > I'm looking at the 3ware 9500S-12MI > > > (http://www.3ware.com/products/serial_ata9000.asp). > > > > Does anyone have any experience with that card on > the > > AMD64? Any other cards you'd recommend that work > well > > with AMD64 (it's gotta support RAID 10 though...)? > > I have no direct experience with this 3Ware model, > but I built some NAS > servers with the 8-port version and this Tyan board. > > They worked nicely with a 64-bit system (and still > do). > > -- > Francois Tigeot > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 17:22:42 2005 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 B370516A4CE for ; Thu, 21 Apr 2005 17:22:42 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F7AA43D1F for ; Thu, 21 Apr 2005 17:22:42 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so579170wri for ; Thu, 21 Apr 2005 10:22:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=czPnaDXltYyr4cohhGDgckkfQdfutW/SIF3tf1Ahnypg4ORv772GljWVj5saSkZ0HFMcZcVMNQU8MBQ1uWoHTM+4qilaaKW/vAhMavBT6GutmnKa3V0RoTn81sKNIQ9n68+CH02PJxma7Mn4pbJ0JSTWJB9C9JQWzvQDwWSzEXk= Received: by 10.54.68.7 with SMTP id q7mr2183256wra; Thu, 21 Apr 2005 10:14:43 -0700 (PDT) Received: by 10.54.40.69 with HTTP; Thu, 21 Apr 2005 10:14:41 -0700 (PDT) Message-ID: <2fd864e0504211014251b18a6@mail.gmail.com> Date: Thu, 21 Apr 2005 10:14:41 -0700 From: Astrodog To: Scott Long In-Reply-To: <4267D30E.6080902@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050419202419.GB63598@bahre.achedra.org> <20050419151900.29d0ee57.kgunders@teamcool.net> <20050419214414.GD63598@bahre.achedra.org> <4267D30E.6080902@samsco.org> cc: freebsd-amd64@freebsd.org Subject: Re: designing new freebsd server for amd64 arch X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2005 17:22:42 -0000 On 4/21/05, Scott Long wrote: > Ketrien I. Saihr-Kesenchedra wrote: >=20 > [...] >=20 > > As far as advantages/disadvantages - last I'd heard, aac(4) is not 64-b= it > > clean >=20 > Just to be clear to the folks who read this list, this claim is false. > Why Ketrien likes to spread it with such strong personal authority is > beyond me, and it makes me question whether or not many of the other > things that he says are completely accurate. Sorry for lashing out > here, but gross FUD and mis-information is quite annoying. >=20 > Scott Perhaps the hardware compatibility list needs to be updated? There are still a few issues, maybe just an addendum to the i386 compat list, saying what doesn't work on AMD64, that does on i386. From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 22:32:26 2005 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 03F6016A4CE for ; Thu, 21 Apr 2005 22:32:26 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 684E143D46 for ; Thu, 21 Apr 2005 22:32:23 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id 59B8D4B034; Fri, 22 Apr 2005 00:32:22 +0200 (CEST) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 58674-04-4; Fri, 22 Apr 2005 00:32:22 +0200 (CEST) Received: from palle.girgensohn.se (1-2-8-5a.asp.sth.bostream.se [82.182.157.66]) by melon.pingpong.net (Postfix) with ESMTP id 21BD34AD6C; Fri, 22 Apr 2005 00:32:21 +0200 (CEST) Date: Fri, 22 Apr 2005 00:32:21 +0200 From: Palle Girgensohn To: Damian Gerow , freebsd-amd64@freebsd.org Message-ID: <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> In-Reply-To: <20050322133719.GX697@afflictions.org> References: <20050319021654.GD27012@afflictions.org> <20050322133719.GX697@afflictions.org> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Subject: Re: java/jdk15 help [SOLVED?] 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, 21 Apr 2005 22:32:26 -0000 --On tisdag, mars 22, 2005 08.37.19 -0500 Damian Gerow wrote: > Thus spake Damian Gerow (dgerow@afflictions.org) [19/03/05 08:44]: > : I've noticed that a few people here have successfully gotten a native > : java/jdk15 built. Can one of those people lend me a hand, please? > : > : I've installed linux-sun-jdk-1.4.2.07_1, and worked around the wonky > problem : thrown by the jdk15 build. But afterwards, all I seem to get > is hung javac : processes, each consuming 100% of CPU. > > By some ridiculous fluke, I tried a build with WITH_IPV6 defined. It > built without any issue whatsoever, and has now been installed. So I at > least have a JDK at this point; now to try to figure out how/why it's > failing when I don't want IPV6 support. Are you sure about this? I mean that it all worked when compiling WITH_IPV6? I'm trying to get the linux-sun-jdk-1.4.2.07_1 javac to compile anything, but it just starts consuming 100% forever for a simple hello world app. There's no way it could build anything? What gives? Same thing happens when running the port jdk15 port gets to the javac part, or even running jar... I just noticed that it does not happen every time. I managed to run linux 1.4 javac on a simple hello world app a dozen times in a row, but on the thirteenth time it stuck, and the two javac processes required a kill -9 to die. This is on a Dell 2850 dual CPU (with hyperthreading, so four "virtual" cpus), so it is not really an AMD64, but "EMT64". I'm quite amazed that I see reports of java working on amd64. On this machine it is completely impossible, as linux bootstrapping jdk hangs all the time. Most other things work on the machine, although I've experienced some stability problems. Could it be a hardware problem? /Palle From owner-freebsd-amd64@FreeBSD.ORG Thu Apr 21 23:12:04 2005 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 3B70016A4CE for ; Thu, 21 Apr 2005 23:12:04 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 667AE43D39 for ; Thu, 21 Apr 2005 23:12:03 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id A749F78C72 for ; Thu, 21 Apr 2005 19:13:42 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99283-05 for ; Thu, 21 Apr 2005 19:13:36 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id 7076378C6D for ; Thu, 21 Apr 2005 19:13:35 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 7434733C60; Thu, 21 Apr 2005 19:12:06 -0400 (EDT) Date: Thu, 21 Apr 2005 19:12:06 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050421231206.GO720@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20050319021654.GD27012@afflictions.org> <20050322133719.GX697@afflictions.org> <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: java/jdk15 help [SOLVED?] 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, 21 Apr 2005 23:12:04 -0000 Thus spake Palle Girgensohn (girgen@pingpong.net) [21/04/05 18:34]: : >By some ridiculous fluke, I tried a build with WITH_IPV6 defined. It : >built without any issue whatsoever, and has now been installed. So I at : >least have a JDK at this point; now to try to figure out how/why it's : >failing when I don't want IPV6 support. : : Are you sure about this? I mean that it all worked when compiling : WITH_IPV6? Pretty sure. I tried a build without WITH_IPV6, and it didn't work. I cleaned, and tried a build /with/ WITH_IPV6, and it worked. Someone else reported that defining another option also made it work for him. : This is on a Dell 2850 dual CPU (with hyperthreading, so four "virtual" : cpus), so it is not really an AMD64, but "EMT64". : : I'm quite amazed that I see reports of java working on amd64. On this : machine it is completely impossible, as linux bootstrapping jdk hangs all : the time. Most other things work on the machine, although I've experienced : some stability problems. Could it be a hardware problem? Could be an EMT64 vs AMD64 problem. AFAIk, 'EMT64' machines aren't as common as AMD64 machines. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 22 05:25:19 2005 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 B4B4D16A4CE for ; Fri, 22 Apr 2005 05:25:19 +0000 (GMT) Received: from lobo.homeunix.org (reverse-82-141-57-46.dialin.kamp-dsl.de [82.141.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50F7B43D67 for ; Fri, 22 Apr 2005 05:25:18 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.3/8.13.1) with ESMTP id j3M5QNZi000924; Fri, 22 Apr 2005 07:26:23 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.3/8.13.1/Submit) id j3M5QM6k000923; Fri, 22 Apr 2005 07:26:22 +0200 (CEST) (envelope-from ewinter) Date: Fri, 22 Apr 2005 07:26:22 +0200 From: "Ernst W. Winter" To: Palle Girgensohn Message-ID: <20050422052622.GB834@lobo.homeunix.org> References: <20050319021654.GD27012@afflictions.org> <20050322133719.GX697@afflictions.org> <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.4-STABLE FreeBSD 5.4-STABLE User-Agent: Mutt/1.5.9i cc: freebsd-amd64@freebsd.org Subject: Re: java/jdk15 help [SOLVED?] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 05:25:19 -0000 On Fri, 22 Apr 2005, Palle Girgensohn wrote: > > --On tisdag, mars 22, 2005 08.37.19 -0500 Damian Gerow > wrote: > > >Thus spake Damian Gerow (dgerow@afflictions.org) [19/03/05 08:44]: > >: I've noticed that a few people here have successfully gotten a native > >: java/jdk15 built. Can one of those people lend me a hand, please? > >: > >: I've installed linux-sun-jdk-1.4.2.07_1, and worked around the wonky > >problem : thrown by the jdk15 build. But afterwards, all I seem to get > >is hung javac : processes, each consuming 100% of CPU. > > > >By some ridiculous fluke, I tried a build with WITH_IPV6 defined. It > >built without any issue whatsoever, and has now been installed. So I at > >least have a JDK at this point; now to try to figure out how/why it's > >failing when I don't want IPV6 support. > > Are you sure about this? I mean that it all worked when compiling > WITH_IPV6? > I haven't tried this one, but mine is working well. > I'm trying to get the linux-sun-jdk-1.4.2.07_1 javac to compile > anything, but it just starts consuming 100% forever for a simple > hello world app. There's no way it could build anything? What > gives? Same thing happens when running the port jdk15 port gets to > the javac part, or even running jar... > Hmm, I owuld say some settings are not right by the sound of this. > I just noticed that it does not happen every time. I managed to run > linux 1.4 javac on a simple hello world app a dozen times in a row, > but on the thirteenth time it stuck, and the two javac processes > required a kill -9 to die. > NO problem here to run Linuz Apps. > This is on a Dell 2850 dual CPU (with hyperthreading, so four > "virtual" cpus), so it is not really an AMD64, but "EMT64". > MIne is a single 939 with ASUS MB. > I'm quite amazed that I see reports of java working on amd64. On > this machine it is completely impossible, as linux bootstrapping > jdk hangs all the time. Most other things work on the machine, > although I've experienced some stability problems. Could it be a > hardware problem? > NOt likeley form what I can say, try to contact: Jon Kuster as I helped him a bit to get his problem fixed and from what I remember he had the same machine. Say hello form me. I won't be here as from the next hour and will be back on Monday afternoon, and then I can help if you still need any help. Have a nice weekend. Ernst From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 22 06:53:04 2005 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 1229116A4CE for ; Fri, 22 Apr 2005 06:53:04 +0000 (GMT) Received: from pop-a065c10.pas.sa.earthlink.net (pop-a065c10.pas.sa.earthlink.net [207.217.121.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA59143D46 for ; Fri, 22 Apr 2005 06:53:03 +0000 (GMT) (envelope-from kwsn@earthlink.net) Received: from dialup-4.240.51.43.dial1.phoenix1.level3.net ([4.240.51.43] helo=jonnyv.kwsn.lan) by pop-a065c10.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DOs25-00051v-00; Thu, 21 Apr 2005 23:52:57 -0700 From: Jon Kuster To: "Ernst W. Winter" In-Reply-To: <20050422052622.GB834@lobo.homeunix.org> References: <20050319021654.GD27012@afflictions.org> <20050322133719.GX697@afflictions.org> <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> <20050422052622.GB834@lobo.homeunix.org> Content-Type: text/plain Date: Thu, 21 Apr 2005 23:52:55 -0700 Message-Id: <1114152775.16187.25.camel@jonnyv.kwsn.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org cc: Palle Girgensohn Subject: Re: java/jdk15 help [SOLVED?] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kwsn@earthlink.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 06:53:04 -0000 On Fri, 2005-04-22 at 07:26 +0200, Ernst W. Winter wrote: > On Fri, 22 Apr 2005, Palle Girgensohn wrote: > > > > > --On tisdag, mars 22, 2005 08.37.19 -0500 Damian Gerow > > wrote: > > > > >Thus spake Damian Gerow (dgerow@afflictions.org) [19/03/05 08:44]: > > >: I've noticed that a few people here have successfully gotten a native > > >: java/jdk15 built. Can one of those people lend me a hand, please? > > >: > > >: I've installed linux-sun-jdk-1.4.2.07_1, and worked around the wonky > > >problem : thrown by the jdk15 build. But afterwards, all I seem to get > > >is hung javac : processes, each consuming 100% of CPU. > > > > > >By some ridiculous fluke, I tried a build with WITH_IPV6 defined. It > > >built without any issue whatsoever, and has now been installed. So I at > > >least have a JDK at this point; now to try to figure out how/why it's > > >failing when I don't want IPV6 support. > > > > Are you sure about this? I mean that it all worked when compiling > > WITH_IPV6? > > > I haven't tried this one, but mine is working well. > > > I'm trying to get the linux-sun-jdk-1.4.2.07_1 javac to compile > > anything, but it just starts consuming 100% forever for a simple > > hello world app. There's no way it could build anything? What > > gives? Same thing happens when running the port jdk15 port gets to > > the javac part, or even running jar... > > > Hmm, I owuld say some settings are not right by the sound of this. > > > I just noticed that it does not happen every time. I managed to run > > linux 1.4 javac on a simple hello world app a dozen times in a row, > > but on the thirteenth time it stuck, and the two javac processes > > required a kill -9 to die. > > This sounds exactly like the problems were were experiencing. > NO problem here to run Linuz Apps. > > > This is on a Dell 2850 dual CPU (with hyperthreading, so four > > "virtual" cpus), so it is not really an AMD64, but "EMT64". > > > MIne is a single 939 with ASUS MB. > > > I'm quite amazed that I see reports of java working on amd64. On > > this machine it is completely impossible, as linux bootstrapping > > jdk hangs all the time. Most other things work on the machine, > > although I've experienced some stability problems. Could it be a > > hardware problem? > > > NOt likeley form what I can say, try to contact: > > Jon Kuster > > as I helped him a bit to get his problem fixed and from what I > remember he had the same machine. Say hello form me. Hi Ernst :) I've got an 1850, which I think is the same as a 2850, except in 1U form. I doubt it's a hardware problem. I'm guessing it's a problem somewhere in the linux32 code, but I don't know for sure. Since I wasn't able to determine the real problem, I can't give a surefire solution, but I do have some tips: 1. While you're building jdk15, switch to a UP kernel as it seems to help make the linux-sun-jdk14 a bit more stable. 2. Reinstall linux_base-8 and everything it depends on and everything that depends on it (don't know that this actually helps, but it can't hurt). 3. Make sure linprocfs is mounted. 4. Apply the patch in this message, or jdk15 will abort with SIGILL on your Xeons: http://docs.freebsd.org/cgi/mid.cgi?20050123040212.71599.qmail 5. During the build, make sure the box is as idle as possible. Make sure nothing more intensive than top is active (watching compile messages scroll by is OK). 6. Even if you have no problems with java during the build, it will die with an error about 2/3rds of the way through. Ernst provided me with some notes that got me around this error, so I'll reproduce them here: -----------------------------Snip------------------------------------- i had the same problem and solved it executing the last command which caused the error manually. Looks like the error comes because it's a very long command. Just put the command that comes between 'then' and 'fi' in a shell file and execute it manually in the directory work/j2sre/make/java/java (I'm not seating now in my amd64 FreeBSD computer but I think that was the directory). The compilation will go on without any problem if you resume it afterwards with a 'make build'. Try 'make build |& tee build.out' (if your shell is csh or tcsh) or 'make build 2>&1 | tee build.out' (if sh or bash). After the error comes, edit build.out and you will see the command causing it (takes about two pages). --------------------------------------------------------------------- After you restart the build, it might hang again with your java problem - it did for me once. All I can say is kill it, do a make clean, reapply the patch, and start the build again. On the bright side, once you do manage to get jdk15 built and installed, it should be quite stable. We haven't been able to get our to fail yet on UP or SMP with a -j12 buildworld going on in the background. Hope this helps. -Jon From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 22 07:30:50 2005 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 8DDFE16A4CE for ; Fri, 22 Apr 2005 07:30:50 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBBBF43D2F for ; Fri, 22 Apr 2005 07:30:49 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id DE50478C5D for ; Fri, 22 Apr 2005 03:32:29 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32157-04 for ; Fri, 22 Apr 2005 03:32:25 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id EFC0D78C35 for ; Fri, 22 Apr 2005 03:32:24 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 3EDCB33C60; Fri, 22 Apr 2005 03:30:57 -0400 (EDT) Date: Fri, 22 Apr 2005 03:30:57 -0400 From: Damian Gerow To: freebsd-amd64@freebsd.org Message-ID: <20050422073056.GS720@afflictions.org> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20050319021654.GD27012@afflictions.org> <20050322133719.GX697@afflictions.org> <97B5984DC59670DFEB70AD4C@palle.girgensohn.se> <20050422052622.GB834@lobo.homeunix.org> <1114152775.16187.25.camel@jonnyv.kwsn.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1114152775.16187.25.camel@jonnyv.kwsn.lan> X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: Re: java/jdk15 help [SOLVED?] 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, 22 Apr 2005 07:30:50 -0000 Thus spake Jon Kuster (kwsn@earthlink.net) [22/04/05 02:55]: : After you restart the build, it might hang again with your java problem : - it did for me once. All I can say is kill it, do a make clean, : reapply the patch, and start the build again. This is the problem that, for whatever reason, using WITH_IPV6 fixed for me. For the life of me, I couldn't get past that point without it defined (javac processes hung around like unwanted guests at an open bar wedding reception). As soon as I defined WITH_IPV6, it built just fine. And I ran a few test builds afterwards (before installing, so I was still using the Linux JDK), and defining it always made the difference. : On the bright side, once : you do manage to get jdk15 built and installed, it should be quite : stable. We haven't been able to get our to fail yet on UP or SMP with a : -j12 buildworld going on in the background. Same here. Even though it's marked alpha, it's been *remarkably* stable. From owner-freebsd-amd64@FreeBSD.ORG Fri Apr 22 08:17:43 2005 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 099A316A4CE; Fri, 22 Apr 2005 08:17:43 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54BD743D4C; Fri, 22 Apr 2005 08:17:42 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.3/8.13.3) with ESMTP id j3M8HfJc037854; Fri, 22 Apr 2005 04:17:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id j3M8I4jI061277; Fri, 22 Apr 2005 04:18:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9230E7306E; Fri, 22 Apr 2005 04:17:41 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050422081741.9230E7306E@freebsd-current.sentex.ca> Date: Fri, 22 Apr 2005 04:17:41 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 08:17:43 -0000 TB --- 2005-04-22 06:27:42 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-22 06:27:42 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-04-22 06:27:42 - checking out the source tree TB --- 2005-04-22 06:27:42 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-04-22 06:27:42 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-04-22 06:34:25 - building world (CFLAGS=-O2 -pipe) TB --- 2005-04-22 06:34:25 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-22 06:34:25 - /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 >>> stage 5.1: building 32 bit shim libraries TB --- 2005-04-22 07:57:30 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-22 07:57:30 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-22 07:57:30 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Apr 22 07:57:31 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Apr 22 08:13:08 UTC 2005 TB --- 2005-04-22 08:13:08 - generating LINT kernel config TB --- 2005-04-22 08:13:08 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-04-22 08:13:08 - /usr/bin/make -B LINT TB --- 2005-04-22 08:13:08 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-22 08:13:08 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-22 08:13:08 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Apr 22 08:13:08 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c:45: /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/acpivar.h:425:1: "ACPI_MAX_THREADS" redefined In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acfreebsd.h:128, from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acenv.h:208, from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acpi.h:126, from /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c:43: ./opt_acpi.h:2:1: this is the location of the previous definition *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-04-22 08:17:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-22 08:17:41 - ERROR: failed to build lint kernel TB --- 2005-04-22 08:17:41 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 02:35:48 2005 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 C379316A4CE for ; Sat, 23 Apr 2005 02:35:48 +0000 (GMT) Received: from web60004.mail.yahoo.com (web60004.mail.yahoo.com [216.109.116.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 4AAF743D2D for ; Sat, 23 Apr 2005 02:35:48 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 83736 invoked by uid 60001); 23 Apr 2005 02:35:47 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=uILSF6/g/C37OhzsZfNiB+fKPISTaDTqOE8IJdpkxjSC0oEyWqWC0cLHZXeABIs+nBksOxZTQDPsC0Zm4k5bcB4M3BNx8AvrVTF8x8hyS7edsWKPKGIzMcMTfOxecptg4kO1ikvSpa3iO+bUT/lZ4y/WweHKRmGGJNK/bn+U7zU= ; Message-ID: <20050423023547.83734.qmail@web60004.mail.yahoo.com> Received: from [68.212.162.248] by web60004.mail.yahoo.com via HTTP; Fri, 22 Apr 2005 19:35:47 PDT Date: Fri, 22 Apr 2005 19:35:47 -0700 (PDT) From: Tom Shafron To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 02:35:48 -0000 My 5.3 amd64 just locked up. Seems to be a similar problem to what Vivek has been describing. The config is: Tyan k8s pro (SATA version) 5.3 Release 2 x 246 opteron onboard bge Gb ethernet 4 x 512 MB (2GB) 2 x 250 GB SATA (Western Digitial wd2500sd) I have it configured as a Raid 1 mirror using GEOM mirror. The circumstances were I was logged in remotely using SSH and creating 2 large files (100 MB and 500 MB). I created them and 0 filled them then mmapd the 500 MB file and wrote to it using random access. Upon closing the files the whole system froze for a couple of seconds (to be expected since it was flushing all the data I had just written). I was then able to use the system normally for maybe 15 seconds when ssh just froze up on me. I was still able to ping for about 10-15 minutes but was getting 30 ms response times using a machine that's directly connected to it (no hub) until the machine completely stopped responding. Since it's at a remote location I'm going to check it out tomorrow and see if I can figure out what happened but this seems very similar to what Vivek was reporting earlier. It doesn't seem to be related to network access though and seems to have more to do with heavy disk I/O... or maybe it's just heavy bus traffic that causes it... Btw, is there a specific place I should be submitting this bug report (new to the freebsd community)? -Tom __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 02:43:02 2005 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 ADDC116A4CE for ; Sat, 23 Apr 2005 02:43:02 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 708F143D49 for ; Sat, 23 Apr 2005 02:43:02 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j3N2h125083481; Fri, 22 Apr 2005 19:43:01 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j3N2h1RP083480; Fri, 22 Apr 2005 19:43:01 -0700 (PDT) (envelope-from sgk) Date: Fri, 22 Apr 2005 19:43:01 -0700 From: Steve Kargl To: Tom Shafron Message-ID: <20050423024301.GA83385@troutmask.apl.washington.edu> References: <20050423023547.83734.qmail@web60004.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050423023547.83734.qmail@web60004.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 02:43:02 -0000 On Fri, Apr 22, 2005 at 07:35:47PM -0700, Tom Shafron wrote: > My 5.3 amd64 just locked up. Seems to be a similar > problem to what Vivek has been describing. The config > is: > > Tyan k8s pro (SATA version) > 5.3 Release ^^^^^^^^^^^ This could be your problem (although Scott Long fixes were for systems with >4 GB memory). Since the system is lock-up at the moment, you may want to take this oportunity to upgrade to 5.4 RC2 or newer. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 02:48:55 2005 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 D758716A4CE for ; Sat, 23 Apr 2005 02:48:55 +0000 (GMT) Received: from web60007.mail.yahoo.com (web60007.mail.yahoo.com [216.109.116.245]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F94243D48 for ; Sat, 23 Apr 2005 02:48:55 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 88997 invoked by uid 60001); 23 Apr 2005 02:48:54 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=w3kG4ZqduMAFS58UYbkfLL9YXGhwANETenbTLrVXfwo9g3ZlIyqjvExVsPxKiIrlZEeNs4AI8G+PgLV2FT3S4kTFid744Dub4fiJ3XwPJqYip025Mya5LfSDBJHkTCTraKY4QuG32MlgUXIYLAyKTw3mXeM+eqrt7QpAslSWGhs= ; Message-ID: <20050423024854.88995.qmail@web60007.mail.yahoo.com> Received: from [68.212.162.248] by web60007.mail.yahoo.com via HTTP; Fri, 22 Apr 2005 19:48:54 PDT Date: Fri, 22 Apr 2005 19:48:54 -0700 (PDT) From: Tom Shafron To: Steve Kargl In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 02:48:56 -0000 --- Steve Kargl wrote: > On Fri, Apr 22, 2005 at 07:35:47PM -0700, Tom > Shafron wrote: > > My 5.3 amd64 just locked up. Seems to be a > similar > > problem to what Vivek has been describing. The > config > > is: > > > > Tyan k8s pro (SATA version) > > 5.3 Release > ^^^^^^^^^^^ > This could be your problem (although Scott Long > fixes > were for systems with >4 GB memory). > > Since the system is lock-up at the moment, you > may want to take this oportunity to upgrade to > 5.4 RC2 or newer. > I'm kind of nervous about using 5.4 since it's not considered a "Release" version yet and I'm planning on using this for a production machine... that is assuming I can get it working properly ;) Is it the general consensus that 5.4 RC2 is more stable than 5.3 (who cares if 5.3 is "release" if it locks up right...) and could be used in a production box? Or is this a bad idea...? As of now I'm definitely not comfortable with using this 5.3 box in production... Thanks, Tom __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 02:54:28 2005 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 324C916A4CE for ; Sat, 23 Apr 2005 02:54:28 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD18943D53 for ; Sat, 23 Apr 2005 02:54:27 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D909C514ED; Fri, 22 Apr 2005 19:54:26 -0700 (PDT) Date: Fri, 22 Apr 2005 19:54:26 -0700 From: Kris Kennaway To: Tom Shafron Message-ID: <20050423025426.GA15376@xor.obsecurity.org> References: <20050423024854.88995.qmail@web60007.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <20050423024854.88995.qmail@web60007.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 02:54:28 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 22, 2005 at 07:48:54PM -0700, Tom Shafron wrote: > --- Steve Kargl > wrote: > > On Fri, Apr 22, 2005 at 07:35:47PM -0700, Tom > > Shafron wrote: > > > My 5.3 amd64 just locked up. Seems to be a > > similar > > > problem to what Vivek has been describing. The > > config > > > is: > > >=20 > > > Tyan k8s pro (SATA version) > > > 5.3 Release > > ^^^^^^^^^^^ > > This could be your problem (although Scott Long > > fixes > > were for systems with >4 GB memory). > >=20 > > Since the system is lock-up at the moment, you > > may want to take this oportunity to upgrade to > > 5.4 RC2 or newer. > >=20 >=20 > I'm kind of nervous about using 5.4 since it's not > considered a "Release" version yet and I'm planning on > using this for a production machine... that is > assuming I can get it working properly ;) >=20 > Is it the general consensus that 5.4 RC2 is more > stable than 5.3 (who cares if 5.3 is "release" if it > locks up right...) and could be used in a production > box? Or is this a bad idea...? As of now I'm > definitely not comfortable with using this 5.3 box in > production... Given that 5.3 is apparently unusable for you, it can't be that much of a worry for you to try out the release candidate for 5.4, which is by definition "very close to what will be released as 5.4". Kris --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCabjiWry0BWjoQKURAm0zAJ92MNNHAQLgLp77lPaJ/ao+t8wwJQCfRMHv 1sTOgWdROleWwPTfjeWUE0k= =v5j/ -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 03:03:40 2005 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 6F98E16A4CE for ; Sat, 23 Apr 2005 03:03:40 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E9C343D1D for ; Sat, 23 Apr 2005 03:03:36 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j3N33aoD083631; Fri, 22 Apr 2005 20:03:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j3N33aCl083630; Fri, 22 Apr 2005 20:03:36 -0700 (PDT) (envelope-from sgk) Date: Fri, 22 Apr 2005 20:03:36 -0700 From: Steve Kargl To: Tom Shafron Message-ID: <20050423030336.GC83385@troutmask.apl.washington.edu> References: <20050423024854.88995.qmail@web60007.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050423024854.88995.qmail@web60007.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 03:03:40 -0000 On Fri, Apr 22, 2005 at 07:48:54PM -0700, Tom Shafron wrote: > --- Steve Kargl > wrote: > > On Fri, Apr 22, 2005 at 07:35:47PM -0700, Tom > > Shafron wrote: > > > My 5.3 amd64 just locked up. Seems to be a similar > > > problem to what Vivek has been describing. The config > > > is: > > > > > > Tyan k8s pro (SATA version) > > > 5.3 Release > > ^^^^^^^^^^^ > > This could be your problem (although Scott Long > > fixes were for systems with >4 GB memory). > > > > Since the system is lock-up at the moment, you > > may want to take this oportunity to upgrade to > > 5.4 RC2 or newer. > > > > I'm kind of nervous about using 5.4 since it's not > considered a "Release" version yet and I'm planning on > using this for a production machine... that is > assuming I can get it working properly ;) As Kris said, 5.4 RC2 can't be any worse than a 5.3 that locks your system up. All kidding aside, there were stability problems in 5.3 on amd64, and some of those problems have been fixed in 5.4 -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 03:19:17 2005 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 D3C5A16A4CE for ; Sat, 23 Apr 2005 03:19:17 +0000 (GMT) Received: from web60008.mail.yahoo.com (web60008.mail.yahoo.com [216.109.116.246]) by mx1.FreeBSD.org (Postfix) with SMTP id 6456C43D58 for ; Sat, 23 Apr 2005 03:19:17 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 38884 invoked by uid 60001); 23 Apr 2005 03:19:17 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=tOTfwLiO5hh91S2Sy0oVudJL0Y6m99uuBMN3KHD3vCiy90K81nf1A8CEUcZ3fhTB9xqUeRpDbJMNYOgwdhii3BY73pmgRKv87kYmz9h07951BbjR+RGlwWAhKrYTZDGwovTSSNuxCzAB9jirOICQwTUZfEqJl0WB5GjqZRCU1Jk= ; Message-ID: <20050423031916.38882.qmail@web60008.mail.yahoo.com> Received: from [68.212.162.248] by web60008.mail.yahoo.com via HTTP; Fri, 22 Apr 2005 20:19:16 PDT Date: Fri, 22 Apr 2005 20:19:16 -0700 (PDT) From: Tom Shafron To: Steve Kargl In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-amd64@freebsd.org Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 03:19:17 -0000 --- Steve Kargl wrote: > On Fri, Apr 22, 2005 at 07:48:54PM -0700, Tom > Shafron wrote: > > --- Steve Kargl > > wrote: > > > On Fri, Apr 22, 2005 at 07:35:47PM -0700, Tom > > > Shafron wrote: > > > > My 5.3 amd64 just locked up. Seems to be a > similar > > > > problem to what Vivek has been describing. > The config > > > > is: > > > > > > > > Tyan k8s pro (SATA version) > > > > 5.3 Release > > > ^^^^^^^^^^^ > > > This could be your problem (although Scott Long > > > fixes were for systems with >4 GB memory). > > > > > > Since the system is lock-up at the moment, you > > > may want to take this oportunity to upgrade to > > > 5.4 RC2 or newer. > > > > > > > I'm kind of nervous about using 5.4 since it's not > > considered a "Release" version yet and I'm > planning on > > using this for a production machine... that is > > assuming I can get it working properly ;) > > As Kris said, 5.4 RC2 can't be any worse than a > 5.3 that locks your system up. All kidding aside, > there were stability problems in 5.3 on amd64, and > some of those problems have been fixed in 5.4 > > -- > Steve > Yup, I also have 5.3 running on a very similar i386 machine that is way more active (it's the main dev machine) and it hasn't had a single problem. Seems that the issue is something specific to the amd64 release... You're right, I'll give 5.4 a try. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 03:48:17 2005 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 73F6316A4CE for ; Sat, 23 Apr 2005 03:48:17 +0000 (GMT) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA39B43D31 for ; Sat, 23 Apr 2005 03:48:16 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 02365F7B1 for ; Fri, 22 Apr 2005 21:48:15 -0600 (MDT) Date: Fri, 22 Apr 2005 21:48:14 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050422214814.73cb6ed8.kgunders@teamcool.net> In-Reply-To: <20050423023547.83734.qmail@web60004.mail.yahoo.com> References: <20050423023547.83734.qmail@web60004.mail.yahoo.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.6 (GTK+ 2.6.4; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 03:48:17 -0000 On Fri, 22 Apr 2005 19:35:47 -0700 (PDT) Tom Shafron wrote: > My 5.3 amd64 just locked up. Seems to be a similar > problem to what Vivek has been describing. The config > is: > > Tyan k8s pro (SATA version) > 5.3 Release > 2 x 246 opteron > onboard bge Gb ethernet > 4 x 512 MB (2GB) > 2 x 250 GB SATA (Western Digitial wd2500sd) > > I have it configured as a Raid 1 mirror using GEOM > mirror. Just out of curiosity, what memory are you using here? Also, I don't recall specifics, but I think there were a couple issues with gmirror on 5.3-release. As others have pointed out 5.4RC would be good choice, but if it is too "scary", might try cvsup'ing to 5.3- stable. -- Best regards, Ken Gunderson GPG Key-- 9F5179FD "Freedom begins between the ears." -- Edward Abbey From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 04:11:06 2005 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 6A3A316A4CE for ; Sat, 23 Apr 2005 04:11:06 +0000 (GMT) Received: from web60002.mail.yahoo.com (web60002.mail.yahoo.com [216.109.116.225]) by mx1.FreeBSD.org (Postfix) with SMTP id B516043D1F for ; Sat, 23 Apr 2005 04:11:05 +0000 (GMT) (envelope-from phred1975@yahoo.com) Received: (qmail 63459 invoked by uid 60001); 23 Apr 2005 04:11:05 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=KuYfYx0s6om1O83OTLPOaaCbUhktwA5mtTQ71h9EYJCekxGWuPnrNQfs9AK2+rsISUsIGNkUOktWMHkpsaMp3QDYzfDVFU+YrjWfBABnaTeEdSf8mk0gp7ZUWYtIeeQdxvp2JNeShqMpB7iF57Vk50cyXIOgLXGBXIxope6nJxI= ; Message-ID: <20050423041105.63457.qmail@web60002.mail.yahoo.com> Received: from [68.212.162.248] by web60002.mail.yahoo.com via HTTP; Fri, 22 Apr 2005 21:11:05 PDT Date: Fri, 22 Apr 2005 21:11:05 -0700 (PDT) From: Tom Shafron To: Ken Gunderson , freebsd-amd64@freebsd.org In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: 5.3, amd64, k8s pro locked up just now X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 04:11:06 -0000 --- Ken Gunderson wrote: > On Fri, 22 Apr 2005 19:35:47 -0700 (PDT) > Tom Shafron wrote: > > > My 5.3 amd64 just locked up. Seems to be a > similar > > problem to what Vivek has been describing. The > config > > is: > > > > Tyan k8s pro (SATA version) > > 5.3 Release > > 2 x 246 opteron > > onboard bge Gb ethernet > > 4 x 512 MB (2GB) > > 2 x 250 GB SATA (Western Digitial wd2500sd) > > > > I have it configured as a Raid 1 mirror using GEOM > > mirror. > > Just out of curiosity, what memory are you using > here? > > Also, I don't recall specifics, but I think there > were a couple issues > with gmirror on 5.3-release. As others have pointed > out 5.4RC would be > good choice, but if it is too "scary", might try > cvsup'ing to 5.3- > stable. > > -- Best regards, > Transcend DDR 400 512 MB (registered, ECC) http://www2.newegg.com/Product/Product.asp?Item=N82E16820208122 Thanks for the tip on gmirror, I'll check it out in the archives. I'm gonna give 5.4RC3 a try... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 06:05:02 2005 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 EC20816A4CE; Sat, 23 Apr 2005 06:05:02 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65FE643D45; Sat, 23 Apr 2005 06:05:02 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j3N651rK005664; Sat, 23 Apr 2005 02:05:01 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id j3N65Q86015946; Sat, 23 Apr 2005 02:05:26 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 77DD27306E; Sat, 23 Apr 2005 02:05:01 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050423060501.77DD27306E@freebsd-current.sentex.ca> Date: Sat, 23 Apr 2005 02:05:01 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.82, clamav-milter version 0.82 on clamscanner4 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 06:05:03 -0000 TB --- 2005-04-23 03:47:03 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-23 03:47:03 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2005-04-23 03:47:04 - checking out the source tree TB --- 2005-04-23 03:47:04 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2005-04-23 03:47:04 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-04-23 03:53:47 - building world (CFLAGS=-O2 -pipe) TB --- 2005-04-23 03:53:47 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-23 03:53:47 - /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 >>> stage 5.1: building 32 bit shim libraries TB --- 2005-04-23 05:32:12 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-23 05:32:12 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-23 05:32:12 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Apr 23 05:32:13 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Apr 23 05:57:09 UTC 2005 TB --- 2005-04-23 05:57:09 - generating LINT kernel config TB --- 2005-04-23 05:57:09 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2005-04-23 05:57:09 - /usr/bin/make -B LINT TB --- 2005-04-23 05:57:10 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-04-23 05:57:10 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2005-04-23 05:57:10 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Apr 23 05:57:11 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/amd64/amd64/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-ta bles -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c:45: /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/acpivar.h:425:1: "ACPI_MAX_THREADS" redefined In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acfreebsd.h:128, from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acenv.h:208, from /tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica/acpi.h:126, from /tinderbox/CURRENT/amd64/amd64/src/sys/dev/acpica/Osd/OsdDebug.c:43: ./opt_acpi.h:2:1: this is the location of the previous definition *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2005-04-23 06:05:01 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-23 06:05:01 - ERROR: failed to build lint kernel TB --- 2005-04-23 06:05:01 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 23 17:50:58 2005 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 1C74416A4CE; Sat, 23 Apr 2005 17:50:58 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 891A843D4C; Sat, 23 Apr 2005 17:50:57 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j3NHougl049850; Sat, 23 Apr 2005 13:50:57 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j3NHou8v082939; Sat, 23 Apr 2005 13:50:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D69117306E; Sat, 23 Apr 2005 13:50:55 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050423175055.D69117306E@freebsd-current.sentex.ca> Date: Sat, 23 Apr 2005 13:50:55 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamscanner4 X-Virus-Status: Clean Subject: [releng_5 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Apr 2005 17:50:58 -0000 TB --- 2005-04-23 16:30:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-23 16:30:14 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-04-23 16:30:14 - checking out the source tree TB --- 2005-04-23 16:30:14 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2005-04-23 16:30:14 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-04-23 16:39:30 - building world (CFLAGS=-O -pipe) TB --- 2005-04-23 16:39:30 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-04-23 16:39:30 - /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 >>> stage 5.1: building 32 bit shim libraries TB --- 2005-04-23 17:36:52 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-04-23 17:36:52 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-04-23 17:36:52 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Apr 23 17:36:52 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Apr 23 17:47:11 UTC 2005 TB --- 2005-04-23 17:47:11 - generating LINT kernel config TB --- 2005-04-23 17:47:11 - cd /home/tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/conf TB --- 2005-04-23 17:47:11 - /usr/bin/make -B LINT TB --- 2005-04-23 17:47:11 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-04-23 17:47:11 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2005-04-23 17:47:11 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Apr 23 17:47:11 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/amd64/amd64/src/sys -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/altq -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/pf -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -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 /tinderbox/RELENG_5/amd64/amd64/sr c/sys/dev/acpica/acpi.c In file included from /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/acpica/acpi.c:59: /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/acpica/acpivar.h:409:1: "ACPI_MAX_THREADS" redefined In file included from /tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica/acfreebsd.h:128, from /tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica/acenv.h:208, from /tinderbox/RELENG_5/amd64/amd64/src/sys/contrib/dev/acpica/acpi.h:126, from /tinderbox/RELENG_5/amd64/amd64/src/sys/dev/acpica/acpi.c:58: ./opt_acpi.h:2:1: this is the location of the previous definition *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/obj/amd64/tinderbox/RELENG_5/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. TB --- 2005-04-23 17:50:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-04-23 17:50:55 - ERROR: failed to build lint kernel TB --- 2005-04-23 17:50:55 - tinderbox aborted