From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 15:31:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C2A416A4CE for ; Sun, 21 Nov 2004 15:31:14 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B52D43D45 for ; Sun, 21 Nov 2004 15:31:14 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from [127.0.0.1] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc13) with ESMTP id <200411211531130150010hmae>; Sun, 21 Nov 2004 15:31:14 +0000 Message-ID: <41A0B552.9040901@pythonemproject.com> Date: Sun, 21 Nov 2004 07:33:38 -0800 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20041120011925.GE20068@dragon.nuxi.com> In-Reply-To: <20041120011925.GE20068@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Dude Dude Subject: Re: mobo for amd64 3.2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rob2@pythonemproject.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 15:31:14 -0000 David O'Brien wrote: >On Sat, Nov 20, 2004 at 01:15:09AM +0000, Dude Dude wrote: > > >>hey, i will buy a new amd64bits socket 939, and i would like to know if you >>have good experiences freebsd compatibility with any socket939 board!! >> >> > >Very good. :-) > > > Here very good luck with Abit AV8, although not latest chipset. Has 460W supply, huge fan, 2 SCSI 160 drives, Plextor CDRW drive, coolermaster case. When started up, sounds like u are on the tarmac at an airport, sound just down 20db. I'd like to try to run Grip-GoGo on it and see how fast it will rip a cd. When I had my old Athlon mobo, very high speed chip, it would translate an entire cd's worth of audio to mp3 in 5-10sec. All the rest of the time was spent waiting for cd data to be extracted LOL. Sincerely, Rob. From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 18:07:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2762916A4CE; Sun, 21 Nov 2004 18:07:45 +0000 (GMT) Received: from out009.verizon.net (out009pub.verizon.net [206.46.170.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82A5843D2D; Sun, 21 Nov 2004 18:07:44 +0000 (GMT) (envelope-from andrew.lankford@verizon.net) Received: from [192.168.0.2] ([141.156.50.150]) by out009.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041121180743.MQAH1396.out009.verizon.net@[192.168.0.2]>; Sun, 21 Nov 2004 12:07:43 -0600 Message-ID: <41A0D97A.6020207@verizon.net> Date: Sun, 21 Nov 2004 13:07:54 -0500 From: Andrew Lankford User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amd64@freebsd.org References: <200411190540.iAJ5eb2j096304@freefall.freebsd.org> In-Reply-To: <200411190540.iAJ5eb2j096304@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out009.verizon.net from [141.156.50.150] at Sun, 21 Nov 2004 12:07:43 -0600 cc: Colin Smith cc: Ade Lovett cc: Nicolas Blais Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 18:07:45 -0000 > Now, this could be down to the way I built the miniinst (essentially by > hand-stepping through make release on an x86->amd64 cross-compile -- my > other amd64-based box is completely shot thanks to the local power > company) -- I'd need a native amd64-built miniinst to confirm. Could you possibly pass on a more detailed description of what you did to create your custom miniinst image? Going by the mail on this thread, it doesn't look like anybody has the time/bandwidth to provide a bootable disk image that others can download. I've done a make release (built for i386 on i386) before and cross-compile on both i386, amd64, but creating an amd64 image on an i386 machine (in a clean way) is a protracted PITA, as I don't see how you can create a -RELEASE quality image for amd64 on a plain old i386 box. If us disgruntled Compaq presario owners could contribute towards making a short script for building an experimental boot image on the 386, it would be easier for more folks to test the all the kernel patches/tweaks that have been floating around. Andrew Lankford > > -aDe > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 19:32:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E59F16A4CE for ; Sun, 21 Nov 2004 19:32:07 +0000 (GMT) Received: from hotmail.com (bay17-f37.bay17.hotmail.com [64.4.43.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id E726043D3F for ; Sun, 21 Nov 2004 19:32:06 +0000 (GMT) (envelope-from pheeleep@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 21 Nov 2004 11:32:06 -0800 Message-ID: Received: from 213.22.141.46 by by17fd.bay17.hotmail.msn.com with HTTP; Sun, 21 Nov 2004 19:31:22 GMT X-Originating-IP: [213.22.141.46] X-Originating-Email: [pheeleep@hotmail.com] X-Sender: pheeleep@hotmail.com From: "Dude Dude" To: freebsd-amd64@freebsd.org Date: Sun, 21 Nov 2004 19:31:22 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 21 Nov 2004 19:32:06.0397 (UTC) FILETIME=[C8FF52D0:01C4D000] Subject: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 19:32:07 -0000 hey, i'm buying a new amd64 3500+ and a MSI K8T NEO2-FIR K8T800 PRO SK939 mobo, i have to buy a power supply right ? what should be the model ? thx _________________________________________________________________ MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 20:37:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 028F916A4CE for ; Sun, 21 Nov 2004 20:37:43 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 156B543D45 for ; Sun, 21 Nov 2004 20:37:37 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.208] [213.112.167.208]) by mxfep02.bredband.com with ESMTP id <20041121203733.BUGL6427.mxfep02.bredband.com@[192.168.245.231]>; Sun, 21 Nov 2004 21:37:33 +0100 Message-ID: <41A0FC6D.3090509@bredband.net> Date: Sun, 21 Nov 2004 21:37:01 +0100 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20041024 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dude Dude References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 20:37:43 -0000 Dude Dude wrote: > hey, > > i'm buying a new amd64 3500+ and a MSI K8T NEO2-FIR K8T800 PRO SK939 > mobo, i have to buy a power supply right ? what should be the model ? > > thx > If you want top_of_the_line silent and expensive PSU , probably this one. http://www.qtechnology.net/qt02350gp.htm //Lars From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 20:53:40 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A696516A4CE for ; Sun, 21 Nov 2004 20:53:40 +0000 (GMT) Received: from hotmail.com (bay17-f26.bay17.hotmail.com [64.4.43.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D0C543D3F for ; Sun, 21 Nov 2004 20:53:40 +0000 (GMT) (envelope-from pheeleep@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 21 Nov 2004 12:53:40 -0800 Message-ID: Received: from 213.22.148.76 by by17fd.bay17.hotmail.msn.com with HTTP; Sun, 21 Nov 2004 20:52:22 GMT X-Originating-IP: [213.22.148.76] X-Originating-Email: [pheeleep@hotmail.com] X-Sender: pheeleep@hotmail.com In-Reply-To: <41A0FC6D.3090509@bredband.net> From: "Dude Dude" To: freebsd-amd64@freebsd.org Date: Sun, 21 Nov 2004 20:52:22 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 21 Nov 2004 20:53:40.0101 (UTC) FILETIME=[2DDF4B50:01C4D00C] Subject: Re: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 20:53:40 -0000 I'm confused... Apart from the cpu, i need a power supply AND a cpu coole?? i want something not expensive, but silentiest as possible... thx >From: Lars Tunkrans >To: Dude Dude >CC: freebsd-amd64@freebsd.org >Subject: Re: power supply >Date: Sun, 21 Nov 2004 21:37:01 +0100 > >Dude Dude wrote: >>hey, >> >>i'm buying a new amd64 3500+ and a MSI K8T NEO2-FIR K8T800 PRO SK939 mobo, >>i have to buy a power supply right ? what should be the model ? >> >>thx >> > >If you want top_of_the_line silent and expensive PSU , probably this one. > >http://www.qtechnology.net/qt02350gp.htm > >//Lars _________________________________________________________________ MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 21:17:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3E0416A4CE for ; Sun, 21 Nov 2004 21:17:02 +0000 (GMT) Received: from hotmail.com (bay17-f7.bay17.hotmail.com [64.4.43.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1EA043D46 for ; Sun, 21 Nov 2004 21:17:02 +0000 (GMT) (envelope-from pheeleep@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 21 Nov 2004 13:17:02 -0800 Message-ID: Received: from 213.22.148.76 by by17fd.bay17.hotmail.msn.com with HTTP; Sun, 21 Nov 2004 21:16:31 GMT X-Originating-IP: [213.22.148.76] X-Originating-Email: [pheeleep@hotmail.com] X-Sender: pheeleep@hotmail.com In-Reply-To: <41A0FC6D.3090509@bredband.net> From: "Dude Dude" To: freebsd-amd64@freebsd.org Date: Sun, 21 Nov 2004 21:16:31 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 21 Nov 2004 21:17:02.0434 (UTC) FILETIME=[71BA5420:01C4D00F] Subject: Re: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 21:17:03 -0000 Ok, forget it, i need a power supply for the computer to work... anyone knows a power supply not expensive, and very quiet?? 2. a cpu cooler(i need with amd64 right!?) for 3500+. I want the minium noise possible ... >From: Lars Tunkrans >To: Dude Dude >CC: freebsd-amd64@freebsd.org >Subject: Re: power supply >Date: Sun, 21 Nov 2004 21:37:01 +0100 > >Dude Dude wrote: >>hey, >> >>i'm buying a new amd64 3500+ and a MSI K8T NEO2-FIR K8T800 PRO SK939 mobo, >>i have to buy a power supply right ? what should be the model ? >> >>thx >> > >If you want top_of_the_line silent and expensive PSU , probably this one. > >http://www.qtechnology.net/qt02350gp.htm > >//Lars _________________________________________________________________ MSN Messenger: converse com os seus amigos online. http://messenger.msn.com.br From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 21:20:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3E9416A4CE for ; Sun, 21 Nov 2004 21:20:46 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A79143D5A for ; Sun, 21 Nov 2004 21:20:45 +0000 (GMT) (envelope-from A.deGroot@cs.ru.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/4.23) with ESMTP id iALLKhhn017561; Sun, 21 Nov 2004 22:20:43 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Sun, 21 Nov 2004 22:20:40 +0100 User-Agent: KMail/1.7.50 References: In-Reply-To: Organization: University of Nijmegen MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411212220.40806.adridg@cs.kun.nl> cc: Dude Dude Subject: Re: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 21:20:46 -0000 On Sunday 21 November 2004 21:52, Dude Dude wrote: > I'm confused... > Apart from the cpu, i need a power supply AND a cpu coole?? > > i want something not expensive, but silentiest as possible... > thx Dude, this isn't really the list for basic I-want-to-build-a-computer advice, it's a list for questions specific to the use of FreeBSD on amd64 (and possibly 64-bit Intel processors, with which I'm not familiar). If you want a complete checklist of parts you will need to build a computer, here: 1) A box to put it in. This is often called a "case", but can be a carboard box for all that the machine really cares about it. 2) A power supply, to provide power to the computer. While power is often called "juice", Snapple just won't cut it. 3) A motherboard, to put inside the case and attach the actual computery bits to. 4) A CPU, or "brain" for the machine. This is installed on the motherboard. 5) Memory for the machine. This is often sold as "DIMMs", but don't be fooled, they're quite smart, and will refuse to operate if you don't get the right kind or speed. Check the compatibility list of your motherboard vendor. For consumer-grade amd64 boards, there are usually only 3 DIMM slots available, and populating all three causes a speed degradation -- personally I'd aim for 2x512M PC-3200. 6) A CPU cooler (HSF, for Heat-Sink and Fan), which will keep your CPU from melting and dribbling through the case and into the ground, where it will melt a hole straight to the earth's core just like on Three Mile Island. Depending on the uses you want to make of the machine, you may also want a keyboard, mouse, monitor, video card. Sound cards and networking devices are often found on-board the motherboard and needn't be purchased separately anymore, unless you have special needs (quality audio comes to mind). Oooh, a hard-drive and CD drive are useful, for installing FreeBSD amd64 5.3-R, for which ISO's are available from ftp.freebsd.org. Hope that helps, [ade] From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 21 21:42:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2457216A4CE for ; Sun, 21 Nov 2004 21:42:59 +0000 (GMT) Received: from phoenix.severttk.ru (phoenix.severttk.ru [80.92.0.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83F7843D55 for ; Sun, 21 Nov 2004 21:42:58 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from phoenix.severttk.ru (localhost [127.0.0.1]) by phoenix.severttk.ru (Postfix) with SMTP id AE969A924 for ; Mon, 22 Nov 2004 00:42:57 +0300 (MSK) Received: from proxy.km.vibrators.ru (vlan101-sv-yar03ra.severttk.ru [80.92.2.130]) by phoenix.severttk.ru (Postfix) with ESMTP id 6D2EBA915 for ; Mon, 22 Nov 2004 00:42:48 +0300 (MSK) Received: from 192.168.1.90 (reaper-home [192.168.1.90] (may be forged)) by proxy.km.vibrators.ru (8.13.1/8.13.1) with ESMTP id iALLjTX8036101; Mon, 22 Nov 2004 00:45:29 +0300 (MSK) (envelope-from liettneff@bk.ru) Date: Mon, 22 Nov 2004 00:42:54 +0300 From: Michael Lednev X-Mailer: The Bat! (v2.01) Business Organization: none X-Priority: 3 (Normal) Message-ID: <159392064921.20041122004254@bk.ru> To: "Dude Dude" In-Reply-To: References: <41A0FC6D.3090509@bredband.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re[2]: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: liettneff List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 21:42:59 -0000 Hi, Dude. 22 Nov 2004, 0:16:31: DD> Ok, forget it, i need a power supply for the computer to work... anyone DD> knows a power supply not expensive, and very quiet?? DD> 2. a cpu cooler(i need with amd64 right!?) for 3500+. 2 words: Zalman, Zalman DD> I want the minium noise possible ... sure ;) they are not very expensive (maybe very expensive, it depends...), but noise level is very comfortable. -- Michael mailto:liettneff@bk.ru From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 00:33:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E16216A4CE; Mon, 22 Nov 2004 00:33:11 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23E1743D45; Mon, 22 Nov 2004 00:33:11 +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.1/8.13.1) with ESMTP id iAM0XAwm025777; Sun, 21 Nov 2004 19:33:10 -0500 (EST) (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.1/8.13.1) with ESMTP id iAM0X9pv080164; Sun, 21 Nov 2004 19:33:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A82897306E; Sun, 21 Nov 2004 19:33:09 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041122003309.A82897306E@freebsd-current.sentex.ca> Date: Sun, 21 Nov 2004 19:33:09 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean 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: Mon, 22 Nov 2004 00:33:11 -0000 TB --- 2004-11-21 23:14:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-21 23:14:21 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2004-11-21 23:14:21 - checking out the source tree TB --- 2004-11-21 23:14:21 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2004-11-21 23:14:21 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2004-11-21 23:23:22 - building world (CFLAGS=-O -pipe) TB --- 2004-11-21 23:23:22 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-11-21 23:23:22 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-22 00:15:22 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 00:15:22 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-11-22 00:15:22 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 22 00:15:22 UTC 2004 >>> 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 Mon Nov 22 00:24:29 UTC 2004 TB --- 2004-11-22 00:24:29 - generating LINT kernel config TB --- 2004-11-22 00:24:29 - cd /home/tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/conf TB --- 2004-11-22 00:24:29 - /usr/bin/make -B LINT TB --- 2004-11-22 00:24:29 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2004-11-22 00:24:29 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-11-22 00:24:29 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 22 00:24:29 UTC 2004 >>> 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 [...] /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `bus_dmamap_load': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:720: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `bus_dmamap_load_mbuf': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:777: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:837: error: `KTR_BUSDMA' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c: In function `_bus_dmamap_sync': /tinderbox/RELENG_5/amd64/amd64/src/sys/amd64/amd64/busdma_machdep.c:868: error: `KTR_BUSDMA' undeclared (first use in this function) *** 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 --- 2004-11-22 00:33:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-22 00:33:09 - ERROR: failed to build lint kernel TB --- 2004-11-22 00:33:09 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 02:03:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4E3D16A4CE for ; Mon, 22 Nov 2004 02:03:07 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F4A443D41 for ; Mon, 22 Nov 2004 02:03:07 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iAM236Cf012790; Sun, 21 Nov 2004 18:03:06 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iAM236sU012789; Sun, 21 Nov 2004 18:03:06 -0800 (PST) (envelope-from obrien) Date: Sun, 21 Nov 2004 18:03:05 -0800 From: "David O'Brien" To: Dude Dude Message-ID: <20041122020305.GA12737@dragon.nuxi.com> References: <41A0FC6D.3090509@bredband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 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 cc: freebsd-amd64@freebsd.org Subject: Re: power supply X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 02:03:07 -0000 On Sun, Nov 21, 2004 at 09:16:31PM +0000, Dude Dude wrote: > Ok, forget it, i need a power supply for the computer to work... anyone > knows a power supply not expensive, and very quiet?? > > 2. a cpu cooler(i need with amd64 right!?) for 3500+. > I want the minium noise possible ... To make things simple I would buy an AMD PIB (processor in a box) as it comes with a suitable heatsink+fan and comes with a 3 year warranty. The fans AMD uses with Athlon64 PIB's are quite quiet. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 02:13:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2236516A4CE for ; Mon, 22 Nov 2004 02:13:30 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECCFC43D48 for ; Mon, 22 Nov 2004 02:13:29 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iAM2DMKV013101; Sun, 21 Nov 2004 18:13:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iAM2DHid013095; Sun, 21 Nov 2004 18:13:17 -0800 (PST) (envelope-from obrien) Date: Sun, 21 Nov 2004 18:13:16 -0800 From: "David O'Brien" To: Lars Tunkrans Message-ID: <20041122021316.GC12737@dragon.nuxi.com> References: <419F08C5.2080100@bredband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419F08C5.2080100@bredband.net> User-Agent: Mutt/1.4.1i 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 cc: freebsd-amd64@freebsd.org Subject: Re: cputype FX-53 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 02:13:30 -0000 On Sat, Nov 20, 2004 at 10:05:09AM +0100, Lars Tunkrans wrote: > Gert Cuykens wrote: > >Hi whats the cputype of a FX-53 please > > The FX-53 is an overclock-able, 2.4 Ghz, 1MB 2nd-levelcache, AMD64 Opteron > 150. > The FX-55 is the same but runs at 2.6 Ghz nominal speed. The FX-53 940-pin FX-53 is mostly an Opteron 150. The FX-55 is 939-pin only (there is also a 939-pin FX-53 ADAFX53DEP5AS). And thus won't work in the same motherboard as the Opteron and original FX-53. The CPU type for all of these is AMD64 64-bit. They all can also run FreeBSD/i386 extremely well. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 02:58:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB9C216A4CE for ; Mon, 22 Nov 2004 02:58:49 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2BAB43D48 for ; Mon, 22 Nov 2004 02:58:49 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so99689cwc for ; Sun, 21 Nov 2004 18:58:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding; b=Wj3hpCnxTrxAzYQaitubImiTIGc5C6Tzo3oyf6UAznRpHyryWFUgdJv27YFrJOZGyCHLc2K4DhknONDHrApxYtTjodsUhyIHP8I/K/V0AGTZSKdssa6JR8j3m8Q3JE1+X1mF5UEIhLee4tTylbKLPOaVd1JYlBNM02DLR2d8iaY= Received: by 10.11.122.5 with SMTP id u5mr67803cwc; Sun, 21 Nov 2004 18:58:49 -0800 (PST) Received: from ?192.168.102.103? ([67.160.118.158]) by smtp.gmail.com with ESMTP id v71sm18207cwb; Sun, 21 Nov 2004 18:58:49 -0800 (PST) Message-ID: <41A155DF.3070701@gmail.com> Date: Sun, 21 Nov 2004 18:58:39 -0800 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: R3000Z ISO 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, 22 Nov 2004 02:58:50 -0000 Alright, I'm building an ISO that should be bootable, from the source tree right around the 6-CURRENT fork. I simply added an if (1) return 0; to both offending functions. The image will be located at http://zidane.evogaming.net/miniinst-r3000.iso at some point tonight. I beg of you, don't use that URL for wide distribution, I'm hoping to facilitate a fix making -CURRENT sometime soon, and then we can all use snapshots. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 05:19:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60A3716A4CE for ; Mon, 22 Nov 2004 05:19:28 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 319C843D4C for ; Mon, 22 Nov 2004 05:19:28 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id q44so69466cwc for ; Sun, 21 Nov 2004 21:19:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding; b=Gd73Lz2XlgNvw1E9Q+aLFUyfIuBtRcnHBHFKuCgZCGSMzign6Vxsv4WiTpFxFliUunmQEKKA4i9yN0NKarQO3pFAzMItjxc6lTqMNVjdJ/sY5fgBwV138Nq85oONusVHmeiLFCj2poSfjfZc6ENOKGLlj+ViXeJvj+ziddsRb60= Received: by 10.11.99.1 with SMTP id w1mr109666cwb; Sun, 21 Nov 2004 21:19:27 -0800 (PST) Received: from ?192.168.102.103? ([67.160.118.158]) by smtp.gmail.com with ESMTP id o9sm24558cwc; Sun, 21 Nov 2004 21:19:27 -0800 (PST) Message-ID: <41A176D5.6070806@gmail.com> Date: Sun, 21 Nov 2004 21:19:17 -0800 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: R3000Z ISO 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, 22 Nov 2004 05:19:28 -0000 The R3000Z ISO is up @ http://zidane.evogaming.net/miniinst-r3000.iso Its some version of 5-CURRENT.... I'm not sure which. You must boot with ACPI disabled. Sorry I don't have more information on it, but the machine I ran make release on, wasn't the one I thought it was. It should work though. I tested it here, and it boots great. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 05:21:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E97B816A4CF for ; Mon, 22 Nov 2004 05:21:52 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B74643D6B for ; Mon, 22 Nov 2004 05:21:50 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id q44so69513cwc for ; Sun, 21 Nov 2004 21:21:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding; b=Prky0lvsiHSOFiyqbQha7y1a2UdluN4dZoLlg4ts2q5TBniItl/4D+6D/flttb3+mcnRxolo+c+dRTqIcjgaMMTWD5lP+VlrCJfVzUEFVZniWLZ3xPGaUKELreod4+WJrnxu0XjKujFLNL/2SA7N7ogFMIXpTKFMc/RNlUE5hf4= Received: by 10.11.116.54 with SMTP id o54mr109454cwc; Sun, 21 Nov 2004 21:21:49 -0800 (PST) Received: from ?192.168.102.103? ([67.160.118.158]) by smtp.gmail.com with ESMTP id o9sm24663cwc; Sun, 21 Nov 2004 21:21:49 -0800 (PST) Message-ID: <41A17764.4020304@gmail.com> Date: Sun, 21 Nov 2004 21:21:40 -0800 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: R3000Z ISO 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, 22 Nov 2004 05:21:53 -0000 On another note, this was built from i386 using make release TARGET=amd64 TARGET_ARCH=amd64, with no cvsup, and no docs.Like I said, on my laptop, it seems to work fine. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 08:34:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1352416A4CE for ; Mon, 22 Nov 2004 08:34:17 +0000 (GMT) Received: from mail.uk.psi.com (mail.uk.psi.com [154.8.2.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8866243D31 for ; Mon, 22 Nov 2004 08:34:16 +0000 (GMT) (envelope-from alan.barrow@psinet.telstra.co.uk) Received: from [154.8.26.81] (helo=psinet.telstra.co.uk) by mail.uk.psi.com with esmtp (Exim 4.41) id 1CW9eH-0002hn-3e; Mon, 22 Nov 2004 08:34:13 +0000 Message-ID: <41A1A467.9000404@psinet.telstra.co.uk> Date: Mon, 22 Nov 2004 08:33:43 +0000 From: alan barrow Organization: PSINet a telstra company User-Agent: Mozilla Thunderbird 0.5 (Macintosh/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Claus Guttesen References: <20041119163615.63809.qmail@web14107.mail.yahoo.com> In-Reply-To: <20041119163615.63809.qmail@web14107.mail.yahoo.com> Content-Type: multipart/mixed; boundary="------------000003000302010209070403" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-amd64@freebsd.org cc: Palle Girgensohn Subject: Re: Dell 2850 & amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: alan.barrow@psinet.telstra.co.uk List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 08:34:17 -0000 This is a multi-part message in MIME format. --------------000003000302010209070403 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Java on amd64 ? think you will have to go i386. Claus Guttesen wrote: >>The machine shall be a general utility system, >>running email (cyrus) and >>web (apache), postgresql and php, some simple java >>(tomcat). >>Before I build all ports needed, is there anything I >>need to set to make >>the ports build 64 bit? All I've done now is to get >>the kernel built in >>64-bit mode. Is that enough to make all ports built >>in 64 bit? Shall I set >>CPUTYPE to something? The CPUs are two Xeon, is that >>p4? >> >> > >I omitted CPUTYPE in /etc/make.conf. Other than that, >you just have to check CPUTYPE in a shell. > > > >>Is it even wise to use amd64? Is it stable enough? >>Docs say so, but >>browsning this list gives me second thoughts? >> >> > >I have a 2850 running postgresql, sometimes heavily >loaded, but works like a charm besides that. > >There is a description on how to get java working on >this list (as far as I remember). > > > >>Perhaps this is all FAQ and RTFM, but I've searched >>the net a bit about >>this, couldn't find the right answers. Sorry, I'm >>still a newbie in >>AMD64-land. :)= >> >> > >The amd-port appears to be slightly faster than it's >i386-cousin on same hardware. > >Claus > >_______________________________________________ >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" > > > --------------000003000302010209070403-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 08:48:20 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21F7816A4CE for ; Mon, 22 Nov 2004 08:48:20 +0000 (GMT) Received: from mail.uk.psi.com (mail.uk.psi.com [154.8.2.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0A0743D54 for ; Mon, 22 Nov 2004 08:48:19 +0000 (GMT) (envelope-from alan.barrow@psinet.telstra.co.uk) Received: from [154.8.26.81] (helo=psinet.telstra.co.uk) by mail.uk.psi.com with esmtp (Exim 4.41) id 1CW9ru-0003Wt-6j; Mon, 22 Nov 2004 08:48:18 +0000 Message-ID: <41A1A7B3.7060908@psinet.telstra.co.uk> Date: Mon, 22 Nov 2004 08:47:47 +0000 From: alan barrow Organization: PSINet a telstra company User-Agent: Mozilla Thunderbird 0.5 (Macintosh/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Palle Girgensohn References: <66F48C43D96D2D4253E5FF62@palle.girgensohn.se> In-Reply-To: <66F48C43D96D2D4253E5FF62@palle.girgensohn.se> Content-Type: multipart/mixed; boundary="------------030305050909070508040301" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-amd64@freebsd.org Subject: Re: jdk @ amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: alan.barrow@psinet.telstra.co.uk List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2004 08:48:20 -0000 This is a multi-part message in MIME format. --------------030305050909070508040301 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit You need the i386 build, no one has ported it yet. Palle Girgensohn wrote: > Hi! > > I've been trying to dig the archives for info about running a native > JDK 1.4 on an AMD64 system (Dell 2850, really "EM64T"?). > > Can anyone get me up to speed with how this is done, if it is > possible? Do I need lib32 stuff to run the jdk, and is that what the > src/tools/lib32/build32.sh script creates? Is it not possible to run > the JDK in "native" AMD64? > > Thanks > Palle > > _______________________________________________ > 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" > --------------030305050909070508040301-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 22 11:01:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C81316A4CE for ; Mon, 22 Nov 2004 11:01:55 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 140DB43D67 for ; Mon, 22 Nov 2004 11:01:55 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iAMB1sms075897 for ; Mon, 22 Nov 2004 11:01:54 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iAMB1sL9075891 for freebsd-amd64@freebsd.org; Mon, 22 Nov 2004 11:01:54 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 22 Nov 2004 11:01:54 GMT Message-Id: <200411221101.iAMB1sL9075891@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, 22 Nov 2004 11:01:55 -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 [2004/11/06] amd64/73603 amd64 kernel build amd64 fails when device ath 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/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z 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/04] amd64/72333 amd64 vinum doesn't scan for drives on slices o 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 12 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/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve a [2004/09/12] amd64/71674 amd64 static libraries cannot be linked when bu o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 11:45:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEC6616A4CE for ; Tue, 23 Nov 2004 11:45:07 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9805F43D55 for ; Tue, 23 Nov 2004 11:45:06 +0000 (GMT) (envelope-from a.degroot@science.ru.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=odin.cs.kun.nl) by pandora.cs.kun.nl (8.12.10/4.23) with ESMTP id iANBj5tx029225 for ; Tue, 23 Nov 2004 12:45:05 +0100 (MET) Date: Tue, 23 Nov 2004 12:45:05 +0100 (MET) From: a.degroot@science.ru.nl X-X-Sender: adridg@odin.cs.kun.nl To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Cross-compiling on x86 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: a.degroot@science.ru.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 11:45:07 -0000 For various large compiles (KDE, mostly), I'm looking into setting up a compile farm to produce amd64 inaries. A basic distcc setup, to start with (icecream, the teambuilder-alike with some pretty neat features, is still horribly linux-specific and I need to fix that some time), but I'm somewhat lacking on the number-of-amd64 machines front, as in I've got 1. So I got to thinking: why should the x86 machines in the house get a break? They should be able to produce amd64 code at the least. The system gcc on 5.3-R on x86 doesn't like -m64: -bash-2.05b$ g++ -c -m64 t.cc t.cc:1: sorry, unimplemented: 64-bit mode not compiled in which is unfortunate, because if I understand correctly, that's the only flag I would really need to use to make gcc on x86en produce code for amd64 (ie. x86box$ g++ -m64 t.cc amd64box$ g++ t.cc should produce identical results?). Information on building a cross-compiling gcc is not thick on the ground (at least, not for a trivial setup like this -- for weird embedded targets there seems to be enough). Does anyone have a hint on how to set this up -- or just plain build a gcc 3.4.3 that outputs amd64 .o files -- so my x86en can compile for their new 64 bit overlords? PS. Yes, I realise that using a 32-bit userland with LIB32 would allow me to share the compiles and use just the plain system gcc on the x86 machines, but as of yet not all possible 64-bit errors have been removed from KDE, so I do want to be building in 64-bit mode. -- As of September 1st, 2004, the University of Nijmegen will _still_ be the University of Nijmegen, but with a different nonsensical adjective in front. Reach me at groot@kde.org instead. GPG FEA2 A3FE From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 13:56:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BC2216A4CE for ; Tue, 23 Nov 2004 13:56:39 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C9FF43D48 for ; Tue, 23 Nov 2004 13:56:39 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so9244cwc for ; Tue, 23 Nov 2004 05:56:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding; b=b6NjK84PtROqKEnnV8bTOHmQvMHksNAlO+2urDpsHYnjqK1GAfjXYDk68YelT+DTOE6XwH5lt95PJdCpRWNBa+StrcTQz8BvANZRx2Pz2oNXfPC8g4LDU90H+Hu/e+CXLsAfW1IYuZXS6Lno5Fx8FScbW+g7k53GvysS9pTvjT8= Received: by 10.11.100.61 with SMTP id x61mr12026cwb; Tue, 23 Nov 2004 05:56:38 -0800 (PST) Received: from ?192.168.102.104? ([67.160.118.158]) by smtp.gmail.com with ESMTP id v71sm5758cwb; Tue, 23 Nov 2004 05:56:38 -0800 (PST) Message-ID: <41A2D10B.7030108@gmail.com> Date: Tue, 23 Nov 2004 05:56:27 +0000 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (X11/20041122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 3000Z Bugs Noticed Now That Its Running 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, 23 Nov 2004 13:56:39 -0000 Well, now I hope we have a larger base for 3000Z work, so I figured I'd post the bugs I've run into so far, in no particular order. If you want more information on one, feel free to drop me a line, just posting this so other people know what they're getting in to. #1. No ACPI, I'm working on this one now #2. Kernel Panic when you close the lid. Goes away when ACPI is enabled, but then the boot gets stuck. #3. Loss of usable LCD display when you switch from X back to a normal terminal. Goes into what looks like an old TV with its vertical sync fried. Beyond those 3 things, which I think extend to most mobiles before they get some attention, its golden. I haven't tried nvidia's own drivers yet, or DRI... we'll see soon. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 15:53:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16DBC16A4CE for ; Tue, 23 Nov 2004 15:53:25 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57E9143D46 for ; Tue, 23 Nov 2004 15:53:22 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iANFrLwe090237; Tue, 23 Nov 2004 10:53:21 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Tue, 23 Nov 2004 10:53:16 -0500 User-Agent: KMail/1.6.2 References: <41A2D10B.7030108@gmail.com> In-Reply-To: <41A2D10B.7030108@gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231053.17874.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: 3000Z Bugs Noticed Now That Its Running 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, 23 Nov 2004 15:53:25 -0000 On Tuesday 23 November 2004 12:56 am, Astrodog wrote: > Well, now I hope we have a larger base for 3000Z work, so I figured > I'd post the bugs I've run into so far, in no particular order. If > you want more information on one, feel free to drop me a line, just > posting this so other people know what they're getting in to. > > #1. No ACPI, I'm working on this one now > > #2. Kernel Panic when you close the lid. Goes away when ACPI is > enabled, but then the boot gets stuck. When ACPI is enabled, it works fine but the keyboard doesn't work AFAIK, i. e., PS/2 port is not probed. However you can login from network, which is bad for laptop. :-( > #3. Loss of usable LCD display when you switch from X back to a > normal terminal. Goes into what looks like an old TV with its > vertical sync fried. This is well known bug in Xorg driver. https://bugs.freedesktop.org/show_bug.cgi?id=1549 nVidia's binary driver doesn't have this bug but it is not available for FreeBSD/amd64 yet. > Beyond those 3 things, which I think extend to most mobiles before > they get some attention, its golden. I haven't tried nvidia's own > drivers yet, or DRI... we'll see soon. DRI doesn't work because there is no open source driver. http://dri.sourceforge.net/cgi-bin/moin.cgi/nVidia?action=highlight&value=CategoryHardwareVendor nVidia's own driver works fine for FreeBSD/i386 though. Jung-uk Kim > --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 16:58:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76A9716A4CE for ; Tue, 23 Nov 2004 16:58:06 +0000 (GMT) Received: from hotmail.com (bay17-f27.bay17.hotmail.com [64.4.43.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E10243D4C for ; Tue, 23 Nov 2004 16:58:06 +0000 (GMT) (envelope-from pheeleep@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 23 Nov 2004 08:58:03 -0800 Message-ID: Received: from 213.22.140.103 by by17fd.bay17.hotmail.msn.com with HTTP; Tue, 23 Nov 2004 16:57:08 GMT X-Originating-IP: [213.22.140.103] X-Originating-Email: [pheeleep@hotmail.com] X-Sender: pheeleep@hotmail.com From: "Dude Dude" To: freebsd-amd64@freebsd.org Date: Tue, 23 Nov 2004 16:57:08 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 23 Nov 2004 16:58:03.0271 (UTC) FILETIME=[987DB970:01C4D17D] Subject: amd64 ram system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 16:58:06 -0000 Something i read today scared me, i already spend a lot of money in my system (amd64), witch comes tomorrow, and now, i read somewhere that amd64 mobos (MSI K8T NEO2-FIR is mine) only allows dual memory collocation. To have my system working i have to order 2 simetric DDR Dimm's?? i only order one 512MB Dimm DDR '184 pin' 400mHz (samsung) .... i was thinking in combining with other 512MB Dimm DDR Kingstone that i have here, but it is 133mHz, what sould i do ?? _________________________________________________________________ MSN Messenger: converse com os seus amigos online. http://messenger.msn.com.br From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 17:02:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5832516A4CE for ; Tue, 23 Nov 2004 17:02:22 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3466943D58 for ; Tue, 23 Nov 2004 17:02:22 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id w67so135186cwb for ; Tue, 23 Nov 2004 09:02:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=gRYBTIzuKfQZpd11tsomnXQx38OmjU31gwZ3GdQ+1HneNd40AzlXMojTMIX9L0hldxTBVBURpazqkLCT/qvu2vG+VEX+RPpynUw+CVxKpd2/Vsy8Xa01n+MoFSfHWiZGh1CQAqj+VRjLOTrkTV7XqteovDEoMp+KT4/Ph6Sem/Q= Received: by 10.11.117.29 with SMTP id p29mr480024cwc; Tue, 23 Nov 2004 09:02:22 -0800 (PST) Received: from ?192.168.102.104? ([67.160.118.158]) by smtp.gmail.com with ESMTP id p77sm24269cwc; Tue, 23 Nov 2004 09:02:21 -0800 (PST) Message-ID: <41A2FC92.3010506@gmail.com> Date: Tue, 23 Nov 2004 09:02:10 +0000 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (X11/20041122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dude Dude , freebsd-amd64@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: amd64 ram system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 17:02:22 -0000 Dude Dude wrote: > Something i read today scared me, i already spend a lot of money in my > system (amd64), witch comes tomorrow, and now, i read somewhere that > amd64 mobos (MSI K8T NEO2-FIR is mine) only allows dual memory > collocation. > > To have my system working i have to order 2 simetric DDR Dimm's?? > > i only order one 512MB Dimm DDR '184 pin' 400mHz (samsung) .... > i was thinking in combining with other 512MB Dimm DDR Kingstone that i > have here, but it is 133mHz, what sould i do ?? > > _________________________________________________________________ > MSN Messenger: converse com os seus amigos online. > http://messenger.msn.com.br > > _______________________________________________ > 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" > Quite simply, you should limit your memory to 266 DDR. I suspect another issue will arise though. Opterons require Registered, ECC memory. and the K8T NEO is Opteron/940, isn't it? (I don't remember offhand) From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 17:28:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF83416A4CE for ; Tue, 23 Nov 2004 17:28:01 +0000 (GMT) Received: from hotmail.com (bay17-f39.bay17.hotmail.com [64.4.43.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id C604943D2D for ; Tue, 23 Nov 2004 17:28:01 +0000 (GMT) (envelope-from pheeleep@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 23 Nov 2004 09:28:01 -0800 Message-ID: Received: from 213.22.140.103 by by17fd.bay17.hotmail.msn.com with HTTP; Tue, 23 Nov 2004 17:27:35 GMT X-Originating-IP: [213.22.140.103] X-Originating-Email: [pheeleep@hotmail.com] X-Sender: pheeleep@hotmail.com In-Reply-To: <41A2FC92.3010506@gmail.com> From: "Dude Dude" To: freebsd-amd64@freebsd.org Date: Tue, 23 Nov 2004 17:27:35 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 23 Nov 2004 17:28:01.0519 (UTC) FILETIME=[C85497F0:01C4D181] Subject: Re: amd64 ram system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 17:28:02 -0000 No, it's skt939 athlon64. >Quite simply, you should limit your memory to 266 DDR. what do you mean ?? >From: Astrodog >To: Dude Dude , freebsd-amd64@freebsd.org >Subject: Re: amd64 ram system >Date: Tue, 23 Nov 2004 09:02:10 +0000 >>_______________________________________________ >>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" >> >Quite simply, you should limit your memory to 266 DDR. > >I suspect another issue will arise though. Opterons require Registered, ECC >memory. and the K8T NEO is Opteron/940, isn't it? (I don't remember >offhand) _________________________________________________________________ MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 20:00:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A454716A4CF for ; Tue, 23 Nov 2004 20:00:58 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FE1C43D6E for ; Tue, 23 Nov 2004 20:00:57 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 7344 invoked from network); 23 Nov 2004 20:00:56 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 20:00:56 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANK0msL037155; Tue, 23 Nov 2004 15:00:49 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: powerpc@FreeBSD.org, amd64@FreeBSD.org, ia64@FreeBSD.org Date: Tue, 23 Nov 2004 15:00:55 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411231500.55841.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Robert Watson Subject: Patch to optimize "bare" critical sections 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, 23 Nov 2004 20:00:59 -0000 Basically, I have a patch to divorce the interrupt disable/deferring to only happen inside of spinlocks using a new spinlock_enter/exit() API (where a spinlock_enter/exit includes a critical section as well) but that plain critical sections won't have to do such a thing. I've tested it on i386, alpha, and sparc64 already, and it has also been tested on arm. I'm unable to get a cross-built powerpc kernel to link (linker dies with a signal 6), but the compile did finish. I have cross-compiled ia64 and amd64 successfully, but have not run tested due to ENOHARDWARE. So, I would appreciate it if a few folks could try the patch out on ppc, ia64, and amd64 to make sure it works ok. Thanks. http://www.FreeBSD.org/~jhb/spinlock.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 21:36:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E066A16A4CF for ; Tue, 23 Nov 2004 21:36:45 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E4E343D41 for ; Tue, 23 Nov 2004 21:36:45 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 15071 invoked from network); 23 Nov 2004 21:36:45 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 23 Nov 2004 21:36:44 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iANLaXfM037718; Tue, 23 Nov 2004 16:36:41 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: powerpc@FreeBSD.org, amd64@FreeBSD.org, ia64@FreeBSD.org, Robert Watson Date: Tue, 23 Nov 2004 16:31:00 -0500 User-Agent: KMail/1.6.2 References: <200411231500.55841.jhb@FreeBSD.org> In-Reply-To: <200411231500.55841.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411231631.00945.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: Patch to optimize "bare" critical sections 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, 23 Nov 2004 21:36:46 -0000 On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: > Basically, I have a patch to divorce the interrupt disable/deferring to > only happen inside of spinlocks using a new spinlock_enter/exit() API > (where a spinlock_enter/exit includes a critical section as well) but that > plain critical sections won't have to do such a thing. I've tested it on > i386, alpha, and sparc64 already, and it has also been tested on arm. I'm > unable to get a cross-built powerpc kernel to link (linker dies with a > signal 6), but the compile did finish. I have cross-compiled ia64 and > amd64 > successfully, but have not run tested due to ENOHARDWARE. So, I would > appreciate it if a few folks could try the patch out on ppc, ia64, and > amd64 to make sure it works ok. Thanks. > > http://www.FreeBSD.org/~jhb/spinlock.patch *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch Sorry about that. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 23 23:47:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 033BB16A4CE for ; Tue, 23 Nov 2004 23:47:31 +0000 (GMT) Received: from salvador.pacific.net.sg (salvador.pacific.net.sg [203.120.90.219]) by mx1.FreeBSD.org (Postfix) with SMTP id D312643D1F for ; Tue, 23 Nov 2004 23:47:29 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 2885 invoked from network); 23 Nov 2004 23:47:28 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by salvador with SMTP; 23 Nov 2004 23:47:28 -0000 Received: from [192.168.0.109] ([210.24.246.156]) by maxwell2.pacific.net.sg with ESMTP <20041123234728.XNKP12758.maxwell2.pacific.net.sg@[192.168.0.109]>; Wed, 24 Nov 2004 07:47:28 +0800 Message-ID: <41A3CC4B.90603@pacific.net.sg> Date: Wed, 24 Nov 2004 07:48:27 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dude Dude 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: amd64 ram system X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 23:47:31 -0000 Hi, Dude Dude wrote: > No, it's skt939 athlon64. > >> Quite simply, you should limit your memory to 266 DDR. > > what do you mean ?? > Your system will work but at a lower speed. >> I suspect another issue will arise though. Opterons require >> Registered, ECC memory. and the K8T NEO is Opteron/940, isn't it? (I >> don't remember offhand) > But only after you checked for this condition. Erich From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 03:26:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8502616A4CE; Wed, 24 Nov 2004 03:26:22 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB06943D58; Wed, 24 Nov 2004 03:26:21 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iAO3QLDX020560; Tue, 23 Nov 2004 19:26:21 -0800 (PST) (envelope-from marcel@xcllnt.net) In-Reply-To: <200411231631.00945.jhb@FreeBSD.org> References: <200411231500.55841.jhb@FreeBSD.org> <200411231631.00945.jhb@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Tue, 23 Nov 2004 19:26:21 -0800 To: John Baldwin X-Mailer: Apple Mail (2.619) cc: amd64@freebsd.org cc: powerpc@freebsd.org cc: ia64@freebsd.org Subject: Re: Patch to optimize "bare" critical sections 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, 24 Nov 2004 03:26:22 -0000 On Nov 23, 2004, at 1:31 PM, John Baldwin wrote: > On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: >> Basically, I have a patch to divorce the interrupt disable/deferring >> to >> only happen inside of spinlocks using a new spinlock_enter/exit() API >> (where a spinlock_enter/exit includes a critical section as well) but >> that >> plain critical sections won't have to do such a thing. I've tested >> it on >> i386, alpha, and sparc64 already, and it has also been tested on arm. >> I'm >> unable to get a cross-built powerpc kernel to link (linker dies with a >> signal 6), but the compile did finish. I have cross-compiled ia64 and >> amd64 >> successfully, but have not run tested due to ENOHARDWARE. So, I would >> appreciate it if a few folks could try the patch out on ppc, ia64, and >> amd64 to make sure it works ok. Thanks. >> >> http://www.FreeBSD.org/~jhb/spinlock.patch > > *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch > > Sorry about that. The patch doesn't apply cleanly. Can you create a patch against HEAD and not your lock branch? Rejects are: Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |--- //depot/projects/smpng/sys/kern/kern_mutex.c 2004/11/15 20:20:33 |+++ //depot/user/jhb/lock/kern/kern_mutex.c 2004/11/17 16:42:34 -------------------------- Patching file sys/kern/kern_mutex.c using Plan A... Hunk #1 failed at 602. Hunk #2 failed at 630. 2 out of 2 hunks failed--saving rejects to sys/kern/kern_mutex.c.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |--- //depot/projects/smpng/sys/sys/mutex.h 2004/08/18 16:47:14 |+++ //depot/user/jhb/lock/sys/mutex.h 2004/11/04 23:48:43 -------------------------- Patching file sys/sys/mutex.h using Plan A... Hunk #1 succeeded at 164 (offset -3 lines). Hunk #2 failed at 176. Hunk #3 succeeded at 194 (offset -11 lines). Hunk #4 succeeded at 212 with fuzz 2 (offset -4 lines). Hunk #5 failed at 220. 2 out of 5 hunks failed--saving rejects to sys/sys/mutex.h.rej -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 05:13:05 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 783D216A4CE for ; Wed, 24 Nov 2004 05:13:05 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F1F243D46 for ; Wed, 24 Nov 2004 05:13:05 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so39450cwc for ; Tue, 23 Nov 2004 21:13:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=G4xhKXbF8uw8yLX8p6zcjcSkkgAwnUm444guyXG15atbp3Pb1VN0AgkTvYoMuz/3zuVwj4DkgsxKy2wNFJN8AeeATWWcp72s13suaDLscCH8O/JFwx/glIIJfCjw3ht3BCJo+rBy6m9SyI5328PsXguOAdz008D86UxiYbTqhjo= Received: by 10.11.122.45 with SMTP id u45mr15453cwc; Tue, 23 Nov 2004 21:13:05 -0800 (PST) Received: from ?192.168.102.104? ([67.160.118.158]) by smtp.gmail.com with ESMTP id v71sm1572cwb; Tue, 23 Nov 2004 21:13:05 -0800 (PST) Message-ID: <41A3A7D9.7090009@gmail.com> Date: Tue, 23 Nov 2004 21:12:57 +0000 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (X11/20041122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <200411231500.55841.jhb@FreeBSD.org> <200411231631.00945.jhb@FreeBSD.org> <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> In-Reply-To: <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Patch to optimize "bare" critical sections 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, 24 Nov 2004 05:13:05 -0000 Marcel Moolenaar wrote: > > On Nov 23, 2004, at 1:31 PM, John Baldwin wrote: > >> On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: >> >>> Basically, I have a patch to divorce the interrupt disable/deferring to >>> only happen inside of spinlocks using a new spinlock_enter/exit() API >>> (where a spinlock_enter/exit includes a critical section as well) >>> but that >>> plain critical sections won't have to do such a thing. I've tested >>> it on >>> i386, alpha, and sparc64 already, and it has also been tested on >>> arm. I'm >>> unable to get a cross-built powerpc kernel to link (linker dies with a >>> signal 6), but the compile did finish. I have cross-compiled ia64 and >>> amd64 >>> successfully, but have not run tested due to ENOHARDWARE. So, I would >>> appreciate it if a few folks could try the patch out on ppc, ia64, and >>> amd64 to make sure it works ok. Thanks. >>> >>> http://www.FreeBSD.org/~jhb/spinlock.patch >> >> >> *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch >> >> Sorry about that. > > > The patch doesn't apply cleanly. Can you create a patch against HEAD > and not your lock branch? > > Rejects are: > > Hmm... The next patch looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |--- //depot/projects/smpng/sys/kern/kern_mutex.c 2004/11/15 > 20:20:33 > |+++ //depot/user/jhb/lock/kern/kern_mutex.c 2004/11/17 16:42:34 > -------------------------- > Patching file sys/kern/kern_mutex.c using Plan A... > Hunk #1 failed at 602. > Hunk #2 failed at 630. > 2 out of 2 hunks failed--saving rejects to sys/kern/kern_mutex.c.rej > Hmm... The next patch looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |--- //depot/projects/smpng/sys/sys/mutex.h 2004/08/18 16:47:14 > |+++ //depot/user/jhb/lock/sys/mutex.h 2004/11/04 23:48:43 > -------------------------- > Patching file sys/sys/mutex.h using Plan A... > Hunk #1 succeeded at 164 (offset -3 lines). > Hunk #2 failed at 176. > Hunk #3 succeeded at 194 (offset -11 lines). > Hunk #4 succeeded at 212 with fuzz 2 (offset -4 lines). > Hunk #5 failed at 220. > 2 out of 5 hunks failed--saving rejects to sys/sys/mutex.h.rej > Tonight, I'll work out merging it with 5.3-STABLE, I think this might help with a problem I'm having with some of our machines. I'll let you know what the effect is, and how I'll include a patch if I can get it done. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 06:18:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FCAF16A4CE for ; Wed, 24 Nov 2004 06:18:51 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBF4643D48 for ; Wed, 24 Nov 2004 06:18:49 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id w67so150955cwb for ; Tue, 23 Nov 2004 22:18:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=b3GjAeQfhoeebEuzAVunaVGxEfSu6KQHzQtTV9344Anq6V7L+JRkDXyfIQQcv1D6zy7nL+fBg8msPmjlcRAugUoqK926129c6lkKvqatCI2V0Aq0C7PQuJZ3Kr0EQuy/MnMQsFN4+xRqLXsHE9fc0cxNlW55zclRyb4qVf4tUGI= Received: by 10.11.117.74 with SMTP id p74mr42334cwc; Tue, 23 Nov 2004 22:18:48 -0800 (PST) Received: from ?192.168.102.104? ([67.160.118.158]) by smtp.gmail.com with ESMTP id p77sm1069cwc; Tue, 23 Nov 2004 22:18:48 -0800 (PST) Message-ID: <41A3B73D.4080806@gmail.com> Date: Tue, 23 Nov 2004 22:18:37 +0000 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (X11/20041122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <200411231500.55841.jhb@FreeBSD.org> <200411231631.00945.jhb@FreeBSD.org> <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> In-Reply-To: <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Patch to optimize "bare" critical sections 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, 24 Nov 2004 06:18:51 -0000 Marcel Moolenaar wrote: > > On Nov 23, 2004, at 1:31 PM, John Baldwin wrote: > >> On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: >> >>> Basically, I have a patch to divorce the interrupt disable/deferring to >>> only happen inside of spinlocks using a new spinlock_enter/exit() API >>> (where a spinlock_enter/exit includes a critical section as well) >>> but that >>> plain critical sections won't have to do such a thing. I've tested >>> it on >>> i386, alpha, and sparc64 already, and it has also been tested on >>> arm. I'm >>> unable to get a cross-built powerpc kernel to link (linker dies with a >>> signal 6), but the compile did finish. I have cross-compiled ia64 and >>> amd64 >>> successfully, but have not run tested due to ENOHARDWARE. So, I would >>> appreciate it if a few folks could try the patch out on ppc, ia64, and >>> amd64 to make sure it works ok. Thanks. >>> >>> http://www.FreeBSD.org/~jhb/spinlock.patch >> >> >> *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch >> >> Sorry about that. > > > The patch doesn't apply cleanly. Can you create a patch against HEAD > and not your lock branch? > > Rejects are: > > Hmm... The next patch looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |--- //depot/projects/smpng/sys/kern/kern_mutex.c 2004/11/15 > 20:20:33 > |+++ //depot/user/jhb/lock/kern/kern_mutex.c 2004/11/17 16:42:34 > -------------------------- > Patching file sys/kern/kern_mutex.c using Plan A... > Hunk #1 failed at 602. > Hunk #2 failed at 630. > 2 out of 2 hunks failed--saving rejects to sys/kern/kern_mutex.c.rej > Hmm... The next patch looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |--- //depot/projects/smpng/sys/sys/mutex.h 2004/08/18 16:47:14 > |+++ //depot/user/jhb/lock/sys/mutex.h 2004/11/04 23:48:43 > -------------------------- > Patching file sys/sys/mutex.h using Plan A... > Hunk #1 succeeded at 164 (offset -3 lines). > Hunk #2 failed at 176. > Hunk #3 succeeded at 194 (offset -11 lines). > Hunk #4 succeeded at 212 with fuzz 2 (offset -4 lines). > Hunk #5 failed at 220. > 2 out of 5 hunks failed--saving rejects to sys/sys/mutex.h.rej > It does not compile. Complains out redundant declarations of spinlock_enter and spinlock_exit, for me on amd64. I applied the patch by hand, so it could be a mistake on my end. Doesn't appear to be though. This was with 5.3-STABLE. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 07:06:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2221816A4CE for ; Wed, 24 Nov 2004 07:06:56 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACF8C43D41 for ; Wed, 24 Nov 2004 07:06:55 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id iAO76qO7030581 for ; Wed, 24 Nov 2004 02:06:54 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id iAO76qb5030580 for freebsd-amd64@freebsd.org; Wed, 24 Nov 2004 02:06:52 -0500 (EST) (envelope-from wayne) Date: Wed, 24 Nov 2004 02:06:52 -0500 From: "Michael R. Wayne" To: freebsd-amd64@freebsd.org Message-ID: <20041124070652.GT49800@manor.msen.com> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041116052630.GD49800@manor.msen.com> <20041120014424.GI20068@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041120014424.GI20068@dragon.nuxi.com> User-Agent: Mutt/1.4.2.1i Subject: Re: How to use older libs in 32bit mode? 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, 24 Nov 2004 07:06:56 -0000 On Fri, Nov 19, 2004 at 05:44:24PM -0800, David O'Brien wrote: > On Tue, Nov 16, 2004 at 12:26:30AM -0500, Michael R. Wayne wrote: > > I'm trying to use a 32 bit executable which uses older libraries > > (e.g. libm.so.2) and can not easily be regenerated. > > This should be fine. You just want *.so.*. > > > I've tried copying the libs from a i386 5.3 RELEASE system into > > /usr/lib32 with no success. > > Please give details about "no success" -- that doesn't give us much to go > on. Sorry. No success as in it cores. I reduced the problem down to a very simple case: > cat hello.c #include main () { printf("Hello world\n"); } Put this onto a 5.3 RELEASE i386 platform and compiled it: > file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.3.0, dynamically linked (uses shared libs), not stripped It won't run though: > ./hello Segmentation fault (core dumped) I did run the script to build the libs: > ls /usr/lib32 | wc 393 393 5069 /\/\ \/\/ From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 07:13:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBDE216A4CF for ; Wed, 24 Nov 2004 07:13:44 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82C8B43D55 for ; Wed, 24 Nov 2004 07:13:44 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id iAO7DhO7030648 for ; Wed, 24 Nov 2004 02:13:44 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id iAO7DhHI030647 for freebsd-amd64@freebsd.org; Wed, 24 Nov 2004 02:13:43 -0500 (EST) (envelope-from wayne) Date: Wed, 24 Nov 2004 02:13:43 -0500 From: "Michael R. Wayne" To: freebsd-amd64@freebsd.org Message-ID: <20041124071343.GU49800@manor.msen.com> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041108191947.GA49800@manor.msen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041108191947.GA49800@manor.msen.com> User-Agent: Mutt/1.4.2.1i Subject: Re: How to debug >2GB memory issues (and 3ware) 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, 24 Nov 2004 07:13:45 -0000 Resolution for the archives On Mon, Nov 08, 2004 at 02:19:47PM -0500, I wrote: > I have a Dual 4GB system with a 3ware SATA controller that's working > properly as long as I restrict it to 2GB with: > hw.physmem=2G > > Obviously, I'd like to have access to the other 2GB of RAM. But > if I go past 2GB, I get random crashes during all builds (world, > kernel, port). Short term fix: Remove the last Gig of RAM so that there was only 3 GB physical RAM in the box. Note that limiting it to 3GB with hw.physmem=3G did NOT work, that only worked to 2 GB. Long term fix: Replace the 8 512MB Corsair DIMMs (where are approved to run with the Arima motherboard) with 4 Kingston 1GB DIMMs. All problems vanished immediately and the box runs fine with 4 Gig. /\/\ \/\/ From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 07:51:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39FA616A4CE for ; Wed, 24 Nov 2004 07:51:14 +0000 (GMT) Received: from web14106.mail.yahoo.com (web14106.mail.yahoo.com [216.136.172.136]) by mx1.FreeBSD.org (Postfix) with SMTP id 0948343D5C for ; Wed, 24 Nov 2004 07:51:14 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 74056 invoked by uid 60001); 24 Nov 2004 07:51:13 -0000 Message-ID: <20041124075113.74052.qmail@web14106.mail.yahoo.com> Received: from [194.248.174.50] by web14106.mail.yahoo.com via HTTP; Wed, 24 Nov 2004 08:51:13 CET Date: Wed, 24 Nov 2004 08:51:13 +0100 (CET) From: Claus Guttesen To: "Michael R. Wayne" , freebsd-amd64@freebsd.org In-Reply-To: <20041124071343.GU49800@manor.msen.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: How to debug >2GB memory issues (and 3ware) 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, 24 Nov 2004 07:51:14 -0000 > > I have a Dual 4GB system with a 3ware SATA > > controller that's working > > properly as long as I restrict it to 2GB with: > > hw.physmem=2G > > > Short term fix: > Remove the last Gig of RAM so that there was only > 3 GB physical RAM in the box. Note that limiting it > to 3GB with hw.physmem=3G > did NOT work, that only worked to 2 GB. > > Long term fix: > Replace the 8 512MB Corsair DIMMs (where are > approved to run with the Arima motherboard) with 4 > Kingston 1GB DIMMs. All problems vanished > immediately and the box runs fine with 4 Gig. Hmm, funny. I just bougth an Tyan GX28 with 4 GB RAM and a 3ware-sata-controller. Installed FreeBSD 5.3 (amd64), works like a charm. Luckily (as it turns out) the salesman and I agreed on 4 x 1GB memory modules (long term fix). Claus From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 10:28:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD90B16A4CE for ; Wed, 24 Nov 2004 10:28:23 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8223D43D31 for ; Wed, 24 Nov 2004 10:28:23 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so47438cwc for ; Wed, 24 Nov 2004 02:28:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding; b=hGIXz9/MdfxESTY9Jf0KajEFByR7FzBVW+x5vL5Z3mHy7sug8FxSCVzIYaluew7ocy9NmX/F3jf5uNN04Pj/bf71f86SyyVBrD5DLA6TPaj+V4BgyAII0pQFdfi7Qo/sbj1JbxXo3Q5m8MsTFzdkN9laBIYNORQXmffbDrANdz8= Received: by 10.11.100.61 with SMTP id x61mr21295cwb; Wed, 24 Nov 2004 02:28:23 -0800 (PST) Received: from ?192.168.102.103? ([67.160.118.158]) by smtp.gmail.com with ESMTP id v71sm7629cwb; Wed, 24 Nov 2004 02:28:23 -0800 (PST) Message-ID: <41A46242.8060305@gmail.com> Date: Wed, 24 Nov 2004 02:28:18 -0800 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim , freebsd-amd64@freebsd.org References: <41A2D10B.7030108@gmail.com> <200411231053.17874.jkim@niksun.com> In-Reply-To: <200411231053.17874.jkim@niksun.com> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 3000Z Bugs Noticed Now That Its Running 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, 24 Nov 2004 10:28:23 -0000 Jung-uk Kim wrote: >On Tuesday 23 November 2004 12:56 am, Astrodog wrote: > > >>Well, now I hope we have a larger base for 3000Z work, so I figured >>I'd post the bugs I've run into so far, in no particular order. If >>you want more information on one, feel free to drop me a line, just >>posting this so other people know what they're getting in to. >> >>#1. No ACPI, I'm working on this one now >> >>#2. Kernel Panic when you close the lid. Goes away when ACPI is >>enabled, but then the boot gets stuck. >> >> > >When ACPI is enabled, it works fine but the keyboard doesn't work >AFAIK, i. e., PS/2 port is not probed. However you can login from >network, which is bad for laptop. :-( > > > >>#3. Loss of usable LCD display when you switch from X back to a >>normal terminal. Goes into what looks like an old TV with its >>vertical sync fried. >> >> > >This is well known bug in Xorg driver. > >https://bugs.freedesktop.org/show_bug.cgi?id=1549 > >nVidia's binary driver doesn't have this bug but it is not available >for FreeBSD/amd64 yet. > > > >>Beyond those 3 things, which I think extend to most mobiles before >>they get some attention, its golden. I haven't tried nvidia's own >>drivers yet, or DRI... we'll see soon. >> >> > >DRI doesn't work because there is no open source driver. > >http://dri.sourceforge.net/cgi-bin/moin.cgi/nVidia?action=highlight&value=CategoryHardwareVendor > >nVidia's own driver works fine for FreeBSD/i386 though. > >Jung-uk Kim > > > >>--- Harrison Grundy >> >> > > > When ACPI is enabled, mine locks up during boot. between ad0: (HDD info) acd0: (CDROM Info) and mounting root from: /dev/ad0s3a From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 12:22:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3137B16A4CE for ; Wed, 24 Nov 2004 12:22:22 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9501A43D3F for ; Wed, 24 Nov 2004 12:22:21 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao03.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20041124122220.HKVS14730.lakermmtao03.cox.net@dolphin.local.net>; Wed, 24 Nov 2004 07:22:20 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iAOCMHH0074153; Wed, 24 Nov 2004 06:22:20 -0600 (CST) (envelope-from conrads@cox.net) Date: Wed, 24 Nov 2004 06:22:12 -0600 From: "Conrad J. Sabatier" To: a.degroot@science.ru.nl Message-ID: <20041124062212.392f8848@dolphin.local.net> In-Reply-To: References: X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Cross-compiling on x86 to 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, 24 Nov 2004 12:22:22 -0000 On Tue, 23 Nov 2004 12:45:05 +0100 (MET), a.degroot@science.ru.nl wrote: > For various large compiles (KDE, mostly), I'm looking into setting up > a compile farm to produce amd64 inaries. A basic distcc setup, to > start with(icecream, the teambuilder-alike with some pretty neat > features, is still horribly linux-specific and I need to fix that some > time), but I'm somewhat lacking on the number-of-amd64 machines front, > as in I've got 1. > > So I got to thinking: why should the x86 machines in the house get a > break? They should be able to produce amd64 code at the least. > > The system gcc on 5.3-R on x86 doesn't like -m64: > > -bash-2.05b$ g++ -c -m64 t.cc > t.cc:1: sorry, unimplemented: 64-bit mode not compiled in > > which is unfortunate, because if I understand correctly, that's the > only flag I would really need to use to make gcc on x86en produce code > for amd64 (ie. > > x86box$ g++ -m64 t.cc > amd64box$ g++ t.cc > > should produce identical results?). Information on building a > cross-compiling gcc is not thick on the ground (at least, not for a > trivial setup like this -- for weird embedded targets there seems to > be enough). Does anyone have a hint on how to set this up -- or just > plain build a gcc 3.4.3 that outputs amd64 .o files -- so my x86en can > compile for their new 64 bit overlords? > > > PS. Yes, I realise that using a 32-bit userland with LIB32 would allow > me to share the compiles and use just the plain system gcc on the x86 > machines, but as of yet not all possible 64-bit errors have been > removed from KDE, so I do want to be building in 64-bit mode. I attempted the same thing with distcc a while back, trying to farm the builds between my athlon 64 and athlon boxes, but hit the same snag as you, and was stymied as to how to proceed. I'd certainly like to know if there's any way to get this to work. Please followup to the list if you find out anything useful! -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 15:41:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27AED16A53C for ; Wed, 24 Nov 2004 15:41:25 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B6343D1F for ; Wed, 24 Nov 2004 15:41:24 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30716 invoked from network); 24 Nov 2004 15:41:20 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 24 Nov 2004 15:41:20 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAOFf5WY043775; Wed, 24 Nov 2004 10:41:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Marcel Moolenaar Date: Wed, 24 Nov 2004 10:26:35 -0500 User-Agent: KMail/1.6.2 References: <200411231500.55841.jhb@FreeBSD.org> <200411231631.00945.jhb@FreeBSD.org> <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> In-Reply-To: <9C77F94E-3DC8-11D9-A2B1-000D93C47836@xcllnt.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411241026.35486.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: amd64@FreeBSD.org cc: powerpc@FreeBSD.org cc: ia64@FreeBSD.org Subject: Re: Patch to optimize "bare" critical sections 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, 24 Nov 2004 15:41:27 -0000 On Tuesday 23 November 2004 10:26 pm, Marcel Moolenaar wrote: > On Nov 23, 2004, at 1:31 PM, John Baldwin wrote: > > On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: > >> Basically, I have a patch to divorce the interrupt disable/deferring > >> to > >> only happen inside of spinlocks using a new spinlock_enter/exit() API > >> (where a spinlock_enter/exit includes a critical section as well) but > >> that > >> plain critical sections won't have to do such a thing. I've tested > >> it on > >> i386, alpha, and sparc64 already, and it has also been tested on arm. > >> I'm > >> unable to get a cross-built powerpc kernel to link (linker dies with a > >> signal 6), but the compile did finish. I have cross-compiled ia64 and > >> amd64 > >> successfully, but have not run tested due to ENOHARDWARE. So, I would > >> appreciate it if a few folks could try the patch out on ppc, ia64, and > >> amd64 to make sure it works ok. Thanks. > >> > >> http://www.FreeBSD.org/~jhb/spinlock.patch > > > > *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch > > > > Sorry about that. > > The patch doesn't apply cleanly. Can you create a patch against HEAD > and not your lock branch? Doh, the patch has been updated to be against HEAD now. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 19:30:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AFFC16A4CE for ; Wed, 24 Nov 2004 19:30:56 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48F4843D55 for ; Wed, 24 Nov 2004 19:30:54 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.13.1/8.12.11) with ESMTP id iAOJv9U7021880 for ; Wed, 24 Nov 2004 14:57:09 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAOJv7oS021877 for ; Wed, 24 Nov 2004 14:57:09 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Wed, 24 Nov 2004 14:57:07 -0500 (EST) From: Chuck Robey To: freebsd-amd64@freebsd.org Message-ID: <20041124145143.O4002@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: acroread on the 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, 24 Nov 2004 19:30:56 -0000 I noticed that acroread is marked as being only for the i386 ... I have a question about that ... I'm a little new at running the amd64, but I thought that it was compatible (if it had the 32 bit libraries installed to support it) with i386, so I would have expected my amd64 machine to be ablel to run acroread with little trouble. The port being marked as"ONLY_FOR_ARCHS", well, I considered, *possibly*, that the port author hadn't had the testing capability, and maybe it did too work on the amd64. Anyone have more detailed info about that? Notice, I didn't mail to freeBSD-ports, I don't know how strict our mailing list filters are, I thought they'd probably kick me out if I tried to cross-post. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 19:39:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37E4516A4CE for ; Wed, 24 Nov 2004 19:39:42 +0000 (GMT) Received: from mailhub.sweetdreamsracing.biz (mailhub.sweetdreamsracing.biz [66.92.171.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A052943D3F for ; Wed, 24 Nov 2004 19:39:41 +0000 (GMT) (envelope-from culverk@sweetdreamsracing.biz) Received: by mailhub.sweetdreamsracing.biz (Postfix, from userid 80) id 3794961BF; Wed, 24 Nov 2004 14:36:35 -0500 (EST) Received: from 141.156.69.109 ([141.156.69.109]) by www.sweetdreamsracing.biz (Horde) with HTTP for ; Wed, 24 Nov 2004 14:36:34 -0500 Message-ID: <20041124143634.ji8s8k80o84w8ksg@www.sweetdreamsracing.biz> Date: Wed, 24 Nov 2004 14:36:34 -0500 From: Kenneth Culver To: Chuck Robey References: <20041124145143.O4002@april.chuckr.org> In-Reply-To: <20041124145143.O4002@april.chuckr.org> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the 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, 24 Nov 2004 19:39:42 -0000 Quoting Chuck Robey : > I noticed that acroread is marked as being only for the i386 ... I have a > question about that ... I'm a little new at running the amd64, but I > thought that it was compatible (if it had the 32 bit libraries installed > to support it) with i386, so I would have expected my amd64 machine to be > ablel to run acroread with little trouble. The port being marked > as"ONLY_FOR_ARCHS", well, I considered, *possibly*, that the port author > hadn't had the testing capability, and maybe it did too work on the amd64. > > Anyone have more detailed info about that? Notice, I didn't mail to > freeBSD-ports, I don't know how strict our mailing list filters are, I > thought they'd probably kick me out if I tried to cross-post. > acroread is a linux binary. I'm not sure that 32 bit linux emulation works yet on amd64... although I could be wrong. Ken From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 19:42:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB57E16A4D6 for ; Wed, 24 Nov 2004 19:42:18 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9EC343D49 for ; Wed, 24 Nov 2004 19:42:18 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAOJgdQX028092; Wed, 24 Nov 2004 11:42:39 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAOJgdV9028090; Wed, 24 Nov 2004 11:42:39 -0800 Date: Wed, 24 Nov 2004 11:42:39 -0800 From: Brooks Davis To: Chuck Robey Message-ID: <20041124194239.GB24353@odin.ac.hmc.edu> References: <20041124145143.O4002@april.chuckr.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9zSXsLTf0vkW971A" Content-Disposition: inline In-Reply-To: <20041124145143.O4002@april.chuckr.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the 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, 24 Nov 2004 19:42:20 -0000 --9zSXsLTf0vkW971A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 24, 2004 at 02:57:07PM -0500, Chuck Robey wrote: > I noticed that acroread is marked as being only for the i386 ... I have a > question about that ... I'm a little new at running the amd64, but I > thought that it was compatible (if it had the 32 bit libraries installed > to support it) with i386, so I would have expected my amd64 machine to be > ablel to run acroread with little trouble. The port being marked > as"ONLY_FOR_ARCHS", well, I considered, *possibly*, that the port author > hadn't had the testing capability, and maybe it did too work on the amd64. If you get 32-bit linux compatability running then acrobat should work. This is actually a deficencly in our ports infrastructure. For binary only ports, we could really use the ability to say that the port supports the following native architectures and the system should be smart enough to know that i386 ports will work on amd64. > Anyone have more detailed info about that? Notice, I didn't mail to > freeBSD-ports, I don't know how strict our mailing list filters are, I > thought they'd probably kick me out if I tried to cross-post. A single cross post will work. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --9zSXsLTf0vkW971A Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBpOQvXY6L6fI4GtQRAgBdAKCrHjhzyg3mHBwNinMui/NhtPMS2QCfVfJq Jr6SAeOxXBZnW+3YGChKryg= =C3Zi -----END PGP SIGNATURE----- --9zSXsLTf0vkW971A-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 19:47:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0452716A4CE for ; Wed, 24 Nov 2004 19:47:37 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id DF35843D41 for ; Wed, 24 Nov 2004 19:47:35 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 1418 invoked by uid 513); 24 Nov 2004 19:47:40 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.58.21):SA:0(-4.9/5.0):. Processed in 0.635651 secs); 24 Nov 2004 19:47:40 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.21) by dsl-mail.kamp.net with SMTP; 24 Nov 2004 19:47:39 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id iAOJoqLE002641 for ; Wed, 24 Nov 2004 20:50:52 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id iAOJoqHW002640 for freebsd-amd64@freebsd.org; Wed, 24 Nov 2004 20:50:52 +0100 (CET) (envelope-from ewinter) Date: Wed, 24 Nov 2004 20:50:52 +0100 From: "Ernst W. Winter" To: Chuck Robey Message-ID: <20041124195052.GA2391@lobo.homeunix.org> References: <20041124145143.O4002@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041124145143.O4002@april.chuckr.org> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i Subject: Re: acroread on the amd64 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: Wed, 24 Nov 2004 19:47:37 -0000 On Wed, 24 Nov 2004, Chuck Robey wrote: > Anyone have more detailed info about that? Notice, I didn't mail > to freeBSD-ports, I don't know how strict our mailing list filters > are, I thought they'd probably kick me out if I tried to > cross-post. > Sorry I posted this to you, but for the benefit to others I would suggest to compile "xpf" or "gpdf" and "gv" as I never used the Acrobat reader and had no need for it. I found those other ones done a job well even here now on a AMD64. Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 20:01:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8890F16A4CE for ; Wed, 24 Nov 2004 20:01:55 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0B8F43D54 for ; Wed, 24 Nov 2004 20:01:54 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao03.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20041124200154.MHTY14730.lakermmtao03.cox.net@dolphin.local.net>; Wed, 24 Nov 2004 15:01:54 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iAOK1rgV078919; Wed, 24 Nov 2004 14:01:53 -0600 (CST) (envelope-from conrads@cox.net) Date: Wed, 24 Nov 2004 14:01:48 -0600 From: "Conrad J. Sabatier" To: Brooks Davis Message-ID: <20041124140148.61926075@dolphin.local.net> In-Reply-To: <20041124194239.GB24353@odin.ac.hmc.edu> References: <20041124145143.O4002@april.chuckr.org> <20041124194239.GB24353@odin.ac.hmc.edu> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the 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, 24 Nov 2004 20:01:55 -0000 On Wed, 24 Nov 2004 11:42:39 -0800, Brooks Davis wrote: > On Wed, Nov 24, 2004 at 02:57:07PM -0500, Chuck Robey wrote: > > I noticed that acroread is marked as being only for the i386 ... I > > have a question about that ... I'm a little new at running the > > amd64, but I thought that it was compatible (if it had the 32 bit > > libraries installed to support it) with i386, so I would have > > expected my amd64 machine to be ablel to run acroread with little > > trouble. The port being marked as"ONLY_FOR_ARCHS", well, I > > considered, *possibly*, that the port author hadn't had the testing > > capability, and maybe it did too work on the amd64. > > If you get 32-bit linux compatability running then acrobat should > work. Not only should, but actually does. :-) > This is actually a deficencly in our ports infrastructure. For > binary only ports, we could really use the ability to say that the > port supports the following native architectures and the system should > be smart enough to know that i386 ports will work on amd64. Yes, I've tinkered with a number of ONLY_FOR_ARCHS ports on amd64, and gotten them to build and run successfully. I really should send-pr these (if I can remember now which ones they were). :-) -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 20:03:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D11EA16A4CE for ; Wed, 24 Nov 2004 20:03:54 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 0B8B743D54 for ; Wed, 24 Nov 2004 20:03:54 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 15735 invoked by uid 513); 24 Nov 2004 20:03:58 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.58.21):SA:0(-4.9/5.0):. Processed in 16.94708 secs); 24 Nov 2004 20:03:58 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.21) by dsl-mail.kamp.net with SMTP; 24 Nov 2004 20:03:41 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id iAOK6sUd003263; Wed, 24 Nov 2004 21:06:54 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id iAOK6rfb003262; Wed, 24 Nov 2004 21:06:53 +0100 (CET) (envelope-from ewinter) Date: Wed, 24 Nov 2004 21:06:53 +0100 From: "Ernst W. Winter" To: Chuck Robey Message-ID: <20041124200653.GB2754@lobo.homeunix.org> References: <20041124145143.O4002@april.chuckr.org> <20041124194744.GA2102@lobo.homeunix.org> <20041124151507.M4002@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041124151507.M4002@april.chuckr.org> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the amd64 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: Wed, 24 Nov 2004 20:03:54 -0000 On Wed, 24 Nov 2004, Chuck Robey wrote: > On Wed, 24 Nov 2004, Ernst W. Winter wrote: > > > On Wed, 24 Nov 2004, Chuck Robey wrote: > > > > > Anyone have more detailed info about that? Notice, I didn't mail > > > to freeBSD-ports, I don't know how strict our mailing list filters > > > are, I thought they'd probably kick me out if I tried to > > > cross-post. > > > > > well I would suggest that you should try "xpdf" or "gpdf" and "gv" as > > that would cover that part well, I never have used the Acrobat reader > > as these other always done whatever I needed them for and I have > > compiled them now with a AMD64 here and they behave well. I would > > say, try it. > > Trying to get apsfilter working, and it wants acroread, so I'm going to > *try* that first. In my own experience, although it's rare, there ARE > those docs that get read by acroread, and not by xpdf, I've seen them. > well I never used that option and with xpdf there where a time when there where some hickups, but so far no more, also as I said there is gpdf and it works well and I have seen others with kde that do the job well, so far I have collected some Gigabyte of documents as I do research for people and neve had any problems and do I can't comment on Acroread either. Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 20:33:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF25A16A4CE for ; Wed, 24 Nov 2004 20:33:41 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D4CF43D3F for ; Wed, 24 Nov 2004 20:33:41 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.13.1/8.12.11) with ESMTP id iAOKxsJe022221; Wed, 24 Nov 2004 15:59:54 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAOKxqfk022218; Wed, 24 Nov 2004 15:59:53 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Wed, 24 Nov 2004 15:59:52 -0500 (EST) From: Chuck Robey To: "Ernst W. Winter" In-Reply-To: <20041124200653.GB2754@lobo.homeunix.org> Message-ID: <20041124155620.B4002@april.chuckr.org> References: <20041124145143.O4002@april.chuckr.org> <20041124194744.GA2102@lobo.homeunix.org> <20041124200653.GB2754@lobo.homeunix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the 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, 24 Nov 2004 20:33:42 -0000 On Wed, 24 Nov 2004, Ernst W. Winter wrote: > On Wed, 24 Nov 2004, Chuck Robey wrote: > > > On Wed, 24 Nov 2004, Ernst W. Winter wrote: > > > > > On Wed, 24 Nov 2004, Chuck Robey wrote: > > > > > > > Anyone have more detailed info about that? Notice, I didn't mail > > > > to freeBSD-ports, I don't know how strict our mailing list filters > > > > are, I thought they'd probably kick me out if I tried to > > > > cross-post. > > > > > > > well I would suggest that you should try "xpdf" or "gpdf" and "gv" as > > > that would cover that part well, I never have used the Acrobat reader > > > as these other always done whatever I needed them for and I have > > > compiled them now with a AMD64 here and they behave well. I would > > > say, try it. > > > > Trying to get apsfilter working, and it wants acroread, so I'm going to > > *try* that first. In my own experience, although it's rare, there ARE > > those docs that get read by acroread, and not by xpdf, I've seen them. > > > well I never used that option and with xpdf there where a time when > there where some hickups, but so far no more, also as I said there is > gpdf and it works well and I have seen others with kde that do the > job well, so far I have collected some Gigabyte of documents as I do > research for people and neve had any problems and do I can't comment > on Acroread either. Well, you did say (above) that you didn't try acroread, so I guess you probably didn't even realize that one of the files that you might have given up on, "garbage", actually might have printed with acroread. Not common .... maybe not worth the work, I dunno, the damn install from Adobe is very , very unfriendly, I will have to hack the heck out of it to get it to work, not sure I want to invest all that skullsweat. I do know how to do that, but I don't think it's worth too much time. > > Ernst > > -- > Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz > Microsoft: Where do you want to go today? > Linux: Where do you want to go tomorrow? > BSD: Are you guys coming, or what? > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 20:45:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBBA916A4CE for ; Wed, 24 Nov 2004 20:45:21 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 0FCC743D49 for ; Wed, 24 Nov 2004 20:45:21 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 18474 invoked by uid 513); 24 Nov 2004 20:45:26 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.58.21):SA:0(-4.9/5.0):. Processed in 5.940807 secs); 24 Nov 2004 20:45:26 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.58.21) by dsl-mail.kamp.net with SMTP; 24 Nov 2004 20:45:20 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id iAOKmWSh004160; Wed, 24 Nov 2004 21:48:32 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id iAOKmVSX004159; Wed, 24 Nov 2004 21:48:31 +0100 (CET) (envelope-from ewinter) Date: Wed, 24 Nov 2004 21:48:31 +0100 From: "Ernst W. Winter" To: Chuck Robey Message-ID: <20041124204831.GA3367@lobo.homeunix.org> References: <20041124145143.O4002@april.chuckr.org> <20041124194744.GA2102@lobo.homeunix.org> <20041124151507.M4002@april.chuckr.org> <20041124200653.GB2754@lobo.homeunix.org> <20041124155620.B4002@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041124155620.B4002@april.chuckr.org> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the amd64 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: Wed, 24 Nov 2004 20:45:22 -0000 On Wed, 24 Nov 2004, Chuck Robey wrote: [..] > > > Trying to get apsfilter working, and it wants acroread, so I'm > > > going to *try* that first. In my own experience, although it's > > > rare, there ARE those docs that get read by acroread, and not > > > by xpdf, I've seen them. > > > > > well I never used that option and with xpdf there where a time > > when there where some hickups, but so far no more, also as I said > > there is gpdf and it works well and I have seen others with kde > > that do the job well, so far I have collected some Gigabyte of > > documents as I do research for people and neve had any problems > > and do I can't comment on Acroread either. > > Well, you did say (above) that you didn't try acroread, so I guess > you probably didn't even realize that one of the files that you > might have given up on, "garbage", actually might have printed with > acroread. Not common .... maybe not worth the work, I dunno, the Hmm, so far I had no problem, as I can convert it to something else. I have some experinece with that, and I can assre you since I started with Unix (that was with 386BSD form Bill Jollitz) and I never used any WINdum software as I'm very content with what FreeBSD has to offer. I tmight not be always there when you want it, but on the other hand I have learned to live with many things and found some nice conversions for various documents. I just had a example that someone sent me a *rtf and as a dcoument and the second part as *doc and you can just load them up with Abiword and convert them or print them and also manipulate them and then conver them again. I LOVE it!!! > damn install from Adobe is very , very unfriendly, I will have to > hack the heck out of it to get it to work, not sure I want to > invest all that skullsweat. > Why should you? I lived without and never used it and have nice life and do many conversions and there is enough software around to mak my life easy. > I do know how to do that, but I don't think it's worth too much > time. > Why bother, there are too many things around in the Unix world that can do wonders with some of the conversions. Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 21:55:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EBDD16A4CE for ; Wed, 24 Nov 2004 21:55:51 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ED8A43D4C for ; Wed, 24 Nov 2004 21:55:50 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zgzuvq@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id iAOLtlEu099212 for ; Wed, 24 Nov 2004 22:55:48 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id iAOLtl56099211; Wed, 24 Nov 2004 22:55:47 +0100 (CET) (envelope-from olli) Date: Wed, 24 Nov 2004 22:55:47 +0100 (CET) Message-Id: <200411242155.iAOLtl56099211@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <20041124195052.GA2391@lobo.homeunix.org> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: acroread on the amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 21:55:51 -0000 Ernst W. Winter wrote: > Sorry I posted this to you, but for the benefit to others I would > suggest to compile "xpf" or "gpdf" and "gv" as I never used the > Acrobat reader and had no need for it. I found those other ones done > a job well even here now on a AMD64. Acroread is a _lot_ faster than those, especially with anti-aliasing enabled. I've had a complex document (containing lots of detailed maps and graphics) which gv took more than two minutes to render, while Acroread took 10 seconds. Also, I've had several cases where gv etc. did not render a document properly, most of the time it had to do with overlapping elements which were rendered in the wrong order. Acroread has never any such problems. For those reasons I use Acroread most of the time, if possible. (The above are just my observations. YMMV.) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. > Can the denizens of this group enlighten me about what the > advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling checker than "perl". -- An unknown poster and Fredrik Lundh From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 03:10:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7957E16A4CE for ; Thu, 25 Nov 2004 03:10:19 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6344B43D1F for ; Thu, 25 Nov 2004 03:10:18 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.11] (CPE-144-133-92-247.vic.bigpond.net.au [144.133.92.247]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id iAP3AArO036413 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Thu, 25 Nov 2004 14:10:12 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20041124070652.GT49800@manor.msen.com> References: <20041116052630.GD49800@manor.msen.com> <20041120014424.GI20068@dragon.nuxi.com> <20041124070652.GT49800@manor.msen.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <80EAD071-3E8F-11D9-AF21-000D93AD5C52@hydrix.com> Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Thu, 25 Nov 2004 14:10:04 +1100 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.8 required=6.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/533/Sun Oct 17 11:09:44 2004 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean Subject: Re: How to use older libs in 32bit mode? 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, 25 Nov 2004 03:10:19 -0000 On 24/11/2004, at 6:06 PM, Michael R. Wayne wrote: > Sorry. No success as in it cores. > Exact same thing here. Any attempts to run a 32 bits executable on an AMD64 machines result in a coredump Jean-Yves > --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 06:50:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED3F316A4CE for ; Thu, 25 Nov 2004 06:50:59 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id D24B443D60 for ; Thu, 25 Nov 2004 06:50:58 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 2215 invoked by uid 513); 25 Nov 2004 06:50:59 -0000 Received: from ewinter@lobo.homeunix.org by dsl-mail by uid 89 with qmail-scanner-1.21 Clear:RC:1(82.141.59.173):SA:0(-4.9/5.0):. Processed in 0.778742 secs); 25 Nov 2004 06:50:59 -0000 X-Spam-Status: No, hits=-4.9 required=5.0 Received: from unknown (HELO lobo.homeunix.org) (82.141.59.173) by dsl-mail.kamp.net with SMTP; 25 Nov 2004 06:50:58 -0000 Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.1/8.13.1) with ESMTP id iAP6sC89001002 for ; Thu, 25 Nov 2004 07:54:12 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id iAP6sCDL001001 for freebsd-amd64@freebsd.org; Thu, 25 Nov 2004 07:54:12 +0100 (CET) (envelope-from ewinter) Date: Thu, 25 Nov 2004 07:54:12 +0100 From: "Ernst W. Winter" To: freebsd-amd64@freebsd.org Message-ID: <20041125065412.GA634@lobo.homeunix.org> References: <20041124195052.GA2391@lobo.homeunix.org> <200411242155.iAOLtl56099211@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411242155.iAOLtl56099211@lurza.secnetix.de> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.3-STABLE FreeBSD 5.3-STABLE User-Agent: Mutt/1.5.6i Subject: Re: acroread on the amd64 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: Thu, 25 Nov 2004 06:51:00 -0000 On Wed, 24 Nov 2004, Oliver Fromme wrote: > Ernst W. Winter wrote: > > Sorry I posted this to you, but for the benefit to others I would > > suggest to compile "xpf" or "gpdf" and "gv" as I never used the > > Acrobat reader and had no need for it. I found those other ones done > > a job well even here now on a AMD64. > > Acroread is a _lot_ faster than those, especially with > anti-aliasing enabled. I've had a complex document As I said I don't know as I never needed nor used it. > (containing lots of detailed maps and graphics) which > gv took more than two minutes to render, while Acroread > took 10 seconds. Also, I've had several cases where Please send me some as I never had any problems with that either, so it would be nice to see it and gain the experience. > gv etc. did not render a document properly, most of the > time it had to do with overlapping elements which were > rendered in the wrong order. Acroread has never any > such problems. > Again, it would be nice to see it as I said I never had such problems, so please enlighten me or send me something so I can see what you mean and which type of documents. > For those reasons I use Acroread most of the time, if > possible. > Sure no worries, if it fits why not. > (The above are just my observations. YMMV.) > same here. > Best regards > Oliver > Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 14:41:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9182E16A4CE for ; Thu, 25 Nov 2004 14:41:16 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F37143D4C for ; Thu, 25 Nov 2004 14:41:15 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ahsrqx@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id iAPEfE8J030265 for ; Thu, 25 Nov 2004 15:41:14 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id iAPEfEtF030264; Thu, 25 Nov 2004 15:41:14 +0100 (CET) (envelope-from olli) Date: Thu, 25 Nov 2004 15:41:14 +0100 (CET) Message-Id: <200411251441.iAPEfEtF030264@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <20041125065412.GA634@lobo.homeunix.org> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: acroread on the 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, 25 Nov 2004 14:41:16 -0000 Ernst W. Winter wrote: > On Wed, 24 Nov 2004, Oliver Fromme wrote: > > Acroread is a _lot_ faster than those, especially with > > anti-aliasing enabled. I've had a complex document > > As I said I don't know as I never needed nor used it. > > > (containing lots of detailed maps and graphics) which > > gv took more than two minutes to render, while Acroread > > took 10 seconds. Also, I've had several cases where > > Please send me some as I never had any problems with that either, so > it would be nice to see it and gain the experience. Something which I've been using a lot recently: The new public transport map of munich. You can download it here: http://www.mvv-muenchen.de/web4archiv/objects/download/1/vlp_041212_stadt.pdf For a short test, zoom into the center of the city (so that the blue rectangle in the center is displayed full-screen). Acroread finishes after 18 seconds on my machine, gv takes several minutes. (This is on a remote X connection which is tunneled through ssh, using 1280 x 1024 pixels at 32 bit truecolor. Using a local X server and/or lower resolution or lower color-depth should be faster, I guess.) But also simple documents make a difference. This is a 4-page flyer from Sandisk that I looked at recently: http://www.sandisk.com/pdf/retail/retail-product-info-guide.pdf Acroread displays each page in about 2 to 3 seconds (full- screen), while gv takes about 7 to 8 seconds. > > gv etc. did not render a document properly, most of the > > time it had to do with overlapping elements which were > > rendered in the wrong order. Acroread has never any > > such problems. > > Again, it would be nice to see it as I said I never had such > problems, so please enlighten me or send me something so I can see > what you mean and which type of documents. I don't have one at hand right now (and I don't feel like testing all of my collected PDF files with gv), but there definitely have been such cases. In the worst case, gv ends up with an empty page (or a page that is all red or whatever), because it paints the background last. Uhm, I think this is getting somewhat off-topic here. :-) But anyway, it would be very nice to have Linux/i386 compa- tibility working on FreeBSD/amd64 so that Acroread, Opera and others can be used. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies." -- C.A.R. Hoare, ACM Turing Award Lecture, 1980 From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 15:08:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3FAE16A4CE; Thu, 25 Nov 2004 15:08:37 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 282B443D31; Thu, 25 Nov 2004 15:08:37 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAPF6jsg041741; Thu, 25 Nov 2004 10:06:45 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAPF6j30041738; Thu, 25 Nov 2004 15:06:45 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 25 Nov 2004 15:06:45 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin In-Reply-To: <200411231631.00945.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: amd64@FreeBSD.org cc: powerpc@FreeBSD.org cc: ia64@FreeBSD.org Subject: Re: Patch to optimize "bare" critical sections 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, 25 Nov 2004 15:08:38 -0000 On Tue, 23 Nov 2004, John Baldwin wrote: > On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: > > Basically, I have a patch to divorce the interrupt disable/deferring to > > only happen inside of spinlocks using a new spinlock_enter/exit() API > > (where a spinlock_enter/exit includes a critical section as well) but that > > plain critical sections won't have to do such a thing. I've tested it on > > i386, alpha, and sparc64 already, and it has also been tested on arm. I'm > > unable to get a cross-built powerpc kernel to link (linker dies with a > > signal 6), but the compile did finish. I have cross-compiled ia64 and > > amd64 > > successfully, but have not run tested due to ENOHARDWARE. So, I would > > appreciate it if a few folks could try the patch out on ppc, ia64, and > > amd64 to make sure it works ok. Thanks. > > > > http://www.FreeBSD.org/~jhb/spinlock.patch > > *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch FYI, I'm seeing a fairly solid wedge occuring under stress with the i386 patch in place on a dual Xeon test box in the Netperf cluster. I thought at first it was a property of the UMA optimizations I have that use the critical sections, but it also happens with just the critical section changes, so... :-) The reproduction mode I'm using is to run the syscall_timing tool on the box over a serial console repeatedly: http://www.watson.org/~robert/freebsd/syscall_timing.c In particular, I'm running 10,000 iterations of the socket create/free test. Under normal circumstances it looks like this: tiger-2# while (1) while? ./syscall_timing 10000 socket | grep per while? end 0.000006708 per/iteration 0.000006642 per/iteration 0.000006658 per/iteration 0.000006660 per/iteration ... ^C When I get the wedge it does this: tiger-2# while (1) while? ./syscall_timing 10000 socket | grep per while? end 0.000006735 per/iteration 0.000006772 per/iteration 0.000006721 per/iteration 0.000006744 per/iteration ... 0.000006716 per/iteration 0.000006710 per/iteration 0.000006745 per/ <-- hung It could well be associated with poor timing involving a clock or serial interrupt. I haven't made much headway at investigating it yet, and it looks like serial break is of no help, but will attempt to see what I can do this afternoon. I suspect without NMI on the box in question it will be dificult. I haven't yet tried with a UP kernel, however, only SMP. That said, with the critical section optimization in place and moving UMA to using critical sections rather than mutexes for the per-CPU cache on SMP, I see a small but heathy performance improvement in the socket create/destroy micro-benchmark: x netperf-socket-smp + percpu-socket-smp +--------------------------------------------------------------------------+ | + x | | ++ x xxx| |+ + ++++ + xxxxx| | |____A____| |AM|| +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 10 6.64e-06 6.676e-06 6.666e-06 6.6601e-06 1.2359881e-08 + 10 6.078e-06 6.236e-06 6.172e-06 6.165e-06 4.0734915e-08 Difference at 95.0% confidence -4.951e-07 +/- 2.82825e-08 -7.43382% +/- 0.424655% (Student's t, pooled s = 3.01007e-08) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 16:47:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB91C16A4CE for ; Thu, 25 Nov 2004 16:47:03 +0000 (GMT) Received: from hotmail.com (bay17-f5.bay17.hotmail.com [64.4.43.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBE8843D1F for ; Thu, 25 Nov 2004 16:47:03 +0000 (GMT) (envelope-from pheeleep@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 25 Nov 2004 08:47:02 -0800 Message-ID: Received: from 193.136.39.100 by by17fd.bay17.hotmail.msn.com with HTTP; Thu, 25 Nov 2004 16:46:12 GMT X-Originating-IP: [193.136.39.100] X-Originating-Email: [pheeleep@hotmail.com] X-Sender: pheeleep@hotmail.com From: "Dude Dude" To: freebsd-amd64@freebsd.org Date: Thu, 25 Nov 2004 16:46:12 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 25 Nov 2004 16:47:02.0668 (UTC) FILETIME=[639134C0:01C4D30E] Subject: Defenitive dual dimm under 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, 25 Nov 2004 16:47:04 -0000 Hey, one last , if i have 2 (equal) 512MB samsung DDR dimm, will these work as dual channel dimm? dual channel only require that i have 2 equal ddr cards?? or dual dimm ddr dimm's, are special type of ram? thks _________________________________________________________________ MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 20:42:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72FC416A4CE for ; Thu, 25 Nov 2004 20:42:35 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5140243D45 for ; Thu, 25 Nov 2004 20:42:35 +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 28B9D2A8D5 for ; Thu, 25 Nov 2004 12:42:35 -0800 (PST) (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 87121E2B3 for ; Thu, 25 Nov 2004 12:42:34 -0800 (PST) (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 iAPKgX5s003666; Thu, 25 Nov 2004 12:42:33 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAPKgXa4003665; Thu, 25 Nov 2004 12:42:33 -0800 (PST) (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: Thu, 25 Nov 2004 12:42:33 -0800 User-Agent: KMail/1.7 References: <20041116052630.GD49800@manor.msen.com> <20041124070652.GT49800@manor.msen.com> <80EAD071-3E8F-11D9-AF21-000D93AD5C52@hydrix.com> In-Reply-To: <80EAD071-3E8F-11D9-AF21-000D93AD5C52@hydrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411251242.33406.peter@wemm.org> Subject: Re: How to use older libs in 32bit mode? 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, 25 Nov 2004 20:42:35 -0000 On Wednesday 24 November 2004 07:10 pm, Jean-Yves Avenard wrote: > On 24/11/2004, at 6:06 PM, Michael R. Wayne wrote: > > Sorry. No success as in it cores. > > Exact same thing here. Any attempts to run a 32 bits executable on an > AMD64 machines result in a coredump > > Jean-Yves Things to check: * Make sure you have COMPAT_IA32 in your kernel config. For example, this command should work: peter@overcee[8:16pm]~/fbp4/hammer/sys/amd64/conf-120> sysctl kern.elf32 kern.elf32.fallback_brand: -1 (The important thing is that it prints something, not the value) * Make sure you have NOT copied ld-elf or libc from an i386 system. You *MUST* build at least these two on your machine. How to check: peter@overcee[8:17pm]~-123> strings /libexec/ld-elf32.so.1 | grep libmap32 /etc/libmap32.conf If this comes up empty, you're in trouble. Check that /usr/libexec/ld-elf32.so.1 and /libexec/ld-elf.so.1 are the same file. If you are running 5.3-stable and not 5.3-release, you can check libc like this: peter@overcee[8:18pm]~-125> objdump --dynamic-syms /usr/lib32/libc.so.5 | grep fsbase 00026500 g DF .text 0000002b _amd64_set_fsbase 00026580 g DF .text 0000004a _amd64_get_fsbase These will not be present on a 5.3-release system. Oh wait a second. Did you build your libraries with WITH_LIB32=yes or by running build32.sh ? I have a suspicion that build32.sh will produce a bad library now. BTW: it is helpful to do a ktrace/kdump and show the last few lines. I suspect there will be a sysarch syscall, followed by a SIGSEGV. -- 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 Thu Nov 25 21:17:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34DC616A4CE for ; Thu, 25 Nov 2004 21:17:23 +0000 (GMT) Received: from dglawrence.com (c-24-21-223-117.client.comcast.net [24.21.223.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03FB243D58 for ; Thu, 25 Nov 2004 21:17:23 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.1/8.13.1) with ESMTP id iAPLHMH0005914; Thu, 25 Nov 2004 13:17:22 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.1/8.13.1/Submit) id iAPLHM7l005913; Thu, 25 Nov 2004 13:17:22 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Thu, 25 Nov 2004 13:17:22 -0800 From: "David G. Lawrence" To: Dude Dude Message-ID: <20041125211722.GB673@opteron.dglawrence.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-amd64@freebsd.org Subject: Re: Defenitive dual dimm under 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, 25 Nov 2004 21:17:23 -0000 > Hey, > one last , > > if i have 2 (equal) 512MB samsung DDR dimm, will these work as dual channel > dimm? > dual channel only require that i have 2 equal ddr cards?? > > or dual dimm ddr dimm's, are special type of ram? "Dual channel" refers to the motherboard/processor/memory controller and not to the memory modules themselves. When manufactures sell "dual channel" memory, what they mean is that the modules are compatible with dual channel memory systems. There is nothing special about the modules other than that they are the same (size, timing, row/column layout, banks, etc). -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 Thu Nov 25 22:10:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A81916A4CF for ; Thu, 25 Nov 2004 22:10:55 +0000 (GMT) Received: from lakermmtao10.cox.net (lakermmtao10.cox.net [68.230.240.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id B509843D58 for ; Thu, 25 Nov 2004 22:10:54 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041125221052.BTQ22973.lakermmtao10.cox.net@dolphin.local.net>; Thu, 25 Nov 2004 17:10:52 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id iAPMArmJ073690; Thu, 25 Nov 2004 16:10:53 -0600 (CST) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.13.1/8.13.1/Submit) id iAPMAi33073689; Thu, 25 Nov 2004 16:10:44 -0600 (CST) (envelope-from conrads) From: "Conrad J. Sabatier" To: Kenneth Culver In-Reply-To: <20041124143634.ji8s8k80o84w8ksg@www.sweetdreamsracing.biz> References: <20041124145143.O4002@april.chuckr.org> <20041124143634.ji8s8k80o84w8ksg@www.sweetdreamsracing.biz> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Evolution-Format: text/plain X-Evolution-Account: conrads@cox.net X-Evolution-Transport: smtp://conrads@localhost X-Evolution-Fcc: email://1101338965.1174.12@dolphin.local.net/sent Organization: A Rag-Tag Band of Drug-Crazed Hippies X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Date: Thu, 25 Nov 2004 15:57:29 -0600 Message-Id: <1101419849.64190.2.camel@dolphin.local.net> Mime-Version: 1.0 X-Evolution: 00000010-0010 cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 22:10:55 -0000 On Wed, 2004-11-24 at 14:36 -0500, Kenneth Culver wrote: > > acroread is a linux binary. I'm not sure that 32 bit linux emulation works yet > on amd64... although I could be wrong. 32-bit Linux emulation has been working for a good while now. Haven't you tried it yet? -- Conrad J. Sabatier -- conrads@cox.net -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 22:57:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A777C16A4CE for ; Thu, 25 Nov 2004 22:57:22 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C4C243D54 for ; Thu, 25 Nov 2004 22:57:21 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.11] (CPE-144-133-92-247.vic.bigpond.net.au [144.133.92.247]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id iAPMvDP3060861 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 26 Nov 2004 09:57:15 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: <200411251242.33406.peter@wemm.org> References: <20041116052630.GD49800@manor.msen.com> <20041124070652.GT49800@manor.msen.com> <80EAD071-3E8F-11D9-AF21-000D93AD5C52@hydrix.com> <200411251242.33406.peter@wemm.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <560E2314-3F35-11D9-AF21-000D93AD5C52@hydrix.com> Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Fri, 26 Nov 2004 09:57:09 +1100 To: Peter Wemm X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.2 required=6.5 tests=ALL_TRUSTED,J_CHICKENPOX_73 autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/533/Sun Oct 17 11:09:44 2004 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: How to use older libs in 32bit mode? 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, 25 Nov 2004 22:57:22 -0000 Hello Peter. I have checked several times the mail list and each time I pass those *tests* On 26/11/2004, at 7:42 AM, Peter Wemm wrote: > Things to check: > > * Make sure you have COMPAT_IA32 in your kernel config. For example, > this command should work: > It is > peter@overcee[8:16pm]~/fbp4/hammer/sys/amd64/conf-120> sysctl > kern.elf32 > kern.elf32.fallback_brand: -1 > (The important thing is that it prints something, not the value) > server3# sysctl kern.elf32 kern.elf32.fallback_brand: -1 > > * Make sure you have NOT copied ld-elf or libc from an i386 system. > You *MUST* build at least these two on your machine. How to check: > > peter@overcee[8:17pm]~-123> strings /libexec/ld-elf32.so.1 | grep > libmap32 > /etc/libmap32.conf server3# strings /libexec/ld-elf32.so.1 | grep libmap32 /etc/libmap32.conf > If this comes up empty, you're in trouble. Check that > /usr/libexec/ld-elf32.so.1 and /libexec/ld-elf.so.1 are the same file. > Hum.. They aren't server3# ls -l total 504 -r-xr-xr-x 1 root wheel 173248 Nov 5 13:42 ld-elf.so.1 -r-xr-xr-x 1 root wheel 151620 Nov 26 04:02 ld-elf32.so.1 somebody sent me a copy on a system that did work and they didn't have the same ld-elf files either > If you are running 5.3-stable and not 5.3-release, you can check libc > like this: > > peter@overcee[8:18pm]~-125> objdump --dynamic-syms > /usr/lib32/libc.so.5 | grep fsbase > 00026500 g DF .text 0000002b _amd64_set_fsbase > 00026580 g DF .text 0000004a _amd64_get_fsbase > server3# objdump --dynamic-syms /usr/lib32/libc.so.5 | grep fsbase server3# Hum. Now that's weird. I'm not using 5.3-release anymore but STABLE. This is an extract of the cvsup file i'm using: *default host=cvsup.au.freebsd.org *default base=/usr *default prefix=/usr # The following line is for 4-stable. If you want 3-stable or 2.2-stable, # change "RELENG_4" to "RELENG_3" or "RELENG_2_2" respectively. *default release=cvs tag=RELENG_5 I did a make update last night and recompiled both KERNEL and WORLD > These will not be present on a 5.3-release system. > > Oh wait a second. Did you build your libraries with > WITH_LIB32=yes or by running build32.sh ? I have a suspicion > that build32.sh will produce a bad library now. > I did with both. Same result. First I did a makebuildworld make installworld , tried the simple Hello World program compiled on a FreeBSD 5.3-release i386 machine: core dump Then i deleted the /lib32 and /usr/lib32 and ran the build32.sh scripts. Same result: core dump > BTW: it is helpful to do a ktrace/kdump and show the last few lines. > I suspect there will be a sysarch syscall, followed by a SIGSEGV. If you could give me more details on how to do this it would be great. Thank you for your time and help here Jean-Yves --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 25 23:07:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24BBD16A4CE for ; Thu, 25 Nov 2004 23:07:59 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9250143D45 for ; Thu, 25 Nov 2004 23:07:58 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/4.23) with ESMTP id iAPN7ptw014955; Fri, 26 Nov 2004 00:07:51 +0100 (MET) From: groot@kde.org To: "Conrad J. Sabatier" Date: Fri, 26 Nov 2004 00:07:56 +0100 User-Agent: KMail/1.7.50 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411260007.57587.groot@kde.org> cc: freebsd-amd64@freebsd.org Subject: Cross-compiling amd64 on x86 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, 25 Nov 2004 23:07:59 -0000 Unfortunately, buying a second amd64 system is faster than figuring out how to cross compile (and less aggravating, too), so that's what I've done. I followed a number of links around (http://www.kegel.com/crosstool/), but there is nothing really comprehensive nor anything simple and straightforward. I did hack the ports Makefile a little to allow me to set the target architecture, and indeed, it does build _a_ gcc for amd64 then, but the bootstrapping process then tries to use that amd64 compiler to build itself - on x86, which fails. So there's two issues: - getting binutils for amd64 built on x86. This is not addressed by messing with the existing ports. - getting gcc built and doing only the first-stage of the bootstrap. The latter should be fairly simple for someone who understands the build process for gcc; the port itself provides a useful invocation of configure that you would need to modify. binutils is another can of worm(let)s, but that URL above suggests that this might even happen automatically if you unpack them into the gcc source tree. From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 15:34:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AC9C16A4CE for ; Fri, 26 Nov 2004 15:34:01 +0000 (GMT) Received: from hermes.aboutit.co.za (nat.aboutit.co.za [196.23.168.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF2A243D48 for ; Fri, 26 Nov 2004 15:33:59 +0000 (GMT) (envelope-from mark@aboutit.co.za) Received: by hermes.aboutit.co.za (Postfix, from userid 65534) id 6A9F4B1D62; Fri, 26 Nov 2004 17:33:56 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by hermes.aboutit.co.za (Postfix) with ESMTP id 81CA2B1D7F; Fri, 26 Nov 2004 17:33:55 +0200 (SAST) Received: from hermes.aboutit.co.za (localhost [127.0.0.1]) by hermes.aboutit.co.za (Postfix) with ESMTP id 05D86A6EFA; Fri, 26 Nov 2004 17:33:55 +0200 (SAST) Message-ID: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> From: Mark Bojara To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (normal) X-Mailer: SuSE Linux Openexchange Server 4 - WebMail (Build 2.3780) X-Operating-System: Linux 2.4.19-4GB i386 (JVM 1.3.1_04) Organization: AboutIT Online Date: Fri, 26 Nov 2004 17:33:55 +0200 (SAST) X-Virus-Scanned: by AMaViS snapshot-20020531 X-Spam-Status: No, hits=-0.5 required=8.0 tests=AWL version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Page fault on Tyan K8S Pro (S2882) board 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, 26 Nov 2004 15:34:01 -0000 Hello All, For the last 3 weeks I have been trying to get this motherboard to run with 5.3-STABLE. Basically what happens is if I run the box at 100% utilization the server is stable but as soon as I let it idle and do basic Apache webserver tests and other small apps an hour after that the server will crash. I have tried enabling debug support in my kernel to supply the mailing list with a debug of the error but it seems that when it page faults the entire machine locks up. Please let me know if you require any additional information. Spec: 2 x AMD Opteron 242 CPU's 1 x 1GB Corsair PC2700 Memory Module Bios Version 2.03E Error: Fatal trap 12: page fault while in kernel mode cpu id =1; apic id=01 fault virtual address = 0x18 fault code = supervisor read,page not present Instruction pointer = 0x8:0xffffffffa25bc800 frame pointer = 0x10:0x0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, olef32 0, gran 1 trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 uptime 10h3m45s I have also tried disabling ACPI to see if thats the problem but the server still crashes Thanks Alot Mark Bojara AboutIT Online - 012-460-1000 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 17:54:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D441916A4CE for ; Fri, 26 Nov 2004 17:54:06 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE5E343D64 for ; Fri, 26 Nov 2004 17:54:00 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.208] [213.112.167.208]) by mxfep02.bredband.com with ESMTP id <20041126175359.HRY24004.mxfep02.bredband.com@[192.168.245.231]>; Fri, 26 Nov 2004 18:53:59 +0100 Message-ID: <41A76D8E.5090507@bredband.net> Date: Fri, 26 Nov 2004 18:53:18 +0100 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20041024 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Bojara References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> In-Reply-To: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Page fault on Tyan K8S Pro (S2882) board 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, 26 Nov 2004 17:54:06 -0000 Mark Bojara wrote: > Hello All, > > For the last 3 weeks I have been trying to get this motherboard to run with 5.3-STABLE. Basically what happens is if I run the box at 100% utilization the server is stable but as soon as I let it idle and do basic Apache webserver tests and other small apps an hour after that the server will crash. I have tried enabling debug support in my kernel to supply the mailing list with a debug of the error but it seems that when it page faults the entire machine locks up. Please let me know if you require any additional information. > > Spec: > 2 x AMD Opteron 242 CPU's > 1 x 1GB Corsair PC2700 Memory Module > Bios Version 2.03E That memory setup seems to be wrong. you should have at least 4 DIMM's in the machine. two for each CPU. I dont think the board would even run on a single DIMM. Please tell us more about how your RAM is configured. //LArs From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 18:46:05 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA4A016A52F for ; Fri, 26 Nov 2004 18:46:03 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33A0643D31 for ; Fri, 26 Nov 2004 18:46:03 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id iAQIk0O7074645 for ; Fri, 26 Nov 2004 13:46:02 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id iAQIk0x6074644 for freebsd-amd64@freebsd.org; Fri, 26 Nov 2004 13:46:00 -0500 (EST) (envelope-from wayne) Date: Fri, 26 Nov 2004 13:46:00 -0500 From: "Michael R. Wayne" To: freebsd-amd64@freebsd.org Message-ID: <20041126184559.GJ49800@manor.msen.com> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041116052630.GD49800@manor.msen.com> <20041124070652.GT49800@manor.msen.com> <80EAD071-3E8F-11D9-AF21-000D93AD5C52@hydrix.com> <200411251242.33406.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411251242.33406.peter@wemm.org> User-Agent: Mutt/1.4.2.1i Subject: Re: How to use older libs in 32bit mode? 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, 26 Nov 2004 18:46:06 -0000 On Thu, Nov 25, 2004 at 12:42:33PM -0800, Peter Wemm wrote: > Things to check: > > * Make sure you have COMPAT_IA32 in your kernel config. For example, > this command should work: > > peter@overcee[8:16pm]~/fbp4/hammer/sys/amd64/conf-120> sysctl kern.elf32 > kern.elf32.fallback_brand: -1 > (The important thing is that it prints something, not the value) Yes: > sysctl kern.elf32 kern.elf32.fallback_brand: -1 > * Make sure you have NOT copied ld-elf or libc from an i386 system. > You *MUST* build at least these two on your machine. How to check: > > peter@overcee[8:17pm]~-123> strings /libexec/ld-elf32.so.1 | grep libmap32 > /etc/libmap32.conf > If this comes up empty, you're in trouble. Check that > /usr/libexec/ld-elf32.so.1 and /libexec/ld-elf.so.1 are the same file. So far OK: > strings /libexec/ld-elf32.so.1 | grep libmap32 /etc/libmap32.conf and lrwxr-xr-x 1 root wheel 22 Nov 15 17:13 /usr/libexec/ld-elf32.so.1@ -> /libexec/ld-elf32.so.1 > These will not be present on a 5.3-release system. Running 5.3-RELEASE so they are not present, as expected. > Oh wait a second. Did you build your libraries with > WITH_LIB32=yes or by running build32.sh ? I have a suspicion > that build32.sh will produce a bad library now. Aha. Yes, I built with build32.sh as it was the only way I found to do it. If this is not correct, perhaps someone could put up a quick "how-to" page and post a URL? It would also be useful to understand how to build a port for i386, google was not helpful in determining how to do this. > BTW: it is helpful to do a ktrace/kdump and show the last few lines. > I suspect there will be a sysarch syscall, followed by a SIGSEGV. You are correct: 72509 hello CALL sysarch(0x1,0xffffd70c) 72509 hello RET sysarch -1 errno 22 Invalid argument 72509 hello PSIG SIGSEGV SIG_DFL 72509 hello NAMI "hello.core" So, it looks like build32.sh is broken on 5.3-RELEASE. What now? /\/\ \/\/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 18:58:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E7F116A4CE for ; Fri, 26 Nov 2004 18:58:43 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4349343D5E for ; Fri, 26 Nov 2004 18:58:43 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAQIwXOi008684; Fri, 26 Nov 2004 10:58:33 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAQIwWfR008683; Fri, 26 Nov 2004 10:58:32 -0800 (PST) (envelope-from sgk) Date: Fri, 26 Nov 2004 10:58:32 -0800 From: Steve Kargl To: Lars Tunkrans Message-ID: <20041126185832.GA8665@troutmask.apl.washington.edu> References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> <41A76D8E.5090507@bredband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A76D8E.5090507@bredband.net> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: Page fault on Tyan K8S Pro (S2882) board 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, 26 Nov 2004 18:58:43 -0000 On Fri, Nov 26, 2004 at 06:53:18PM +0100, Lars Tunkrans wrote: > That memory setup seems to be wrong. > you should have at least 4 DIMM's in the machine. > two for each CPU. I dont think the board would even run > on a single DIMM. > > Please tell us more about how your RAM is configured. The board will work with 1 DIMM, but 2 would be better. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 19:17:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F01C16A4CE for ; Fri, 26 Nov 2004 19:17:04 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EBD43D1F for ; Fri, 26 Nov 2004 19:17:04 +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 ECEB72A8E0 for ; Fri, 26 Nov 2004 11:17:03 -0800 (PST) (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 7B82BE2B3 for ; Fri, 26 Nov 2004 11:17:03 -0800 (PST) (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 iAQJH3cq017533; Fri, 26 Nov 2004 11:17:03 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAQJH2vv017532; Fri, 26 Nov 2004 11:17:02 -0800 (PST) (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: Fri, 26 Nov 2004 11:17:02 -0800 User-Agent: KMail/1.7 References: <20041116052630.GD49800@manor.msen.com> <200411251242.33406.peter@wemm.org> <20041126184559.GJ49800@manor.msen.com> In-Reply-To: <20041126184559.GJ49800@manor.msen.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411261117.02622.peter@wemm.org> Subject: Re: How to use older libs in 32bit mode? 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, 26 Nov 2004 19:17:04 -0000 On Friday 26 November 2004 10:46 am, Michael R. Wayne wrote: > On Thu, Nov 25, 2004 at 12:42:33PM -0800, Peter Wemm wrote: > > Things to check: > > > > * Make sure you have COMPAT_IA32 in your kernel config. For > > example, this command should work: > > > > peter@overcee[8:16pm]~/fbp4/hammer/sys/amd64/conf-120> sysctl > > kern.elf32 kern.elf32.fallback_brand: -1 > > (The important thing is that it prints something, not the value) > > Yes: > > sysctl kern.elf32 > > kern.elf32.fallback_brand: -1 > > > * Make sure you have NOT copied ld-elf or libc from an i386 system. > > You *MUST* build at least these two on your machine. How to check: > > > > peter@overcee[8:17pm]~-123> strings /libexec/ld-elf32.so.1 | grep > > libmap32 /etc/libmap32.conf > > If this comes up empty, you're in trouble. Check that > > /usr/libexec/ld-elf32.so.1 and /libexec/ld-elf.so.1 are the same > > file. > > So far OK: > > strings /libexec/ld-elf32.so.1 | grep libmap32 > > /etc/libmap32.conf > and > lrwxr-xr-x 1 root wheel 22 Nov 15 17:13 > /usr/libexec/ld-elf32.so.1@ -> /libexec/ld-elf32.so.1 > > > These will not be present on a 5.3-release system. > > Running 5.3-RELEASE so they are not present, as expected. > > > Oh wait a second. Did you build your libraries with > > WITH_LIB32=yes or by running build32.sh ? I have a suspicion > > that build32.sh will produce a bad library now. > > Aha. Yes, I built with build32.sh as it was the only way I found to > do it. If this is not correct, perhaps someone could put up a > quick "how-to" page and post a URL? > > It would also be useful to understand how to build a port for i386, > google was not helpful in determining how to do this. > > > BTW: it is helpful to do a ktrace/kdump and show the last few > > lines. I suspect there will be a sysarch syscall, followed by a > > SIGSEGV. > > You are correct: > 72509 hello CALL sysarch(0x1,0xffffd70c) > 72509 hello RET sysarch -1 errno 22 Invalid argument > 72509 hello PSIG SIGSEGV SIG_DFL > 72509 hello NAMI "hello.core" > > So, it looks like build32.sh is broken on 5.3-RELEASE. What now? Oh no! It means that FreeBSD/i386 binaries unconditionally use TLS (thread-local-storage) setup calls in early startup. That means we are hosed until a bunch of TLS support routines are merged from 6.0 to 5.3-stable. Unfortunately, there is nothing that you can do for now. :-( -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 20:38:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F20CB16A4CE for ; Fri, 26 Nov 2004 20:38:20 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B205543D5C for ; Fri, 26 Nov 2004 20:38:20 +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 756B72A8D5 for ; Fri, 26 Nov 2004 12:38:20 -0800 (PST) (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 1CFEAE2B3 for ; Fri, 26 Nov 2004 12:38:20 -0800 (PST) (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 iAQKcJTU018460 for ; Fri, 26 Nov 2004 12:38:19 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAQKcJFZ018459 for freebsd-amd64@freebsd.org; Fri, 26 Nov 2004 12:38:19 -0800 (PST) (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: Fri, 26 Nov 2004 12:38:19 -0800 User-Agent: KMail/1.7 References: <20041116052630.GD49800@manor.msen.com> <20041126184559.GJ49800@manor.msen.com> <200411261117.02622.peter@wemm.org> In-Reply-To: <200411261117.02622.peter@wemm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411261238.19311.peter@wemm.org> Subject: Re: How to use older libs in 32bit mode? 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, 26 Nov 2004 20:38:21 -0000 On Friday 26 November 2004 11:17 am, Peter Wemm wrote: > On Friday 26 November 2004 10:46 am, Michael R. Wayne wrote: > > On Thu, Nov 25, 2004 at 12:42:33PM -0800, Peter Wemm wrote: > > > Things to check: > > > > > > * Make sure you have COMPAT_IA32 in your kernel config. For > > > example, this command should work: > > > > > > peter@overcee[8:16pm]~/fbp4/hammer/sys/amd64/conf-120> sysctl > > > kern.elf32 kern.elf32.fallback_brand: -1 > > > (The important thing is that it prints something, not the value) > > > > Yes: > > > sysctl kern.elf32 > > > > kern.elf32.fallback_brand: -1 > > > > > * Make sure you have NOT copied ld-elf or libc from an i386 > > > system. You *MUST* build at least these two on your machine. How > > > to check: > > > > > > peter@overcee[8:17pm]~-123> strings /libexec/ld-elf32.so.1 | grep > > > libmap32 /etc/libmap32.conf > > > If this comes up empty, you're in trouble. Check that > > > /usr/libexec/ld-elf32.so.1 and /libexec/ld-elf.so.1 are the same > > > file. > > > > So far OK: > > > strings /libexec/ld-elf32.so.1 | grep libmap32 > > > > /etc/libmap32.conf > > and > > lrwxr-xr-x 1 root wheel 22 Nov 15 17:13 > > /usr/libexec/ld-elf32.so.1@ -> /libexec/ld-elf32.so.1 > > > > > These will not be present on a 5.3-release system. > > > > Running 5.3-RELEASE so they are not present, as expected. > > > > > Oh wait a second. Did you build your libraries with > > > WITH_LIB32=yes or by running build32.sh ? I have a suspicion > > > that build32.sh will produce a bad library now. > > > > Aha. Yes, I built with build32.sh as it was the only way I found > > to do it. If this is not correct, perhaps someone could put up a > > quick "how-to" page and post a URL? > > > > It would also be useful to understand how to build a port for i386, > > google was not helpful in determining how to do this. > > > > > BTW: it is helpful to do a ktrace/kdump and show the last few > > > lines. I suspect there will be a sysarch syscall, followed by a > > > SIGSEGV. > > > > You are correct: > > 72509 hello CALL sysarch(0x1,0xffffd70c) > > 72509 hello RET sysarch -1 errno 22 Invalid argument > > 72509 hello PSIG SIGSEGV SIG_DFL > > 72509 hello NAMI "hello.core" > > > > So, it looks like build32.sh is broken on 5.3-RELEASE. What now? > > Oh no! It means that FreeBSD/i386 binaries unconditionally use TLS > (thread-local-storage) setup calls in early startup. That means we > are hosed until a bunch of TLS support routines are merged from 6.0 > to 5.3-stable. > > Unfortunately, there is nothing that you can do for now. :-( I've merged some of the changes (rtld-elf/reloc.c and libc/i386/gen/_set_tp.c), and removed build32.sh from RELENG_5. If you were to build a new set of libraries, I expect it will work now. libc_r threaded binaries might work, but libthr and libpthread binaries will not. If you need to run something threaded, you can set libmap32.conf to remap all libthr or libpthread references into libc_r. BTW: if you have already done a buildworld, it might be possible to rebuild just the 32 bit libraries without a full buildworld again. If you want to try this, then "cd /usr/src; rm -rf /usr/obj/lib32; make build32; make install32" -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 26 21:35:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C9E916A4CE; Fri, 26 Nov 2004 21:35:17 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3530A43D49; Fri, 26 Nov 2004 21:35:17 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iAQLZGnZ057650; Fri, 26 Nov 2004 13:35:16 -0800 (PST) (envelope-from marcel@xcllnt.net) In-Reply-To: <200411231631.00945.jhb@FreeBSD.org> References: <200411231500.55841.jhb@FreeBSD.org> <200411231631.00945.jhb@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0F35A925-3FF3-11D9-8DD8-000D93C47836@xcllnt.net> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Fri, 26 Nov 2004 13:35:14 -0800 To: John Baldwin X-Mailer: Apple Mail (2.619) cc: amd64@freebsd.org cc: powerpc@freebsd.org cc: Robert Watson cc: ia64@freebsd.org Subject: Re: Patch to optimize "bare" critical sections 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, 26 Nov 2004 21:35:17 -0000 On Nov 23, 2004, at 1:31 PM, John Baldwin wrote: > On Tuesday 23 November 2004 03:00 pm, John Baldwin wrote: >> Basically, I have a patch to divorce the interrupt disable/deferring >> to >> only happen inside of spinlocks using a new spinlock_enter/exit() API >> (where a spinlock_enter/exit includes a critical section as well) but >> that >> plain critical sections won't have to do such a thing. I've tested >> it on >> i386, alpha, and sparc64 already, and it has also been tested on arm. >> I'm >> unable to get a cross-built powerpc kernel to link (linker dies with a >> signal 6), but the compile did finish. I have cross-compiled ia64 and >> amd64 >> successfully, but have not run tested due to ENOHARDWARE. So, I would >> appreciate it if a few folks could try the patch out on ppc, ia64, and >> amd64 to make sure it works ok. Thanks. > > *cough* Ahem, http://www.FreeBSD.org/~jhb/patches/spinlock.patch No problems on ia64. I haven't loaded the machine to see if I get the wedge Robert was talking about, but I'm not too worried about that at the moment. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 00:03:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3911416A4CF for ; Sat, 27 Nov 2004 00:03:29 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E483843D31 for ; Sat, 27 Nov 2004 00:03:27 +0000 (GMT) (envelope-from a.degroot@science.ru.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=odin.cs.kun.nl) by pandora.cs.kun.nl (8.12.10/4.23) with ESMTP id iAR03Qtx010933 for ; Sat, 27 Nov 2004 01:03:26 +0100 (MET) Date: Sat, 27 Nov 2004 01:03:26 +0100 (MET) From: a.degroot@science.ru.nl X-X-Sender: adridg@odin.cs.kun.nl To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: xmbmon 205 bogus on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: a.degroot@science.ru.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 00:03:29 -0000 Trying to quiet down my rather noisy machine, I turned on cool 'n quiet and some other fan control gadget, which leads me to wanting to monitor the CPU temperature for now to see that it doesn't freak out. With xmbmon 204, I get output like this (the CPU fan is indeed stopped now): Temp.= 32.0, 52.0, 0.0; Rot.= 0, 0, 0 Vcore = 1.57, 0.00; Volt. = 3.41, 5.11, 11.31, 0.39, 5.11 xmbmon 205, on the other hand, gives me all voltages 0, and a temperature of 124 degrees. Can anyone else confirm (similar weirdness)? FWIW, this is on an Asus K8V SE, a Via KT800-based board. -- As of September 1st, 2004, the University of Nijmegen will _still_ be the University of Nijmegen, but with a different nonsensical adjective in front. Reach me at groot@kde.org instead. GPG FEA2 A3FE From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 05:01:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0C4916A4CE for ; Sat, 27 Nov 2004 05:01:51 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9336443D1F for ; Sat, 27 Nov 2004 05:01:51 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by mproxy.gmail.com with SMTP id w41so139378cwb for ; Fri, 26 Nov 2004 21:01:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding; b=DldtwfAmPTKueGMZN2JmuEsDW0mKw8w14lXzc2lXK+vnwRaS4OvUYzwTpUjS26USwkmlID5kbM9vW20+qV+sxajt031IuhmGEpxnnKF3npxDcHdXNYVb647SOf/vUayIBZOkxvi2/AErx4mI/ztplXK4K4nQ6/5hzHfX2Jj9V+o= Received: by 10.11.99.16 with SMTP id w16mr39385cwb; Fri, 26 Nov 2004 21:01:50 -0800 (PST) Received: from ?192.168.102.103? ([67.160.118.158]) by smtp.gmail.com with ESMTP id o9sm3953cwc; Fri, 26 Nov 2004 21:01:50 -0800 (PST) Message-ID: <41A80A0F.9030502@gmail.com> Date: Fri, 26 Nov 2004 21:01:03 -0800 From: Astrodog User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Bojara , freebsd-amd64@freebsd.org References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> In-Reply-To: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Page fault on Tyan K8S Pro (S2882) board 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, 27 Nov 2004 05:01:52 -0000 Mark Bojara wrote: >Hello All, > >For the last 3 weeks I have been trying to get this motherboard to run with 5.3-STABLE. Basically what happens is if I run the box at 100% utilization the server is stable but as soon as I let it idle and do basic Apache webserver tests and other small apps an hour after that the server will crash. I have tried enabling debug support in my kernel to supply the mailing list with a debug of the error but it seems that when it page faults the entire machine locks up. Please let me know if you require any additional information. > >Spec: >2 x AMD Opteron 242 CPU's >1 x 1GB Corsair PC2700 Memory Module >Bios Version 2.03E > > >Error: >Fatal trap 12: page fault while in kernel mode >cpu id =1; apic id=01 >fault virtual address = 0x18 >fault code = supervisor read,page not present >Instruction pointer = 0x8:0xffffffffa25bc800 >frame pointer = 0x10:0x0 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, olef32 0, gran 1 >trap number = 12 >panic: page fault >cpuid = 1 >boot() called on cpu#1 >uptime 10h3m45s > >I have also tried disabling ACPI to see if thats the problem but the server still crashes > >Thanks Alot >Mark Bojara >AboutIT Online - 012-460-1000 > >_______________________________________________ >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" > > > Couple things. We use this setup pretty often, but there are a couple things to keep in mind. #1. on the 4 bank Tyan Tiger boards (K8W), you have one CPU acting as a memory controller for the other. The second CPU makes use of AMD's Hypertransport system for this access. #2. I'd put $50 on the problem going away with SMP disabled, but thats a whole new can of worms. #3. AMD Opteron processors expect, and for all intents and purposes, require ECC Registered Memory. Furthermore, they expect the memory to operate in a dual channel mode. Running 1 DIMM in this kind of setup is shooting yourself in the foot. If CPU #1 requests something through CPU #0, and we're using 1 bank of memory the whole setup..... performance is gonna be crap. Both CPUs will be blocked from processing instructions while the request is fulfilled. There are known performance issues with the 4+0 memory config... but they're still good if you use 2 or 4 DIMMs. It boils down to adding another DIMM, and seeing if that solves your problem. I would strongly suspect that it will quite easily. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 11:40:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11E5316A4CE for ; Sat, 27 Nov 2004 11:40:49 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9021E43D49 for ; Sat, 27 Nov 2004 11:40:48 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so544797wri for ; Sat, 27 Nov 2004 03:40:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=BuHBtO+y/xbC1CE9CECFrEQ+W26H6ynGemQHXgEbjoGXVpBC13I2NlSFfVGD0o4lCrUY6gsTyldo2HhMB/VxASbCF5OvbBIoESlYIObDBiCXZ27FORzl5rJFMA4zgh2VPG4vIKcvfTHVenWctYplRVtY9Mr+uAf7kUmDKTrIEL0= Received: by 10.54.6.78 with SMTP id 78mr19420wrf; Sat, 27 Nov 2004 03:40:47 -0800 (PST) Received: by 10.54.3.2 with HTTP; Sat, 27 Nov 2004 03:40:47 -0800 (PST) Message-ID: <2fd864e0411270340503f3a68@mail.gmail.com> Date: Sat, 27 Nov 2004 03:40:47 -0800 From: Astrodog To: Mark Bojara , freebsd-amd64@freebsd.org In-Reply-To: <1101538050.17795.13.camel@mark.aboutit.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <606711.1101483235019.SLOX.WebMail.wwwrun@hermes.aboutit.co.za> <41A80A0F.9030502@gmail.com> <1101538050.17795.13.camel@mark.aboutit.co.za> Subject: Re: Page fault on Tyan K8S Pro (S2882) board 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: Sat, 27 Nov 2004 11:40:49 -0000 I'll take a look. We use the boards on -CURRENT atm with no ill effects. If there's an issue with it on 5_RELENG, I need to check it out. Will keep you posted. --- Harrison Grundy On Sat, 27 Nov 2004 08:47:30 +0200, Mark Bojara wrote: > Hey Harrison > > You are right about the memory speed problem I have noticed quite a > significant speed drop but I will be purchasing another DIMM shortly. > This however doesnt fix the problem because last week I had 4 x 256MB > DIMM's in the motherboard and I was having the same problem > > However setting net.inet.tcp.sack.enable=0 seems to have sorted out the > problem. I am unsure how important this feature is in 5.3 but Tyan > definatley does not like this! > > Thanks > Mark > > > > On Sat, 2004-11-27 at 07:01, Astrodog wrote: > > Mark Bojara wrote: > > > > >Hello All, > > > > > >For the last 3 weeks I have been trying to get this motherboard to run with 5.3-STABLE. Basically what happens is if I run the box at 100% utilization the server is stable but as soon as I let it idle and do basic Apache webserver tests and other small apps an hour after that the server will crash. I have tried enabling debug support in my kernel to supply the mailing list with a debug of the error but it seems that when it page faults the entire machine locks up. Please let me know if you require any additional information. > > > > > >Spec: > > >2 x AMD Opteron 242 CPU's > > >1 x 1GB Corsair PC2700 Memory Module > > >Bios Version 2.03E > > > > > > > > >Error: > > >Fatal trap 12: page fault while in kernel mode > > >cpu id =1; apic id=01 > > >fault virtual address = 0x18 > > >fault code = supervisor read,page not present > > >Instruction pointer = 0x8:0xffffffffa25bc800 > > >frame pointer = 0x10:0x0 > > >code segment = base 0x0, limit 0xfffff, type 0x1b > > > = DPL 0, pres 1, long 1, olef32 0, gran 1 > > >trap number = 12 > > >panic: page fault > > >cpuid = 1 > > >boot() called on cpu#1 > > >uptime 10h3m45s > > > > > >I have also tried disabling ACPI to see if thats the problem but the server still crashes > > > > > >Thanks Alot > > >Mark Bojara > > >AboutIT Online - 012-460-1000 > > > > > >_______________________________________________ > > >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" > > > > > > > > > > > Couple things. We use this setup pretty often, but there are a couple > > things to keep in mind. > > #1. on the 4 bank Tyan Tiger boards (K8W), you have one CPU acting as a > > memory controller for the other. The second CPU makes use of AMD's > > Hypertransport system for this access. > > > > #2. I'd put $50 on the problem going away with SMP disabled, but thats a > > whole new can of worms. > > > > #3. AMD Opteron processors expect, and for all intents and purposes, > > require ECC Registered Memory. Furthermore, they expect the memory to > > operate in a dual channel mode. Running 1 DIMM in this kind of setup is > > shooting yourself in the foot. If CPU #1 requests something through CPU > > #0, and we're using 1 bank of memory the whole setup..... performance is > > gonna be crap. Both CPUs will be blocked from processing instructions > > while the request is fulfilled. There are known performance issues with > > the 4+0 memory config... but they're still good if you use 2 or 4 DIMMs. > > > > It boils down to adding another DIMM, and seeing if that solves your > > problem. I would strongly suspect that it will quite easily. > > > > --- Harrison Grundy > > From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 13:58:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCEEF16A4CE for ; Sat, 27 Nov 2004 13:58:01 +0000 (GMT) Received: from hotmail.com (bay13-f32.bay13.hotmail.com [64.4.31.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id C803943D2D for ; Sat, 27 Nov 2004 13:58:01 +0000 (GMT) (envelope-from martarese@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 27 Nov 2004 05:58:01 -0800 Message-ID: Received: from 213.22.141.194 by by13fd.bay13.hotmail.msn.com with HTTP; Sat, 27 Nov 2004 13:57:49 GMT X-Originating-IP: [213.22.141.194] X-Originating-Email: [martarese@hotmail.com] X-Sender: martarese@hotmail.com From: "Marta Resende" To: freebsd-amd64@freebsd.org Date: Sat, 27 Nov 2004 13:57:49 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 27 Nov 2004 13:58:01.0026 (UTC) FILETIME=[1B80F220:01C4D489] Subject: error message: "NOTE: BIOS IS NOT INSTALLED" 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, 27 Nov 2004 13:58:02 -0000 hello, i had freebsd working in my machine(amd athlon xp and asus mobo), and today, i change the motherboard and cpu, and when i turn on the computer, it says: [NOTE]: THE BIOS IS NOT INSTALLED. and i reboot and press delete in the boot, to configure the bios, and i save&exit, and the same message appears. So... i did nothing after hardware installation of the mobo and cpu, should i have done something to proceed with bios installation?? i post in these forum cause this error was with a MSI k8t board and athlon 64. thank you! _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 14:30:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADD7216A4CE for ; Sat, 27 Nov 2004 14:30:55 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 852BA43D1F for ; Sat, 27 Nov 2004 14:30:54 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.11] (CPE-144-133-92-247.vic.bigpond.net.au [144.133.92.247]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id iAREUkno000843 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 28 Nov 2004 01:30:47 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: <200411261238.19311.peter@wemm.org> References: <20041116052630.GD49800@manor.msen.com> <20041126184559.GJ49800@manor.msen.com> <200411261117.02622.peter@wemm.org> <200411261238.19311.peter@wemm.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jean-Yves Avenard Date: Sun, 28 Nov 2004 01:30:40 +1100 To: Peter Wemm X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.8 required=6.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on server2.private.hydrix.com X-Virus-Scanned: ClamAV 0.80/533/Sun Oct 17 11:09:44 2004 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd-amd64@freebsd.org Subject: Re: How to use older libs in 32bit mode? 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, 27 Nov 2004 14:30:55 -0000 Hello On 27/11/2004, at 7:38 AM, Peter Wemm wrote: > I've merged some of the changes (rtld-elf/reloc.c and > libc/i386/gen/_set_tp.c), and removed build32.sh from RELENG_5. If you > were to build a new set of libraries, I expect it will work now. > libc_r threaded binaries might work, but libthr and libpthread > binaries will not. If you need to run something threaded, you can set > libmap32.conf to remap all libthr or libpthread references into libc_r. > did a make update this morning and I saw your changes; now buildworld doesn't compile anymore ! cc -m32 -march=athlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT -I/usr/obj/usr/src/lib32/usr/include -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32 -O -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/lib32/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libc/i386/gen/_set_tp.c /usr/src/lib/libc/i386/gen/_set_tp.c: In function `_set_tp': /usr/src/lib/libc/i386/gen/_set_tp.c:54: warning: implicit declaration of function `_amd64_set_gsbase' *** Error code 1 Stop in /usr/src/lib/libc. --- Jean-Yves Avenard Hydrix Pty Ltd - Embedding the net www.hydrix.com | fax +61 3 9572 2686 | phone +61 3 9572 0686 ext 100 VoIP: direct: 100@voip.hydrix.com, general: info@voip.hydrix.com From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 27 15:27:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3979A16A4CE for ; Sat, 27 Nov 2004 15:27:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id B129D43D5E for ; Sat, 27 Nov 2004 15:27:55 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so649494wra for ; Sat, 27 Nov 2004 07:27:53 -0800 (PST) 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:references; b=R34qaPGO9eDfNWNRG8hPTTTiNb1e6iICOx1Cv8J0jWUCzq47TuTieTFul8yV+o6hIqnDAf+wsPCOiakIzG489wHzmDwyNjojJGNvUc/ws0vEtHVSLdGs6krCH/Yx09ojSXNNuM/5cUScWSGFGARuJCumjNS+aJzfRD/dc1sgogA= Received: by 10.54.25.38 with SMTP id 38mr1739335wry; Sat, 27 Nov 2004 07:27:53 -0800 (PST) Received: by 10.54.3.2 with HTTP; Sat, 27 Nov 2004 07:27:53 -0800 (PST) Message-ID: <2fd864e0411270727793aa88a@mail.gmail.com> Date: Sat, 27 Nov 2004 07:27:53 -0800 From: Astrodog To: Marta Resende In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: cc: freebsd-amd64@freebsd.org Subject: Re: error message: "NOTE: BIOS IS NOT INSTALLED" 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: Sat, 27 Nov 2004 15:27:56 -0000 While not a FreeBSD issue.... it sounds like your CMOS battery may be dead. If its working... call MSI. On Sat, 27 Nov 2004 13:57:49 +0000, Marta Resende wrote: > hello, i had freebsd working in my machine(amd athlon xp and asus mobo), and > today, i change the motherboard and cpu, and when i turn on the computer, it > says: [NOTE]: THE BIOS IS NOT INSTALLED. > > and i reboot and press delete in the boot, to configure the bios, and i > save&exit, and the same message appears. > > So... i did nothing after hardware installation of the mobo and cpu, should > i have done something to proceed with bios installation?? > > i post in these forum cause this error was with a MSI k8t board and athlon > 64. > > thank you! > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > _______________________________________________ > 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 Sat Nov 27 20:25:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CBBF16A4CE for ; Sat, 27 Nov 2004 20:25:55 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5072A43D48 for ; Sat, 27 Nov 2004 20:25:55 +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 22A4D2A7EA for ; Sat, 27 Nov 2004 12:25:55 -0800 (PST) (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 5C846E2B3 for ; Sat, 27 Nov 2004 12:25:54 -0800 (PST) (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 iARKPrf4033421; Sat, 27 Nov 2004 12:25:53 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iARKPrWJ033420; Sat, 27 Nov 2004 12:25:53 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: Jean-Yves Avenard Date: Sat, 27 Nov 2004 12:25:53 -0800 User-Agent: KMail/1.7 References: <20041116052630.GD49800@manor.msen.com> <200411261238.19311.peter@wemm.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411271225.53359.peter@wemm.org> cc: freebsd-amd64@freebsd.org Subject: Re: How to use older libs in 32bit mode? 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, 27 Nov 2004 20:25:55 -0000 On Saturday 27 November 2004 06:30 am, Jean-Yves Avenard wrote: > Hello > > On 27/11/2004, at 7:38 AM, Peter Wemm wrote: > > I've merged some of the changes (rtld-elf/reloc.c and > > libc/i386/gen/_set_tp.c), and removed build32.sh from RELENG_5. If > > you were to build a new set of libraries, I expect it will work > > now. libc_r threaded binaries might work, but libthr and > > libpthread binaries will not. If you need to run something > > threaded, you can set libmap32.conf to remap all libthr or > > libpthread references into libc_r. > > did a make update this morning and I saw your changes; now buildworld > doesn't compile anymore ! OOPS! I'm an idiot! Now I've added the missing parts. -- 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 Sat Nov 27 20:28:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2097116A4CE for ; Sat, 27 Nov 2004 20:28:28 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0389443D46 for ; Sat, 27 Nov 2004 20:28:28 +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 D79782A8E0 for ; Sat, 27 Nov 2004 12:28:27 -0800 (PST) (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 68767E2B3 for ; Sat, 27 Nov 2004 12:28:27 -0800 (PST) (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 iARKSR2r033452; Sat, 27 Nov 2004 12:28:27 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iARKSQWW033451; Sat, 27 Nov 2004 12:28:26 -0800 (PST) (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: Sat, 27 Nov 2004 12:28:26 -0800 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411271228.26645.peter@wemm.org> Subject: Re: error message: "NOTE: BIOS IS NOT INSTALLED" 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, 27 Nov 2004 20:28:28 -0000 On Saturday 27 November 2004 05:57 am, Marta Resende wrote: > hello, i had freebsd working in my machine(amd athlon xp and asus > mobo), and today, i change the motherboard and cpu, and when i turn > on the computer, it says: [NOTE]: THE BIOS IS NOT INSTALLED. This is generally for things like the SATA bios. Many athlon64 motherboards have two SATA controllers... one is the on-chip VIA controller, the other is the Promise raid controller. If you have drives connected to just the Promise, then the VIA SATA BIOS will say "no drives attached" and "BIOS NOT INSTALLED". All this means is that the bios support for accessing the SATA drives wasn't activated because there is no point... no drives! -- 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 Sat Nov 27 21:37:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3EF716A4CE for ; Sat, 27 Nov 2004 21:37:37 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09C6743D2F for ; Sat, 27 Nov 2004 21:37:36 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.208] [213.112.167.208]) by mxfep01.bredband.com with ESMTP id <20041127213734.LEDC5665.mxfep01.bredband.com@[192.168.245.231]>; Sat, 27 Nov 2004 22:37:34 +0100 Message-ID: <41A8F374.70806@bredband.net> Date: Sat, 27 Nov 2004 22:36:52 +0100 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20041024 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marta Resende References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: error message: "NOTE: BIOS IS NOT INSTALLED" 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, 27 Nov 2004 21:37:37 -0000 Marta Resende wrote: > hello, i had freebsd working in my machine(amd athlon xp and asus mobo), > and today, i change the motherboard and cpu, and when i turn on the > computer, it says: [NOTE]: THE BIOS IS NOT INSTALLED. > > and i reboot and press delete in the boot, to configure the bios, and i > save&exit, and the same message appears. > > So... i did nothing after hardware installation of the mobo and cpu, > should i have done something to proceed with bios installation?? > > i post in these forum cause this error was with a MSI k8t board and > athlon 64. > > thank you! Hello, New Boards have several ATA, SATA and RAID disc-controllers, If any of them are enabled without having any discs attached, the controller complains and says that it did not activate its part of the BIOS. On my MSI K8T Neo2 FIR , this exact same message appears if I enable the Promise 20579 Raid controller to which there are no discs attached. Does FreeBSD start at all on your system after the Motherboard swap ? If you are running the Generic Kernel I guess it should, but if the kernel was heavily customised toward the previous MOBO, maybe you need to manually start the Generic kernel from the bootstrap..... //Lars