From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 16 10:45:56 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B437B16A4CE; Sun, 16 Jan 2005 10:45:56 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E1D643D41; Sun, 16 Jan 2005 10:45:55 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] (CPE-144-133-80-177.vic.bigpond.net.au [144.133.80.177]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0GAjfoC025439 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 16 Jan 2005 21:45:42 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: References: 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, 16 Jan 2005 21:45:17 +1100 To: "Vinod Kashyap" 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/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd stable cc: freebsd-amd64@FreeBSD.ORG Subject: Re: twa breakage on AMD64 with 9.1.5.2 3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 16 Jan 2005 10:45:56 -0000 Hello On 15/01/2005, at 12:40 PM, Vinod Kashyap wrote: > > Could you give the attached patch a try? Just a hunch... > I did... same behavior. it just hangs right after displaying the twa0 line. Actually, hangs is incorrect. As I had to drive to the office to reload a previous kernel (never, ever rely on nextboot my friends!) When I got there I saw that it went a little bit further, so it seems that it doesn't just hang... it is just very very slow 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 Mon Jan 17 00:28:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A14C516A4CE for ; Mon, 17 Jan 2005 00:28:12 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 199A143D1D for ; Mon, 17 Jan 2005 00:28:12 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id 8DC544AC3A for ; Mon, 17 Jan 2005 01:28:10 +0100 (CET) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 15442-03-2 for ; Mon, 17 Jan 2005 01:28:10 +0100 (CET) Received: from palle.girgensohn.se (1-2-8-5a.asp.sth.bostream.se [82.182.157.66]) by melon.pingpong.net (Postfix) with ESMTP id 5C1EE4AC35 for ; Mon, 17 Jan 2005 01:28:10 +0100 (CET) Date: Mon, 17 Jan 2005 01:28:10 +0100 From: Palle Girgensohn To: freebsd-amd64@freebsd.org Message-ID: X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Subject: jdk @ amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 00:28:12 -0000 Hello again! Some time ago I asked how to get jdk running on a Dell 2850 with 5.3-stable-amd64, built WITH_LIB32=YES. I've built the JDK on a plain old 32-bit machine, and installed the package on the Dell. When trying to start java, it complains as follows: bin$ ./java /libexec/ld-elf.so.1: /usr/lib32/libpthread.so.1: Undefined symbol "i386_set_ldt" How do I get it running? I have nothing in /etc/libmap.conf, perhaps I should? /Palle From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 00:38:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA1AA16A4CE; Mon, 17 Jan 2005 00:38:03 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 497F743D45; Mon, 17 Jan 2005 00:38:03 +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 j0H0c2od062332; Sun, 16 Jan 2005 16:38:02 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0H0c26g062331; Sun, 16 Jan 2005 16:38:02 -0800 (PST) (envelope-from obrien) Date: Sun, 16 Jan 2005 16:38:02 -0800 From: "David O'Brien" To: Palle Girgensohn Message-ID: <20050117003802.GA62302@dragon.nuxi.com> References: 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: jdk @ 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: Mon, 17 Jan 2005 00:38:03 -0000 On Mon, Jan 17, 2005 at 01:28:10AM +0100, Palle Girgensohn wrote: > Hello again! > > Some time ago I asked how to get jdk running on a Dell 2850 with > 5.3-stable-amd64, built WITH_LIB32=YES. I've built the JDK on a plain old > 32-bit machine, and installed the package on the Dell. When trying to start > java, it complains as follows: > > bin$ ./java > /libexec/ld-elf.so.1: /usr/lib32/libpthread.so.1: Undefined symbol > "i386_set_ldt" > > How do I get it running? I have nothing in /etc/libmap.conf, perhaps I > should? Just 1-2 weeks ago Peter Wemm addressed this issue. Please see the list archives. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 01:28:49 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7930D16A4CE for ; Mon, 17 Jan 2005 01:28:49 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2956A43D45 for ; Mon, 17 Jan 2005 01:28:49 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id A6D424AC3D for ; Mon, 17 Jan 2005 02:28:47 +0100 (CET) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 21753-01 for ; Mon, 17 Jan 2005 02:28:47 +0100 (CET) Received: from palle.girgensohn.se (1-2-8-5a.asp.sth.bostream.se [82.182.157.66]) by melon.pingpong.net (Postfix) with ESMTP id 663244AC35; Mon, 17 Jan 2005 02:28:47 +0100 (CET) Date: Mon, 17 Jan 2005 02:28:47 +0100 From: Palle Girgensohn To: freebsd-amd64@FreeBSD.org Message-ID: <96EBAAED7629B17F00C7E58F@palle.girgensohn.se> In-Reply-To: <20050117003802.GA62302@dragon.nuxi.com> References: <20050117003802.GA62302@dragon.nuxi.com> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net cc: freebsd-amd64@FreeBSD.org Subject: Re: jdk @ amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 01:28:50 -0000 --On s=F6ndag, januari 16, 2005 16.38.02 -0800 David O'Brien=20 wrote: > On Mon, Jan 17, 2005 at 01:28:10AM +0100, Palle Girgensohn wrote: >> Hello again! >> >> Some time ago I asked how to get jdk running on a Dell 2850 with >> 5.3-stable-amd64, built WITH_LIB32=3DYES. I've built the JDK on a plain >> old 32-bit machine, and installed the package on the Dell. When trying >> to start java, it complains as follows: >> >> bin$ ./java >> /libexec/ld-elf.so.1: /usr/lib32/libpthread.so.1: Undefined symbol >> "i386_set_ldt" >> >> How do I get it running? I have nothing in /etc/libmap.conf, perhaps I >> should? > > Just 1-2 weeks ago Peter Wemm addressed this issue. Please see the list > archives. Thanks, I did browse the list archives, but missed it. Seems I'm out of=20 luck, java cannot run @ amd64 according to that thread. :( Seems odd, I believe I've read success stories in the past. Am I wrong? /Palle From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 01:48:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9BF416A4CE for ; Mon, 17 Jan 2005 01:48:51 +0000 (GMT) Received: from mail.magnachip.com (mail.magnachip.com [211.40.120.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1637B43D31 for ; Mon, 17 Jan 2005 01:48:51 +0000 (GMT) (envelope-from sungbak.kim@magnachip.com) Received: from magnachip.com (localhost [127.0.0.1]) by mail.magnachip.com (8.12.11/8.12.11) with ESMTP id j0H1jd4a003442 for ; Mon, 17 Jan 2005 10:45:40 +0900 (KST) Message-ID: <41EB19D7.3C5D753C@magnachip.com> Date: Mon, 17 Jan 2005 10:50:15 +0900 From: Kim Sungbark X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,ko MIME-Version: 1.0 Cc: freebsd-amd64@freebsd.org References: <20050111132101.84B1.SHINO@fornext.org> <200501122149.49712.peter@wemm.org> <20050114171031.F520.SHINO@fornext.org> Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Subject: How can I find lost CPU1 in Sun V20Z ? 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, 17 Jan 2005 01:48:51 -0000 I compiled with SMP option with "make kernel KERNCONF=MYKERNEL" in /usr/src $(TOP) derective of source tree but the kernel comes panic with "CPU1 Launched !" message. Whenever I put in SMP option with MYKERNEL, the kernel comes panic. Is there any successful story with SMP option in V20Z ? I am suspicious that why even GENERIC KERNEL can't find CPU1? MyKernel configuration file SMP option for AMD64 # Workarounds for some known-to-be-broken chipsets (nVidia nForce3-Pro150) device atpic # 8259A compatability options NO_MIXED_MODE # Don't penalize working chipsets # Bus support. Do not remove isa, even if you have no isa slots options SMP device acpi options ACPI_DEBUG options ACPI_MAX_THREADS=1 device isa device pci Below messages are only one CPU option FreeBSD 5.3-STABLE #4: Thu Jan 13 02:39:51 KST 2005 sbkim@v20z.xxx.com:/usr/obj/usr/src/sys/V20Z MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 mpt0: port 0x2000-0x20ff mem 0xfe820000-0xfe82ffff,0xfe830000-0xfe83ffff irq 27 at device 4.0 on pci2 mpt0: [GIANT-LOCKED] da0 at mpt0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 70103MB (143571316 512 byte sectors: 255H 63S/T 8936C) From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 06:56:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 842EF16A4CE for ; Mon, 17 Jan 2005 06:56:50 +0000 (GMT) Received: from web26810.mail.ukl.yahoo.com (web26810.mail.ukl.yahoo.com [217.146.176.86]) by mx1.FreeBSD.org (Postfix) with SMTP id A104643D31 for ; Mon, 17 Jan 2005 06:56:49 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 71828 invoked by uid 60001); 17 Jan 2005 06:56:48 -0000 Message-ID: <20050117065648.71826.qmail@web26810.mail.ukl.yahoo.com> Received: from [194.248.174.58] by web26810.mail.ukl.yahoo.com via HTTP; Mon, 17 Jan 2005 07:56:48 CET Date: Mon, 17 Jan 2005 07:56:48 +0100 (CET) From: Claus Guttesen To: Kim Sungbark In-Reply-To: <41EB19D7.3C5D753C@magnachip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: How can I find lost CPU1 in Sun V20Z ? 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, 17 Jan 2005 06:56:50 -0000 > I am suspicious that why even GENERIC KERNEL can't > find CPU1? Default GENERIC was changed in 5.3 to UP-kernel. Claus From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 07:52:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5A8616A4CE for ; Mon, 17 Jan 2005 07:52:30 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 8A69C43D2D for ; Mon, 17 Jan 2005 07:52:29 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 32011 invoked by uid 513); 17 Jan 2005 07:52:28 -0000 Received: from 82.141.58.12 by dsl-mail (envelope-from , uid 89) with qmail-scanner-1.24 (clamdscan: 0.80/609. spamassassin: 2.60. Clear:RC:1(82.141.58.12):SA:0(-1.4/5.0):. Processed in 5.686595 secs); 17 Jan 2005 07:52:28 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 Received: from reverse-82-141-58-12.dialin.kamp-dsl.de (HELO lobo.homeunix.org) (82.141.58.12) by dsl-mail.kamp.net with SMTP; 17 Jan 2005 07:52:22 -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 j0H7qTrx048081 for ; Mon, 17 Jan 2005 08:52:29 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id j0H7qSXa048080 for freebsd-amd64@freebsd.org; Mon, 17 Jan 2005 08:52:28 +0100 (CET) (envelope-from ewinter) Date: Mon, 17 Jan 2005 08:52:28 +0100 From: "Ernst W. Winter" To: freebsd-amd64@freebsd.org Message-ID: <20050117075228.GA48063@lobo.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: printer? 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: Mon, 17 Jan 2005 07:52:30 -0000 has anyone experienced problems with the printer under amd64? all of a sudden I cant't print anymore. I puts the documents in the spooler but then nothing happen. This happens wehn I use "lpr document.ps" also "dvips latex_document.dvi". 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 Mon Jan 17 08:53:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6BC316A4DF for ; Mon, 17 Jan 2005 08:53:25 +0000 (GMT) Received: from web26806.mail.ukl.yahoo.com (web26806.mail.ukl.yahoo.com [217.146.176.82]) by mx1.FreeBSD.org (Postfix) with SMTP id 1319A43D1D for ; Mon, 17 Jan 2005 08:53:25 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 6458 invoked by uid 60001); 17 Jan 2005 08:53:24 -0000 Message-ID: <20050117085324.6456.qmail@web26806.mail.ukl.yahoo.com> Received: from [194.248.174.58] by web26806.mail.ukl.yahoo.com via HTTP; Mon, 17 Jan 2005 09:53:24 CET Date: Mon, 17 Jan 2005 09:53:24 +0100 (CET) From: Claus Guttesen To: "Ernst W. Winter" , freebsd-amd64@freebsd.org In-Reply-To: <20050117075228.GA48063@lobo.homeunix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: printer? 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, 17 Jan 2005 08:53:26 -0000 > has anyone experienced problems with the printer > under amd64? Are you using printcap or cups? Claus From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 09:02:36 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5B9416A4CE; Mon, 17 Jan 2005 09:02:36 +0000 (GMT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64F9243D45; Mon, 17 Jan 2005 09:02:36 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.36.69) by smtp01.syd.iprimus.net.au (7.0.036) id 41A76DD901610717; Mon, 17 Jan 2005 20:02:35 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 7F2844324; Mon, 17 Jan 2005 20:03:14 +1100 (EST) Date: Mon, 17 Jan 2005 20:03:14 +1100 From: Tim Robbins To: Palle Girgensohn Message-ID: <20050117090314.GA1519@cat.robbins.dropbear.id.au> References: <20050117003802.GA62302@dragon.nuxi.com> <96EBAAED7629B17F00C7E58F@palle.girgensohn.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <96EBAAED7629B17F00C7E58F@palle.girgensohn.se> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: jdk @ amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 09:02:36 -0000 On Mon, Jan 17, 2005 at 02:28:47AM +0100, Palle Girgensohn wrote: > > > --On s?ndag, januari 16, 2005 16.38.02 -0800 David O'Brien > wrote: > > >On Mon, Jan 17, 2005 at 01:28:10AM +0100, Palle Girgensohn wrote: > >>Hello again! > >> > >>Some time ago I asked how to get jdk running on a Dell 2850 with > >>5.3-stable-amd64, built WITH_LIB32=YES. I've built the JDK on a plain > >>old 32-bit machine, and installed the package on the Dell. When trying > >>to start java, it complains as follows: > >> > >>bin$ ./java > >>/libexec/ld-elf.so.1: /usr/lib32/libpthread.so.1: Undefined symbol > >>"i386_set_ldt" > >> > >>How do I get it running? I have nothing in /etc/libmap.conf, perhaps I > >>should? > > > >Just 1-2 weeks ago Peter Wemm addressed this issue. Please see the list > >archives. > > Thanks, I did browse the list archives, but missed it. Seems I'm out of > luck, java cannot run @ amd64 according to that thread. :( > > Seems odd, I believe I've read success stories in the past. Am I wrong? The official Sun 32-bit Linux binaries run on FreeBSD/amd64 (at least 5.3-RELEASE) with minimal effort and should be suitable for most tasks. The runtime suffers the same stability problems under Linux emulation on amd64 as it does on i386 when running certain intensive applications, but it may be worth a try. See http://people.freebsd.org/~tjr/linux32.html or search the list archives for instructions to set up Linux emulation. Tim From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 09:10:48 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A53E16A4CE for ; Mon, 17 Jan 2005 09:10:48 +0000 (GMT) Received: from ns3.bsn.com (ns3.bsn.com [194.221.32.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E8143D4C for ; Mon, 17 Jan 2005 09:10:47 +0000 (GMT) (envelope-from ewwinter@ns3.bsn.com) Received: from ns3.bsn.com (localhost [127.0.0.1]) by ns3.bsn.com (8.12.10/8.12.10) with ESMTP id j0H9AkI2045624; Mon, 17 Jan 2005 10:10:46 +0100 (CET) (envelope-from ewwinter@ns3.bsn.com) Received: (from ewwinter@localhost) by ns3.bsn.com (8.12.10/8.12.10/Submit) id j0H9Akmo045623; Mon, 17 Jan 2005 10:10:46 +0100 (CET) (envelope-from ewwinter) Date: Mon, 17 Jan 2005 10:10:46 +0100 From: "Ernst W. Winter" To: Claus Guttesen Message-ID: <20050117101046.A45581@ns3.bsn.com> References: <20050117075228.GA48063@lobo.homeunix.org> <20050117085324.6456.qmail@web26806.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20050117085324.6456.qmail@web26806.mail.ukl.yahoo.com>; from cguttesen@yahoo.dk on Mon, Jan 17, 2005 at 09:53:24AM +0100 X-Phone: + 49-89-3075-6800 Organization: BSn -- Basis Systeme netzwerk X-Operating-System: FreeBSD ns3.bsn.com 4.9-STABLE FreeBSD 4.9-STABLE cc: freebsd-amd64@freebsd.org Subject: Re: printer? 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: Mon, 17 Jan 2005 09:10:48 -0000 On Mon, 17 Jan 2005, Claus Guttesen wrote: > > has anyone experienced problems with the printer > > under amd64? > > Are you using printcap or cups? > using printcap with apsfilter. what is the difference with cups? Thanks, -- Ernst W. Winter Basis Systeme netzwerk phone: +49 89 692 8120 Brecherspitzstr. 8/Rgb. fax: +49 89 692 8150 D-81541 Muenchen, Germany http://www.bsn.com/ From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 09:29:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E576316A4F6 for ; Mon, 17 Jan 2005 09:29:06 +0000 (GMT) Received: from web26801.mail.ukl.yahoo.com (web26801.mail.ukl.yahoo.com [217.146.176.77]) by mx1.FreeBSD.org (Postfix) with SMTP id 28BBD43D2D for ; Mon, 17 Jan 2005 09:29:06 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 51543 invoked by uid 60001); 17 Jan 2005 09:29:05 -0000 Message-ID: <20050117092905.51541.qmail@web26801.mail.ukl.yahoo.com> Received: from [194.248.174.58] by web26801.mail.ukl.yahoo.com via HTTP; Mon, 17 Jan 2005 10:29:05 CET Date: Mon, 17 Jan 2005 10:29:05 +0100 (CET) From: Claus Guttesen To: "Ernst W. Winter" In-Reply-To: <20050117101046.A45581@ns3.bsn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org Subject: Re: printer? 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, 17 Jan 2005 09:29:07 -0000 > > Are you using printcap or cups? > using printcap with apsfilter. > > what is the difference with cups? Cups puts lp*-files in /usr/local/bin and you have to remove the lp*-files in /usb/bin before you can use cups. If NO_LPR= true is commented out in /etc/make.conf (not activated) the base-lp* will be put back during a make world and thus prevent cups from being used. Cups is easier for me since I haven't used printcap very much, webbased interface etc. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 09:40:21 2005 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BCC916A4CE for ; Mon, 17 Jan 2005 09:40:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1575C43D45 for ; Mon, 17 Jan 2005 09:40:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0H9eKaS075346 for ; Mon, 17 Jan 2005 09:40:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0H9eKl9075345; Mon, 17 Jan 2005 09:40:20 GMT (envelope-from gnats) Resent-Date: Mon, 17 Jan 2005 09:40:20 GMT Resent-Message-Id: <200501170940.j0H9eKl9075345@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Matthew Sullivan Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9ECF816A4CE for ; Mon, 17 Jan 2005 09:39:16 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7470E43D41 for ; Mon, 17 Jan 2005 09:39:16 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j0H9dG2F098174 for ; Mon, 17 Jan 2005 09:39:16 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j0H9dGwO098135; Mon, 17 Jan 2005 09:39:16 GMT (envelope-from nobody) Message-Id: <200501170939.j0H9dGwO098135@www.freebsd.org> Date: Mon, 17 Jan 2005 09:39:16 GMT From: Matthew Sullivan To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/76336: racoon/setkey -D cases instant "Fatal Trap 12: Page fault while in kernel mode" on 5.3-RELEASE-P4 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, 17 Jan 2005 09:40:21 -0000 >Number: 76336 >Category: amd64 >Synopsis: racoon/setkey -D cases instant "Fatal Trap 12: Page fault while in kernel mode" on 5.3-RELEASE-P4 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 17 09:40:20 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Matthew Sullivan >Release: 5.3-RELEASE-P4 >Organization: SORBS >Environment: FreeBSD desperado.sorbs.net 5.3-RELEASE-p4 FreeBSD 5.3-RELEASE-p4 #2: Wed Jan 12 15:07:54 EST 2005 root@desperado.sorbs.net:/usr/obj/usr/src/sys/DESPERADO amd64 >Description: Starting racoon or using 'setkey -D' will cause an immediate Page Fault as follows: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x39 fault code = supervisor write, page not present instruction pointer = 0x8:0xffffffff80307a70 stack pointer = 0x10:0xffffffff93cc0860 frame pointer = 0x10:0xffffffff93cc0960 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 480 (racoon) [thread 100068] Stopped at keydb_newsecasvar+0x100: decl %ecx db> where keydb_newsecasvar() at keydb_newsecasvar+0x100 raw_usend() at raw_usend+0x60 key_send() at key_send+0xa sosend() at sosend+0x626 kern_sendit() at kern_sendit+0x113 sendit() at sendit+0x5f sendto() at sendto+0x4d syscall() at syscall+0x50c Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (133, FreeBSD ELF64, sendto), rip = 0x800a63da8, rsp = 0x7fffffffec38, rbp = 0x2 --- db> call doadump Dumping 479 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 Dump complete 0xf (kgdb) file /usr/obj/usr/src/sys/DESPERADO/kernel.debug Reading symbols from /usr/obj/usr/src/sys/DESPERADO/kernel.debug...done. (kgdb) where #0 doadump () at pcpu.h:167 #1 0xffffffff80172736 in db_fncall (dummy1=0, dummy2=0, dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:531 #2 0xffffffff80172bc5 in db_command_loop () at /usr/src/sys/ddb/db_command.c:349 #3 0xffffffff80174a53 in db_trap (type=-1815345680, code=0) at /usr/src/sys/ddb/db_main.c:221 #4 0xffffffff8023070b in kdb_trap (type=12, code=0, tf=0xffffffff93cc07b0) at /usr/src/sys/kern/subr_kdb.c:418 #5 0xffffffff80371dae in trap_fatal (frame=0xffffffff93cc07b0, eva=18446742974681318688) at /usr/src/sys/amd64/amd64/trap.c:626 #6 0xffffffff80372143 in trap_pfault (frame=0xffffffff93cc07b0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:554 #7 0xffffffff803723a4 in trap (frame= {tf_rdi = -1099028463104, tf_rsi = 640, tf_rdx = -1815344784, tf_rcx = -1815344833, tf_r8 = 160, tf_r9 = -1099028232928 , tf_rax = -1815345008, tf_rbx = -2144306579, tf_rbp = -1815344800, tf_r10 = -2142160512, tf_r11 = -1815344624, tf_r12 = 57, tf_r13 = 0, tf_r14 = 0, tf_r15 = -1099140303240, tf_trapno = 12, tf_addr = 57, tf_flags = -1099132378656, tf_err = 2, tf_rip = -2144306576, tf_cs = 8, tf_rflags = 66054, tf_rsp = -1815345040, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:333 #8 0xffffffff80361bab in calltrap () at /usr/src/sys/amd64/amd64/exception.S:171 #9 0xffffff001ccc8200 in ?? () #10 0x0000000000000280 in ?? () #11 0xffffffff93cc0970 in ?? () #12 0xffffffff93cc093f in ?? () #13 0x00000000000000a0 in ?? () #14 0xffffff001cd00520 in ?? () #15 0xffffffff93cc0890 in ?? () #16 0xffffffff80307a6d in keydb_newsecasvar () at /usr/src/sys/netkey/keydb.c:187 #17 0xffffffff8029cfc0 in raw_usend (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0, td=0x0) at /usr/src/sys/net/raw_usrreq.c:263 #18 0xffffffff8030845a in key_send (so=0x0, flags=0, m=0x0, nam=0x0, control=0x0, td=0x0) at /usr/src/sys/netkey/keysock.c:442 #19 0xffffffff80253bc6 in sosend (so=0xffffff001621f678, addr=0x0, uio=0xffffffff93cc0a80, top=0xffffff001ccc8200, control=0x0, flags=0, td=0xffffff001cd00520) at /usr/src/sys/kern/uipc_socket.c:815 #20 0xffffffff8025ba73 in kern_sendit (td=0xffffff001cd00520, s=4, mp=0xffffffff93cc0b50, flags=0, control=0x0) at /usr/src/sys/kern/uipc_syscalls.c:738 #21 0xffffffff8025ca5f in sendit (td=0xffffff001cd00520, s=4, mp=0xffffffff93cc0b50, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:682 #22 0xffffffff8025cbed in sendto (td=0x0, uap=0x0) at /usr/src/sys/kern/uipc_syscalls.c:795 #23 0xffffffff80372b6c in syscall (frame= {tf_rdi = 4, tf_rsi = 5660864, tf_rdx = 16, tf_rcx = 0, tf_r8 = 0, tf_r9 = 0, tf_rax = 133, tf_rbx = 5660880, tf_rbp = 2, tf_r10 = -2141993928, tf_r11 = 514, tf_r12 = 5660864, tf_r13 = 16, tf_r14 = 7, tf_r15 = 4, tf_trapno = 12, tf_addr = 42840 00, tf_flags = 0, tf_err = 2, tf_rip = 34370633128, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488350264, tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:763 #24 0xffffffff80361ce8 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:248 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 11:02:13 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEAA516A4D0 for ; Mon, 17 Jan 2005 11:02:13 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 771AD43D3F for ; Mon, 17 Jan 2005 11:02:13 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0HB2DFI071160 for ; Mon, 17 Jan 2005 11:02:13 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0HB2CaM071154 for freebsd-amd64@freebsd.org; Mon, 17 Jan 2005 11:02:12 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 17 Jan 2005 11:02:12 GMT Message-Id: <200501171102.j0HB2CaM071154@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, 17 Jan 2005 11:02:13 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra 15 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 17:26:27 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8043716A4CE for ; Mon, 17 Jan 2005 17:26:27 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 101C343D5E for ; Mon, 17 Jan 2005 17:26:26 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.163] [213.112.167.163]) by mxfep02.bredband.com with ESMTP <20050117172624.GPBR12890.mxfep02.bredband.com@[192.168.245.231]>; Mon, 17 Jan 2005 18:26:24 +0100 Message-ID: <41EBF4C0.5030906@bredband.net> Date: Mon, 17 Jan 2005 18:24:16 +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: Kim Sungbark References: <20050111132101.84B1.SHINO@fornext.org> <200501122149.49712.peter@wemm.org> <20050114171031.F520.SHINO@fornext.org> <41EB19D7.3C5D753C@magnachip.com> In-Reply-To: <41EB19D7.3C5D753C@magnachip.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: How can I find lost CPU1 in Sun V20Z ? 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, 17 Jan 2005 17:26:27 -0000 Kim Sungbark wrote: > I compiled with SMP option with "make kernel KERNCONF=MYKERNEL" in > /usr/src $(TOP) derective of source tree but the kernel comes panic with > "CPU1 Launched !" message. Whenever I put in SMP option with MYKERNEL, > the kernel comes panic. Is there any successful story with SMP option in > V20Z ? > I am suspicious that why even GENERIC KERNEL can't find CPU1? > > MyKernel configuration file SMP option for AMD64 > > # Workarounds for some known-to-be-broken chipsets (nVidia > nForce3-Pro150) > device atpic # 8259A compatability > options NO_MIXED_MODE # Don't penalize working chipsets The SUN V20z Uses the AMD8000 series chipset. To be exact, it uses the AMD8131 HyperTransport to PCI bridge and the AMD8111 to communicate with keyboard, USB, CD/DVD and Mouse. This is the same general chipset as the Tyan boards. Maybe the above options for nforce3 are wrong in this context. //Lars From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 18:13:06 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E22916A4CE for ; Mon, 17 Jan 2005 18:13:06 +0000 (GMT) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C45443D4C for ; Mon, 17 Jan 2005 18:13:06 +0000 (GMT) (envelope-from will@exomi.com) Received: from ZMXLVII.dsl.saunalahti.fi (ZMXLVII.dsl.saunalahti.fi [85.76.70.148]) by will.iki.fi (Postfix) with ESMTP id 921E8152; Mon, 17 Jan 2005 20:13:04 +0200 (EET) From: Ville-Pertti Keinonen To: william paul In-Reply-To: <200501171758.JAA01960@huisne.wrs.com> References: <200501171758.JAA01960@huisne.wrs.com> Content-Type: text/plain Date: Mon, 17 Jan 2005 20:12:35 +0200 Message-Id: <1105985555.68143.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: RFC: if_ndis on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 18:13:06 -0000 On Mon, 2005-01-17 at 09:58 -0800, william paul wrote: > Oh... something just occured to me. Did you have to modify ndiscvt(8) > or subr_pe.c to deal with any differences between i386 PE binaries > and AMD64 PE binaries? I noticed that there were some changes needed > to handle the 64 bit relocations. Was that all really that had to be fixed? Getting ndiscvt to work required a couple of minor modifications in the pe_var.h header, as image_optional_header looks slightly different for 64-bit. The only other change related to the binary format was adding the 64-bit relocation type in subr_pe.c. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 20:38:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57EED16A4CE for ; Mon, 17 Jan 2005 20:38:19 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A38243D55 for ; Mon, 17 Jan 2005 20:38:19 +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 j0HKcIU1029247 for ; Mon, 17 Jan 2005 12:38:18 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0HKcI0K029246 for freebsd-amd64@freebsd.org; Mon, 17 Jan 2005 12:38:18 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2005 12:38:18 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20050117203818.GA29131@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 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 Subject: [RFC] what to name linux 32-bit compat 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, 17 Jan 2005 20:38:19 -0000 [ Respect the Reply-to:! ] /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough for what is expected of FreeBSD. Anyway... We need to decide how to have both Linux i686 and Linux amd64 compat support live side-by-side. At the moment my leanings are for /compat/linux32 and /compat/linux. We could also go with /compat/linux and /compat/linux64 <- taking a page from the Linux LSB naming convention (ie, they have lib and lib64). Linux 32-bit support is most interesting -- that is how we get Acrobat reader and some other binary-only ports. The only Linux 64-bit things we might want to run that truly matter 32-bit vs. 64-bit is Oracle and IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just Because Its There(tm)" thing. So making Linux 32-bit support the cleanest looking from a /usr/ports POV has some merit. What do others think? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 20:48:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDAA416A4CE for ; Mon, 17 Jan 2005 20:48:01 +0000 (GMT) Received: from peedub.jennejohn.org (J9ca2.j.pppool.de [85.74.156.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 229F543D1F for ; Mon, 17 Jan 2005 20:48:01 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id j0HKlxS7022766 for ; Mon, 17 Jan 2005 21:47:59 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200501172047.j0HKlxS7022766@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-amd64@freebsd.org In-Reply-To: Message from "David O'Brien" <20050117203818.GA29131@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2005 21:47:59 +0100 From: Gary Jennejohn Subject: Re: [RFC] what to name linux 32-bit compat 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, 17 Jan 2005 20:48:02 -0000 "David O'Brien" writes: > [ Respect the Reply-to:! ] > > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > for what is expected of FreeBSD. Anyway... > > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). > > Linux 32-bit support is most interesting -- that is how we get Acrobat > reader and some other binary-only ports. The only Linux 64-bit things we > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > Because Its There(tm)" thing. So making Linux 32-bit support the > cleanest looking from a /usr/ports POV has some merit. > > What do others think? > I agree with this 100%. Besides, at the moment the really interesting Linux applications for normal users, like realplayer, are only available in 32-bit mode, AFAIK. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 20:48:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9357C16A4CF for ; Mon, 17 Jan 2005 20:48:59 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD38C43D41 for ; Mon, 17 Jan 2005 20:48:58 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so781820wri for ; Mon, 17 Jan 2005 12:48:56 -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=SWWHvfnmjQAd4rB6HQnE94E9sVDeAQ70BkRVcCwWzEW60zN9eGGzsqkWKyiPzePUv+mArXzT4IvgUBrJ/3GZ3UIMaEHSgugciepUreiXd3qws3QP/ZoQo9ouvIxpb7QZVyuF8KhI4JKWZTyt7M/SBmSs/d3ZZ7WhWCI7bYEeXEY= Received: by 10.54.52.40 with SMTP id z40mr102946wrz; Mon, 17 Jan 2005 12:48:56 -0800 (PST) Received: by 10.54.40.73 with HTTP; Mon, 17 Jan 2005 12:48:56 -0800 (PST) Message-ID: <2fd864e0501171248791ddd18@mail.gmail.com> Date: Mon, 17 Jan 2005 14:48:56 -0600 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050117203818.GA29131@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050117203818.GA29131@dragon.nuxi.com> Subject: Re: [RFC] what to name linux 32-bit compat 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: Mon, 17 Jan 2005 20:48:59 -0000 On Mon, 17 Jan 2005 12:38:18 -0800, David O'Brien wrote: > [ Respect the Reply-to:! ] > > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > for what is expected of FreeBSD. Anyway... > > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). > > Linux 32-bit support is most interesting -- that is how we get Acrobat > reader and some other binary-only ports. The only Linux 64-bit things we > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > Because Its There(tm)" thing. So making Linux 32-bit support the > cleanest looking from a /usr/ports POV has some merit. > > What do others think? > > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ > 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" > What about having linux32, linux64, and linux (Which builds whatever the arch on the local machine is)? Seems like the easiest for all involved, as well as people with clean, 64-bit safe code, who want to avoid the problem entirely can just use linux as a dep too, instead of having to have some ugly kludgery to figure out which one they're on, and which one they should depend on, based on arch. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 20:53:01 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F94516A4CE for ; Mon, 17 Jan 2005 20:53:01 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA1BE43D2D for ; Mon, 17 Jan 2005 20:53:00 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so782326wri for ; Mon, 17 Jan 2005 12:53:00 -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=lbHCzOZ3wRbnioHYHaYoY5yLWBVn1HuP420yzB91LJzOKB4Ms+2PJTCD5dQfC6VM5vqgffVvEPLog8d8tw97QtL7xwraPr1W5ikOoBAvJKpk/qUK5BO3SI09sw+g6If2CPYAtlLgMOvaYrbRwPJGtCCqUJ8S5jx5zhcXHxWf20Y= Received: by 10.54.50.13 with SMTP id x13mr414773wrx; Mon, 17 Jan 2005 12:53:00 -0800 (PST) Received: by 10.54.40.73 with HTTP; Mon, 17 Jan 2005 12:52:58 -0800 (PST) Message-ID: <2fd864e05011712523018285c@mail.gmail.com> Date: Mon, 17 Jan 2005 14:52:59 -0600 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <2fd864e05011712527cad68f6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050111132101.84B1.SHINO@fornext.org> <200501122149.49712.peter@wemm.org> <20050114171031.F520.SHINO@fornext.org> <41EB19D7.3C5D753C@magnachip.com> <41EBF4C0.5030906@bredband.net> <2fd864e05011712527cad68f6@mail.gmail.com> Subject: Fwd: How can I find lost CPU1 in Sun V20Z ? 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: Mon, 17 Jan 2005 20:53:01 -0000 On Mon, 17 Jan 2005 18:24:16 +0100, Lars Tunkrans wrote: > Kim Sungbark wrote: > > I compiled with SMP option with "make kernel KERNCONF=MYKERNEL" in > > /usr/src $(TOP) derective of source tree but the kernel comes panic with > > "CPU1 Launched !" message. Whenever I put in SMP option with MYKERNEL, > > the kernel comes panic. Is there any successful story with SMP option in > > V20Z ? > > I am suspicious that why even GENERIC KERNEL can't find CPU1? > > > > MyKernel configuration file SMP option for AMD64 > > > > # Workarounds for some known-to-be-broken chipsets (nVidia > > nForce3-Pro150) > > device atpic # 8259A compatability > > options NO_MIXED_MODE # Don't penalize working chipsets > > The SUN V20z Uses the AMD8000 series chipset. To be exact, > it uses the AMD8131 HyperTransport to PCI bridge and the > AMD8111 to communicate with keyboard, USB, CD/DVD and Mouse. > > This is the same general chipset as the Tyan boards. > Maybe the above options for nforce3 are wrong in this context. > > //Lars > _______________________________________________ > 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" > Sorry Lars, Reply-To: always makes me sad. :( I've never seen a Tyan motherboard based machine have that issue, but its worth a shot. Anyone used FreeBSD with the V20z, anyway? Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 21:21:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7239216A4CE for ; Mon, 17 Jan 2005 21:21:08 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE30C43D46 for ; Mon, 17 Jan 2005 21:21:06 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.163] [213.112.167.163]) by mxfep01.bredband.com with ESMTP <20050117212105.EJPN12264.mxfep01.bredband.com@[192.168.245.231]>; Mon, 17 Jan 2005 22:21:05 +0100 Message-ID: <41EC2BC1.6080900@bredband.net> Date: Mon, 17 Jan 2005 22:18:57 +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: Astrodog References: <20050111132101.84B1.SHINO@fornext.org> <200501122149.49712.peter@wemm.org> <20050114171031.F520.SHINO@fornext.org> <41EB19D7.3C5D753C@magnachip.com> <41EBF4C0.5030906@bredband.net> <2fd864e05011712527cad68f6@mail.gmail.com> <2fd864e05011712523018285c@mail.gmail.com> In-Reply-To: <2fd864e05011712523018285c@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Fwd: How can I find lost CPU1 in Sun V20Z ? 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, 17 Jan 2005 21:21:08 -0000 Astrodog wrote: > Sorry Lars, Reply-To: always makes me sad. :( > No worries :-) > I've never seen a Tyan motherboard based machine have that issue, but > its worth a shot. Anyone used FreeBSD with the V20z, anyway? > > Harrison Grundy Here is one 9 months old article that shows that 5.2.1 ( probably i386 ) did run. http://lists.freebsd.org/mailman/htdig/freebsd-amd64/2004-April/001138.html //Lars From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 21:28:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FA7616A4CE for ; Mon, 17 Jan 2005 21:28:07 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53EA943D1F for ; Mon, 17 Jan 2005 21:28:06 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.163] [213.112.167.163]) by mxfep01.bredband.com with ESMTP id <20050117212805.ELBN12264.mxfep01.bredband.com@[192.168.245.231]> for ; Mon, 17 Jan 2005 22:28:05 +0100 Message-ID: <41EC2D65.3080807@bredband.net> Date: Mon, 17 Jan 2005 22:25:57 +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: freebsd-amd64@freebsd.org References: <20050111132101.84B1.SHINO@fornext.org> <200501122149.49712.peter@wemm.org> <20050114171031.F520.SHINO@fornext.org> <41EB19D7.3C5D753C@magnachip.com> <41EBF4C0.5030906@bredband.net> <2fd864e05011712527cad68f6@mail.gmail.com> <2fd864e05011712523018285c@mail.gmail.com> <41EC2BC1.6080900@bredband.net> In-Reply-To: <41EC2BC1.6080900@bredband.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Fwd: How can I find lost CPU1 in Sun V20Z ? 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, 17 Jan 2005 21:28:07 -0000 and here is a verbose bootlog from Robs site. http://rob.com/sun/opteron/freebsd.txt //Lars From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 23:00:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03E7216A4CE for ; Mon, 17 Jan 2005 23:00:19 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A783943D5A for ; Mon, 17 Jan 2005 23:00: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 j0HN4F0R012657 for ; Mon, 17 Jan 2005 15:04:15 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0HN4FvV012656 for freebsd-amd64@freebsd.org; Mon, 17 Jan 2005 15:04:15 -0800 Date: Mon, 17 Jan 2005 15:04:15 -0800 From: Brooks Davis To: freebsd-amd64@freebsd.org Message-ID: <20050117230415.GB28810@odin.ac.hmc.edu> References: <20050117203818.GA29131@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f2QGlHpHGjS2mn6Y" Content-Disposition: inline In-Reply-To: <20050117203818.GA29131@dragon.nuxi.com> 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 Subject: Re: [RFC] what to name linux 32-bit compat 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, 17 Jan 2005 23:00:19 -0000 --f2QGlHpHGjS2mn6Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 12:38:18PM -0800, David O'Brien wrote: > [ Respect the Reply-to:! ] >=20 > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > for what is expected of FreeBSD. Anyway... >=20 > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). >=20 > Linux 32-bit support is most interesting -- that is how we get Acrobat > reader and some other binary-only ports. The only Linux 64-bit things we > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > Because Its There(tm)" thing. So making Linux 32-bit support the > cleanest looking from a /usr/ports POV has some merit. >=20 > What do others think? The argument of making 32-bit linux compat easier seems somewhat compelling, but I'm also not sure that taking this path isn't a sure way to will make eventual 64-bit linux support even more painful. I disagree that databases are the only real applications of 64-bit. There are plenty of Mathematica and Matlab users who would like to solve very large problems that won't fit in 2GB. Even without the address space, the extra registers are supposed to make many calculations much faster so may compute bound applications are likely to benefit. -- 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 --f2QGlHpHGjS2mn6Y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB7ERuXY6L6fI4GtQRAq1rAKC/nd7wTq4hr22WupV1zLUQVVDDvwCgj6ju 09vmwty4YnvSipo2F4fWVnI= =jsz0 -----END PGP SIGNATURE----- --f2QGlHpHGjS2mn6Y-- From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 02:48:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DB4316A622 for ; Tue, 18 Jan 2005 02:48:06 +0000 (GMT) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55D3343D1D for ; Tue, 18 Jan 2005 02:48:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 27587 invoked from network); 18 Jan 2005 02:48:06 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) AES256-SHA encrypted SMTP for ; 18 Jan 2005 02:48:05 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0I2lqaK092340; Mon, 17 Jan 2005 21:48:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org, "Ernst W. Winter" Date: Mon, 17 Jan 2005 21:42:21 -0500 User-Agent: KMail/1.6.2 References: <20050117075228.GA48063@lobo.homeunix.org> In-Reply-To: <20050117075228.GA48063@lobo.homeunix.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501172142.21445.jhb@FreeBSD.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: printer? 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, 18 Jan 2005 02:48:08 -0000 On Monday 17 January 2005 02:52 am, Ernst W. Winter wrote: > has anyone experienced problems with the printer under amd64? > > all of a sudden I cant't print anymore. I puts the documents in the > spooler but then nothing happen. This happens wehn I use "lpr > document.ps" also "dvips latex_document.dvi". Is lpd running and does it think the printer is up? -- 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 Jan 18 02:48:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEE4916A54D for ; Tue, 18 Jan 2005 02:48:07 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7677043D1D for ; Tue, 18 Jan 2005 02:48:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 18878 invoked from network); 18 Jan 2005 02:48:07 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) AES256-SHA encrypted SMTP for ; 18 Jan 2005 02:48:06 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0I2lqaL092340; Mon, 17 Jan 2005 21:48:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 17 Jan 2005 21:46:17 -0500 User-Agent: KMail/1.6.2 References: <20050117203818.GA29131@dragon.nuxi.com> In-Reply-To: <20050117203818.GA29131@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501172146.17965.jhb@FreeBSD.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: David O'Brien Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 02:48:08 -0000 On Monday 17 January 2005 03:38 pm, David O'Brien wrote: > [ Respect the Reply-to:! ] > > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > for what is expected of FreeBSD. Anyway... > > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). > > Linux 32-bit support is most interesting -- that is how we get Acrobat > reader and some other binary-only ports. The only Linux 64-bit things we > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > Because Its There(tm)" thing. So making Linux 32-bit support the > cleanest looking from a /usr/ports POV has some merit. > > What do others think? Personally, I think /compat/linux32 and /compat/linux (for linux64) would be the best way to go. The idea being that /compat/linux runs native binaries on any given arch, and if there's more than one arch supported, the non-native ones get the funky names. I don't think it will really matter all to the end user much as acroread goes in /usr/local/bin and is in the path and that's all the user has to worry about. The ports stuff to put linux32 in /compat/linux32 on amd64 is going to be stuff the user doesn't have to worry or care about, so I don't think there's any user-visible benefit to linux and linux64 versus linux32 and linux. -- 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 Jan 18 03:05:40 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA81516A4CE; Tue, 18 Jan 2005 03:05:40 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62E0F43D54; Tue, 18 Jan 2005 03:05:40 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0I39oYq022622; Mon, 17 Jan 2005 20:09:51 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41EC7D01.2070107@freebsd.org> Date: Mon, 17 Jan 2005 20:05:37 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> In-Reply-To: <200501172146.17965.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 03:05:41 -0000 John Baldwin wrote: > On Monday 17 January 2005 03:38 pm, David O'Brien wrote: > >>[ Respect the Reply-to:! ] >> >>/usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough >>for what is expected of FreeBSD. Anyway... >> >>We need to decide how to have both Linux i686 and Linux amd64 compat >>support live side-by-side. At the moment my leanings are for >>/compat/linux32 and /compat/linux. We could also go with /compat/linux >>and /compat/linux64 <- taking a page from the Linux LSB naming convention >>(ie, they have lib and lib64). >> >>Linux 32-bit support is most interesting -- that is how we get Acrobat >>reader and some other binary-only ports. The only Linux 64-bit things we >>might want to run that truly matter 32-bit vs. 64-bit is Oracle and >>IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just >>Because Its There(tm)" thing. So making Linux 32-bit support the >>cleanest looking from a /usr/ports POV has some merit. >> >>What do others think? > > > Personally, I think /compat/linux32 and /compat/linux (for linux64) would be > the best way to go. The idea being that /compat/linux runs native binaries > on any given arch, and if there's more than one arch supported, the > non-native ones get the funky names. I don't think it will really matter all > to the end user much as acroread goes in /usr/local/bin and is in the path > and that's all the user has to worry about. The ports stuff to put linux32 > in /compat/linux32 on amd64 is going to be stuff the user doesn't have to > worry or care about, so I don't think there's any user-visible benefit to > linux and linux64 versus linux32 and linux. > Having different naming schemes for identical bits is risks confusion and inconsistency for both ports mainainers and ports users. I agree that your scheme is attractive, but I think that consistency is more important. Also, I'd say that we should probably think about leaning in the direction of the LSB for linux compat. So my vote is that on all platforms, /compat/linux is for 32-bit and /compat/linux64 is for 64-bit. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 03:20:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B54A916A4CE; Tue, 18 Jan 2005 03:20:37 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 438EB43D55; Tue, 18 Jan 2005 03:20:37 +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 j0I3Oasa006613; Mon, 17 Jan 2005 19:24:36 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0I3Oa3Y006612; Mon, 17 Jan 2005 19:24:36 -0800 Date: Mon, 17 Jan 2005 19:24:36 -0800 From: Brooks Davis To: Scott Long Message-ID: <20050118032436.GA5325@odin.ac.hmc.edu> References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> <41EC7D01.2070107@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <41EC7D01.2070107@freebsd.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: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 03:20:37 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 08:05:37PM -0700, Scott Long wrote: > John Baldwin wrote: >=20 > >On Monday 17 January 2005 03:38 pm, David O'Brien wrote: > > > >>[ Respect the Reply-to:! ] > >> > >>/usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > >>for what is expected of FreeBSD. Anyway... > >> > >>We need to decide how to have both Linux i686 and Linux amd64 compat > >>support live side-by-side. At the moment my leanings are for > >>/compat/linux32 and /compat/linux. We could also go with /compat/linux > >>and /compat/linux64 <- taking a page from the Linux LSB naming conventi= on > >>(ie, they have lib and lib64). > >> > >>Linux 32-bit support is most interesting -- that is how we get Acrobat > >>reader and some other binary-only ports. The only Linux 64-bit things = we > >>might want to run that truly matter 32-bit vs. 64-bit is Oracle and > >>IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > >>Because Its There(tm)" thing. So making Linux 32-bit support the > >>cleanest looking from a /usr/ports POV has some merit. > >> > >>What do others think? > > > > > >Personally, I think /compat/linux32 and /compat/linux (for linux64) woul= d=20 > >be the best way to go. The idea being that /compat/linux runs native=20 > >binaries on any given arch, and if there's more than one arch supported,= =20 > >the non-native ones get the funky names. I don't think it will really= =20 > >matter all to the end user much as acroread goes in /usr/local/bin and i= s=20 > >in the path and that's all the user has to worry about. The ports stuff= =20 > >to put linux32 in /compat/linux32 on amd64 is going to be stuff the user= =20 > >doesn't have to worry or care about, so I don't think there's any=20 > >user-visible benefit to linux and linux64 versus linux32 and linux. > > >=20 > Having different naming schemes for identical bits is risks confusion > and inconsistency for both ports mainainers and ports users. I agree > that your scheme is attractive, but I think that consistency is more > important. Also, I'd say that we should probably think about leaning in > the direction of the LSB for linux compat. So my vote is that on all > platforms, /compat/linux is for 32-bit and /compat/linux64 is for > 64-bit. I think this is a stretch. By this argument we should really be using /compat/linux-i386 and /compat/linux-amd64 (or would that be x86-64 since that's that linux calls it). I suspect that if Intel doesn't kill ia64 entirely, we will be looking at machines where linux64 is potentially ambiguous in the not too distant a future. -- 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 --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB7IFzXY6L6fI4GtQRArslAJ48XXXk4EudBBUC7RgzH7Mt8QoeHACgt0EM ilR2PSUvv9e91j0XkjUiy20= =+2+n -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 03:22:57 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1912816A4CE; Tue, 18 Jan 2005 03:22:57 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5933B43D5D; Tue, 18 Jan 2005 03:22:56 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0I3R72t022692; Mon, 17 Jan 2005 20:27:07 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41EC810E.9020205@freebsd.org> Date: Mon, 17 Jan 2005 20:22:54 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> <41EC7D01.2070107@freebsd.org> <20050118032436.GA5325@odin.ac.hmc.edu> In-Reply-To: <20050118032436.GA5325@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 03:22:57 -0000 Brooks Davis wrote: > On Mon, Jan 17, 2005 at 08:05:37PM -0700, Scott Long wrote: > >>John Baldwin wrote: >> >> >>>On Monday 17 January 2005 03:38 pm, David O'Brien wrote: >>> >>> >>>>[ Respect the Reply-to:! ] >>>> >>>>/usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough >>>>for what is expected of FreeBSD. Anyway... >>>> >>>>We need to decide how to have both Linux i686 and Linux amd64 compat >>>>support live side-by-side. At the moment my leanings are for >>>>/compat/linux32 and /compat/linux. We could also go with /compat/linux >>>>and /compat/linux64 <- taking a page from the Linux LSB naming convention >>>>(ie, they have lib and lib64). >>>> >>>>Linux 32-bit support is most interesting -- that is how we get Acrobat >>>>reader and some other binary-only ports. The only Linux 64-bit things we >>>>might want to run that truly matter 32-bit vs. 64-bit is Oracle and >>>>IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just >>>>Because Its There(tm)" thing. So making Linux 32-bit support the >>>>cleanest looking from a /usr/ports POV has some merit. >>>> >>>>What do others think? >>> >>> >>>Personally, I think /compat/linux32 and /compat/linux (for linux64) would >>>be the best way to go. The idea being that /compat/linux runs native >>>binaries on any given arch, and if there's more than one arch supported, >>>the non-native ones get the funky names. I don't think it will really >>>matter all to the end user much as acroread goes in /usr/local/bin and is >>>in the path and that's all the user has to worry about. The ports stuff >>>to put linux32 in /compat/linux32 on amd64 is going to be stuff the user >>>doesn't have to worry or care about, so I don't think there's any >>>user-visible benefit to linux and linux64 versus linux32 and linux. >>> >> >>Having different naming schemes for identical bits is risks confusion >>and inconsistency for both ports mainainers and ports users. I agree >>that your scheme is attractive, but I think that consistency is more >>important. Also, I'd say that we should probably think about leaning in >>the direction of the LSB for linux compat. So my vote is that on all >>platforms, /compat/linux is for 32-bit and /compat/linux64 is for >>64-bit. > > > I think this is a stretch. By this argument we should really be using > /compat/linux-i386 and /compat/linux-amd64 (or would that be x86-64 > since that's that linux calls it). I suspect that if Intel doesn't kill > ia64 entirely, we will be looking at machines where linux64 is > potentially ambiguous in the not too distant a future. > > -- Brooks > Linux/ia64 is sufficiently irrelevant at this point. It might survive in niche areas, but it should be the exception and not part of the rule. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 03:38:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A84B916A501 for ; Tue, 18 Jan 2005 03:38:47 +0000 (GMT) Received: from mail14.speakeasy.net (mail22.sea5.speakeasy.net [69.17.117.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C72443D48 for ; Tue, 18 Jan 2005 03:38:47 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20364 invoked from network); 18 Jan 2005 03:38:47 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 03:38:46 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0I3cgqE092717; Mon, 17 Jan 2005 22:38:44 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Brooks Davis Date: Mon, 17 Jan 2005 22:35:34 -0500 User-Agent: KMail/1.6.2 References: <20050117203818.GA29131@dragon.nuxi.com> <41EC7D01.2070107@freebsd.org> <20050118032436.GA5325@odin.ac.hmc.edu> In-Reply-To: <20050118032436.GA5325@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501172235.34509.jhb@FreeBSD.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Scott Long cc: freebsd-amd64@FreeBSD.org Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 03:38:50 -0000 On Monday 17 January 2005 10:24 pm, Brooks Davis wrote: > On Mon, Jan 17, 2005 at 08:05:37PM -0700, Scott Long wrote: > > John Baldwin wrote: > > >On Monday 17 January 2005 03:38 pm, David O'Brien wrote: > > >>[ Respect the Reply-to:! ] > > >> > > >>/usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > > >>for what is expected of FreeBSD. Anyway... > > >> > > >>We need to decide how to have both Linux i686 and Linux amd64 compat > > >>support live side-by-side. At the moment my leanings are for > > >>/compat/linux32 and /compat/linux. We could also go with /compat/linux > > >>and /compat/linux64 <- taking a page from the Linux LSB naming > > >> convention (ie, they have lib and lib64). > > >> > > >>Linux 32-bit support is most interesting -- that is how we get Acrobat > > >>reader and some other binary-only ports. The only Linux 64-bit things > > >> we might want to run that truly matter 32-bit vs. 64-bit is Oracle and > > >> IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > > >> Because Its There(tm)" thing. So making Linux 32-bit support the > > >> cleanest looking from a /usr/ports POV has some merit. > > >> > > >>What do others think? > > > > > >Personally, I think /compat/linux32 and /compat/linux (for linux64) > > > would be the best way to go. The idea being that /compat/linux runs > > > native binaries on any given arch, and if there's more than one arch > > > supported, the non-native ones get the funky names. I don't think it > > > will really matter all to the end user much as acroread goes in > > > /usr/local/bin and is in the path and that's all the user has to worry > > > about. The ports stuff to put linux32 in /compat/linux32 on amd64 is > > > going to be stuff the user doesn't have to worry or care about, so I > > > don't think there's any user-visible benefit to linux and linux64 > > > versus linux32 and linux. > > > > Having different naming schemes for identical bits is risks confusion > > and inconsistency for both ports mainainers and ports users. I agree > > that your scheme is attractive, but I think that consistency is more > > important. Also, I'd say that we should probably think about leaning in > > the direction of the LSB for linux compat. So my vote is that on all > > platforms, /compat/linux is for 32-bit and /compat/linux64 is for > > 64-bit. > > I think this is a stretch. By this argument we should really be using > /compat/linux-i386 and /compat/linux-amd64 (or would that be x86-64 > since that's that linux calls it). I suspect that if Intel doesn't kill > ia64 entirely, we will be looking at machines where linux64 is > potentially ambiguous in the not too distant a future. Actually, I think going the non-ambiguous route and using the fuller names like that (now that I see it) is probably the best bet when there is more than one possibility. -- 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 Jan 18 03:44:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38D7C16A4CE for ; Tue, 18 Jan 2005 03:44:25 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF37843D4C for ; Tue, 18 Jan 2005 03:44:24 +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 j0I3iOBK037337; Mon, 17 Jan 2005 19:44:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0I3iNmR037336; Mon, 17 Jan 2005 19:44:23 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2005 19:44:23 -0800 From: "David O'Brien" To: Gary Jennejohn Message-ID: <20050118034423.GA37298@dragon.nuxi.com> References: <20050117203818.GA29131@dragon.nuxi.com> <200501172047.j0HKlxS7022766@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501172047.j0HKlxS7022766@peedub.jennejohn.org> 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: [RFC] what to name linux 32-bit compat 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: Tue, 18 Jan 2005 03:44:25 -0000 On Mon, Jan 17, 2005 at 09:47:59PM +0100, Gary Jennejohn wrote: > "David O'Brien" writes: > > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > > for what is expected of FreeBSD. Anyway... > > > > We need to decide how to have both Linux i686 and Linux amd64 compat > > support live side-by-side. At the moment my leanings are for > > /compat/linux32 and /compat/linux. We could also go with /compat/linux > > and /compat/linux64 <- taking a page from the Linux LSB naming convention > > (ie, they have lib and lib64). > > > > Linux 32-bit support is most interesting -- that is how we get Acrobat > > reader and some other binary-only ports. The only Linux 64-bit things we > > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > > Because Its There(tm)" thing. So making Linux 32-bit support the > > cleanest looking from a /usr/ports POV has some merit. > > > > What do others think? > > I agree with this 100%. Besides, at the moment the really interesting > Linux applications for normal users, like realplayer, are only available > in 32-bit mode, AFAIK. You didn't actually answer the question. :-) Or rather I can't tell which way above you're agreeing with. :-( -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 03:53:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37BAE16A4CE; Tue, 18 Jan 2005 03:53:00 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1034443D39; Tue, 18 Jan 2005 03:53:00 +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 j0I3qxpQ037501; Mon, 17 Jan 2005 19:52:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0I3qxcA037500; Mon, 17 Jan 2005 19:52:59 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2005 19:52:59 -0800 From: "David O'Brien" To: Scott Long Message-ID: <20050118035259.GA37476@dragon.nuxi.com> References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> <41EC7D01.2070107@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41EC7D01.2070107@freebsd.org> 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: [RFC] what to name linux 32-bit compat 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: Tue, 18 Jan 2005 03:53:00 -0000 On Mon, Jan 17, 2005 at 08:05:37PM -0700, Scott Long wrote: > the direction of the LSB for linux compat. So my vote is that on all > platforms, /compat/linux is for 32-bit and /compat/linux64 is for > 64-bit. ... where there can be both. For Alpha there isn't a '64' suffix as there is only one possbility. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 04:39:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CB4716A4CE; Tue, 18 Jan 2005 04:39:45 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 428F843D48; Tue, 18 Jan 2005 04:39:45 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from 68-116-59-22.or.charter.com ([68.116.59.22] helo=[10.21.91.5]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1Cql9d-000F4U-5i; Tue, 18 Jan 2005 04:39:45 +0000 Message-ID: <41EC9313.90008@FreeBSD.org> Date: Mon, 17 Jan 2005 20:39:47 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20050117203818.GA29131@dragon.nuxi.com> <41EC7D01.2070107@freebsd.org> <20050118032436.GA5325@odin.ac.hmc.edu> <200501172235.34509.jhb@FreeBSD.org> In-Reply-To: <200501172235.34509.jhb@FreeBSD.org> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Scott Long cc: freebsd-amd64@FreeBSD.org Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 04:39:45 -0000 John Baldwin wrote: > Actually, I think going the non-ambiguous route and using the fuller names > like that (now that I see it) is probably the best bet when there is more > than one possibility. If you're (plural) going to go for the fuller names, given that /compat, (or more likely /usr/compat), could be shared in a large environment, it may be wise to revisit completely the naming: /usr/compat/linux/-/... eg: linux/amd64-i386, linux/alpha-alpha {/usr}/compat/linux/proc could still easily exist for linprocfs, if required. hell, even linux-pc98-i386 should something like that ever exist. I'm purposely not extending things to differentiate between redhat, suse, etc., since I'm a firm believer that we should be choosing one, and exactly one, "linux distribution" for the linuxulator. The key point I guess I'm trying to make is that this particular problem is not really limited to amd64 vs. i386 (or even 64- vs. 32-bit), and probably needs a bit more widespread thinking before going with a solution. If things are going to change, let's at least get them right for all possible architectures we know of (and support) now, rather than specific hacks for one particular instantiation of FreeBSD. -aDe From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 04:41:02 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EF0916A4CE for ; Tue, 18 Jan 2005 04:41:02 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18DF643D58 for ; Tue, 18 Jan 2005 04:41:02 +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 j0I4f1eR038490 for ; Mon, 17 Jan 2005 20:41:01 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0I4f1Pe038489 for freebsd-amd64@freebsd.org; Mon, 17 Jan 2005 20:41:01 -0800 (PST) (envelope-from obrien) Date: Mon, 17 Jan 2005 20:41:01 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20050118044101.GA38434@dragon.nuxi.com> References: <20050117203818.GA29131@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050117203818.GA29131@dragon.nuxi.com> 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 Subject: Re: [RFC] what to name linux 32-bit compat 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: Tue, 18 Jan 2005 04:41:02 -0000 On Mon, Jan 17, 2005 at 12:38:18PM -0800, David O'Brien wrote: > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). kan (Alexander Kabaev) fealt we could probably just follow Red Hat Enterprise Linux - which would put both 32-bit and 64-bit bits under /compat/linux. Upon thinking more about this; I think this will work. The linux32(1) command will be a little harder to impliment than seperate /compat/linux* (and I'm sure other details will have to be solved); but this does simplify things from a ports application POV. jhb agreed this was probably the better approach so I think this is what we'll do. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 07:36:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA82916A4CE; Tue, 18 Jan 2005 07:36:37 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 870D343D41; Tue, 18 Jan 2005 07:36:36 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) j0I7aYHo013132 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jan 2005 08:36:34 +0100 (CET) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)j0I7aY2X013131; Tue, 18 Jan 2005 08:36:34 +0100 (CET) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.1/8.13.1) with ESMTP id j0I7aDL0010643; Tue, 18 Jan 2005 08:36:14 +0100 (CET) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.1/8.13.1/Submit) id j0I7aDeJ010642; Tue, 18 Jan 2005 08:36:13 +0100 (CET) (envelope-from andreas) Date: Tue, 18 Jan 2005 08:36:13 +0100 From: Andreas Klemm To: John Baldwin Message-ID: <20050118073612.GA10427@titan.klemm.apsfilter.org> References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501172146.17965.jhb@FreeBSD.org> X-Operating-System: FreeBSD 5.3-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.6i cc: freebsd-amd64@freebsd.org Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 07:36:37 -0000 On Mon, Jan 17, 2005 at 09:46:17PM -0500, John Baldwin wrote: > > Personally, I think /compat/linux32 and /compat/linux (for linux64) would be > the best way to go. The idea being that /compat/linux runs native binaries > on any given arch, and if there's more than one arch supported, the > non-native ones get the funky names. Am not 100% sure but it might be a win to re-think this for port builders/designers. It might be beneficial not to use such "implicit" rules for naming like your suggestion for taking /compat/linux as native arch. I would perhaps name /compat/linux32 and /compat/linux64 explicitely, which might be a win and is IMHO not too expensive. Uname should IMHO get a new switch to print out default architecture of being 32 or 64 bit. So together with uname and the above naming scheme you have all you need and is compareable to what we already have (concerning uname) for cpu architecture. Do perhaps other BSD teams have added an mechanism like that or do they get 32/4 bit out of /proc ? Best regards Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 13:17:25 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B5DD16A56A; Tue, 18 Jan 2005 13:17:25 +0000 (GMT) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id C11DD43D2D; Tue, 18 Jan 2005 13:17:24 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: from aldan.algebra.com (mi@localhost [127.0.0.1]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j0IDHMRl003567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2005 08:17:22 -0500 (EST) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.13.1/8.13.1/Submit) id j0IDHGRH003566; Tue, 18 Jan 2005 08:17:16 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <200501181317.j0IDHGRH003566@aldan.algebra.com> To: amd64@FreeBSD.org, freebsd-emulation@FreeBSD.org Date: Tue, 18 Jan 2005 08:17:16 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w y+z3/UR{6SCQ X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: stijn@win.tue.nl cc: danfe@FreeBSD.org cc: danfe@regency.nsu.ru cc: tjr@FreeBSD.org cc: osa@FreeBSD.org Subject: Linux i386, NVidia on FreeBSD/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: Tue, 18 Jan 2005 13:17:25 -0000 Hello! I'd like my next machine to be an amd64, but need to make sure, a few things can be made to work before comitting. 1) Linux/i386 emulation -- Tim's page at http://people.freebsd.org/~tjr/linux32.html seems to suggest, there should be no problems with most of the things, does the linux-mozilla and Flash-7.x combo work anyone on FreeBSD/amd64? The OFoto.com web-site has a nice "application", which requires Flash-7 (6.x will not work). 2) NVidia X11 driver -- this is not a must, but would be very nice to have -- I have a fairly high-end dual-DVI card, that works fine on my dual PentiumII. Any hope of getting NVidia to release amd64-version? 3) SMP -- a dual-Opteron machine seems within my budget. Does that change the answers to any of the above questions? Thanks a lot for your time! Yours, -mi From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 14:37:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 312EE16A4CE for ; Tue, 18 Jan 2005 14:37:50 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7983C43D46 for ; Tue, 18 Jan 2005 14:37:49 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so864952wri for ; Tue, 18 Jan 2005 06:37:49 -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=CWB1LJ/I/ZxDjCQ9OKZX+Zo8KTbIpKvyvFc7tflZ5XP4vx2cEpN0VZDZLsJtlTIE6yLytcIeuGAYNpQ0YXkQPyi7ZZOqkGJ8gzTJm3PnZNFfcCNwPrarz9j0OcXLjEsMQR5MAAldz0fGj9TqT3AG4NisanNiI49+t4apr6XDkhU= Received: by 10.54.1.69 with SMTP id 69mr32986wra; Tue, 18 Jan 2005 06:37:49 -0800 (PST) Received: by 10.54.40.73 with HTTP; Tue, 18 Jan 2005 06:37:48 -0800 (PST) Message-ID: <2fd864e050118063747f5caa3@mail.gmail.com> Date: Tue, 18 Jan 2005 08:37:48 -0600 From: Astrodog To: Andreas Klemm , freebsd-amd64@freebsd.org In-Reply-To: <20050118073612.GA10427@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> <20050118073612.GA10427@titan.klemm.apsfilter.org> Subject: Re: [RFC] what to name linux 32-bit compat X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 14:37:50 -0000 On Tue, 18 Jan 2005 08:36:13 +0100, Andreas Klemm wrote: > On Mon, Jan 17, 2005 at 09:46:17PM -0500, John Baldwin wrote: > > > > Personally, I think /compat/linux32 and /compat/linux (for linux64) would be > > the best way to go. The idea being that /compat/linux runs native binaries > > on any given arch, and if there's more than one arch supported, the > > non-native ones get the funky names. > > Am not 100% sure but it might be a win to re-think this for port > builders/designers. > > It might be beneficial not to use such "implicit" rules for naming > like your suggestion for taking /compat/linux as native arch. > > I would perhaps name /compat/linux32 and /compat/linux64 explicitely, > which might be a win and is IMHO not too expensive. > > Uname should IMHO get a new switch to print out default architecture > of being 32 or 64 bit. > > So together with uname and the above naming scheme you have all you need > and is compareable to what we already have (concerning uname) for > cpu architecture. > > Do perhaps other BSD teams have added an mechanism like that or > do they get 32/4 bit out of /proc ? > > Best regards > > Andreas /// > > -- > Andreas Klemm - Powered by FreeBSD 5.1-CURRENT > Need a magic printfilter today ? -> http://www.apsfilter.org/ > _______________________________________________ > 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" > Not sure if it got lost, so I'm gonna summarize what I said earlier, Why not have /compat/linux32, and /compat/linux64 (For things that require one or the other), then just have /compat/linux linked to the native setup for the machine? That gives the ease of /compat/linux for the native stuff, without causing the problems Andreas pointed out. Also allows people with "clean" 64-bit friendly code to just use /compat/linux on AMD64 or i386, and have things work in whatever way is native to the machine. This could also be extended to other archs, if that ever becomes an issue. (linuxppc, linuxsparc64, whatever), with linux still pointing to native. --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 19:36:19 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EB3E16A4CE for ; Tue, 18 Jan 2005 19:36:19 +0000 (GMT) Received: from pegasus.cc.ucf.edu (ucf.edu [132.170.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F30C43D41 for ; Tue, 18 Jan 2005 19:36:19 +0000 (GMT) (envelope-from ewayte@pegasus.cc.ucf.edu) Received: from pegasus (pegasus [132.170.240.30]) by pegasus.cc.ucf.edu (Postfix) with ESMTP id 505A22903 for ; Tue, 18 Jan 2005 14:36:18 -0500 (EST) Date: Tue, 18 Jan 2005 14:36:18 -0500 (EST) From: Eric Wayte X-X-Sender: ewayte@pegasus To: freebsd-amd64@freebsd.org In-Reply-To: <20050118044101.GA38434@dragon.nuxi.com> Message-ID: References: <20050117203818.GA29131@dragon.nuxi.com> <20050118044101.GA38434@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 19:36:19 -0000 On Mon, 17 Jan 2005, David O'Brien wrote: > Date: Mon, 17 Jan 2005 20:41:01 -0800 > From: David O'Brien > Reply-To: freebsd-amd64@freebsd.org > To: freebsd-amd64@freebsd.org > Subject: Re: [RFC] what to name linux 32-bit compat > > On Mon, Jan 17, 2005 at 12:38:18PM -0800, David O'Brien wrote: >> We need to decide how to have both Linux i686 and Linux amd64 compat >> support live side-by-side. At the moment my leanings are for >> /compat/linux32 and /compat/linux. We could also go with /compat/linux >> and /compat/linux64 <- taking a page from the Linux LSB naming convention >> (ie, they have lib and lib64). > > kan (Alexander Kabaev) fealt we could probably just follow Red Hat > Enterprise Linux - which would put both 32-bit and 64-bit bits under > /compat/linux. Upon thinking more about this; I think this will work. > The linux32(1) command will be a little harder to impliment than seperate > /compat/linux* (and I'm sure other details will have to be solved); but > this does simplify things from a ports application POV. > > jhb agreed this was probably the better approach so I think this is what > we'll do. > > -- > -- David (obrien@FreeBSD.org) > A previous post mentioned having 64-bit Linux around for Oracle. Why don't we follow their standard of /lib (/compat/linux) for 64-bit libraries and /lib32 (/compat/linux32) for the 32-bit libraries? This is how it's done on 64-bit Solaris anyway. Eric Wayte Sr. DBA Univ. of Central Florida ewayte@pegasus.cc.ucf.edu From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 19:53:34 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C2D916A4CE for ; Tue, 18 Jan 2005 19:53:34 +0000 (GMT) Received: from mail13.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3730D43D1F for ; Tue, 18 Jan 2005 19:53:34 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6805 invoked from network); 18 Jan 2005 19:53:34 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 19:53:33 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0IJrRCW098493; Tue, 18 Jan 2005 14:53:30 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Tue, 18 Jan 2005 14:53:57 -0500 User-Agent: KMail/1.6.2 References: <20050117203818.GA29131@dragon.nuxi.com> <20050118044101.GA38434@dragon.nuxi.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501181453.57467.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 19:53:34 -0000 On Tuesday 18 January 2005 02:36 pm, Eric Wayte wrote: > On Mon, 17 Jan 2005, David O'Brien wrote: > > Date: Mon, 17 Jan 2005 20:41:01 -0800 > > From: David O'Brien > > Reply-To: freebsd-amd64@freebsd.org > > To: freebsd-amd64@freebsd.org > > Subject: Re: [RFC] what to name linux 32-bit compat > > > > On Mon, Jan 17, 2005 at 12:38:18PM -0800, David O'Brien wrote: > >> We need to decide how to have both Linux i686 and Linux amd64 compat > >> support live side-by-side. At the moment my leanings are for > >> /compat/linux32 and /compat/linux. We could also go with /compat/linux > >> and /compat/linux64 <- taking a page from the Linux LSB naming > >> convention (ie, they have lib and lib64). > > > > kan (Alexander Kabaev) fealt we could probably just follow Red Hat > > Enterprise Linux - which would put both 32-bit and 64-bit bits under > > /compat/linux. Upon thinking more about this; I think this will work. > > The linux32(1) command will be a little harder to impliment than seperate > > /compat/linux* (and I'm sure other details will have to be solved); but > > this does simplify things from a ports application POV. > > > > jhb agreed this was probably the better approach so I think this is what > > we'll do. > > > > -- > > -- David (obrien@FreeBSD.org) > > A previous post mentioned having 64-bit Linux around for Oracle. Why > don't we follow their standard of /lib (/compat/linux) for 64-bit > libraries and /lib32 (/compat/linux32) for the 32-bit libraries? This is > how it's done on 64-bit Solaris anyway. What RedHat apparently does is /lib for 32-bit libraries and /lib64 for 64-bit libraries, and kan's suggestion would be for us to do the same with /compat/linux/lib and /compat/linux/lib64. -- 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 Jan 18 19:54:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F5BE16A4CE for ; Tue, 18 Jan 2005 19:54:53 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 58BD543D49 for ; Tue, 18 Jan 2005 19:54:52 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 4751 invoked by uid 513); 18 Jan 2005 19:54:55 -0000 Received: from 82.141.59.141 by dsl-mail (envelope-from , uid 89) with qmail-scanner-1.24 (clamdscan: 0.80/609. spamassassin: 2.60. Clear:RC:1(82.141.59.141):SA:0(-1.4/5.0):. Processed in 9.278186 secs); 18 Jan 2005 19:54:55 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 Received: from reverse-82-141-59-141.dialin.kamp-dsl.de (HELO lobo.homeunix.org) (82.141.59.141) by dsl-mail.kamp.net with SMTP; 18 Jan 2005 19:54:46 -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 j0IJshDC014666 for ; Tue, 18 Jan 2005 20:54:44 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id j0IJshUq014657 for freebsd-amd64@freebsd.org; Tue, 18 Jan 2005 20:54:43 +0100 (CET) (envelope-from ewinter) Date: Tue, 18 Jan 2005 20:54:43 +0100 From: "Ernst W. Winter" To: freebsd-amd64@freebsd.org Message-ID: <20050118195443.GA14235@lobo.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: printer 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: Tue, 18 Jan 2005 19:54:53 -0000 I have found the probolem, the dmesg output is this: ppc0: cannot reserve I/O port range so what can I do? Ersnt -- 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 Tue Jan 18 20:12:57 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7FDE16A4CE; Tue, 18 Jan 2005 20:12:57 +0000 (GMT) Received: from minerva.int.gov.br (nat.int.gov.br [200.20.196.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98FFD43D31; Tue, 18 Jan 2005 20:12:56 +0000 (GMT) (envelope-from jonny@jonny.eng.br) Received: from [10.0.8.17] (dinf-02 [10.0.8.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by minerva.int.gov.br (Postfix) with ESMTP id C7004BE507; Tue, 18 Jan 2005 18:12:54 -0200 (BRDT) Message-ID: <41ED6DC6.1000604@jonny.eng.br> Date: Tue, 18 Jan 2005 18:12:54 -0200 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Astrodog References: <20050117203818.GA29131@dragon.nuxi.com> <200501172146.17965.jhb@FreeBSD.org> <20050118073612.GA10427@titan.klemm.apsfilter.org> <2fd864e050118063747f5caa3@mail.gmail.com> In-Reply-To: <2fd864e050118063747f5caa3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-amd64@freebsd.org cc: Andreas Klemm Subject: Re: [RFC] what to name linux 32-bit compat 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, 18 Jan 2005 20:12:57 -0000 Astrodog wrote: > On Tue, 18 Jan 2005 08:36:13 +0100, Andreas Klemm wrote: > >>On Mon, Jan 17, 2005 at 09:46:17PM -0500, John Baldwin wrote: >> >>>Personally, I think /compat/linux32 and /compat/linux (for linux64) would be >>>the best way to go. The idea being that /compat/linux runs native binaries >>>on any given arch, and if there's more than one arch supported, the >>>non-native ones get the funky names. >> >>Am not 100% sure but it might be a win to re-think this for port >>builders/designers. >> >>It might be beneficial not to use such "implicit" rules for naming >>like your suggestion for taking /compat/linux as native arch. >> >>I would perhaps name /compat/linux32 and /compat/linux64 explicitely, >>which might be a win and is IMHO not too expensive. >> >>Uname should IMHO get a new switch to print out default architecture >>of being 32 or 64 bit. >> >>So together with uname and the above naming scheme you have all you need >>and is compareable to what we already have (concerning uname) for >>cpu architecture. >> >>Do perhaps other BSD teams have added an mechanism like that or >>do they get 32/4 bit out of /proc ? >> >>Best regards >> >> Andreas /// > > > Not sure if it got lost, so I'm gonna summarize what I said earlier, > Why not have /compat/linux32, and /compat/linux64 (For things that > require one or the other), then just have /compat/linux linked to the > native setup for the machine? That gives the ease of /compat/linux for > the native stuff, without causing the problems Andreas pointed out. Thats exactly what I was going to write now. Symlink is the solution! > Also allows people with "clean" 64-bit friendly code to just use > /compat/linux on AMD64 or i386, and have things work in whatever way > is native to the machine. > > This could also be extended to other archs, if that ever becomes an > issue. (linuxppc, linuxsparc64, whatever), with linux still pointing > to native. -- João Carlos Mendes Luís From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 20:55:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03D5916A4CE for ; Tue, 18 Jan 2005 20:55:54 +0000 (GMT) Received: from mail.wolves.k12.mo.us (duey.wolves.k12.mo.us [207.160.214.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 568B843D3F for ; Tue, 18 Jan 2005 20:55:53 +0000 (GMT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id A9CBB1FE27; Tue, 18 Jan 2005 14:55:52 -0600 (CST) Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (mail.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 77490-01; Tue, 18 Jan 2005 14:55:50 -0600 (CST) Received: by mail.wolves.k12.mo.us (Postfix, from userid 1001) id 219DE1FE26; Tue, 18 Jan 2005 14:55:50 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 200C21A90C; Tue, 18 Jan 2005 14:55:50 -0600 (CST) Date: Tue, 18 Jan 2005 14:55:50 -0600 (CST) From: Chris Dillon To: Mikhail Teterin In-Reply-To: <200501181317.j0IDHGRH003566@aldan.algebra.com> Message-ID: <20050118144834.X78006@duey.wolves.k12.mo.us> References: <200501181317.j0IDHGRH003566@aldan.algebra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at wolves.k12.mo.us cc: amd64@FreeBSD.org Subject: Re: Linux i386, NVidia on FreeBSD/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: Tue, 18 Jan 2005 20:55:54 -0000 On Tue, 18 Jan 2005, Mikhail Teterin wrote: > I'd like my next machine to be an amd64, but need to make sure, a > few things can be made to work before comitting. Even if you can't get what you want to work under FreeBSD/amd64, you can still get the AMD64 machine and run FreeBSD/x86 on it just like any other box. Eventually you could move up to FreeBSD/amd64 when everything you want works there. I was running my dual-Opteron under FreeBSD/x86 4.10 for a while (mostly out of laziness because that was what was already on my hard drive from my previous system) and just recently installed FreeBSD/amd64 5.3, but I don't have the same requirements you listed so I can't comment on wether any of that works under amd64 yet. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest, most open, and most stable OS on the planet - Available for IA32, IA64, AMD64, PC98, Alpha, and UltraSPARC architectures - PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 21:11:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 251EE16A4CE for ; Tue, 18 Jan 2005 21:11:51 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7E3A43D5A for ; Tue, 18 Jan 2005 21:11:50 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so53032wri for ; Tue, 18 Jan 2005 13:11:44 -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=drKfaaDcliXANV8jdD/2GBY7VGo8WjWlN17w1SeY3Irx4I+SZGX3HrXgMt9VWMZ9Wovu45JlbyQYrkLSBNs5yHO82T5YFpbDeoXpiTRYL4KqySOlPqiWz0kp1U2atpqy80e+JU4MFv3qS5MRflDCagHdvMoILQ1CVlWYnh6Zel0= Received: by 10.54.30.53 with SMTP id d53mr284602wrd; Tue, 18 Jan 2005 13:11:43 -0800 (PST) Received: by 10.54.40.73 with HTTP; Tue, 18 Jan 2005 13:11:43 -0800 (PST) Message-ID: <2fd864e05011813114d470c14@mail.gmail.com> Date: Tue, 18 Jan 2005 15:11:43 -0600 From: Astrodog To: Ganael Laplanche , freebsd-amd64@freebsd.org In-Reply-To: <20050106165128.M36915@martymac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <20050105172443.M43967@martymac.com> <41DC2AEE.9090805@bredband.net> <20050106165128.M36915@martymac.com> Subject: Re: Asus K8N-E and slow disk transfer X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 21:11:51 -0000 On Thu, 6 Jan 2005 16:52:35 +0000, Ganael Laplanche wrote: > Hi, >=20 > Thank you for you answer :) >=20 > I have a new 80 lead ATA cable (a brand new provided with my mobo) and my= disk > is a single device on the channel (no slave)... >=20 > Any (other) idea ? >=20 > Gana=EBl LAPLANCHE > ganael.laplanche@martymac.com > http://www.martymac.com > Tel : (+33)6.84.03.57.24. >=20 > ---------- Original Message ----------- > From: Lars Tunkrans > To: Ganael Laplanche > Cc: freebsd-amd64@freebsd.org > Sent: Wed, 05 Jan 2005 18:59:10 +0100 > Subject: Re: Asus K8N-E and slow disk transfer >=20 > > Ganael Laplanche wrote: > > > Hi all, > > > > > > I've just bought an ASUS K8N-E mobo. I'm using FreeBSD-5.3-Stable (am= d64) and > > > suffering from *very* slow disk transfer rates. The chipset is an nfo= rce3 and is > > > correctly detected at boot : > > > > > > # dmesg > > > [...] > > > atapci0: port > > > 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pc= i 0 > > > [...] > > > > > > My disk is an UDMA100 one, everything seems to be correct : > > > # atacontrol mode 0 > > > Master =3D UDMA100 > > > Slave =3D BIOSPIO > > > > > > > If you have a New and an OLD disk on the same ATA chanell ; > > Do you have an old 40 lead or an new 80 lead ATA cable ? > > > > 80 lead cable is a requirement f=F6r UDMA100 ! > > > > //Lars > ------- End of Original Message ------- > _______________________________________________ > 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" >=20 This may be a potential NForce3 Compatibility Issue. You may try using atacontrol to force the "slave" to UDMA100 as well. Also, at 11MB/s, its above the rate I'd expect to see if it was using PIO (Though, I may easily be wrong on that). Also, if you're copying from the disk, to the same disk, keep in mind, 11MB/s apparent, is 22MB/s of disc I/O. What kind of CPU usage do you see during the copy? (time, uptime, and vmstat output would be helpful) --- Harrison Grundy From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 21:12:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F105416A4CE for ; Tue, 18 Jan 2005 21:12:37 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E2BB43D55 for ; Tue, 18 Jan 2005 21:12:37 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so53189wri for ; Tue, 18 Jan 2005 13:12:36 -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=U/IfekXLJMegSbH2Nt/r0MMhziNJvP0P5a8BmmUH1/CYlTp3CuX9KlS8qEfQf0KV53/C8SJ87SxZtwpFhNwDe+lvXijd+lz/HeNGljiLWm0HTQAPeyECMie//GZGn5p6OtUb8JhPhw6JQ72RAaRGe3wscLjbcEueLdk8xRAkYTM= Received: by 10.54.38.8 with SMTP id l8mr131249wrl; Tue, 18 Jan 2005 13:12:36 -0800 (PST) Received: by 10.54.40.73 with HTTP; Tue, 18 Jan 2005 13:12:36 -0800 (PST) Message-ID: <2fd864e05011813123a196136@mail.gmail.com> Date: Tue, 18 Jan 2005 15:12:36 -0600 From: Astrodog To: Ganael Laplanche , freebsd-amd64@freebsd.org In-Reply-To: <2fd864e05011813114d470c14@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: <20050105172443.M43967@martymac.com> <41DC2AEE.9090805@bredband.net> <20050106165128.M36915@martymac.com> <2fd864e05011813114d470c14@mail.gmail.com> Subject: Re: Asus K8N-E and slow disk transfer X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 21:12:38 -0000 On Tue, 18 Jan 2005 15:11:43 -0600, Astrodog wrote: > On Thu, 6 Jan 2005 16:52:35 +0000, Ganael Laplanche > wrote: > > Hi, > > > > Thank you for you answer :) > > > > I have a new 80 lead ATA cable (a brand new provided with my mobo) and = my disk > > is a single device on the channel (no slave)... > > > > Any (other) idea ? > > > > Gana=EBl LAPLANCHE > > ganael.laplanche@martymac.com > > http://www.martymac.com > > Tel : (+33)6.84.03.57.24. > > > > ---------- Original Message ----------- > > From: Lars Tunkrans > > To: Ganael Laplanche > > Cc: freebsd-amd64@freebsd.org > > Sent: Wed, 05 Jan 2005 18:59:10 +0100 > > Subject: Re: Asus K8N-E and slow disk transfer > > > > > Ganael Laplanche wrote: > > > > Hi all, > > > > > > > > I've just bought an ASUS K8N-E mobo. I'm using FreeBSD-5.3-Stable (= amd64) and > > > > suffering from *very* slow disk transfer rates. The chipset is an n= force3 and is > > > > correctly detected at boot : > > > > > > > > # dmesg > > > > [...] > > > > atapci0: port > > > > 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on = pci 0 > > > > [...] > > > > > > > > My disk is an UDMA100 one, everything seems to be correct : > > > > # atacontrol mode 0 > > > > Master =3D UDMA100 > > > > Slave =3D BIOSPIO > > > > > > > > > > If you have a New and an OLD disk on the same ATA chanell ; > > > Do you have an old 40 lead or an new 80 lead ATA cable ? > > > > > > 80 lead cable is a requirement f=F6r UDMA100 ! > > > > > > //Lars > > ------- End of Original Message ------- > > _______________________________________________ > > 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= " > > >=20 > This may be a potential NForce3 Compatibility Issue. >=20 > You may try using atacontrol to force the "slave" to UDMA100 as well. >=20 > Also, at 11MB/s, its above the rate I'd expect to see if it was using > PIO (Though, I may easily be wrong on that). Also, if you're copying > from the disk, to the same disk, keep in mind, 11MB/s apparent, is > 22MB/s of disc I/O. >=20 > What kind of CPU usage do you see during the copy? (time, uptime, and > vmstat output would be helpful) >=20 > --- Harrison Grundy >=20 Disregard second to last paragraph. Just noticed you said 1MB/s, instead of 11MB/s. Sorry. From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 21:18:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E715D16A4CE for ; Tue, 18 Jan 2005 21:18:53 +0000 (GMT) Received: from tao.gomezmarin.com (83.Red-80-59-5.pooles.rima-tde.net [80.59.5.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 7725643D60 for ; Tue, 18 Jan 2005 21:18:52 +0000 (GMT) (envelope-from francisco@gomezmarin.com) Received: (qmail 7680 invoked from network); 18 Jan 2005 21:18:51 -0000 Received: from unknown (HELO ?172.26.0.2?) (172.26.0.2) by tao.gomezmarin.com with SMTP; 18 Jan 2005 21:18:51 -0000 Message-ID: <41ED7D36.1000604@gomezmarin.com> Date: Tue, 18 Jan 2005 22:18:46 +0100 From: =?ISO-8859-15?Q?Francisco_G=F3mez_Mar=EDn?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Freebsd Amd64 X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: x86 to amd64 upgrade 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, 18 Jan 2005 21:18:54 -0000 Hi all, I am running FreeBSD-AMD64 5.3 in my Athlon64 box. If I install on it the x86 version, could it be possible to upgrade to the amd64 without reinstalling? any experiences? -- Key fingerprint = 2D5F 59BD E6CB 8473 9619 2DD9 029A 36F9 7B3E 6A90 From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 21:43:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C088416A4CE for ; Tue, 18 Jan 2005 21:43:30 +0000 (GMT) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id E05CB43D2D for ; Tue, 18 Jan 2005 21:43:29 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: (qmail 24010 invoked by uid 513); 18 Jan 2005 21:43:35 -0000 Received: from 82.141.59.141 by dsl-mail (envelope-from , uid 89) with qmail-scanner-1.24 (clamdscan: 0.80/609. spamassassin: 2.60. Clear:RC:1(82.141.59.141):SA:0(-1.4/5.0):. Processed in 5.793461 secs); 18 Jan 2005 21:43:35 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 Received: from reverse-82-141-59-141.dialin.kamp-dsl.de (HELO lobo.homeunix.org) (82.141.59.141) by dsl-mail.kamp.net with SMTP; 18 Jan 2005 21:43:29 -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 j0ILiQGM000612 for ; Tue, 18 Jan 2005 22:44:26 +0100 (CET) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.1/8.13.1/Submit) id j0ILiPIv000611 for freebsd-amd64@freebsd.org; Tue, 18 Jan 2005 22:44:25 +0100 (CET) (envelope-from ewinter) Date: Tue, 18 Jan 2005 22:44:25 +0100 From: "Ernst W. Winter" To: freebsd-amd64@freebsd.org Message-ID: <20050118214425.GC550@lobo.homeunix.org> References: <20050118195443.GA14235@lobo.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050118195443.GA14235@lobo.homeunix.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: printer 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: Tue, 18 Jan 2005 21:43:30 -0000 On Tue, 18 Jan 2005, Ernst W. Winter wrote: > I have found the probolem, the dmesg output is this: > > ppc0: cannot reserve I/O port range > > so what can I do? > got the solution too, it was in the BIOS and I set the printer to ECP and this is the message now with it: -----------------------------Snip------------------------------------- ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on ac pi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 -----------------------------Snip------------------------------------- and all is well. Silly when you think of it, but it helped. 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 Tue Jan 18 21:54:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3194E16A4CE for ; Tue, 18 Jan 2005 21:54:16 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9848843D48 for ; Tue, 18 Jan 2005 21:54:15 +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 j0ILsDqK028949; Tue, 18 Jan 2005 22:54:14 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Tue, 18 Jan 2005 22:52:53 +0100 User-Agent: KMail/1.7.91 References: <41ED7D36.1000604@gomezmarin.com> In-Reply-To: <41ED7D36.1000604@gomezmarin.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1399551.DTiTbP3jiM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501182252.58752.groot@kde.org> Subject: Re: x86 to amd64 upgrade 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, 18 Jan 2005 21:54:16 -0000 --nextPart1399551.DTiTbP3jiM Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 18 January 2005 22:18, Francisco G=F3mez Mar=EDn wrote: > I am running FreeBSD-AMD64 5.3 in my Athlon64 box. If I install on it > the x86 version, could it be possible to upgrade to the amd64 without > reinstalling? any experiences? Check the archives of this list; this is a question that comes up again and= =20 again. The brief answer is: no, not unless you are a masochist with time to= =20 waste and capable of an infuriating attention to detail (do you play nethac= k?=20 do you play each charater to win _and_ as an extinctionist? then you're=20 in :) ). Or David O'Brien, I think he figured it out. The game plan is 30-o= dd=20 steps fraught with peril. I think the old luxury-goods adage applies: if you have to ask, you can't=20 afford it. =2D-=20 Don't worry, 't ain't no shame to be stupid - ol' mouse. GPG: FEA2 A3FE Adriaan de Groot --nextPart1399551.DTiTbP3jiM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBB7YU6dqzuAf6io/4RAvk1AKCW5KvGISGLt48gqEPxBHKpRtYXFwCeKPni u8C4uluK7UcQQXvlkuRGTmA= =x/tL -----END PGP SIGNATURE----- --nextPart1399551.DTiTbP3jiM-- From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 22:22:00 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B941A16A4CE for ; Tue, 18 Jan 2005 22:22:00 +0000 (GMT) Received: from mail16.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 777CF43D4C for ; Tue, 18 Jan 2005 22:22:00 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 22704 invoked from network); 18 Jan 2005 22:22:00 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 22:21:59 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0IMLt6o099440; Tue, 18 Jan 2005 17:21:55 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Tue, 18 Jan 2005 16:53:41 -0500 User-Agent: KMail/1.6.2 References: <41ED7D36.1000604@gomezmarin.com> In-Reply-To: <41ED7D36.1000604@gomezmarin.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <200501181653.41668.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Subject: Re: x86 to amd64 upgrade 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, 18 Jan 2005 22:22:00 -0000 On Tuesday 18 January 2005 04:18 pm, Francisco G=F3mez Mar=EDn wrote: > Hi all, > > I am running FreeBSD-AMD64 5.3 in my Athlon64 box. If I install on it > the x86 version, could it be possible to upgrade to the amd64 without > reinstalling? any experiences? Not without much pain and suffering. A reinstall is really the only viable= =20 choice. Note that you could make sure and stick all your data on a /data=20 partition or some such and when you reinstall FreeBSD/amd64 just not newfs= =20 that partition so you keep the actual data. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 03:58:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F179F16A4CE; Wed, 19 Jan 2005 03:58:03 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9ACC43D4C; Wed, 19 Jan 2005 03:58:03 +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 j0J3vct8065691; Tue, 18 Jan 2005 19:57:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0J3vb3E065690; Tue, 18 Jan 2005 19:57:37 -0800 (PST) (envelope-from obrien) Date: Tue, 18 Jan 2005 19:57:37 -0800 From: "David O'Brien" To: Mikhail Teterin Message-ID: <20050119035737.GA65592@dragon.nuxi.com> References: <200501181317.j0IDHGRH003566@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501181317.j0IDHGRH003566@aldan.algebra.com> 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-emulation@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: Linux i386, NVidia on FreeBSD/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, 19 Jan 2005 03:58:04 -0000 On Tue, Jan 18, 2005 at 08:17:16AM -0500, Mikhail Teterin wrote: > Hello! > > I'd like my next machine to be an amd64, but need to make sure, a few > things can be made to work before comitting. > > 1) Linux/i386 emulation -- Tim's page at > http://people.freebsd.org/~tjr/linux32.html I wish he'd update that page -- just use the ports now. > 2) NVidia X11 driver -- this is not a must, but would be very > nice to have -- I have a fairly high-end dual-DVI card, that > works fine on my dual PentiumII. Any hope of getting NVidia to > release amd64-version? Nope. > 3) SMP -- a dual-Opteron machine seems within my budget. Does > that change the answers to any of the above questions? Works even better. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 04:03:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF6F016A4CE; Wed, 19 Jan 2005 04:03:39 +0000 (GMT) Received: from web4.thecenturiongroup.com (104-238-234-66.cosmoweb.net [66.234.238.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCFF443D58; Wed, 19 Jan 2005 04:03:36 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id 2E98F7C007; Tue, 18 Jan 2005 23:03:36 -0500 (EST) Message-ID: <41EDDB38.1000107@michaelmeltzer.com> Date: Tue, 18 Jan 2005 22:59:52 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 19 Jan 2005 04:03:40 -0000 straight boot, no patches or extra debug. -mjm Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #14: Thu Jan 13 23:55:20 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963796480 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 pci1: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: [GIANT-LOCKED] pci0: at device 11.1 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled acd0: DVDROM at ata0-master UDMA33 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> Vinod Kashyap wrote: >I tried reproducing the problem on both i386 and amd64, >but could not. I installed 5.3 RELEASE, cvsuped to the >tip of RELENG_5, re-built the kernel with twa integrated, >and rebooted. The test systems booted just fine (off of >3ware controlled da0). I even tried replacing just the >twa sources of 5.3 RELEASE with the twa sources from the >tip of RELENG_5, and that worked fine too. All this, >without even upgrading the firmware from 2.02.00.008 (which >is bundled into 5.3 RELEASE sources). So, I am confused as >to what might be happening. > >Could you give the attached patch a try? Just a hunch... > > > > > >>-----Original Message----- >>From: owner-freebsd-stable@freebsd.org >>[mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Michael Meltzer >>Sent: Friday, January 14, 2005 6:03 AM >>To: Vinod Kashyap >>Cc: freebsd stable >>Subject: Re: twa breakage on AMD64 with 9.1.5.2 >>3wareversionand2005-01-1103:00:49 UTC RELENG_5 commit >> >> >> >> >> >>>Could you see if the driver is getting loaded? The driver prints >>>the message: "3ware device driver for 9000 series storage >>> >>> >>controllers...". >> >> >>>Did the new firmware get flashed? You can download the firmware >>> >>> >>>from the 3ware website and flash it on the card using a DOS floppy. >> >> >>>Alternatively, you can add 'options TWA_FLASH_FIRMWARE' to your >>>kernel configuration file and rebuild the kernel. This should build >>>the kernel/driver with the firmware bundled, and the firmware should >>>automatically get downloaded the next time you reboot. >>> >>> >>> >>> >>> >>> >>> >>> >>I reloaded the new driver and rebuilt the kernel last night with the >>TWA_FLASH_FIRMWARE, Did not see the -D on the command line for the >>rebuild, the new firmware was not requested to load. I got the new >>firmware from 3ware and flashed it in, Still does not work. I >>also build >>a straight GENERIC Kernel, still no luck. Their is no error >>message that >>I saw and the versions number for the pieces did change so it >>the "new" >>stuff. I need to setup a serial console to capture the full messages, >>should have that on monday night. Thank You -mjm >> >> >>_______________________________________________ >>freebsd-stable@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>To unsubscribe, send any mail to >>"freebsd-stable-unsubscribe@freebsd.org" >> >> > > > From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 05:09:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 183B816A4CF; Wed, 19 Jan 2005 05:09:08 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4469A43D2D; Wed, 19 Jan 2005 05:09:07 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id B05F37C007; Wed, 19 Jan 2005 00:09:06 -0500 (EST) Message-ID: <41EDEA93.5060305@michaelmeltzer.com> Date: Wed, 19 Jan 2005 00:05:23 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 19 Jan 2005 05:09:08 -0000 boot with twa_r5.diff patch and options TWA_DEBUG=10 -mjm Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #15: Tue Jan 18 23:58:45 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 twa_probe: entered pcib1: at device 6.0 on pci0 pci1: on pcib1 twa_probe: entered pci1: at device 6.0 (no driver attached) twa_probe: entered isab0: at device 7.0 on pci0 isa0: on isab0 twa_probe: entered atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: at device 7.2 (no driver attached) twa_probe: entered pci0: at device 7.3 (no driver attached) twa_probe: entered pcib2: at device 10.0 on pci0 pci2: on pcib2 twa_probe: entered bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: at device 10.1 (no driver attached) twa_probe: entered pcib3: at device 11.0 on pci0 pci3: on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_init_ctlr: entered. twa0: twa_wait_status: entered. twa0: twa_drain_response_queue: entered. twa0: twa_init_connection: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_request: entered. twa0: twa_execute_scsi: SCSI I/O request 0x3 twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_enqueue_aen: entered. twa0: twa_enqueue_aen: AEN queue empty twa0: twa_release_request: entered. twa0: twa_init_ctlr: exiting. twa0: twa_describe_controller: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: twa_cam_setup: sc = 0xffffffff8082f000 twa0: twa_cam_setup: Calling cam_sim_alloc twa0: twa_cam_setup: Calling xpt_bus_register twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Calling xpt_create_path twa0: twa_cam_setup: Calling xpt_setup_ccb twa0: twa_cam_setup: Calling twa_request_bus_scan twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Exiting twa_probe: entered pci0: at device 11.1 (no driver attached) twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled twa0: twa_interrupt: entered. twa_bus_scan_cb: ccb = 0xffffff017f236800 twa_bus_scan_cb: success acd0: DVDROM at ata0-master UDMA33 twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 05:37:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20F9316A4CE; Wed, 19 Jan 2005 05:37:28 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51C4543D55; Wed, 19 Jan 2005 05:37:25 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id C17D87C007; Wed, 19 Jan 2005 00:37:24 -0500 (EST) Message-ID: <41EDF135.6010404@michaelmeltzer.com> Date: Wed, 19 Jan 2005 00:33:41 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 19 Jan 2005 05:37:28 -0000 using twa_patch1.diff: needed to add "int error" to twa_alloc_req_pkts -mjm Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #16: Wed Jan 19 00:29:26 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 twa_probe: entered pcib1: at device 6.0 on pci0 pci1: on pcib1 twa_probe: entered pci1: at device 6.0 (no driver attached) twa_probe: entered isab0: at device 7.0 on pci0 isa0: on isab0 twa_probe: entered atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: at device 7.2 (no driver attached) twa_probe: entered pci0: at device 7.3 (no driver attached) twa_probe: entered pcib2: at device 10.0 on pci0 pci2: on pcib2 twa_probe: entered bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: at device 10.1 (no driver attached) twa_probe: entered pcib3: at device 11.0 on pci0 pci3: on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 17f2da000, len = 40000 twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_init_ctlr: entered. twa0: twa_wait_status: entered. twa0: twa_drain_response_queue: entered. twa0: twa_init_connection: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_request: entered. twa0: twa_execute_scsi: SCSI I/O request 0x3 twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_enqueue_aen: entered. twa0: twa_enqueue_aen: AEN queue empty twa0: twa_release_request: entered. twa0: twa_init_ctlr: exiting. twa0: twa_describe_controller: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: twa_cam_setup: sc = 0xffffffff8082f000 twa0: twa_cam_setup: Calling cam_sim_alloc twa0: twa_cam_setup: Calling xpt_bus_register twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Calling xpt_create_path twa0: twa_cam_setup: Calling xpt_setup_ccb twa0: twa_cam_setup: Calling twa_request_bus_scan twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Exiting twa_probe: entered pci0: at device 11.1 (no driver attached) twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled twa0: twa_interrupt: entered. twa_bus_scan_cb: ccb = 0xffffff017f236800 twa_bus_scan_cb: success acd0: DVDROM at ata0-master UDMA33 twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 05:50:44 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A11C616A4CE; Wed, 19 Jan 2005 05:50:44 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA98243D46; Wed, 19 Jan 2005 05:50:43 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id BABFC7C00C; Wed, 19 Jan 2005 00:50:42 -0500 (EST) Message-ID: <41EDF452.1070305@michaelmeltzer.com> Date: Wed, 19 Jan 2005 00:46:58 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jean-Yves Avenard cc: freebsd stable cc: freebsd-amd64@freebsd.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 19 Jan 2005 05:50:44 -0000 twa_patch2.diff, had to add the "int error; in twa_alloc_req_pkts -mjm Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #17: Wed Jan 19 00:44:33 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 twa_probe: entered pcib1: at device 6.0 on pci0 pci1: on pcib1 twa_probe: entered pci1: at device 6.0 (no driver attached) twa_probe: entered isab0: at device 7.0 on pci0 isa0: on isab0 twa_probe: entered atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: at device 7.2 (no driver attached) twa_probe: entered pci0: at device 7.3 (no driver attached) twa_probe: entered pcib2: at device 10.0 on pci0 pci2: on pcib2 twa_probe: entered bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: at device 10.1 (no driver attached) twa_probe: entered pcib3: at device 11.0 on pci0 pci3: on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 17f2da000, len = 40000 twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_init_ctlr: entered. twa0: twa_wait_status: entered. twa0: twa_drain_response_queue: entered. twa0: twa_init_connection: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_request: entered. twa0: twa_execute_scsi: SCSI I/O request 0x3 twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_enqueue_aen: entered. twa0: twa_enqueue_aen: AEN queue empty twa0: twa_release_request: entered. twa0: twa_init_ctlr: exiting. twa0: twa_describe_controller: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: twa_get_param: entered. twa0: twa_get_request: entered. twa0: twa_immediate_request: entered. twa0: twa_map_request: entered. twa0: twa_setup_data_dmamap: entered. twa0: twa_start: entered. twa0: twa_done: entered. twa0: twa_drain_complete_queue: entered. twa0: twa_unmap_request: entered. twa0: twa_unmap_request: entered. twa0: twa_release_request: entered. twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: twa_cam_setup: sc = 0xffffffff8082f000 twa0: twa_cam_setup: Calling cam_sim_alloc twa0: twa_cam_setup: Calling xpt_bus_register twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Calling xpt_create_path twa0: twa_cam_setup: Calling xpt_setup_ccb twa0: twa_cam_setup: Calling twa_request_bus_scan twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_cam_setup: Exiting twa_probe: entered pci0: at device 11.1 (no driver attached) twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered twa_probe: entered atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled twa0: twa_interrupt: entered. twa_bus_scan_cb: ccb = 0xffffff017f236800 twa_bus_scan_cb: success acd0: DVDROM at ata0-master UDMA33 twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request twa0: twa_action: XPT_PATH_INQ request SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroo From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 07:32:45 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F276E16A4CE for ; Wed, 19 Jan 2005 07:32:44 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EFEF43D46 for ; Wed, 19 Jan 2005 07:32:44 +0000 (GMT) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CrAKY-0006Ts-00 for ; Wed, 19 Jan 2005 08:32:42 +0100 Received: from dhcp193.ifado.de ([195.253.22.193]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Jan 2005 08:32:42 +0100 Received: from wb by dhcp193.ifado.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Jan 2005 08:32:42 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-amd64@freebsd.org From: "Wilhelm B. Kloke" Date: Tue, 18 Jan 2005 18:26:23 +0000 (UTC) Organization: InstArbPhysUniDo Lines: 20 Message-ID: References: <200501181317.j0IDHGRH003566__19987.5461090871$1106054371$gmane$org@aldan.algebra.com> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dhcp193.ifado.de User-Agent: slrn/0.9.8.0 (FreeBSD) Cache-Post-Path: vestein!unknown@yorikke X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) Sender: news Subject: Re: Linux i386, NVidia on FreeBSD/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, 19 Jan 2005 07:32:45 -0000 Mikhail Teterin schrieb: > > 2) NVidia X11 driver -- this is not a must, but would be very > nice to have -- I have a fairly high-end dual-DVI card, that > works fine on my dual PentiumII. Any hope of getting NVidia to > release amd64-version? I have got an amd64 and a Nvidia Quadro card. So I can tell you about my personal experiences. So far, X11 works in 32bit-mode on both amd64 and i386. On a real i386 (AMD K6) active stereo was near to usable (minor flickering), on the amd64 I observed a lot more of flickering perturbations, in fact, there are only few moments, when stereo is not disturbed. The standard nv driver works fine on amd64. I asked for support for amd64 on the NVidia Linux forum. No answer till now. Probably you better stick to Linux when using the NVidia card. -- Dipl.-Math. Wilhelm Bernhard Kloke Institut fuer Arbeitsphysiologie an der Universitaet Dortmund Ardeystrasse 67, D-44139 Dortmund, Tel. 0231-1084-257 From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 18 18:13:07 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78FFD16A4E1 for ; Tue, 18 Jan 2005 18:13:05 +0000 (GMT) Received: from f26.mail.ru (f26.mail.ru [194.67.57.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF8C843D39 for ; Tue, 18 Jan 2005 18:13:04 +0000 (GMT) (envelope-from truthseeker@list.ru) Received: from mail by f26.mail.ru with local id 1Cqxqh-000OCt-00 for freebsd-amd64@freebsd.org; Tue, 18 Jan 2005 21:13:03 +0300 Received: from [62.32.51.190] by koi.mail.ru with HTTP; Tue, 18 Jan 2005 21:13:03 +0300 From: =?koi8-r?Q?=F2=D5=D3=CC=C1=CE=20=E2=D5=CB=C9=CE=20?= To: freebsd-amd64@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 192.168.0.1 via proxy [62.32.51.190] Date: Tue, 18 Jan 2005 21:13:03 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Mailman-Approved-At: Wed, 19 Jan 2005 13:05:28 +0000 Subject: one question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?koi8-r?Q?=F2=D5=D3=CC=C1=CE=20=E2=D5=CB=C9=CE?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 18:13:07 -0000 Is freebsd 5.3 support Amd 64 "Winchester" (socket939)? From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 13:43:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E24FC16A4CE for ; Wed, 19 Jan 2005 13:43:08 +0000 (GMT) Received: from peedub.jennejohn.org (J9dbe.j.pppool.de [85.74.157.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E97C43D39 for ; Wed, 19 Jan 2005 13:43:07 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id j0JDgrp9001928; Wed, 19 Jan 2005 14:42:54 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200501191342.j0JDgrp9001928@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: truthseeker@list.ru In-Reply-To: Message from =?koi8-r?Q?=F2=D5=D3=CC=C1=CE=20=E2=D5=CB=C9=CE=20?= Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jan 2005 14:42:53 +0100 From: Gary Jennejohn cc: freebsd-amd64@freebsd.org Subject: Re: one question 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, 19 Jan 2005 13:43:09 -0000 =?koi8-r?Q?=F2=D5=D3=CC=C1=CE=20=E2=D5=CB=C9=CE=20?= writes: > Is freebsd 5.3 support Amd 64 "Winchester" (socket939)? > _______________________________________________ Yes, I and a friend are using a winchester right now. He's running 5.3-STABLE, I'm running 6-current. It would be nice if you could avoid using russian characters in the headers. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 21:42:33 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 135B116A4D3; Wed, 19 Jan 2005 21:42:33 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC9BD43D39; Wed, 19 Jan 2005 21:42:32 +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 j0JLgTTA082822; Wed, 19 Jan 2005 16:42:31 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0JLgTBC082821; Wed, 19 Jan 2005 16:42:29 -0500 (EST) (envelope-from wayne) Date: Wed, 19 Jan 2005 16:42:29 -0500 From: "Michael R. Wayne" To: freebsd-stable@freebsd.org Message-ID: <20050119214229.GE1168@manor.msen.com> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Failure on today's CVS (stable, AMD) 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, 19 Jan 2005 21:42:33 -0000 CVS today. Dual Opteron running 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 Following the instructions in UPDATING, I get the following, indicating a bad kernel. 2 questions: 1) Is this a known, corrected issue as of today? I ran another CVSUP and did not see any changed to src. 2) More importantly, I recovered by loading /boot/kernel.old/kernel and the box is up BUT I am concerned that the NEXT time that I do "make installkernel" I'll stomp on kernel.old losing this fallback procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save but is there something else I should save? Or is there another suggested procedure? /\/\ \/\/ The box failed with: Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 21:45:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE73E16A4CE for ; Wed, 19 Jan 2005 21:45:12 +0000 (GMT) Received: from smtp1.fuse.net (mail-out1.fuse.net [216.68.8.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id C437E43D46 for ; Wed, 19 Jan 2005 21:45:11 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx4.fuse.net ([216.196.253.14]) by smtp1.fuse.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050119214327.LPSY18019.smtp1.fuse.net@gx4.fuse.net> for ; Wed, 19 Jan 2005 16:43:27 -0500 Received: from ramen.cokane.org ([216.196.253.14]) by gx4.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20050119214341.KIEZ13012.gx4.fuse.net@ramen.cokane.org> for ; Wed, 19 Jan 2005 16:43:41 -0500 Received: (qmail 83106 invoked by uid 1001); 19 Jan 2005 17:51:30 -0000 Date: Wed, 19 Jan 2005 17:51:30 +0000 From: Coleman Kane To: freebsd-amd64@freebsd.org Message-ID: <20050119175130.GI40809@ramen> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fLj60tP2PZ34xyqD" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Gateway/Emachines Mobile AMD64 Laptops (Arima 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: Wed, 19 Jan 2005 21:45:12 -0000 --fLj60tP2PZ34xyqD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I have a Gateway 7422GX mobile athlon64 laptop and have not been able to get the cpu throttling working. I went through the acpi_cpu.c code to investigate this, played around for a bit and came up empty. I looked at the linux cpufreq code and noticed some differences. I also did a DSDT dump from my ACPI BIOS to figure out the reason why the throttli= ng doesn't get probed.=20 It looks like when the FreeBSD driver searches for it, it looks for some data in the FADT (FACP) ACPI table to set it up. This information does=20 not appear to be in the acpi table at all. Thus, it comes up empty. The linux ACPI driver seems to look at the structures "_PSS", "_PCT", and "_PPC" which are links off the Processor object. These -do- exist in my DSDT dumps, but for some reason I can't seem to write code for the acpi_cpu driver to even find these and give me results. The information to handle my speed throttling and voltage throttling would appear to be in here, but I can't figure it out. Has anybody else messed with this code, or had these problems yet. I would like to help out if somebody else has already started working on solving this issue. I'd really like to get more than an hour out of my battery! BTW, I'm pretty happy with the laptop otherwise. It runs FreeBSD current quite well, ACPI enabled and all (which is more than I can say for the HP and Compaq laptops I've dealt with). Also, any helpful links you may have would be nice. I run the Free OS User Group at the University of Cincinnati and we've started seeing a number of these pop up around campus. Oh yeah, I had to set hw.ata.wc=3D0 to eliminate some UFS corruption issues. -- coleman kane --fLj60tP2PZ34xyqD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFB7p4iuDFwFZcwSdoRAnDsAKCEpVa4AO3rXlGTBOcDpAvGbOm70wCfYtf/ chN+pUOJZrbtBYC7+LhezF0= =KBY5 -----END PGP SIGNATURE----- --fLj60tP2PZ34xyqD-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 22:42:10 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DCC716A4CE for ; Wed, 19 Jan 2005 22:42:10 +0000 (GMT) Received: from kheops.speedy.net.pe (kheops.speedy.net.pe [200.48.172.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA23343D58 for ; Wed, 19 Jan 2005 22:42:09 +0000 (GMT) (envelope-from rcc@speedy.net.pe) Received: from kheops.speedy.net.pe (kheops.speedy.net.pe [200.48.172.40]) by kheops.speedy.net.pe (Postfix) with ESMTP id 2CE4A26427 for ; Wed, 19 Jan 2005 17:44:20 -0500 (PET) Date: Wed, 19 Jan 2005 17:44:20 -0500 (PET) From: Richard Cotrina To: freebsd-amd64@freebsd.org Message-ID: <20050119173135.V18358@kheops.speedy.net.pe> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: elf-32 binaries compat 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, 19 Jan 2005 22:42:10 -0000 Hi : Is there any special configuration needed to run elf 32 (i386) binaries in FreeBSD 5.3R/amd64 ? I am trying to run some 32 bit application in a kernel that has the following options enabled: options COMPAT_IA32 options COMPAT_FREEBSD4 and i got the following error: ELF interpreter /libexec/ld-elf32.so.1 not found Searching the list i found out that lib32 needs to be enabled, so I did : # cd /usr/src # /usr/src/tools/lib32/build32.sh It seems that it did not help because i still get an error when trying to run the elf 32 application : /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: unsupported file layout The question is how do I enable i386 compatibility (elf32)?. I don't have /compat/ia32 or something similar despite the fact my kernel has compat options enabled. I also got the following: # sysctl kern.elf32 kern.elf32.fallback_brand: -1 Any help or suggestion is welcome. Thanks in advance Richard Cotrina From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 19 23:48:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81F6416A4D4 for ; Wed, 19 Jan 2005 23:48:51 +0000 (GMT) Received: from mail.uk.psi.com (mail.uk.psi.com [154.8.2.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 492A343D49 for ; Wed, 19 Jan 2005 23:48:50 +0000 (GMT) (envelope-from alan.barrow@psinet.telstra.co.uk) Received: from ip11.vpn.uk.psi.com ([154.8.4.11] helo=macros) by mail.uk.psi.com with smtp (Exim 4.41) id 1CrPZ9-0000uS-Gx; Wed, 19 Jan 2005 23:48:48 +0000 From: To: "Richard Cotrina" , Date: Wed, 19 Jan 2005 23:42:47 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <20050119173135.V18358@kheops.speedy.net.pe> Subject: RE: elf-32 binaries compat 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: Wed, 19 Jan 2005 23:48:51 -0000 had many issues with this, gave up and rolled back to i386 on the opteron for the moment, we need the orcacle driver :( still i'm sure this will work in time. yours a.r.b. -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org]On Behalf Of Richard Cotrina Sent: 19 January 2005 22:44 To: freebsd-amd64@freebsd.org Subject: elf-32 binaries compat Hi : Is there any special configuration needed to run elf 32 (i386) binaries in FreeBSD 5.3R/amd64 ? I am trying to run some 32 bit application in a kernel that has the following options enabled: options COMPAT_IA32 options COMPAT_FREEBSD4 and i got the following error: ELF interpreter /libexec/ld-elf32.so.1 not found Searching the list i found out that lib32 needs to be enabled, so I did : # cd /usr/src # /usr/src/tools/lib32/build32.sh It seems that it did not help because i still get an error when trying to run the elf 32 application : /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: unsupported file layout The question is how do I enable i386 compatibility (elf32)?. I don't have /compat/ia32 or something similar despite the fact my kernel has compat options enabled. I also got the following: # sysctl kern.elf32 kern.elf32.fallback_brand: -1 Any help or suggestion is welcome. Thanks in advance Richard Cotrina _______________________________________________ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 03:14:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C61A416A4CE for ; Thu, 20 Jan 2005 03:14:42 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 119A343D2F for ; Thu, 20 Jan 2005 03:14:40 +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 j0K3EdxT051139 for ; Wed, 19 Jan 2005 22:14:39 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Wed, 19 Jan 2005 22:14:27 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_TIy7B7bJJiYMvtw" Message-Id: <200501192214.27401.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: Compaq R3000z ACPI fix 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, 20 Jan 2005 03:14:43 -0000 --Boundary-00=_TIy7B7bJJiYMvtw Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I finally found some time and made ACPI working on Compaq R3000z. You need to fix kernel and DSDT. The kernel hack is for FreeBSD/amd64. Similar hack should work with FreeBSD/i386 but I haven't tested. To enable the hack, you need to set 'hw.acpi.skip_timer_override=1' from loader or loader.conf. Yes, I stole the idea from Linux. ;-) http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.5/20040422223905-nforce2_timer.patch I only tested with the following options: options SMP device atpic The DSDT fix is against BIOS version F.33. To override DSDT, please read: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html Enjoy, Jung-uk Kim --Boundary-00=_TIy7B7bJJiYMvtw Content-Type: text/plain; charset="us-ascii"; name="madt.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="madt.diff" --- src/sys/amd64/acpica/madt.c.orig Thu Jun 10 17:30:08 2004 +++ src/sys/amd64/acpica/madt.c Wed Jan 19 21:49:50 2005 @@ -595,6 +595,14 @@ enum intr_trigger trig; enum intr_polarity pol; char buf[64]; + int skip_timer_override; + + if (getenv_int("hw.acpi.skip_timer_override", &skip_timer_override) && + intr->Source == 0 && intr->Interrupt == 2) { + if (bootverbose) + printf("MADT: skipping timer override.\n"); + return; + } if (bootverbose) printf("MADT: intr override: source %u, irq %u\n", --Boundary-00=_TIy7B7bJJiYMvtw Content-Type: text/plain; charset="us-ascii"; name="r3000z-asl.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="r3000z-asl.diff" --- r3000z.asl Wed Jan 19 21:53:10 2005 +++ r3000z-fixed.asl Wed Jan 19 21:19:20 2005 @@ -161,6 +161,7 @@ { Notify (\_SB.PWRB, 0x02) } + Return(Package(0x02){0x00, 0x00}) } Scope (\_PR) @@ -201,9 +202,10 @@ Scope (\_SB) { +/* Device (WMID) { - Name (_HID, "*pnp0c14") + Name (_HID, "PNP0C14") Name (_UID, 0x00) Name (_WDG, Buffer (0x14) { @@ -254,6 +256,7 @@ } } } +*/ Scope (\_SB) { @@ -1865,7 +1868,7 @@ } OperationRegion (ERAM, EmbeddedControl, 0x00, 0xFF) - Field (ERAM, AnyAcc, Lock, Preserve) + Field (ERAM, ByteAcc, Lock, Preserve) { Offset (0x60), SMPR, 8, @@ -2094,7 +2097,7 @@ } OperationRegion (ECRM, EmbeddedControl, 0x00, 0xFF) - Field (ECRM, AnyAcc, Lock, Preserve) + Field (ECRM, ByteAcc, Lock, Preserve) { Offset (0x94), ERIB, 16, @@ -2328,7 +2331,7 @@ IO (Decode16, 0x0010, 0x0010, 0x01, 0x10) IO (Decode16, 0x0022, 0x0022, 0x01, 0x1E) IO (Decode16, 0x0044, 0x0044, 0x01, 0x1C) - IO (Decode16, 0x0062, 0x0062, 0x01, 0x02) + /* IO (Decode16, 0x0062, 0x0062, 0x01, 0x02) */ IO (Decode16, 0x0065, 0x0065, 0x01, 0x0B) IO (Decode16, 0x0072, 0x0072, 0x01, 0x02) IO (Decode16, 0x0074, 0x0074, 0x01, 0x0C) @@ -3209,7 +3212,8 @@ IRQNoFlags () {3,4,5,11} DMA (Compatibility, BusMaster, Transfer16) {1,3,6} } - /*** Missing EndDependentFunctions descriptor */ }) + EndDependentFn() + }) Method (_SRS, 1, NotSerialized) { CreateByteField (Arg0, 0x02, IOLO) @@ -3633,6 +3637,7 @@ \_SB.PCI0.LPC0.PHSS (0x01) } } + Return (Package(0x02){0x00,0x00}) } Method (STBL, 1, NotSerialized) --Boundary-00=_TIy7B7bJJiYMvtw-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 03:19:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F328A16A505; Thu, 20 Jan 2005 03:19:49 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6ACB43D46; Thu, 20 Jan 2005 03:19:49 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id C176D72DD4; Wed, 19 Jan 2005 19:19:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id BEB7372DCB; Wed, 19 Jan 2005 19:19:49 -0800 (PST) Date: Wed, 19 Jan 2005 19:19:49 -0800 (PST) From: Doug White To: "Michael R. Wayne" In-Reply-To: <20050119214229.GE1168@manor.msen.com> Message-ID: <20050119191813.H78340@carver.gumbysoft.com> References: <20050119214229.GE1168@manor.msen.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) 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, 20 Jan 2005 03:19:50 -0000 On Wed, 19 Jan 2005, Michael R. Wayne wrote: > CVS today. Dual Opteron running > 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > Following the instructions in UPDATING, I get the following, > indicating a bad kernel. 2 questions: > > 1) Is this a known, corrected issue as of today? I ran another > CVSUP and did not see any changed to src. Looks like your SCSi controller stopped probing. You'll need to look at the dmesg more closely to identify why. > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure? You can use "make reinstallkernel", which will just spam over the current one without rotating it. I'd make the backup anyway in case you screw up; its also nice to keep a known working kenrel around Just In Case. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 03:47:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50C3A16A4CF; Thu, 20 Jan 2005 03:47:59 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC01E43D1F; Thu, 20 Jan 2005 03:47:57 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id IALJW000.2AS; Wed, 19 Jan 2005 19:48:00 -0800 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2005011919505908873 ; Wed, 19 Jan 2005 19:50:59 -0800 From: "Vinod Kashyap" To: Michael Meltzer Date: Wed, 19 Jan 2005 19:47:45 -0800 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=-------797c823797c823 Message-ID: cc: freebsd stable cc: Jean-Yves Avenard cc: freebsd-amd64@freebsd.org cc: freebsd-scsi@FreeBSD.org Subject: RE: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 20 Jan 2005 03:47:59 -0000 This is a multi-part message in MIME format ---------797c823797c823 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Strange... CAM doesn't seem to be sending down inquiries to the twa driver, although it was requested to do so (twa_request_bus_scan). I have seen this kind of behavior on 5.x, when doing kldload of the driver, and when logical units are created/deleted on the fly. Although the SIM (twa) requests for a bus scan, CAM never sends down inquiries, and the logical units underneath don't get detected. This behavior is not consistent, and happens some times only. However, I have never seen a case where CAM fails to send inquiries when twa is integrated into the kernel. Do any CAM experts know what might be happening? Also strange is the fact that twa of 5.3-RELEASE works fine. In the attached patch, I have tried to revert back to the way XPT_PATH_INQ is handled by twa of 5.3-RELEASE. Could you apply it to RELENG_5 and let me know the results? > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of Michael Meltzer > Sent: Tuesday, January 18, 2005 9:47 PM > To: Vinod Kashyap > Cc: Jean-Yves Avenard > Subject: Re: twa breakage on AMD64 > with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit > = > = > twa_patch2.diff, had to add the "int error; in twa_alloc_req_pkts > = > -mjm > = > = > = > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, = > 1993, 1994 > The Regents of the University of California. All = > rights reserved. > FreeBSD 5.3-STABLE #17: Wed Jan 19 00:44:33 EST 2005 > root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0xf51 Stepping =3D 1 > = > Features=3D0x78bfbff ,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > AMD Features=3D0xe0500800 > real memory =3D 6442450944 (6144 MB) > avail memory =3D 5963784192 (5687 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-27 on motherboard > ioapic2 irqs 28-31 on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > unknown: I/O range not supported > unknown: I/O range not supported > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > twa_probe: entered > pcib1: at device 6.0 on pci0 > pci1: on pcib1 > twa_probe: entered > pci1: at device 6.0 (no driver attached) > twa_probe: entered > isab0: at device 7.0 on pci0 > isa0: on isab0 > twa_probe: entered > atapci0: port > 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device = > 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > twa_probe: entered > pci0: at device 7.2 (no driver attached) > twa_probe: entered > pci0: at device 7.3 (no driver attached) > twa_probe: entered > pcib2: at device 10.0 on pci0 > pci2: on pcib2 > twa_probe: entered > bge0: mem > 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:50:45:5b:8e:76 > twa_probe: entered > bge1: mem > 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: Ethernet address: 00:50:45:5b:8e:77 > twa_probe: entered > atapci1: port > 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem > 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device = > 5.0 on pci2 > atapci1: failed: rid 0x20 is memory, requested 4 > ata2: channel #0 on atapci1 > ata3: channel #1 on atapci1 > ata4: channel #2 on atapci1 > ata5: channel #3 on atapci1 > twa_probe: entered > pci0: at device 10.1 = > (no driver > attached) > twa_probe: entered > pcib3: at device 11.0 on pci0 > pci3: on pcib3 > twa_probe: entered > 3ware device driver for 9000 series storage controllers, version: > 2.50.02.011 > twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem > 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device = > 2.0 on pci3 > unknown: twa_attach: entered. > twa0: [GIANT-LOCKED] > twa0: twa_setup: entered. > twa0: twa_setup_request_dmamap: entered. > twa0: twa_setup_request_dmamap: error =3D 0, segs[0].addr =3D = > 17f2da000, len > =3D 40000 > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_release_request: entered. > twa0: twa_init_ctlr: entered. > twa0: twa_wait_status: entered. > twa0: twa_drain_response_queue: entered. > twa0: twa_init_connection: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: twa_get_request: entered. > twa0: twa_execute_scsi: SCSI I/O request 0x3 > twa0: twa_execute_scsi: XPT_SCSI_IO: Single virtual address! > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_enqueue_aen: entered. > twa0: twa_enqueue_aen: AEN queue empty > twa0: twa_release_request: entered. > twa0: twa_init_ctlr: exiting. > twa0: twa_describe_controller: entered. > twa0: twa_get_param: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: twa_get_param: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: twa_get_param: entered. > twa0: twa_get_request: entered. > twa0: twa_immediate_request: entered. > twa0: twa_map_request: entered. > twa0: twa_setup_data_dmamap: entered. > twa0: twa_start: entered. > twa0: twa_done: entered. > twa0: twa_drain_complete_queue: entered. > twa0: twa_unmap_request: entered. > twa0: twa_unmap_request: entered. > twa0: twa_release_request: entered. > twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 > twa0: twa_cam_setup: sc =3D 0xffffffff8082f000 > twa0: twa_cam_setup: Calling cam_sim_alloc > twa0: twa_cam_setup: Calling xpt_bus_register > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_cam_setup: Calling xpt_create_path > twa0: twa_cam_setup: Calling xpt_setup_ccb > twa0: twa_cam_setup: Calling twa_request_bus_scan > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_cam_setup: Exiting > twa_probe: entered > pci0: at device 11.1 = > (no driver > attached) > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > twa_probe: entered > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse, device ID 3 > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 = > drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 = > flags 0x10 on > acpi0 > sio0: type 16550A, console > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > ppc0: port = > 0x778-0x77f,0x378-0x37f irq 7 drq > 4 on acpi0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppbus0: on ppc0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > orm0: at iomem > 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7ff > f on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x100> > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: at port 0x3c0-0x3df iomem = > 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > IP Filter: v3.4.35 initialized. Default =3D pass all, Logging = > =3D disabled > twa0: twa_interrupt: entered. > twa_bus_scan_cb: ccb =3D 0xffffff017f236800 > = > twa_bus_scan_cb: success > acd0: DVDROM at ata0-master UDMA33 > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > twa0: twa_action: XPT_PATH_INQ request > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/da0s1a > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > = > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0a > ? List valid disk boot devices > Abort manual input > = > mountroo > = > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = > "freebsd-stable-unsubscribe@freebsd.org" > ---------797c823797c823 Content-Type: application/octet-stream; name="twa_patch3.diff" Content-Disposition: attachment; filename="twa_patch3.diff" Content-Transfer-Encoding: base64 SW5kZXg6IHR3YV9jYW0uYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvaG9tZS9uY3ZzL3Ny Yy9zeXMvZGV2L3R3YS90d2FfY2FtLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMy4yLjEK ZGlmZiAtdSAtcjEuMy4yLjEgdHdhX2NhbS5jCi0tLSB0d2FfY2FtLmMJMTEgSmFuIDIwMDUg MDM6MDA6NDggLTAwMDAJMS4zLjIuMQorKysgdHdhX2NhbS5jCTIwIEphbiAyMDA1IDAzOjI2 OjM1IC0wMDAwCkBAIC00MDksOSArNDA5LDkgQEAKIAkJdHdhX2RiZ19kcHJpbnQoMywgc2Ms ICJYUFRfUEFUSF9JTlEgcmVxdWVzdCIpOwogCiAJCXBhdGhfaW5xLT52ZXJzaW9uX251bSA9 IDE7Ci0JCXBhdGhfaW5xLT5oYmFfaW5xdWlyeSA9IFBJX1dJREVfMTY7CisJCXBhdGhfaW5x LT5oYmFfaW5xdWlyeSA9IDA7CiAJCXBhdGhfaW5xLT50YXJnZXRfc3BydCA9IDA7Ci0JCXBh dGhfaW5xLT5oYmFfbWlzYyB8PSBQSU1fTk9CVVNSRVNFVDsKKwkJcGF0aF9pbnEtPmhiYV9t aXNjID0gMDsKIAkJcGF0aF9pbnEtPmhiYV9lbmdfY250ID0gMDsKIAkJcGF0aF9pbnEtPm1h eF90YXJnZXQgPSBUV0FfTUFYX1VOSVRTOwogCQlwYXRoX2lucS0+bWF4X2x1biA9IDA7Cklu ZGV4OiB0d2FfZnJlZWJzZC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMv c3JjL3N5cy9kZXYvdHdhL3R3YV9mcmVlYnNkLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEu Ny4yLjIKZGlmZiAtdSAtcjEuNy4yLjIgdHdhX2ZyZWVic2QuYwotLS0gdHdhX2ZyZWVic2Qu YwkxMSBKYW4gMjAwNSAwMzowMDo0OCAtMDAwMAkxLjcuMi4yCisrKyB0d2FfZnJlZWJzZC5j CTIwIEphbiAyMDA1IDAzOjI2OjM1IC0wMDAwCkBAIC0yNjEsMTUgKzI2MSw2IEBACiAJc2Mt PnR3YV9idXNfdGFnID0gcm1hbl9nZXRfYnVzdGFnKHNjLT50d2FfaW9fcmVzKTsKIAlzYy0+ dHdhX2J1c19oYW5kbGUgPSBybWFuX2dldF9idXNoYW5kbGUoc2MtPnR3YV9pb19yZXMpOwog Ci0JLyogSW5pdGlhbGl6ZSB0aGUgZHJpdmVyIGZvciB0aGlzIGNvbnRyb2xsZXIuICovCi0J aWYgKChlcnJvciA9IHR3YV9zZXR1cChzYykpKSB7Ci0JCXR3YV9mcmVlKHNjKTsKLQkJcmV0 dXJuKGVycm9yKTsKLQl9Ci0KLQkvKiBQcmludCBzb21lIGluZm9ybWF0aW9uIGFib3V0IHRo ZSBjb250cm9sbGVyIGFuZCBjb25maWd1cmF0aW9uLiAqLwotCXR3YV9kZXNjcmliZV9jb250 cm9sbGVyKHNjKTsKLQogCS8qIEFsbG9jYXRlIGFuZCBjb25uZWN0IG91ciBpbnRlcnJ1cHQu ICovCiAJcmVzX2lkID0gMDsKIAlpZiAoKHNjLT50d2FfaXJxX3JlcyA9IGJ1c19hbGxvY19y ZXNvdXJjZShzYy0+dHdhX2J1c19kZXYsIFNZU19SRVNfSVJRLApAQCAtMjg2LDYgKzI3Nywx NSBAQAogCQlyZXR1cm4oRU5YSU8pOwogCX0KIAorCS8qIEluaXRpYWxpemUgdGhlIGRyaXZl ciBmb3IgdGhpcyBjb250cm9sbGVyLiAqLworCWlmICgoZXJyb3IgPSB0d2Ffc2V0dXAoc2Mp KSkgeworCQl0d2FfZnJlZShzYyk7CisJCXJldHVybihlcnJvcik7CisJfQorCisJLyogUHJp bnQgc29tZSBpbmZvcm1hdGlvbiBhYm91dCB0aGUgY29udHJvbGxlciBhbmQgY29uZmlndXJh dGlvbi4gKi8KKwl0d2FfZGVzY3JpYmVfY29udHJvbGxlcihzYyk7CisKIAkvKiBDcmVhdGUg dGhlIGNvbnRyb2wgZGV2aWNlLiAqLwogCXNjLT50d2FfY3RybF9kZXYgPSBtYWtlX2Rldigm dHdhX2NkZXZzdywgZGV2aWNlX2dldF91bml0KHNjLT50d2FfYnVzX2RldiksCiAJCQkJCVVJ RF9ST09ULCBHSURfT1BFUkFUT1IsIFNfSVJVU1IgfCBTX0lXVVNSLApAQCAtNTQzLDYgKzU0 Myw3IEBACiB7CiAJc3RydWN0IHR3YV9yZXF1ZXN0CSp0cjsKIAlpbnQJCQlpOworCWludAkJ CWVycm9yOwogCiAJaWYgKChzYy0+dHdhX3JlcV9idWYgPSBtYWxsb2MobnVtX3JlcXMgKiBz aXplb2Yoc3RydWN0IHR3YV9yZXF1ZXN0KSwKIAkJCQkJVFdBX01BTExPQ19DTEFTUywgTV9O T1dBSVQpKSA9PSBOVUxMKQpAQCAtNTk1LDEwICs1OTYsMTIgQEAKIAkJcmV0dXJuKEVOT01F TSk7CiAJfQogCi0JYnVzX2RtYW1hcF9sb2FkKHNjLT50d2FfY21kX3RhZywgc2MtPnR3YV9j bWRfbWFwLAorCWlmICgoZXJyb3IgPSBidXNfZG1hbWFwX2xvYWQoc2MtPnR3YV9jbWRfdGFn LCBzYy0+dHdhX2NtZF9tYXAsCiAJCQkJc2MtPnR3YV9jbWRfcGt0X2J1ZiwKIAkJCQludW1f cmVxcyAqIHNpemVvZihzdHJ1Y3QgdHdhX2NvbW1hbmRfcGFja2V0KSwKLQkJCQl0d2Ffc2V0 dXBfcmVxdWVzdF9kbWFtYXAsIHNjLCAwKTsKKwkJCQl0d2Ffc2V0dXBfcmVxdWVzdF9kbWFt YXAsIHNjLCBCVVNfRE1BX05PV0FJVCkpKSB7CisJCXR3YV9wcmludGYoc2MsICJidXNfZG1h bWFwX2xvYWQgcmV0dXJuZWQgJWRcbiIsIGVycm9yKTsKKwl9CiAJYnplcm8oc2MtPnR3YV9y ZXFfYnVmLCBudW1fcmVxcyAqIHNpemVvZihzdHJ1Y3QgdHdhX3JlcXVlc3QpKTsKIAliemVy byhzYy0+dHdhX2NtZF9wa3RfYnVmLAogCQkJbnVtX3JlcXMgKiBzaXplb2Yoc3RydWN0IHR3 YV9jb21tYW5kX3BhY2tldCkpOwpAQCAtNzcwLDYgKzc3Myw4IEBACiAJc3RydWN0IHR3YV9z b2Z0Ywkqc2MgPSAoc3RydWN0IHR3YV9zb2Z0YyAqKWFyZzsKIAogCXR3YV9kYmdfZHByaW50 X2VudGVyKDEwLCBzYyk7CisJdHdhX2RiZ19kcHJpbnQoMywgc2MsICJlcnJvciA9ICVkLCBz ZWdzWzBdLmFkZHIgPSAlbHgsIGxlbiA9ICVseCIsCisJCWVycm9yLCBzZWdzWzBdLmRzX2Fk ZHIsIHNlZ3NbMF0uZHNfbGVuKTsKIAogCXNjLT50d2FfY21kX3BrdF9waHlzID0gc2Vnc1sw XS5kc19hZGRyOwogfQo= ---------797c823797c823-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 08:46:14 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4497F16A4CE for ; Thu, 20 Jan 2005 08:46:14 +0000 (GMT) Received: from hermes.hw.ru (hermes.hw.ru [80.68.240.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A7BB43D5E for ; Thu, 20 Jan 2005 08:46:13 +0000 (GMT) (envelope-from anbs@rbc.ru) Received: from [80.68.240.83] (HELO smtp.rbc.ru) by hermes.hw.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 69303615 for freebsd-amd64@FreeBSD.org; Thu, 20 Jan 2005 11:46:11 +0300 Received: from goover.rbc.ru (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E3CF139044 for ; Thu, 20 Jan 2005 11:46:10 +0300 (MSK) Received: by smtp.rbc.ru (Postfix, from userid 501) id DA4673904A; Thu, 20 Jan 2005 11:46:10 +0300 (MSK) Received: from anbswork (unknown [80.68.244.199]) by smtp.rbc.ru (Postfix) with SMTP id BE2B539044 for ; Thu, 20 Jan 2005 11:46:10 +0300 (MSK) Message-ID: <000901c4fecc$7e24f030$c7f44450@users.rbc.ru> From: "Andrey B Semakin" To: Date: Thu, 20 Jan 2005 11:46:11 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-SpamTest-Info: Profile: Formal (197/050118) X-SpamTest-Info: Profile: Detect Standard No RBL (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking Spam - Subject (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0125], KAS/Release Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: sysctl 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, 20 Jan 2005 08:46:14 -0000 Could not set vm.max_proc_mmap over 2Gb Resource limits (current): cputime infinity secs filesize infinity kb datasize 33554432 kb stacksize 524288 kb coredumpsize infinity kb memoryuse infinity kb memorylocked infinity kb maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kb FreeBSD 5.3-STABLE Andrey Semakin From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 08:46:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A921E16A4CE for ; Thu, 20 Jan 2005 08:46:59 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D84F43D62 for ; Thu, 20 Jan 2005 08:46:59 +0000 (GMT) (envelope-from ccnp.bsd@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so69665rnf for ; Thu, 20 Jan 2005 00:46:58 -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:mime-version:content-type:content-transfer-encoding; b=ei8+0bb1NdaZYubGgqMmUMB/gtbCbjp+UahqMoosPEKIA/paYP3wz8SN7Std5480fBNJxs8QWZ++i8Y0A0x1txIYYwxzZw+AOtOwRTjfpFby3l19MFSx2zX0YvCGF+DTCzzukJNisoBVQRA2dVzYo37GpU/THAM5OYdOu5jk5lw= Received: by 10.38.11.55 with SMTP id 55mr159322rnk; Thu, 20 Jan 2005 00:46:58 -0800 (PST) Received: by 10.38.208.42 with HTTP; Thu, 20 Jan 2005 00:46:58 -0800 (PST) Message-ID: Date: Thu, 20 Jan 2005 02:46:58 -0600 From: Nick Lozinsky To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FreeBSD-STABLE/amd64 DWL-650 ath & ath_hal compile error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nick Lozinsky List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 08:46:59 -0000 Greetings, I have included: device ath device ath_hal to my kernel, and when attempting to `make', it fails with: linking kernel ah_osdep.o(.text+0x157): In function `ath_hal_modevent': : undefined reference to `ath_hal_version' ah_osdep.o(.data+0x1b8): undefined reference to `ath_hal_version' *** Error code 1 I've googled for over a week, with no solution. According to `man ath' and `man ath_hal', this is the proper procedure to create the `ath' device. My reason for doing this, is to get the Dlink DWL-650 RevP PCCard to function on my Gateway 7405GX AMD64; It also has a built in Broadcom 802.11g WiFi NIC, and I have attempted to use the NDIS wrapper, but without any luck, meaning, erroring out at loading the proper modules (i.e. `if_ndis.ko', etc.) Please advice on the next step. Nick Lozinsky From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 09:08:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D03C16A4CE for ; Thu, 20 Jan 2005 09:08:37 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F74343D46 for ; Thu, 20 Jan 2005 09:08:37 +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 j0K9D2ig007872; Thu, 20 Jan 2005 01:13:02 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0K9D2E0007871; Thu, 20 Jan 2005 01:13:02 -0800 Date: Thu, 20 Jan 2005 01:13:02 -0800 From: Brooks Davis To: Nick Lozinsky Message-ID: <20050120091302.GA5825@odin.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: 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: FreeBSD-STABLE/amd64 DWL-650 ath & ath_hal compile error 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, 20 Jan 2005 09:08:37 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 02:46:58AM -0600, Nick Lozinsky wrote: > Greetings, >=20 > I have included: >=20 > device ath > device ath_hal >=20 > to my kernel, and when attempting to `make', it fails with: >=20 > linking kernel > ah_osdep.o(.text+0x157): In function `ath_hal_modevent': > : undefined reference to `ath_hal_version' > ah_osdep.o(.data+0x1b8): undefined reference to `ath_hal_version' > *** Error code 1 >=20 > I've googled for over a week, with no solution. According to `man ath' > and `man ath_hal', this is the proper procedure to create the `ath' > device. My reason for doing this, is to get the Dlink DWL-650 RevP > PCCard to function on my Gateway 7405GX AMD64; It also has a built in > Broadcom 802.11g WiFi NIC, and I have attempted to use the NDIS > wrapper, but without any luck, meaning, erroring out at loading the > proper modules (i.e. `if_ndis.ko', etc.) What version of FreeBSD are you using? I don't think there's a hal binary for amd64 in 5.x. -- 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 --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB73YdXY6L6fI4GtQRAsO8AJ410BlwAjsMrlxIyG7XOp//Ur9c4wCfc2o8 iQCAmBOOjtGPGlP65a0NVHU= =30ZW -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 11:18:23 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80DD716A4CE for ; Thu, 20 Jan 2005 11:18:23 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79FA943D45 for ; Thu, 20 Jan 2005 11:18:22 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.0.61] (elrond.private.hydrix.com [192.168.0.61]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0KBIDoV089139 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Thu, 20 Jan 2005 22:18:14 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: <339AB484-6942-11D9-8858-000D93AD5C52@hydrix.com> References: <339AB484-6942-11D9-8858-000D93AD5C52@hydrix.com> 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: Thu, 20 Jan 2005 22:17:54 +1100 To: Vinod Kashyap , Michael Meltzer 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/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean cc: freebsd-amd64@FreeBSD.org Subject: Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 20 Jan 2005 11:18:23 -0000 Hello Ok it went a little bit further with your new patch (ver3) Now it displays: twa_probe: entered 3ware device driver for 9000 series storage controllers, version 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x8800-0x88ff mem 0xfb800000-xfbffffff,0xfc5ffc00-0xfc5ffcff irq 29 at device 1.0 on pci1 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 3d62e000, len = 40000 then it hangs. I'm stil lwondering how you guys get the boot print in your email, I have to copy them by hand which takes forever I tried the Control Alt Escape key combination (direct keyboard access, no console here) without any success. Cheers Jean-Yves On 18/01/2005, at 10:15 PM, Jean-Yves Avenard wrote: > Ok.. > > I don't know how to get a file from what I see on the screen so I'll > copy it by hand: > > twa_probe: entered > 3ware device driver for 9000 series storage controllers, version > 2.50.02.011 > twa0: <3ware 9000 series Storage Controller> port 0x9800-0x98ff mem > 0xfb800000-xfbffffff,0xfc6ffc00-0xfc6ffcff irq 29 at device 1.0 on > pci1 > unknown: twa_attach: entered. > twa0: twa_setup: entered. > twa0: twa_setup_request_dmamap: entered. > > From there it hangs nothing else will be displayed > > Now I type Control-Alt-Esc > and it does.... absolutely nothing > > In my kernel config file I have: > # My options > options COMPAT_43 > options COMPAT_LINUX32 > options LINPROCFS > > options TWA_FLASH_FIRMWARE > options TWA_DEBUG=10 > > options KDB > options DDB > > Jean-Yves > > On 18/01/2005, at 7:08 AM, Vinod Kashyap wrote: > >> >> One more thing. When you enter the kernel debugger, please do a >> 'call twa_report', and let me know what gets printed. >> >> >>> -----Original Message----- >>> From: Vinod Kashyap [mailto:vkashyap@amcc.com] >>> Sent: Monday, January 17, 2005 12:04 PM >>> To: Jean-Yves Avenard; Michael Meltzer >>> Subject: RE: twa breakage on AMD64 with >>> 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit >>> >>> >>> >>> Could you add 'options TWA_DEBUG=10' to the kernel config file? >>> This will make the driver print a lot of debug messages, which >>> might be helpful. >>> >>> Also, you might want to try adding 'options KDB' and 'options DDB' >>> to the kernel config file, and if you experience a hang, press >>> Ctrl+Alt+Esc to enter the debugger, and do a 'tr,20' which >>> might indicate where the system is hanging. >>> >>> >>>> -----Original Message----- >>>> From: owner-freebsd-stable@freebsd.org >>>> [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of >>>> Jean-Yves Avenard >>>> Sent: Sunday, January 16, 2005 2:45 AM >>>> To: Vinod Kashyap >>>> Cc: freebsd stable >>>> Subject: Re: twa breakage on AMD64 with >>>> 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit >>>> >>>> >>>> Hello >>>> >>>> On 15/01/2005, at 12:40 PM, Vinod Kashyap wrote: >>>> >>>>> >>>>> Could you give the attached patch a try? Just a hunch... >>>>> >>>> >>>> I did... same behavior. it just hangs right after >>> displaying the twa0 >>>> line. >>>> >>>> Actually, hangs is incorrect. As I had to drive to the office >>>> to reload >>>> a previous kernel (never, ever rely on nextboot my friends!) >>>> When I got there I saw that it went a little bit further, >>> so it seems >>>> that it doesn't just hang... it is just very very slow >>>> >>>> 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 >>>> >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to >>>> "freebsd-stable-unsubscribe@freebsd.org" >>>> >>> >> >> >> > --- > 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 > > --- 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 Jan 20 13:28:23 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC70B16A4CE; Thu, 20 Jan 2005 13:28:23 +0000 (GMT) Received: from web4.thecenturiongroup.com (fw14.delivery.com [67.102.42.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEFF343D1F; Thu, 20 Jan 2005 13:28:20 +0000 (GMT) (envelope-from mjm@michaelmeltzer.com) Received: from [127.0.0.1] (ix1x1000.thecenturiongroup.com [192.32.248.52]) by web4.thecenturiongroup.com (Postfix) with ESMTP id 40A187C008; Thu, 20 Jan 2005 08:28:20 -0500 (EST) Message-ID: <41EFB111.8010906@michaelmeltzer.com> Date: Thu, 20 Jan 2005 08:24:33 -0500 From: Michael Meltzer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd stable cc: Jean-Yves Avenard cc: freebsd-amd64@freebsd.org cc: freebsd-scsi@FreeBSD.org Subject: Re: twa breakage on AMD64with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 20 Jan 2005 13:28:24 -0000 looks like patch3 worked, good job! I had to turn off TWA_DEBUG to get the boot going, the debug was starving the boot on a 9600 baud terminal. I can increase the speed and caputer the output on monday if it will help(it on the large side, bigger than the 10,000 line capture buffer in am using). I incude 2 iozone reports, the first one the new driver the second one the old driver, Is thier a way to increase the "read ahead" in freebsd?? -mjm iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Iozone: Performance Test of File I/O Version $Revision: 3.196 $ Compiled for 64 bit mode. Build: freebsd Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Jean-Marc Zucconi, Jeff Blomberg. Run began: Thu Jan 20 07:45:52 2005 File size set to 20971520 KB Record Size 60 KB Command line used: iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Output is in Kbytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 Kbytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. Throughput test with 1 process Each process writes a 20971520 Kbyte file in 60 Kbyte records Children see throughput for 1 initial writers = 78219.47 KB/sec Parent sees throughput for 1 initial writers = 78060.45 KB/sec Min throughput per process = 78219.47 KB/sec Max throughput per process = 78219.47 KB/sec Avg throughput per process = 78219.47 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 rewriters = 19394.53 KB/sec Parent sees throughput for 1 rewriters = 19394.32 KB/sec Min throughput per process = 19394.53 KB/sec Max throughput per process = 19394.53 KB/sec Avg throughput per process = 19394.53 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 readers = 55960.09 KB/sec Parent sees throughput for 1 readers = 55954.25 KB/sec Min throughput per process = 55960.09 KB/sec Max throughput per process = 55960.09 KB/sec Avg throughput per process = 55960.09 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 re-readers = 55948.26 KB/sec Parent sees throughput for 1 re-readers = 55946.60 KB/sec Min throughput per process = 55948.26 KB/sec Max throughput per process = 55948.26 KB/sec Avg throughput per process = 55948.26 KB/sec Min xfer = 20971500.00 KB iozone test complete. iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Iozone: Performance Test of File I/O Version $Revision: 3.196 $ Compiled for 64 bit mode. Build: freebsd Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Jean-Marc Zucconi, Jeff Blomberg. Run began: Mon Dec 20 21:03:36 2004 File size set to 20971520 KB Record Size 60 KB Command line used: iozone -s 20480m -r 60 -i 0 -i 1 -t 1 Output is in Kbytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 Kbytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. Throughput test with 1 process Each process writes a 20971520 Kbyte file in 60 Kbyte records Children see throughput for 1 initial writers = 78738.67 KB/sec Parent sees throughput for 1 initial writers = 78716.55 KB/sec Min throughput per process = 78738.67 KB/sec Max throughput per process = 78738.67 KB/sec Avg throughput per process = 78738.67 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 rewriters = 32126.46 KB/sec Parent sees throughput for 1 rewriters = 32125.77 KB/sec Min throughput per process = 32126.46 KB/sec Max throughput per process = 32126.46 KB/sec Avg throughput per process = 32126.46 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 readers = 58563.70 KB/sec Parent sees throughput for 1 readers = 58557.14 KB/sec Min throughput per process = 58563.70 KB/sec Max throughput per process = 58563.70 KB/sec Avg throughput per process = 58563.70 KB/sec Min xfer = 20971500.00 KB Children see throughput for 1 re-readers = 58583.77 KB/sec Parent sees throughput for 1 re-readers = 58581.98 KB/sec Min throughput per process = 58583.77 KB/sec Max throughput per process = 58583.77 KB/sec Avg throughput per process = 58583.77 KB/sec Min xfer = 20971500.00 KB iozone test complete. Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #21: Thu Jan 20 01:21:10 EST 2005 root@web7.thecenturiongroup.com:/usr/src/sys/amd64/compile/web7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf51 Stepping = 1 Features=0x78bfbff AMD Features=0xe0500800 real memory = 6442450944 (6144 MB) avail memory = 5964316672 (5688 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 pci1: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 bge0: mem 0xfd000000-0xfd00ffff irq 27 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 bge1: mem 0xfd010000-0xfd01ffff irq 27 at device 4.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 atapci1: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd020000-0xfd03ffff,0xfd040000-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci3: on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: <3ware 9000 series Storage Controller> port 0x4000-0x40ff mem 0xfd800000-0xfdffffff,0xfd100000-0xfd1000ff irq 30 at device 2.0 on pci3 twa0: [GIANT-LOCKED] twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 pci0: at device 11.1 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled acd0: DVDROM at ata0-master UDMA33 da0 at twa0 bus 0 target 0 lun 0 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device da0: 100.000MB/s transfers da0: 70550MB (144486400 512 byte sectors: 255H 63S/T 8993C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/da0s1b as swap device Starting file system checks: /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1a: clean, 3005287 free (1559 frags, 375466 blocks, 0.1% fragmentation) /dev/da0s1h: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1h: clean, 15168492 free (20 frags, 1896059 blocks, 0.0% fragmentation) /dev/da0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1g: clean, 5010318 free (56766 frags, 619194 blocks, 0.9% fragmentation) /dev/da0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1f: clean, 6078377 free (553 frags, 759728 blocks, 0.0% fragmentation) Enabling ipfilter. ioctl(SIOCIPFL6): Invalid argument Setting hostname: web7.thecenturiongroup.com. Installing NAT rules. 0 entries flushed from NAT table 0 entries flushed from NAT list bge0: flags=8843 mtu 1500 options=1a inet 192.32.248.84 netmask 0xffffff00 broadcast 192.32.248.255 ether 00:50:45:5b:8e:76 media: Ethernet autoselect (none) status: no carrier bge1: flags=8843 mtu 1500 options=1a inet 10.200.0.7 netmask 0xffffff00 broadcast 10.200.0.255 ether 00:50:45:5b:8e:77 media: Ethernet autoselect (none) status: no carrier lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 filter sync'd add net default: gateway 10.200.0.1 Additional routing options: IP gateway=YES. Starting devd. Mounting NFS file systems:. Starting syslogd. Jan 20 01:24:35 web7 syslogd: kernel boot file is /boot/kernel/kernel ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib Starting usbd. No USB host controllers found Starting local daemons:. Updating motd. Starting ntpd. Jan 20 01:24:35 web7 ntpd[393]: no IPv6 interfaces found Configuring syscons: blanktime screensaver. Starting sshd. Initial amd64 initialization:. Additional ABI support:. Starting cron. Local package initialization:. Additional TCP options:. Starting moused:. Starting inetd. Starting background file system checks in 60 seconds. Thu Jan 20 01:24:36 EST 2005 FreeBSD/amd64 (web7.thecenturiongroup.com) (ttyd0) login: Jan 20 01:24:43 web7 ntpd[393]: sendto(139.88.35.33): No route to host Jan 20 01:24:44 web7 ntpd[393]: sendto(208.184.49.9): No route to host Jan 20 01:24:45 web7 ntpd[393]: sendto(216.200.93.8): No route to host FreeBSD/amd64 (web7.thecenturiongroup.com) (ttyd0) login: From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 14:59:32 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51CB216A4CE for ; Thu, 20 Jan 2005 14:59:32 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id B684C43D55 for ; Thu, 20 Jan 2005 14:59:31 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so21829rne for ; Thu, 20 Jan 2005 06:59:31 -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=uAqj15Vddo78KXwiucbJRSuCht3eyQn6uhCtIJXN/QIjm3clZ79M147qxE9I9yGiR9h2Jasvtm+9YJZ+fdTMZMXpOnyWKZQS9BbeBx5j+Ag5iC7wq4sTTEE6eNNaWrPLtpcIsx51chRFnHp9MAXSy/aLpkbDG2B0MDCb1Jxhy+Y= Received: by 10.38.153.46 with SMTP id a46mr178260rne; Thu, 20 Jan 2005 06:59:31 -0800 (PST) Received: by 10.38.22.76 with HTTP; Thu, 20 Jan 2005 06:59:30 -0800 (PST) Message-ID: <346a802205012006592d9e3870@mail.gmail.com> Date: Thu, 20 Jan 2005 09:59:30 -0500 From: Coleman Kane To: Brooks Davis In-Reply-To: <20050120091302.GA5825@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050120091302.GA5825@odin.ac.hmc.edu> cc: Nick Lozinsky cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD-STABLE/amd64 DWL-650 ath & ath_hal compile error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 14:59:32 -0000 The amd64 hal module doesn't exist in 5-stable. I happen to have a Gateway 7422GX, and am running the latest -CURRENT prefectly fine. The ath and ath_hal in -CURRENT are newer versions that sam recently imported. The wlan framework in -CURRENT has also gone through a number of changes (namely to support WPA, et. al.), and so a simple back-copy of the driver won't work without some huge effort. Anyhow, sam has comitted my patch to get the ath_hal to build for amd64, since it works on this laptop (very well I might add). Pull down -current and work from there, that's my advice. It seems more stable and feature-full than 5-stable anyhow for this platform. Keep an eye on freebsd-amd64 to be aware of -current breakage later on. NDIS wrapper doesn't work yet on amd64. The broadcom chip bites anyhow. I've got an SMC 2536W-AG EliteConnect which supports the a,b,g modes as well as something called 'turbo' mode. -- coleman kane On Thu, 20 Jan 2005 01:13:02 -0800, Brooks Davis wrote: > On Thu, Jan 20, 2005 at 02:46:58AM -0600, Nick Lozinsky wrote: > > Greetings, > > > > I have included: > > > > device ath > > device ath_hal > > > > to my kernel, and when attempting to `make', it fails with: > > > > linking kernel > > ah_osdep.o(.text+0x157): In function `ath_hal_modevent': > > : undefined reference to `ath_hal_version' > > ah_osdep.o(.data+0x1b8): undefined reference to `ath_hal_version' > > *** Error code 1 > > > > I've googled for over a week, with no solution. According to `man ath' > > and `man ath_hal', this is the proper procedure to create the `ath' > > device. My reason for doing this, is to get the Dlink DWL-650 RevP > > PCCard to function on my Gateway 7405GX AMD64; It also has a built in > > Broadcom 802.11g WiFi NIC, and I have attempted to use the NDIS > > wrapper, but without any luck, meaning, erroring out at loading the > > proper modules (i.e. `if_ndis.ko', etc.) > > What version of FreeBSD are you using? I don't think there's a hal > binary for amd64 in 5.x. > > -- Brooks > > -- > 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 > > > From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 16:12:05 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B21D16A4CF for ; Thu, 20 Jan 2005 16:12:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02BAD43D2F for ; Thu, 20 Jan 2005 16:12:05 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so3017wri for ; Thu, 20 Jan 2005 08:12:04 -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=i3po18Kd675+Qj+uifF2TuVIUL0uXxUg1bjjXVrT5LjQoPcnGSeWm4ayUirNw8RbJBvouwQqVjKD8tW2Wai2OlkZUF1X1H6QnheW2VUy9g6YriYVNLakQ7ITKLZDlK+1IMDJIftMcwxlBSIYAivr+UdeVAGpAMlVhDw2lqRrpu4= Received: by 10.54.46.68 with SMTP id t68mr262863wrt; Thu, 20 Jan 2005 08:12:04 -0800 (PST) Received: by 10.54.29.4 with HTTP; Thu, 20 Jan 2005 08:12:04 -0800 (PST) Message-ID: <790a9fff050120081229a3ec6a@mail.gmail.com> Date: Thu, 20 Jan 2005 10:12:04 -0600 From: Scot Hetzel To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org In-Reply-To: <20050119214229.GE1168@manor.msen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050119214229.GE1168@manor.msen.com> Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 16:12:05 -0000 On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne wrote: > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another > suggested procedure? > When I have a bad kernel I do the following after booting the good kernel. cd /boot rm -rf kernel cp -rp kernel.old kernel cp -rp kernel.old kernel.good This way I can reboot the box without going into the loader to load kernel.old. Scot From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 16:36:21 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 811D416A4CE for ; Thu, 20 Jan 2005 16:36:21 +0000 (GMT) Received: from mail.freebsd.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 065D443D2F for ; Thu, 20 Jan 2005 16:36:19 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 98278 invoked by uid 0); 20 Jan 2005 16:28:25 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.99.7) by mail.freebsd.org.cn with SMTP; 20 Jan 2005 16:28:25 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id EE4E11335C0; Fri, 21 Jan 2005 00:36:10 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44853-14; Fri, 21 Jan 2005 00:35:59 +0800 (CST) Received: from localhost.localdomain (unknown [61.48.135.6]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by beastie.frontfree.net (Postfix) with ESMTP id B8552133598; Fri, 21 Jan 2005 00:35:57 +0800 (CST) From: Xin LI To: "Michael R. Wayne" In-Reply-To: <20050119214229.GE1168@manor.msen.com> References: <20050119214229.GE1168@manor.msen.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NZ7y5Bhvmo3DnfIk7N+N" Organization: The FreeBSD Simplified Chinese Project Date: Fri, 21 Jan 2005 00:34:42 +0800 Message-Id: <1106238882.1019.48.camel@spirit> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at frontfree.net cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: delphij@delphij.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 16:36:21 -0000 --=-NZ7y5Bhvmo3DnfIk7N+N Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Michael, =E5=9C=A8 2005-01-19=E4=B8=89=E7=9A=84 16:42 -0500=EF=BC=8CMichael R. Wayne= =E5=86=99=E9=81=93=EF=BC=9A > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another=20 > suggested procedure? I personally do: cp -R /boot/kernel /boot/kernel.good If the kernel has provided stability for 30 days. For your case, you may want to do: cp -R /boot/kernel.old /boot/kernel.good since the kernel.old is last known good kernel. Of course kernel.save is a good name. For a STABLE branch you generally won't need to fear that loader changes can prevent you from being able to boot from older kernels. Therefore, I think the procedure you have listed is enough to do. Cheers, --=20 Xin LI http://www.delphij.net/ --=-NZ7y5Bhvmo3DnfIk7N+N Content-Type: application/pgp-signature; name=signature.asc Content-Description: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=BF=A1=E4=BB=B6=E7=9A=84=E6=95=B0?= =?UTF-8?Q?=E5=AD=97=E7=AD=BE=E5=90=8D=E9=83=A8?= =?UTF-8?Q?=E5=88=86?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB792i/cVsHxFZiIoRAmPyAJ0c5XWM/RuUgYSLU+RMmsj/iMFLPgCfQp3Q xqgIceP0t6xDmtNxE1RAac4= =9iwj -----END PGP SIGNATURE----- --=-NZ7y5Bhvmo3DnfIk7N+N-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 18:01:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F08516A4CE; Thu, 20 Jan 2005 18:01:28 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1FE643D49; Thu, 20 Jan 2005 18:01:27 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Thu, 20 Jan 2005 10:01:27 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3BCB35D07; Thu, 20 Jan 2005 10:01:27 -0800 (PST) To: Scot Hetzel In-reply-to: Your message of "Thu, 20 Jan 2005 10:12:04 CST." <790a9fff050120081229a3ec6a@mail.gmail.com> Date: Thu, 20 Jan 2005 10:01:27 -0800 From: "Kevin Oberman" Message-Id: <20050120180127.3BCB35D07@ptavv.es.net> cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) 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, 20 Jan 2005 18:01:28 -0000 > Date: Thu, 20 Jan 2005 10:12:04 -0600 > From: Scot Hetzel > Sender: owner-freebsd-stable@freebsd.org > > On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne > wrote: > > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > > and the box is up BUT I am concerned that the NEXT time that I > > do "make installkernel" I'll stomp on kernel.old losing this fallback > > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > > but is there something else I should save? Or is there another > > suggested procedure? > > > When I have a bad kernel I do the following after booting the good kernel. > > cd /boot > rm -rf kernel > cp -rp kernel.old kernel > cp -rp kernel.old kernel.good > > This way I can reboot the box without going into the loader to load kernel.old. While this works (I've done it), "make reinstallkernel" and "make -DMODULES_WITH_WORLD" reinstallkernel" can also be good friends. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 20:24:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FE5916A4CE for ; Thu, 20 Jan 2005 20:24:35 +0000 (GMT) Received: from hotmail.com (bay23-f8.bay23.hotmail.com [64.4.22.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F87943D54 for ; Thu, 20 Jan 2005 20:24:35 +0000 (GMT) (envelope-from fustigadorplenipotenciario@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 20 Jan 2005 12:24:02 -0800 Message-ID: Received: from 80.35.77.221 by by23fd.bay23.hotmail.msn.com with HTTP; Thu, 20 Jan 2005 20:23:19 GMT X-Originating-IP: [80.35.77.221] X-Originating-Email: [fustigadorplenipotenciario@hotmail.com] X-Sender: fustigadorplenipotenciario@hotmail.com From: "Miccionador Compulsivo" To: freebsd-amd64@freebsd.org Date: Thu, 20 Jan 2005 20:23:19 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 20 Jan 2005 20:24:02.0944 (UTC) FILETIME=[FB63A800:01C4FF2D] Subject: TV players for bt848 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, 20 Jan 2005 20:24:35 -0000 Hi, I've compiled fxtv (1.03) sources from freebsd5.0-i386, it runs but show nothing. Someone tried it (or other player)? Thanks, Enrique From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 22:06:03 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F13816A4CE; Thu, 20 Jan 2005 22:06:03 +0000 (GMT) Received: from maunakea.aafes.com (maunakea.aafes.com [199.67.7.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 152F543D39; Thu, 20 Jan 2005 22:05:57 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (from daemon@localhost) by maunakea.aafes.com (8.12.8p2/8.12.8) id j0KM5t3S002656; Thu, 20 Jan 2005 16:05:55 -0600 (CST) (envelope-from delphij@frontfree.net) Received: from hqmailbh02.aafes.com(192.168.32.54) via SMTP by mxproxy.aafes.com, id smtpdpS3PGq; Thu Jan 20 15:37:14 2005 Received: from mail pickup service by hqmailbh02.aafes.com with Microsoft SMTPSVC; Thu, 20 Jan 2005 15:36:36 -0600 Received: from aafes.com ([192.168.32.58]) by hqmailbh02.aafes.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 20 Jan 2005 10:40:22 -0600 Received: from ([192.168.32.46]) by hqmailgw02.aafes.com with SMTP id KP-NTD32.32839134; Thu, 20 Jan 2005 10:37:59 -0600 Received: (from daemon@localhost) by maunakea.aafes.com (8.12.8p2/8.12.8) id j0KGbf7b065725 for ; Thu, 20 Jan 2005 10:37:41 -0600 (CST) (envelope-from owner-freebsd-stable@freebsd.org) Received: from mx2.freebsd.org(216.136.204.119) via SMTP by maunakea.aafes.com, id smtpdwZ8nCG; Thu Jan 20 10:37:27 2005 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 0726E56E94; Thu, 20 Jan 2005 16:37:08 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B590416A541; Thu, 20 Jan 2005 16:36:57 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAA8A16A4CE for ; Thu, 20 Jan 2005 16:36:21 +0000 (GMT) Received: from mail.freebsd.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id 13ADE43D4C for ; Thu, 20 Jan 2005 16:36:16 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 98278 invoked by uid 0); 20 Jan 2005 16:28:25 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.99.7) by mail.freebsd.org.cn with SMTP; 20 Jan 2005 16:28:25 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id EE4E11335C0; Fri, 21 Jan 2005 00:36:10 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44853-14; Fri, 21 Jan 2005 00:35:59 +0800 (CST) Received: from localhost.localdomain (unknown [61.48.135.6]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by beastie.frontfree.net (Postfix) with ESMTP id B8552133598; Fri, 21 Jan 2005 00:35:57 +0800 (CST) From: Xin LI To: "Michael R. Wayne" In-Reply-To: <20050119214229.GE1168@manor.msen.com> References: <20050119214229.GE1168@manor.msen.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NZ7y5Bhvmo3DnfIk7N+N" Organization: The FreeBSD Simplified Chinese Project Date: Fri, 21 Jan 2005 00:34:42 +0800 Message-Id: <1106238882.1019.48.camel@spirit> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at frontfree.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org X-OriginalArrivalTime: 20 Jan 2005 16:40:22.0139 (UTC) FILETIME=[BBF754B0:01C4FF0E] cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-amd64@freebsd.org Reply-To: delphij@delphij.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:06:03 -0000 --=-NZ7y5Bhvmo3DnfIk7N+N Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Michael, =E5=9C=A8 2005-01-19=E4=B8=89=E7=9A=84 16:42 -0500=EF=BC=8CMichael R. Wayne= =E5=86=99=E9=81=93=EF=BC=9A > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > procedure. I can certainly copy /boot/kernel.old to /boot/kernel.save > but is there something else I should save? Or is there another=20 > suggested procedure? I personally do: cp -R /boot/kernel /boot/kernel.good If the kernel has provided stability for 30 days. For your case, you may want to do: cp -R /boot/kernel.old /boot/kernel.good since the kernel.old is last known good kernel. Of course kernel.save is a good name. For a STABLE branch you generally won't need to fear that loader changes can prevent you from being able to boot from older kernels. Therefore, I think the procedure you have listed is enough to do. Cheers, --=20 Xin LI http://www.delphij.net/ --=-NZ7y5Bhvmo3DnfIk7N+N Content-Type: application/pgp-signature; name=signature.asc Content-Description: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=BF=A1=E4=BB=B6=E7=9A=84=E6=95=B0?= =?UTF-8?Q?=E5=AD=97=E7=AD=BE=E5=90=8D=E9=83=A8?= =?UTF-8?Q?=E5=88=86?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB792i/cVsHxFZiIoRAmPyAJ0c5XWM/RuUgYSLU+RMmsj/iMFLPgCfQp3Q xqgIceP0t6xDmtNxE1RAac4= =9iwj -----END PGP SIGNATURE----- --=-NZ7y5Bhvmo3DnfIk7N+N-- From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 20 22:30:42 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F6B816A4CE; Thu, 20 Jan 2005 22:30:42 +0000 (GMT) Received: from mail.hydrix.com (ns1.hydrix.com [218.214.210.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4136043D2F; Thu, 20 Jan 2005 22:30:41 +0000 (GMT) (envelope-from jean-yves.avenard@hydrix.com) Received: from [192.168.2.10] (CPE-144-133-80-177.vic.bigpond.net.au [144.133.80.177]) (authenticated bits=0) by mail.hydrix.com (8.13.1/8.13.1) with ESMTP id j0KMTRxC096358 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 21 Jan 2005 09:30:28 +1100 (EST) (envelope-from jean-yves.avenard@hydrix.com) In-Reply-To: <41EFB111.8010906@michaelmeltzer.com> References: <41EFB111.8010906@michaelmeltzer.com> Mime-Version: 1.0 (Apple Message framework v619) Message-Id: From: Jean-Yves Avenard Date: Fri, 21 Jan 2005 09:30:07 +1100 To: Michael Meltzer X-Mailer: Apple Mail (2.619) X-Spam-Status: No, score=-2.2 required=6.5 tests=ALL_TRUSTED,J_CHICKENPOX_42 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/664/Fri Jan 14 02:13:05 2005 clamav-milter version 0.80j on server2.private.hydrix.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-scsi@FreeBSD.ORG cc: freebsd stable cc: freebsd-amd64@FreeBSD.ORG Subject: Re: twa breakage on AMD64 with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 20 Jan 2005 22:30:42 -0000 Well, it may work for you, but not for me. Still hangs exactly in the same spot. Jean-Yves On 21/01/2005, at 12:24 AM, Michael Meltzer wrote: > looks like patch3 worked, good job! I had to turn off TWA_DEBUG to=20 > get the boot going, the debug was starving the boot on a 9600 baud=20 > terminal. I can increase the speed and caputer the output on monday if=20= > it will help(it on the large side, bigger than the 10,000 line capture=20= > buffer in am using).=A0 I incude 2 iozone reports, the first one the = new=20 > driver the second one the old driver, Is thier a way to increase the=20= > "read ahead" in freebsd?? -mjm > > --- 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 Fri Jan 21 03:32:51 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CB3916A4CE for ; Fri, 21 Jan 2005 03:32:51 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74A8443D3F for ; Fri, 21 Jan 2005 03:32:50 +0000 (GMT) (envelope-from archive.it@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so50398rne for ; Thu, 20 Jan 2005 19:32:50 -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:mime-version:content-type:content-transfer-encoding; b=UplxzStETn8NYsXZpNt/2yHPUXGyQbGSA+7ifzn0T92bVX2W9dob1IT5H+6hTNKqjH6xOrJFU4N/JbJiPTRTw0Px+qS5HN2KKGL1vj0jv1vIvH86efFb5MqObHfYagXQAmpU61+VLHuU0w4k+xKNXZ8Ew8/mCNfzhypPwGNwrOI= Received: by 10.38.89.9 with SMTP id m9mr161425rnb; Thu, 20 Jan 2005 19:32:49 -0800 (PST) Received: by 10.39.2.26 with HTTP; Thu, 20 Jan 2005 19:32:49 -0800 (PST) Message-ID: <64559708050120193253245590@mail.gmail.com> Date: Fri, 21 Jan 2005 11:32:49 +0800 From: DIrk To: amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Adaptec AIC-7902W can not use 320M/s Sync Transfer Rate. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: DIrk List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 03:32:51 -0000 I have a AMD64 server : Thunder K8S Pro (S2882) Opteron 246 x2 1G x4 RAM Seagate ST3146707LW x2 FreeBSD/amd64 5.3 stable Mobo BIOS: 2.04 Adaptec BIOS: 4.30 NO ANY RAID CARD used. At first, I use the SCSI U320 mode, FreeBSD complained about "DUMP CARD STATE" at booting & disk io sometimes. And it is working fine when I set SCSI to U160 mode (Step down the "Sync Transfer Rate" from 320M/s to 160M/s). Is here some problem with the SCSI cable or terminator ? Any suggestion ? Thanks very much. Here is system Uname: FreeBSD www.test.com 5.3-STABLE FreeBSD 5.3-STABLE #0: Thu Jan 20 22:47:43 CST 2005 root@www.test.com:/usr/obj/usr/src/sys/THENORA amd64 Here is error dmesg under U320 mode: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Thu Jan 20 22:47:43 CST 2005 root@www.test.com:/usr/obj/usr/src/sys/THENORA WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 246 (1995.40-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 4227792896 (4031 MB) avail memory = 4083990528 (3894 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 pci3: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs bge0: mem 0xfc9b0000-0xfc9bffff,0xfc9c0000-0xfc9cffff irq 24 at device 9.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:2b:a5:62 bge0: [GIANT-LOCKED] bge1: mem 0xfc9e0000-0xfc9effff,0xfc9f0000-0xfc9fffff irq 25 at device 9.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:2b:a5:63 bge1: [GIANT-LOCKED] pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acd0: CDROM at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle ahd0: Invalid Sequencer interrupt occurred. >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahd0: Dumping Card State at program address 0x23c Mode 0x0 Card was paused INTSTAT[0x0] SELOID[0x1] SELID[0x0] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] SCSISIGI[0x0] SCSIPHASE[0x0] SCSIBUS[0x0] LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x0] SEQINTCTL[0x6] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x2] KERNEL_QFREEZE_COUNT[0x2] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x8] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 16 CMDS_PENDING = 0 LASTSCB 0xffff CURRSCB 0xe NEXTSCB 0xff40 qinstart = 28 qinfifonext = 28 QINFIFO: WAITING_TID_QUEUES: Pending list: Total 0 Kernel Free SCB list: 15 14 1 2 3 4 5 6 7 8 9 10 11 12 13 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xf SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xe SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x8 0x0 0x0 0xf 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x4] ahd0: REG0 == 0x563e, SINDEX = 0x10e, DINDEX = 0x104 ahd0: SCBPTR == 0xf, SCB_NEXT == 0xff40, SCB_NEXT2 == 0xff9b CDB 12 20 0 80 88 a6 STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 SMP: AP CPU #1 Launched! da0 at ahd0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) da1 at ahd0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) Mounting root from ufs:/dev/da0s1a And no problem dmesg under U160: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Thu Jan 20 22:47:43 CST 2005 root@www.test.com:/usr/obj/usr/src/sys/THENORA WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 246 (1995.49-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 4227792896 (4031 MB) avail memory = 4083990528 (3894 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci3: on pcib1 pci3: at device 6.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib2: at device 10.0 on pci0 pci2: on pcib2 ahd0: port 0xac00-0xacff,0xa000-0xa0ff mem 0xfc8fc000-0xfc8fdfff irq 24 at device 6.0 on pci2 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0xa400-0xa4ff,0xa800-0xa8ff mem 0xfc8fe000-0xfc8fffff irq 25 at device 6.1 on pci2 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs bge0: mem 0xfc9b0000-0xfc9bffff,0xfc9c0000-0xfc9cffff irq 24 at device 9.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:2b:a5:62 bge0: [GIANT-LOCKED] bge1: mem 0xfc9e0000-0xfc9effff,0xfc9f0000-0xfc9fffff irq 25 at device 9.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:e0:81:2b:a5:63 bge1: [GIANT-LOCKED] pci0: at device 10.1 (no driver attached) pcib3: at device 11.0 on pci0 pci1: on pcib3 pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acd0: CDROM at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ahd0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) da1 at ahd0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) Mounting root from ufs:/dev/da0s1a From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 21 05:08:54 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14A9516A4CE; Fri, 21 Jan 2005 05:08:54 +0000 (GMT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F47F43D39; Fri, 21 Jan 2005 05:08:53 +0000 (GMT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com ([151.204.231.237]) by out002.verizon.netESMTP <20050121050852.UJBG12052.out002.verizon.net@corbulon.video-collage.com>; Thu, 20 Jan 2005 23:08:52 -0600 Received: from corbulon.video-collage.com (mi@localhost.video-collage.com [127.0.0.1])j0L58hci067716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 00:08:44 -0500 (EST) (envelope-from mi@corbulon.video-collage.com) Received: (from mi@localhost)j0L58hqD067715; Fri, 21 Jan 2005 00:08:43 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <200501210508.j0L58hqD067715@corbulon.video-collage.com> To: freebsd-amd64@FreeBSD.org Date: Fri, 21 Jan 2005 00:08:43 -0500 (EST) In-Reply-To: <20050119035737.GA65592@dragon.nuxi.com> X-Mailer: ELM [version 2.5 PL7] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [151.204.231.237] at Thu, 20 Jan 2005 23:08:52 -0600 cc: freebsd-emulation@FreeBSD.org Subject: Re: Linux i386, NVidia on FreeBSD/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: Fri, 21 Jan 2005 05:08:54 -0000 > > 2) NVidia X11 driver -- this is not a must, but would be very > > nice to have -- I have a fairly high-end dual-DVI card, that > > works fine on my dual PentiumII. Any hope of getting NVidia to > > release amd64-version? > > Nope. Actually, I'm quite hopeful now :-) NVidia does offer AMD64-drivers for Linux already... If enough people ask (and I just did), the support for FreeBSD/amd64 just might appear. http://www.nvidia.com/object/linux.html > > 3) SMP -- a dual-Opteron machine seems within my budget. Does > > that change the answers to any of the above questions? > > Works even better. Any particular motherboards, chipsets to recommend? How about: http://www.iwillusa.com/products/ProductDetail.asp?vID=182&CID=92 Thanks! -mi From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 21 17:45:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7828916A4CE; Fri, 21 Jan 2005 17:45:53 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00BF843D54; Fri, 21 Jan 2005 17:45:53 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id D69A23001109; Fri, 21 Jan 2005 18:45:51 +0100 (CET) Message-ID: <41F13FC5.4070106@uni-mainz.de> Date: Fri, 21 Jan 2005 18:45:41 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050102 X-Accept-Language: de-de, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: ASUS A8N-SLI Deluxe supported by FreeBSD 5.3? 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, 21 Jan 2005 17:45:53 -0000 Hello. Maybe this question is out of focus of this list, but maybe not. I wish to obtain a new AMD64 based system with PCIe and found the ASUS A8N-SLI/Deluxe mainboard based on NVidia NForce4-SLI chipset suitable. I would like to know whether this board or more precise, the chipset and its ATA II facilities are supported by FreeBSD 5.3-STABLE or oncoming FreeBSD 5.4-RELEASE. Furthermore I would like to equippt this system by a ATI Radeon X600 based PCIe graphics board and maybe someone is out here who can offer some bad or good experiences with this board. Thanks a lot. Oliver From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 21 22:33:12 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BC7616A4CE; Fri, 21 Jan 2005 22:33:12 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D3743D49; Fri, 21 Jan 2005 22:33:11 +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 j0LMX8TA012526; Fri, 21 Jan 2005 17:33:11 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0LMX8Gk012525; Fri, 21 Jan 2005 17:33:08 -0500 (EST) (envelope-from wayne) Date: Fri, 21 Jan 2005 17:33:08 -0500 From: "Michael R. Wayne" To: freebsd stable , freebsd-amd64@freebsd.org Message-ID: <20050121223308.GN1168@manor.msen.com> Mail-Followup-To: freebsd stable , freebsd-amd64@freebsd.org References: <41EFB111.8010906@michaelmeltzer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Subject: Re: twa breakage on AMD64 with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit 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, 21 Jan 2005 22:33:12 -0000 Hmm, this might be my problem as well. I'm running -STABLE from November: FreeBSD 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 but when I build a current kernel, I can't even boot! At this point I am reluctant to upgrade anything until the problem is determined - breaking production servers isn't a good plan. >From my (working) dmesg: 3ware device driver for 9000 series storage controllers, version: 2.50.00.000 twa0: <3ware 9000 series Storage Controller> port 0x3000-0x30ff mem 0xfd800000-0xfdffffff,0xfd020000-0xfd0200ff irq 26 at device 2.0 on pci2 twa0: [GIANT-LOCKED] twa0: 4 ports, Firmware FE9X 2.04.00.003, BIOS BE9X 2.03.01.047 The box failed with: Mounting root from ufs:/dev/da0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 21 23:30:16 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 138DB16A4CF for ; Fri, 21 Jan 2005 23:30:16 +0000 (GMT) Received: from mail.celeritystorm.com (mail.celeritystorm.com [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92EA143D2F for ; Fri, 21 Jan 2005 23:30:15 +0000 (GMT) (envelope-from adm@celeritystorm.com) Received: from [192.168.0.1] (unknown [81.84.175.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id 1F5893D74AD for ; Sat, 22 Jan 2005 00:29:02 +0100 (CET) Message-ID: <41F1903D.3060508@celeritystorm.com> Date: Fri, 21 Jan 2005 23:29:01 +0000 From: Hugo Silva User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Would this system work correctly with FreeBSD 5.3 ? 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, 21 Jan 2005 23:30:16 -0000 Hi list, I'm buying a Quad AMD Opteron 64 bits, with 4GB memory. I'd like to know if FreeBSD 5.3 will support a quad-cpu system (with HTT, 8) correctly, without performance losses and consistent operation, no crashes etc. Is the 4GB memory still a problem in amd64 ? Lastly, I'd like to hear experiences of linux-compat games (such as enemy territory, call of duty, halflife 2) running on FreeBSD-AMD64 -- Do they work correctly on this 64bit CPU system ? I want to use FreeBSD as I use on all my servers, but I want to be sure 4 CPUs, 4GB of ram, and 64 bit architecture won't bring me any stability/usability problems under AMD64. Regards From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 21 23:55:53 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50F5416A4CE for ; Fri, 21 Jan 2005 23:55:53 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BEB743D2F for ; Fri, 21 Jan 2005 23:55:53 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j0LNtoBV094815; Fri, 21 Jan 2005 15:55:50 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j0LNtoW4094814; Fri, 21 Jan 2005 15:55:50 -0800 (PST) (envelope-from sgk) Date: Fri, 21 Jan 2005 15:55:50 -0800 From: Steve Kargl To: Hugo Silva Message-ID: <20050121235550.GA85260@troutmask.apl.washington.edu> References: <41F1903D.3060508@celeritystorm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F1903D.3060508@celeritystorm.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: Would this system work correctly with FreeBSD 5.3 ? 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, 21 Jan 2005 23:55:53 -0000 On Fri, Jan 21, 2005 at 11:29:01PM +0000, Hugo Silva wrote: > > I'm buying a Quad AMD Opteron 64 bits, with 4GB memory. I'd like to know > if FreeBSD 5.3 will support a quad-cpu system (with HTT, 8) correctly, > without performance losses and consistent operation, no crashes etc. Is > the 4GB memory still a problem in amd64 ? You're asking a possibly bad question. First, FreeBSD 5.3 will run on a quad opteron system. The tyan quad motherboard supports upto 32 GB on memory, and FreeBSD 5.3 should/will use all 32 GB. So, your 4 GB is no problem. Second, HTT may or may not cause a small impact on performance. It depends on what applications you run. Of course, my opteron processes don't support HTT CPU: AMD Opteron(tm) Processor 248 (2193.43-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff Third, what OS have you run that you have never experienced a crash? If your electricity goes out, you'll have a crash. If your hard drive dies a (un)natural death, then you have a crash. > Lastly, I'd like to hear experiences of linux-compat games (such as > enemy territory, call of duty, halflife 2) running on FreeBSD-AMD64 -- > Do they work correctly on this 64bit CPU system ? Linux-compat for 32-bit applications works. But I must ask, you're purchasing a quad opteron system to run games? -- Steve From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:05:37 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C791A16A4CE for ; Sat, 22 Jan 2005 00:05:37 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D48743D41 for ; Sat, 22 Jan 2005 00:05:37 +0000 (GMT) (envelope-from jbehl@fastclick.com) Received: from [192.168.3.100] (unknown [205.180.85.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sb.santaba.com (Postfix) with ESMTP id 53D1828485 for ; Fri, 21 Jan 2005 16:05:37 -0800 (PST) Message-ID: <41F198F8.9020608@fastclick.com> Date: Fri, 21 Jan 2005 16:06:16 -0800 From: Jeff Behl User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) 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: bsd i386 on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 00:05:37 -0000 i have a dual proc 3gHz AMD Opteron box that i want to run java on, so it looks like i have to use the i386 build (any news on the jdk coming to AMD?). from what i've gathered, this should not be a problem and performance should be at least par compared to to running on a Xeon. is this true? i even seem to remember hearing rumor that the Opteron could even run i386 code faster, mHz to mHz, than a Xeon? thanks. From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:09:28 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0A3116A4CE for ; Sat, 22 Jan 2005 00:09:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FE2843D54 for ; Sat, 22 Jan 2005 00:09:28 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0M0DxCk042080; Fri, 21 Jan 2005 17:13:59 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41F199B3.1030809@freebsd.org> Date: Fri, 21 Jan 2005 17:09:23 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <41F1903D.3060508@celeritystorm.com> <20050121235550.GA85260@troutmask.apl.washington.edu> In-Reply-To: <20050121235550.GA85260@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-amd64@freebsd.org Subject: Re: Would this system work correctly with FreeBSD 5.3 ? 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, 22 Jan 2005 00:09:28 -0000 Steve Kargl wrote: > On Fri, Jan 21, 2005 at 11:29:01PM +0000, Hugo Silva wrote: > >>I'm buying a Quad AMD Opteron 64 bits, with 4GB memory. I'd like to know >>if FreeBSD 5.3 will support a quad-cpu system (with HTT, 8) correctly, >>without performance losses and consistent operation, no crashes etc. Is >>the 4GB memory still a problem in amd64 ? > > > You're asking a possibly bad question. > > First, FreeBSD 5.3 will run on a quad opteron system. The tyan > quad motherboard supports upto 32 GB on memory, and FreeBSD 5.3 > should/will use all 32 GB. So, your 4 GB is no problem. > 4GB+ is a problem on 5.3-RELEASE due to DMA issues. Only a small handful of storage drivers will actually work. > Second, HTT may or may not cause a small impact on performance. > It depends on what applications you run. Of course, my opteron > processes don't support HTT > Of course there is no such a thing as an HTT Opteron system. In any case, there have been fixes recently that help with a potential lockup on systems with lots of CPU's. It's not yet ideal, but even more fixes are in the pipeline. Scott From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:13:21 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA35016A4CE for ; Sat, 22 Jan 2005 00:13:21 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7FD843D41 for ; Sat, 22 Jan 2005 00:13:21 +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 j0M0DKiJ040682; Fri, 21 Jan 2005 16:13:20 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0M0DK39040681; Fri, 21 Jan 2005 16:13:20 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2005 16:13:20 -0800 From: "David O'Brien" To: Jeff Behl Message-ID: <20050122001320.GA39743@dragon.nuxi.com> References: <41F198F8.9020608@fastclick.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F198F8.9020608@fastclick.com> 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: bsd i386 on 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: Sat, 22 Jan 2005 00:13:22 -0000 On Fri, Jan 21, 2005 at 04:06:16PM -0800, Jeff Behl wrote: > i have a dual proc 3gHz AMD Opteron box Impossible. :-) The fastest Opteron right now is 2.5 GHz. > that i want to run java on, so > it looks like i have to use the i386 build (any news on the jdk coming > to AMD?). You probably want to use the Linux 'i386' JDK. > from what i've gathered, this should not be a problem and > performance should be at least par compared to to running on a Xeon. is > this true? i even seem to remember hearing rumor that the Opteron could > even run i386 code faster, mHz to mHz, than a Xeon? An Opteron runs all code faster MHz to MHz compared to Xeon. Opteron has a shorter pipeline and thus can do more work per cycle. Xeon has a very deep pipeline and thus can be clocked higher and must be clocked higher to get the same performance. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:15:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 538C316A4CE for ; Sat, 22 Jan 2005 00:15:38 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F9A043D2F for ; Sat, 22 Jan 2005 00:15:38 +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 j0M0FYGT040766; Fri, 21 Jan 2005 16:15:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0M0FX9M040765; Fri, 21 Jan 2005 16:15:33 -0800 (PST) (envelope-from obrien) Date: Fri, 21 Jan 2005 16:15:33 -0800 From: "David O'Brien" To: Hugo Silva Message-ID: <20050122001533.GB39743@dragon.nuxi.com> References: <41F1903D.3060508@celeritystorm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F1903D.3060508@celeritystorm.com> 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: Would this system work correctly with FreeBSD 5.3 ? 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: Sat, 22 Jan 2005 00:15:38 -0000 On Fri, Jan 21, 2005 at 11:29:01PM +0000, Hugo Silva wrote: > Hi list, > > I'm buying a Quad AMD Opteron 64 bits, with 4GB memory. I'd like to know > if FreeBSD 5.3 will support a quad-cpu system (with HTT, 8) correctly, > without performance losses and consistent operation, no crashes etc. Is > the 4GB memory still a problem in amd64 ? This configuration does not exist -- AMD does not have a HTT (SMT) processor. AMD will lauch full-fledged dual-core (CMP) CPU's later this year. That said, FreeBSD 5.3 should run just fine on a 4-CPU 4GB Opteron server. That said, I prefer to run 5-STABLE (RELENG_5) on the FreeBSD/amd64 platform as it gets a lot of improvements committed to it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:16:38 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FE5F16A4CE for ; Sat, 22 Jan 2005 00:16:38 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57A6043D31 for ; Sat, 22 Jan 2005 00:16:38 +0000 (GMT) (envelope-from jbehl@fastclick.com) Received: from [192.168.3.100] (unknown [205.180.85.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sb.santaba.com (Postfix) with ESMTP id F31C428485 for ; Fri, 21 Jan 2005 16:16:37 -0800 (PST) Message-ID: <41F19B8D.4010005@fastclick.com> Date: Fri, 21 Jan 2005 16:17:17 -0800 From: Jeff Behl User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org References: <41F198F8.9020608@fastclick.com> <20050122001320.GA39743@dragon.nuxi.com> In-Reply-To: <20050122001320.GA39743@dragon.nuxi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: bsd i386 on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 00:16:38 -0000 David O'Brien wrote: >On Fri, Jan 21, 2005 at 04:06:16PM -0800, Jeff Behl wrote: > > >>i have a dual proc 3gHz AMD Opteron box >> >> > >Impossible. :-) The fastest Opteron right now is 2.5 GHz. > > > yep, you got got me. they're 2gHz. >>that i want to run java on, so >>it looks like i have to use the i386 build (any news on the jdk coming >>to AMD?). >> >> > >You probably want to use the Linux 'i386' JDK. > > > so Linux JDK is stable and has decent performance, and won't cause me any headache in terms of compatibility with things like Tomcat? i guess byte code is byte, or so they say... >>from what i've gathered, this should not be a problem and >>performance should be at least par compared to to running on a Xeon. is >>this true? i even seem to remember hearing rumor that the Opteron could >>even run i386 code faster, mHz to mHz, than a Xeon? >> >> > >An Opteron runs all code faster MHz to MHz compared to Xeon. Opteron >has a shorter pipeline and thus can do more work per cycle. Xeon has a >very deep pipeline and thus can be clocked higher and must be clocked >higher to get the same performance. > > > great news, thanks much! jeff From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:31:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA13E16A4CE for ; Sat, 22 Jan 2005 00:31:35 +0000 (GMT) Received: from mail.celeritystorm.com (mail.celeritystorm.com [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 421A543D39 for ; Sat, 22 Jan 2005 00:31:35 +0000 (GMT) (envelope-from adm@celeritystorm.com) Received: from [192.168.0.1] (unknown [81.84.175.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id A6DD73D74B1 for ; Sat, 22 Jan 2005 01:30:22 +0100 (CET) Message-ID: <41F19E9D.30603@celeritystorm.com> Date: Sat, 22 Jan 2005 00:30:21 +0000 From: Hugo Silva User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <41F1903D.3060508@celeritystorm.com> <20050121235550.GA85260@troutmask.apl.washington.edu> In-Reply-To: <20050121235550.GA85260@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Would this system work correctly with FreeBSD 5.3 ? 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, 22 Jan 2005 00:31:35 -0000 Hey all, Thanks for the replies! By HTT I meant HyperTransport, isn't that AMD's version of HyperThreading? I could be wrong. Steve Kargl wrote: >On Fri, Jan 21, 2005 at 11:29:01PM +0000, Hugo Silva wrote: > > >>I'm buying a Quad AMD Opteron 64 bits, with 4GB memory. I'd like to know >>if FreeBSD 5.3 will support a quad-cpu system (with HTT, 8) correctly, >>without performance losses and consistent operation, no crashes etc. Is >>the 4GB memory still a problem in amd64 ? >> >> > >You're asking a possibly bad question. > >First, FreeBSD 5.3 will run on a quad opteron system. The tyan >quad motherboard supports upto 32 GB on memory, and FreeBSD 5.3 >should/will use all 32 GB. So, your 4 GB is no problem. > >Second, HTT may or may not cause a small impact on performance. >It depends on what applications you run. Of course, my opteron >processes don't support HTT > > CPU: AMD Opteron(tm) Processor 248 (2193.43-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > Features=0x78bfbff MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > >Third, what OS have you run that you have never experienced a crash? >If your electricity goes out, you'll have a crash. If your hard drive >dies a (un)natural death, then you have a crash. > > > By crash I meant the OS dying, not hardware/natural causes fault. I've had some problems with 5.1 (not on amd64 tho), guess I still distrust 5.X a bit.. 4.X has always been rock-solid to me, but nowdays I have few 4.X servers and only one 5.3 server has problems, which I suspect are hardware related-- but that's another story. > > >>Lastly, I'd like to hear experiences of linux-compat games (such as >>enemy territory, call of duty, halflife 2) running on FreeBSD-AMD64 -- >>Do they work correctly on this 64bit CPU system ? >> >> > >Linux-compat for 32-bit applications works. But I must ask, you're >purchasing a quad opteron system to run games? > > > Yes, I'll use it as a server for gaming only. I wasn't sure if it would be better to buy two dual opterons, or a quad opteron. For now I'm going with the quad, but it isn't too late to change this yet. I think FreeBSD can handle the load with a lot of gameservers ontop of it, it's the bandwidth (packet-loss free) that concerns me. One super server with lots of gameservers on it will have some packetloss if the network isn't good, and packet loss isn't an option when talking about onling gaming (First person shooters) From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 00:46:08 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ED8D16A4CE for ; Sat, 22 Jan 2005 00:46:08 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B909443D41 for ; Sat, 22 Jan 2005 00:46:07 +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 j0M0kHdE023468; Fri, 21 Jan 2005 16:46:17 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0M0kHui023467; Fri, 21 Jan 2005 16:46:17 -0800 Date: Fri, 21 Jan 2005 16:46:17 -0800 From: Brooks Davis To: Hugo Silva Message-ID: <20050122004617.GA23349@odin.ac.hmc.edu> References: <41F1903D.3060508@celeritystorm.com> <20050121235550.GA85260@troutmask.apl.washington.edu> <41F19E9D.30603@celeritystorm.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <41F19E9D.30603@celeritystorm.com> 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: Would this system work correctly with FreeBSD 5.3 ? 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, 22 Jan 2005 00:46:08 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 22, 2005 at 12:30:21AM +0000, Hugo Silva wrote: > Hey all, >=20 > Thanks for the replies! >=20 > By HTT I meant HyperTransport, isn't that AMD's version of=20 > HyperThreading? I could be wrong. You are. :-) HyperTransport is the interconnect used by the CPUs are bridge chips. -- 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 --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB8aJYXY6L6fI4GtQRAuKDAKDTkwxvdE3jJ8vM8JGSirlk/TZiFQCdFrlt A3+Pv0cqdJa7EcTLfD/jpPY= =YeDO -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 14:17:43 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B7916A4CE for ; Sat, 22 Jan 2005 14:17:43 +0000 (GMT) Received: from web26804.mail.ukl.yahoo.com (web26804.mail.ukl.yahoo.com [217.146.176.80]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E82743D48 for ; Sat, 22 Jan 2005 14:17:42 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 9692 invoked by uid 60001); 22 Jan 2005 14:17:41 -0000 Message-ID: <20050122141741.9690.qmail@web26804.mail.ukl.yahoo.com> Received: from [194.248.174.50] by web26804.mail.ukl.yahoo.com via HTTP; Sat, 22 Jan 2005 15:17:41 CET Date: Sat, 22 Jan 2005 15:17:41 +0100 (CET) From: Claus Guttesen To: Hugo Silva , freebsd-amd64@freebsd.org In-Reply-To: <41F1903D.3060508@celeritystorm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Would this system work correctly with FreeBSD 5.3 ? 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, 22 Jan 2005 14:17:43 -0000 > I'm buying a Quad AMD Opteron 64 bits, with 4GB > memory. I'd like to know > if FreeBSD 5.3 will support a quad-cpu system (with > HTT, 8) correctly, > without performance losses and consistent operation, > no crashes etc. Is > the 4GB memory still a problem in amd64 ? I have a tyan quad-opteron @ 2 Ghz with 4 GB RAM. Works fine, using it as a postgresql-server. Running 5.3-stable. Very nice hardware. Claus From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 22 21:17:41 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0154416A4CF for ; Sat, 22 Jan 2005 21:17:40 +0000 (GMT) Received: from mail.uk.psi.com (mail.uk.psi.com [154.8.2.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE60243D1D for ; Sat, 22 Jan 2005 21:17:39 +0000 (GMT) (envelope-from alan.barrow@psinet.telstra.co.uk) Received: from ip10.vpn.uk.psi.com ([154.8.4.10] helo=macros) by mail.uk.psi.com with smtp (Exim 4.41) id 1CsSdV-0000Ab-UJ; Sat, 22 Jan 2005 21:17:38 +0000 From: To: "Hugo Silva" , Date: Sat, 22 Jan 2005 21:11:33 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <41F19E9D.30603@celeritystorm.com> Importance: Normal Subject: RE: Would this system work correctly with FreeBSD 5.3 ? 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: Sat, 22 Jan 2005 21:17:41 -0000 Why a quad ?? Seems like overkill ! yours a.r.b -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org]On Behalf Of Hugo Silva Sent: 22 January 2005 00:30 To: freebsd-amd64@freebsd.org Subject: Re: Would this system work correctly with FreeBSD 5.3 ? Hey all, Thanks for the replies! By HTT I meant HyperTransport, isn't that AMD's version of HyperThreading? I could be wrong. Steve Kargl wrote: >On Fri, Jan 21, 2005 at 11:29:01PM +0000, Hugo Silva wrote: > > >>I'm buying a Quad AMD Opteron 64 bits, with 4GB memory. I'd like to know >>if FreeBSD 5.3 will support a quad-cpu system (with HTT, 8) correctly, >>without performance losses and consistent operation, no crashes etc. Is >>the 4GB memory still a problem in amd64 ? >> >> > >You're asking a possibly bad question. > >First, FreeBSD 5.3 will run on a quad opteron system. The tyan >quad motherboard supports upto 32 GB on memory, and FreeBSD 5.3 >should/will use all 32 GB. So, your 4 GB is no problem. > >Second, HTT may or may not cause a small impact on performance. >It depends on what applications you run. Of course, my opteron >processes don't support HTT > > CPU: AMD Opteron(tm) Processor 248 (2193.43-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 > Features=0x78bfbff MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > >Third, what OS have you run that you have never experienced a crash? >If your electricity goes out, you'll have a crash. If your hard drive >dies a (un)natural death, then you have a crash. > > > By crash I meant the OS dying, not hardware/natural causes fault. I've had some problems with 5.1 (not on amd64 tho), guess I still distrust 5.X a bit.. 4.X has always been rock-solid to me, but nowdays I have few 4.X servers and only one 5.3 server has problems, which I suspect are hardware related-- but that's another story. > > >>Lastly, I'd like to hear experiences of linux-compat games (such as >>enemy territory, call of duty, halflife 2) running on FreeBSD-AMD64 -- >>Do they work correctly on this 64bit CPU system ? >> >> > >Linux-compat for 32-bit applications works. But I must ask, you're >purchasing a quad opteron system to run games? > > > Yes, I'll use it as a server for gaming only. I wasn't sure if it would be better to buy two dual opterons, or a quad opteron. For now I'm going with the quad, but it isn't too late to change this yet. I think FreeBSD can handle the load with a lot of gameservers ontop of it, it's the bandwidth (packet-loss free) that concerns me. One super server with lots of gameservers on it will have some packetloss if the network isn't good, and packet loss isn't an option when talking about onling gaming (First person shooters) _______________________________________________ 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 Jan 22 21:19:57 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B05116A4CE for ; Sat, 22 Jan 2005 21:19:57 +0000 (GMT) Received: from mail.uk.psi.com (mail.uk.psi.com [154.8.2.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 531D443D1D for ; Sat, 22 Jan 2005 21:19:57 +0000 (GMT) (envelope-from alan.barrow@psinet.telstra.co.uk) Received: from ip10.vpn.uk.psi.com ([154.8.4.10] helo=macros) by mail.uk.psi.com with smtp (Exim 4.41) id 1CsSfh-0000DX-Vp; Sat, 22 Jan 2005 21:19:55 +0000 From: To: "Jeff Behl" , Date: Sat, 22 Jan 2005 21:13:49 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <41F19B8D.4010005@fastclick.com> Importance: Normal Subject: RE: bsd i386 on 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: Sat, 22 Jan 2005 21:19:57 -0000 Compare 248 against dual 2.8 xeon 2 gig of ram each the dual opteron running the jdk on i386 and tomcat is at least twice as fast on compile time for a start. The amd's are animals, you WILL have trouble abusing the system. yours a.r.b. -----Original Message----- From: owner-freebsd-amd64@freebsd.org [mailto:owner-freebsd-amd64@freebsd.org]On Behalf Of Jeff Behl Sent: 22 January 2005 00:17 To: freebsd-amd64@FreeBSD.org Subject: Re: bsd i386 on amd64 David O'Brien wrote: >On Fri, Jan 21, 2005 at 04:06:16PM -0800, Jeff Behl wrote: > > >>i have a dual proc 3gHz AMD Opteron box >> >> > >Impossible. :-) The fastest Opteron right now is 2.5 GHz. > > > yep, you got got me. they're 2gHz. >>that i want to run java on, so >>it looks like i have to use the i386 build (any news on the jdk coming >>to AMD?). >> >> > >You probably want to use the Linux 'i386' JDK. > > > so Linux JDK is stable and has decent performance, and won't cause me any headache in terms of compatibility with things like Tomcat? i guess byte code is byte, or so they say... >>from what i've gathered, this should not be a problem and >>performance should be at least par compared to to running on a Xeon. is >>this true? i even seem to remember hearing rumor that the Opteron could >>even run i386 code faster, mHz to mHz, than a Xeon? >> >> > >An Opteron runs all code faster MHz to MHz compared to Xeon. Opteron >has a shorter pipeline and thus can do more work per cycle. Xeon has a >very deep pipeline and thus can be clocked higher and must be clocked >higher to get the same performance. > > > great news, thanks much! jeff _______________________________________________ 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"