From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 01:50:17 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B6A816A41F; Sun, 27 Nov 2005 01:50:17 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79D1243D5E; Sun, 27 Nov 2005 01:50:16 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.5/jtpda-5.4) with ESMTP id jAR1oEED078622 ; Sun, 27 Nov 2005 02:50:14 +0100 (CET) X-Ids: 165 Received: from heho.labo (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id jAR1oD4u081808 ; Sun, 27 Nov 2005 02:50:13 +0100 (MET) Received: (from arno@localhost) by heho.labo (8.13.3/8.13.1/Submit) id jAR1oCx0081805; Sun, 27 Nov 2005 02:50:12 +0100 (MET) (envelope-from arno) Sender: arno@heho.snv.jussieu.fr To: amd64@freebsd.org From: "Arno J. Klaassen" Date: 27 Nov 2005 02:50:12 +0100 Message-ID: Lines: 114 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.165]); Sun, 27 Nov 2005 02:50:14 +0100 (CET) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 438910D6.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: java@freebsd.org, freebsd-emulation@freebsd.org Subject: quest for help on a linux emul problem (source unknown) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 01:50:17 -0000 Hello, I try to get a commercial linux32 package to work on amd64; this package includes it's own binary distrib of some linux-jdk1.3.1 and works OK on i386 (RELENG_5 and RELENG_6) but hangs on amd64-RELENG_6 (though it did work on a couple of months old amd64-RELENG-5, but I do not any longer have such a box around ... ). I write this email in the hope someone can put me on the right track to nail down this problem : when I do a ktrace on i386 I get : CALL mincore(0xbfbfc480,0) RET mincore 0 CALL #175(0,0,0xbfbfc2b4,0x8) RET #175 0 CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) RET #175 0 CALL mincore(0xbfbfc290,0) RET mincore 0 CALL getdomainname(0xbfbfc288,0) RET getdomainname 0 then some dozens of : CALL #175(0x2,0xbfbfc338,0,0x8) RET #175 0 CALL mincore(0xbfbfc480,0) RET mincore 0 CALL #175(0,0,0xbfbfc2b4,0x8) RET #175 0 CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) RET #175 0 CALL mincore(0xbfbfc290,0) RET mincore 0 CALL getdomainname(0xbfbfc288,0) RET getdomainname 0 and finally : CALL #175(0x2,0xbfbfc338,0,0x8) RET #175 0 CALL write(0xb,0x83189e8,0x18) GIO fd 11 wrote 24 bytes On amd64-RELENG_6 it eternally loops in phase2 and never reaches the 'finally'. Iff I understand correctly (far from sure!) and correct for different syscall-numbers, I get : ask-for-initing-something { gettimeofday() sigprocmask(SIG_BLOCK,..) sigprocmask(SIG_UNBLOCK,..) gettimeofday() nanosleep() } while-not-OK { sigprocmask(SIG_SETMASK,..) gettimeofday() sigprocmask(SIG_BLOCK,..) sigprocmask(SIG_UNBLOCK,..) gettimeofday() nanosleep() } OK! { sigprocmask(SIG_SETMASK,..) continue() } Since the program works OK in terminal mode, the problem very probably is in the jdk-execution. I re-downloaded the jdk13 sources and found that only at two places sigprocmask() is called with SIG_UNBLOCK as argument, and one of them only seems to serve the purpose of a work-around : * a workaround for the preemptive-close * problem on Linux (bug #4344135); A thread currently waiting in * a I/O operation will not wake up if one the file involved * is actually closed (last close - the file is no longer accessible, * but the thread is still waiting in the kernel). NB, this is a linux-jdk-1.3.0 problem, solved in linux-jdk-1.3.1, so "an sich" not involved in my problem, but the idea of a thread not waking up or signal not getting correctly delivered seems plausible to my simple end-user mind. once again, if this kind of pseudo-code sounds familiar to someone, please give me some hints which way to go to write a simple test-program to pinpoint the problem. Thank you very much for your time anyway. Regards, Arno -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 03:20:32 2005 Return-Path: X-Original-To: amd64@freeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21BCC16A41F for ; Sun, 27 Nov 2005 03:20:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EC1243D81 for ; Sun, 27 Nov 2005 03:20:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id F154B1A3C27 for ; Sat, 26 Nov 2005 19:20:13 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8D41D51584; Sat, 26 Nov 2005 22:20:12 -0500 (EST) Date: Sat, 26 Nov 2005 22:20:12 -0500 From: Kris Kennaway To: Kris Kennaway Message-ID: <20051127032012.GA86016@xor.obsecurity.org> References: <20051124232616.GA32023@xor.obsecurity.org> <20051126232244.GA83432@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <20051126232244.GA83432@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: amd64@freeBSD.org Subject: smp_tlb_shootdown loop (Re: spin lock smp rendezvous held by 0xffffff01250a7980 for > 5 seconds) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 03:20:32 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 26, 2005 at 06:22:45PM -0500, Kris Kennaway wrote: > On Thu, Nov 24, 2005 at 06:26:16PM -0500, Kris Kennaway wrote: > > I got this on a quad amd64 machine running 6.0-STABLE. At the time it > > was running 21 simultaneous tar extractions onto a sync-mounted md. > >=20 > > panic() at panic+0x1e6 > > _mtx_lock_spin() at _mtx_lock_spin+0xad > > pmap_invalidate_range() at pmap_invalidate_range+0xb3 > > pmap_qremove() at pmap_qremove+0x53 > > vfs_vmio_release() at vfs_vmio_release+0x1e0 > > getnewbuf() at getnewbuf+0x368 > > getblk() at getblk+0x3d9 > > ffs_balloc_ufs1() at ffs_balloc_ufs1+0x662 > > ffs_write() at ffs_write+0x31b > > VOP_WRITE_APV() at VOP_WRITE_APV+0xed > > vn_write() at vn_write+0x228 > > dofilewrite() at dofilewrite+0x90 > > kern_writev() at kern_writev+0x54 > > write() at write+0x4b Another CPU is here: smp_tlb_shootdown() at smp_tlb_shootdown+0x40 smp_invlpg_range() at smp_invlpg_range+0x1e pmap_invalidate_range() at pmap_invalidate_range+0xf9 pmap_qenter() at pmap_qenter+0x64 allocbuf() at allocbuf+0x9a0 getblk() at getblk+0x52d ffs_balloc_ufs1() at ffs_balloc_ufs1+0x662 ffs_write() at ffs_write+0x31b VOP_WRITE_APV() at VOP_WRITE_APV+0xed vn_write() at vn_write+0x228 dofilewrite() at dofilewrite+0x90 kern_writev() at kern_writev+0x54 write() at write+0x4b syscall() at syscall+0x404 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (4, FreeBSD ELF64, write), rip =3D 0x80070ea6c, rsp =3D 0x7ffff= fffe6a8, rbp =3D 0x52a800 --- - It is looping: smp_tlb_shootdown+0x40: repe nop smp_tlb_shootdown+0x42: movl 0x21c4f8,%eax smp_tlb_shootdown+0x48: cmpl %ebx,%eax smp_tlb_shootdown+0x4a: jb smp_tlb_shootdown+0x40 smp_tlb_shootdown(u_int vector, vm_offset_t addr1, vm_offset_t addr2) { u_int ncpu; ncpu =3D mp_ncpus - 1; /* does not shootdown self */ if (ncpu < 1) return; /* no other cpus */ mtx_assert(&smp_ipi_mtx, MA_OWNED); smp_tlb_addr1 =3D addr1; smp_tlb_addr2 =3D addr2; atomic_store_rel_int(&smp_tlb_wait, 0); ipi_all_but_self(vector); while (smp_tlb_wait < ncpu) ia32_pause(); } which seems to be the while loop at the end. db> x/x smp_tlb_wait smp_tlb_wait: 1 db> x mp_ncpus mp_ncpus: 4 So it looks like it's stuck waiting for the tlb shootdown on the other processors. However, the 3 other CPUs are all in the same place: > _mtx_lock_spin() at _mtx_lock_spin+0x6b > getit() at getit+0x6f > DELAY() at DELAY+0x44 > _mtx_lock_spin() at _mtx_lock_spin+0x6b > pmap_invalidate_range() at pmap_invalidate_range+0xb3 > pmap_qremove() at pmap_qremove+0x53 > vfs_vmio_release() at vfs_vmio_release+0x1e0 > getnewbuf() at getnewbuf+0x368 > getblk() at getblk+0x3d9 > ffs_balloc_ufs1() at ffs_balloc_ufs1+0x662 > ffs_write() at ffs_write+0x31b > VOP_WRITE_APV() at VOP_WRITE_APV+0xed > vn_write() at vn_write+0x228 > dofilewrite() at dofilewrite+0x90 > kern_writev() at kern_writev+0x54 > write() at write+0x4b > syscall() at syscall+0x404 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (4, FreeBSD ELF64, write), rip =3D 0x80070ea6c, rsp =3D 0x7ff= fffffe6a8, rbp =3D 0x52ae00 --- >=20 > i.e. the first _mtx_lock_spin() tried to acquire the ipi lock and > spun, which called DELAY and getit, which tried to acquire the clock > lock: >=20 > mtx_lock_spin(&clock_lock); >=20 > which *also* spun, and called DELAY...and at that point things went to > hell and it recursed until it blew out the stack. So why aren't they processing the IPI? Was the IPI lost somehow? Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiSXrWry0BWjoQKURApEbAJ9GfAv+JVE6KdBEigKU/Dh9WGbAoACgkcks vsIgmV7M7nBQC8H6QFDtgYg= =0l2N -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 04:30:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14FEB16A426 for ; Sun, 27 Nov 2005 04:30:37 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8D6543D53 for ; Sun, 27 Nov 2005 04:30:36 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from [192.168.1.109] (pcp0011002249pcs.longhl01.md.comcast.net[68.55.192.50]) by comcast.net (sccrmhc13) with ESMTP id <200511270424590130039hl2e>; Sun, 27 Nov 2005 04:24:59 +0000 From: Derrick Edwards To: freebsd-amd64@freebsd.org Date: Sat, 26 Nov 2005 23:24:25 -0500 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511262324.26247.dantavious@comcast.net> Subject: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 04:30:37 -0000 All, I am also having this problem. I even tried 3 times. I read the previous post and I would like to know the procedure for this solution. "You could boot and install as i386 and cross-build your way into amd64 land. It's pretty straightforward." Not exactly sure where to start. Thanks Derrick From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 05:44:44 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20CCC16A41F for ; Sun, 27 Nov 2005 05:44:44 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AD5443D49 for ; Sun, 27 Nov 2005 05:44:43 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1880533wxc for ; Sat, 26 Nov 2005 21:44:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HQ/049+ROgeEuh7k6LeQQQ3yLKJlsSmq9l2n/a2Y+6bpZHxiGKJByX4xnljWNrAVriMM6wJVrcyNol2WVryg5BHks3dJC/gR5hpz2Z3jMZCqkgsX07CS8FUdx/HvwV459X8murbNd5G9INxiPcns3Rv2PXlnUO7f/7+kwcCs3ic= Received: by 10.70.54.16 with SMTP id c16mr3742019wxa; Sat, 26 Nov 2005 21:44:43 -0800 (PST) Received: by 10.70.105.13 with HTTP; Sat, 26 Nov 2005 21:44:43 -0800 (PST) Message-ID: <84dead720511262144s1602a2efl8628d626766396ad@mail.gmail.com> Date: Sun, 27 Nov 2005 11:14:43 +0530 From: Joseph Koshy To: Derrick Edwards In-Reply-To: <200511262324.26247.dantavious@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511262324.26247.dantavious@comcast.net> Cc: freebsd-amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 05:44:44 -0000 de> "You could boot and install as i386 and cross-build your way de> into amd64 land. It's pretty straightforward." de> Not exactly sure where to start. Here: http://edoofus.blogspot.com/2005/10/cross-building-freebsd.html But I'd only recommend doing this if you are familiar with natively building FreeBSD from source. It might be too much of an adventure for someone who is new to the build system. It may be worthwhile digging deeper into the CD boot failure problem. This only seems to affect the amd64 release CD: 1) Does your ISO image have the correct MD5 and SHA256 checksums? Checksums are here: http://www.freebsd.org/releases/6.0R/announce.html 2) What's your hardware like (the dmesg from an i386 boot would be useful). Is this one of the known good motherboards? http://www.freebsd.org/platforms/amd64/motherboards.html 3) What are the symptoms when trying to boot from the AMD64 CD? Do you get to the point where the amd64 kernel is launched? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 06:55:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C866D16A420 for ; Sun, 27 Nov 2005 06:55:26 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CBD643D82 for ; Sun, 27 Nov 2005 06:55:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAR6reOR063070; Sat, 26 Nov 2005 23:53:41 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438957FB.7040808@samsco.org> Date: Sat, 26 Nov 2005 23:53:47 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derrick Edwards References: <200511262324.26247.dantavious@comcast.net> In-Reply-To: <200511262324.26247.dantavious@comcast.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 06:55:26 -0000 Derrick Edwards wrote: > All, > I am also having this problem. I even tried 3 times. I read the previous post > and I would like to know the procedure for this solution. > > "You could boot and install as i386 and cross-build your way into amd64 land. > It's pretty straightforward." > > Not exactly sure where to start. > Thanks > Derrick I'm a little worried by the number of reports of this. Can you send information on your motherboard, BIOS, and cdrom? Scott From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 14:36:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47B5616A41F for ; Sun, 27 Nov 2005 14:36:32 +0000 (GMT) (envelope-from nicca64@srt.com) Received: from nigel.srt.com (nigel.srt.com [216.221.96.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E7F043D60 for ; Sun, 27 Nov 2005 14:36:31 +0000 (GMT) (envelope-from nicca64@srt.com) Received: from [192.168.1.102] (dsl-119-235.srtnet.com [216.221.119.235]) (authenticated bits=0) by nigel.srt.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jAREaOKl008224 for ; Sun, 27 Nov 2005 08:36:24 -0600 Message-ID: <4389C471.1090603@srt.com> Date: Sun, 27 Nov 2005 08:36:33 -0600 From: Christopher Thomas User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) 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: Re: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 14:36:32 -0000 Derrick Edwards wrote: >> All, >> I am also having this problem. I even tried 3 times. I read the previous post >> and I would like to know the procedure for this solution. >> >> "You could boot and install as i386 and cross-build your way into amd64 land. >> It's pretty straightforward." >> >> Not exactly sure where to start. >> Thanks >> Derrick > > I too am having this problem with 6.0-release amd64. Posted about this in my Lanparty UT NF4 Ultra-D thread. Not sure if its the same problem as this gent is having. But a problem none-the-less. --I'm a little worried by the number of reports of this. Can you send --information on your motherboard, BIOS, and cdrom? --Scott To add to a potential non-working amd64 database. Here is my specs as well. (Considering I'm not the only one.) Lanparty UT NF4 Ultra-D AMD64 3500+ 1GB GeIL DDR 400 NEC DVD-RW BIOS: Phoenix - Award WorkstationBIOS Although I think a problem with mine might have been the ataraid module trying to load at boot, but I'm not sure and at this point, unable to retest the issue. Hope this helps, Christopher Thomas From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 16:07:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7548616A426 for ; Sun, 27 Nov 2005 16:07:32 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E03CE43D6E for ; Sun, 27 Nov 2005 16:07:27 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jARG7PND068031; Sun, 27 Nov 2005 09:07:26 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4389D9C5.1000908@samsco.org> Date: Sun, 27 Nov 2005 09:07:33 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Thomas References: <4389C471.1090603@srt.com> In-Reply-To: <4389C471.1090603@srt.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 16:07:32 -0000 Christopher Thomas wrote: > Derrick Edwards wrote: > >>> All, I am also having this problem. I even tried 3 times. I read >>> the previous post and I would like to know the procedure for this >>> solution. >>> >>> "You could boot and install as i386 and cross-build your way into >>> amd64 land. >>> It's pretty straightforward." >>> >>> Not exactly sure where to start. >>> Thanks Derrick >> >> >> > I too am having this problem with 6.0-release amd64. Posted about this > in my Lanparty UT NF4 Ultra-D thread. Not sure if its the same problem > as this gent is having. But a problem none-the-less. > > --I'm a little worried by the number of reports of this. Can you send > --information on your motherboard, BIOS, and cdrom? > --Scott > > To add to a potential non-working amd64 database. Here is my specs as > well. (Considering I'm not the only one.) > > Lanparty UT NF4 Ultra-D > AMD64 3500+ > 1GB GeIL DDR 400 > NEC DVD-RW > BIOS: Phoenix - Award WorkstationBIOS > > Although I think a problem with mine might have been the ataraid module > trying to load at boot, but I'm not sure and at this point, unable to > retest the issue. > Hope this helps, > Christopher Thomas > Ok, sorry if I'm asking you to repeat, but where exactly does it stop working? Scott From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 18:31:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAB4B16A41F for ; Sun, 27 Nov 2005 18:31:48 +0000 (GMT) (envelope-from surija@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3161E43D45 for ; Sun, 27 Nov 2005 18:31:48 +0000 (GMT) (envelope-from surija@gmail.com) Received: by xproxy.gmail.com with SMTP id h27so2277107wxd for ; Sun, 27 Nov 2005 10:31:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=og6ui0sbMme1t3l/CAh8U7vPV5AhgJqB6JXEr2Tth77geVu7aT4Sfxf6XuhiJXSXhb3P95pdxdiwdADuhBF99mWW4nu156vu6gmtnfxuOhEsQnHFd0rwKDr0kUIqXh3HT/+r8zI3ZrXGre53KoUi9JYIdqP3P2BYgm/zgz2Pl0c= Received: by 10.64.149.1 with SMTP id w1mr627685qbd; Sun, 27 Nov 2005 10:31:47 -0800 (PST) Received: by 10.64.208.8 with HTTP; Sun, 27 Nov 2005 10:31:47 -0800 (PST) Message-ID: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> Date: Sun, 27 Nov 2005 13:31:47 -0500 From: Ranko Sredojevic To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 18:31:48 -0000 Hi all! Since I'm not sure where these should go, I'm putting them here, and someone might give me directions to another list if appropriate. Couple of questions now: (1) Octave build is finally over and I'm trying it out. It took around 16 hours on athlon 3200+/1GB for the record. SciLab won't build. It gives message that gcc3.?.? (I forgot the number) is needed and that this is unavailable for amd64. Any cure? (2) What are these. I did quick search on google and archives but couldn't locate more than a page in italian (which I, unfortunately, still don't understand= ) so I have to ask here: Nov 25 18:46:14 svarga kernel: pid 14597 (xdfc), uid 0: exited on signal 11 (core dumped) Nov 25 20:00:19 svarga kernel: pid 32872 (xsfc), uid 0: exited on signal 11 (core dumped) Nov 25 20:01:53 svarga kernel: pid 33385 (xsfc), uid 0: exited on signal 11 (core dumped) Nov 25 20:04:08 svarga kernel: pid 33984 (xsfc), uid 0: exited on signal 11 (core dumped) Nov 25 20:50:03 svarga kernel: pid 46735 (xzfc), uid 0: exited on signal 11 (core dumped) Nov 25 21:47:09 svarga kernel: pid 63517 (xcfc), uid 0: exited on signal 11 (core dumped) Nov 25 21:48:47 svarga kernel: pid 64276 (xcfc), uid 0: exited on signal 11 (core dumped) I noticed these in my messages file when I tried to see why printing is not working so I wanted to see if lpd logged something here (along with lpd-errs)... I have no idea what are these (X-related?). System is, generally running fine. I haven't experienced crashes so far. Occasionally I get "application quit unexpectedly" from evolution or one of ps/pdf viewers but rarely. Any ideas? I'm on RELENG_6_0 with GENERIC kernel (still didn't have time to compile my own...). (3) lpd/lpq acts somewhat strangely I followed instructions to set up printing to the network printer... It worked very well. Although, I'd like to know why LPQ "hangs" ... if I send something for printing: $ lpr output.ps $ lpq Rank Owner Job Files Total Size 1st rasha 25 output.ps 1450287 bytes and it is not letting me back to the comman line... until I do ^C ? cheers, rasha From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 18:46:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E30416A41F for ; Sun, 27 Nov 2005 18:46:24 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr3.xs4all.nl (smtp-vbr3.xs4all.nl [194.109.24.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3094943D7E for ; Sun, 27 Nov 2005 18:46:14 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr3.xs4all.nl (8.13.3/8.13.3) with ESMTP id jARIkDbu081207; Sun, 27 Nov 2005 19:46:13 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id D4BF5B84B; Sun, 27 Nov 2005 19:46:12 +0100 (CET) Date: Sun, 27 Nov 2005 19:46:12 +0100 From: Roland Smith To: Ranko Sredojevic Message-ID: <20051127184612.GA93799@slackbox.xs4all.nl> Mail-Followup-To: Ranko Sredojevic , freebsd-amd64@freebsd.org References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 18:46:24 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 27, 2005 at 01:31:47PM -0500, Ranko Sredojevic wrote: > Hi all! >=20 > Since I'm not sure where these should go, I'm putting them here, and > someone might give me directions to another list if appropriate. >=20 > Couple of questions now: >=20 > (1) Octave build is finally over and I'm trying it out. It took around 16 > hours on athlon > 3200+/1GB for the record. A lot of that time is for the atlas library. If you already have that installed, octave builds a lot faster. =20 > SciLab won't build. It gives message that gcc3.?.? (I forgot the number) = is > needed > and that this is unavailable for amd64. Any cure? According to the port's Makefile, scilab doesn't work with GCC 3.3, and then asks for GCC 3.2, which doesn't seem to work on amd64. Since 6.0 uses GCC 3.4, try removing the following lines from the port's makefile, and see if it works: # Scilab broken with GCC 3.3 on FreeBSD 5.3 =2Eif ${OSVERSION} >=3D 503000 USE_GCC=3D 3.2 =2Eendif > (2) What are these. I did quick search on google and archives but couldn't > locate > more than a page in italian (which I, unfortunately, still don't understa= nd) > so I have > to ask here: > Nov 25 21:48:47 svarga kernel: pid 64276 (xcfc), uid 0: exited on signal = 11 > (core dumped) IIRC, they are test programs from the atlas build. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDif70EnfvsMMhpyURAi+0AJ4nSayFJndBShCegJ/XgqwTZQSZzwCfchqb 18hCTT1lwWxuiYvrvdGwCd0= =yI4e -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd-- From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 20:10:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1068416A41F for ; Sun, 27 Nov 2005 20:10:48 +0000 (GMT) (envelope-from surija@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51D4743D45 for ; Sun, 27 Nov 2005 20:10:31 +0000 (GMT) (envelope-from surija@gmail.com) Received: by xproxy.gmail.com with SMTP id s11so2402864wxc for ; Sun, 27 Nov 2005 12:10:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=HuCvpVy7TCbFX610szQpJZXcfOFI769oJAnG04SBmS9Fl1r0L/eluoeKZ5sSFRuJpxoTl5NwOsAEbuJGxbREOqrxUOj+g5lt/U5S23Kg4XFga8rlP0W67ZAhCydVZNG6hTq3Y57ePG1RrXIjh+pdXJgzmqr/anNv2BIgzh/4w+I= Received: by 10.64.249.18 with SMTP id w18mr2618303qbh; Sun, 27 Nov 2005 12:10:29 -0800 (PST) Received: by 10.64.208.8 with HTTP; Sun, 27 Nov 2005 12:10:29 -0800 (PST) Message-ID: <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> Date: Sun, 27 Nov 2005 15:10:29 -0500 From: Ranko Sredojevic To: Ranko Sredojevic , freebsd-amd64@freebsd.org In-Reply-To: <20051127184612.GA93799@slackbox.xs4all.nl> MIME-Version: 1.0 References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> <20051127184612.GA93799@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 20:10:48 -0000 On 11/27/05, Roland Smith wrote: > > On Sun, Nov 27, 2005 at 01:31:47PM -0500, Ranko Sredojevic wrote: > > Hi all! > > > > Since I'm not sure where these should go, I'm putting them here, and > > someone might give me directions to another list if appropriate. > > > > Couple of questions now: > > > > (1) Octave build is finally over and I'm trying it out. It took around > 16 > > hours on athlon > > 3200+/1GB for the record. > > A lot of that time is for the atlas library. If you already have that > installed, octave builds a lot faster. > > > SciLab won't build. It gives message that gcc3.?.? (I forgot the number= ) > is > > needed > > and that this is unavailable for amd64. Any cure? > > According to the port's Makefile, scilab doesn't work with GCC > 3.3, and then asks for GCC 3.2, which doesn't seem to work on amd64. > Since 6.0 uses GCC 3.4, try removing the following lines from the > port's makefile, and see if it works: > > # Scilab broken with GCC 3.3 on FreeBSD 5.3 > .if ${OSVERSION} >=3D 503000 > USE_GCC=3D 3.2 > .endif It compiles (I actually changed 503000 to 600000 and 3.2 to 3.4). No problems... It loads fine, without any problems. Couple quick calculations also went fine. I guess it works... Any ideas on lpd/lpq problem? I sent various things out to print... More or less succesfully... :\ I use the simplest filter: cat, trying to send .ps to the printer. Sometime= s it prints the whole document... sometimes just part of it... (for longer ones) I haven't manage= d to get more than 8 pages (4 sheets) in one print? Any ideas? rasha From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 20:28:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96AAC16A41F for ; Sun, 27 Nov 2005 20:28:04 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3C8D43D6A for ; Sun, 27 Nov 2005 20:28:01 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (ap6.matik.com.br [200.152.83.36] (may be forged)) by msrv.matik.com.br (8.13.3/8.13.1) with ESMTP id jARKS0wh027786 for ; Sun, 27 Nov 2005 18:28:01 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Sun, 27 Nov 2005 18:28:01 -0200 User-Agent: KMail/1.8.3 References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> <20051127184612.GA93799@slackbox.xs4all.nl> <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> In-Reply-To: <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511271828.01193.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 20:28:04 -0000 On Sunday 27 November 2005 18:10, Ranko Sredojevic wrote: > Any ideas on lpd/lpq problem? I sent various things out to print... More = or > less succesfully... :\ > I use the simplest filter: cat, trying to send .ps to the printer. > Sometimes it prints the whole > document... sometimes just part of it... (for longer ones) I haven't > managed to get more > than 8 pages (4 sheets) in one print? Any ideas? > may be still this annoying thing: hw.intr_storm_threshold setting to 3000000 (correct 3 million) I could finally print on 5.4=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 21:47:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7B1616A420 for ; Sun, 27 Nov 2005 21:47:37 +0000 (GMT) (envelope-from surija@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4C2943D60 for ; Sun, 27 Nov 2005 21:47:33 +0000 (GMT) (envelope-from surija@gmail.com) Received: by zproxy.gmail.com with SMTP id z3so1984538nzf for ; Sun, 27 Nov 2005 13:47:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=DmFZgLlWhTjXQ+XnrJjlyxr+eNwUOcP6M6Fwe41AQbvU3ieAr9TZ2p0ecbQI0G62TXprU6HKbC5mDbHNcnPCvMEL3Sfl3X34CgboKJdE+z3kkPc0SdN7zNSG7eoPb5NiaWKTtXll+LT5Ln6vFbD6/26FfuB8gkFy6WLb/t2mud0= Received: by 10.64.249.18 with SMTP id w18mr2690289qbh; Sun, 27 Nov 2005 13:47:33 -0800 (PST) Received: by 10.64.208.8 with HTTP; Sun, 27 Nov 2005 13:47:33 -0800 (PST) Message-ID: <21bc91010511271347x629ae848sf6567e7d3a6ebc2f@mail.gmail.com> Date: Sun, 27 Nov 2005 16:47:33 -0500 From: Ranko Sredojevic To: freebsd-amd64@freebsd.org In-Reply-To: <21bc91010511271334u44e29839n3b3f06e0e7f15445@mail.gmail.com> MIME-Version: 1.0 References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> <20051127184612.GA93799@slackbox.xs4all.nl> <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> <200511271828.01193.joao@matik.com.br> <21bc91010511271334u44e29839n3b3f06e0e7f15445@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fwd: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 21:47:38 -0000 ---------- Forwarded message ---------- From: Ranko Sredojevic Date: Nov 27, 2005 4:34 PM Subject: Re: directions To: JoaoBR On 11/27/05, JoaoBR wrote: > > On Sunday 27 November 2005 18:10, Ranko Sredojevic wrote: > > Any ideas on lpd/lpq problem? I sent various things out to print... Mor= e > or > > less succesfully... :\ > > I use the simplest filter: cat, trying to send .ps to the printer. > > Sometimes it prints the whole > > document... sometimes just part of it... (for longer ones) I haven't > > managed to get more > > than 8 pages (4 sheets) in one print? Any ideas? > > > > may be still this annoying thing: > > hw.intr_storm_threshold > > setting to 3000000 (correct 3 million) I could finally print on 5.4 Made it a little faster... but I still don't get it prited completely. Sometimes, it just doesn't do anything at all... I got this error when I sent document for printing right after printing of previous (partial printig :) ) was done (printer idle - according to lpc): (this was printed out... not a message on screen): ERROR NAME; configurationerror COMMAND; setpagedevice OPERAND STACK; --dicttype-- rasha P.S. Sorry... I clicked reply but didn't see that it is your address, and not the list... From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 22:28:15 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C490716A42B for ; Sun, 27 Nov 2005 22:28:15 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B55243E11 for ; Sun, 27 Nov 2005 22:27:10 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.13.3/8.13.3) with ESMTP id jARMQZCX016777; Sun, 27 Nov 2005 23:26:35 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id A644EB84B; Sun, 27 Nov 2005 23:26:34 +0100 (CET) Date: Sun, 27 Nov 2005 23:26:34 +0100 From: Roland Smith To: Ranko Sredojevic Message-ID: <20051127222634.GB97673@slackbox.xs4all.nl> Mail-Followup-To: Ranko Sredojevic , freebsd-amd64@freebsd.org References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> <20051127184612.GA93799@slackbox.xs4all.nl> <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline In-Reply-To: <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 22:28:16 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 27, 2005 at 03:10:29PM -0500, Ranko Sredojevic wrote: > Any ideas on lpd/lpq problem? I sent various things out to print... More = or > less succesfully... :\ > I use the simplest filter: cat, trying to send .ps to the printer. Someti= mes > it prints the whole > document... sometimes just part of it... (for longer ones) I haven't mana= ged > to get more > than 8 pages (4 sheets) in one print? Any ideas? Is it a parallel port printer? If so, set your parallel port into polling mode: lptcontrol -p -d /dev/lpt0.ctl If that works, set the following in /boot/device.hints: hint.ppc.0.flags=3D"0x20" and it will be put into polling mode at boot. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDijKaEnfvsMMhpyURAhNFAKCrFPohXNdRorrsBIuBKxaB1hAllQCfTlAB YVZkUlIOyufRQGdAWbzonn4= =oNPI -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb-- From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 27 23:06:13 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A37116A41F for ; Sun, 27 Nov 2005 23:06:13 +0000 (GMT) (envelope-from surija@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80F8C43D4C for ; Sun, 27 Nov 2005 23:06:12 +0000 (GMT) (envelope-from surija@gmail.com) Received: by zproxy.gmail.com with SMTP id q3so2145243nzb for ; Sun, 27 Nov 2005 15:06:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ThgLqKdNOm/xW/9gwZpoUHhdjjLnLAjT+7PkKb8+usf3/MI+Vut+ifj84ceUemuCIaZMRiGPu9w9m2898wqo8mbkHiyL9sK4NcStHLFAQBnK1wb1+HDjO0/54Z1iQ7qiM9XkMZsQqsWw9NOqxW2I5eCWjUF/ZhjzpFeto0W/mwM= Received: by 10.65.181.10 with SMTP id i10mr5480032qbp; Sun, 27 Nov 2005 15:06:11 -0800 (PST) Received: by 10.64.208.8 with HTTP; Sun, 27 Nov 2005 15:06:11 -0800 (PST) Message-ID: <21bc91010511271506l5bf716dcq666f1819d5fa9356@mail.gmail.com> Date: Sun, 27 Nov 2005 18:06:11 -0500 From: Ranko Sredojevic To: Ranko Sredojevic , freebsd-amd64@freebsd.org In-Reply-To: <20051127222634.GB97673@slackbox.xs4all.nl> MIME-Version: 1.0 References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> <20051127184612.GA93799@slackbox.xs4all.nl> <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> <20051127222634.GB97673@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Nov 2005 23:06:13 -0000 On 11/27/05, Roland Smith wrote: > > On Sun, Nov 27, 2005 at 03:10:29PM -0500, Ranko Sredojevic wrote: > > > Any ideas on lpd/lpq problem? I sent various things out to print... Mor= e > or > > less succesfully... :\ > > I use the simplest filter: cat, trying to send .ps to the printer. > Sometimes > > it prints the whole > > document... sometimes just part of it... (for longer ones) I haven't > managed > > to get more > > than 8 pages (4 sheets) in one print? Any ideas? > > Is it a parallel port printer? If so, set your parallel port into > polling mode: lptcontrol -p -d /dev/lpt0.ctl > > If that works, set the following in /boot/device.hints: > > hint.ppc.0.flags=3D"0x20" > > and it will be put into polling mode at boot. No, it is network printer... Sorry, I forgot to mention. Some documents (smaller ones) it prints fine. Some other: it just doesn't print ... or prints the error message I already sent ... or part of it... depends on mood I guess :) rasha From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 01:53:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CB4816A41F for ; Mon, 28 Nov 2005 01:53:14 +0000 (GMT) (envelope-from surija@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6A4443D53 for ; Mon, 28 Nov 2005 01:53:07 +0000 (GMT) (envelope-from surija@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so776646nzo for ; Sun, 27 Nov 2005 17:53:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=m24eMUUFtw2lT4D2HmwIUeEuq5+AttlwvlTmuUeBSSuJ66Xxarx+HsnM1gycFMuvvp2hAZcOviss4JTnXNMo242ms4Qp3jSdYqmDPVamtL152EsNI6SUaOCcM7Xii73C10QWbEPVRkK0PTP+cfrqlb5KIhuxrMfmSpGWwliBvGQ= Received: by 10.65.214.4 with SMTP id r4mr869261qbq; Sun, 27 Nov 2005 17:53:06 -0800 (PST) Received: by 10.64.208.8 with HTTP; Sun, 27 Nov 2005 17:53:05 -0800 (PST) Message-ID: <21bc91010511271753u53a69486y5d2c7439495e352a@mail.gmail.com> Date: Sun, 27 Nov 2005 20:53:06 -0500 From: Ranko Sredojevic To: Ranko Sredojevic , freebsd-amd64@freebsd.org In-Reply-To: <21bc91010511271506l5bf716dcq666f1819d5fa9356@mail.gmail.com> MIME-Version: 1.0 References: <21bc91010511271031y6357b2f0ue2891afbe71b83f4@mail.gmail.com> <20051127184612.GA93799@slackbox.xs4all.nl> <21bc91010511271210k35ccd954ic16d168e8c6d155a@mail.gmail.com> <20051127222634.GB97673@slackbox.xs4all.nl> <21bc91010511271506l5bf716dcq666f1819d5fa9356@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: directions X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 01:53:14 -0000 On 11/27/05, Ranko Sredojevic wrote: > > > > On 11/27/05, Roland Smith wrote: > > > > On Sun, Nov 27, 2005 at 03:10:29PM -0500, Ranko Sredojevic wrote: > > > > > Any ideas on lpd/lpq problem? I sent various things out to print... > > More or > > > less succesfully... :\ > > > I use the simplest filter: cat, trying to send .ps to the printer. > > Sometimes > > > it prints the whole > > > document... sometimes just part of it... (for longer ones) I haven't > > managed > > > to get more > > > than 8 pages (4 sheets) in one print? Any ideas? > > > > Is it a parallel port printer? If so, set your parallel port into > > polling mode: lptcontrol -p -d /dev/lpt0.ctl > > > > If that works, set the following in /boot/device.hints: > > > > hint.ppc.0.flags=3D"0x20" > > > > and it will be put into polling mode at boot. > > > No, it is network printer... Sorry, I forgot to mention. > > Some documents (smaller ones) it prints fine. Some other: it just > doesn't print ... or prints the error message I already sent ... or part > of it... depends on mood I guess :) > > rasha > > > This seems to be printer/PS problem. It seems that LPD delivers all the data properly, but for some reason, .ps files that I tried to send are not printable (at least the printer thinks so). I generated these from the .pdf files through xpdf or PostScriptViewer and most of time they are good. Unfortunately this one just won't print. Should I try some other software to generate .ps or try printig as a picture, would it help? The error is mentioned in connection with wrong paper size or some other configuration during printing, but I couldn't find more details so far... rasha From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 02:47:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B646C16A41F for ; Mon, 28 Nov 2005 02:47:10 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C37543D49 for ; Mon, 28 Nov 2005 02:47:10 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from [192.168.1.109] (pcp0011002249pcs.longhl01.md.comcast.net[68.55.192.50]) by comcast.net (sccrmhc11) with ESMTP id <200511280246590110008e4de>; Mon, 28 Nov 2005 02:47:04 +0000 From: Derrick Edwards To: freebsd-amd64@freebsd.org Date: Sun, 27 Nov 2005 21:46:47 -0500 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511272146.48247.dantavious@comcast.net> Subject: FreeBSD amd 64 and VMWARE issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 02:47:10 -0000 Hi, I am trying to install FreeBSD amd 6.0 release as a guest operating system on VMWARE 5.0. I have a ABIT KU8 motherboard and AMD 64 anthlon 3700. If I install Freebsd 6 amd 64 by itself I works great. I only get the following error when installing it in VMWARE. Please help v/r Derrick iint=0000000d err=00000000 efl=00010006 eip=00027995 eax=00000100 ebx=00000000 ecx=c0000080 edx=00000000 esi=00036000 edi=00035000 ebp=000948a4 esp=0009e870 cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 cs:eip:0f 30 of 20 e0 83 30-of 22 e0 b8 00 f0 03 00 0f 22 d8 0f 20 c0 0d 00-00 00 80 0f 22 c0 b8 00 ss:esp:69 95 00 00 00 20 d7 00-00 30 d7 00 00 00 10 04 00 00 00 00 00 00 00 04 00-00 00 00 00 20 d7 00 BTX Halted From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 02:59:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D3F16A420 for ; Mon, 28 Nov 2005 02:59:25 +0000 (GMT) (envelope-from dfeustel@verizon.net) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F5CD43D46 for ; Mon, 28 Nov 2005 02:59:24 +0000 (GMT) (envelope-from dfeustel@verizon.net) Received: from [71.97.178.169] by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQN002ZR9MVSCR7@vms048.mailsrvcs.net> for freebsd-amd64@freebsd.org; Sun, 27 Nov 2005 20:59:20 -0600 (CST) Date: Sun, 27 Nov 2005 21:59:18 -0500 From: Dave Feustel In-reply-to: <200511272146.48247.dantavious@comcast.net> To: freebsd-amd64@freebsd.org Message-id: <200511272159.18551.dfeustel@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200511272146.48247.dantavious@comcast.net> User-Agent: KMail/1.7.2 Cc: Subject: Re: FreeBSD amd 64 and VMWARE issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfeustel@mindspring.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 02:59:25 -0000 Try using qemu (http://fabrice.bellard.free.fr/qemu/) instead and see if that works any better. Dave Feustel On Sunday 27 November 2005 21:46, Derrick Edwards wrote: > Hi, > I am trying to install FreeBSD amd 6.0 release as a guest operating system on > VMWARE 5.0. I have a ABIT KU8 motherboard and AMD 64 anthlon 3700. If I > install Freebsd 6 amd 64 by itself I works great. I only get the following > error when installing it in VMWARE. > Please help > v/r > Derrick > > iint=0000000d err=00000000 efl=00010006 eip=00027995 > eax=00000100 ebx=00000000 ecx=c0000080 edx=00000000 > esi=00036000 edi=00035000 ebp=000948a4 esp=0009e870 > cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 > cs:eip:0f 30 of 20 e0 83 30-of 22 e0 b8 00 f0 03 00 > 0f 22 d8 0f 20 c0 0d 00-00 00 80 0f 22 c0 b8 00 > ss:esp:69 95 00 00 00 20 d7 00-00 30 d7 00 00 00 10 04 00 > 00 00 00 00 00 00 04 00-00 00 00 00 20 d7 00 > BTX Halted > _______________________________________________ > 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" > -- Switch to Secure OpenBSD with a KDE desktop!!! NOW with Virtual PC OS support via QEMU and Beowulf clustering using PETSc and MPICH2! From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 06:22:26 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 300BC16A41F for ; Mon, 28 Nov 2005 06:22:26 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B93D43D69 for ; Mon, 28 Nov 2005 06:22:23 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep01.bredband.com with ESMTP id <20051128062222.CDPX18713.mxfep01.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se> for ; Mon, 28 Nov 2005 07:22:22 +0100 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id AACA0678DC for ; Mon, 28 Nov 2005 07:22:21 +0100 (CET) Message-ID: <438AA21E.2030702@gneto.com> Date: Mon, 28 Nov 2005 07:22:22 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 06:22:26 -0000 Hi list, I made some simple comparing of CPU performance between intel and AMD CPU:s on FreeBSD 6.0R The intent was to see how things like dualcore and Hyperthreading affects a rather CPU bound real world job. The results can be seen here: http://www.mullet.se/support/amd64-buildworld.html Please don't publish this anywhere else, I want to have your comments and a chance to fix any errors before I get slashdotted and flamed to hell :-) /Martin From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 09:50:55 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0A8116A41F for ; Mon, 28 Nov 2005 09:50:55 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9869143D5D for ; Mon, 28 Nov 2005 09:50:40 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Egfe5-0007OC-00; Mon, 28 Nov 2005 10:50:01 +0100 Message-ID: <438AD2C3.6090806@millennics.com> Date: Mon, 28 Nov 2005 10:49:55 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: Yikes! Dire trouble with 9500S-4 installation :((( X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 09:50:55 -0000 Hi all, Firstly: thanks a lot for all your replies, they were actually very helpful in deciding what to install, and I'll get back to them a bit further ahead in this message... However, unfortunately, last weekend Murphy struck, correction, he struck raised to the power of three. :( Firstly, we were hit by a blizzard over here on Friday, effectively knocking out most roads, and hence depriving Versatel of the means to install the new ADSL modem at our home. So, off to a bad start, I have been Internet-less at home as of last Wednesday, and it will not be before tomorrow that they'll install it. Furthermore, due to the same reason, the machine could not be delivered to my home on Friday. Secondly, on Saturday, the client and I made a brave effort to force luck our way by going to the site where the machine is at (not exactly straightforward due to the snow). When we were finally there, we could at least get some hands-on work done. A nice surprise for me was that the guy who normally assembles the machines was ill, so the client worked on that, while I read through the various messages regarding the 9500S-4 + FreeBSD 5.4 vs. 6, etc. When that was done, I had a strategy set out (FreeBSD 6.0 + MySQL 4.1.x built from the ports), and gave the client some help in assembling the machine. Once that was out of the way, I booted up the machine, configured the RAID 10 array as I would on any RAID controller (no surprises there), and then I decided to give FreeBSD 6 a go (I actually agree with Ray on preferring to stick with "non .0" versions, but given the other messages I gather that FreeBSD 6.0 has actually already been pounded on a lot). Surprise, surprise, stuff did not work as expected. Firstly, FreeBSD choked on the Gigabit NICs we had installed, and then on the RAID controller. I tried various things, removed the NICs, verified the RAID array from the controller's BIOS itself (checked out all ok), tried the various different settings with enabling/disabling the write cache etc., tried it with FreeBSD 5.4 and all to no avail. :(((( Very frustrating. To compound matters, it started to snow heavily again, so we had to dig the car out and head back for our living places. We decided to leave the machine at the client's site as we didn't want to risk it getting damaged and I didn't have Internet at home anyway. Nowwwww, does anyone have any ideas what could be wrong? To give a bit more detail, the machine has an Asus motherboard with 939 socket (dunno the number from memory (but if deemed relevant I can request it), but it's something like the K8N or A8N or so), and the processor is an Athlon dual core 4400. The 9500S-4 is installed in a normal 32-bit PCI slot, and I cannot see any hardware errors (FreeBSD recognises it as well), and the RAID verification went fine (though of course there is no data yet on the drives). The drives are Maxtor drives of 189Gb each (dunno the exact type number) and they were recognised properly by the controller. Yet, upon booting, it is very weird that the NICs (or at least one of them) and the 9500S-4 all gave trouble, especially since all of them are brand new. I _think_ we didn't make any errors in the assembly of the machine, but given the trouble I cannot be 100% sure. The errors given by FreeBSD 5.4 and 6 all seem to be related to the twa interrupt handler (I hope I identified that correctly). I didn't write down the very error messages, but I did Google them when I was over there and the only hits I found were basically the various sources of the driver. By doing a Google search just now, I found one such example at (note: this may not be the very driver that 5.4 or 6 uses, but it should indicate the same source of error): http://fxr.watson.org/fxr/source/dev/twa/tw_cl_intr.c The types of errors I saw passing by were things like: "Failed to fetch AEN" "Response queue empty" "Unposted command completed" I _think_ I've seen the first two, and I've definitely seen that last error message. When doing a more general search on these issues in Google using the terms "3ware freebsd twa interrupt", I found several more people who've had issues, but none of them sound like te very thing that happened to me. The nasty thing is that this goes wrong already upon booting from the installation CD and once FreeBSD enters sysinstall, it doesn't find any drives, so there's no chance for me to first install it and then fix the driver or so... Any help/ideas would be greatly appreciated.... Cheers, and thanks a lot in advance! Olafo PS: I didn't try booting in any other mode than the default one; perhaps one of the other modes works better??? From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 10:43:59 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7B4216A41F for ; Mon, 28 Nov 2005 10:43:59 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB61E43D58 for ; Mon, 28 Nov 2005 10:43:58 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jASAhvoK024995; Mon, 28 Nov 2005 12:43:57 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 20554-01-4; Mon, 28 Nov 2005 12:43:55 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jASAgqUU024929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Nov 2005 12:42:52 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jASAgrTX060113; Mon, 28 Nov 2005 12:42:53 +0200 (EET) (envelope-from ru) Date: Mon, 28 Nov 2005 12:42:53 +0200 From: Ruslan Ermilov To: Martin Nilsson Message-ID: <20051128104253.GB59977@ip.net.ua> References: <438AA21E.2030702@gneto.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: <438AA21E.2030702@gneto.com> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: amd64@FreeBSD.org Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 10:43:59 -0000 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 07:22:22AM +0100, Martin Nilsson wrote: > Hi list, >=20 > I made some simple comparing of CPU performance between intel and AMD=20 > CPU:s on FreeBSD 6.0R The intent was to see how things like dualcore and= =20 > Hyperthreading affects a rather CPU bound real world job. >=20 > The results can be seen here: > http://www.mullet.se/support/amd64-buildworld.html >=20 > Please don't publish this anywhere else, I want to have your comments=20 > and a chance to fix any errors before I get slashdotted and flamed to=20 > hell :-) >=20 For the starters, you're compiling two different sets of files, one for i386 and another for amd64. You'd better compare the same set. This can be done (approximately) by doing a cross-build for say i386: "make -jN buildworld TARGET_ARCH=3Di386". Also, given the amount of memory that you have in these machines, it shouldn't be a problem to put /usr/src and /usr/obj onto a memory disk. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDit8tqRfpzJluFF4RAjWxAJ0YvHOv+P9c9tflqUxT3RQhyndJGwCfcCFg wLN0pVxFs4S6tegyztkaPJo= =Q7qw -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 10:52:18 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B4A516A41F; Mon, 28 Nov 2005 10:52:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73EA043D5D; Mon, 28 Nov 2005 10:52:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4947D1A3C27; Mon, 28 Nov 2005 02:52:17 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5A61251527; Mon, 28 Nov 2005 05:52:16 -0500 (EST) Date: Mon, 28 Nov 2005 05:52:16 -0500 From: Kris Kennaway To: Ruslan Ermilov Message-ID: <20051128105215.GA16457@xor.obsecurity.org> References: <438AA21E.2030702@gneto.com> <20051128104253.GB59977@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <20051128104253.GB59977@ip.net.ua> User-Agent: Mutt/1.4.2.1i Cc: amd64@FreeBSD.org Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 10:52:18 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 12:42:53PM +0200, Ruslan Ermilov wrote: > On Mon, Nov 28, 2005 at 07:22:22AM +0100, Martin Nilsson wrote: > > Hi list, > >=20 > > I made some simple comparing of CPU performance between intel and AMD= =20 > > CPU:s on FreeBSD 6.0R The intent was to see how things like dualcore an= d=20 > > Hyperthreading affects a rather CPU bound real world job. > >=20 > > The results can be seen here: > > http://www.mullet.se/support/amd64-buildworld.html > >=20 > > Please don't publish this anywhere else, I want to have your comments= =20 > > and a chance to fix any errors before I get slashdotted and flamed to= =20 > > hell :-) > >=20 > For the starters, you're compiling two different sets of files, > one for i386 and another for amd64. You'd better compare the > same set. This can be done (approximately) by doing a cross-build > for say i386: "make -jN buildworld TARGET_ARCH=3Di386". Also, given > the amount of memory that you have in these machines, it shouldn't > be a problem to put /usr/src and /usr/obj onto a memory disk. That will only cross-compile on amd64; isn't it better to cross-compile a third party (e.g. sparc64) on both i386 and amd64? Also, you can get best performance by eliminating the hard disk altogether. This would most clearly show you any differences between the CPU and memory hardware. First build a (native) world, install it into a md (swap-backed, not malloc backed, and mount the filesystems async), mount devfs there and copy in your /etc, then copy in /usr/src (or put it in a new md so you can get concurrent access, although this may not be needed since a single md won't be saturated), and chroot to the md. Then run the cross-build. When I tried this for fun the other day on a 4-CPU amd64 machine it took a little over 15 minutes to buildworld. Kris --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiuFfWry0BWjoQKURAnoBAKChxgcsUV8mu9wpCv8r+9S7SbQeyACdEJgi jCKcAJPM3zMomE3Y9TSKlww= =KQx6 -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 11:02:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23EF616A41F for ; Mon, 28 Nov 2005 11:02:20 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1676D43D73 for ; Mon, 28 Nov 2005 11:01:57 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jASB1v0U088073 for ; Mon, 28 Nov 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jASB1ubE088067 for freebsd-amd64@freebsd.org; Mon, 28 Nov 2005 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 28 Nov 2005 11:01:56 GMT Message-Id: <200511281101.jASB1ubE088067@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 11:02:20 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step o [2005/11/17] amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMP o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/20] amd64/87748 amd64 can't initialize X o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre o [2005/11/19] amd64/89261 amd64 IPSec always causes panics on amd64 o [2005/11/24] amd64/89501 amd64 System crashes on install using ftp on lo o [2005/11/24] amd64/89503 amd64 Cant Boot Installation Disk o [2005/11/25] amd64/89546 amd64 [geom] GEOM error o [2005/11/25] amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o [2005/11/25] amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) 57 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] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/08/15] amd64/70500 amd64 [bge] bge driver for 3Com 3C996B on amd64 o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 [bge] [patch] FreeBSD 5.4 released versio o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported p [2005/07/20] amd64/83806 amd64 Can not compile /usr/src/lib/msun/amd64/f o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins 17 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 11:04:32 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2351816A424; Mon, 28 Nov 2005 11:04:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8848343D9B; Mon, 28 Nov 2005 11:04:08 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4DCB81A3C27; Mon, 28 Nov 2005 03:04:01 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4329C5158D; Mon, 28 Nov 2005 06:03:55 -0500 (EST) Date: Mon, 28 Nov 2005 06:03:52 -0500 From: Kris Kennaway To: Kris Kennaway Message-ID: <20051128110351.GA16593@xor.obsecurity.org> References: <438AA21E.2030702@gneto.com> <20051128104253.GB59977@ip.net.ua> <20051128105215.GA16457@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20051128105215.GA16457@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: amd64@FreeBSD.org, Ruslan Ermilov Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 11:04:32 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 05:52:16AM -0500, Kris Kennaway wrote: > On Mon, Nov 28, 2005 at 12:42:53PM +0200, Ruslan Ermilov wrote: > > On Mon, Nov 28, 2005 at 07:22:22AM +0100, Martin Nilsson wrote: > > > Hi list, > > >=20 > > > I made some simple comparing of CPU performance between intel and AMD= =20 > > > CPU:s on FreeBSD 6.0R The intent was to see how things like dualcore = and=20 > > > Hyperthreading affects a rather CPU bound real world job. > > >=20 > > > The results can be seen here: > > > http://www.mullet.se/support/amd64-buildworld.html > > >=20 > > > Please don't publish this anywhere else, I want to have your comments= =20 > > > and a chance to fix any errors before I get slashdotted and flamed to= =20 > > > hell :-) > > >=20 > > For the starters, you're compiling two different sets of files, > > one for i386 and another for amd64. You'd better compare the > > same set. This can be done (approximately) by doing a cross-build > > for say i386: "make -jN buildworld TARGET_ARCH=3Di386". Also, given > > the amount of memory that you have in these machines, it shouldn't > > be a problem to put /usr/src and /usr/obj onto a memory disk. >=20 > That will only cross-compile on amd64; isn't it better to > cross-compile a third party (e.g. sparc64) on both i386 and amd64? Actually, I don't think it matters..the compilers are still different on amd64 and i386, so you're comparing two different binaries and you don't know how different their performance is. It'll only be meaningful for comparisons within the same architecture (amd64 or i386), so you might as well not cross-build. Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiuQVWry0BWjoQKURAk5DAKCC1RyQzFOa8lJefhYRSaqFXJmKUQCg360U a2O5AVHyOHbznLQJg9fYFtw= =Tayz -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 11:16:47 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03B0D16A42B for ; Mon, 28 Nov 2005 11:16:47 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A59043D49 for ; Mon, 28 Nov 2005 11:15:26 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jASBFAbw026079; Mon, 28 Nov 2005 13:15:10 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 20653-04; Mon, 28 Nov 2005 13:15:07 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jASBAoFI025979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Nov 2005 13:10:51 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jASBAp7S060964; Mon, 28 Nov 2005 13:10:51 +0200 (EET) (envelope-from ru) Date: Mon, 28 Nov 2005 13:10:51 +0200 From: Ruslan Ermilov To: Kris Kennaway Message-ID: <20051128111051.GG58778@ip.net.ua> References: <438AA21E.2030702@gneto.com> <20051128104253.GB59977@ip.net.ua> <20051128105215.GA16457@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iJXiJc/TAIT2rh2r" Content-Disposition: inline In-Reply-To: <20051128105215.GA16457@xor.obsecurity.org> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: amd64@FreeBSD.org Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 11:16:47 -0000 --iJXiJc/TAIT2rh2r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 05:52:16AM -0500, Kris Kennaway wrote: > On Mon, Nov 28, 2005 at 12:42:53PM +0200, Ruslan Ermilov wrote: > > On Mon, Nov 28, 2005 at 07:22:22AM +0100, Martin Nilsson wrote: > > > Hi list, > > >=20 > > > I made some simple comparing of CPU performance between intel and AMD= =20 > > > CPU:s on FreeBSD 6.0R The intent was to see how things like dualcore = and=20 > > > Hyperthreading affects a rather CPU bound real world job. > > >=20 > > > The results can be seen here: > > > http://www.mullet.se/support/amd64-buildworld.html > > >=20 > > > Please don't publish this anywhere else, I want to have your comments= =20 > > > and a chance to fix any errors before I get slashdotted and flamed to= =20 > > > hell :-) > > >=20 > > For the starters, you're compiling two different sets of files, > > one for i386 and another for amd64. You'd better compare the > > same set. This can be done (approximately) by doing a cross-build > > for say i386: "make -jN buildworld TARGET_ARCH=3Di386". Also, given > > the amount of memory that you have in these machines, it shouldn't > > be a problem to put /usr/src and /usr/obj onto a memory disk. >=20 > That will only cross-compile on amd64; isn't it better to > cross-compile a third party (e.g. sparc64) on both i386 and amd64? >=20 As jkoshy@ has pointed out to me, the Intel CPUs present in this table support EMT64, so the author is probably running FreeBSD/amd64 on them and my point about cross-build doesn't make sense. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --iJXiJc/TAIT2rh2r Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiuW7qRfpzJluFF4RAmMeAJ95YWEgCuVEH4qcvKrAGa4HDtHxyQCfbYYH YPC1nUyCURTxfcwt1CQfMuw= =klr3 -----END PGP SIGNATURE----- --iJXiJc/TAIT2rh2r-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 12:18:55 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72ACA16A41F; Mon, 28 Nov 2005 12:18:55 +0000 (GMT) (envelope-from martin@gneto.com) Received: from av9-2-sn3.vrr.skanova.net (av9-2-sn3.vrr.skanova.net [81.228.9.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFDAE43D45; Mon, 28 Nov 2005 12:18:54 +0000 (GMT) (envelope-from martin@gneto.com) Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 81CF337EA6; Mon, 28 Nov 2005 13:18:53 +0100 (CET) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 2A6EB37E68; Mon, 28 Nov 2005 13:18:53 +0100 (CET) Received: from [192.168.2.30] (h99n2fls34o985.telia.com [213.66.202.99]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 179EF37E4C; Mon, 28 Nov 2005 13:18:52 +0100 (CET) Message-ID: <438AF5A8.8080009@gneto.com> Date: Mon, 28 Nov 2005 13:18:48 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <438AA21E.2030702@gneto.com> <20051128104253.GB59977@ip.net.ua> In-Reply-To: <20051128104253.GB59977@ip.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: amd64@FreeBSD.org Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 12:18:55 -0000 Ruslan Ermilov wrote: > For the starters, you're compiling two different sets of files, > one for i386 and another for amd64. You'd better compare the > same set. Que? I'm compiling the same thing, a full buildworld of FreeBSD 6.0/amd64. I'm even using the same disk/installation for all tests. (except the opteron). There is no i386 code here execpt the compatibility libraries. > This can be done (approximately) by doing a cross-build > for say i386: "make -jN buildworld TARGET_ARCH=i386". The we're using a 32-bit compiler in some tests and a 64-bit one in other tests what will that show? > Also, given the amount of memory that you have in these machines, > it shouldn't be a problem to put /usr/src and /usr/obj onto a > memory disk. I'll make a run with a mfs so I can see how much that will improve things. Please take another look at the page. /Martin From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 12:43:17 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CBFB16A420 for ; Mon, 28 Nov 2005 12:43:17 +0000 (GMT) (envelope-from martin@gneto.com) Received: from av12-1-sn2.hy.skanova.net (av12-1-sn2.hy.skanova.net [81.228.8.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F3FF43D72 for ; Mon, 28 Nov 2005 12:43:13 +0000 (GMT) (envelope-from martin@gneto.com) Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id 5737D38001; Mon, 28 Nov 2005 13:43:12 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id 293B537FF6; Mon, 28 Nov 2005 13:43:12 +0100 (CET) Received: from [192.168.2.30] (h99n2fls34o985.telia.com [213.66.202.99]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id CBECC37E44; Mon, 28 Nov 2005 13:43:11 +0100 (CET) Message-ID: <438AFB5B.8070303@gneto.com> Date: Mon, 28 Nov 2005 13:43:07 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <438AA21E.2030702@gneto.com> <20051128104253.GB59977@ip.net.ua> <20051128105215.GA16457@xor.obsecurity.org> In-Reply-To: <20051128105215.GA16457@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: amd64@FreeBSD.org Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 12:43:17 -0000 Kris Kennaway wrote: > the md. Then run the cross-build. When I tried this for fun the > other day on a 4-CPU amd64 machine it took a little over 15 minutes to > buildworld. What did you compile? How fast is your 4-CPU Opteron? The Dual 265 compiles 6.0/amd64 in ~21 minutes when using a single ATA100 disk. A 265 have the equal of two x44 cores so a box with four faster CPU:s with their own memory should compile in less time. Anyway I'll rerun the test on some of the boxes so we can see how much disk IO affects the result. /Martin From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 12:55:07 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 796A916A41F for ; Mon, 28 Nov 2005 12:55:07 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail5.redshift.com (mail5.redshift.com [216.228.2.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5EA943D45 for ; Mon, 28 Nov 2005 12:55:06 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 82852 invoked by uid 89); 28 Nov 2005 12:55:03 -0000 Received: by simscan 1.2.0 ppid: 82837, pid: 82838, t: 1.2571s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail5.redshift.com with SMTP; 28 Nov 2005 12:55:02 -0000 Message-Id: <3.0.1.32.20051128045500.00a47aa8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Mon, 28 Nov 2005 04:55:00 -0800 To: Olaf Greve From: ray@redshift.com In-Reply-To: <438AD2C3.6090806@millennics.com> References: <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: amd64@freebsd.org Subject: Re: Yikes! Dire trouble with 9500S-4 installation :((( X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 12:55:07 -0000 At 10:49 AM 11/28/2005 +0100, Olaf Greve wrote: | Hi all, | | Firstly: thanks a lot for all your replies, they were actually very | helpful in deciding what to install, and I'll get back to them a bit | further ahead in this message... | | However, unfortunately, last weekend Murphy struck, correction, he | struck raised to the power of three. :( | | Firstly, we were hit by a blizzard over here on Friday, effectively | knocking out most roads, and hence depriving Versatel of the means to | install the new ADSL modem at our home. So, off to a bad start, I have | been Internet-less at home as of last Wednesday, and it will not be | before tomorrow that they'll install it. Furthermore, due to the same | reason, the machine could not be delivered to my home on Friday. | | Secondly, on Saturday, the client and I made a brave effort to force | luck our way by going to the site where the machine is at (not exactly | straightforward due to the snow). When we were finally there, we could | at least get some hands-on work done. A nice surprise for me was that | the guy who normally assembles the machines was ill, so the client | worked on that, while I read through the various messages regarding the | 9500S-4 + FreeBSD 5.4 vs. 6, etc. When that was done, I had a strategy | set out (FreeBSD 6.0 + MySQL 4.1.x built from the ports), and gave the | client some help in assembling the machine. | | Once that was out of the way, I booted up the machine, configured the | RAID 10 array as I would on any RAID controller (no surprises there), | and then I decided to give FreeBSD 6 a go (I actually agree with Ray on | preferring to stick with "non .0" versions, but given the other messages | I gather that FreeBSD 6.0 has actually already been pounded on a lot). | | Surprise, surprise, stuff did not work as expected. Firstly, FreeBSD | choked on the Gigabit NICs we had installed, and then on the RAID | controller. I tried various things, removed the NICs, verified the RAID | array from the controller's BIOS itself (checked out all ok), tried the | various different settings with enabling/disabling the write cache etc., | tried it with FreeBSD 5.4 and all to no avail. :(((( | | Very frustrating. To compound matters, it started to snow heavily again, | so we had to dig the car out and head back for our living places. We | decided to leave the machine at the client's site as we didn't want to | risk it getting damaged and I didn't have Internet at home anyway. | | Nowwwww, does anyone have any ideas what could be wrong? To give a bit | more detail, the machine has an Asus motherboard with 939 socket (dunno | the number from memory (but if deemed relevant I can request it), but | it's something like the K8N or A8N or so), and the processor is an | Athlon dual core 4400. The 9500S-4 is installed in a normal 32-bit PCI | slot, and I cannot see any hardware errors (FreeBSD recognises it as | well), and the RAID verification went fine (though of course there is no | data yet on the drives). The drives are Maxtor drives of 189Gb each | (dunno the exact type number) and they were recognised properly by the | controller. | | Yet, upon booting, it is very weird that the NICs (or at least one of | them) and the 9500S-4 all gave trouble, especially since all of them are | brand new. I _think_ we didn't make any errors in the assembly of the | machine, but given the trouble I cannot be 100% sure. The errors given | by FreeBSD 5.4 and 6 all seem to be related to the twa interrupt handler | (I hope I identified that correctly). | | I didn't write down the very error messages, but I did Google them when | I was over there and the only hits I found were basically the various | sources of the driver. By doing a Google search just now, I found one | such example at (note: this may not be the very driver that 5.4 or 6 | uses, but it should indicate the same source of error): | http://fxr.watson.org/fxr/source/dev/twa/tw_cl_intr.c | The types of errors I saw passing by were things like: | "Failed to fetch AEN" | "Response queue empty" | "Unposted command completed" | | I _think_ I've seen the first two, and I've definitely seen that last | error message. | | When doing a more general search on these issues in Google using the | terms "3ware freebsd twa interrupt", I found several more people who've | had issues, but none of them sound like te very thing that happened to me. | | The nasty thing is that this goes wrong already upon booting from the | installation CD and once FreeBSD enters sysinstall, it doesn't find any | drives, so there's no chance for me to first install it and then fix the | driver or so... | | Any help/ideas would be greatly appreciated.... | | Cheers, and thanks a lot in advance! | Olafo | | PS: I didn't try booting in any other mode than the default one; perhaps | one of the other modes works better??? Hi Olaf, I've never run across any problem like that, although I've always only used two brands of motherboard for servers (supermicro & tyan). ASUS is also good however and if I used 3 brands, ASUS would probably be the next on my list of brands to use. Your problem sort of sounds like an IRQ conflict, but that's just a guess. You might try going into the BIOS on the motherboard and disabling/remove the NIC's for a moment and see if that makes any difference. I would also disable USB, the parallel printer port, and the serial port(s) in the BIOS if you don't need them. Even if you do need them, it might not be a bad idea to try that. My thinking is that this might free up some IRQ channels for the 3ware card (if there is in fact some conflict there). I would also make sure spread spectrum is disabled in the BIOS, since that can cause funny problems sometimes (it's a technology to limit or "cloak" RF coming from the machine - more or less - and you don't need it). I would also take the 3ware card out and try doing an install on the machine with a normal old IDE drive, just to see if it is in fact something about the 3ware card that the problem is related to. I would also install the 3ware card in the slot closes to the AGP slot, since that slot usually is the fastest, etc. Are there any other cards installed? If so, remove them and see if that changes anything. I would also check the BIOS and if you are not using IDE (while the 3ware is installed) I would disable the primary and secondary IDE channels (assuming you do not have a local CD-ROM/DVD). On our servers, I have an external USB floppy and external USB CD-ROM that I use for installation, then once FreeBSD is up and running, I disable USB and unplug those (since our servers don't require floppy or CD's, etc.) While you are searching google next time, you might try searching for the make/model of your motherboard and FreeBSD or something along those lines. People often forget how much impact the motherboard and chipset can have on things. BTW, since you have been removing cards and stuff, you might try removing all the card and then doing a CMOS clear. Then boot and configure the BIOS. Then power down, install just the 3ware card, boot up, then try installing FreeBSD without anything else. That might help the 3ware card recognize a different IRQ or something. Keep everyone posted. If I think of anything else, I will e-mail you. Ray From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 13:06:40 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD50516A47C for ; Mon, 28 Nov 2005 13:06:40 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57D3F43D5C for ; Mon, 28 Nov 2005 13:06:39 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1EgiiI-0003cZ-00; Mon, 28 Nov 2005 14:06:34 +0100 Message-ID: <438B00D9.3040109@millennics.com> Date: Mon, 28 Nov 2005 14:06:33 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125114640.00a5d2f8@pop.redshift.com> <3.0.1.32.20051128045500.00a47aa8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051128045500.00a47aa8@pop.redshift.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: Re: Yikes! Dire trouble with 9500S-4 installation :((( X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 13:06:41 -0000 Hi Ray, Tnx for the reply! Indeed I think an IRQ conflict sounds like a very good candidate for the source of the issues. I'll try to get the client to bring the machine to my home today and then I can work on resolving the conflict... I'll keep everyone posted... Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 13:33:23 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3835D16A429 for ; Mon, 28 Nov 2005 13:33:23 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A135D43D67 for ; Mon, 28 Nov 2005 13:31:41 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from eirik.unicore.no ([213.225.74.166] helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1Egj6B-000OoN-Gs for amd64@freebsd.org; Mon, 28 Nov 2005 14:31:15 +0100 Resent-Message-Id: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Resent-Date: Mon, 28 Nov 2005 14:31:14 +0100 Message-Id: <93F6B911-8C64-4F5C-81F9-80EC271ED298@anduin.net> Content-Transfer-Encoding: 7bit Resent-To: amd64@freebsd.org From: =?ISO-8859-1?Q?Eirik_=D8verby?= Resent-From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Sat, 26 Nov 2005 03:06:29 +0100 To: stable@freebsd.org X-Mailer: Apple Mail (2.746.2) Cc: Subject: Reduced java/tomcat performance 6-beta3 -> 6-stable ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 13:33:23 -0000 [Cross-posting after lack of response on -stable] Hi all, are there any obvious changes between 6.0-BETA3 and 6.0-RELEASE / 6.0- STABLE that I should be aware of, that could cause a quite noticeable decline in performance (and a change in performance patterns) for java/tomcat? On a BETA-3 system I'm seeing, with the particular application we're running, about 28 transactions/second over a 10 minute interval. With -RELEASE and -STABLE I'm lucky to reach 24, and it'll usually wobble around 20. Another oddity is that where the BETA-3 system starts out with good performance from the beginning when running load tests, the -RELEASE and -STABLE systems need a good 20 seconds to reach their "max", starting out very low (3-10 transactions/second for the first 10 seconds or so). This is on HP DL385 servers with dual 2.4ghz Opteron CPUs, running FreeBSD-amd64 from 15kRPM drives in cached RAID. Hardware and software configuration (apart from the base system), network configuration and latencies, database access, etc. is 100% equal on all systems. Any ideas? Thanks, /Eirik From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 13:58:08 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD8C16A41F for ; Mon, 28 Nov 2005 13:58:08 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F47843D55 for ; Mon, 28 Nov 2005 13:58:07 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jASDw5Gq097904; Mon, 28 Nov 2005 08:58:06 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <438B0CEC.4070308@wmptl.com> Date: Mon, 28 Nov 2005 08:58:04 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.711 () J_CHICKENPOX_53,RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 13:58:08 -0000 ray@redshift.com wrote: > | > My policy is to never be the first kid on the block to test something new - > | > especially not in production. FreeBSD 5.4 has been hammered on for a long time > | > and works really well. 5.4 is an evolution of 5.2.1 and 5.3 - all of which are > | > very mature and very stable. I've been running FreeBSD in production since > | > version 5.2.1 and have been using FreeBSD since 4.9 (previously we used Redhat > | > linux for our production servers). Anyway, when I build a machine, here is > | > exactly what I use: > | > > | > | I disagree. First-off, 6.0-RELEASE may be new to the block, but 6.0 has been > | kicking it almost as long as 5.4-RELEASE has been out. Most of the experiences > | I've heard back from other users are saying 6.0, even RC-1 before -RELEASE > | actually runs better than 5.4-RELEASE. Certain key optimizations in 6.0 will > | help you out, (eg filesystem changes, SMP support, hardware drivers, etc). > | Considering the newer hardware you've chosen (dual core amd64 cpu) - 6.0 is much > | better prepared to handle it in the kernel. I've been running 6.0-RC1 on one of > | the dual opterons we have here now for a couple of months now - performance is > | great and havn't had a moments downtime yet. Seriously, do not discount 6.0 > | because it's a '.0' release, really it's not. As Ray pointed out, 5.4 was an > | evolution of 5.2 - 5.3, etc... what he did not potentially realize, is that 6.0 > | is of that same evolution. Read the notes as to why the version skipped from 5.4 > | -> 6.0, and you'll realize that 6.0 was simply a new version number to a release > | that would have otherwise been say 5.5, the reason for the skip was because of > | the large number of new capbilities and features. And yes, new features generall > | can equal new bugs - but if you're not relying upon them and you're doing the > | same thing you would with a 5.4 machine, then why sacrafice the added filesystem > | performance and hardware support by not running 6.0? > > Can you provide some specific benchmarks you have run comparing 5.4 to 6.0? > I've heard too many people, too many times, pull stats out of the air regarding > "the new release". If you have done some specific testing to show that 5.4 is > slow than 6.0 - then great. But if you are just going by the seat of your > pants, then I think it can be dangerous to assume a new version if faster. In > the case of FreeBSD 6.0, it may very well be the case, but I personally have no > tested it in production. In cases of things like PHP5 vs. PHP4, 4 is clearly > faster. Same for apache. 2.0.52, based on my testing, is clearly slower > compared to 1.3.33. If you have stats showing the different between 5.x and 6.x > in areas such as disk I/O, CPU load, etc., I for one would appreciate seeing > some hard numbers. So far, I haven't had a chance to run any and I'm certainly > interested in version 6.0 However, as a system admin for close to 25 years, I > still stick by my guns that immediately jumping to the latest release for use in > a production machine can be quite risky. If you are just playing around at > home, that's one thing. But if 5x9+ uptime is critical, then it's a whole > different story. > Again, my point was that 6.0-RELEASE is not the 'newest/latest untested release', but rather that it comes as a new version number to a large number of improvements over the 5.4 branch. While I have no 'cold hard numbers' to support my benchmarking, I will say from experience running 6.0 in production now for a few months (actually have a production server environment running 6.0-RC1, because on the AMD64 platform it proved to be more stable and more complete than 5.4-RELEASE did). I had many issues with various libraries in FreeBSD 5.4, especially in areas of ldap client, threads, and a port of nss_ldap. All of which is based on the same code I've been running for a LONG time on other machines now. Without digressing too far from the subject, the bottom line was 6.0 did (and still does) run cleaner, and faster without the stability issues I encountered with 5.4 on AMD64 platform - and as I said in my original reply I disagree because 6.0 is not as new as you claim. Generally, I share the same opinion as yourself - don't jump to something new just because it's new, stick with what's tried-and-true. That being said, I still stand to my original remark when I say with some confidence that 6.0 - IS tried-and-true, and I can back that up with at least the last 4 months of day-to-day production use of it. > | I agree, short of large security patches, stick with a -RELEASE code. In any > | given production environment stability is key. While cvsup'ing and building the > | new box everyday to stay current sounds good - it is in practice not good for > | production servers - if it isn't broke, don't fix it. > > Agreed. CVS is great for getting the latest code to test, but I've seen friend > constantly doing CVS's and build worlds on servers in production only to have > them exhibit strange behavior until the next patch comes out. In fact, not too > long ago a buddy of mine updated a machine and ended up having to roll back the > OS to a previous version in order to cure some strange crashing problem (which > later went away a few patches down the road). > > | As Olaf pointed out many times in this thread (or related threads) - budget is > | key with this deal, so I doubt load balancing and plopping another machine in is > | an option his client really wants to hear about - until they've gotten to a > | point to justify doing so. Why scare customers away telling them they can buy > | more, if you just sold them something new why isn't it going to be good enough - > | guarantee that's not a question you'll want to provoke. > > I haven't seen Olaf's P/L for the year, so I can't really comment. All I can > say is some people build clusters some don't :) For those that do, load > balancing is a much more viable option in a lot of cases than trying to squeeze > every last ounce of performance from a machine. I've been woken up too many > times between 1995 and 1999 with machines dead to the world because we tried to > tweak every last red cent out of them (running Linux) to do it any more. As far > as my opinion on it, in the long run, it's money ahead if you have redundancy, > even if the initial jump into it is a little more costly than you want. > > | Same response. Look at the SMP file, it's basically "options smp; include > | GENERIC"... just copy the GENERIC to your own config, remove the driver(s) you > | don't require, add 'options SMP' and any other options you may wish - rename the > | config and go from there. > > When I first moved from i386 to AMD64, that one tripped me up but good! :) I > was so used to just editing GENERIC, I didn't even look at SMP or realize it was > there for about 3 days. Yeah, caught me too - didn't even realize one could do an include-xyz from a kernel config file. Guess that's how one learns though eh ;) > > | The ports collection has been optimized for 'the average install', leveraging > | performance for functionality in most situations to be ideal. The ports usually > | have added patches or adjustments to code which integrates them better with > | FreeBSD, if you're not all that familair with the code you're working with, (in > | this case mysql), then I'd reccomend you stick with the ports collection. > | However, that being said - note that the ports collection isn't always up to > | date, and you may want a differing version of mysql. Follow the documentation on > | mysql.com and you should be just fine - fairly staght forward install and > | differs little from doing so via the FreeBSD ports collection. In any production > | system though, I highly reccomend compiling from source vs downloading binaries > | - that way nothing has been linked to/from librairies which may or may not be > | the same on your system. > > Agreed. > > | I agree, stick with 4.1.x, but for different reasons. Compatability; not sure > | what you are doing, the size or scope of the database you're dealing with, but > | if for example you're going to be writting and app in windows which uses the > | myodbc driver to connect... then you may run into problems with newer versions > | of mysql. I encountered a LOT of this, when we moved from 3.x up to 4.1, largely > | because of changes in the client - at least I was aware of that before I > | started, but I did have to rebuild client librairies on all webservers, and > | re-install odbc drivers on client machines throughout the building because of > | it. Might not be something you're willing/ready to undertake for the features > | you've already mentioned not being required in mysql 5. > > Couldn't comment on using the Win API to connect directly to MySQL, but it > doesn't sound fun! :) Are you using VC++ to do it or MFC or ? If you have any > sample code for that, I'd be interested in seeing it (off list). Actually, just work with MS ADO as you normally would, it's just a connection string. Essentially no different in code from that to using MS Access or SQL server connections, you simply supply a connection string (email off list if you'd like a sample). > > Anyway, hopefully Olaf doesn't hang himself over there after reading our > messages. I think he's on a pretty good track to a nice server from what I've > read so far. I still am not a fan of jumping to the latest 'anything' as far as > production machines go. Yes, it may work, but I've been burned too many times > in the past doing that. If it's not a production environment, then that's a > totally different story, but for anything business related or HA, it's usually a > risk to be the first ones running something fresh off hacking-room-floor :) > Again, 6.0 is NOT as new as you keep trying to stress it. Read the archives regarding why the release numbering jumped from 5.4 -> 6.0; and try asking those who have been running 6 for > 5-6months now without issue. In my case, I had issues with stability and librairies in 5.4 that forced me to prematurely move over to 6.0 - a step I did not take lightly with terabytes of data and a lot of users on the line. I did the research, talked to people running 6, and did as you suggested 'posting a thread for 5.4 vs 6.0 in production', check the list archives if you missed it. > Anyway, have a good weekend. > > Ray > > I'm not trying to provoke you here, and I'm glad for the debate - but sometimes I tend to come off as though I'm trying to fight or argue... that's my bad, and just want to make sure you don't feel like I'm attacking/defending against you. I'd wish you a good weekend too, except that it's Monday now and I'm just getting back to reading my email ;) > -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 14:12:11 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0CE316A422 for ; Mon, 28 Nov 2005 14:12:11 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-webmail.redshift.com (mail-webmail.redshift.com [216.228.2.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FEA043D46 for ; Mon, 28 Nov 2005 14:12:09 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 48903 invoked by uid 89); 28 Nov 2005 14:12:03 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-webmail.redshift.com with SMTP; 28 Nov 2005 14:12:03 -0000 Message-Id: <3.0.1.32.20051128061159.00a47aa8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Mon, 28 Nov 2005 06:11:59 -0800 To: Nathan Vidican From: ray@redshift.com In-Reply-To: <438B0CEC.4070308@wmptl.com> References: <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: amd64@freebsd.org Subject: Re: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 14:12:12 -0000 | Again, my point was that 6.0-RELEASE is not the 'newest/latest untested | release', but rather that it comes as a new version number to a large number of | improvements over the 5.4 branch. While I have no 'cold hard numbers' to support | my benchmarking, I will say from experience running 6.0 in production now for a | few months (actually have a production server environment running 6.0-RC1, | because on the AMD64 platform it proved to be more stable and more complete than | 5.4-RELEASE did). I had many issues with various libraries in FreeBSD 5.4, | especially in areas of ldap client, threads, and a port of nss_ldap. All of | which is based on the same code I've been running for a LONG time on other | machines now. Without digressing too far from the subject, the bottom line was | 6.0 did (and still does) run cleaner, and faster without the stability issues I | encountered with 5.4 on AMD64 platform - and as I said in my original reply I | disagree because 6.0 is not as new as you claim. Generally, I share the same | opinion as yourself - don't jump to something new just because it's new, stick | with what's tried-and-true. That being said, I still stand to my original remark | when I say with some confidence that 6.0 - IS tried-and-true, and I can back | that up with at least the last 4 months of day-to-day production use of it. That's certainly good to hear. I wasn't trying to suggest FreeBSD 6.0 is buggy. As I mentioned previously, I'm constantly impressed by how stable FreeBSD is. My only point was that in general it can be risky to suddenly jump to something new. Since 6.0 is relatively new, I was just suggesting to Olaf that perhaps he should stick with 5.4, since he's dealing with a lot of variables. I plan to move to 6.0 to do some testing myself in a few months here. It's good to hear you have been using it for 4 months with no troubles. | > | Same response. Look at the SMP file, it's basically "options smp; include | > | GENERIC"... just copy the GENERIC to your own config, remove the driver(s) you | > | don't require, add 'options SMP' and any other options you may wish - rename the | > | config and go from there. | > | > When I first moved from i386 to AMD64, that one tripped me up but good! :) I | > was so used to just editing GENERIC, I didn't even look at SMP or realize it was | > there for about 3 days. | | Yeah, caught me too - didn't even realize one could do an include-xyz from a | kernel config file. Guess that's how one learns though eh ;) :-) I'm glad I'm not the only one that got. I felt like a total dolt when I spent nearly 2 weeks running benchmarks to compare i386/Xeon vs AMD64/Opteron only to find out I had accidently compiled out SMP on the AMD64 OS! DOH! No, wait, that would actually be (DOH*DOH)/.00001 | Again, 6.0 is NOT as new as you keep trying to stress it. Read the archives | regarding why the release numbering jumped from 5.4 -> 6.0; and try asking those | who have been running 6 for > 5-6months now without issue. In my case, I had | issues with stability and librairies in 5.4 that forced me to prematurely move | over to 6.0 - a step I did not take lightly with terabytes of data and a lot of | users on the line. I did the research, talked to people running 6, and did as | you suggested 'posting a thread for 5.4 vs 6.0 in production', check the list | archives if you missed it. I wasn't stressing it's bad. I was simply saying that a lot of times new software has things that need to be worked out. I think that's true with anything. Look at the Ferrari 355 and 360 - only a very brave man/woman buys the first year car from Ferrari! :-) Their policy seems to be "let the client figure out what's wrong with our cars, then we'll fix it for future clients". FreeBSD seems to always be very stable right out of the box, but you have to admit those -p levels are there for a reason :-) | I'm not trying to provoke you here, and I'm glad for the debate - but sometimes | I tend to come off as though I'm trying to fight or argue... that's my bad, and | just want to make sure you don't feel like I'm attacking/defending against you. | I'd wish you a good weekend too, except that it's Monday now and I'm just | getting back to reading my email ;) Thanks Nathan. I know things don't always come across right over e-mail since you can't see people, hear voices, etc. Like you, I enjoy a good debate about something and think it's always good to listen/explore all concepts, ideas. Once that's done and the points are made, then it's back to being friends :) Ray From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 14:58:12 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C53E716A41F for ; Mon, 28 Nov 2005 14:58:12 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2670C43D64 for ; Mon, 28 Nov 2005 14:58:11 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id D75D9B80D for ; Mon, 28 Nov 2005 09:58:09 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <438844C2.3000902@bredband.net> References: <437CF0E5.5030405@wmptl.com> <437D0FF6.20009@deadcafe.de> <1E1A2905-37CA-45BA-8E3E-BC3DDF3094EF@khera.org> <4384BBBF.4030007@wmptl.com> <438844C2.3000902@bredband.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <10F00268-9E17-4EAB-B806-D8666C50177D@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 28 Nov 2005 09:58:08 -0500 To: amd64@freebsd.org X-Mailer: Apple Mail (2.746.2) Cc: Subject: Re: Sun x2100 Server Compatability X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 14:58:12 -0000 On Nov 26, 2005, at 6:19 AM, Lars Tunkrans wrote: > The intention here is to provide a FAST bus for the optional > PCI-E infiniband card and PCI-E FibreChannel CARD. > > The box is inteded as a GRID building block. On the list of expansion cards, they list a bunch of PCI-E ethernet cards available Q4 2005, so presumably they will sell some soon. Even if it is intended as a GRID building block, it still looks like a wicked awesome (and cheap) web server. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 17:04:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1609416A427; Mon, 28 Nov 2005 17:04:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E69F43D79; Mon, 28 Nov 2005 17:04:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2741931 for multiple; Mon, 28 Nov 2005 12:04:25 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASH3rCN058457; Mon, 28 Nov 2005 12:04:11 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 28 Nov 2005 11:48:47 -0500 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281148.49017.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 X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: amd64@freebsd.org, java@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: quest for help on a linux emul problem (source unknown) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 17:04:16 -0000 On Saturday 26 November 2005 08:50 pm, Arno J. Klaassen wrote: > Hello, > > > I try to get a commercial linux32 package to work on amd64; > this package includes it's own binary distrib of some > linux-jdk1.3.1 and works OK on i386 (RELENG_5 and RELENG_6) but > hangs on amd64-RELENG_6 (though it did work on a couple > of months old amd64-RELENG-5, but I do not any longer have such > a box around ... ). > > I write this email in the hope someone can put me on the right > track to nail down this problem : > > when I do a ktrace on i386 I get : > > CALL mincore(0xbfbfc480,0) > RET mincore 0 > CALL #175(0,0,0xbfbfc2b4,0x8) > RET #175 0 > CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) > RET #175 0 > CALL mincore(0xbfbfc290,0) > RET mincore 0 > CALL getdomainname(0xbfbfc288,0) > RET getdomainname 0 > > then some dozens of : > > CALL #175(0x2,0xbfbfc338,0,0x8) > RET #175 0 > CALL mincore(0xbfbfc480,0) > RET mincore 0 > CALL #175(0,0,0xbfbfc2b4,0x8) > RET #175 0 > CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) > RET #175 0 > CALL mincore(0xbfbfc290,0) > RET mincore 0 > CALL getdomainname(0xbfbfc288,0) > RET getdomainname 0 > > > and finally : > > CALL #175(0x2,0xbfbfc338,0,0x8) > RET #175 0 > CALL write(0xb,0x83189e8,0x18) > GIO fd 11 wrote 24 bytes FYI, there is a 'linux-kdump' in ports that parses the syscalls from a ktrace on a linux binary. You can use that to make sure your mapping of 175 to sigprocmask() is correct. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 17:04:16 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1609416A427; Mon, 28 Nov 2005 17:04:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E69F43D79; Mon, 28 Nov 2005 17:04:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2741931 for multiple; Mon, 28 Nov 2005 12:04:25 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASH3rCN058457; Mon, 28 Nov 2005 12:04:11 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 28 Nov 2005 11:48:47 -0500 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281148.49017.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 X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: amd64@freebsd.org, java@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: quest for help on a linux emul problem (source unknown) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 17:04:16 -0000 On Saturday 26 November 2005 08:50 pm, Arno J. Klaassen wrote: > Hello, > > > I try to get a commercial linux32 package to work on amd64; > this package includes it's own binary distrib of some > linux-jdk1.3.1 and works OK on i386 (RELENG_5 and RELENG_6) but > hangs on amd64-RELENG_6 (though it did work on a couple > of months old amd64-RELENG-5, but I do not any longer have such > a box around ... ). > > I write this email in the hope someone can put me on the right > track to nail down this problem : > > when I do a ktrace on i386 I get : > > CALL mincore(0xbfbfc480,0) > RET mincore 0 > CALL #175(0,0,0xbfbfc2b4,0x8) > RET #175 0 > CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) > RET #175 0 > CALL mincore(0xbfbfc290,0) > RET mincore 0 > CALL getdomainname(0xbfbfc288,0) > RET getdomainname 0 > > then some dozens of : > > CALL #175(0x2,0xbfbfc338,0,0x8) > RET #175 0 > CALL mincore(0xbfbfc480,0) > RET mincore 0 > CALL #175(0,0,0xbfbfc2b4,0x8) > RET #175 0 > CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) > RET #175 0 > CALL mincore(0xbfbfc290,0) > RET mincore 0 > CALL getdomainname(0xbfbfc288,0) > RET getdomainname 0 > > > and finally : > > CALL #175(0x2,0xbfbfc338,0,0x8) > RET #175 0 > CALL write(0xb,0x83189e8,0x18) > GIO fd 11 wrote 24 bytes FYI, there is a 'linux-kdump' in ports that parses the syscalls from a ktrace on a linux binary. You can use that to make sure your mapping of 175 to sigprocmask() is correct. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 18:06:47 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CCC416A420 for ; Mon, 28 Nov 2005 18:06:47 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6210143D81 for ; Mon, 28 Nov 2005 18:06:38 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jASI6Uxm006832; Mon, 28 Nov 2005 13:06:30 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <438B4726.4010706@wmptl.com> Date: Mon, 28 Nov 2005 13:06:30 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Wojciech Puchar References: <20051128182431.I64067@chylonia.3miasto.net> In-Reply-To: <20051128182431.I64067@chylonia.3miasto.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: bad instability on FreeBSD/amd64 6.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 18:06:47 -0000 Wojciech Puchar wrote: > i've read few articles on the net that FreeBSD/amd64 crashes very > frequently, contrary to /i386. > > how much truth is in that? i would strongly prefer to run amd64 system > on amd64 machine that i will buy this week. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > > Been running for well over a year now - in production, from 5.3-RELEASE to 6.0-RELEASE units in single and dual AMD Opterons, and on AMD Athlon 64 desktops - no instability as far as I've encountered, outside of some library and version compatability stuff with ldap/threads/nss_ldap - but still not cause lockup of machine or anything, just wayward ldap processes (problem fixed within 6.0-RC1 and newer) - so would really reccomend you go with the 6.0 branch if you're going to be using nss/pam tied to an LDAP tree anyhow. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 18:10:13 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A38D816A41F for ; Mon, 28 Nov 2005 18:10:13 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EFF343D75 for ; Mon, 28 Nov 2005 18:10:01 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so1239328nzo for ; Mon, 28 Nov 2005 10:09:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=DmnT2oO+9le2/OFvnPj0dFz+jLvxlae2imPK5bW04W9ZH0GbRP8B4D/c4kOK/97kYHKFyIasOWCNHfTnt73q6XKPqI/BWnrJ5Rkg5mFAAJ7Sth6ksPFZ8IE5nmycRhhyYLKhdTOP6MwlQAf6O0AcrcAtaytQZfVCU5m3iBFJrq0= Received: by 10.64.131.1 with SMTP id e1mr1771745qbd; Mon, 28 Nov 2005 10:09:59 -0800 (PST) Received: by 10.65.192.16 with HTTP; Mon, 28 Nov 2005 10:09:59 -0800 (PST) Message-ID: Date: Mon, 28 Nov 2005 19:09:59 +0100 From: Claus Guttesen To: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-amd64 List Subject: increasing PMAP_SHPGPERPROC (was: FreeBSD 5.4 or 6.0 as postgresql-server) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 18:10:13 -0000 > > I'd be interested in your experiences w/6.0. Would you mind testing > > the onboard bge nics at the kind of loads that was causing them to > > puke under 5.4? I've got same system and as of yet not encountered > > issues w/ the onboard bge nics. The machine is also at the latest > > BIOS, however, so that may contribute as well. I just put our new db-server in production and so far everything works fine, including the two build-in bge-nics. When load hit the server the following showed up in /var/log/messages: kernel: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC The default value is found in /usr/src/sys/amd64/conf/NOTES and says: # The value below is the one more than the default. # options PMAP_SHPGPERPROC=3D201 But I can't find any rule of thumb on what value to raise it to, 402, 512, just above it says: # Set the number of PV entries per process. Increasing this can # stop panics related to heavy use of shared memory. However, that can # (combined with large amounts of physical memory) cause panics at # boot time due the kernel running out of VM space. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 18:12:06 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCA3716A422 for ; Mon, 28 Nov 2005 18:12:06 +0000 (GMT) (envelope-from wojtek@tensor.3miasto.net) Received: from chylonia.3miasto.net (chylonia.3miasto.net [213.192.74.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2540C43D58 for ; Mon, 28 Nov 2005 18:11:52 +0000 (GMT) (envelope-from wojtek@tensor.3miasto.net) Received: from chylonia.3miasto.net (localhost [127.0.0.1]) by chylonia.3miasto.net (8.13.4/8.13.4) with ESMTP id jASIBgKZ064781; Mon, 28 Nov 2005 19:11:42 +0100 (CET) (envelope-from wojtek@tensor.3miasto.net) Received: from localhost (wojtek@localhost) by chylonia.3miasto.net (8.13.4/8.13.4/Submit) with ESMTP id jASIBgAX064778; Mon, 28 Nov 2005 19:11:42 +0100 (CET) (envelope-from wojtek@tensor.3miasto.net) X-Authentication-Warning: chylonia.3miasto.net: wojtek owned process doing -bs Date: Mon, 28 Nov 2005 19:11:42 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@chylonia.3miasto.net To: Nathan Vidican In-Reply-To: <438B4726.4010706@wmptl.com> Message-ID: <20051128191114.T64740@chylonia.3miasto.net> References: <20051128182431.I64067@chylonia.3miasto.net> <438B4726.4010706@wmptl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: amd64@freebsd.org Subject: Re: bad instability on FreeBSD/amd64 6.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 18:12:06 -0000 > Been running for well over a year now - in production, from 5.3-RELEASE to > 6.0-RELEASE units in single and dual AMD Opterons, and on AMD Athlon 64 > desktops - no instability as far as I've encountered, outside of some library > and version compatability stuff with ldap/threads/nss_ldap - but still not that's what i wanted to hear. i will install FreeBSD/amd64 6.0 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 18:29:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E59CB16A41F for ; Mon, 28 Nov 2005 18:29:37 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BB8443D46 for ; Mon, 28 Nov 2005 18:29:37 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 951C4B864 for ; Mon, 28 Nov 2005 13:29:36 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3-276553020; protocol="application/pkcs7-signature" Message-Id: <9050D228-231F-415C-8F5C-FBF5AE4BACE8@khera.org> From: Vivek Khera Date: Mon, 28 Nov 2005 13:29:35 -0500 To: freebsd-amd64 List X-Mailer: Apple Mail (2.746.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: increasing PMAP_SHPGPERPROC (was: FreeBSD 5.4 or 6.0 as postgresql-server) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 18:29:38 -0000 --Apple-Mail-3-276553020 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Nov 28, 2005, at 1:09 PM, Claus Guttesen wrote: > kernel: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC I've never been able to get good advice on how to tune this parameter. I believe on one box I just upped it by 50 from the default (back in 4.x days) and stopped getting them. --Apple-Mail-3-276553020-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 19:09:57 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 9582316A420; Mon, 28 Nov 2005 19:09:57 +0000 (GMT) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A25843D45; Mon, 28 Nov 2005 19:09:57 +0000 (GMT) (envelope-from ru@FreeBSD.org) Received: from freefall.freebsd.org (ru@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jASJ9vDj069703; Mon, 28 Nov 2005 19:09:57 GMT (envelope-from ru@freefall.freebsd.org) Received: (from ru@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jASJ9vjA069699; Mon, 28 Nov 2005 19:09:57 GMT (envelope-from ru) Date: Mon, 28 Nov 2005 19:09:57 GMT From: Ruslan Ermilov Message-Id: <200511281909.jASJ9vjA069699@freefall.freebsd.org> To: kobayasi@pp.iij4u.or.jp, ru@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/83806: Can not compile /usr/src/lib/msun/amd64/fenv.c at make buildworld. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 19:09:57 -0000 Synopsis: Can not compile /usr/src/lib/msun/amd64/fenv.c at make buildworld. State-Changed-From-To: patched->closed State-Changed-By: ru State-Changed-When: Mon Nov 28 19:09:06 GMT 2005 State-Changed-Why: Also fixed in 6.0-STABLE. http://www.freebsd.org/cgi/query-pr.cgi?pr=83806 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 20:45:49 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9339516A41F for ; Mon, 28 Nov 2005 20:45:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D23943D76 for ; Mon, 28 Nov 2005 20:45:41 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E675C1A3C32; Mon, 28 Nov 2005 12:45:40 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 426075158D; Mon, 28 Nov 2005 15:45:40 -0500 (EST) Date: Mon, 28 Nov 2005 15:45:40 -0500 From: Kris Kennaway To: Martin Nilsson Message-ID: <20051128204540.GA28393@xor.obsecurity.org> References: <438AA21E.2030702@gneto.com> <20051128104253.GB59977@ip.net.ua> <20051128105215.GA16457@xor.obsecurity.org> <438AFB5B.8070303@gneto.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <438AFB5B.8070303@gneto.com> User-Agent: Mutt/1.4.2.1i Cc: amd64@FreeBSD.org, Kris Kennaway Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 20:45:49 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 01:43:07PM +0100, Martin Nilsson wrote: > Kris Kennaway wrote: > >the md. Then run the cross-build. When I tried this for fun the > >other day on a 4-CPU amd64 machine it took a little over 15 minutes to > >buildworld. >=20 > What did you compile? 6.0-STABLE world. > How fast is your 4-CPU Opteron? CPU: AMD Opteron(tm) Processor 846 (1991.70-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf5a Stepping =3D 10 Features=3D0x78bfbff AMD Features=3D0xe0500800 real memory =3D 17179869184 (16384 MB) avail memory =3D 15583883264 (14861 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Kris --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDi2xzWry0BWjoQKURAqPaAJ4xnQwXghGA14ecGsdrH33Gygz/VgCfcZbc g56Is1YN/ugQ5uqufmocYog= =jOpQ -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 20:47:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85B4416A41F for ; Mon, 28 Nov 2005 20:47:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40CF243D46 for ; Mon, 28 Nov 2005 20:47:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E180A1A3C28; Mon, 28 Nov 2005 12:47:51 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 50C315158D; Mon, 28 Nov 2005 15:47:51 -0500 (EST) Date: Mon, 28 Nov 2005 15:47:51 -0500 From: Kris Kennaway To: Vivek Khera Message-ID: <20051128204751.GB28393@xor.obsecurity.org> References: <9050D228-231F-415C-8F5C-FBF5AE4BACE8@khera.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s2ZSL+KKDSLx8OML" Content-Disposition: inline In-Reply-To: <9050D228-231F-415C-8F5C-FBF5AE4BACE8@khera.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64 List Subject: Re: increasing PMAP_SHPGPERPROC (was: FreeBSD 5.4 or 6.0 as postgresql-server) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 20:47:54 -0000 --s2ZSL+KKDSLx8OML Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 01:29:35PM -0500, Vivek Khera wrote: >=20 > On Nov 28, 2005, at 1:09 PM, Claus Guttesen wrote: >=20 > >kernel: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC >=20 > I've never been able to get good advice on how to tune this =20 > parameter. I believe on one box I just upped it by 50 from the =20 > default (back in 4.x days) and stopped getting them. In my experience it's usually best to make fractional changes like this when tuning a parameter, since the defaults are usually nearly good enough, and it's pretty hard to generate a workload that will blow them out by a large amount. Kris --s2ZSL+KKDSLx8OML Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDi2z2Wry0BWjoQKURAgl4AKCblMULJNVwCiUEpt+OBrlURq7YZwCg/xRo 8mi3yCIs8qbh1e2bKGd7DK4= =yccM -----END PGP SIGNATURE----- --s2ZSL+KKDSLx8OML-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 23:43:11 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9844916A41F for ; Mon, 28 Nov 2005 23:43:11 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3D2743D4C for ; Mon, 28 Nov 2005 23:43:07 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jASNh6KD043947; Tue, 29 Nov 2005 00:43:06 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jASNh4WQ043941; Mon, 28 Nov 2005 18:43:04 -0500 (EST) (envelope-from cracauer) Date: Mon, 28 Nov 2005 18:43:04 -0500 From: Martin Cracauer To: Wojciech Puchar Message-ID: <20051128184304.A43894@cons.org> References: <20051128182431.I64067@chylonia.3miasto.net> <438B4726.4010706@wmptl.com> <20051128191114.T64740@chylonia.3miasto.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20051128191114.T64740@chylonia.3miasto.net>; from wojtek@tensor.3miasto.net on Mon, Nov 28, 2005 at 07:11:42PM +0100 Cc: amd64@freebsd.org Subject: Re: bad instability on FreeBSD/amd64 6.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 23:43:11 -0000 No stability problems here with AMD64, and I ran heavy loads. The only problem I noticed are a couple broadcom GbE chips which require to be loaded as a module, not compiled in, or vice versa. But who uses these anyway? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 28 23:47:28 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B45C316A41F for ; Mon, 28 Nov 2005 23:47:28 +0000 (GMT) (envelope-from wojtek@tensor.3miasto.net) Received: from chylonia.3miasto.net (chylonia.3miasto.net [213.192.74.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F7A343D53 for ; Mon, 28 Nov 2005 23:47:25 +0000 (GMT) (envelope-from wojtek@tensor.3miasto.net) Received: from chylonia.3miasto.net (localhost [127.0.0.1]) by chylonia.3miasto.net (8.13.4/8.13.4) with ESMTP id jASNkvBE069451; Tue, 29 Nov 2005 00:46:57 +0100 (CET) (envelope-from wojtek@tensor.3miasto.net) Received: from localhost (wojtek@localhost) by chylonia.3miasto.net (8.13.4/8.13.4/Submit) with ESMTP id jASNkv5k069448; Tue, 29 Nov 2005 00:46:57 +0100 (CET) (envelope-from wojtek@tensor.3miasto.net) X-Authentication-Warning: chylonia.3miasto.net: wojtek owned process doing -bs Date: Tue, 29 Nov 2005 00:46:57 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@chylonia.3miasto.net To: Martin Cracauer In-Reply-To: <20051128184304.A43894@cons.org> Message-ID: <20051129004626.H69275@chylonia.3miasto.net> References: <20051128182431.I64067@chylonia.3miasto.net> <438B4726.4010706@wmptl.com> <20051128191114.T64740@chylonia.3miasto.net> <20051128184304.A43894@cons.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: amd64@freebsd.org Subject: Re: bad instability on FreeBSD/amd64 6.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Nov 2005 23:47:28 -0000 > No stability problems here with AMD64, and I ran heavy loads. one more person saying that it's stable. very good news :) From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 09:45:57 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 213E116A41F for ; Tue, 29 Nov 2005 09:45:57 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AB9643D69 for ; Tue, 29 Nov 2005 09:45:50 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Eh22y-0007Es-00; Tue, 29 Nov 2005 10:45:12 +0100 Message-ID: <438C2322.8020801@axis.nl> Date: Tue, 29 Nov 2005 10:45:06 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nathan Vidican , ray@redshift.com References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> In-Reply-To: <438B0CEC.4070308@wmptl.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 09:45:57 -0000 Hi again, Well, the plot thickens... Yesterday the machine was brought to my place (unfortunately without the user manuals :( ), so I could give various things a try. Bottomline: still no solution. I'll do my best to abbreviate the report of the many things I tried. Summed up, they come down to the following (note: I'm very heavily suspecting a conflict with the MoBo and/or chipset, and/or memory): * The MoBo is an Asus A8N-SLI premium. I just discovered that more people have had issues with this combination. E.g. check: http://www.planetamd64.com/lofiversion/index.php/t12603.html (found using Google, with the terms "asus a8n-sli premium 3ware 9500 problem" - I have yet to check if one of the links perhaps mentions a solution). * The chipset is an nforce one; I think it was 4, but perhaps it's 3. * The controller is the 9500S-4LP controller. * I did not flash the 9500S-4LP controller's Firmware. Maybe that would yield a solution, but what I gather from the above URL it may not). I'll have a look-see to see what the latest firmware version is... * Other than the controller and the video board, there were no other boards used (i.e. I took both NICs out straight away). * I called the US ACMM support line, and the controller cannot be jumpered or otherwise configured to enforce a specific IRQ. Instead, putting it in different PCI slots should take care of that. * I tried pretty much all combinations of the board in the various PCI slots (all 32-bits), both in combination with the AGP video board, as well as in combination with a PCI video board. No solution there. * I tried disabling virtually everything in the BIOS but for 1 IDE channel (which I need for the FreeBSD CD-ROM) and the CPU. :D No solution there. * I tried overriding the Auto PCI IRQ settings, but unfortunately it only allows individual lines to be switched between "Auto" and "Reserved". I tried flagging the seemingly conflicting lines as reserved, but the machine then just reassigned different IRQ lines to the same possibly conflicting devices. * The only thing which caused FreeBSD to not hick-up, was to completely remove the 3ware controller, and just plug in one drive on one of the on-board normal SATA controllers (I guess this will work with the other SATA controllers and multiple drives, as well as the on-board RAID controller as well). That way no errors were given by FreeBSD, and it would actually try to install (needlessly to say, I aborted the actual installation). * The returned errors from FreeBSD come in two varieties; one very quick hang (with the "unposted command completed!! error", and one in which FreeBSD returns many more errors (including stuff like a firmware vs. driver mismatch, which may be of importance), but in which FreeBSD most of the times manages to pull through until sysinstall (and then simply mentions there are no HDs). The difference between these two is reproducable by disabling/enabling lots of on-board stuff (dunno from the top of my head which one is the culprit). * One of the errors FreeBSD gives for the 9500S mentions "...irq 18 at device 8.0 on pci5". Interestingly enough, a further error (or warning, or just "info") is given that something from Texas Instruments (the memory, I guess ?!?) is also located on pci5 (I couldn't write down the exact error)... Perhaps a suspect? Good, so far for a 'bulleted' report. In order to give more complete information I have listed some more debug information down below. Maybe someone can spot something off in it? Firstly, a typical list of PCI devices at boot time (with already lots of stuff such as the audio controller, etc. disabled): PCI device listing: Bus No. Device No. Func. No. vendor/device class device class IRQ ======================================================================= 0 1 1 10DE 0052 0C05 SMBus contr. 4 0 7 0 10DE 0054 0101 IDE contr. 11 0 8 0 10DE 0055 0101 IDE contr. 5 1 0 0 10DE 0161 0300 Display contr. 12 5 8 0 13C1 1002 0104 RAID contr. 12 5 11 0 104C 8023 0C00 Serial bus 3 ACPI contr. 9 ======================================================================= Perhaps the display controller bites the RAID controller (at least: both use the same IRQ)? In an even more minimal set-up, and using the PCI video board instead of the AGP one, a typical listing looks like: PCI device listing: Bus No. Device No. Func. No. vendor/device class device class IRQ ======================================================================= 0 1 1 10DE 0052 0C05 SMBus contr. 7 6 0 0 102B 0525 0300 Display contr. 10 5 8 0 13C1 1002 0104 RAID contr. 11 5 11 0 104C 8023 0C00 Serial bus 3 ACPI contr. 9 ======================================================================= So, seemingly no more shared IRQs, yet the trouble remained. :((( The 9500S BIOS reports the following upon booting: Escalade 9500S-4LP BIOS: BE9X 2.03.01.051 Firmware: FE9X 2.06.00.009 The short FreeBSD error/info is: 3ware device driver for 9000 series storage controllers, version 3.60.00.017 twa0: <3ware 9000 series storage controller> port 0xa000-0xa0ff mem 0xd8005000-0xd80050ff, 0xd2000000-0xd27fffff irq 18 at device 8.0 on pci5 twa0: [GIANT-LOCKED] twa0: Error: (0x15: 0x1201): Unposted command completed!!: Request=0xffffffff810452ee, status=0 twa0: INFO: (0x16: 0x1108): Resetting controller...: At that point FreeBSD hangs. The other version of errors show many more errors (which flash by too quickly in order to be written down, and the "pause" key doesn't pause the screen). They include things like: -Can't drain the AEN queue -Driver/Firmware mismatch -Unposted command completed!! And several other things... I hope someone has any idea or a solution, as it's not really an option to use the on-board RAID controller for obvious reasons, and we also really rather would not want to have to use a different MoBo...:(( Thanks again, and cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 10:17:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C62BE16A41F for ; Tue, 29 Nov 2005 10:17:22 +0000 (GMT) (envelope-from myh016@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5878643D5F for ; Tue, 29 Nov 2005 10:17:22 +0000 (GMT) (envelope-from myh016@gmail.com) Received: by xproxy.gmail.com with SMTP id s6so1229697wxc for ; Tue, 29 Nov 2005 02:17:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mA1lYiUQimVx3n9/hOYoH/zXlHarXPQRKcF69emWsiM9dMPMN83CFFxz2r8GJlE4JH7FNTjEkB4eb9CtUbZVYLSyqu/9c7IcqZ3x/EyTf8BBFi23n012vg5jeC4oEpNiydfwn88PKKWYJd/SgflBLFnc/4kVwn9DOX8CYw6VV9M= Received: by 10.64.53.2 with SMTP id b2mr3763318qba; Tue, 29 Nov 2005 02:17:21 -0800 (PST) Received: by 10.65.141.9 with HTTP; Tue, 29 Nov 2005 02:17:21 -0800 (PST) Message-ID: <98f0db4a0511290217m69c812c8rc74ec0e9538eb2f9@mail.gmail.com> Date: Tue, 29 Nov 2005 13:17:21 +0300 From: Dmitry Malkin To: freebsd-amd64@freebsd.org In-Reply-To: <200511252005.jAPK5qTo097801@www.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511252005.jAPK5qTo097801@www.freebsd.org> Subject: Re: amd64/89549: [amd64] nve timeouts on 6.0-release X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 10:17:22 -0000 is there no fix yet? mb it fixed in 7.0-current? From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 10:28:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0A9F16A41F for ; Tue, 29 Nov 2005 10:28:03 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D25143D5D for ; Tue, 29 Nov 2005 10:28:02 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 73C161FFDD4; Tue, 29 Nov 2005 11:28:00 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C99E21FFAD1; Tue, 29 Nov 2005 11:27:57 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 68465444F6B; Tue, 29 Nov 2005 10:22:30 +0000 (UTC) Date: Tue, 29 Nov 2005 10:22:30 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Dmitry Malkin In-Reply-To: <98f0db4a0511290217m69c812c8rc74ec0e9538eb2f9@mail.gmail.com> Message-ID: <20051129101619.F23990@maildrop.int.zabbadoz.net> References: <200511252005.jAPK5qTo097801@www.freebsd.org> <98f0db4a0511290217m69c812c8rc74ec0e9538eb2f9@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/89549: [amd64] nve timeouts on 6.0-release X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 10:28:03 -0000 On Tue, 29 Nov 2005, Dmitry Malkin wrote: > is there no fix yet? > mb it fixed in 7.0-current? depends on how much of the problem you are seeing. If it used to work for some time before you were seeing the timeouts things might be better now and some more patches have been posted to current@ I think for testing. If it simply didn't work at all it still won't. Might be a problem of specific hardware but as long as nobdoy has detailed information from nvidia I'd expect that we will not be able to fix that easily. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 12:01:23 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F34616A41F for ; Tue, 29 Nov 2005 12:01:23 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-smtp.redshift.com (mail-smtp.redshift.com [216.228.2.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 918BA43D6B for ; Tue, 29 Nov 2005 12:01:14 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 74351 invoked by uid 89); 29 Nov 2005 12:01:17 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-smtp.redshift.com with SMTP; 29 Nov 2005 12:01:17 -0000 Message-Id: <3.0.1.32.20051129040106.00a50918@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 04:01:06 -0800 To: Olaf Greve ,Nathan Vidican From: ray@redshift.com In-Reply-To: <438C2322.8020801@axis.nl> References: <438B0CEC.4070308@wmptl.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 12:01:23 -0000 At 10:45 AM 11/29/2005 +0100, Olaf Greve wrote: | Hi again, | | Well, the plot thickens... Yesterday the machine was brought to my place | (unfortunately without the user manuals :( ), so I could give various | things a try. | | Bottomline: still no solution. Hi Olaf, I would try flashing the BIOS on the 3ware card, although that's a long shot. I would also check to see if there is a more recent BIOS for the motherboard. I've cursed "very strange problems" in the past by flashing the motherboard bios on supermicro motherboards a couple of times over the years (mainly on workstations however). I wouldn't rule out a motherboard brand change. While ASUS is "good", I personally have avoided them for server use. I've never had any direction problems with them, but over the years we have had such good luck with Tyan and Supermicro. I recall a situation some years back on a Workstation running Windows XP. I built the machine using an Intel 845 motherboard. It was a nightmare. I couldn't get anything to work and the driver installation was a mess, etc. So many conflicts I couldn't keep track. I returned the Intel MB and upgraded to a Supermicro board and "presto" all the problems vanished. Chipsets can have a huge impact on things. While I don't have any first hand experience with the motherboard you are using, you may be knocking your head up against a wall with something relating to the motherboard not liking the 3ware card or something with FreeBSD not liking the chipset. That's just a guess, but it's very possible. I've used the 3Ware card in a number of servers and have never had any problem with it while running under either Linux or FreeBSD. Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 12:36:22 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE1D416A41F for ; Tue, 29 Nov 2005 12:36:22 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from whisk.dreamhost.com (whisk.dreamhost.com [205.196.208.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B2B243D46 for ; Tue, 29 Nov 2005 12:36:09 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by whisk.dreamhost.com (Postfix) with ESMTP id 9FA007F056 for ; Tue, 29 Nov 2005 04:36:06 -0800 (PST) From: Dev Tugnait To: amd64@freebsd.org Content-Type: text/plain; charset=iso-8859-13 Date: Tue, 29 Nov 2005 07:36:05 -0500 Message-Id: <1133267765.48495.8.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: Subject: Asus A8N-E X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 12:36:22 -0000 I am planning on buying Athlon X2 4400 and was looking at the Asus A8N-E mobo for it. I have checked http://www.freebsd.org/platforms/amd64/motherboards.html the dmesg and pr, seems like every things working in order. My main question is are Athlon X2's supported? I gather this from the processor listing support As of this writing, the following processors are supported: * AMD Athlon64 (´Clawhammer¡). * AMD Opteron (´Sledgehammer¡). Can someone shed some light on this motherboard or perhaps an alternative. Thank you -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 12:49:50 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8930E16A41F for ; Tue, 29 Nov 2005 12:49:50 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27F5743D5E for ; Tue, 29 Nov 2005 12:49:49 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Eh4vX-0008Q6-00; Tue, 29 Nov 2005 13:49:43 +0100 Message-ID: <438C4E65.9040605@axis.nl> Date: Tue, 29 Nov 2005 13:49:41 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@unixdaemon.org References: <1133267765.48495.8.camel@dracula> In-Reply-To: <1133267765.48495.8.camel@dracula> Content-Type: text/plain; charset=iso-8859-13; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: Re: Asus A8N-E X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 12:49:50 -0000 Hi, > I am planning on buying Athlon X2 4400 and was looking at the Asus A8N-E > mobo for it. I have checked > http://www.freebsd.org/platforms/amd64/motherboards.html the dmesg and > pr, seems like every things working in order. My main question is are > Athlon X2's supported? I gather this from the processor listing support Yes they are. At present I'm setting up a machine with that very type of processor and that is working fine. However, I am having a lot of issues with a different Asus MoBo (the A8N-SLI premium) in combination with a 3ware 9500S-4LP RAID SATA controller. If you need that controller, beware! If not, I think you should be in the clear, as without the RAID controller the MoBo + Athlon X2 4400 + FreeBSD 6 AMD64 seems to work a charm. Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 12:51:32 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B246F16A433 for ; Tue, 29 Nov 2005 12:51:32 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBA3F44182 for ; Tue, 29 Nov 2005 12:25:31 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Eh4Xx-0004wb-00; Tue, 29 Nov 2005 13:25:21 +0100 Message-ID: <438C48AC.30803@millennics.com> Date: Tue, 29 Nov 2005 13:25:16 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Greve References: <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> In-Reply-To: <438C2322.8020801@axis.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 12:51:33 -0000 Hi, A little bit of further information (which I just checked on the machine when I went home for lunch): I identified the Texas Instruments device. It's not the memory (which of course makes sense), but rather, it seems to be a FireWire controller. (TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI]) ). When considering the following FreeBSD output: twa0: <3ware 9000 series storage controller> port 0xa000-0xa0ff mem 0xd8005000-0xd80050ff, 0xd2000000-0xd27fffff irq 16 at device 6.0 on pci5 And: fwohci0: irq 16 at device 11.0 on pci5 Could this perhaps be the culprit??? I don't recall having seen any way to disable FireWire on the MoBo, but perhaps there is... Also, I checked the chipset: it's nForce 4. Hopefully this additional information contributes to identifying the clashing devices... Cheers, Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 13:14:48 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 724DC16A41F for ; Tue, 29 Nov 2005 13:14:48 +0000 (GMT) (envelope-from martin@gneto.com) Received: from av9-2-sn2.hy.skanova.net (av9-2-sn2.hy.skanova.net [81.228.8.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id E44C843D46 for ; Tue, 29 Nov 2005 13:14:47 +0000 (GMT) (envelope-from martin@gneto.com) Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502) id 10C843811C; Tue, 29 Nov 2005 14:14:46 +0100 (CET) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP id F3CEF37EB2; Tue, 29 Nov 2005 14:14:45 +0100 (CET) Received: from [192.168.2.30] (h99n2fls34o985.telia.com [213.66.202.99]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id A033137E49; Tue, 29 Nov 2005 14:14:45 +0100 (CET) Message-ID: <438C5443.6050306@gneto.com> Date: Tue, 29 Nov 2005 14:14:43 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: dev@unixdaemon.org References: <1133267765.48495.8.camel@dracula> In-Reply-To: <1133267765.48495.8.camel@dracula> Content-Type: text/plain; charset=ISO-8859-13; format=flowed Content-Transfer-Encoding: 7bit Cc: amd64@freebsd.org Subject: Re: Asus A8N-E X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 13:14:48 -0000 Dev Tugnait wrote: > I am planning on buying Athlon X2 4400 and was looking at the Asus A8N-E > mobo for it. I have checked I have one in my home server with a x2 3800+ it's been running 6.0/amd64 for about a week. The nVidia Gbit LAN have its problems don't count on it. I have a MegaRAID 320-2e in the x16 PCI-e slot, a Broadcom nic in one of the x1 PCI-e slots and a PCI graphics card everything works well. I have tested with a cheap PCI-e graphics board in the x2 slot and it worked too. I'm not using the SATA connectors but they did work when I tested them before. /Martin From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 13:18:19 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F0C616A420 for ; Tue, 29 Nov 2005 13:18:19 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail4.redshift.com (mail4.redshift.com [216.228.2.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6964743D5A for ; Tue, 29 Nov 2005 13:18:18 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 60548 invoked by uid 89); 29 Nov 2005 13:18:18 -0000 Received: by simscan 1.2.0 ppid: 60539, pid: 60545, t: 0.1353s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail4.redshift.com with SMTP; 29 Nov 2005 13:18:18 -0000 Message-Id: <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 05:18:12 -0800 To: Olaf Greve ,Olaf Greve From: ray@redshift.com In-Reply-To: <438C48AC.30803@millennics.com> References: <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 13:18:19 -0000 At 01:25 PM 11/29/2005 +0100, Olaf Greve wrote: | Hi, | | A little bit of further information (which I just checked on the machine | when I went home for lunch): | | I identified the Texas Instruments device. It's not the memory (which of | course makes sense), but rather, it seems to be a FireWire controller. | (TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI]) ). | | When considering the following FreeBSD output: | twa0: <3ware 9000 series storage controller> port 0xa000-0xa0ff mem | 0xd8005000-0xd80050ff, 0xd2000000-0xd27fffff irq 16 at device 6.0 on pci5 | | And: | fwohci0: irq 16 at device 11.0 on pci5 | | Could this perhaps be the culprit??? | | I don't recall having seen any way to disable FireWire on the MoBo, but | perhaps there is... | | Also, I checked the chipset: it's nForce 4. | | Hopefully this additional information contributes to identifying the | clashing devices... | | Cheers, | Olafo Olafo, Did you remove all the cards and clear the CMOS on the motherboard yet? There should be a jumper you short. That will reset all the IRQ stuff. Then disable everything in the BIOS you can. Then plug in the 3ware card. That might shift around the IRQ's. You almost might change the setting about "Plug and Play OS" to see if that has any impact. You might also set an IRQ in the BIOS as reserved and see if that makes any difference. I don't know the exact impact of that as it relates to the motherboard, but it's possible that will keep motherboard devices (such as the fire wire stuff) off those channels and allow them to be used by cards? I don't know, but it's worth trying. I know you aren't going to like to hear this, but perhaps a motherboard brand chance is in order? In the long run, it may save time/money. In my experience, a big part of building a good, stable server is to buy the right hardware out of the gate. For AMD CPU's, I only use Tyan here. I run the Tyan boards on my servers and Workstation and they are some of the most stable boards I have ever used. Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 13:28:09 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73FB416A420 for ; Tue, 29 Nov 2005 13:28:09 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-pop.redshift.com (mail-pop.redshift.com [216.228.2.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BCC643D53 for ; Tue, 29 Nov 2005 13:28:08 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 73415 invoked by uid 89); 29 Nov 2005 13:28:08 -0000 Received: by simscan 1.2.0 ppid: 73411, pid: 73412, t: 0.0584s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail-pop.redshift.com with SMTP; 29 Nov 2005 13:28:08 -0000 Message-Id: <3.0.1.32.20051129052802.00a87dc8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 05:28:02 -0800 To: dev@unixdaemon.org,amd64@freebsd.org From: ray@redshift.com In-Reply-To: <1133267765.48495.8.camel@dracula> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Cc: Subject: Re: Asus A8N-E X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 13:28:09 -0000 At 07:36 AM 11/29/2005 -0500, Dev Tugnait wrote: | I am planning on buying Athlon X2 4400 and was looking at the Asus A8N-E | mobo for it. I have checked | http://www.freebsd.org/platforms/amd64/motherboards.html the dmesg and | pr, seems like every things working in order. My main question is are | Athlon X2's supported? I gather this from the processor listing support | | As of this writing, the following processors are supported: | | * AMD Athlon64 (´Clawhammer¡). | | * AMD Opteron (´Sledgehammer¡). | | | Can someone shed some light on this motherboard or perhaps an | alternative. Tyan S2881 and dual Opteron's work fantastic. That's the combo I always use. Rock solid under both Windows XP and FreeBSD. Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 13:48:03 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F03E916A41F for ; Tue, 29 Nov 2005 13:48:02 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0CFF43D66 for ; Tue, 29 Nov 2005 13:48:00 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Eh5pp-0008Lu-00; Tue, 29 Nov 2005 14:47:53 +0100 Message-ID: <438C5C03.2040505@axis.nl> Date: Tue, 29 Nov 2005 14:47:47 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> In-Reply-To: <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: Olaf Greve , amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 13:48:03 -0000 Hi, > Did you remove all the cards and clear the CMOS on the motherboard yet? The former: yes, the latter: no. > There should be a jumper you short. Hehehe, "shorting the MoBo", eh? ;) No problem... However I didn't have the documentation yesterday, so I have just requested it. If all goes well, I should have it tonight, and then I can check to see if there are CMOS reset jumpers. If supported, that should be a dooze. I hope it'll do any magic then. BTW: in your opinion would you also suspect the FireWire controller to indeed be clashing with the 9500S? > That will reset all the IRQ stuff. Then disable > everything in the BIOS you can. Then plug in the 3ware card. That might shift > around the IRQ's. You almost might change the setting about "Plug and Play OS" > to see if that has any impact. Good plan. Switching the PnP OS around is about the only thing I haven't tried yet. Might indeed be a good plan to try that too. > You might also set an IRQ in the BIOS as reserved and see if that makes any > difference. I tried doing that for various IRQs, yet it seemed that it always simply skipped those IRQs and reassigned multiple devices to the same (different from the previously selected IRQ). E.g. if previously the RAID and display controllers were set to IRQ 12, and I then set that one to reserved in the BIOS, afterwards both controllers would e.g. be on IRQ 11... > I don't know the exact impact of that as it relates to the > motherboard, but it's possible that will keep motherboard devices (such as the > fire wire stuff) off those channels and allow them to be used by cards? I don't > know, but it's worth trying. It looks like there may be a further issue there. AFAIR these settings can only be made for IRQ0 - IRQ15, whereas the possibly conflicting controllers were at higher IRQs (like IRQ16 and IRQ18). Perhaps these are shared, but I won't know for sure until I can read up on it in the MoBo docs. > I know you aren't going to like to hear this, but perhaps a motherboard brand > chance is in order? In the long run, it may save time/money. I hear you, and what's more, I hear you really well. If I cannot get this combination to run VERY soon, I'll recommend them to do so, as a different MoBo should be a lot cheaper (and a better solution in the end) than me having to spend a lot of hours on it. ;) Yet, personal pride and perseverance prevents me from throwing the towel into the ring all too easily; I just can't stand it when I can't get anything to work. But then, that might just be a personality issue. :D > In my experience, > a big part of building a good, stable server is to buy the right hardware out of > the gate. For AMD CPU's, I only use Tyan here. I run the Tyan boards on my > servers and Workstation and they are some of the most stable boards I have ever > used. Definitly, and indeed I have heard a lot of good things about the Tyans. I'm not certain if they're very common over here, but surely they must be obtainable from provider that deliver server parts. I don't think the client's provider has them, but if Asus doesn't do the trick; Tyan it'll be... Cheers, Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 14:08:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FCF216A41F for ; Tue, 29 Nov 2005 14:08:11 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C08CF43D45 for ; Tue, 29 Nov 2005 14:08:10 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 94385F7C5 for ; Tue, 29 Nov 2005 07:08:07 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 53C67F7BB for ; Tue, 29 Nov 2005 07:08:07 -0700 (MST) Date: Tue, 29 Nov 2005 07:08:05 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051129070805.7c6c5cef.kgunders@teamcool.net> In-Reply-To: <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> References: <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 14:08:11 -0000 On Tue, 29 Nov 2005 05:18:12 -0800 ray@redshift.com wrote: > At 01:25 PM 11/29/2005 +0100, Olaf Greve wrote: > | Hi, > | > | A little bit of further information (which I just checked on the machine > | when I went home for lunch): > | > | I identified the Texas Instruments device. It's not the memory (which of > | course makes sense), but rather, it seems to be a FireWire controller. > | (TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI]) ). > | > | When considering the following FreeBSD output: > | twa0: <3ware 9000 series storage controller> port 0xa000-0xa0ff mem > | 0xd8005000-0xd80050ff, 0xd2000000-0xd27fffff irq 16 at device 6.0 on pci5 > | > | And: > | fwohci0: irq 16 at device 11.0 on pci5 > | > | Could this perhaps be the culprit??? > | > | I don't recall having seen any way to disable FireWire on the MoBo, but > | perhaps there is... > | > | Also, I checked the chipset: it's nForce 4. > | > | Hopefully this additional information contributes to identifying the > | clashing devices... > | > | Cheers, > | Olafo > > Olafo, > > Did you remove all the cards and clear the CMOS on the motherboard yet? There > should be a jumper you short. That will reset all the IRQ stuff. Then disable > everything in the BIOS you can. Then plug in the 3ware card. That might shift > around the IRQ's. You almost might change the setting about "Plug and Play OS" > to see if that has any impact. Try setting "Plug and Pray OS" to "No". > You might also set an IRQ in the BIOS as reserved and see if that makes any > difference. I don't know the exact impact of that as it relates to the > motherboard, but it's possible that will keep motherboard devices (such as the > fire wire stuff) off those channels and allow them to be used by cards? I don't > know, but it's worth trying. > > I know you aren't going to like to hear this, but perhaps a motherboard brand > chance is in order? In the long run, it may save time/money. In my experience, > a big part of building a good, stable server is to buy the right hardware out of > the gate. For AMD CPU's, I only use Tyan here. I run the Tyan boards on my > servers and Workstation and they are some of the most stable boards I have ever > used. IMHO the Asus was a sub optimal choice for a server board. I like some of their boards for workstation use but for AMD servers, w/the exception of 1 machine, have had pretty good results w/Tyan barbone units in the Transport line. Super Micro would also make my short list. The Sun x2100 that's been discussed recently may be an attractive candidate pending on how well other's experiences w/it prove out. The mobo may still be new enough to RMA in wh/case I'd go w/a non nVidia based Tyan server board. Yes, I know the nVidia stuff is supported much better under 6.0 than 5.4 but it's still not as mature as the AMD chipsets so I'm still staying away form them for a while yet for applications like webservers where rock solid stability is a concern Olafo-- refresh my meory on this- what are the disk config requirements? -- Best regards, Ken Gunderson 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 Nov 29 14:10:37 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A77A16A422 for ; Tue, 29 Nov 2005 14:10:37 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-smtp.redshift.com (mail-smtp.redshift.com [216.228.2.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EF4643D95 for ; Tue, 29 Nov 2005 14:10:22 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 45964 invoked by uid 89); 29 Nov 2005 14:10:29 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-smtp.redshift.com with SMTP; 29 Nov 2005 14:10:29 -0000 Message-Id: <3.0.1.32.20051129061016.00a82848@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 06:10:16 -0800 To: Olaf Greve From: ray@redshift.com In-Reply-To: <438C5C03.2040505@axis.nl> References: <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Olaf Greve , amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 14:10:37 -0000 | Hehehe, "shorting the MoBo", eh? ;) | No problem... However I didn't have the documentation yesterday, so I | have just requested it. If all goes well, I should have it tonight, and | then I can check to see if there are CMOS reset jumpers. If supported, | that should be a dooze. I hope it'll do any magic then. There should be manuals in PDF on line. Motherboards have a shunt or jumper which you short that will erase the CMOS back to factory settings in the event of a catastrophic lockup. | BTW: in your opinion would you also suspect the FireWire controller to | indeed be clashing with the 9500S? Anything is possible :-) I've never had any problems with firewire in the past however. | > I know you aren't going to like to hear this, but perhaps a motherboard | > brand chance is in order? In the long run, it may save time/money. | | I hear you, and what's more, I hear you really well. If I cannot get | this combination to run VERY soon, I'll recommend them to do so, as a | different MoBo should be a lot cheaper (and a better solution in the | end) than me having to spend a lot of hours on it. ;) | Yet, personal pride and perseverance prevents me from throwing the towel | into the ring all too easily; I just can't stand it when I can't get | anything to work. But then, that might just be a personality issue. :D :-) Don't feel bad, I spent a week trying to resolve some strange SCSI RAID conflict with FreeBSD and some hardware not too long ago. Finally had to return the server. Never could pin down what was wrong exactly. | Definitly, and indeed I have heard a lot of good things about the Tyans. | I'm not certain if they're very common over here, but surely they must | be obtainable from provider that deliver server parts. I don't think the | client's provider has them, but if Asus doesn't do the trick; Tyan it'll | be... In the US - and this is strictly just my personal opinion - ASUS tends to be your run of the mill motherboard. I'm sure people will disagree with that, but that is how I have always viewed them. I have used ASUS motherboards in both servers and workstations over the years, but a few years ago we phased them out in favor of Tyan (for AMD) and Supermicro (for Xeon's). That's the only two brands we ever buy anymore and since limiting to those two companies, it's rare when a problem shows up. Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 14:16:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E3C416A41F for ; Tue, 29 Nov 2005 14:16:31 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E61443D45 for ; Tue, 29 Nov 2005 14:15:56 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id C16C0F7C5 for ; Tue, 29 Nov 2005 07:15:52 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 848F8F7BB for ; Tue, 29 Nov 2005 07:15:52 -0700 (MST) Date: Tue, 29 Nov 2005 07:15:51 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051129071551.1de69958.kgunders@teamcool.net> In-Reply-To: <438C5C03.2040505@axis.nl> References: <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> <438C5C03.2040505@axis.nl> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 14:16:31 -0000 On Tue, 29 Nov 2005 14:47:47 +0100 Olaf Greve wrote: > Hi, > > > Did you remove all the cards and clear the CMOS on the motherboard yet? > > The former: yes, the latter: no. > > > There should be a jumper you short. > > Hehehe, "shorting the MoBo", eh? ;) > No problem... However I didn't have the documentation yesterday, so I > have just requested it. If all goes well, I should have it tonight, and > then I can check to see if there are CMOS reset jumpers. If supported, > that should be a dooze. I hope it'll do any magic then. To clear the CMOS-- mainboards typically follow the convention of locating a 3 pin jumper near the battery. There should be a jumper on 2 of the pins, e.g. 1 & 2. Moving it to 2 & 3 will clear the CMOS memory. You should also be able to find details at Asus's website. They're pretty good about having docs available online. [snip] > > I know you aren't going to like to hear this, but perhaps a motherboard brand > > chance is in order? In the long run, it may save time/money. > > I hear you, and what's more, I hear you really well. If I cannot get > this combination to run VERY soon, I'll recommend them to do so, as a > different MoBo should be a lot cheaper (and a better solution in the > end) than me having to spend a lot of hours on it. ;) > Yet, personal pride and perseverance prevents me from throwing the towel > into the ring all too easily; I just can't stand it when I can't get > anything to work. But then, that might just be a personality issue. :D IMHO a good servef mobo is only going to be cheaper in the long run when you factor in the time you're spending screwing around w/ incompatibilities. It's probably going to cost you more cash up front. -- Best regards, Ken Gunderson 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 Nov 29 14:44:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E660B16A422; Tue, 29 Nov 2005 14:44:00 +0000 (GMT) (envelope-from mathieu.prevot@club-internet.fr) Received: from relay-cv.club-internet.fr (relay-cv.club-internet.fr [194.158.96.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84CC943D79; Tue, 29 Nov 2005 14:43:56 +0000 (GMT) (envelope-from mathieu.prevot@club-internet.fr) Received: from [192.168.0.5] (l07m-213-44-99-143.d4.club-internet.fr [213.44.99.143]) by relay-cv.club-internet.fr (Postfix) with ESMTP id B08AE25658; Tue, 29 Nov 2005 15:43:54 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mathieu Prevot Date: Tue, 29 Nov 2005 15:44:12 +0100 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.746.2) Cc: freebsd-amd64@freebsd.org, freebsd-ports@freebsd.org Subject: via 64 bits (adm64) driver in Xorg X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 14:44:01 -0000 Hi, The Xorg's via driver is compiled in 32bits but not in 64 bits (amd64). I tryed to force the compilation in 64 bits but it does not work (no screen found). Does someone knows (D. O'Brien...) what kind of rewriting the via source may need to work ? Is it much effort ? Regards, MP From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 15:06:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 525E516A41F for ; Tue, 29 Nov 2005 15:06:23 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B2B543D4C for ; Tue, 29 Nov 2005 15:06:15 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Eh73R-0003Jh-00; Tue, 29 Nov 2005 16:06:01 +0100 Message-ID: <438C6E52.7040605@axis.nl> Date: Tue, 29 Nov 2005 16:05:54 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> <20051129070805.7c6c5cef.kgunders@teamcool.net> In-Reply-To: <20051129070805.7c6c5cef.kgunders@teamcool.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: Olaf Greve , freebsd-amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 15:06:23 -0000 Hi Ken, Ray, and the list, > Try setting "Plug and Pray OS" to "No". Will do. And I'll also check the possibility of the CMOS clearing. It seems that at home we have internet again (at least: that's what I gather from my wife and daughter) so I can also at ease read up in the docs of the MoBo on how to achieve this. > IMHO the Asus was a sub optimal choice for a server board. I know. The MoBo in question seems to be a gamer's board, rather than a server board. The "issue" is that the client has a preferred supplier and they do not seem to have brands like Tyan (AFAIR). As an added ho-hum regarding using a gamer's board vs. a server board, there is of course the inherent difference in intended usage types, respectively fast graphics and CPU calculations vs. 24/7 reliability... Dunno how well these Asus-es perform in that respect......... > The mobo may > still be new enough to RMA in wh/case I'd go w/a non nVidia based Tyan > server board. Yes, I know the nVidia stuff is supported much better > under 6.0 than 5.4 but it's still not as mature as the AMD chipsets so > I'm still staying away form them for a while yet for applications like > webservers where rock solid stability is a concern Yes, this is definitely a thing to consider. I can see the client's point for wanting to get the Asus working (as they indeed to use the same architecture for future machines, and then of course it would be handy if they can readily achieve the parts from their own supplier), so I'll give it a few more shots tonight, but in case I can't get it to work, I'll make sure to stress the importance of sticking to server boards, and I'll then steer them towards a Tyan. On the bright side for the client: I'm not exactly charging them full-blown consultancy fees, as they are friends of mine; but even at the amounts they do pay me, the break-even point between added cost for a better MoBo vs. the required hours of me fiddling around with it will quickly be reached; and then the former has by far the preference as that has the added advantage of them having a better (suited) MoBo... > Olafo-- refresh my meory on this- what are the disk config requirements? RAID 10, 4x SATA 187GB. To be used in a semi high end MySQL database server, and for me software RAID is pretty much a no-no (unless all else fails). Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 15:18:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91C9616A41F for ; Tue, 29 Nov 2005 15:18:40 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-smtp.redshift.com (mail-smtp.redshift.com [216.228.2.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id A04EE43D5F for ; Tue, 29 Nov 2005 15:18:39 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 84989 invoked by uid 89); 29 Nov 2005 15:18:47 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-smtp.redshift.com with SMTP; 29 Nov 2005 15:18:47 -0000 Message-Id: <3.0.1.32.20051129071832.00a87dc8@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 07:18:32 -0800 To: Olaf Greve ,Ken Gunderson From: ray@redshift.com In-Reply-To: <438C6E52.7040605@axis.nl> References: <20051129070805.7c6c5cef.kgunders@teamcool.net> <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> <20051129070805.7c6c5cef.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Olaf Greve , freebsd-amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 15:18:40 -0000 | RAID 10, 4x SATA 187GB. To be used in a semi high end MySQL database | server, and for me software RAID is pretty much a no-no (unless all else | fails). If your clients are hoping for a high end reliable MySQL database, they sure picked a funny motherboard for it :) Like you say, I think that motherboard is popular with gamers. And usually those boards are designed for working great with the latest greatest video card and not much else. Tyan baby, tyan. Check their website for distributors. Or check some place like pricewatch.com and see how has the board you are looking for. I also have a distributor I use that is an AMD gold partner (or something like that). I would imagine they can ship pretty much wherever. If you need a contact for them, contact me off list. Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 15:32:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69AD916A41F for ; Tue, 29 Nov 2005 15:32:48 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 654F443D92 for ; Tue, 29 Nov 2005 15:32:35 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 616DBF7C5 for ; Tue, 29 Nov 2005 08:32:32 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 2AAB4F7BB for ; Tue, 29 Nov 2005 08:32:32 -0700 (MST) Date: Tue, 29 Nov 2005 08:32:31 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051129083231.1df4158e.kgunders@teamcool.net> In-Reply-To: <3.0.1.32.20051129071832.00a87dc8@pop.redshift.com> References: <20051129070805.7c6c5cef.kgunders@teamcool.net> <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> <20051129070805.7c6c5cef.kgunders@teamcool.net> <3.0.1.32.20051129071832.00a87dc8@pop.redshift.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 15:32:48 -0000 On Tue, 29 Nov 2005 07:18:32 -0800 ray@redshift.com wrote: > | RAID 10, 4x SATA 187GB. To be used in a semi high end MySQL database > | server, and for me software RAID is pretty much a no-no (unless all else > | fails). > > If your clients are hoping for a high end reliable MySQL database, they sure > picked a funny motherboard for it :) Like you say, I think that motherboard is > popular with gamers. And usually those boards are designed for working great > with the latest greatest video card and not much else. > > Tyan baby, tyan. Check their website for distributors. Or check some place > like pricewatch.com and see how has the board you are looking for. I also have > a distributor I use that is an AMD gold partner (or something like that). I > would imagine they can ship pretty much wherever. If you need a contact for > them, contact me off list. I'm waiting to see how things play out w/a DOA server before I buy/ recommend Tyan (other than this I have several w/no problems). Using an SLI based gaming board for a webserver was, IMHO, not the best use of logic regardless of preferred supplier issues. I am curious as to why they didn't opt for a dual Opteron for semi high-end database use. A dual core Athalon isn't going to come close. Not to mention that the Asus board doesn't use ECC Registered memory. Standardizing workstation and server stuff on same hw platform is bad planning. Unless, of course, one is expecting the venture to fail and hopes to redeploy that Asus board and dual core Athalon in their new high end gaming system... I, too, have my preferred suppliers. You'd be amazed at what they are capable of getting for you once they realize not doing so means you'll go elsewhere. Heck, mine now even brought the LSI line in as preferred RAID solution because they kept losing my biz when I refused to settle for Adaptec. But perhaps we're beating a dead horse here since client has their criteria. Good luck. -- Best regards, Ken Gunderson 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 Nov 29 16:35:35 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0457116A41F for ; Tue, 29 Nov 2005 16:35:35 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: from smtp2.versatel.nl (smtp2.versatel.nl [62.58.50.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF1A43D72 for ; Tue, 29 Nov 2005 16:35:32 +0000 (GMT) (envelope-from ogreve@millennics.com) Received: (qmail 6494 invoked by uid 0); 29 Nov 2005 16:35:30 -0000 Received: from unknown (HELO Millennics3) ([87.208.33.147]) (envelope-sender ) by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 29 Nov 2005 16:35:30 -0000 From: "Olaf Greve" To: , "Scott Long" Date: Tue, 29 Nov 2005 17:35:32 +0100 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <3.0.1.32.20051125123128.00a61c88@pop.redshift.com> Cc: ogreve@millennics.com, amd64@freebsd.org Subject: RE: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 16:35:35 -0000 Hi all, First off: thanks a lot for the most excellent replies and opinions; no worries they won't cause me to hang myself. ;) At this very moment I'm over at the client's site and we're assembling the machine, so this message will be short for now. As I feared, I'm still Internet-less at home though it was actually due to Versatel being physically unable to come over due to excessive high snowfall. Great. Just when you need Internet most there's no chance that I'll have it at home again for the next few days...:P Either way: just like I'm doing now, I'll make some selective print-outs of the various things mentioned in the threads about this topic and also of some of the FreeBSD pages (like the one about the custom kernel). All in all that should at the very least provide me with a proper roadmap. I'll definitely keep you all up to date (both on and off list) as to the progress of what'll happen with the installation, and as I have precious few hours over here today, I think I shall first stick with several standard things. The strategy I'll perform will be: 1-Install FreeBSD 6.0 Release (I'll give it a shot and if it doesn't work I'll fall back to 5.4). 2-Update the ports tree. 3-Install MySQL 4.1.x from the ports (I'll build it from there, after checking/tuning the makefile). 4-Build a custom kernel. 5-Import the DB dump. 6-Tune the DB. If I'll have enough time over here, I'll swap nrs. 3 and 4. O.k., thanks so far and I'll keep you guys informed! Thanks a lot for the excellent pointers, they were most useful in making the choices between the various versions etc. I hope sticking with 6.0 is indeed a good idea (I normally too tend to use Ray's philosophy of sticking with "non .0 versions"), but from what I gather the 6.0 version has already been pounded on a lot, so I'll give it a go. :) Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 16:40:10 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7DB516A41F for ; Tue, 29 Nov 2005 16:40:10 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail5.redshift.com (mail5.redshift.com [216.228.2.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7452943D76 for ; Tue, 29 Nov 2005 16:39:58 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 82580 invoked by uid 89); 29 Nov 2005 16:39:54 -0000 Received: by simscan 1.2.0 ppid: 82571, pid: 82572, t: 0.2128s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail5.redshift.com with SMTP; 29 Nov 2005 16:39:54 -0000 Message-Id: <3.0.1.32.20051129083950.00a82848@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 08:39:50 -0800 To: "Olaf Greve" ,"Scott Long" From: ray@redshift.com In-Reply-To: References: <3.0.1.32.20051125123128.00a61c88@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: ogreve@millennics.com, amd64@freebsd.org Subject: RE: FreeBSD 5.4 or 6 for DB server with 9500S-4 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 16:40:11 -0000 At 05:35 PM 11/29/2005 +0100, Olaf Greve wrote: | Hi all, | | First off: thanks a lot for the most excellent replies and opinions; no | worries they won't cause me to hang myself. ;) | | At this very moment I'm over at the client's site and we're assembling the | machine, so this message will be short for now. As I feared, I'm still | Internet-less at home though it was actually due to Versatel being | physically unable to come over due to excessive high snowfall. Great. Just | when you need Internet most there's no chance that I'll have it at home | again for the next few days...:P | | Either way: just like I'm doing now, I'll make some selective print-outs of | the various things mentioned in the threads about this topic and also of | some of the FreeBSD pages (like the one about the custom kernel). All in all | that should at the very least provide me with a proper roadmap. | | I'll definitely keep you all up to date (both on and off list) as to the | progress of what'll happen with the installation, and as I have precious few | hours over here today, I think I shall first stick with several standard | things. | | The strategy I'll perform will be: | | 1-Install FreeBSD 6.0 Release (I'll give it a shot and if it doesn't work | I'll fall back to 5.4). | 2-Update the ports tree. | 3-Install MySQL 4.1.x from the ports (I'll build it from there, after | checking/tuning the makefile). | 4-Build a custom kernel. | 5-Import the DB dump. | 6-Tune the DB. | | If I'll have enough time over here, I'll swap nrs. 3 and 4. | | O.k., thanks so far and I'll keep you guys informed! Thanks a lot for the | excellent pointers, they were most useful in making the choices between the | various versions etc. I hope sticking with 6.0 is indeed a good idea (I | normally too tend to use Ray's philosophy of sticking with "non .0 | versions"), but from what I gather the 6.0 version has already been pounded | on a lot, so I'll give it a go. :) | | Cheers! | Olafo Hi Olafo, I'm sure 6.0 is fine :-) BTW, you might want to tweak /etc/make.conf before you compile MySQL and the kernel, etc. There are a couple of things you can add in there that might speed the machine up a bit. Although until you get it running, it might be better off not to introduce more variables :) Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 16:52:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2F8A16A420 for ; Tue, 29 Nov 2005 16:52:47 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-webmail.redshift.com (mail-webmail.redshift.com [216.228.2.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id D673A43D69 for ; Tue, 29 Nov 2005 16:52:25 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 26218 invoked by uid 89); 29 Nov 2005 16:52:19 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-webmail.redshift.com with SMTP; 29 Nov 2005 16:52:19 -0000 Message-Id: <3.0.1.32.20051129085212.00a50918@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Tue, 29 Nov 2005 08:52:12 -0800 To: Ken Gunderson ,freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <20051129083231.1df4158e.kgunders@teamcool.net> References: <3.0.1.32.20051129071832.00a87dc8@pop.redshift.com> <20051129070805.7c6c5cef.kgunders@teamcool.net> <438C2322.8020801@axis.nl> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <20051119200222.V2029@roble.com> <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> <3.0.1.32.20051129051812.00a87dc8@pop.redshift.com> <20051129070805.7c6c5cef.kgunders@teamcool.net> <3.0.1.32.20051129071832.00a87dc8@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 16:52:48 -0000 | I'm waiting to see how things play out w/a DOA server before I buy/ | recommend Tyan (other than this I have several w/no problems). Using | an SLI based gaming board for a webserver was, IMHO, not the best use | of logic regardless of preferred supplier issues. I am curious as to | why they didn't opt for a dual Opteron for semi high-end database use. | A dual core Athalon isn't going to come close. Not to mention that the | Asus board doesn't use ECC Registered memory. Standardizing workstation | and server stuff on same hw platform is bad planning. Unless, of | course, one is expecting the venture to fail and hopes to redeploy that | Asus board and dual core Athalon in their new high end gaming system... LOL - just tell us how you really feel Ken :-) Ray From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 18:23:18 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53FFB16A423 for ; Tue, 29 Nov 2005 18:23:18 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6D4643D6B for ; Tue, 29 Nov 2005 18:23:16 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: by nproxy.gmail.com with SMTP id l23so566005nfc for ; Tue, 29 Nov 2005 10:23:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=nUrBmpBMkrzzKV3kbWS0t7MxkyJdtArKNbCXvcTMJSNjRD7YsvXGesCeDXykxbWyqLX08VdD30qhiOFbvaE1AtZqDp82BDDMGqjO7DiYBvvCl1nAjY1ZjyRd45h4/EfhN7dI/lzd54VlN7hQ04vkggIHJYrN3k7ZFJq06BXUjhg= Received: by 10.48.220.6 with SMTP id s6mr611637nfg; Tue, 29 Nov 2005 10:23:15 -0800 (PST) Received: by 10.48.162.4 with HTTP; Tue, 29 Nov 2005 10:23:15 -0800 (PST) Message-ID: Date: Tue, 29 Nov 2005 10:23:15 -0800 From: Tom Cumming To: Olaf Greve In-Reply-To: <438C2322.8020801@axis.nl> MIME-Version: 1.0 References: <20051119120051.39BE216A41F@hub.freebsd.org> <20051119200222.V2029@roble.com> <3.0.1.32.20051121055411.00aa1490@pop.redshift.com> <3.0.1.32.20051125041044.00a47720@pop.redshift.com> <3.0.1.32.20051125121159.00a5d2f8@pop.redshift.com> <438B0CEC.4070308@wmptl.com> <438C2322.8020801@axis.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 18:23:18 -0000 This may be your problem: > Firmware: FE9X 2.06.00.009 ... and... -Can't drain the AEN queue -Driver/Firmware mismatch <------------------------------------------ !!! -Unposted command completed!! The firmware version on my card is FE9X 2.08.00.003 From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 19:06:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B374616A420 for ; Tue, 29 Nov 2005 19:06:46 +0000 (GMT) (envelope-from johan@granlund.nu) Received: from cleaver.granlund.nu (84-246-94-171.rev.ownit.se [84.246.94.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3090943D83 for ; Tue, 29 Nov 2005 19:06:35 +0000 (GMT) (envelope-from johan@granlund.nu) Received: from [192.168.0.10] (hatchet.granlund.nu [192.168.0.10]) (authenticated bits=0) by cleaver.granlund.nu (8.13.4/8.13.4) with ESMTP id jATJ66hj007063 for ; Tue, 29 Nov 2005 20:06:07 +0100 (CET) (envelope-from johan@granlund.nu) Message-ID: <438CA689.7080602@granlund.nu> Date: Tue, 29 Nov 2005 20:05:45 +0100 From: Johan Granlund User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) 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 X-Virus-Scanned: ClamAV 0.87.1/1198/Tue Nov 29 11:05:20 2005 on cleaver.granlund.nu X-Virus-Scanned: amavisd-new at granlund.nu X-Virus-Status: Clean Subject: Linux Boinc and project climateprediction.net X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 19:06:46 -0000 Hi all, I'm trying to run Linux Boinc and project climateprediction.net. When boinc starts the climateprediction.net application I get the following messages: ============================================================ Starting model in /usr/compat/linux/opt/BOINC/projects/climateprediction.net... Created shared memory region key = 77930 Can't setup pointer to .so shared memory sulphur_4.21_i686-pc-linux-gnu: undefined symbol: setupSharedMem! Can't setup pointer to .so graphics cleanup sulphur_4.21_i686-pc-linux-gnu: undefined symbol: graphics_thread_cleanup Copying files for startup... Starting model ID sulphur_dh6t_000628805 Phase 1 Waiting for model startup, this may take a minute... ============================================================ and there it hangs. I can see that a sulphur.... is started, but it dont seem to do anything useful. Is there a limitation on shared memory usage, or is I missing something in my configuration? The machine is running 7-Current/amd64 /Johan From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 29 19:13:10 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEB8916A425 for ; Tue, 29 Nov 2005 19:13:10 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from sdcexchange01.amcc.com (gatekeeper-out.amcc.com [198.137.200.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D39D43D77 for ; Tue, 29 Nov 2005 19:12:58 +0000 (GMT) (envelope-from vkashyap@amcc.com) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Importance: normal Priority: normal Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 29 Nov 2005 11:12:52 -0800 Message-ID: <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: More about the 9500S-4 issues with the MoBo and FreeBSD... thread-index: AcX0yZiMg+GUdsO3R7KfM2sG+pYRtAATtPjA From: "Vinod Kashyap" To: "Olaf Greve" , "Nathan Vidican" , Cc: amd64@freebsd.org Subject: RE: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2005 19:13:11 -0000 >=20 >=20 > The 9500S BIOS reports the following upon booting: > Escalade 9500S-4LP > BIOS: BE9X 2.03.01.051 > Firmware: FE9X 2.06.00.009 >=20 >=20 > The short FreeBSD error/info is: > 3ware device driver for 9000 series storage controllers,=20 > version 3.60.00.017 > twa0: <3ware 9000 series storage controller> port=20 > 0xa000-0xa0ff mem 0xd8005000-0xd80050ff,=20 > 0xd2000000-0xd27fffff irq 18 at device 8.0 on pci5 > twa0: [GIANT-LOCKED] > twa0: Error: (0x15: 0x1201): Unposted command completed!!:=20 > Request=3D0xffffffff810452ee, status=3D0 > twa0: INFO: (0x16: 0x1108): Resetting controller...: >=20 >=20 > At that point FreeBSD hangs. Are you sure you have the installation CD for amd64? The error messages make me think you might be using an i386 version of the CD. >=20 > The other version of errors show many more errors (which flash by too=20 > quickly in order to be written down, and the "pause" key=20 > doesn't pause=20 > the screen). They include things like: > -Can't drain the AEN queue > -Driver/Firmware mismatch > -Unposted command completed!! >=20 > And several other things... >=20 > I hope someone has any idea or a solution, as it's not really=20 > an option=20 > to use the on-board RAID controller for obvious reasons, and we also=20 > really rather would not want to have to use a different MoBo...:(( >=20 > Thanks again, and cheers! > Olafo >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to=20 > "freebsd-amd64-unsubscribe@freebsd.org" > -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, = is for the sole use of the intended recipient(s) and contains = information that is confidential and proprietary to Applied Micro = Circuits Corporation or its subsidiaries. It is to be used solely for = the purpose of furthering the parties' business relationship. All = unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply = e-mail and destroy all copies of the original message. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 01:57:41 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6D7116A420 for ; Wed, 30 Nov 2005 01:57:41 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DC8E43D8E for ; Wed, 30 Nov 2005 01:57:36 +0000 (GMT) (envelope-from dantavious@comcast.net) Received: from [192.168.1.109] (pcp0011002249pcs.longhl01.md.comcast.net[68.55.192.50]) by comcast.net (sccrmhc12) with ESMTP id <2005113001572901200be46ae>; Wed, 30 Nov 2005 01:57:33 +0000 From: Derrick Edwards To: amd64@freebsd.org Date: Tue, 29 Nov 2005 20:57:12 -0500 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511292057.13225.dantavious@comcast.net> Cc: Subject: 64bit FreeBSD performance X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 01:57:42 -0000 All, I purchased a amd anthlon 64 3700 (754) to be used with VMWARE 5.5. FreeBSD was going to be the guest OS. It seems that VMWARE only works with amd 64 bit (939). I was wondering if the performance gain of FreeBSD 64 bit really be significant compared to 32bit FreeBSD. I was also wondering if all the ports for FreeBSD 64 running as 64 bit applications. If the performance is minimal then I will not go through the hassle of sending stuff back. v/r Derrick From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 02:04:36 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4418916A420 for ; Wed, 30 Nov 2005 02:04:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C068343D72 for ; Wed, 30 Nov 2005 02:04:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7B7E81A3C25; Tue, 29 Nov 2005 18:04:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7417751469; Tue, 29 Nov 2005 21:04:24 -0500 (EST) Date: Tue, 29 Nov 2005 21:04:24 -0500 From: Kris Kennaway To: Derrick Edwards Message-ID: <20051130020424.GA62452@xor.obsecurity.org> References: <200511292057.13225.dantavious@comcast.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <200511292057.13225.dantavious@comcast.net> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org Subject: Re: 64bit FreeBSD performance X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 02:04:36 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 29, 2005 at 08:57:12PM -0500, Derrick Edwards wrote: > All, > I purchased a amd anthlon 64 3700 (754) to be used with VMWARE 5.5. FreeB= SD=20 > was going to be the guest OS. It seems that VMWARE only works with amd 64= bit=20 > (939). I was wondering if the performance gain of FreeBSD 64 bit really b= e=20 > significant compared to 32bit FreeBSD. Entirely depends on your application. > I was also wondering if all the ports=20 > for FreeBSD 64 running as 64 bit applications. Except for ports of precompiled i386 binary applications, they are all natively compiled (i.e. "64-bit"). Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDjQioWry0BWjoQKURAs60AJ9a4BsanH0JwB9bOJpGAONG5pWmlgCfb9D2 UgzwNVv8chUW8DZXYGo/XzM= =+mbh -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 03:08:03 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD31116A41F for ; Wed, 30 Nov 2005 03:08:03 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from skewer.dreamhost.com (skewer.dreamhost.com [64.111.107.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 093E543D5F for ; Wed, 30 Nov 2005 03:08:01 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by skewer.dreamhost.com (Postfix) with ESMTP id 574017C5AE for ; Tue, 29 Nov 2005 19:08:01 -0800 (PST) From: Dev Tugnait To: amd64@freebsd.org In-Reply-To: <20051130020424.GA62452@xor.obsecurity.org> References: <200511292057.13225.dantavious@comcast.net> <20051130020424.GA62452@xor.obsecurity.org> Content-Type: text/plain Date: Tue, 29 Nov 2005 22:07:58 -0500 Message-Id: <1133320078.48495.14.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: 64bit FreeBSD performance X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2005 03:08:03 -0000 How do you check to see if a port is? On Tue, 2005-11-29 at 21:04 -0500, Kris Kennaway wrote: > Except for ports of precompiled i386 binary application -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 03:22:35 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E04A16A423 for ; Wed, 30 Nov 2005 03:22:35 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from whisk.dreamhost.com (whisk.dreamhost.com [205.196.208.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3CB243D46 for ; Wed, 30 Nov 2005 03:22:29 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by whisk.dreamhost.com (Postfix) with ESMTP id 1679E7F055 for ; Tue, 29 Nov 2005 19:22:27 -0800 (PST) From: Dev Tugnait To: amd64@freebsd.org Content-Type: text/plain Date: Tue, 29 Nov 2005 22:22:27 -0500 Message-Id: <1133320947.48495.17.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Nividia Drivers X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2005 03:22:35 -0000 I am just curious if any of the developers have any idea about this? Nvidia forums refuse to disclose any information if at all amd64 nvidia graphic drivers will be released. Just wondering if someone has some information on whats going on there. Thanks -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 03:28:47 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4805B16A41F for ; Wed, 30 Nov 2005 03:28:47 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C68043D53 for ; Wed, 30 Nov 2005 03:28:47 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3C58E1A3C29; Tue, 29 Nov 2005 19:28:46 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 996AD514DF; Tue, 29 Nov 2005 22:28:45 -0500 (EST) Date: Tue, 29 Nov 2005 22:28:45 -0500 From: Kris Kennaway To: Dev Tugnait Message-ID: <20051130032845.GA63316@xor.obsecurity.org> References: <200511292057.13225.dantavious@comcast.net> <20051130020424.GA62452@xor.obsecurity.org> <1133320078.48495.14.camel@dracula> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <1133320078.48495.14.camel@dracula> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org Subject: Re: 64bit FreeBSD performance X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 03:28:47 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 29, 2005 at 10:07:58PM -0500, Dev Tugnait wrote: > How do you check to see if a port is? Look for ports that depend on a compat?x port, or use file(1) by hand on the binaries it installs. In general there's no reason to worry though, there are only a handful of such ports (if you exclude linux binaries). Kris --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDjRxtWry0BWjoQKURAoshAJ4vd8qIR5bUEgLPlwPexJC8868LJwCggE/s DKZbTQVXxEvUO18961dI0/M= =anUn -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 03:52:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44ED416A422 for ; Wed, 30 Nov 2005 03:52:43 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id D40D343D98 for ; Wed, 30 Nov 2005 03:52:27 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id A01F8F7C5 for ; Tue, 29 Nov 2005 20:52:26 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 600A2F7BB for ; Tue, 29 Nov 2005 20:52:26 -0700 (MST) Date: Tue, 29 Nov 2005 20:52:25 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051129205225.66fa0c4e.kgunders@teamcool.net> In-Reply-To: <20051130032845.GA63316@xor.obsecurity.org> References: <200511292057.13225.dantavious@comcast.net> <20051130020424.GA62452@xor.obsecurity.org> <1133320078.48495.14.camel@dracula> <20051130032845.GA63316@xor.obsecurity.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: 64bit FreeBSD performance X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 03:52:43 -0000 On Tue, 29 Nov 2005 22:28:45 -0500 Kris Kennaway wrote: > On Tue, Nov 29, 2005 at 10:07:58PM -0500, Dev Tugnait wrote: > > How do you check to see if a port is? > > Look for ports that depend on a compat?x port, or use file(1) by hand > on the binaries it installs. In general there's no reason to worry > though, there are only a handful of such ports (if you exclude linux > binaries). > > Kris > FYI- DarwinStreamingServer port is one such port. -- Best regards, Ken Gunderson 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 Wed Nov 30 08:19:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0861116A41F for ; Wed, 30 Nov 2005 08:19:53 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FA2743D53 for ; Wed, 30 Nov 2005 08:19:52 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so1664764nzo for ; Wed, 30 Nov 2005 00:19:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=E6WBHN/bEWPy9iJtIxvM9JCrzfhkrRwGbZmBuZomAs/E+sNATlpiVXMe5qLTHZnPsNeeLM3MQ7Calzzg5ieyTdbNF8jVdcr3MHDHSyQcJfOdZL1lkik27zU0hLBXykSq0Sh1zrJ0CeTw3/ABjjNcpsy7Ql/H/wQLoX7iM7qBsO4= Received: by 10.64.249.18 with SMTP id w18mr5282894qbh; Wed, 30 Nov 2005 00:19:52 -0800 (PST) Received: by 10.64.196.13 with HTTP; Wed, 30 Nov 2005 00:19:51 -0800 (PST) Message-ID: <4bdd3edf0511300019u1138a137g@mail.gmail.com> Date: Wed, 30 Nov 2005 10:19:51 +0200 From: Popov Maxim To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 08:19:53 -0000 I installed FreeBSD 6.0 for AMD64 ... In my kernel configuration i wrote this: options VESA (to get a high resolution in the console). In the i386 version of the FreeBSD it worked, but know it says: VESA: no such option (or something like that). What's wrong ??? From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 08:38:00 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6235216A41F for ; Wed, 30 Nov 2005 08:38:00 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E571243D49 for ; Wed, 30 Nov 2005 08:37:59 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id E81471FFACA; Wed, 30 Nov 2005 09:37:57 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 6764C1FFAD2; Wed, 30 Nov 2005 09:37:55 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id D3B3E444F6B; Wed, 30 Nov 2005 08:30:35 +0000 (UTC) Date: Wed, 30 Nov 2005 08:30:35 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Dev Tugnait In-Reply-To: <1133320947.48495.17.camel@dracula> Message-ID: <20051130082553.I23990@maildrop.int.zabbadoz.net> References: <1133320947.48495.17.camel@dracula> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: amd64@freebsd.org Subject: Re: Nividia Drivers X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 08:38:00 -0000 On Tue, 29 Nov 2005, Dev Tugnait wrote: > I am just curious if any of the developers have any idea about this? > Nvidia forums refuse to disclose any information if at all amd64 nvidia > graphic drivers will be released. Just wondering if someone has some > information on whats going on there. you might find the answer in the mailing list archive of this months current@. Search for Message-Id: <200511071256.04488.jhb@freebsd.org> on http://www.freebsd.org/search/search-mid.html -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 08:57:00 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4278C16A41F for ; Wed, 30 Nov 2005 08:57:00 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F2843D64 for ; Wed, 30 Nov 2005 08:56:58 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1EhNl9-0004jF-00; Wed, 30 Nov 2005 09:56:15 +0100 Message-ID: <438D6926.8070807@axis.nl> Date: Wed, 30 Nov 2005 09:56:06 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vinod Kashyap References: <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> In-Reply-To: <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 08:57:00 -0000 Hi, > Are you sure you have the installation CD for amd64? The error messages > make me think you might be using an i386 version of the CD. ???? Well, I D/L-ed it from the French (I think) FreeBSD mirror from the AMD64 directory... Having said that, I did notice the CDs bootstrap loader mentions freebsd/i386 (I meant to ask about that one). If indeed I somehow was totally numb (a thing which I cannot entirely exclude given some of the following I'm about to type) and made such a stupid mistake myself, then that could certainly explain a lot. However.... that still wouldn't explain why FreeBSD 5.4-release AMD64 also chokes on it; and on that CD I am 100% positive it's the AMD64 version, as I have installed it on my own AMD64 machine from the very same CDs. Also, really, I am about 99% (if not 100%) sure that I made very certain to D/L the AMD64 version. The ISO images also reflected that name (I think), so it's not very likely it's the i386 version. Then: I'm amased. Really I am. As the client needs this machine to be up an running this Friday, yesterday evening I decided to opt for a different strategy: install this machine using the on-board RAID controller, then in the meantime ask the client to order an Opteron (or dual Opteron) with a Tyan MoBo, install, tune and test that one at ease and then when it's all set-up swap that with the machine I'm currently working on. So, just when I thought I had a workable strategy again, look at what horrors were bestowed upon me next: the Sil 3114 on-board RAID controller recognises the drives, enters the BIOS, but when confirming the total RAID array size it totally hangs! And that's the controller's BIOS; it didn't even get to the point where one could install FreeBSD (or anything else for that matter). So, with "Plan B" out, there was even a "Plan C": use the nVidia on-board RAID controller. O.k., I plugged over the SATA controllers, configured the MoBo's BIOS to do this, and what do ya guess? Indeed, another full blown controller hang. Nice. :( Well, over the past 15 years I must have installed dozens of machines (several of them including Asus boards, in combination with Adaptec SCSI RAID controllers and various different versions and flavours (i.e. 1386/amd64) of FreeBSD), with OS-es ranging from MS-DOS, through the full array of W*nd*wses, FreeBSDs, Linuxes, and I can hardly recall any more troublesome installation process than this time; really, it reminds me of the good 'ole MS-DOS days where one had to jumper each and every ISA board and then tweak memory configurations in order to get the lot going. :(((((( Actually, I think something is simply b*ll*xed up on the board, but I just can't put my finger on what it is. Surele even if it is primarily a gaming board, still these type of errors should not have occurred. I spent the better part of late last evening and the wee hours on reading the MoBo's docs, and checking if we perhaps missed something. I didn't spot anything, but something MUST be off... :(((( Dunno. Time for a "plan D" I guess; I'll ask if the client can somehow get a working machine, and then I'll pull two more late nighters to at least get the bit I was supposed to do done: installing and tuning FreeBSD and MySQL. At present it's highly frustrating that I can't even really reach the OS installation part...:(((( OK, guys thanks for hanging in there with me. I'm sure some day in the future I can laugh out loud at it too, just not right now....;) Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 11:42:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4E2116A41F for ; Wed, 30 Nov 2005 11:42:34 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31CD143D64 for ; Wed, 30 Nov 2005 11:42:33 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-121.dynamic.qsc.de [212.202.37.121]) by efacilitas.de (Postfix) with ESMTP id DE0E94B1F3; Wed, 30 Nov 2005 12:50:35 +0100 (CET) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id 1461D508A9; Wed, 30 Nov 2005 12:41:28 +0100 (CET) Message-ID: <438D902B.6040801@cs.tu-berlin.de> Date: Wed, 30 Nov 2005 12:42:35 +0100 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Popov Maxim References: <4bdd3edf0511300019u1138a137g@mail.gmail.com> In-Reply-To: <4bdd3edf0511300019u1138a137g@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 11:42:34 -0000 Popov Maxim schrieb: > I installed FreeBSD 6.0 for AMD64 ... > > In my kernel configuration i wrote this: options VESA (to get a high > resolution in the console). In the i386 version of the FreeBSD it > worked, but know it says: > VESA: no such option (or something like that). > > What's wrong ??? The current console VESA driver is for i386 only. I guess it is not well adapted for amd64. Björn From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 12:50:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3419D16A41F for ; Wed, 30 Nov 2005 12:50:34 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8182843D5A for ; Wed, 30 Nov 2005 12:50:33 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so89248wri for ; Wed, 30 Nov 2005 04:50:27 -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:content-disposition:references; b=f8TrqXTf414Rn8XkRPh2sgryDPobzStQBAYzWNd1d7eDWTYRQdm/Xb1Xxtlpav3CIlis7+zmb9KLtb3low5IyC6oDZiXHoq7gZtnPfpOHm2znkh+N9+WdJV1leoOGOnSxSnX7rbBXGctvNKFr/YWjlqfcw0lcYeuenCHhy8dIrI= Received: by 10.64.193.4 with SMTP id q4mr113488qbf; Wed, 30 Nov 2005 04:50:27 -0800 (PST) Received: by 10.65.72.5 with HTTP; Wed, 30 Nov 2005 04:50:26 -0800 (PST) Message-ID: Date: Wed, 30 Nov 2005 20:50:26 +0800 From: Xin LI To: Popov Maxim In-Reply-To: <4bdd3edf0511300019u1138a137g@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <4bdd3edf0511300019u1138a137g@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 30 Nov 2005 12:50:34 -0000 SGksCgpPbiAxMS8zMC8wNSwgUG9wb3YgTWF4aW0gPHBvcG92Lm1heEBnbWFpbC5jb20+IHdyb3Rl Ogo+IEluIG15IGtlcm5lbCBjb25maWd1cmF0aW9uIGkgd3JvdGUgdGhpczogb3B0aW9ucyBWRVNB ICh0byBnZXQgYSBoaWdoCj4gcmVzb2x1dGlvbiBpbiB0aGUgY29uc29sZSkuIEluIHRoZSBpMzg2 IHZlcnNpb24gb2YgdGhlIEZyZWVCU0QgaXQKPiB3b3JrZWQsIGJ1dCBrbm93IGl0IHNheXM6Cj4g VkVTQTogbm8gc3VjaCBvcHRpb24gKG9yIHNvbWV0aGluZyBsaWtlIHRoYXQpLgoKQ3VycmVudGx5 IFZFU0EgaXMgbm90IGF2YWlsYWJsZSBmb3IgYW1kNjQga2VybmVscy4uLiAgSSB0aGluayB5b3Ug bWF5CndhbnQgdG8gZG8gc29tZSBzbWFsbCBoYWNraW5nIHRvIGZvcmNlbHkgYWRkIGl0LCBidXQg SSBhbSBub3Qgc3VyZQp3aGV0aGVyIGl0IHdvcmtzIHdlbGwgdGhhdCB3YXkuLi4KCkNoZWVycywK LS0KWGluIExJIDxkZWxwaGlqQGRlbHBoaWoubmV0PiBodHRwOi8vd3d3LmRlbHBoaWoubmV0Cg== From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 13:28:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 978CD16A41F for ; Wed, 30 Nov 2005 13:28:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id F132B43D46 for ; Wed, 30 Nov 2005 13:28:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2869913 for multiple; Wed, 30 Nov 2005 08:26:54 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAUDSr8I080419; Wed, 30 Nov 2005 08:28:53 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org, delphij@delphij.net Date: Wed, 30 Nov 2005 08:28:50 -0500 User-Agent: KMail/1.8.3 References: <4bdd3edf0511300019u1138a137g@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511300828.51685.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 X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Popov Maxim Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 13:28:57 -0000 On Wednesday 30 November 2005 07:50 am, Xin LI wrote: > Hi, > > On 11/30/05, Popov Maxim wrote: > > In my kernel configuration i wrote this: options VESA (to get a high > > resolution in the console). In the i386 version of the FreeBSD it > > worked, but know it says: > > VESA: no such option (or something like that). > > Currently VESA is not available for amd64 kernels... I think you may > want to do some small hacking to forcely add it, but I am not sure > whether it works well that way... VESA needs to talk to the BIOS of the video card. On i386, we use vm86 mod= e=20 to execute the VESA BIOS code, but on amd64's long mode, there is no vm86=20 mode, so we have now way to talk to the VESA BIOS on amd64. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 14:48:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 046E316A41F for ; Wed, 30 Nov 2005 14:48:27 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C65C843D78 for ; Wed, 30 Nov 2005 14:48:24 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id BD8C1B854; Wed, 30 Nov 2005 16:48:23 +0200 (EET) Received: (nullmailer pid 22643 invoked by uid 1002); Wed, 30 Nov 2005 14:48:23 -0000 Date: Wed, 30 Nov 2005 16:48:23 +0200 From: Vasil Dimov To: Popov Maxim Message-ID: <20051130144823.GA22623@qlovarnika.bg.datamax> References: <4bdd3edf0511300019u1138a137g@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline In-Reply-To: <4bdd3edf0511300019u1138a137g@mail.gmail.com> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 Cc: freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2005 14:48:27 -0000 --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 30, 2005 at 10:19:51AM +0200, Popov Maxim wrote: > I installed FreeBSD 6.0 for AMD64 ... >=20 > In my kernel configuration i wrote this: options VESA (to get a high > resolution in the console). In the i386 version of the FreeBSD it > worked, but know it says: > VESA: no such option (or something like that). >=20 > What's wrong ??? http://lists.freebsd.org/pipermail/freebsd-amd64/2005-October/006376.html --=20 Vasil Dimov --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFDjbu2Fw6SP/bBpCARAgaXAKCqi4vIDSUlOvgzwu336GDySyuStQCeOnF8 SQo8Anp4Uh54L+8v2zyHUjQ= =R7tD -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 15:48:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3B8B16A41F for ; Wed, 30 Nov 2005 15:48:29 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26A3543D53 for ; Wed, 30 Nov 2005 15:48:29 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by zproxy.gmail.com with SMTP id q3so21655nzb for ; Wed, 30 Nov 2005 07:48:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z8tmkaZ3mW6hjqe6/IRKZ93GJPSonYSZ+SVF9Q6k2ZLCjqlezMv1jjHr1fBX3TLzZEW4AZ9SXWaPF2wx7LylBZSfJ57Lh4Xf9QOO8ogN3M17U6ISHg/Vkmh+Sz/xO97wsoq2IVfhHQUs0JrrWzVqrR0oCqd8/jxysGyQHHaxxRc= Received: by 10.65.116.15 with SMTP id t15mr228776qbm; Wed, 30 Nov 2005 07:48:27 -0800 (PST) Received: by 10.65.112.13 with HTTP; Wed, 30 Nov 2005 07:48:27 -0800 (PST) Message-ID: <1d6d20bc0511300748m1adedb31t@mail.gmail.com> Date: Wed, 30 Nov 2005 23:48:27 +0800 From: Jia-Shiun Li To: Derrick Edwards In-Reply-To: <200511272146.48247.dantavious@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511272146.48247.dantavious@comcast.net> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD amd 64 and VMWARE issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 15:48:30 -0000 Derrick, You must have 1.Windows x64 edition as host 2.VMWare Workstation 5.5 (from which begins to support amd64 guests) to install amd64 version as guest OS. JIa-Shiun. 2005/11/28, Derrick Edwards : > Hi, > I am trying to install FreeBSD amd 6.0 release as a guest operating syste= m on > VMWARE 5.0. I have a ABIT KU8 motherboard and AMD 64 anthlon 3700. If I > install Freebsd 6 amd 64 by itself I works great. I only get the followin= g > error when installing it in VMWARE. > Please help > v/r > Derrick > > iint=3D0000000d err=3D00000000 efl=3D00010006 eip=3D00027995 > eax=3D00000100 ebx=3D00000000 ecx=3Dc0000080 edx=3D00000000 > esi=3D00036000 edi=3D00035000 ebp=3D000948a4 esp=3D0009e870 > cs=3D0008 ds=3D0010 es=3D0010 fs=3D0010 gs=3D0010 ss=3D0010 > cs:eip:0f 30 of 20 e0 83 30-of 22 e0 b8 00 f0 03 00 > 0f 22 d8 0f 20 c0 0d 00-00 00 80 0f 22 c0 b8 00 > ss:esp:69 95 00 00 00 20 d7 00-00 30 d7 00 00 00 10 04 00 > 00 00 00 00 00 00 04 00-00 00 00 00 20 d7 00 > BTX Halted > _______________________________________________ > 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 Wed Nov 30 16:43:43 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 549DA16A41F for ; Wed, 30 Nov 2005 16:43:43 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8471E43D5C for ; Wed, 30 Nov 2005 16:43:42 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: by nproxy.gmail.com with SMTP id k26so10476nfc for ; Wed, 30 Nov 2005 08:43:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ZqAFtFAI+yGAIrkuUJcoeIzGYvZf6YpjOkZYx3Bqjb0k+ELtdZAzH/IiTG5spbNLufNYnI3v+M0PDOClCQsbxxAEbPHCpGhtan3sQHhDtQy6iKj579vwsf8x7HpfKrm6OBkH9YOLq5dWWAfxDQ5T1tf7FsslBMFilwa2JMJWWwE= Received: by 10.48.223.6 with SMTP id v6mr38264nfg; Wed, 30 Nov 2005 08:43:40 -0800 (PST) Received: by 10.48.162.4 with HTTP; Wed, 30 Nov 2005 08:43:40 -0800 (PST) Message-ID: Date: Wed, 30 Nov 2005 08:43:40 -0800 From: Tom Cumming To: Olaf Greve In-Reply-To: <438D6926.8070807@axis.nl> MIME-Version: 1.0 References: <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> <438D6926.8070807@axis.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 16:43:43 -0000 Did you try flashing the card? Your running old firmware, and you do have a driver/firmware mismatch. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 16:45:51 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 359F116A41F for ; Wed, 30 Nov 2005 16:45:50 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail6.redshift.com (mail6.redshift.com [216.228.2.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DA3B43D45 for ; Wed, 30 Nov 2005 16:45:50 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 30773 invoked by uid 89); 30 Nov 2005 16:45:47 -0000 Received: by simscan 1.2.0 ppid: 30769, pid: 30770, t: 0.1618s scanners: clamav: 0.87/m:34/d:1191 Received: from unknown (HELO workstation) (216.228.19.21) by mail6.redshift.com with SMTP; 30 Nov 2005 16:45:47 -0000 Message-Id: <3.0.1.32.20051130084540.00a57480@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Wed, 30 Nov 2005 08:45:40 -0800 To: Tom Cumming ,Olaf Greve From: ray@redshift.com In-Reply-To: References: <438D6926.8070807@axis.nl> <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> <438D6926.8070807@axis.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 16:45:51 -0000 At 08:43 AM 11/30/2005 -0800, Tom Cumming wrote: | Did you try flashing the card? Your running old firmware, and you do have a | driver/firmware mismatch. Tom has a very strong point here! :) Ray From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 16:51:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0036316A41F for ; Wed, 30 Nov 2005 16:51:37 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42E7B43D69 for ; Wed, 30 Nov 2005 16:51:34 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5FEFD.dip.t-dialin.net [84.165.254.253]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAUGpPwi036517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Nov 2005 17:51:30 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jAUGpCGC059510; Wed, 30 Nov 2005 17:51:12 +0100 (CET) Message-ID: <438DD87C.9060906@deadcafe.de> Date: Wed, 30 Nov 2005 17:51:08 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Jia-Shiun Li References: <200511272146.48247.dantavious@comcast.net> <1d6d20bc0511300748m1adedb31t@mail.gmail.com> In-Reply-To: <1d6d20bc0511300748m1adedb31t@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD amd 64 and VMWARE issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 16:51:38 -0000 Jia-Shiun Li schrieb: > Derrick, > > You must have > 1.Windows x64 edition as host You can run an 64 bit guest OS on a 32 bit Windows host. > 2.VMWare Workstation 5.5 (from which begins to support amd64 guests) > to install amd64 version as guest OS. > 2005/11/28, Derrick Edwards : > >> Hi, >>I am trying to install FreeBSD amd 6.0 release as a guest operating system on >>VMWARE 5.0. I have a ABIT KU8 motherboard and AMD 64 anthlon 3700. If I >>install Freebsd 6 amd 64 by itself I works great. I only get the following >>error when installing it in VMWARE. 3. You need an Athlon64/Opteron processor with at least D-Stepping. AFAIK all Socket 754 processors are stepping CG or lower. So I don't think you will have any luck even with the current VMWare release. http://www.amdcompare.com/us-en/desktop/Default.aspx Daniel From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 17:11:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7604216A41F for ; Wed, 30 Nov 2005 17:11:02 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B66743D60 for ; Wed, 30 Nov 2005 17:11:01 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 513A8F7C5 for ; Wed, 30 Nov 2005 10:10:58 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 0413BF7BB for ; Wed, 30 Nov 2005 10:10:57 -0700 (MST) Date: Wed, 30 Nov 2005 10:10:56 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051130101056.6cc8c47f.kgunders@teamcool.net> In-Reply-To: <3.0.1.32.20051130084540.00a57480@pop.redshift.com> References: <438D6926.8070807@axis.nl> <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> <438D6926.8070807@axis.nl> <3.0.1.32.20051130084540.00a57480@pop.redshift.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 17:11:02 -0000 On Wed, 30 Nov 2005 08:45:40 -0800 ray@redshift.com wrote: > At 08:43 AM 11/30/2005 -0800, Tom Cumming wrote: > | Did you try flashing the card? Your running old firmware, and you do have a > | driver/firmware mismatch. > > Tom has a very strong point here! :) This has been a long thread but I thought he'd reported that he'd flashed the firmware already?? -- Best regards, Ken Gunderson 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 Wed Nov 30 17:18:39 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2728916A41F for ; Wed, 30 Nov 2005 17:18:39 +0000 (GMT) (envelope-from ray@redshift.com) Received: from mail-smtp.redshift.com (mail-smtp.redshift.com [216.228.2.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFD2943D45 for ; Wed, 30 Nov 2005 17:18:38 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 2266 invoked by uid 89); 30 Nov 2005 17:18:39 -0000 Received: from unknown (HELO workstation) (216.228.19.21) by mail-smtp.redshift.com with SMTP; 30 Nov 2005 17:18:39 -0000 Message-Id: <3.0.1.32.20051130091830.00a51cf0@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Wed, 30 Nov 2005 09:18:30 -0800 To: Ken Gunderson ,freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <20051130101056.6cc8c47f.kgunders@teamcool.net> References: <3.0.1.32.20051130084540.00a57480@pop.redshift.com> <438D6926.8070807@axis.nl> <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> <438D6926.8070807@axis.nl> <3.0.1.32.20051130084540.00a57480@pop.redshift.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 17:18:39 -0000 At 10:10 AM 11/30/2005 -0700, Ken Gunderson wrote: | On Wed, 30 Nov 2005 08:45:40 -0800 | ray@redshift.com wrote: | | > At 08:43 AM 11/30/2005 -0800, Tom Cumming wrote: | > | Did you try flashing the card? Your running old firmware, and you do have a | > | driver/firmware mismatch. | > | > Tom has a very strong point here! :) | | This has been a long thread but I thought he'd reported that he'd flashed the | firmware already?? I'm not sure.. I think he has flash danced around the controller card signing "I hope this SOB works this time" - but I'm not sure about actually flashing the firmware... :) Olafo? Ray From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 17:25:33 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F30B16A423 for ; Wed, 30 Nov 2005 17:25:33 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from sdcexchange01.amcc.com (gatekeeper-out.amcc.com [198.137.200.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B0AE43D73 for ; Wed, 30 Nov 2005 17:25:25 +0000 (GMT) (envelope-from vkashyap@amcc.com) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Importance: normal Priority: normal Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 30 Nov 2005 09:25:19 -0800 Message-ID: <2B3B2AA816369A4E87D7BE63EC9D2F2601021D20@SDCEXCHANGE01.ad.amcc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: More about the 9500S-4 issues with the MoBo and FreeBSD... thread-index: AcX1i6XgPOJRKOpkRz6pImB6+0wHrQARw4pQ From: "Vinod Kashyap" To: "Olaf Greve" Cc: amd64@freebsd.org Subject: RE: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 17:25:33 -0000 > -----Original Message----- > From: Olaf Greve [mailto:o.greve@axis.nl]=20 > Sent: Wednesday, November 30, 2005 12:56 AM > To: Vinod Kashyap > Cc: Nathan Vidican; ray@redshift.com; amd64@freebsd.org > Subject: Re: More about the 9500S-4 issues with the MoBo and=20 > FreeBSD... >=20 > Hi, >=20 > > Are you sure you have the installation CD for amd64? The error=20 > > messages make me think you might be using an i386 version of the CD. >=20 > ???? > Well, I D/L-ed it from the French (I think) FreeBSD mirror from the > AMD64 directory... Having said that, I did notice the CDs=20 > bootstrap loader mentions freebsd/i386 (I meant to ask about=20 > that one). >=20 > If indeed I somehow was totally numb (a thing which I cannot=20 > entirely exclude given some of the following I'm about to=20 > type) and made such a stupid mistake myself, then that could=20 > certainly explain a lot.=20 > However.... that still wouldn't explain why FreeBSD=20 > 5.4-release AMD64 also chokes on it; and on that CD I am 100%=20 > positive it's the AMD64 version, as I have installed it on my=20 > own AMD64 machine from the very same CDs. Also, really, I am=20 > about 99% (if not 100%) sure that I made very certain to D/L=20 > the AMD64 version. The ISO images also reflected that name (I=20 > think), so it's not very likely it's the i386 version. >=20 I am sorry about the question, but the error messages looked like ones that could get printed if the driver was running in a 64-bit environment, but thought it was running in a 32-bit environment. Anyways, please know that you can always contact 3ware support for help. > Then: I'm amased. Really I am. >=20 > As the client needs this machine to be up an running this=20 > Friday, yesterday evening I decided to opt for a different=20 > strategy: install this machine using the on-board RAID=20 > controller, then in the meantime ask the client to order an=20 > Opteron (or dual Opteron) with a Tyan MoBo, install, tune and=20 > test that one at ease and then when it's all set-up swap that=20 > with the machine I'm currently working on. >=20 > So, just when I thought I had a workable strategy again, look=20 > at what horrors were bestowed upon me next: the Sil 3114=20 > on-board RAID controller recognises the drives, enters the=20 > BIOS, but when confirming the total RAID array size it=20 > totally hangs! And that's the controller's BIOS; it didn't=20 > even get to the point where one could install FreeBSD (or=20 > anything else for that matter). So, with "Plan B" out, there=20 > was even a "Plan C": use the nVidia on-board RAID controller.=20 > O.k., I plugged over the SATA controllers, configured the=20 > MoBo's BIOS to do this, and what do ya guess? Indeed, another=20 > full blown controller hang.=20 > Nice. :( >=20 > Well, over the past 15 years I must have installed dozens of=20 > machines (several of them including Asus boards, in=20 > combination with Adaptec SCSI RAID controllers and various=20 > different versions and flavours (i.e.=20 > 1386/amd64) of FreeBSD), with OS-es ranging from MS-DOS,=20 > through the full array of W*nd*wses, FreeBSDs, Linuxes, and I=20 > can hardly recall any more troublesome installation process=20 > than this time; really, it reminds me of the good 'ole MS-DOS=20 > days where one had to jumper each and every ISA board and=20 > then tweak memory configurations in order to get the lot=20 > going. :(((((( >=20 > Actually, I think something is simply b*ll*xed up on the=20 > board, but I just can't put my finger on what it is. Surele=20 > even if it is primarily a gaming board, still these type of=20 > errors should not have occurred. I spent the better part of=20 > late last evening and the wee hours on reading the MoBo's=20 > docs, and checking if we perhaps missed something. >=20 > I didn't spot anything, but something MUST be off... :(((( >=20 > Dunno. Time for a "plan D" I guess; I'll ask if the client=20 > can somehow get a working machine, and then I'll pull two=20 > more late nighters to at least get the bit I was supposed to=20 > do done: installing and tuning FreeBSD and MySQL. At present=20 > it's highly frustrating that I can't even really reach the OS=20 > installation part...:(((( >=20 > OK, guys thanks for hanging in there with me. I'm sure some=20 > day in the future I can laugh out loud at it too, just not=20 > right now....;) >=20 > Cheers! > Olafo > -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, = is for the sole use of the intended recipient(s) and contains = information that is confidential and proprietary to Applied Micro = Circuits Corporation or its subsidiaries. It is to be used solely for = the purpose of furthering the parties' business relationship. All = unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply = e-mail and destroy all copies of the original message. From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 18:58:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18AD616A420 for ; Wed, 30 Nov 2005 18:58:01 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86AB743D72 for ; Wed, 30 Nov 2005 18:57:47 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so69094nzo for ; Wed, 30 Nov 2005 10:57:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jI+k1JTwRLOGiWGbXpBtW3kPY7oUl7usqsyYeHNhHnhenmzeGcpDA5L7dWcTwObCzWFPbR/JlvbsIgB6UgkGDbnWGCP+YIiXfegTTk8CMoMOfhU+AsQ38frbx3MceHCYvaCVyCSyOh6/8mfqBedOAsL+jJ46gejiNLtAERuE/tI= Received: by 10.65.38.14 with SMTP id q14mr353067qbj; Wed, 30 Nov 2005 10:57:45 -0800 (PST) Received: by 10.64.196.13 with HTTP; Wed, 30 Nov 2005 10:57:45 -0800 (PST) Message-ID: <4bdd3edf0511301057w11c78fd7t@mail.gmail.com> Date: Wed, 30 Nov 2005 20:57:45 +0200 From: Popov Maxim To: freebsd-amd64@freebsd.org In-Reply-To: <20051130144823.GA22623@qlovarnika.bg.datamax> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4bdd3edf0511300019u1138a137g@mail.gmail.com> <20051130144823.GA22623@qlovarnika.bg.datamax> Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 30 Nov 2005 18:58:01 -0000 Then, there is no way to get a high resolution console on amd64 ? From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 01:28:46 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C7E216A41F; Thu, 1 Dec 2005 01:28:46 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A9E43D46; Thu, 1 Dec 2005 01:28:45 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 469F18A00D; Thu, 1 Dec 2005 12:28:31 +1100 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 2A1178A00A; Thu, 1 Dec 2005 12:28:31 +1100 (EST) Message-ID: <438E51CC.1090807@roq.com> Date: Thu, 01 Dec 2005 12:28:44 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Arno J. Klaassen" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: amd64@freebsd.org, java@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: quest for help on a linux emul problem (source unknown) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 01:28:46 -0000 Which linux port are you using? I have had beta versions of OpenOffice2 for linux lock up my FreeBSD amd64 desktop, but once I started using OO2 release for linux the lockups went away. I also started using the Suse port. /usr/ports/emulators/linux_base-suse-9.2/ OVERRIDE_LINUX_BASE_PORT=suse-9.2 in make.conf Arno J. Klaassen wrote: >Hello, > > >I try to get a commercial linux32 package to work on amd64; >this package includes it's own binary distrib of some >linux-jdk1.3.1 and works OK on i386 (RELENG_5 and RELENG_6) but >hangs on amd64-RELENG_6 (though it did work on a couple >of months old amd64-RELENG-5, but I do not any longer have such >a box around ... ). > >I write this email in the hope someone can put me on the right >track to nail down this problem : > >when I do a ktrace on i386 I get : > > CALL mincore(0xbfbfc480,0) > RET mincore 0 > CALL #175(0,0,0xbfbfc2b4,0x8) > RET #175 0 > CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) > RET #175 0 > CALL mincore(0xbfbfc290,0) > RET mincore 0 > CALL getdomainname(0xbfbfc288,0) > RET getdomainname 0 > >then some dozens of : > > CALL #175(0x2,0xbfbfc338,0,0x8) > RET #175 0 > CALL mincore(0xbfbfc480,0) > RET mincore 0 > CALL #175(0,0,0xbfbfc2b4,0x8) > RET #175 0 > CALL #175(0x1,0xbfbfc3b8,0xbfbfc338,0x8) > RET #175 0 > CALL mincore(0xbfbfc290,0) > RET mincore 0 > CALL getdomainname(0xbfbfc288,0) > RET getdomainname 0 > > >and finally : > > CALL #175(0x2,0xbfbfc338,0,0x8) > RET #175 0 > CALL write(0xb,0x83189e8,0x18) > GIO fd 11 wrote 24 bytes > > >On amd64-RELENG_6 it eternally loops in phase2 and never >reaches the 'finally'. > >Iff I understand correctly (far from sure!) and correct >for different syscall-numbers, I get : > >ask-for-initing-something { > gettimeofday() > sigprocmask(SIG_BLOCK,..) > sigprocmask(SIG_UNBLOCK,..) > gettimeofday() > nanosleep() >} > >while-not-OK { > sigprocmask(SIG_SETMASK,..) > gettimeofday() > sigprocmask(SIG_BLOCK,..) > sigprocmask(SIG_UNBLOCK,..) > gettimeofday() > nanosleep() >} > >OK! { > sigprocmask(SIG_SETMASK,..) > continue() >} > > >Since the program works OK in terminal mode, the problem >very probably is in the jdk-execution. I re-downloaded the >jdk13 sources and found that only at two places sigprocmask() is >called with SIG_UNBLOCK as argument, and one of them only >seems to serve the purpose of a work-around : > > * a workaround for the preemptive-close > * problem on Linux (bug #4344135); A thread currently waiting in > * a I/O operation will not wake up if one the file involved > * is actually closed (last close - the file is no longer accessible, > * but the thread is still waiting in the kernel). > >NB, this is a linux-jdk-1.3.0 problem, solved in linux-jdk-1.3.1, >so "an sich" not involved in my problem, but the idea of a thread >not waking up or signal not getting correctly delivered seems >plausible to my simple end-user mind. > >once again, if this kind of pseudo-code sounds familiar to someone, please >give me some hints which way to go to write a simple test-program >to pinpoint the problem. >Thank you very much for your time anyway. > >Regards, Arno > > > > From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 01:31:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0F9516A41F for ; Thu, 1 Dec 2005 01:31:50 +0000 (GMT) (envelope-from surija@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5159843D5A for ; Thu, 1 Dec 2005 01:31:50 +0000 (GMT) (envelope-from surija@gmail.com) Received: by zproxy.gmail.com with SMTP id z3so151367nzf for ; Wed, 30 Nov 2005 17:31:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=YRz5ftB3L7wjFFGY5z+rQ9XrSEgjBi83Ecl5owQranFz92qqYzfX4iMIUz/OvDBmcExBJ/mow6EUm2Jm6PwR+Xb/J4+77Ii22Ua5VdBtR/PLMupJKhzDzCO1gFhpk9NLTBM7nWablJYIvtF/p0M2sxEVRbRQ8nsNQTtAGfE2Ldk= Received: by 10.65.191.8 with SMTP id t8mr558445qbp; Wed, 30 Nov 2005 17:31:49 -0800 (PST) Received: by 10.64.213.20 with HTTP; Wed, 30 Nov 2005 17:31:49 -0800 (PST) Message-ID: <21bc91010511301731q32bd254avd5b9bacd32cb08e@mail.gmail.com> Date: Wed, 30 Nov 2005 20:31:49 -0500 From: Ranko Sredojevic To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: xorg configuration? or sshd? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 01:31:50 -0000 Hi, all! Has anyone seen these trying to start Cadence on remote host: *WARNING* file /home/rasha/CDS.log File is already locked by some other process. *ERROR* Failed to find either 24-bit TrueColor or 8-bit PseudoColor Visual. *WARNING* Failed to find either 24-bit TrueColor or 8-pbit PseudoColor Visual. If so, could you give some pointers what to do? One solution proposed on some RH list is changing the video card?!? My xorg.conf has only 24-bit entry and I have radeon 9250 and ATI(RADEON) drivers. I have been experiencing problems with Matlab GUI when running it on remote host (GUI was dead and it appeared as a huge window without right edge...) until I started using ssh -CY instead ssh -CX Could this one be ssh related or is it my xorg configuration? cheers, rasha From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 02:15:33 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6171616A41F for ; Thu, 1 Dec 2005 02:15:33 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7C1F43D45 for ; Thu, 1 Dec 2005 02:15:32 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by xproxy.gmail.com with SMTP id h31so152418wxd for ; Wed, 30 Nov 2005 18:15:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ciy/1CeejOpE6E1yPhB1Iy6m0Wj+FG68CYODocV4q0tj0OmxbxhJIFRDdRR+onPCR2tLzQCjnWVSm36jFVFhFkgsft7/FHz254TV9aHq2P4MdGySx4D2Wb7qKhnQbq6mgFzAob36YWgLfAWPtLsdCRk7d56rqJ1IVSLQs/qAxsE= Received: by 10.65.103.8 with SMTP id f8mr578350qbm; Wed, 30 Nov 2005 18:15:28 -0800 (PST) Received: by 10.65.112.13 with HTTP; Wed, 30 Nov 2005 18:15:28 -0800 (PST) Message-ID: <1d6d20bc0511301815q1029ad05k@mail.gmail.com> Date: Thu, 1 Dec 2005 10:15:28 +0800 From: Jia-Shiun Li To: Daniel Rock In-Reply-To: <438DD87C.9060906@deadcafe.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511272146.48247.dantavious@comcast.net> <1d6d20bc0511300748m1adedb31t@mail.gmail.com> <438DD87C.9060906@deadcafe.de> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD amd 64 and VMWARE issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 02:15:33 -0000 2005/12/1, Daniel Rock : > Jia-Shiun Li schrieb: > > Derrick, > > > > You must have > > 1.Windows x64 edition as host > You can run an 64 bit guest OS on a 32 bit Windows host. That's not what I realized: http://www.vmware.com/support/ws55/doc/releasenotes_ws55.html > > 2.VMWare Workstation 5.5 (from which begins to support amd64 guests) > > to install amd64 version as guest OS. > 3. You need an Athlon64/Opteron processor with at least D-Stepping. AFAIK= all > Socket 754 processors are stepping CG or lower. So I don't think you will= have > any luck even with the current VMWare release. > http://www.amdcompare.com/us-en/desktop/Default.aspx ya... I just found that not every x64 CPU will work. Only those Intel ones with VT (Pentium 4 6[67]2), and AMD ones of newer stepping (I dont know what is the real difference that matters) can run 64-bit guests. These CPUs are still rare. Jia-Shiun From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 05:11:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E071F16A420 for ; Thu, 1 Dec 2005 05:11:20 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7760943D5D for ; Thu, 1 Dec 2005 05:11:20 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id BC562F7C5 for ; Wed, 30 Nov 2005 22:11:19 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 83A81F7BB for ; Wed, 30 Nov 2005 22:11:19 -0700 (MST) Date: Wed, 30 Nov 2005 22:11:18 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051130221118.167f0624.kgunders@teamcool.net> In-Reply-To: <200509270225.CAA08104@sopwith.solgatos.com> References: <200509270225.CAA08104@sopwith.solgatos.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: dmesg from Tyan Tomcat K8E 2865 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 05:11:21 -0000 On Mon, 26 Sep 2005 19:25:01 +0100 Dieter wrote: > > > pci0: at device 4.0 (no driver attached) > > > > This is your sound card. No idea if any of the pcm(4) drivers support the > > sound on the nForce 4. > > > > > pci_link3: BIOS IRQ 10 does not match initial IRQ 5 > > > > Unless something is not working and you are getting an interrupt storm or some > > such, don't worry about this message. > > > > > pci1: at device 5.0 (no driver attached) > > > > If you use DRI, X will load a device driver that will attach here as drm0. > > Other than that, you don't need a device driver for this device for basic > > console video to work. > > > > > Suggestions on how to fix any of those would be welcome. > > > > None of these messages indicate any actual problems. Are you having any > > problems? > > No problems with the board yet other than Xorg refusing to do sync on green: > > (WW) ATI(0): Option "sync on green" is not used > > I haven't tried to use the onboard Ethernet or audio yet. I'm looking at one of these. Any updates now that you've had it for a while? Any outstanding issues? TIA-- -- Best regards, Ken Gunderson 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 Thu Dec 1 06:14:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2481E16A41F for ; Thu, 1 Dec 2005 06:14:57 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8874843D55 for ; Thu, 1 Dec 2005 06:14:56 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.11.6/8.11.6) with UUCP id jB16F4Y01047; Wed, 30 Nov 2005 22:15:04 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id GAA07204; Thu, 1 Dec 2005 06:12:02 GMT Message-Id: <200512010612.GAA07204@sopwith.solgatos.com> To: freebsd-amd64@freebsd.org Date: Wed, 30 Nov 2005 22:12:02 +0000 From: Dieter Cc: Subject: Re: dmesg from Tyan Tomcat K8E 2865 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 06:14:57 -0000 > I'm looking at one of these. Any updates now that you've had it for a > while? Any outstanding issues? I am still annoyed at ATI for not implementing sync-on-green in their video chips. Reading DV from the onboard firewire via fwcontrol -R seems to work okay, but sending DV to the onboard firewire via fwcontrol -S results in dropouts. Very repeatable. Sending DV to a NEC uPD72871/2 (PCI card) either works fine or not at all. So there is something not quite right in firewire land, but at this point I can't blame it on the Tyan's onboard controller. Ordered some cat6 patch cables earlier today, so I'll be able to try out the onboard Ethernets. (RJ45s and BNCs don't play well together.) From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 07:57:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24FE016A41F for ; Thu, 1 Dec 2005 07:57:37 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A4443D53 for ; Thu, 1 Dec 2005 07:57:36 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by xproxy.gmail.com with SMTP id h28so376906wxd for ; Wed, 30 Nov 2005 23:57:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K1EnikLUCyiVJzllzvMQkrTRxtlj0AO87X/g01VJFAP4bZbBdsOcC4F+m9nzJ/apWHgGQwvwevTvlrPCANMZuz4WRF5ni1a5AqnktGTVrcPge6kjcxsZUXUcZ/FXVG7svcS+1ptrHUdyaPW4FujDwrUJ/lC8tbV8W4YE4PXdT3s= Received: by 10.65.237.13 with SMTP id o13mr642035qbr; Wed, 30 Nov 2005 23:57:36 -0800 (PST) Received: by 10.65.112.13 with HTTP; Wed, 30 Nov 2005 23:57:35 -0800 (PST) Message-ID: <1d6d20bc0511302357g20e15afbn@mail.gmail.com> Date: Thu, 1 Dec 2005 15:57:35 +0800 From: Jia-Shiun Li To: Daniel Rock In-Reply-To: <1d6d20bc0511301815q1029ad05k@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511272146.48247.dantavious@comcast.net> <1d6d20bc0511300748m1adedb31t@mail.gmail.com> <438DD87C.9060906@deadcafe.de> <1d6d20bc0511301815q1029ad05k@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD amd 64 and VMWARE issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 07:57:37 -0000 2005/12/1, Jia-Shiun Li : > 2005/12/1, Daniel Rock : > > Jia-Shiun Li schrieb: > > > Derrick, > > > > > > You must have > > > 1.Windows x64 edition as host > > You can run an 64 bit guest OS on a 32 bit Windows host. > > That's not what I realized: > http://www.vmware.com/support/ws55/doc/releasenotes_ws55.html > Sorry I misunderstood it. According to http://www.vmware.com/support/ws55/doc/releasenotes_ws55.html#bb_64 --8<--- If your host machine has a 32-bit processor or a 64-bit processor that is not supported, Workstation does not support 64-bit guest operating systems. If your host machine has a supported 64-bit processor, you can run supported 32-bit and 64-bit operating systems in either the host or a guest, in any combination. -->8--- so it is possible to run 64-bit guest on 32-bit host OS, as long as the CPU is supported. Jia-Shiun From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 08:06:40 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6558816A41F for ; Thu, 1 Dec 2005 08:06:40 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E198743D5C for ; Thu, 1 Dec 2005 08:06:39 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 7939D8A00D; Thu, 1 Dec 2005 19:06:25 +1100 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 5E4498A00A; Thu, 1 Dec 2005 19:06:25 +1100 (EST) Message-ID: <438EAF0E.3000107@roq.com> Date: Thu, 01 Dec 2005 19:06:38 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Nilsson References: <438AA21E.2030702@gneto.com> In-Reply-To: <438AA21E.2030702@gneto.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: amd64@freebsd.org Subject: Re: My make buildworld FreeBSD 6.0R amd64 test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 08:06:40 -0000 I just did the test on a Dell 2850 AMD64 /usr/bin/time make -j 4 buildworld 1801.19 real 5224.01 user 927.94 sys Mike Martin Nilsson wrote: > Hi list, > > I made some simple comparing of CPU performance between intel and AMD > CPU:s on FreeBSD 6.0R The intent was to see how things like dualcore > and Hyperthreading affects a rather CPU bound real world job. > > The results can be seen here: > http://www.mullet.se/support/amd64-buildworld.html > > Please don't publish this anywhere else, I want to have your comments > and a chance to fix any errors before I get slashdotted and flamed to > hell :-) > > /Martin > _______________________________________________ > 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 Dec 1 08:40:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8481916A41F for ; Thu, 1 Dec 2005 08:40:56 +0000 (GMT) (envelope-from eike@unorganized.net) Received: from segfault.0xC0DE.de (0xc0de.de [81.169.134.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id D963C43D4C for ; Thu, 1 Dec 2005 08:40:55 +0000 (GMT) (envelope-from eike@unorganized.net) Received: from localhost (localhost [127.0.0.1]) by segfault.0xC0DE.de (Postfix) with ESMTP id D4D504502 for ; Thu, 1 Dec 2005 09:40:53 +0100 (CET) Received: from segfault.0xC0DE.de ([127.0.0.1]) by localhost (segfault.0xC0DE.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79974-04 for ; Thu, 1 Dec 2005 09:40:51 +0100 (CET) Received: from [192.168.100.104] (mobile.pmnet.uni-oldenburg.de [134.106.120.15]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by segfault.0xC0DE.de (Postfix) with ESMTP id C593544FC for ; Thu, 1 Dec 2005 09:40:51 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <200512010612.GAA07204@sopwith.solgatos.com> References: <200512010612.GAA07204@sopwith.solgatos.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1D01FE57-E475-4073-99B1-D5FE5E0557E6@unorganized.net> Content-Transfer-Encoding: 7bit From: Eike Bernhardt Date: Thu, 1 Dec 2005 09:40:44 +0100 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at 0xC0DE.de Subject: Re: dmesg from Tyan Tomcat K8E 2865 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 08:40:56 -0000 Am 30.11.2005 um 23:12 schrieb Dieter: >> I'm looking at one of these. Any updates now that you've had it >> for a >> while? Any outstanding issues? ... > Ordered some cat6 patch cables earlier today, so I'll be able to > try out > the onboard Ethernets. (RJ45s and BNCs don't play well together.) We just got a Tomcat K8E in a new server -- since it is a proxy, we don't use audio or firewire, so I can't say anything about them. The onboard bge network interface is working without problems, the onboard nve interface -- well, that interface has some problem, it is frequently running into timeouts and is becoming unusable. As Bjoern A. Zeeb posted some days ago, there is some bug hunting going on in -current, so that problem might go away soon -- but in the meantime we just disabled the nve interface, put in an old 3com card and thats working without problems. So if you need two network interfaces, be prepared to put in another nic until the problems with the nve interface are fixed. The onboard SATA Controller works out of the box -- we have four disks attached to it, no problems there. Bye, Eike -- Eike Bernhardt http://unorganized.net/ ICQ: 1125665 "Duct tape is like the force. It has a light side, and a dark side, and it holds the universe together." -- Carl Zwanzig From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 08:45:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E08516A41F for ; Thu, 1 Dec 2005 08:45:28 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A17343D55 for ; Thu, 1 Dec 2005 08:45:27 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1Ehk3z-0007Dx-00; Thu, 01 Dec 2005 09:45:11 +0100 Message-ID: <438EB80F.9070701@axis.nl> Date: Thu, 01 Dec 2005 09:45:03 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ray@redshift.com References: <3.0.1.32.20051130084540.00a57480@pop.redshift.com> <438D6926.8070807@axis.nl> <2B3B2AA816369A4E87D7BE63EC9D2F2601021B34@SDCEXCHANGE01.ad.amcc.com> <438D6926.8070807@axis.nl> <3.0.1.32.20051130084540.00a57480@pop.redshift.com> <3.0.1.32.20051130091830.00a51cf0@pop.redshift.com> In-Reply-To: <3.0.1.32.20051130091830.00a51cf0@pop.redshift.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: wayne@staff.msen.com, freebsd-amd64@freebsd.org Subject: Re: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 08:45:28 -0000 Hi again, > I'm not sure.. I think he has flash danced around the controller card signing "I > hope this SOB works this time" - but I'm not sure about actually flashing the > firmware... :) Olafo? Nope, that's about the only thing I hadn't done yet (due to the machine not having a floppy drive, and my own machine's CD writer being n*ckered). I wanted to get a floppy drive and/or make a CD and flash it yesterday evening, but the client decided to pick the machine up and in the meantime installed W*nd*ws on it. No comments please; I know this'll make all of you (and me too) want to request Ray's nailgun. ;) Interestingly enough, I must add, Windows didn't have any problems with it; or at least - NOT YET...;))) As sick as it may sound, I can actually understand their thinking somewhat: my time is very limited (I work a full-time job, and do the consultancy stuff in my evening and night hours, along with having a family), so given the fact that they need to have this machine up and running this Friday, you can do the math on just how precious little time there would have been left for me to install the lot on it (at, least, in a RAID set-up, that is), do the custom kernel compilation ceremonies, compile MySQL, and tune it (!!!). In stead, they have their own personnel who are on their normal payroll (and could spend all of the remainder of yesterday, and today on it) and who have installed W*nd*ws lots of times on their DB servers. Given those parameters, combined with their requirement to have the drives run in a RAID set-up, I can understand their logic somewhat. However... Not all is lost: they like the initially proposed back-up plan of giving this machine a temporary go, and then have me install a proper Opteron board in case the machine gets stressed heavily...:) I'll have them sort out a provider for it (Ray: I may come back to you off-list for that), and then in the future they can spend their money much better on the proper hardware, rather than on my time in order to tweak the sub-optimal hardware configurations... Also, today I'll ask them to Flash the 3ware card and see if FreeBSD boots from the CD to see if that does any magic... If it works, then at least they know that on their second identical config they ordered (but of which the CPU hasn't yet been ordered), FreeBSD would or wouldn't work (in case the Opteron stuff is beyond their budget)...:/ Oh well, live and learn; I guess they'll have learned their lesson regarding server hardware vs. other hardware, but still they need to have a DB server up and running, so for now they'll have to do with some interim solution, and then do it proper... Anyway: if anything new pops up I'll let you guys know, and if this is not the case, then I'd like to thank you guys already for hanging in there with me, and for all your help and suggestions. :) Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 10:12:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FF6916A41F for ; Thu, 1 Dec 2005 10:12:00 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 469A543D53 for ; Thu, 1 Dec 2005 10:11:59 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 1369BB830; Thu, 1 Dec 2005 12:11:58 +0200 (EET) Received: (nullmailer pid 15935 invoked by uid 1002); Thu, 01 Dec 2005 10:11:58 -0000 Date: Thu, 1 Dec 2005 12:11:58 +0200 From: Vasil Dimov To: Popov Maxim Message-ID: <20051201101158.GA15889@qlovarnika.bg.datamax> References: <4bdd3edf0511300019u1138a137g@mail.gmail.com> <20051130144823.GA22623@qlovarnika.bg.datamax> <4bdd3edf0511301057w11c78fd7t@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <4bdd3edf0511301057w11c78fd7t@mail.gmail.com> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 Cc: freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 10:12:00 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 30, 2005 at 08:57:45PM +0200, Popov Maxim wrote: > Then, there is no way to get a high resolution console on amd64 ? Depends on how do you understand the question. With the current version of FreeBSD the answer is "no way, sorry". Otherwise you can help implementing it :-) --=20 Vasil Dimov --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFDjsxtFw6SP/bBpCARAo5RAJ47PdBOxwWkl4NcrgmIq6ewQ5g5FwCgvmUN jz7PkmKzeic1P5e/N7Sh+Fo= =juoH -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 10:41:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32A1016A41F for ; Thu, 1 Dec 2005 10:41:50 +0000 (GMT) (envelope-from ukki@savot.org) Received: from netbox.wsoy.fi (netbox.wsoy.fi [193.208.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E05D43D49 for ; Thu, 1 Dec 2005 10:41:48 +0000 (GMT) (envelope-from ukki@savot.org) Received: from hki.wsoy.fi ([193.208.165.10]) by netbox.wsoy.fi with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Dec 2005 12:41:44 +0200 Received: from savo.wsoy.fi (savo.wsoy.fi [192.89.52.130]) by hki.wsoy.fi (8.12.8/8.12.5) with ESMTP id jB1AfhKK029647 for ; Thu, 1 Dec 2005 12:41:47 +0200 Received: from hataapukoppero.wsoy.fi ([192.89.52.134]) by savo.wsoy.fi (Lotus Domino Release 5.0.13a) with ESMTP id 2005120112514455:538 ; Thu, 1 Dec 2005 12:51:44 +0200 From: Janne =?iso-8859-15?q?M=E4kinen?= To: freebsd-amd64@freebsd.org Date: Thu, 1 Dec 2005 12:40:28 +0200 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Message-Id: <200512011240.29126.ukki@savot.org> X-MIMETrack: Itemize by SMTP Server on savo/WSOY/fi(Release 5.0.13a |April 8, 2004) at 01.12.2005 12:51:44, Serialize by Router on savo/WSOY/fi(Release 5.0.13a |April 8, 2004) at 01.12.2005 12:51:48, Serialize complete at 01.12.2005 12:51:48 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-15" Content-Disposition: inline X-OriginalArrivalTime: 01 Dec 2005 10:41:44.0744 (UTC) FILETIME=[D2B8AA80:01C5F663] Subject: FreeBSD 6 amd64 on HP Pavilion zv6000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 10:41:50 -0000 I wrote a small howto for people trying to install FreeBSD 6.0-amd64 on HP Pavilion zv6000 laptop. Could help others too. If there are errors or disinformation, please drop me a mail and I'll fix them. http://savot.org/ukki/freebsd/ From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 12:45:15 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F75616A41F for ; Thu, 1 Dec 2005 12:45:15 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from yggdrasil.interstroom.nl (yggdrasil.interstroom.nl [80.85.129.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 693F543D53 for ; Thu, 1 Dec 2005 12:45:14 +0000 (GMT) (envelope-from o.greve@axis.nl) Received: from ip127-180.introweb.nl ([80.65.127.180] helo=[192.168.1.42]) by yggdrasil with asmtp (Exim 3.35 #1 (Debian)) id 1EhnoB-0000Pj-00; Thu, 01 Dec 2005 13:45:07 +0100 Message-ID: <438EF04E.4000706@axis.nl> Date: Thu, 01 Dec 2005 13:45:02 +0100 From: Olaf Greve User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Palle Girgensohn References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> In-Reply-To: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Interstroom virusscan, please e-mail helpdesk@interstroom.nl for more information X-MailScanner-SpamCheck: Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 12:45:15 -0000 Hi, Normally if the i386 version boots from a CD-ROM drive, then so should the amd64 version (in the same drive). So, unless the burning of the CD-ROM somehow failed and/or the CD is damaged, it should really work. Nowwwww, having said that, I once made an extremely stupid mistake. In fact, it's so stupid that I was not going to tell it to anyone, but then, there is a remote possibility the same happened to you, sooo (*blush*): did you actually check if your burning program _interpreted_ the ISO file and burnt the _contents_ to disc (which would be correct), or whether it just burnt the ISO image _itself_ to disc (which would explain why the CD doesn't boot ;) )? I know from personal experience that one feels really stupid when this happens (I certainly did :P ), but at times when dragging an ISO image in a burning program the result is not as expected. In my case this occurred when I dragged an ISO image in K3B under CentOS Linux. I have to add that that day I was somewhat in a hurry and therefore didn't check properly before hitting the "burn" button, but that was what happened to me...:) Cheers! Olafo From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 16:18:59 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFA3916A41F for ; Thu, 1 Dec 2005 16:18:59 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id A86D843D72 for ; Thu, 1 Dec 2005 16:18:58 +0000 (GMT) (envelope-from girgen@FreeBSD.org) Received: from palle.girgensohn.se ([85.226.194.174] [85.226.194.174]) by mxfep01.bredband.com with ESMTP id <20051201161857.LJGA18713.mxfep01.bredband.com@palle.girgensohn.se>; Thu, 1 Dec 2005 17:18:57 +0100 Received: from palle.girgensohn.se (palle.girgensohn.se [127.0.0.1]) by palle.girgensohn.se (Postfix) with ESMTP id 6B4DF17BC3; Thu, 1 Dec 2005 17:18:58 +0100 (CET) Date: Thu, 01 Dec 2005 17:18:58 +0100 From: Palle Girgensohn To: Olaf Greve Message-ID: <856ED5EBF47DC7512CF58AD7@palle.girgensohn.se> In-Reply-To: <438EF04E.4000706@axis.nl> References: <8FF761CF16D72B2EB6D853AC@rambutan.pingpong.net> <438EF04E.4000706@axis.nl> 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 Cc: amd64@freebsd.org Subject: Re: 6.0 boot CD does not boot? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 01 Dec 2005 16:18:59 -0000 --On torsdag, december 01, 2005 13.45.02 +0100 Olaf Greve wrote: > Hi, > > Normally if the i386 version boots from a CD-ROM drive, then so should > the amd64 version (in the same drive). So, unless the burning of the > CD-ROM somehow failed and/or the CD is damaged, it should really work. It was in fact the CD that was broken, or actually two CDs. Maybe it was the burner, I'm having difficulties with that brand, it stops working sometimes, very odd. I borrowed a PowerBook and it went geschwinnt. > Nowwwww, having said that, I once made an extremely stupid mistake. In > fact, it's so stupid that I was not going to tell it to anyone, but then, > there is a remote possibility the same happened to you, sooo (*blush*): > did you actually check if your burning program _interpreted_ the ISO file > and burnt the _contents_ to disc (which would be correct), or whether it > just burnt the ISO image _itself_ to disc (which would explain why the CD > doesn't boot ;) )? This almost happened when my collegue was going to burn the CD om the Mac, but I pursuaded him to do it "the right way". Happens to everybody, I guess... :) Cheers, Palle From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 18:22:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2E6D16A41F for ; Thu, 1 Dec 2005 18:22:01 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32911.mail.mud.yahoo.com (web32911.mail.mud.yahoo.com [68.142.206.58]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DD9D43D46 for ; Thu, 1 Dec 2005 18:22:01 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 29632 invoked by uid 60001); 1 Dec 2005 18:22:00 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=FZXMtL63w7w/Zy/evzkf3sjC3I9phnZKTFLYnrYIn6nO4wk2kUz76LaJlzs/HK8B0DguWk0Q0Bc4AJ96pnxELYkrHEh/9yPP34w57VHj1yej48umhncRCK2U6mpjknxKFTPSIQH+1QZOkLV16qn+p5o5AUt7iCs/sGkEBAIUEpY= ; Message-ID: <20051201182200.29630.qmail@web32911.mail.mud.yahoo.com> Received: from [69.79.141.246] by web32911.mail.mud.yahoo.com via HTTP; Thu, 01 Dec 2005 19:22:00 CET Date: Thu, 1 Dec 2005 19:22:00 +0100 (CET) From: To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 18:22:02 -0000 > Then, there is no way to get a high resolution console on amd64 ? No promises but when my Pentium D arrives I'll work on porting KGI4BSD to the AMD64. http://people.freebsd.org/~nsouch/kgi4BSD/ It's completely untested and not ready for production but that said I don't see why it shouldn't work. ___________________________________ Yahoo! Messenger: chiamate gratuite in tutto il mondo http://it.messenger.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 1 21:32:12 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60A6E16A41F for ; Thu, 1 Dec 2005 21:32:12 +0000 (GMT) (envelope-from buebo@buebo.de) Received: from natfrord.rzone.de (natfrord.rzone.de [81.169.145.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5FA243D53 for ; Thu, 1 Dec 2005 21:32:11 +0000 (GMT) (envelope-from buebo@buebo.de) Received: from gwen.pulp-friction.local (reverse-82-141-57-114.dialin.kamp-dsl.de [82.141.57.114]) by post.webmailer.de (8.13.1/8.13.1) with SMTP id jB1LW6PW018355 for ; Thu, 1 Dec 2005 22:32:08 +0100 (MET) Date: Thu, 1 Dec 2005 22:32:00 +0100 From: "Felix 'buebo' Kakrow" To: amd64@freebsd.org Message-Id: <20051201223200.96bac2da.buebo@buebo.de> In-Reply-To: <1133267765.48495.8.camel@dracula> References: <1133267765.48495.8.camel@dracula> X-Mailer: Sylpheed version 2.1.8 (GTK+ 2.8.8; i386-portbld-freebsd6.0) X-JahLuv: Always, Brother! Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__1_Dec_2005_22_32_00_+0100_GPQJr8Niio/Pq1MZ" Cc: Subject: Re: Asus A8N-E X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: 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: Thu, 01 Dec 2005 21:32:12 -0000 --Signature=_Thu__1_Dec_2005_22_32_00_+0100_GPQJr8Niio/Pq1MZ Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am Tue, 29 Nov 2005 07:36:05 -0500 Dev Tugnait (Dev Tugnait ) schrieb in 1133267765.48495.8.camel@dracula: > I am planning on buying Athlon X2 4400 and was looking at the Asus > A8N-E mobo for it. I have checked > http://www.freebsd.org/platforms/amd64/motherboards.html the dmesg and > pr, seems like every things working in order. My main question is are > Athlon X2's supported?=20 Yes they are. I have exactly this motherboard with an athlon x2 3800+ running and everything but the Nvidia LAN works fine, including Sound and SATA. Cheers Felix --=20 This Message is digitally signed with GnuPG! Check out http://www.gnupg.org to learn more. Get my public key from http://www.buebo.de/pub_key.asc Fingerprint: B615 F83E D46F 8C56 AE8E AC25 8772 8994 FFB4 FCFB --Signature=_Thu__1_Dec_2005_22_32_00_+0100_GPQJr8Niio/Pq1MZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Enrcypt your mail with GnuPG! iD8DBQFDj2vWh3KJlP+0/PsRAhpCAKC7HJ5WwoaQKgEP9pu7Fm36pCnMBwCg0u6i Ls/mSLLiS+tbEbjMf3FeHEo= =cL/x -----END PGP SIGNATURE----- --Signature=_Thu__1_Dec_2005_22_32_00_+0100_GPQJr8Niio/Pq1MZ-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 00:28:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7622716A41F for ; Fri, 2 Dec 2005 00:28:34 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 210E743D45 for ; Fri, 2 Dec 2005 00:28:30 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id A94CDF7C5 for ; Thu, 1 Dec 2005 17:28:29 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 71A11F7BB for ; Thu, 1 Dec 2005 17:28:29 -0700 (MST) Date: Thu, 1 Dec 2005 17:28:28 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051201172828.5b25fdd4.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Tyan alternatives cuz their support totally sucks X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 00:28:34 -0000 Greetings List: I've been really quite happy w/the Tyan barebones systems I've deployed the past few months. Until I needed support on a DOA TA26 barebones unit. I'll spare you the gory details but the nightmare is ongoing. So regardless of how much I like the product it pretty much isn't worth jack in my book if support is piss poor when things go amiss. Which brings me to the task at hand. I need to deploy a front end webserver. Had a Tyan unit on order but, as my dear old granddaddy used to say; "Screw me once shame on you, screw me twice shame on me". So I'm looking for recommendations on Super Micro (reported to have good support- if you have experiences with them good/ bad then please share cuz I don't want to go down that rabbit hole again...) barebones units known to work well under FBSD-6.0? Requirements: 1) Single Opteron should suffice 2) DDR400 ECC supported 3) SATA disk subsystem will suffice 2 drive gmirror conf. 4 drive would be bonus. SATA-II (or 3.0 I guess they're calling it now) preferred. All this b.s. w/Tyan has chewed up far too much of my time so I need something that will "just work" and not require any hardware compatibility histrionics. TIA-- -- Best regards, Ken Gunderson 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 Fri Dec 2 05:00:15 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 EB0A216A41F for ; Fri, 2 Dec 2005 05:00:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86C7943D64 for ; Fri, 2 Dec 2005 05:00:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB250Dld051004 for ; Fri, 2 Dec 2005 05:00:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB250D3h051003; Fri, 2 Dec 2005 05:00:13 GMT (envelope-from gnats) Resent-Date: Fri, 2 Dec 2005 05:00:13 GMT Resent-Message-Id: <200512020500.jB250D3h051003@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, Tsurutani Naoki Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F66D16A41F for ; Fri, 2 Dec 2005 04:53:22 +0000 (GMT) (envelope-from turutani@scphys.kyoto-u.ac.jp) Received: from polymer3.scphys.kyoto-u.ac.jp (polymer3.scphys.kyoto-u.ac.jp [130.54.55.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 906DB43D5A for ; Fri, 2 Dec 2005 04:53:18 +0000 (GMT) (envelope-from turutani@scphys.kyoto-u.ac.jp) Received: from h116.65.226.10.32118.vlan.kuins.net (h116.65.226.10.32118.vlan.kuins.net [10.226.65.116]) by polymer3.scphys.kyoto-u.ac.jp (8.13.4/8.13.4/20050803-1) with ESMTP id jB24rEXk097628; Fri, 2 Dec 2005 13:53:14 +0900 (JST) (envelope-from turutani@scphys.kyoto-u.ac.jp) Received: from h116.65.226.10.32118.vlan.kuins.net (localhost [127.0.0.1]) by h116.65.226.10.32118.vlan.kuins.net (8.13.4/8.13.4) with ESMTP id jB24rEok001538; Fri, 2 Dec 2005 13:53:14 +0900 (JST) (envelope-from turutani@h116.65.226.10.32118.vlan.kuins.net) Received: (from root@localhost) by h116.65.226.10.32118.vlan.kuins.net (8.13.4/8.13.4/Submit) id jB24rE7O001537; Fri, 2 Dec 2005 13:53:14 +0900 (JST) (envelope-from turutani) Message-Id: <200512020453.jB24rE7O001537@h116.65.226.10.32118.vlan.kuins.net> Date: Fri, 2 Dec 2005 13:53:14 +0900 (JST) From: Tsurutani Naoki To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/89830: setkey causes system crash. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tsurutani Naoki List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 05:00:16 -0000 >Number: 89830 >Category: amd64 >Synopsis: setkey causes system crash. >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 02 05:00:13 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Tsurutani Naoki >Release: FreeBSD 5.4-STABLE amd64 >Organization: >Environment: System: FreeBSD h116.65.226.10.32118.vlan.kuins.net 5.4-STABLE FreeBSD 5.4-STABLE #2: Wed Nov 23 18:21:19 JST 2005 turutani@h116.65.226.10.32118.vlan.kuins.net:/usr/local/work/usr/obj/usr/src/sys/POLYMER13 amd64 >Description: running /usr/sbin/setkey causes system crash. this happens either on boot process or run it manually after boot. any messages can be collected. >How-To-Repeat: always running setkey on FreeBSD/amd64 5-STABLE. >Fix: i have no idea. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 06:20:07 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 A8F2616A41F for ; Fri, 2 Dec 2005 06:20:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D93443D4C for ; Fri, 2 Dec 2005 06:20:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB26K7gM065468 for ; Fri, 2 Dec 2005 06:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB26K65t065467; Fri, 2 Dec 2005 06:20:07 GMT (envelope-from gnats) Date: Fri, 2 Dec 2005 06:20:07 GMT Message-Id: <200512020620.jB26K65t065467@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Andrew P." Cc: Subject: Re: amd64/89830: setkey causes system crash. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Andrew P." List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 06:20:07 -0000 The following reply was made to PR amd64/89830; it has been noted by GNATS. From: "Andrew P." To: bug-followup@FreeBSD.org, Tsurutani Naoki Cc: Subject: Re: amd64/89830: setkey causes system crash. Date: Fri, 2 Dec 2005 09:15:36 +0300 This issue is discussed at: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Damd64/89261 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 06:37:50 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 970EE16A420; Fri, 2 Dec 2005 06:37:50 +0000 (GMT) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 472F243D46; Fri, 2 Dec 2005 06:37:50 +0000 (GMT) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (bz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB26boPX067022; Fri, 2 Dec 2005 06:37:50 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB26bnIO067018; Fri, 2 Dec 2005 06:37:49 GMT (envelope-from bz) Date: Fri, 2 Dec 2005 06:37:49 GMT From: "Bjoern A. Zeeb" Message-Id: <200512020637.jB26bnIO067018@freefall.freebsd.org> To: turutani@scphys.kyoto-u.ac.jp, bz@FreeBSD.org, freebsd-amd64@FreeBSD.org, bz@FreeBSD.org Cc: Subject: Re: amd64/89830: setkey causes system crash. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 06:37:50 -0000 Synopsis: setkey causes system crash. State-Changed-From-To: open->closed State-Changed-By: bz State-Changed-When: Fri Dec 2 06:36:19 GMT 2005 State-Changed-Why: Same report as in amd64/89261 but we have more information there. Please track amd64/89261. Responsible-Changed-From-To: freebsd-amd64->bz Responsible-Changed-By: bz Responsible-Changed-When: Fri Dec 2 06:36:19 GMT 2005 Responsible-Changed-Why: Assign it to me for possible followups. http://www.freebsd.org/cgi/query-pr.cgi?pr=89830 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 06:38:45 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 2DF7A16A41F; Fri, 2 Dec 2005 06:38:45 +0000 (GMT) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA22743D55; Fri, 2 Dec 2005 06:38:44 +0000 (GMT) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (bz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB26ciiF067069; Fri, 2 Dec 2005 06:38:44 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB26ciFp067065; Fri, 2 Dec 2005 06:38:44 GMT (envelope-from bz) Date: Fri, 2 Dec 2005 06:38:44 GMT From: "Bjoern A. Zeeb" Message-Id: <200512020638.jB26ciFp067065@freefall.freebsd.org> To: bz@FreeBSD.org, freebsd-amd64@FreeBSD.org, bz@FreeBSD.org Cc: Subject: Re: amd64/89261: IPSec always causes panics on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 06:38:45 -0000 Synopsis: IPSec always causes panics on amd64 Responsible-Changed-From-To: freebsd-amd64->bz Responsible-Changed-By: bz Responsible-Changed-When: Fri Dec 2 06:38:03 GMT 2005 Responsible-Changed-Why: I'll work on this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=89261 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 07:42:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC51516A41F for ; Fri, 2 Dec 2005 07:42:49 +0000 (GMT) (envelope-from ychsiao@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5655543D60 for ; Fri, 2 Dec 2005 07:42:48 +0000 (GMT) (envelope-from ychsiao@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so101982wxc for ; Thu, 01 Dec 2005 23:42:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=NWvj2/9Y6QAz3vmSB+vZVSroqNRzxumm6HZoeWPl6BNYy3nXsH1pLgm5xIM39oteArDTPF0eJhRnGz3mhHDOLgLb26rWxFjyOjOg3ZeVCQDPJwwLmZxGV+2LXue6qHoR3TNac9OjQcYyOKB7oM4zztDNDsZlmlrTd2zgpLl8s80= Received: by 10.70.108.6 with SMTP id g6mr3198786wxc; Thu, 01 Dec 2005 23:42:47 -0800 (PST) Received: by 10.70.110.1 with HTTP; Thu, 1 Dec 2005 23:42:47 -0800 (PST) Message-ID: <59e4fc130512012342m2404d33fr@mail.gmail.com> Date: Fri, 2 Dec 2005 15:42:47 +0800 From: Yuan-Chung Hsiao To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: FreeBSD 6 on AMD Dual-core Opteron - buildworld fail X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 07:42:49 -0000 Hi all: My server is HP DL385G4(AMD Opteron), when I buildworld(RELENG_6/RELENG_6_0), I get the error msg. Does anyone have this problem? FreeBSD Opteron.stu.edu.tw 6.0-RELEASE FreeBSD 6.0-RELEASE #1: Thu Dec 1 22:39:08 CST 2005 =20 root@amd.stu.edu.tw:/usr/obj/usr/src/sys/FreeBSD amd64 make.conf MACHINE=3Damd64 TARGET_ARCH=3Damd64 MACHINE_ARCH=3Damd64 WITH_LIB32=3Dyes CPUTYPE=3Dopteron #CFLAGS=3D -O -pipe #COPTFLAGS=3D -O -pipe FETCH_CMD=3Dfetch -d -A -p KERNCONF=3DFreeBSD SUP_UPDATE=3D yes SUP=3D /usr/local/bin/cvsup SUPFLAGS=3D -g -L 2 dmesg: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 250 (2405.46-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x20f51 Stepping =3D 1 Features=3D0x78bfbff Features2=3D0x1 AMD Features=3D0xe2500800,LM,3DNow+,3DNow> real memory =3D 4118773760 (3927 MB) avail memory =3D 3976265728 (3792 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 fail msg /usr/obj/usr/src/lib32/usr/include/ncurses.h -> curses.h /usr/obj/usr/src/lib32/usr/lib32/libcurses.a -> libncurses.a /usr/obj/usr/src/lib32/usr/lib32/libtermcap.a -> libncurses.a /usr/obj/usr/src/lib32/usr/lib32/libtermlib.a -> libncurses.a /usr/obj/usr/src/lib32/usr/lib32/libmytinfo.a -> libncurses.a /usr/obj/usr/src/lib32/usr/lib32/libtinfo.a -> libncurses.a /usr/obj/usr/src/lib32/usr/lib32/libcurses.so -> libncurses.so /usr/obj/usr/src/lib32/usr/lib32/libtermcap.so -> libncurses.so /usr/obj/usr/src/lib32/usr/lib32/libtermlib.so -> libncurses.so /usr/obj/usr/src/lib32/usr/lib32/libmytinfo.so -> libncurses.so /usr/obj/usr/src/lib32/usr/lib32/libtinfo.so -> libncurses.so /usr/obj/usr/src/lib32/usr/lib32/libcurses_p.a -> libncurses_p.a /usr/obj/usr/src/lib32/usr/lib32/libtermcap_p.a -> libncurses_p.a /usr/obj/usr/src/lib32/usr/lib32/libtermlib_p.a -> libncurses_p.a /usr/obj/usr/src/lib32/usr/lib32/libmytinfo_p.a -> libncurses_p.a /usr/obj/usr/src/lib32/usr/lib32/libtinfo_p.a -> libncurses_p.a =3D=3D=3D> lib/libnetgraph (depend,all,install) rm -f .depend CC=3D'cc -m32 -march=3Dathlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT=20 -I/usr/obj/usr/src/lib32/usr/include=20 -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/ src/lib32/usr/lib32' mkdep -f .depend -a =20 /usr/src/lib/libnetgraph/sock.c /usr/src/lib/libnetgraph/msg.c /usr/src/lib/libnetgraph/debug.c cc -m32 -march=3Dathlon-xp -msse2 -mfancy-math-387 -DCOMPAT_32BIT=20 -I/usr/obj/usr/src/lib32/usr/include=20 -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/ lib32/usr/lib32 -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototype s -Wpointer-arith -Wno-uninitialized -c /usr/src/lib/libnetgraph/sock.c In file included from /usr/obj/usr/src/lib32/usr/include/sys/types.h:44, from /usr/src/lib/libnetgraph/sock.c:44: /usr/obj/usr/src/lib32/usr/include/machine/endian.h: In function `__bswap64= ': /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: right shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: right shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: left shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: left shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: left shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: left shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/machine/endian.h:162: warning: left shift count >=3D width of type In file included from /usr/src/lib/libnetgraph/internal.h:45, from /usr/src/lib/libnetgraph/sock.c:50: /usr/obj/usr/src/lib32/usr/include/sys/time.h: In function `bintime2timespe= c': /usr/obj/usr/src/lib32/usr/include/sys/time.h:112: warning: right shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/sys/time.h:112: warning: right shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/sys/time.h: In function `bintime2timeval= ': /usr/obj/usr/src/lib32/usr/include/sys/time.h:129: warning: right shift count >=3D width of type /usr/obj/usr/src/lib32/usr/include/sys/time.h:129: warning: right shift count >=3D width of type *** Error code 1 Stop in /usr/src/lib/libnetgraph. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 -- Yuan-Chung Hsiao Computer Center,SHU-TE University Yanchao, Kaohsiung County, Taiwan 824 TEL:+886-7-6158000 Ext. 2438 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 09:08:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF7AD16A41F for ; Fri, 2 Dec 2005 09:08:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DB7C43D49 for ; Fri, 2 Dec 2005 09:08:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 531281A3C1A; Fri, 2 Dec 2005 01:08:51 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B19FE512D8; Fri, 2 Dec 2005 04:08:50 -0500 (EST) Date: Fri, 2 Dec 2005 04:08:50 -0500 From: Kris Kennaway To: Yuan-Chung Hsiao Message-ID: <20051202090850.GA18101@xor.obsecurity.org> References: <59e4fc130512012342m2404d33fr@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <59e4fc130512012342m2404d33fr@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 6 on AMD Dual-core Opteron - buildworld fail X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 09:08:52 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 02, 2005 at 03:42:47PM +0800, Yuan-Chung Hsiao wrote: > Hi all: > My server is HP DL385G4(AMD Opteron), when I > buildworld(RELENG_6/RELENG_6_0), I get the error msg. Does anyone have > this problem? >=20 > FreeBSD Opteron.stu.edu.tw 6.0-RELEASE FreeBSD 6.0-RELEASE #1: Thu Dec > 1 22:39:08 CST 2005 =20 > root@amd.stu.edu.tw:/usr/obj/usr/src/sys/FreeBSD amd64 >=20 > make.conf >=20 > MACHINE=3Damd64 > TARGET_ARCH=3Damd64 > MACHINE_ARCH=3Damd64 Don't set these, it was the cause of your problem. Why did you add these settings - is there bad documentation out there somewhere? Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDkA8iWry0BWjoQKURAusjAKDNmzoJ4+ih2MmPn/WT95eFd90UCACeKaky yMBZnqOheWM4uZqlc3Msrx0= =FOXQ -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 09:54:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B970916A41F for ; Fri, 2 Dec 2005 09:54:29 +0000 (GMT) (envelope-from ychsiao@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B0AD43D62 for ; Fri, 2 Dec 2005 09:54:29 +0000 (GMT) (envelope-from ychsiao@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so113492wxc for ; Fri, 02 Dec 2005 01:54:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p5OAIMN1k8nC5VCjNDwnVe2OD+CwxQjNQawjXLyuzfaQLWnTVXGNa3qALvorKvmNXPUxgAsbvpme+Qai3XQWYpEOBLraTgrZB8P0rEpnBXIjmuPROLE1iRkzyVeHr6kdzmO7DOibBiKhjNU3hOuyxeAQ0TZsPMpikT3vlgbKwpI= Received: by 10.70.109.19 with SMTP id h19mr3289393wxc; Fri, 02 Dec 2005 01:54:28 -0800 (PST) Received: by 10.70.110.1 with HTTP; Fri, 2 Dec 2005 01:54:28 -0800 (PST) Message-ID: <59e4fc130512020154k4aacbdcbx@mail.gmail.com> Date: Fri, 2 Dec 2005 17:54:28 +0800 From: Yuan-Chung Hsiao To: freebsd-amd64@freebsd.org In-Reply-To: <20051202090850.GA18101@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <59e4fc130512012342m2404d33fr@mail.gmail.com> <20051202090850.GA18101@xor.obsecurity.org> Subject: Re: FreeBSD 6 on AMD Dual-core Opteron - buildworld fail X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 09:54:29 -0000 2005/12/2, Kris Kennaway : > On Fri, Dec 02, 2005 at 03:42:47PM +0800, Yuan-Chung Hsiao wrote: > > Hi all: > > My server is HP DL385G4(AMD Opteron), when I > > buildworld(RELENG_6/RELENG_6_0), I get the error msg. Does anyone have > > this problem? > > > > FreeBSD Opteron.stu.edu.tw 6.0-RELEASE FreeBSD 6.0-RELEASE #1: Thu Dec > > 1 22:39:08 CST 2005 > > root@amd.stu.edu.tw:/usr/obj/usr/src/sys/FreeBSD amd64 > > > > make.conf > > > > MACHINE=3Damd64 > > TARGET_ARCH=3Damd64 > > MACHINE_ARCH=3Damd64 > > Don't set these, it was the cause of your problem. Why did you add > these settings - is there bad documentation out there somewhere? > > Kris > > > Hi all: These settings was my stupid idea when I see Makefile.inc1 source code. The other problem is my .cshrc have MACHINE=3Di386 variable, of course I remove it now. I try rebuildworld again, thanks. Regards, ychsiao -- Yuan-Chung Hsiao Computer Center,SHU-TE University Yanchao, Kaohsiung County, Taiwan 824 TEL:+886-7-6158000 Ext. 2438 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 13:13:51 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6759216A41F for ; Fri, 2 Dec 2005 13:13:51 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B7AD43D5A for ; Fri, 2 Dec 2005 13:13:50 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jB2DDkMU039898; Fri, 2 Dec 2005 08:13:49 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <4390488A.9060708@wmptl.com> Date: Fri, 02 Dec 2005 08:13:46 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20051201172828.5b25fdd4.kgunders@teamcool.net> In-Reply-To: <20051201172828.5b25fdd4.kgunders@teamcool.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: amd64@freebsd.org Subject: Re: Tyan alternatives cuz their support totally sucks X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 13:13:51 -0000 Ken Gunderson wrote: > Greetings List: > > I've been really quite happy w/the Tyan barebones systems I've deployed > the past few months. Until I needed support on a DOA TA26 barebones > unit. I'll spare you the gory details but the nightmare is ongoing. So > regardless of how much I like the product it pretty much isn't worth > jack in my book if support is piss poor when things go amiss. > > Which brings me to the task at hand. I need to deploy a front end > webserver. Had a Tyan unit on order but, as my dear old granddaddy > used to say; "Screw me once shame on you, screw me twice shame on me". > So I'm looking for recommendations on Super Micro (reported to have > good support- if you have experiences with them good/ bad then please > share cuz I don't want to go down that rabbit hole again...) barebones > units known to work well under FBSD-6.0? > > Requirements: > > 1) Single Opteron should suffice > 2) DDR400 ECC supported > 3) SATA disk subsystem will suffice 2 drive gmirror conf. 4 drive > would be bonus. SATA-II (or 3.0 I guess they're calling it now) > preferred. > > All this b.s. w/Tyan has chewed up far too much of my time so I need > something that will "just work" and not require any hardware > compatibility histrionics. > > TIA-- > I've always had good experiences with MSI boards/systems... generally well priced/featured and their support is pretty good. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 14:11:39 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A28E216A425 for ; Fri, 2 Dec 2005 14:11:39 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6906C43DF4 for ; Fri, 2 Dec 2005 14:11:08 +0000 (GMT) (envelope-from ohartman@mail.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 A3A22300167A; Fri, 2 Dec 2005 15:11:03 +0100 (CET) Message-ID: <439055CB.2030403@mail.uni-mainz.de> Date: Fri, 02 Dec 2005 15:10:19 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051130) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nathan Vidican References: <20051201172828.5b25fdd4.kgunders@teamcool.net> <4390488A.9060708@wmptl.com> In-Reply-To: <4390488A.9060708@wmptl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: amd64@freebsd.org Subject: Re: Tyan alternatives cuz their support totally sucks X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 14:11:39 -0000 >> Requirements: >> >> 1) Single Opteron should suffice >> 2) DDR400 ECC supported >> 3) SATA disk subsystem will suffice 2 drive gmirror conf. 4 drive >> would be bonus. SATA-II (or 3.0 I guess they're calling it now) >> preferred. As far as I know, SATA-II is NOT SATA 3.0. SATA-II is still SATA 1.0a and defines doubling of tranfer rate. >> >> All this b.s. w/Tyan has chewed up far too much of my time so I need >> something that will "just work" and not require any hardware >> compatibility histrionics. > > I've always had good experiences with MSI boards/systems... generally > well priced/featured and their support is pretty good. > TYAN is said to be a good choice in building server related systems, while MSI is more aimed for the home and office market (I may be wrong). Oliver From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 16:13:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AC9616A41F for ; Fri, 2 Dec 2005 16:13:51 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D4A443DA6 for ; Fri, 2 Dec 2005 16:13:21 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so94774wri for ; Fri, 02 Dec 2005 08:13:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=ZQjYpxopJM6Msj342XIjrx4i0rUcrOwjvgun6vr2xPlEvucqEif4SnwqURgTMZ3DKsRqE70Q9cRRsVNYc5L3KP85oCoSVK+ToShJEIHkEi+kVDTbAKqRiu1myz9FvOtgDd6H/nvVGiW4sNcSUzPmexqxVwqY4iWn0uY9dkXmPiU= Received: by 10.65.189.16 with SMTP id r16mr1556527qbp; Fri, 02 Dec 2005 08:13:18 -0800 (PST) Received: by 10.64.196.13 with HTTP; Fri, 2 Dec 2005 08:13:18 -0800 (PST) Message-ID: <4bdd3edf0512020813u3db7498bl@mail.gmail.com> Date: Fri, 2 Dec 2005 18:13:18 +0200 From: Popov Maxim To: pfgshield-freebsd@yahoo.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 16:13:51 -0000 >No promises but when my Pentium D arrives I'll work on porting KGI4BSD to = the >AMD64. > http://people.freebsd.org/~nsouch/kgi4BSD/ > >It's completely untested and not ready for production but that said I don'= t see >why it shouldn't work. OK, we'll be waiting for that ... From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 16:23:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B6C016A41F for ; Fri, 2 Dec 2005 16:23:40 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32903.mail.mud.yahoo.com (web32903.mail.mud.yahoo.com [68.142.206.50]) by mx1.FreeBSD.org (Postfix) with SMTP id 73F8343D58 for ; Fri, 2 Dec 2005 16:23:39 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 71508 invoked by uid 60001); 2 Dec 2005 16:23:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Lb632pcBnLtAQXi6YJX6pq/XM4CyoaAiR3rQx7s6852QAq/fLo7wNoNWgt3K0iB7eBSIisw+3Fj722rSfUJRo0uc4jV0gpaCy16nuT1AWPdD2iwHy6nDwqPp1bWPZKTV0SAAo4JgyaiN8AIpZSreEfwlcLGiAk/4jjXQIztlD4g= ; Message-ID: <20051202162339.71506.qmail@web32903.mail.mud.yahoo.com> Received: from [69.79.141.246] by web32903.mail.mud.yahoo.com via HTTP; Fri, 02 Dec 2005 17:23:38 CET Date: Fri, 2 Dec 2005 17:23:38 +0100 (CET) From: To: Popov Maxim In-Reply-To: <4bdd3edf0512020813u3db7498bl@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 16:23:40 -0000 --- Popov Maxim ha scritto: ... > > OK, we'll be waiting for that ... > Don't wait too much though.. it only works for matrox cards (Radeon support is there too but the port is not finished). Pedro. ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 17:45:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C624616A41F for ; Fri, 2 Dec 2005 17:45:40 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ECEF43D69 for ; Fri, 2 Dec 2005 17:45:37 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: by wproxy.gmail.com with SMTP id i34so138572wra for ; Fri, 02 Dec 2005 09:45:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Op+1g3x3E/Tl3sxv9Kv3fR80u5vOV5Cd0oinYr+VkmRY3L5fk8+i096rn43kGekBgaumfzhCb95krLFaavnx7/3A1MCdsvz/HB1F8IJCPBrV/w/9We5i850r7lBZSThFtpiIRiPmZ4++TpmIR0GQiEpHn3dSmzy/vuImky4pkb0= Received: by 10.65.213.10 with SMTP id p10mr1647001qbq; Fri, 02 Dec 2005 09:45:36 -0800 (PST) Received: by 10.64.196.13 with HTTP; Fri, 2 Dec 2005 09:45:36 -0800 (PST) Message-ID: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> Date: Fri, 2 Dec 2005 19:45:36 +0200 From: Popov Maxim To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Installing Opera ... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 17:45:40 -0000 Hi, i can't install opera .... i did that: (messages given by the system may be different, i'm not under FreeBSD at the moment) cd /usr/ports/www/opera/ make it throws an error and says: this package is not supported on your platform (amd64 ofcourse). Ok, then, i commented the ARCH=3Di386 option in the Makefile and it throws an error again. In my kernel configuration there is enabled the i386 compatibity option (don't remember how it is named exactly). How to install opera ? From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 18:57:46 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DB4916A41F for ; Fri, 2 Dec 2005 18:57:46 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C42F43D5A for ; Fri, 2 Dec 2005 18:57:45 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jB2IviF2051937; Fri, 2 Dec 2005 13:57:44 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <43909927.8070108@wmptl.com> Date: Fri, 02 Dec 2005 13:57:43 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" , amd64@freebsd.org References: <20051201172828.5b25fdd4.kgunders@teamcool.net> <4390488A.9060708@wmptl.com> <439055CB.2030403@mail.uni-mainz.de> In-Reply-To: <439055CB.2030403@mail.uni-mainz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: Subject: Re: Tyan alternatives cuz their support totally sucks X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 18:57:46 -0000 O. Hartmann wrote: >>> Requirements: >>> >>> 1) Single Opteron should suffice >>> 2) DDR400 ECC supported >>> 3) SATA disk subsystem will suffice 2 drive gmirror conf. 4 drive >>> would be bonus. SATA-II (or 3.0 I guess they're calling it now) >>> preferred. > > > As far as I know, SATA-II is NOT SATA 3.0. SATA-II is still SATA 1.0a > and defines doubling of tranfer rate. > >>> >>> All this b.s. w/Tyan has chewed up far too much of my time so I need >>> something that will "just work" and not require any hardware >>> compatibility histrionics. >> >> >> I've always had good experiences with MSI boards/systems... generally >> well priced/featured and their support is pretty good. >> > > TYAN is said to be a good choice in building server related systems, > while MSI is more aimed for the home and office market (I may be wrong). > > Oliver > > > > MSI has a server line as well, including 1U bare-bones, motherboards, etc... I have 4 dual AMD Opteron boxes here based on MSI K8Master's ... GREAT board, though must warn they are a bit pricey at ~ $500 - $600 / each, I have them configured with dual 246 cpu's and 4gb ecc registered memory each (coincidentally with 3ware raid cards we've had so many posts in here about lately). Knock-on-wood, not a single day/moment's downtime yet attributable to the hardware in these things. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 19:44:53 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B41B16A41F for ; Fri, 2 Dec 2005 19:44:53 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EC643D49 for ; Fri, 2 Dec 2005 19:44:50 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 93764F821 for ; Fri, 2 Dec 2005 12:44:50 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 5D8A8F820 for ; Fri, 2 Dec 2005 12:44:50 -0700 (MST) Date: Fri, 2 Dec 2005 12:44:49 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051202124449.11806cbb.kgunders@teamcool.net> In-Reply-To: <43909927.8070108@wmptl.com> References: <20051201172828.5b25fdd4.kgunders@teamcool.net> <4390488A.9060708@wmptl.com> <439055CB.2030403@mail.uni-mainz.de> <43909927.8070108@wmptl.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Tyan alternatives cuz their support totally sucks X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 19:44:53 -0000 On Fri, 02 Dec 2005 13:57:43 -0500 Nathan Vidican wrote: > O. Hartmann wrote: > >>> Requirements: [snip] > > MSI has a server line as well, including 1U bare-bones, motherboards, etc... I > have 4 dual AMD Opteron boxes here based on MSI K8Master's ... GREAT board, > though must warn they are a bit pricey at ~ $500 - $600 / each, I have them > configured with dual 246 cpu's and 4gb ecc registered memory each > (coincidentally with 3ware raid cards we've had so many posts in here about lately). Yes, the Tyan units are great themselves. The issue is getting support when you need it. Any feedback about MSI in this regard? > Knock-on-wood, not a single day/moment's downtime yet attributable to the > hardware in these things. Thanks for the tip- worth investigating. I'm off to their website now... -- Best regards, Ken Gunderson 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 Fri Dec 2 20:15:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E57AD16A41F for ; Fri, 2 Dec 2005 20:15:04 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55EFC43D5E for ; Fri, 2 Dec 2005 20:14:52 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.11.6/8.11.6) with UUCP id jB2KF1G20069 for freebsd-amd64@freebsd.org; Fri, 2 Dec 2005 12:15:01 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id UAA26435; Fri, 2 Dec 2005 20:10:08 GMT Message-Id: <200512022010.UAA26435@sopwith.solgatos.com> To: freebsd-amd64@freebsd.org Date: Fri, 02 Dec 2005 12:10:08 +0000 From: Dieter Subject: SATA-foo (was: Tyan alternatives cuz their support totally sucks) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 20:15:05 -0000 > As far as I know, SATA-II is NOT SATA 3.0. SATA-II is still SATA 1.0a > and defines doubling of tranfer rate. http://www.sata-io.org/namingguidelines.asp Does FreeBSD support NCQ? Port multipliers? From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 20:21:12 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5D5E16A41F for ; Fri, 2 Dec 2005 20:21:12 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (c-67-168-241-176.hsd1.or.comcast.net [67.168.241.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84F6843D46 for ; Fri, 2 Dec 2005 20:21:12 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.11.6/8.11.6) with UUCP id jB2KLNf20124 for freebsd-amd64@freebsd.org; Fri, 2 Dec 2005 12:21:23 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id UAA20705; Fri, 2 Dec 2005 20:21:15 GMT Message-Id: <200512022021.UAA20705@sopwith.solgatos.com> To: freebsd-amd64@freebsd.org Date: Fri, 02 Dec 2005 12:21:15 +0000 From: Dieter Subject: How to get support (was: Tyan alternatives cuz their support totally sucks) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 20:21:13 -0000 > I've been really quite happy w/the Tyan barebones systems I've deployed > the past few months. Until I needed support on a DOA TA26 barebones > unit. I'll spare you the gory details but the nightmare is ongoing. But... we enjoy reading the gory details... > I need something that will "just work" and not require any hardware compatibility > histrionics. ...and someone might know the answer. > Yes, the Tyan units are great themselves. > The issue is getting support when you need it. Have your VP visit one of Tyan's VPs and wave a million dollar PO in their face. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 20:30:12 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6A5616A41F for ; Fri, 2 Dec 2005 20:30:12 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8FCE43D60 for ; Fri, 2 Dec 2005 20:30:11 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 2E209F821 for ; Fri, 2 Dec 2005 13:30:11 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id EBCDBF820 for ; Fri, 2 Dec 2005 13:30:10 -0700 (MST) Date: Fri, 2 Dec 2005 13:30:10 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051202133010.21549f90.kgunders@teamcool.net> In-Reply-To: <200512022021.UAA20705@sopwith.solgatos.com> References: <200512022021.UAA20705@sopwith.solgatos.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: How to get support (was: Tyan alternatives cuz their support totally sucks) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 20:30:13 -0000 On Fri, 02 Dec 2005 12:21:15 +0000 Dieter wrote: > > I've been really quite happy w/the Tyan barebones systems I've deployed > > the past few months. Until I needed support on a DOA TA26 barebones > > unit. I'll spare you the gory details but the nightmare is ongoing. > > But... we enjoy reading the gory details... Ugh!! It's quite the saga and don't think I should clutter up the list w/it. Suffice to say it wasn't pretty and gives me serious concern over any future dealings with them. > > I need something that will "just work" and not require any hardware compatibility > > histrionics. > > ...and someone might know the answer. > > > Yes, the Tyan units are great themselves. > > The issue is getting support when you need it. > > Have your VP visit one of Tyan's VPs and wave a million dollar PO in > their face. Unfortunately that's about the reality of it... I will say in Tyan's defense that things improved significantly once I gave up on support and started working my way up the sales management ladder. Keeping future sales seems to motivate them enough to get things done. -- Best regards, Ken Gunderson 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 Fri Dec 2 20:49:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8982E16A41F for ; Fri, 2 Dec 2005 20:49:26 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE9B43D73 for ; Fri, 2 Dec 2005 20:49:24 +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 jB2KnNo2030570; Fri, 2 Dec 2005 12:49:23 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jB2KnNlu030569; Fri, 2 Dec 2005 12:49:23 -0800 Date: Fri, 2 Dec 2005 12:49:23 -0800 From: Brooks Davis To: Ken Gunderson Message-ID: <20051202204923.GD20567@odin.ac.hmc.edu> References: <200512022021.UAA20705@sopwith.solgatos.com> <20051202133010.21549f90.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline In-Reply-To: <20051202133010.21549f90.kgunders@teamcool.net> 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: How to get support (was: Tyan alternatives cuz their support totally sucks) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 20:49:26 -0000 --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 02, 2005 at 01:30:10PM -0700, Ken Gunderson wrote: > On Fri, 02 Dec 2005 12:21:15 +0000 > Dieter wrote: >=20 > > > I've been really quite happy w/the Tyan barebones systems I've deploy= ed > > > the past few months. Until I needed support on a DOA TA26 barebones > > > unit. I'll spare you the gory details but the nightmare is ongoing. > >=20 > > But... we enjoy reading the gory details... >=20 > Ugh!! It's quite the saga and don't think I should clutter up the list > w/it. Suffice to say it wasn't pretty and gives me serious concern > over any future dealings with them. > =20 > > > I need something that will "just work" and not require any hardware c= ompatibility > > > histrionics. > >=20 > > ...and someone might know the answer. > >=20 > > > Yes, the Tyan units are great themselves. > > > The issue is getting support when you need it. > >=20 > > Have your VP visit one of Tyan's VPs and wave a million dollar PO in > > their face. >=20 > Unfortunately that's about the reality of it... =20 >=20 > I will say in Tyan's defense that things improved significantly once I > gave up on support and started working my way up the sales management > ladder. Keeping future sales seems to motivate them enough to get > things done. I think this is one of those cases when it's much better do deal with them through a good reseller. The reseller has much better leverage then most customers since they buy a lot more boards. You still have to make the reseller care, but I'm had pretty good luck with that myself (of course, I often buy half a rack or more machines at a time which tends to hold their attention. :) -- 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 --JWEK1jqKZ6MHAcjA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDkLNRXY6L6fI4GtQRAmFwAJ9PGTfFR1G34BawX4+U0xsmKGZbDQCfUruU NfUHJ+VKl04u5pYEEV9IY88= =7WKs -----END PGP SIGNATURE----- --JWEK1jqKZ6MHAcjA-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 21:07:34 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3247C16A41F; Fri, 2 Dec 2005 21:07:34 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E85C343D62; Fri, 2 Dec 2005 21:07:03 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB2L6uUB015844; Fri, 2 Dec 2005 16:06:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jB2L6vK2024767; Fri, 2 Dec 2005 16:06:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 47EAC7302F; Fri, 2 Dec 2005 16:06:57 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051202210657.47EAC7302F@freebsd-current.sentex.ca> Date: Fri, 2 Dec 2005 16:06:57 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 21:07:34 -0000 TB --- 2005-12-02 19:28:24 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-02 19:28:24 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-02 19:28:24 - cleaning the object tree TB --- 2005-12-02 19:29:02 - checking out the source tree TB --- 2005-12-02 19:29:02 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-02 19:29:02 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-02 19:35:12 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-02 19:35:12 - cd /src TB --- 2005-12-02 19:35:12 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-12-02 21:06:56 - generating LINT kernel config TB --- 2005-12-02 21:06:56 - cd /src/sys/amd64/conf TB --- 2005-12-02 21:06:56 - /usr/bin/make -B LINT TB --- 2005-12-02 21:06:56 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-02 21:06:56 - cd /src TB --- 2005-12-02 21:06:56 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 2 21:06:56 UTC 2005 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/amd64/conf; PATH=/obj/amd64/src/tmp/legacy/usr/sbin:/obj/amd64/src/tmp/legacy/usr/bin:/obj/amd64/src/tmp/legacy/usr/games:/obj/amd64/src/tmp/usr/sbin:/obj/amd64/src/tmp/usr/bin:/obj/amd64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/amd64/src/sys/LINT /src/sys/amd64/conf/LINT /src/sys/amd64/conf/LINT: unknown option "P1003_1B_MQUEUE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-02 21:06:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-02 21:06:57 - ERROR: failed to build lint kernel TB --- 2005-12-02 21:06:57 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 21:16:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA6B216A420 for ; Fri, 2 Dec 2005 21:16:38 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8DF343D81 for ; Fri, 2 Dec 2005 21:16:34 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 0DA9EF821 for ; Fri, 2 Dec 2005 14:16:34 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id DF4FAF820 for ; Fri, 2 Dec 2005 14:16:33 -0700 (MST) Date: Fri, 2 Dec 2005 14:16:32 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20051202141632.707fdb1a.kgunders@teamcool.net> In-Reply-To: <20051202204923.GD20567@odin.ac.hmc.edu> References: <200512022021.UAA20705@sopwith.solgatos.com> <20051202133010.21549f90.kgunders@teamcool.net> <20051202204923.GD20567@odin.ac.hmc.edu> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: How to get support (was: Tyan alternatives cuz their support totally sucks) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 21:16:39 -0000 On Fri, 2 Dec 2005 12:49:23 -0800 Brooks Davis wrote: > On Fri, Dec 02, 2005 at 01:30:10PM -0700, Ken Gunderson wrote: > > On Fri, 02 Dec 2005 12:21:15 +0000 > > Dieter wrote: > > > > > > I've been really quite happy w/the Tyan barebones systems I've deployed [snip] > I think this is one of those cases when it's much better do deal with > them through a good reseller. The reseller has much better leverage > then most customers since they buy a lot more boards. You still have to > make the reseller care, but I'm had pretty good luck with that myself > (of course, I often buy half a rack or more machines at a time which > tends to hold their attention. :) Thankfully I was. But it still boiled down to terrible support on Tyan's end until we got sales management involved. Strangely enough Tyan's support pages boast having Annadtech's best of the best. I've dealt with them on 3 different issues over the months; 2 minor and one major. No response from Tyan on the 1st two but they were minor enough that I just let them slide. Now that these problems have been brought to the attention of a couple sales managers hopefully they will be channeled up the appropriate ladders and Tyan will take steps to rectify. In the end (as of about 1 hour ago), I got enough satisfaction that, while the saga was extremely frustrating and ate up tons of my time (over two weeks of doing battle to get a DOA replacement for a machine that was outside of their 30 day window due to the CPU's being back ordered), I'm willing to give them another chance. -- Best regards, Ken Gunderson 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 Fri Dec 2 21:23:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26D2B16A41F for ; Fri, 2 Dec 2005 21:23:14 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E30643D58 for ; Fri, 2 Dec 2005 21:23:13 +0000 (GMT) (envelope-from popov.max@gmail.com) Received: by wproxy.gmail.com with SMTP id i28so196476wra for ; Fri, 02 Dec 2005 13:23:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kj2ClSPDWI1SGTTYSDFXRcCCxBOqWVnbGFD8agMTfSlsyDsA8ffMj87xGn0k6UH1hTUTZSm3j1Wbd9mbRCA8Ly4pm/5nzKT4JvuhNsROX29lwTKt3qliy3J/GJZCMTHX8adR4o45pVcZURemFjXiOb67Jbah/GwlSuNECwZhMEY= Received: by 10.64.150.8 with SMTP id x8mr1812783qbd; Fri, 02 Dec 2005 13:23:06 -0800 (PST) Received: by 10.64.196.13 with HTTP; Fri, 2 Dec 2005 13:23:06 -0800 (PST) Message-ID: <4bdd3edf0512021323u32184030u@mail.gmail.com> Date: Fri, 2 Dec 2005 23:23:06 +0200 From: Popov Maxim To: =?ISO-8859-1?Q?Janne_M=E4kinen?= In-Reply-To: <200512022033.55762.janne.makinen@savot.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> <200512022033.55762.janne.makinen@savot.org> Cc: freebsd-amd64@freebsd.org Subject: Re: Installing Opera ... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 21:23:14 -0000 Please, i'll be happy if you'll send that to me .... 2005/12/2, Janne M=E4kinen : > On Friday 02 December 2005 19:45, Popov Maxim wrote: > > Hi, i can't install opera .... i did that: > > > > (messages given by the system may be different, i'm not under FreeBSD > > at the moment) > > > > cd /usr/ports/www/opera/ > > make > > > > it throws an error and says: > > > > this package is not supported on your platform (amd64 ofcourse). > > > > Ok, then, i commented the ARCH=3Di386 option in the Makefile and it > > throws an error again. > > > > In my kernel configuration there is enabled the i386 compatibity > > option (don't remember how it is named exactly). > > > > How to install opera ? > > Not sure you can install Opera, because it requires compat4 and FreeBSD 4 > didn't work on amd64. Linux version of Opera works, if you have linux sup= port > and you'll get Flash etc. working "natively". It takes some editing, but= I > just installed it and it works fine. I can give you the details on how to > install the linux-version if you want. > From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 21:27:41 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1708416A41F for ; Fri, 2 Dec 2005 21:27:41 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D9F743D55 for ; Fri, 2 Dec 2005 21:27:40 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IQW00JH43T1JZA0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 02 Dec 2005 22:31:49 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IQW002SW3QQST10@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Fri, 02 Dec 2005 22:30:26 +0100 (CET) Date: Fri, 02 Dec 2005 22:27:38 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> To: freebsd-amd64@freebsd.org Message-id: <20051202222738.1b741e1a.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> Subject: Re: Installing Opera ... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 21:27:41 -0000 On Fri, 02 Dec 2005 19:45:36 +0200 Popov Maxim wrote: > Ok, then, i commented the ARCH=i386 option in the Makefile and it > throws an error again. Like this? ===> opera-8.51.20051114 depends on shared library: c_r.4 - not found ===> Verifying install for c_r.4 in /usr/ports/misc/compat4x ===> compat4x-amd64-5.3_2 in unsupported (FreeBSD 4.x did not run on this architecture). Opera requires the compat4x port (because it is compiled for FreeBSD 4.6, I think), but the compat4x port isn't supprted on the amd64 platform. Like the message tells you. > How to install opera ? I guess you can't. Or, you can ask the Opera people (again and again and...) to provide an updated Opera for current versions of FreeBSD. Yes, on all supported platforms please. --- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 21:38:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71FA916A41F for ; Fri, 2 Dec 2005 21:38:30 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A47243D5A for ; Fri, 2 Dec 2005 21:38:29 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (unknown [70.152.101.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id A2110AD for ; Fri, 2 Dec 2005 15:38:26 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 97A0F61C27; Fri, 2 Dec 2005 15:38:23 -0600 (CST) Date: Fri, 2 Dec 2005 15:38:23 -0600 From: "Matthew D. Fuller" To: Torfinn Ingolfsen Message-ID: <20051202213823.GC39831@over-yonder.net> References: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> <20051202222738.1b741e1a.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051202222738.1b741e1a.torfinn.ingolfsen@broadpark.no> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: freebsd-amd64@freebsd.org Subject: Re: Installing Opera ... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Dec 2005 21:38:30 -0000 On Fri, Dec 02, 2005 at 10:27:38PM +0100 I heard the voice of Torfinn Ingolfsen, and lo! it spake thus: > > Like this? > ===> opera-8.51.20051114 depends on shared library: c_r.4 - not found > ===> Verifying install for c_r.4 in /usr/ports/misc/compat4x > ===> compat4x-amd64-5.3_2 in unsupported (FreeBSD 4.x did not run on > this architecture). > > Opera requires the compat4x port (because it is compiled for FreeBSD > 4.6, I think), but the compat4x port isn't supprted on the amd64 > platform. Like the message tells you. Well, but Opera is an i386 binary. You may be able to run it if you can get the compat4x-i386 package installed, since it would need the i386 libraries anyway. But it would need the i386 X libraries too... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 2 22:30:59 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB21716A420 for ; Fri, 2 Dec 2005 22:30:59 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (hood.oook.cz [195.250.137.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAD2C43D8D for ; Fri, 2 Dec 2005 22:30:48 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from ikaros.oook.cz (localhost [127.0.0.1]) by hood.oook.cz (8.13.4/8.13.4) with ESMTP id jB2MUMfB000497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 23:30:44 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by ikaros.oook.cz (8.13.4/8.13.4/Submit) id jB2K3v7t083609; Fri, 2 Dec 2005 21:03:57 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: ikaros.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Popov Maxim In-Reply-To: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> References: <4bdd3edf0512020945y7bb688fei@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-AKETjghTbi4Tgp/RYxao" Date: Fri, 02 Dec 2005 21:03:57 +0100 Message-Id: <1133553837.43646.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Cc: freebsd-amd64@FreeBSD.org Subject: Re: Installing Opera ... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 22:31:00 -0000 --=-AKETjghTbi4Tgp/RYxao Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Popov Maxim p=ED=B9e v p=E1 02. 12. 2005 v 19:45 +0200: > Hi, i can't install opera .... i did that: >=20 > (messages given by the system may be different, i'm not under FreeBSD > at the moment) >=20 > cd /usr/ports/www/opera/ > make >=20 > it throws an error and says: >=20 > this package is not supported on your platform (amd64 ofcourse). >=20 > Ok, then, i commented the ARCH=3Di386 option in the Makefile and it > throws an error again. >=20 > In my kernel configuration there is enabled the i386 compatibity > option (don't remember how it is named exactly). >=20 > How to install opera ? Opera does not provide amd64 binaries, and their i386 binaries are dynamically linked. You can attempt the installation by hand. Or you can try linux-opera port which should run on amd64 (i386 linux binaries are emulated on amd64). --=20 Pav Lucistnik The Novice rogue. A rather shifty individual --=-AKETjghTbi4Tgp/RYxao Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDkKitntdYP8FOsoIRAs9NAJ9cvGFdYR+ZZJ08h/0hOAvCGcdpYwCfX7m1 ER8lxpXeTeF1ycQ1I82lwJ8= =D0kl -----END PGP SIGNATURE----- --=-AKETjghTbi4Tgp/RYxao-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 3 00:51:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15DB516A41F for ; Sat, 3 Dec 2005 00:51:46 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3455D43D4C for ; Sat, 3 Dec 2005 00:51:45 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 3244B8A004A for ; Fri, 2 Dec 2005 16:51:45 -0800 (PST) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 55785-01-26 for ; Fri, 2 Dec 2005 16:51:42 -0800 (PST) Received: from imap.sd73.bc.ca (smtp.sd73.bc.ca [10.10.10.15]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 7515C8A01A4 for ; Fri, 2 Dec 2005 16:51:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id E349F18CC4A for ; Fri, 2 Dec 2005 17:55:23 -0800 (PST) Received: from imap.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 41987-11-3 for ; Fri, 2 Dec 2005 17:55:22 -0800 (PST) Received: by imap.sd73.bc.ca (Postfix, from userid 80) id 6B3D618CC76; Fri, 2 Dec 2005 17:55:22 -0800 (PST) Received: from 24.71.129.36 (SquirrelMail authenticated user fcash) by imap.sd73.bc.ca with HTTP; Fri, 2 Dec 2005 17:55:22 -0800 (PST) Message-ID: <60129.24.71.129.36.1133574922.squirrel@imap.sd73.bc.ca> In-Reply-To: <20051202204923.GD20567@odin.ac.hmc.edu> References: <200512022021.UAA20705@sopwith.solgatos.com> <20051202133010.21549f90.kgunders@teamcool.net> <20051202204923.GD20567@odin.ac.hmc.edu> Date: Fri, 2 Dec 2005 17:55:22 -0800 (PST) From: "Freddie Cash" To: freebsd-amd64@freebsd.org User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Subject: Re: How to get support (was: Tyan alternatives cuz their support totally sucks) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fcash@ocis.net List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2005 00:51:46 -0000 > On Fri, Dec 02, 2005 at 01:30:10PM -0700, Ken Gunderson wrote: >> On Fri, 02 Dec 2005 12:21:15 +0000 >> Dieter wrote: >>>> I've been really quite happy w/the Tyan barebones systems I've >>>> deployed the past few months. Until I needed support on a DOA >>>> TA26 barebones unit. I'll spare you the gory details but the >>>> nightmare is ongoing. >>>> I need something that will "just work" and not require any >>>> hardware compatibility histrionics. We've had great experiences with MSI Master-series motherboards (K7D and K8). All of our elementary school servers are running the K7D dual-AthlonMP boards, a few of our early rackmounts are running K8 dual-Opteron boards. All our new systems, though, are Tyan dual-Opteron boards. >>>> Yes, the Tyan units are great themselves. >>>> The issue is getting support when you need it. >>> Have your VP visit one of Tyan's VPs and wave a million dollar PO >>> in their face. >> Unfortunately that's about the reality of it... >> I will say in Tyan's defense that things improved significantly >> once I gave up on support and started working my way up the sales >> management ladder. Keeping future sales seems to motivate them >> enough to get things done. > I think this is one of those cases when it's much better do deal with > them through a good reseller. The reseller has much better leverage > then most customers since they buy a lot more boards. You still > have to make the reseller care, but I'm had pretty good luck with that > myself (of course, I often buy half a rack or more machines at a time > which tends to hold their attention. :) That's the way to do it. We have a local computer company that handles all our hardware needs. We buy in bulk from them, if anything goes wrong they look after it. If it needs to go back to the manufacturer/vendor then they get replacements for us up front and handle all the dirty work behind the scenes. We never have to worry about contacting Tyan, or MSI, or Maxtor, or anybody. :) -- Freddie Cash, CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash@sd73.bc.ca helpdesk@sd73.bc.ca