From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 19 02:07:21 2006 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 57D6E16A420 for ; Sun, 19 Feb 2006 02:07:21 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id A458843D45 for ; Sun, 19 Feb 2006 02:07:20 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k1J27CdJ032007; Sun, 19 Feb 2006 13:07:12 +1100 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k1J279wC022361; Sun, 19 Feb 2006 13:07:10 +1100 Date: Sun, 19 Feb 2006 13:07:10 +1100 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Andrew Gallatin In-Reply-To: <17399.39290.13815.777894@grasshopper.cs.duke.edu> Message-ID: <20060219115807.F99158@epsplex.bde.org> References: <17397.58669.457047.277510@grasshopper.cs.duke.edu> <20060218232213.F59482@delplex.bde.org> <17399.39290.13815.777894@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@FreeBSD.org Subject: Re: non-temporal copyin/copyout? 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, 19 Feb 2006 02:07:21 -0000 On Sat, 18 Feb 2006, Andrew Gallatin wrote: > Bruce Evans writes: > > > A quick test in userspace shows that for large copies, an adapted > > > pagecopy (from amd64/amd64/support.S) more than doubles bcopy > > > bandwidth from 1.2GB/s to 2.5GB/s on my on my Athlon64 X2 3800+. > > > > Is this with 5+GHz memory or with slower memory with the source cached? > > I've seen 1.7GB/s in non-quick tests in user space with PC3200 memory > > overclocked slightly. This is almost twice as fast as using the best > > nontemporal copy method (which gives 0.9GB/s on the same machine). > > This is a "DFI Lanparty UTnF4 Ultra-D" with an Nforce 4 chipset, and 2 > 256 MB sticks of PC3200 ram. The timings I mention above closely > match the lmbench "bcopy" benchmark for large buffers (> L2 cache) > when run on FreeBSD vs when run on Solaris (which uses a non-temporal > bcopy even in userspace). The 2.5GB/s is for the source already cached then. I'm familiar with lmbench. At least in lmbench2, the default pipe benchmark goes at nearly main memory bandwidth on FreeBSD (because the source is cached and half of the copying is virtual), and the default bcopy benchmark goes at about 1/4 of the main memory bandwidth (wasting half the bandwidth) because it is too big for the (L2) cache but the cache is used. > <....> > > > With the Athlon64 behaviour, I think nontemporal copies should only be > > used in cases where it is know that the copies really are nontemporal. > > We use them for page copying now because this is (almost) known. For > > copyout(), it would be certainly known only for copies that are so large > > that they can't fit in the L2 cache. copyin() might be different, since > > it might often be known that the data will be DMA'ed out by a driver and > > need never be cached. > > I think you could make arguments for doing a non-temporal copy for > both copyin and copyout when the size exceeds some tunable threshold. > Solaris even uses a fixed threshold, and I believe the threshold is > quite small (128 bytes). See > http://cvs.opensolaris.org/source/xref/on/usr/src/uts/intel/ia32/ml/copy.s Hmm, that seems far too small. You could make it a sysctl tunable. > Maybe I'm being naive, but I would assume that most bulk data, both > copied in and copied out should never be accessed by the kernel in a > high performance system. Most Gigabit or better, and many 100Mb > network drivers do checksum offloading on both send and receive, so > there is no need for the kernel to touch any data which is copied in > or out for network sends or receives. Further, I can imagine a > network server (like a userspace nfs server or samba) turning around > and writing data to disk which it received via a socket read without > ever looking at the buffer. > > I don't know the storage system as well as the networking system, but > unless a disk driver is using PIO, I don't think the data is ever > touched by the kernel. read()/write() to disk files still always gives through the buffer cache and uses uiomove() and thus copyin/out() to get there. Thus the best method of reading from a socket and write(2)ing to a disk is almost certainly to use a buffer small enough to fit several times in the L2 cache and stay there, and temporal copyout() but temporal copyin() so that the copyout() from the socket buffer prepares for soon rereading the data in the copyin() but the copyin() doesn't prepare for rereading (since the disk driver should use DMA and not do the write for ~30 seconds anyway and it is not expected that the data be otherwise read from the buffer cache). If the application writes the data using m[un]map() and doesn't access it directly, then nontemporal copyout()s seem to be better than than temporaral ones. Even if the vm system copies the data later (I think it doesn't), then the data is likely to have gone out of the L2 cache (if the copyout() put it there) by the time vm gets around to writing it. Aren't you supposed to use ZERO_COPY_SOCKETS to avoid all copying for socket buffers? Bruce From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 19 09:19:11 2006 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 3A99E16A420 for ; Sun, 19 Feb 2006 09:19:11 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCBF43D45 for ; Sun, 19 Feb 2006 09:19:09 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1J9J8t2019124 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 19 Feb 2006 20:19:08 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1J9J7Xp000794 for ; Sun, 19 Feb 2006 20:19:08 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1J9J74F000793 for freebsd-amd64@freebsd.org; Sun, 19 Feb 2006 20:19:07 +1100 (EST) (envelope-from peter) Date: Sun, 19 Feb 2006 20:19:07 +1100 From: Peter Jeremy To: freebsd-amd64@freebsd.org Message-ID: <20060219091907.GA738@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Subject: Hard hang using powerd 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, 19 Feb 2006 09:19:11 -0000 I have an HP nx6125, running about a two week old 6-stable/amd64 and I've found that powerd causes random hard hangs (no response to anything except holding the power-switch down for an extended period). This occurs with both cpufreq and raw acpi frequency control. I wrote a perl script to pseudo-randomly change CPU frequency much as powerd does (but ignoring the load impact) and could trigger the problem after about 12 minutes with a buildworld happening. Has anyone else seen this problem? -- Peter Jeremy From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 19 22:51:31 2006 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 E9EA016A420 for ; Sun, 19 Feb 2006 22:51:31 +0000 (GMT) (envelope-from bsd@mokuhi.com) Received: from 26.mail-out.ovh.net (26.mail-out.ovh.net [213.186.42.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 213B043D48 for ; Sun, 19 Feb 2006 22:51:30 +0000 (GMT) (envelope-from bsd@mokuhi.com) Received: (qmail 8966 invoked by uid 503); 19 Feb 2006 22:51:45 -0000 Received: (QMFILT: 1.0); 19 Feb 2006 22:51:45 -0000 Received: from b6.ovh.net (HELO mail1.ha.ovh.net) (213.186.33.56) by 26.mail-out.ovh.net with SMTP; 19 Feb 2006 22:51:45 -0000 Received: from b0.ovh.net (HELO queue-out) (213.186.33.50) by b0.ovh.net with SMTP; 19 Feb 2006 22:51:35 -0000 Received: from mail45.ha.ovh.net (HELO mail1.ha.ovh.net) (10.0.50.45) by mail45.ha.ovh.net with SMTP; 19 Feb 2006 22:51:30 -0000 Received: from b0.ovh.net (HELO queue-pre) (213.186.33.50) by b0.ovh.net with SMTP; 19 Feb 2006 22:51:29 -0000 Received: from serveur.mokuhi.com (HELO ?192.168.0.3?) (postmaster@mokuhi.com@82.66.114.172) by ns0.ovh.net with SMTP; 19 Feb 2006 22:51:29 -0000 Message-ID: <43F8F665.7000301@mokuhi.com> Date: Sun, 19 Feb 2006 23:51:17 +0100 From: Nicolas Lallouet User-Agent: Thunderbird 1.5 (X11/20060114) MIME-Version: 1.0 To: Ken Easson References: <200602141729.k1EHTH4m049307@peedub.jennejohn.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Ovh-Remote: 82.66.114.172 (serveur.mokuhi.com) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-Spam-Check: fait|type 1&3|0.0|H 0.5 Cc: amd64@freebsd.org Subject: Re: freebsd 5.4 gnome 2.12 build problems. 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, 19 Feb 2006 22:51:32 -0000 Ken Easson wrote: > Thank you Gary for taking the time to help me. > > I got stuck at "try doing ldd on the libraries that are being linked" > I've never used ldd, i read the man pages, and tried a number of things, > but i don't know what i'm doing. Would you be kind enough to give me a > few pointers? > > I've looked up fPIC and now that i understand what that does, the > problem seems more clear - however, i'm still not seeing a solution. > > I'm thinking to update the entire system to 6.0 stable, I'm wondering if > this update could fix my problems during the rebuild, or just compound > them. any advice? > Hy Ken, This wont to much... I have the same problem on AMD64 5.4. Since it appeared (29th Dec 2005), I upgraded to 6.0. This did not change anything! I am still waiting for some answer. Unfortunately, I don't have much time try and find a solution. I did try recompiling libgsf, with no changes. I've already tried contacting one of the maintainers, but no solutions were found at the time. Maybe you could contact them, and see how to solve the problem which seems to be just a compilation issue. -- Lallouet Nicolas Epita - SIGL 2007 From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 20 08:34:17 2006 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 3444116A422 for ; Mon, 20 Feb 2006 08:34:17 +0000 (GMT) (envelope-from apple@justken.net) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADC4F43D53 for ; Mon, 20 Feb 2006 08:34:14 +0000 (GMT) (envelope-from apple@justken.net) Received: from ip04.eastlink.ca ([24.222.10.20]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IUZ0028893H2IA0@mta01.eastlink.ca> for amd64@freebsd.org; Mon, 20 Feb 2006 04:33:17 -0400 (AST) Received: from server4.justken.net (HELO [192.168.0.57]) ([24.222.15.13]) by ip04.eastlink.ca with ESMTP; Mon, 20 Feb 2006 04:34:13 -0400 Date: Mon, 20 Feb 2006 04:22:51 -0400 From: Ken Easson In-reply-to: <43F8F665.7000301@mokuhi.com> To: Nicolas Lallouet Message-id: <39a30e62d378b1e32bc686acd29ae6c7@justken.net> MIME-version: 1.0 X-Mailer: Apple Mail (2.623) Content-type: text/plain; charset=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= References: <200602141729.k1EHTH4m049307@peedub.jennejohn.org> <43F8F665.7000301@mokuhi.com> Cc: amd64@freebsd.org Subject: Re: freebsd 5.4 gnome 2.12 build problems. 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, 20 Feb 2006 08:34:17 -0000 On 19-Feb-06, at 6:51 PM, Nicolas Lallouet wrote: > Ken Easson wrote: >> Thank you Gary for taking the time to help me. >> I got stuck at "try doing ldd on the libraries that are being linked" >> I've never used ldd, i read the man pages, and tried a number of >> things, but i don't know what i'm doing. Would you be kind enough to >> give me a few pointers? >> I've looked up fPIC and now that i understand what that does, the >> problem seems more clear - however, i'm still not seeing a solution. >> I'm thinking to update the entire system to 6.0 stable, I'm wondering >> if this update could fix my problems during the rebuild, or just >> compound them. any advice? > > > Hy Ken, > > This wont to much... I have the same problem on AMD64 5.4. Since it > appeared (29th Dec 2005), I upgraded to 6.0. This did not change > anything! > > I am still waiting for some answer. Unfortunately, I don't have much > time try and find a solution. > > I did try recompiling libgsf, with no changes. I've already tried > contacting one of the maintainers, but no solutions were found at the > time. Maybe you could contact them, and see how to solve the problem > which seems to be just a compilation issue. > > -- > Lallouet Nicolas > Epita - SIGL 2007 > > I've upgraded kernel and userland to Freebsd 6.1, i've followed the instructions in the Freebsd manual to completely remove all gnome2 (pkg_delete -rf pkgconfig\* ), and have deinstalled and reinstalled xorg. while trying to build gnome2 again (after a reboot) using "make install clean" the build Stopped with the same error in librsvg-2.12.7 as i've previously posted. It seems that the fault lies somewhere in libgsf-1 (currently my system is installing libgsf-1.13.3) i have the following related libraries: /usr/local/include/libgsf-1 /usr/local/llib/compat/pkg/libgsf-1.so.12 /usr/local/lib/libgsf-1.so -> libgsf-1.12 /usr/local/lib/libgsf-1.a /usr/local/libdata/pkgconfig/libgsf-1.pc /usr/X11R6/include/libgsf-1 /usr/X11R6/lib/libgsf-1.so.113 /usr/X11R6/lib/libgsf-1.so /usr/X11R6/lib/libgsf-1.a /usr/X11R6/libdata/pkgconfig/libgsf-1.pc /usr/X11R6/share/locale/es/LC_MESSAGES/libgsf.mo trying ldd /usr/local/lib/libgsf-1.so returns "no such file or directory" the file is a symlink to libgsf-1.so.12 which of course doesn't exist. I deleted the link. and rebuilt libgsf andd libgsf-gnome - this did not create a dynalic library in /usr/local/lib - could this be the problem? prior to fully removing gnome from my system, Gnome would run, upon exit, a large number of references to libgobject-2.0.so.600 not being found are in the log. I'm using amd64 on a dual opteron 242 server, Tyan K8S with 1G of ram. I'm also using Gamin instead of Fam which required i modify a number of links in the pkgdb. After deleting the broken symlink - i once again deleted the full gnome2 package, and and am again trying to make all of gnome2.12 - i'll report success if it builds. ken easson From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 20 11:02:24 2006 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 6D98816A420 for ; Mon, 20 Feb 2006 11:02:24 +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 27C8943D45 for ; Mon, 20 Feb 2006 11:02:24 +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.4/8.13.4) with ESMTP id k1KB2OkJ083476 for ; Mon, 20 Feb 2006 11:02:24 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1KB2M3m083469 for freebsd-amd64@freebsd.org; Mon, 20 Feb 2006 11:02:22 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Feb 2006 11:02:22 GMT Message-Id: <200602201102.k1KB2M3m083469@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, 20 Feb 2006 11:02:24 -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/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/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/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) o [2005/12/05] amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem o [2005/12/22] amd64/90798 amd64 asking if motherboard is compatible o [2006/01/06] amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr o [2006/01/08] amd64/91492 amd64 BTX halted o [2006/01/26] amd64/92337 amd64 FreeBsd 6.0 Release Intel Pro 1000 MT em1 o [2006/02/06] amd64/92889 amd64 xdr double buffer overflow o [2006/02/07] amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk o [2006/02/08] amd64/93065 amd64 Running make depend on GENERIC kernel fai o [2006/02/14] amd64/93325 amd64 mount_ufs fails mounting Nero UFS DVD+RW o [2006/02/16] amd64/93413 amd64 lpd does not remove lock file from /var/s o [2006/02/17] amd64/93469 amd64 uninitialised struct stat in lpd prevents 65 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/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/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported 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 o [2006/01/02] amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP o [2006/01/18] amd64/91966 amd64 an error in config of kernel o [2006/01/27] amd64/92412 amd64 rcp.rstatd reports bogus packets/per/seco o [2006/01/28] amd64/92463 amd64 Buttons of USB mouse do no work under KDE o [2006/01/30] amd64/92527 amd64 no driver for "CICADA VSC 8201 Gigabit LA o [2006/02/07] amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable ti o [2006/02/09] amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognize 21 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 20 19:03:46 2006 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 300C416A420 for ; Mon, 20 Feb 2006 19:03:46 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mail08b.verio.de (mail08b.verio.de [213.198.55.74]) by mx1.FreeBSD.org (Postfix) with SMTP id B81B943D64 for ; Mon, 20 Feb 2006 19:03:42 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx02.stngva01.us.mxservers.net (204.202.242.66) by mail08b.verio.de (RS ver 1.0.95vs) with SMTP id 4-0524012219; Mon, 20 Feb 2006 20:03:41 +0100 (CET) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx02.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id c821af34.11280.351.mx02.stngva01.us.mxservers.net; Mon, 20 Feb 2006 14:03:40 -0500 (EST) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id k1KJ3bvh003124; Mon, 20 Feb 2006 20:03:37 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200602201903.k1KJ3bvh003124@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Ken Easson In-Reply-To: Message from Ken Easson of "Mon, 20 Feb 2006 04:22:51 -0400." <39a30e62d378b1e32bc686acd29ae6c7@justken.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Feb 2006 20:03:37 +0100 From: Gary Jennejohn X-Spam: [F=0.0366079703; heur=0.500(-19800); stat=0.010; spamtraq-heur=0.790(2006021901)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: amd64@freebsd.org Subject: Re: freebsd 5.4 gnome 2.12 build problems. 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, 20 Feb 2006 19:03:46 -0000 Ken Easson writes: > I've upgraded kernel and userland to Freebsd 6.1, i've followed the > instructions in the Freebsd manual to completely remove all gnome2 > (pkg_delete -rf pkgconfig\* ), and have deinstalled and reinstalled > xorg. > > while trying to build gnome2 again (after a reboot) using "make install > clean" the build Stopped with the same error in librsvg-2.12.7 as i've > previously posted. > I just did a _virgin_ install of gnome2 on my 64-bit system and had NO problems whatsoever! Note: virgin means there was _never_ a previous installtion of gnome2 on my machine, since I find gnome much too bloated to be useful. Anyway, this leads me to conclude that there's a remnant of some gnome2 dependency on your machine which is causing all the problems. I recommend a radical cure: 1) delete /usr/X11R6 2) delete /usr/local 3) delete /var/db/pkg/* 4) delete /var/db/ports/* 5) do a fresh install of gnome2 for Ernst Winter: I also installed AbiWord with no problem. I suspect you have similar trash on your system. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 20 22:07:19 2006 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 4D2B916A420 for ; Mon, 20 Feb 2006 22:07:19 +0000 (GMT) (envelope-from apple@justken.net) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3B6543D49 for ; Mon, 20 Feb 2006 22:07:18 +0000 (GMT) (envelope-from apple@justken.net) Received: from ip01.eastlink.ca ([24.222.10.5]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IV0002OIAQL2FX1@mta01.eastlink.ca> for amd64@freebsd.org; Mon, 20 Feb 2006 18:06:21 -0400 (AST) Received: from server4.justken.net (HELO [192.168.0.57]) ([24.222.15.13]) by ip01.eastlink.ca with ESMTP; Mon, 20 Feb 2006 18:07:18 -0400 Date: Mon, 20 Feb 2006 17:55:58 -0400 From: Ken Easson In-reply-to: <200602201903.k1KJ3bvh003124@peedub.jennejohn.org> To: Gary Jennejohn Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.623) Content-type: text/plain; charset=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= References: <200602201903.k1KJ3bvh003124@peedub.jennejohn.org> Cc: amd64@freebsd.org Subject: Re: freebsd 5.4 gnome 2.12 build problems. 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, 20 Feb 2006 22:07:19 -0000 On 20-Feb-06, at 3:03 PM, Gary Jennejohn wrote: > > Ken Easson writes: >> I've upgraded kernel and userland to Freebsd 6.1, i've followed the >> instructions in the Freebsd manual to completely remove all gnome2 >> (pkg_delete -rf pkgconfig\* ), and have deinstalled and reinstalled >> xorg. >> >> while trying to build gnome2 again (after a reboot) using "make >> install >> clean" the build Stopped with the same error in librsvg-2.12.7 as i've >> previously posted. >> > > I just did a _virgin_ install of gnome2 on my 64-bit system and had NO > problems whatsoever! > > Note: virgin means there was _never_ a previous installtion of gnome2 > on my machine, since I find gnome much too bloated to be useful. > > Anyway, this leads me to conclude that there's a remnant of some gnome2 > dependency on your machine which is causing all the problems. > > I recommend a radical cure: > > 1) delete /usr/X11R6 > 2) delete /usr/local > 3) delete /var/db/pkg/* > 4) delete /var/db/ports/* > 5) do a fresh install of gnome2 > > for Ernst Winter: I also installed AbiWord with no problem. I suspect > you > have similar trash on your system. > > --- > Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg > garyjATdenxDOTde > > > Thank you. I have managed to get past the problem by copying the libgsf-1.so.12 file from the /usr/local/lib/contrib folder and then symlinknig that to libgsf-1.so.12 whether that will actually fix the underlying problem or not - i don't know. Seems for some reason on my system that librsvg requires a symlinked version of libgsf, while the new libgsf 1.13 doesn't create such a file. I'm still in the process or rebuilding Gnome2, however - once i'm finished i'll post my success. thanks again. ken easson From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 21 23:50:43 2006 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 A3EA516A423; Tue, 21 Feb 2006 23:50:43 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA00143D64; Tue, 21 Feb 2006 23:50:40 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1LNoect050593; Tue, 21 Feb 2006 23:50:40 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1LNocT6050588; Tue, 21 Feb 2006 23:50:38 GMT (envelope-from linimon) Date: Tue, 21 Feb 2006 23:50:38 GMT From: Mark Linimon Message-Id: <200602212350.k1LNocT6050588@freefall.freebsd.org> To: mohringarmin@hotmail.de, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/92463: Buttons of USB mouse do no work under KDE 3.4.2 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, 21 Feb 2006 23:50:43 -0000 Synopsis: Buttons of USB mouse do no work under KDE 3.4.2 State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Feb 21 23:49:54 UTC 2006 State-Changed-Why: Please ask general X11 support questions on the freebsd-x11 mailing list. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=92463 From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 21 23:53:09 2006 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 6BCFC16A420; Tue, 21 Feb 2006 23:53:09 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31FFB43D46; Tue, 21 Feb 2006 23:53:09 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1LNr9KQ050701; Tue, 21 Feb 2006 23:53:09 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1LNr88o050697; Tue, 21 Feb 2006 23:53:08 GMT (envelope-from linimon) Date: Tue, 21 Feb 2006 23:53:08 GMT From: Mark Linimon Message-Id: <200602212353.k1LNr88o050697@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: bin/92412: [patch] rup(1): rpc.rstatd reports bogus packets/per/second info 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, 21 Feb 2006 23:53:09 -0000 Old Synopsis: rup(1): rpc.rstatd reports bogus packets/per/second info New Synopsis: [patch] rup(1): rpc.rstatd reports bogus packets/per/second info Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Feb 21 23:52:43 UTC 2006 Responsible-Changed-Why: This does not sound amd64-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=92412 From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 21 23:55:01 2006 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 2458B16A422; Tue, 21 Feb 2006 23:55:01 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE67243D46; Tue, 21 Feb 2006 23:55:00 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1LNt0to050769; Tue, 21 Feb 2006 23:55:00 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1LNsx1h050761; Tue, 21 Feb 2006 23:54:59 GMT (envelope-from linimon) Date: Tue, 21 Feb 2006 23:54:59 GMT From: Mark Linimon Message-Id: <200602212354.k1LNsx1h050761@freefall.freebsd.org> To: jansen@cpamn.embrapa.br, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/91966: an error in config of kernel 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, 21 Feb 2006 23:55:01 -0000 Synopsis: an error in config of kernel State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Feb 21 23:53:19 UTC 2006 State-Changed-Why: Feedback timeout (>1 month). http://www.freebsd.org/cgi/query-pr.cgi?pr=91966 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 22 17:33:47 2006 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 6795C16A420 for ; Wed, 22 Feb 2006 17:33:47 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC95343D5A for ; Wed, 22 Feb 2006 17:33:41 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FBxrx-000Fnz-9Y for freebsd-amd64@freebsd.org; Wed, 22 Feb 2006 18:33:41 +0100 Message-ID: <43FCA206.50707@datafarm.de> Date: Wed, 22 Feb 2006 18:40:22 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, 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: anyone successfully using an icp-vortex / iir controller? 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, 22 Feb 2006 17:33:47 -0000 Hello, is there anyone here successfully using a raid-controller that's supported by iir(4) in a system with >= 4GB RAM? After a couple of days testing with both GDT8500RZ and GDT8114RZ it seems as if the iir driver is broken. Disk access crashes the system when there are >=4GB of main memory installed. I would reall ylike to here that it's a local problem, but with all the data collected so far I would also be really surprised to hear so. If noone convices me that it's working, I will file a bug report tomorrow. Cheers, vt From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 22 17:41:51 2006 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 D9BEE16A420 for ; Wed, 22 Feb 2006 17:41:51 +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 34C0B43D79 for ; Wed, 22 Feb 2006 17:41:43 +0000 (GMT) (envelope-from ray@redshift.com) Received: (qmail 92542 invoked by uid 89); 22 Feb 2006 17:41:42 -0000 Received: by simscan 1.2.0 ppid: 92536, pid: 92539, t: 0.0726s scanners: attach: 1.2.0 clamav: 0.88/m:36/d:1297 Received: from unknown (HELO workstation) (216.228.19.21) by mail-pop.redshift.com with SMTP; 22 Feb 2006 17:41:42 -0000 Message-Id: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> X-Mailer: na X-Sender: redshift.com Date: Wed, 22 Feb 2006 09:41:47 -0800 To: "V. T. Mueller" ,freebsd-amd64@freebsd.org From: ray@redshift.com In-Reply-To: <43FCA206.50707@datafarm.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: eniazi@ossmail.com Subject: Re: anyone successfully using an icp-vortex / iir controller? 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, 22 Feb 2006 17:41:52 -0000 you might want to check with Eren over at OSS (eniazi@ossmail.com) - I don't think he's on the list, but I know they do a lot with ICP and he may have some clients using it under FreeBSD. I believe they use 3ware and ICP, so I would bet they could toss their 2 cents in. Just a thought. Hope that helps :) ray cc: eniazi@ossmail.com At 06:40 PM 2/22/2006 +0100, V. T. Mueller wrote: | | Hello, | | is there anyone here successfully using a raid-controller that's | supported by iir(4) in a system with >= 4GB RAM? | | After a couple of days testing with both GDT8500RZ and GDT8114RZ it | seems as if the iir driver is broken. Disk access crashes the system | when there are >=4GB of main memory installed. | | I would reall ylike to here that it's a local problem, but with all | the data collected so far I would also be really surprised to hear so. | | If noone convices me that it's working, I will file a bug report | tomorrow. | | Cheers, | vt | _______________________________________________ | 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 Feb 22 23:11:59 2006 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 11EC116A420 for ; Wed, 22 Feb 2006 23:11:59 +0000 (GMT) (envelope-from terry@bluelight.org.uk) Received: from grump.bluelight.org.uk (bluelight.org.uk [80.229.144.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B7F43D49 for ; Wed, 22 Feb 2006 23:11:56 +0000 (GMT) (envelope-from terry@bluelight.org.uk) Received: from games ([192.168.2.138]) by grump.bluelight.org.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1FC3HG-000684-M6 for freebsd-amd64@freebsd.org; Wed, 22 Feb 2006 23:20:11 +0000 Message-ID: <43FCEF9C.5050308@bluelight.org.uk> Date: Wed, 22 Feb 2006 23:11:24 +0000 From: Terry 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: multipart/mixed; boundary="------------060106020803080900070707" X-Spam-Score: -1.4 (-) X-Spam-Report: Spam detection software, running on the system "grump.bluelight.org.uk", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I need to build a new server to send down to the data centre for hosting and possible game server type stuff. I have a ASUS 64 bit board and cpu spare so was considering using these with amd64 version. But due to the data centre being 300 mile away i thought i would check how you guys are finding it first :). Or shall i play it safe and use the i386 i just can't decide [...] Content analysis details: (-1.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 AWL AWL: From: address is in the auto white-list X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: AMD 64 stability 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, 22 Feb 2006 23:11:59 -0000 This is a multi-part message in MIME format. --------------060106020803080900070707 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I need to build a new server to send down to the data centre for hosting and possible game server type stuff. I have a ASUS 64 bit board and cpu spare so was considering using these with amd64 version. But due to the data centre being 300 mile away i thought i would check how you guys are finding it first :). Or shall i play it safe and use the i386 i just can't decide Ter --------------060106020803080900070707-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 22 23:21:58 2006 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 82B6116A420 for ; Wed, 22 Feb 2006 23:21:58 +0000 (GMT) (envelope-from chaim.rieger@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 669BD43D45 for ; Wed, 22 Feb 2006 23:21:57 +0000 (GMT) (envelope-from chaim.rieger@gmail.com) Received: by xproxy.gmail.com with SMTP id s7so51709wxc for ; Wed, 22 Feb 2006 15:21:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=hPGPlJdE1RJxzrWnh8jXSHfMo4CgxI8FMDTSSiE5O28G77CGiSze25nyMM/2H9lJ0zAdAKJwA7I9DGg3ROTyXsxUeEjUHPwSjxxp9aMmR23uJMySlSfLHQNbwXVlMHxzbhYQDyBmakT1nPoLRrdP9LaxR12KCBaNW33cshaeiaw= Received: by 10.70.124.12 with SMTP id w12mr4277173wxc; Wed, 22 Feb 2006 15:21:56 -0800 (PST) Received: from ?172.28.42.203? ( [209.104.55.7]) by mx.gmail.com with ESMTP id i35sm24427wxd.2006.02.22.15.21.55; Wed, 22 Feb 2006 15:21:56 -0800 (PST) Message-ID: <43FCF211.4060509@gmail.com> Date: Wed, 22 Feb 2006 15:21:53 -0800 From: Chaim Rieger User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Terry References: <43FCEF9C.5050308@bluelight.org.uk> In-Reply-To: <43FCEF9C.5050308@bluelight.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 22 Feb 2006 23:21:58 -0000 Terry wrote: > I need to build a new server to send down to the data centre for hosting > and possible game server type stuff. > I have a ASUS 64 bit board and cpu spare so was considering using these > with amd64 version. But due to the data centre being 300 mile away i > thought i would check how you guys are finding it first :). Or shall i > play it safe and use the i386 i just can't decide > > Ter i am running amd64 without any major issues. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 04:19:40 2006 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 A8CD416A420 for ; Thu, 23 Feb 2006 04:19:40 +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 5359D43D45 for ; Thu, 23 Feb 2006 04:19:40 +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 2039BF819 for ; Wed, 22 Feb 2006 21:19:37 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id F0C98F811 for ; Wed, 22 Feb 2006 21:19:36 -0700 (MST) Date: Wed, 22 Feb 2006 21:19:36 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060222211936.6c582399.kgunders@teamcool.net> In-Reply-To: <43FCF211.4060509@gmail.com> References: <43FCEF9C.5050308@bluelight.org.uk> <43FCF211.4060509@gmail.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: AMD 64 stability 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, 23 Feb 2006 04:19:40 -0000 On Wed, 22 Feb 2006 15:21:53 -0800 Chaim Rieger wrote: > Terry wrote: > > I need to build a new server to send down to the data centre for hosting > > and possible game server type stuff. > > I have a ASUS 64 bit board and cpu spare so was considering using these > > with amd64 version. But due to the data centre being 300 mile away i > > thought i would check how you guys are finding it first :). Or shall i > > play it safe and use the i386 i just can't decide > > > > Ter > > > i am running amd64 without any major issues. The operative here being "major". FreeBSD AMD64 rocks. But.. that said, if you're dealing w/a colo situation 300 miles away "playing it safe" may be the prudent thing to do. -- 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 Feb 23 04:35:20 2006 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 372A016A420 for ; Thu, 23 Feb 2006 04:35:20 +0000 (GMT) (envelope-from freebsd@rtl.fmailbox.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2B7043D70 for ; Thu, 23 Feb 2006 04:35:16 +0000 (GMT) (envelope-from freebsd@rtl.fmailbox.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 18EB7D37F0A; Wed, 22 Feb 2006 23:35:15 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Wed, 22 Feb 2006 23:35:15 -0500 X-Sasl-enc: eVJkHen0i6oCrA+ceauivtiqpUW300kjSPAeTjnL8sSv 1140669313 Received: from [192.168.1.51] (cwpp-p-144-139-3-235.prem.tmns.net.au [144.139.3.235]) by frontend2.messagingengine.com (Postfix) with ESMTP id 257F4575A7A; Wed, 22 Feb 2006 23:35:11 -0500 (EST) Message-ID: <43FD3B83.2040109@rtl.fmailbox.com> Date: Thu, 23 Feb 2006 15:35:15 +1100 From: Robert Leftwich User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry References: <43FCEF9C.5050308@bluelight.org.uk> In-Reply-To: <43FCEF9C.5050308@bluelight.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 04:35:20 -0000 Terry wrote: > I need to build a new server to send down to the data centre for hosting > and possible game server type stuff. > I have a ASUS 64 bit board and cpu spare so was considering using these > with amd64 version. But due to the data centre being 300 mile away i > thought i would check how you guys are finding it first :). Or shall i > play it safe and use the i386 i just can't decide > It depends on exactly which ASUS 64 bit board you have - if you have an a8n-sli then I would steer clear of AMD64, I've reported memory leaks and the inability to run with 4gb of ram, both of which are unresolved at this point. I'm currently testing with Ubuntu 64 (live cd) and it appears to be able to access all 4gb of ram w/o a problem. I'm about to bite the bullet, install Ubuntu (server) as well as dump/restore a boatload of data into the databases so I can see if the memory leak is a FreeBSD problem or not (sigh). Be wary of FreeBSD's AMD64 support - test, test again and do even more testing before the box leaves your sight! Robert From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 06:27:03 2006 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 858DD16A420 for ; Thu, 23 Feb 2006 06:27:03 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E976A43D73 for ; Thu, 23 Feb 2006 06:27:02 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1212646wxc for ; Wed, 22 Feb 2006 22:27:02 -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=PDLI5LB6wFFTMaBDbTaDwPwl6GfRztrbJdT6DM4Yw3elgLmDJxAhikZfkgeyGpE/epxV/SUuX8jch74oL2SQI3YsXHbPcP/XQgzIIUKdNzcWEmdbNEx3IvdwyOyzCASNKce3HI/cJj36pL8eJqB5Qdw9b7//UCVAAb4rgqhkd9c= Received: by 10.70.112.1 with SMTP id k1mr6072990wxc; Wed, 22 Feb 2006 22:27:02 -0800 (PST) Received: by 10.70.116.16 with HTTP; Wed, 22 Feb 2006 22:27:02 -0800 (PST) Message-ID: <84dead720602222227g5dcdf987v16cc47f885b0c6a1@mail.gmail.com> Date: Thu, 23 Feb 2006 11:57:02 +0530 From: "Joseph Koshy" To: Terry In-Reply-To: <43FCEF9C.5050308@bluelight.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43FCEF9C.5050308@bluelight.org.uk> Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 06:27:03 -0000 t> I have a ASUS 64 bit board and cpu spare so was considering using these t> with amd64 version. But due to the data centre being 300 mile away i t> thought i would check how you guys are finding it first :). Or shall i t> play it safe and use the i386 i just can't decide Do check if your board has any 'known issues': http://www.freebsd.org/platforms/amd64/motherboards.html -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 07:13:10 2006 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 8B31116A420; Thu, 23 Feb 2006 07:13:10 +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 0E29F43D45; Thu, 23 Feb 2006 07:13:09 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k1N7D8aS052080; Thu, 23 Feb 2006 02:13:08 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k1N7D9vH081097; Thu, 23 Feb 2006 02:13:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D15E87302F; Thu, 23 Feb 2006 02:13:08 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060223071308.D15E87302F@freebsd-current.sentex.ca> Date: Thu, 23 Feb 2006 02:13:08 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [releng_6 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: Thu, 23 Feb 2006 07:13:10 -0000 TB --- 2006-02-23 05:24:02 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-02-23 05:24:02 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2006-02-23 05:24:02 - cleaning the object tree TB --- 2006-02-23 05:25:16 - checking out the source tree TB --- 2006-02-23 05:25:16 - cd /tinderbox/RELENG_6/amd64/amd64 TB --- 2006-02-23 05:25:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2006-02-23 05:48:32 - building world (CFLAGS=-O2 -pipe) TB --- 2006-02-23 05:48:32 - cd /src TB --- 2006-02-23 05:48:32 - /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 [...] gzip -cn /src/share/man/man9/disk.9 > disk.9.gz gzip -cn /src/share/man/man9/domain.9 > domain.9.gz gzip -cn /src/share/man/man9/driver.9 > driver.9.gz gzip -cn /src/share/man/man9/DRIVER_MODULE.9 > DRIVER_MODULE.9.gz gzip -cn /src/share/man/man9/EVENTHANDLER.9 > EVENTHANDLER.9.gz gzip -cn /src/share/man/man9/extattr.9 > extattr.9.gz gzip -cn /src/share/man/man9/fetch.9 > fetch.9.gz make: don't know how to make firmware.9. Stop *** Error code 2 Stop in /src/share/man. *** Error code 1 Stop in /src/share. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-02-23 07:13:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-02-23 07:13:07 - ERROR: failed to build world TB --- 2006-02-23 07:13:07 - tinderbox aborted TB --- 1.30 user 6.69 system 6545.28 real From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 12:15:35 2006 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 44AD616A420 for ; Thu, 23 Feb 2006 12:15:35 +0000 (GMT) (envelope-from g_glasson@jimali.dyndns.org) Received: from londo.jimali.dyndns.org (203.161.105.192.dyn.amnet.net.au [203.161.105.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id B228B43D45 for ; Thu, 23 Feb 2006 12:15:34 +0000 (GMT) (envelope-from g_glasson@jimali.dyndns.org) Received: from londo (londo [192.168.1.10]) by londo.jimali.dyndns.org (Postfix) with ESMTP id D7887D5D6DC for ; Thu, 23 Feb 2006 20:15:32 +0800 (WST) From: Geoff Glasson To: freebsd-amd64@freebsd.org Date: Thu, 23 Feb 2006 20:15:31 +0800 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200602232015.32104.g_glasson@jimali.dyndns.org> Subject: Strange problem with Panasonic DVD RW drive 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, 23 Feb 2006 12:15:35 -0000 Hi, I'm having a really strange problem with my DVD drive in my Athlon64 X2 box, in that I'm unable to mount a CDROM because the machine thinks there is a hardware error. The strange thing is, that this failure is dependent upon the mode in which I boot the machine. For example, if I boot my machine with the CD in the drive, the machine reads the disc and boots quite happily from the CD. If I boot the machine without the CD into safe mode, I'm able to manually mount the CD and read it, however if I boot my machine normally I cannot mount the CD and mount reports the following error "mount_cd9660: /dev/acd0: Input/output error". dmesg reports : "Trying to mount root from ufs:/dev/ad12s1a acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 error=0 g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5" In all cases, the same FreeBSD AMD RC1 boot disc is used, so I know the disc is OK. Has anyone else seen this type of problem? Any ideas how to resolve it? Is there any difference between the default boot mode and safe mode that is likely to cause this problem? Thanks...Geoff uname -a FreeBSD londo.jimali.dyndns.org 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #3: Wed Feb 22 05:59:30 WST 2006 root@:/usr/obj/usr/src/sys/SMP amd64 -- Geoff Glasson E-mail: g_glasson@jimali.dyndns.org MSN: g_glasson@wiredcity.com.au From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 12:16:26 2006 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 2C00916A420 for ; Thu, 23 Feb 2006 12:16:26 +0000 (GMT) (envelope-from andrew@areilly.bpc-users.org) Received: from omta05sl.mx.bigpond.com (omta05sl.mx.bigpond.com [144.140.93.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F84043D45 for ; Thu, 23 Feb 2006 12:16:24 +0000 (GMT) (envelope-from andrew@areilly.bpc-users.org) Received: from omtas01sl.mx.bigpond.com ([141.168.4.160]) by omta05sl.mx.bigpond.com with ESMTP id <20060223121623.NQQI18888.omta05sl.mx.bigpond.com@omtas01sl.mx.bigpond.com> for ; Thu, 23 Feb 2006 12:16:23 +0000 Received: from areilly.bpc-users.org ([141.168.4.160]) by omtas01sl.mx.bigpond.com (InterMail vG.2.01.00.00 201-2161-114-101-20050713) with ESMTP id <20060223121105.PZSB22076.omtas01sl.mx.bigpond.com@areilly.bpc-users.org> for ; Thu, 23 Feb 2006 12:11:05 +0000 Received: (qmail 59984 invoked by uid 501); 23 Feb 2006 12:16:31 -0000 Date: Thu, 23 Feb 2006 23:16:31 +1100 From: Andrew Reilly To: Joseph Koshy Message-ID: <20060223121631.GA59890@gurney.reilly.home> References: <43FCEF9C.5050308@bluelight.org.uk> <84dead720602222227g5dcdf987v16cc47f885b0c6a1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84dead720602222227g5dcdf987v16cc47f885b0c6a1@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at omtas01sl.mx.bigpond.com from [138.217.183.75] using ID topazbpm_qldc_mss02ps@bigpond.com at Thu, 23 Feb 2006 11:49:05 +0000 Cc: Terry , freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 12:16:26 -0000 On Thu, Feb 23, 2006 at 11:57:02AM +0530, Joseph Koshy wrote: > t> I have a ASUS 64 bit board and cpu spare so was considering using these > t> with amd64 version. But due to the data centre being 300 mile away i > t> thought i would check how you guys are finding it first :). Or shall i > t> play it safe and use the i386 i just can't decide > > Do check if your board has any 'known issues': > > http://www.freebsd.org/platforms/amd64/motherboards.html Things are improving pretty rapidly, though. I note that that list says that my motherboard (GA-K8NF-9) on-board ethernet doesn't work (it's an nve). Well, with 6-STABLE as of a few weeks ago, it "worked", but seemed to lose interrupts pretty regularly (with an X2 in dual-core mode), and so go into a time-out mode. In my experience, it would always pull out of that and keep going, but the whole-system pause of a few seconds was painful, so I'm running a plug-in ethernet card at the moment. I expect this problem to go away with time. My current main bug bear (not a big one) is that there isn't much third-party driver support for the AMD64 version, yet. My Nvidia graphics card is currently running the xorg vesa driver because (a) the xorg nv driver doesn't always initialize it properly and (b) NVidia themselves only do FreeBSD-i386. My OSS sound card driver only starts in single-processor mode. At least they produce an AMD version. I could get around all of this by running in i386 mode, but part of the point of this system is to play with the amd64 instruction set... The OS itself works beautifully. For all the comments about SATA-RAID, well, that may be a problem, but I'm running a pair of SATA disks and using ccd to stripe the main (non-boot) partitions together, and it works a bomb. Cheers, -- Andrew From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 12:32:49 2006 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 88FD616A420 for ; Thu, 23 Feb 2006 12:32:49 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57E4443D55 for ; Thu, 23 Feb 2006 12:32:48 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id 574F517208; Thu, 23 Feb 2006 14:32:46 +0200 (EET) Date: Thu, 23 Feb 2006 14:32:46 +0200 From: Ion-Mihai Tetcu To: Geoff Glasson Message-ID: <20060223143246.54af75e7@it.buh.tecnik93.com> In-Reply-To: <200602232015.32104.g_glasson@jimali.dyndns.org> References: <200602232015.32104.g_glasson@jimali.dyndns.org> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Strange problem with Panasonic DVD RW drive 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, 23 Feb 2006 12:32:49 -0000 On Thu, 23 Feb 2006 20:15:31 +0800 Geoff Glasson wrote: > Hi, > > I'm having a really strange problem with my DVD drive in my Athlon64 > X2 box, in that I'm unable to mount a CDROM because the machine > thinks there is a hardware error. The strange thing is, that this > failure is dependent upon the mode in which I boot the machine. > > For example, if I boot my machine with the CD in the drive, the > machine reads the disc and boots quite happily from the CD. If I > boot the machine without the CD into safe mode, I'm able to manually > mount the CD and read it, however if I boot my machine normally I > cannot mount the CD and mount reports the following error > "mount_cd9660: /dev/acd0: Input/output error". > > dmesg reports : > "Trying to mount root from ufs:/dev/ad12s1a > acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x08 ascq=0x03 error=0 > g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5" > > In all cases, the same FreeBSD AMD RC1 boot disc is used, so I know > the disc is OK. > > Has anyone else seen this type of problem? Any ideas how to resolve > it? Is there any difference between the default boot mode and safe > mode that is likely to cause this problem? In safe mode you have hw.ata.atapi_dma=0. Try setting it to 0 at loader prompt and boot -v and see if you can mount the CD. Try changing the cable anyway. What MB/chip-set ? -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" Ferengi Rule of Acquisition #189: Let others keep their reputation. You keep their latinum. -- ST: Legends of the Ferengi From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 13:06:07 2006 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 33D2116A420 for ; Thu, 23 Feb 2006 13:06:07 +0000 (GMT) (envelope-from g_glasson@jimali.dyndns.org) Received: from londo.jimali.dyndns.org (203.161.105.192.dyn.amnet.net.au [203.161.105.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2BE443D46 for ; Thu, 23 Feb 2006 13:06:06 +0000 (GMT) (envelope-from g_glasson@jimali.dyndns.org) Received: from londo (londo [192.168.1.10]) by londo.jimali.dyndns.org (Postfix) with ESMTP id 6EFACD5D746; Thu, 23 Feb 2006 21:06:05 +0800 (WST) From: Geoff Glasson To: Ion-Mihai Tetcu Date: Thu, 23 Feb 2006 21:06:04 +0800 User-Agent: KMail/1.9.1 References: <200602232015.32104.g_glasson@jimali.dyndns.org> <20060223143246.54af75e7@it.buh.tecnik93.com> In-Reply-To: <20060223143246.54af75e7@it.buh.tecnik93.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602232106.04875.g_glasson@jimali.dyndns.org> Cc: freebsd-amd64@freebsd.org Subject: Re: Strange problem with Panasonic DVD RW drive 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, 23 Feb 2006 13:06:07 -0000 On Thursday 23 February 2006 20:32, Ion-Mihai Tetcu wrote: > On Thu, 23 Feb 2006 20:15:31 +0800 > > In safe mode you have hw.ata.atapi_dma=0. Try setting it to 0 at loader > prompt and boot -v and see if you can mount the CD. Try changing the > cable anyway. > > What MB/chip-set ? Thanks for the quick response. Turning off DMA has had the desired effect. FYI: I have an ASUS A8N-SLI Deluxe motherboard with AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2010.31-MHz K8-class CPU). Regards...Geoff -- Geoff Glasson E-mail: g_glasson@jimali.dyndns.org MSN: g_glasson@wiredcity.com.au From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 13:38:40 2006 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 B717916A420 for ; Thu, 23 Feb 2006 13:38:40 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B2BF43D48 for ; Thu, 23 Feb 2006 13:38:40 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id E631017207; Thu, 23 Feb 2006 15:38:38 +0200 (EET) Date: Thu, 23 Feb 2006 15:38:38 +0200 From: Ion-Mihai Tetcu To: Geoff Glasson Message-ID: <20060223153838.0421ff8c@it.buh.tecnik93.com> In-Reply-To: <200602232106.04875.g_glasson@jimali.dyndns.org> References: <200602232015.32104.g_glasson@jimali.dyndns.org> <20060223143246.54af75e7@it.buh.tecnik93.com> <200602232106.04875.g_glasson@jimali.dyndns.org> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Strange problem with Panasonic DVD RW drive 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, 23 Feb 2006 13:38:40 -0000 On Thu, 23 Feb 2006 21:06:04 +0800 Geoff Glasson wrote: > On Thursday 23 February 2006 20:32, Ion-Mihai Tetcu wrote: > > On Thu, 23 Feb 2006 20:15:31 +0800 > > > > > > In safe mode you have hw.ata.atapi_dma=0. Try setting it to 0 at > > loader prompt and boot -v and see if you can mount the CD. Try > > changing the cable anyway. > > > > What MB/chip-set ? > > Thanks for the quick response. Turning off DMA has had the desired > effect. Heh. What about the cable ? > FYI: I have an ASUS A8N-SLI Deluxe motherboard with AMD Athlon(tm) 64 > X2 Dual Core Processor 3800+ (2010.31-MHz K8-class CPU). I have the Premium variant and I don't have this problem with an ASUS DRW-1608P -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #290: The CPU has shifted, and become decentralized From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 13:40:42 2006 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 C217216A420 for ; Thu, 23 Feb 2006 13:40:42 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id E544043D80 for ; Thu, 23 Feb 2006 13:40:30 +0000 (GMT) (envelope-from itetcu@people.tecnik93.com) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id 77E1D17208; Thu, 23 Feb 2006 15:40:29 +0200 (EET) Date: Thu, 23 Feb 2006 15:40:29 +0200 From: Ion-Mihai Tetcu To: Ion-Mihai Tetcu Message-ID: <20060223154029.777a757b@it.buh.tecnik93.com> In-Reply-To: <20060223153838.0421ff8c@it.buh.tecnik93.com> References: <200602232015.32104.g_glasson@jimali.dyndns.org> <20060223143246.54af75e7@it.buh.tecnik93.com> <200602232106.04875.g_glasson@jimali.dyndns.org> <20060223153838.0421ff8c@it.buh.tecnik93.com> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org, Geoff Glasson Subject: Re: Strange problem with Panasonic DVD RW drive 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, 23 Feb 2006 13:40:42 -0000 On Thu, 23 Feb 2006 15:38:38 +0200 Ion-Mihai Tetcu wrote: > On Thu, 23 Feb 2006 21:06:04 +0800 > Geoff Glasson wrote: > > > On Thursday 23 February 2006 20:32, Ion-Mihai Tetcu wrote: > > > On Thu, 23 Feb 2006 20:15:31 +0800 > > > > > > > > > > In safe mode you have hw.ata.atapi_dma=0. Try setting it to 0 at > > > loader prompt and boot -v and see if you can mount the CD. Try > > > changing the cable anyway. > > > > > > What MB/chip-set ? > > > > Thanks for the quick response. Turning off DMA has had the desired > > effect. > > Heh. What about the cable ? > > > FYI: I have an ASUS A8N-SLI Deluxe motherboard with AMD Athlon(tm) > > 64 X2 Dual Core Processor 3800+ (2010.31-MHz K8-class CPU). > > I have the Premium variant and I don't have this problem with an ASUS > DRW-1608P At least in i386 mode in which I am right now (also I have a 3200+ single core CPU). -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #170: popper unable to process jumbo kernel From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 14:23:36 2006 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 05DE216A420 for ; Thu, 23 Feb 2006 14:23:36 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (mail.wmptl.com [216.8.159.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53EC243D45 for ; Thu, 23 Feb 2006 14:23:32 +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.4/8.13.4) with ESMTP id k1NENPZM042120; Thu, 23 Feb 2006 09:23:25 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <43FDC54D.5030008@wmptl.com> Date: Thu, 23 Feb 2006 09:23:09 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Terry References: <43FCEF9C.5050308@bluelight.org.uk> In-Reply-To: <43FCEF9C.5050308@bluelight.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.54 on 10.0.0.80 Cc: amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 14:23:36 -0000 Terry wrote: > I need to build a new server to send down to the data centre for hosting > and possible game server type stuff. > I have a ASUS 64 bit board and cpu spare so was considering using these > with amd64 version. But due to the data centre being 300 mile away i > thought i would check how you guys are finding it first :). Or shall i > play it safe and use the i386 i just can't decide > > Ter > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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" I have been running the AMD64 branch for well into a year now. I've noted considerable issues while attempting to use AMD64 for a desktop, and would therefore not reccomend it for desktop use, (note some other replies mentioning nvidia driver, sound, raid, netcard, etc issues). That being said, as a server - it's rock solid. We're running single and dual AMD Opteron boxen here, with 2+ gigs of ECC RAM. Accross the board we're standardized on 3Ware 9000-Series Escalades and Western Digital 'SD' (RAID-Edition) drives. These machines run OpenLDAP, MySQL, samba, Apache+mod_perl, Apache+mod_ssl, and a myriad of home-built applications written in Perl and C. Baring some issues with nss_ldap, and more specifically the OpenLDAP libs prior to 2.2.x branch under FreeBSD 5.4/amd64... we've had no performance nor stability issues. All the servers here authenticate using nss_ldap, and pam_ldap to a central account server, which is something relatively new to FreeBSD in general (nss_ldap, pam_ldap only been able to work with FreeBSD reliably since the 5.x branches) - so I suspect our troubles even still were not amd64 specific. I've got servers here running 100+ days of uptime, running 6.0/amd64 with SMP and booting from RAID volumes with NO issues. To me, that's as stable as I need to be. I've got some colocated stuff too, but the hardware is i386, so as-is the O/S... -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 14:55:39 2006 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 7A28E16A420 for ; Thu, 23 Feb 2006 14:55:39 +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 0B1FA43D55 for ; Thu, 23 Feb 2006 14:55:38 +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 E23AAB80D for ; Thu, 23 Feb 2006 09:55:37 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <43FD3B83.2040109@rtl.fmailbox.com> References: <43FCEF9C.5050308@bluelight.org.uk> <43FD3B83.2040109@rtl.fmailbox.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 23 Feb 2006 09:55:37 -0500 To: FreeBSD AMD list X-Mailer: Apple Mail (2.746.2) Subject: Re: AMD 64 stability 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, 23 Feb 2006 14:55:39 -0000 On Feb 22, 2006, at 11:35 PM, Robert Leftwich wrote: > Be wary of FreeBSD's AMD64 support - test, test again and do even > more testing before the box leaves your sight! my experience: On the following it has been rock solid: Dell PE1850, Dell PE800 (though in 6.0 and up ACPI locks up at boot), Dell PE1425 (in testing still), Sun X4100 dual CPU. The Dells are Intel EM64T and the Sun is true Opteron. On the following it has been hit-or-miss: generic systems based on Tyan S2881 with Dual Opteron CPU. I went through 6 motherboards in 4 physically different systems and exacly one has been stable, though I'm afraid to reboot it. And just because your data center is 300 miles away doens't mean you can't manage it. Just hook up a serial console to a terminal server like a Cyclades box (or daisy-chain serial port amongst the other servers there) and ensure your kernel has the debugger enabled so you can control it even if it seems to hang on boot. All of the systems I use also route BIOS POST messages to the serial port. The Sun is best at it, allowing ctrl keys to control the functions. The dell's require appropriate terminal emulation of F keys. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 15:38:52 2006 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 7D48916A420 for ; Thu, 23 Feb 2006 15:38:52 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from mail.dc-servers.com (mail.dc-servers.com [83.243.101.206]) by mx1.FreeBSD.org (Postfix) with SMTP id C881B43D4C for ; Thu, 23 Feb 2006 15:38:50 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: (qmail 23700 invoked by uid 399); 23 Feb 2006 15:38:52 -0000 Received: from unknown (HELO alfie.jigsawhq.com) (work@ashleymoran.me.uk@213.106.224.113) by mail.dc-servers.com with SMTP; 23 Feb 2006 15:38:52 -0000 From: Ashley Moran Organization: Codeweavers Ltd To: freebsd-amd64@freebsd.org Date: Thu, 23 Feb 2006 15:37:31 +0000 User-Agent: KMail/1.9.1 References: <43FCEF9C.5050308@bluelight.org.uk> In-Reply-To: <43FCEF9C.5050308@bluelight.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602231537.31325.work@ashleymoran.me.uk> Cc: Terry Subject: Re: AMD 64 stability 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, 23 Feb 2006 15:38:52 -0000 On Wednesday 22 February 2006 23:11, Terry wrote: > I have a ASUS 64 bit board and cpu spare so was considering using these > with amd64 version. But due to the data centre being 300 mile away i > thought i would check how you guys are finding it first :). Or shall i > play it safe and use the i386 i just can't decide I've got a server based around an A8V Deluxe. Runs abolutely great, SATA RAID and everything. Postgres flies on it. Getting Java running in the last couple of days was a pain, but that is down to i386 emulation issues. Not had any other problems at all. I'm so pleased with it I simply won't buy another server that won't run FreeBSD/amd64 natively - although currently that does mean it can take longer to find a compatible server than to actually install it. Ashley From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 16:05:40 2006 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 968AD16A420 for ; Thu, 23 Feb 2006 16:05:40 +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 2BF0243D64 for ; Thu, 23 Feb 2006 16:05:36 +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 86773F811 for ; Thu, 23 Feb 2006 09:05:35 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 4EE51F80F for ; Thu, 23 Feb 2006 09:05:35 -0700 (MST) Date: Thu, 23 Feb 2006 09:05:34 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060223090534.065f3cd1.kgunders@teamcool.net> In-Reply-To: References: <43FCEF9C.5050308@bluelight.org.uk> <43FD3B83.2040109@rtl.fmailbox.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: AMD 64 stability 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, 23 Feb 2006 16:05:40 -0000 On Thu, 23 Feb 2006 09:55:37 -0500 Vivek Khera wrote: > > On Feb 22, 2006, at 11:35 PM, Robert Leftwich wrote: > > > Be wary of FreeBSD's AMD64 support - test, test again and do even > > more testing before the box leaves your sight! > > my experience: > > On the following it has been rock solid: Dell PE1850, Dell PE800 > (though in 6.0 and up ACPI locks up at boot), Dell PE1425 (in testing > still), Sun X4100 dual CPU. The Dells are Intel EM64T and the Sun is > true Opteron. > Did you ever test drive the x2100?? > On the following it has been hit-or-miss: generic systems based on > Tyan S2881 with Dual Opteron CPU. I went through 6 motherboards in 4 > physically different systems and exacly one has been stable, though > I'm afraid to reboot it. > I have a few Tyan Transport TA26's wh/ use the S2882 board. The one MAJOR PITA issue I had w/them is w/LSI 320-1 MegaRAID cards. A mirror using "slot 1" degrades under moderate load and cannot be recovered. The problem goes away w/320-2x. Tyan and LSI are investigating. Tyan reports "unable to reproduce/no problem found". Right.... LSI support, by contrast, rocks and they are investigating further. > And just because your data center is 300 miles away doens't mean you > can't manage it. Just hook up a serial console to a terminal server > like a Cyclades box (or daisy-chain serial port amongst the other > servers there) and ensure your kernel has the debugger enabled so you > can control it even if it seems to hang on boot. > Or an IPMI card.... > All of the systems I use also route BIOS POST messages to the serial > port. The Sun is best at it, allowing ctrl keys to control the > functions. The dell's require appropriate terminal emulation of F keys. Doesn't the Sun use a Tyan board? -- 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 Feb 23 16:28:25 2006 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 46C0B16A420 for ; Thu, 23 Feb 2006 16:28:25 +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 E696A43D46 for ; Thu, 23 Feb 2006 16:28:24 +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 3C502B80D for ; Thu, 23 Feb 2006 11:28:24 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <20060223090534.065f3cd1.kgunders@teamcool.net> References: <43FCEF9C.5050308@bluelight.org.uk> <43FD3B83.2040109@rtl.fmailbox.com> <20060223090534.065f3cd1.kgunders@teamcool.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 23 Feb 2006 11:28:23 -0500 To: FreeBSD AMD list X-Mailer: Apple Mail (2.746.2) Subject: Re: AMD 64 stability 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, 23 Feb 2006 16:28:25 -0000 On Feb 23, 2006, at 11:05 AM, Ken Gunderson wrote: >> still), Sun X4100 dual CPU. The Dells are Intel EM64T and the Sun is >> true Opteron. >> > > Did you ever test drive the x2100?? > no, but someone posted to me the dmesg from an X2100 and it seems everything worked ok. however one of the onboard ethernet is nvidia so that could cause problems if you needed both like I do. > I have a few Tyan Transport TA26's wh/ use the S2882 board. The one > MAJOR PITA issue I had w/them is w/LSI 320-1 MegaRAID cards. A mirror > using "slot 1" degrades under moderate load and cannot be recovered. > The problem goes away w/320-2x. Tyan and LSI are investigating. Tyan > reports "unable to reproduce/no problem found". Right.... LSI > support, by contrast, rocks and they are investigating further. > interesting.... I have a 320-2x card I wanted to use with the X4100, except it doesn't fit the low-profile slot that it has. So I tried it in a Dell 1425SC server... it reports random failures at different times on different disks on two different Dell powervault arrays which otherwise work flawlessly with an Adaptec 2230SLP card. If I run the 320-2X in Ultra 160 mode it has no complaints but that is stupid.... Of course everyone points the finger at everyone else... and I'm stuck in the middle with a bunch of expensive crap that won't work together. Anyhow.... I just (literally 15 minutes ago) got an IBM e326m evaluation unit. Watch for results shortly on that... I hope the 320-2x works fine with this box. > Doesn't the Sun use a Tyan board? It is based on a Tyan design, but significantly modified. The X4100 (and other X series) has no internal cables. Everything is plugged together more or less directly. There is one small flat 4" long ribbon cable hooking up something, but that's it. It is absolutely amazingly engineered. They also seem to have better QC than the OEM boards. However, the BIOS comes configured stupidly -- you have to turn on some options to make it bypass the BIOS 4GB hole, etc. Why not just do that by default?!?!?!!?!?!?!?!?!? From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 17:38:00 2006 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 2B69416A420 for ; Thu, 23 Feb 2006 17:38:00 +0000 (GMT) (envelope-from vayua@sklinks.com) Received: from smtp104.sbc.mail.re2.yahoo.com (smtp104.sbc.mail.re2.yahoo.com [68.142.229.101]) by mx1.FreeBSD.org (Postfix) with SMTP id 99C5B43D48 for ; Thu, 23 Feb 2006 17:37:59 +0000 (GMT) (envelope-from vayua@sklinks.com) Received: (qmail 80556 invoked from network); 23 Feb 2006 17:37:59 -0000 Received: from unknown (HELO akasha.akasha) (varuna@sbcglobal.net@69.229.158.197 with plain) by smtp104.sbc.mail.re2.yahoo.com with SMTP; 23 Feb 2006 17:37:58 -0000 From: Vayu To: freebsd-amd64@freebsd.org Date: Thu, 23 Feb 2006 09:37:44 -0800 User-Agent: KMail/1.9.1 References: <43FCEF9C.5050308@bluelight.org.uk> <200602231537.31325.work@ashleymoran.me.uk> In-Reply-To: <200602231537.31325.work@ashleymoran.me.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602230937.44464.vayua@sklinks.com> Cc: Terry Subject: Re: AMD 64 stability 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, 23 Feb 2006 17:38:00 -0000 On Thursday 23 February 2006 07:37, Ashley Moran wrote: > On Wednesday 22 February 2006 23:11, Terry wrote: > > I have a ASUS 64 bit board and cpu spare so was considering using these > > with amd64 version. But due to the data centre being 300 mile away i > > thought i would check how you guys are finding it first :). Or shall i > > play it safe and use the i386 i just can't decide > > I've got a server based around an A8V Deluxe. Runs abolutely great, SATA > RAID and everything. Postgres flies on it. Getting Java running in the > last couple of days was a pain, but that is down to i386 emulation issues. > Not had any other problems at all. > > I'm so pleased with it I simply won't buy another server that won't run > FreeBSD/amd64 natively - although currently that does mean it can take > longer to find a compatible server than to actually install it. > > Ashley > _______________________________________________ Based on the hardware compatibility list I decided to use that board for my new computer. It seems to be on its way out availabilitywise. I could not find it locally. I ended up with a plain A8V, which appears to be the same without firewire. It works great. From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 18:26:19 2006 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 62C6416A420 for ; Thu, 23 Feb 2006 18:26:19 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 687EB43D46 for ; Thu, 23 Feb 2006 18:26:18 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail02.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1NIQGS2030691 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 24 Feb 2006 05:26:16 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1NIQGWk002831 for ; Fri, 24 Feb 2006 05:26:16 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1NIQGdU002830 for freebsd-amd64@freebsd.org; Fri, 24 Feb 2006 05:26:16 +1100 (EST) (envelope-from peter) Date: Fri, 24 Feb 2006 05:26:16 +1100 From: Peter Jeremy To: freebsd-amd64@freebsd.org Message-ID: <20060223182616.GA2811@turion.vk2pj.dyndns.org> References: <20060219091907.GA738@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060219091907.GA738@turion.vk2pj.dyndns.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Subject: Re: Hard hang using powerd 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, 23 Feb 2006 18:26:19 -0000 On Sun, 2006-Feb-19 20:19:07 +1100, Peter Jeremy wrote: >I have an HP nx6125, running about a two week old 6-stable/amd64 and >I've found that powerd causes random hard hangs (no response to >anything except holding the power-switch down for an extended period). >This occurs with both cpufreq and raw acpi frequency control. FWIW, this occurs with a two-day old -current as well. -- Peter Jeremy From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 18:31:29 2006 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 17FE416A420 for ; Thu, 23 Feb 2006 18:31:29 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A62143D4C for ; Thu, 23 Feb 2006 18:31:28 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FCLFQ-0002K4-2H for freebsd-amd64@freebsd.org; Thu, 23 Feb 2006 19:31:28 +0100 Message-ID: <43FE010F.8040501@datafarm.de> Date: Thu, 23 Feb 2006 19:38:07 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <43FCEF9C.5050308@bluelight.org.uk> <200602231537.31325.work@ashleymoran.me.uk> <200602230937.44464.vayua@sklinks.com> In-Reply-To: <200602230937.44464.vayua@sklinks.com> Content-Type: text/plain; charset=ISO-8859-6; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AMD 64 stability 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, 23 Feb 2006 18:31:29 -0000 Since the original question was related to 'server' usage... the compatibilty list tells if the components found on a single board (along with its BIOS) are supported. It doesn't statethat a specific combination or future setup will work. For example, we just had to find out that iir-based icp controllers work extraordinarily fine as long as <4G RAM are used. Upgrading memory beyond 4G turns your big server(s) into one really big problem. I just filed a bug report. So before taking decision for software/hardware that is expected to run hundreds of miles away, it would be reasonable to also take system changes into account that may be planned for the future. My $0.02 vt From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 18:38:45 2006 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 B263A16A420 for ; Thu, 23 Feb 2006 18:38:45 +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 3332343D6E for ; Thu, 23 Feb 2006 18:38:41 +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 5B520F811 for ; Thu, 23 Feb 2006 11:38:41 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 22F83F805 for ; Thu, 23 Feb 2006 11:38:41 -0700 (MST) Date: Thu, 23 Feb 2006 11:38:40 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060223113840.78b0a1c2.kgunders@teamcool.net> In-Reply-To: <43FE010F.8040501@datafarm.de> References: <43FCEF9C.5050308@bluelight.org.uk> <200602231537.31325.work@ashleymoran.me.uk> <200602230937.44464.vayua@sklinks.com> <43FE010F.8040501@datafarm.de> 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: AMD 64 stability 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, 23 Feb 2006 18:38:45 -0000 On Thu, 23 Feb 2006 19:38:07 +0100 "V. T. Mueller" wrote: > > Since the original question was related to 'server' usage... the > compatibilty list tells if the components found on a single board > (along with its BIOS) are supported. It doesn't statethat a specific > combination or future setup will work. > > For example, we just had to find out that iir-based icp controllers > work extraordinarily fine as long as <4G RAM are used. Upgrading > memory beyond 4G turns your big server(s) into one really big problem. > > I just filed a bug report. > > So before taking decision for software/hardware that is expected to > run hundreds of miles away, it would be reasonable to also take > system changes into account that may be planned for the future. This in reference to the A8V?? -- 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 Feb 23 18:46:29 2006 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 8A3F516A422 for ; Thu, 23 Feb 2006 18:46:29 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 268D543D46 for ; Thu, 23 Feb 2006 18:46:29 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FCLTx-0002QM-4J; Thu, 23 Feb 2006 19:46:29 +0100 Message-ID: <43FE048F.7030702@datafarm.de> Date: Thu, 23 Feb 2006 19:53:03 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <43FCEF9C.5050308@bluelight.org.uk> <200602231537.31325.work@ashleymoran.me.uk> <200602230937.44464.vayua@sklinks.com> <43FE010F.8040501@datafarm.de> <20060223113840.78b0a1c2.kgunders@teamcool.net> In-Reply-To: <20060223113840.78b0a1c2.kgunders@teamcool.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 18:46:29 -0000 Ken Gunderson schrieb: > On Thu, 23 Feb 2006 19:38:07 +0100 > "V. T. Mueller" wrote: > > >>Since the original question was related to 'server' usage... the >>compatibilty list tells if the components found on a single board >>(along with its BIOS) are supported. It doesn't statethat a specific >>combination or future setup will work. >> >>For example, we just had to find out that iir-based icp controllers >>work extraordinarily fine as long as <4G RAM are used. Upgrading >>memory beyond 4G turns your big server(s) into one really big problem. >> >>I just filed a bug report. >> >>So before taking decision for software/hardware that is expected to >>run hundreds of miles away, it would be reasonable to also take >>system changes into account that may be planned for the future. > > > This in reference to the A8V?? Depends. My point is that you'll find plenty of boards that'll work fine. How many chipsets are out there for Athlon64/Opteron? The real problems lurk in the higher number of supplemental drivers (that are maybe) needed for addon-hardware. Cheers, vt From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 18:50:51 2006 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 6966416A420 for ; Thu, 23 Feb 2006 18:50:51 +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 B944A43D49 for ; Thu, 23 Feb 2006 18:50:50 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k1NIomAn032334 for ; Thu, 23 Feb 2006 15:50:49 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Thu, 23 Feb 2006 15:50:46 -0300 User-Agent: KMail/1.9.1 References: <43FCEF9C.5050308@bluelight.org.uk> <20060223113840.78b0a1c2.kgunders@teamcool.net> <43FE048F.7030702@datafarm.de> In-Reply-To: <43FE048F.7030702@datafarm.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602231550.48331.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: AMD 64 stability 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, 23 Feb 2006 18:50:51 -0000 On Thursday 23 February 2006 15:53, V. T. Mueller wrote: > Ken Gunderson schrieb: > >> > >>For example, we just had to find out that iir-based icp controllers > >>work extraordinarily fine as long as <4G RAM are used. Upgrading > >>memory beyond 4G turns your big server(s) into one really big problem. > >> > > > > This in reference to the A8V?? > > Depends. My point is that you'll find plenty of boards that'll work > fine. How many chipsets are out there for Athlon64/Opteron? The real > problems lurk in the higher number of supplemental drivers (that are > maybe) needed for addon-hardware. > depends on the hardware only, that has nothing to do with the software or=20 dirver most MBs on the compatibility list do not support > 4GB=20 especially the A8V max is 4GB 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 Thu Feb 23 19:06:38 2006 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 4251516A420 for ; Thu, 23 Feb 2006 19:06:38 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4B0243D4C for ; Thu, 23 Feb 2006 19:06:37 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FCLnR-0002Ws-Ti; Thu, 23 Feb 2006 20:06:37 +0100 Message-ID: <43FE094A.8030302@datafarm.de> Date: Thu, 23 Feb 2006 20:13:14 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: JoaoBR References: <43FCEF9C.5050308@bluelight.org.uk> <20060223113840.78b0a1c2.kgunders@teamcool.net> <43FE048F.7030702@datafarm.de> <200602231550.48331.joao@matik.com.br> In-Reply-To: <200602231550.48331.joao@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 19:06:38 -0000 JoaoBR schrieb: > On Thursday 23 February 2006 15:53, V. T. Mueller wrote: >>Ken Gunderson schrieb: >>>>For example, we just had to find out that iir-based icp controllers >>>>work extraordinarily fine as long as <4G RAM are used. Upgrading >>>>memory beyond 4G turns your big server(s) into one really big problem. >>>This in reference to the A8V?? >>Depends. My point is that you'll find plenty of boards that'll work >>fine. How many chipsets are out there for Athlon64/Opteron? The real >>problems lurk in the higher number of supplemental drivers (that are >>maybe) needed for addon-hardware. > depends on the hardware only, that has nothing to do with the software or > dirver > most MBs on the compatibility list do not support > 4GB > especially the A8V max is 4GB I was relating to "server usage", as stated in the first sentence of my original email - which you decided not to quote. Of course the A8V is no server board. So the limitations by design will prevent a couple of pitfalls that were otherwise possible. If the original poster is going to buy a server board/system, he should carefully collect information regarding the whole environment he is about to set up. Besides, you should take a look on the compatibilty list again, counting the number of server boards with chipsets that can address up to 32 GB of RAM ;) Cheers, vt From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 23 22:45:37 2006 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 C501316A420 for ; Thu, 23 Feb 2006 22:45:37 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D5C943D48 for ; Thu, 23 Feb 2006 22:45:37 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [IPv6:2001:980:ffe:3:a00:20ff:fe85:fa39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id A51DCBDBC; Thu, 23 Feb 2006 23:45:34 +0100 (CET) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id DAC0021B; Thu, 23 Feb 2006 23:45:33 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id C0102213; Thu, 23 Feb 2006 23:45:33 +0100 (CET) Date: Thu, 23 Feb 2006 23:45:33 +0100 (CET) From: Sten Spans To: "V. T. Mueller" In-Reply-To: <43FE094A.8030302@datafarm.de> Message-ID: References: <43FCEF9C.5050308@bluelight.org.uk> <20060223113840.78b0a1c2.kgunders@teamcool.net> <43FE048F.7030702@datafarm.de> <200602231550.48331.joao@matik.com.br> <43FE094A.8030302@datafarm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 23 Feb 2006 22:45:37 -0000 On Thu, 23 Feb 2006, V. T. Mueller wrote: > > I was relating to "server usage", as stated in the first sentence of my > original email - which you decided not to quote. > > Of course the A8V is no server board. So the limitations by design will > prevent a couple of pitfalls that were otherwise possible. If the original > poster is going to buy a server board/system, he should carefully collect > information regarding the whole environment he is about to set up. > > Besides, you should take a look on the compatibilty list again, counting the > number of server boards with chipsets that can address up to 32 GB of RAM ;) Opterons don't use chipsets to access main memory ... The motherbord just needs enough slots and good enough traces to support a fully populated memory bus. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 06:36:09 2006 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 B919B16A420 for ; Fri, 24 Feb 2006 06:36:09 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48C8443D48 for ; Fri, 24 Feb 2006 06:36:09 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 46DD462C87B; Fri, 24 Feb 2006 02:36:08 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 61072-02; Fri, 24 Feb 2006 02:36:08 -0400 (AST) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 3180B62C88A; Fri, 24 Feb 2006 02:13:56 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 26CB039E88; Fri, 24 Feb 2006 02:13:56 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 1FDD334B50; Fri, 24 Feb 2006 02:13:56 -0400 (AST) Date: Fri, 24 Feb 2006 02:13:56 -0400 (AST) From: "Marc G. Fournier" To: ray@redshift.com In-Reply-To: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> Message-ID: <20060224021327.H1005@ganymede.hub.org> References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? 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, 24 Feb 2006 06:36:09 -0000 I run an IIR controller on one of our servers just fine ... 4GB of RAM, FreeBSD 4.x ... haven't tried 6.x on it yet ... On Wed, 22 Feb 2006, ray@redshift.com wrote: > you might want to check with Eren over at OSS (eniazi@ossmail.com) - I don't > think he's on the list, but I know they do a lot with ICP and he may have some > clients using it under FreeBSD. I believe they use 3ware and ICP, so I would > bet they could toss their 2 cents in. > > Just a thought. Hope that helps :) > > ray > > cc: eniazi@ossmail.com > > At 06:40 PM 2/22/2006 +0100, V. T. Mueller wrote: > | > | Hello, > | > | is there anyone here successfully using a raid-controller that's > | supported by iir(4) in a system with >= 4GB RAM? > | > | After a couple of days testing with both GDT8500RZ and GDT8114RZ it > | seems as if the iir driver is broken. Disk access crashes the system > | when there are >=4GB of main memory installed. > | > | I would reall ylike to here that it's a local problem, but with all > | the data collected so far I would also be really surprised to hear so. > | > | If noone convices me that it's working, I will file a bug report > | tomorrow. > | > | Cheers, > | vt > | _______________________________________________ > | 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" > | > | > _______________________________________________ > 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" > > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 06:41:27 2006 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 3494716A420 for ; Fri, 24 Feb 2006 06:41:27 +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 E05F343D45 for ; Fri, 24 Feb 2006 06:41:26 +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 BCC581A3C1C; Thu, 23 Feb 2006 22:41:26 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1CB18515AE; Fri, 24 Feb 2006 01:41:26 -0500 (EST) Date: Fri, 24 Feb 2006 01:41:26 -0500 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060224064125.GA1782@xor.obsecurity.org> References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20060224021327.H1005@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? 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, 24 Feb 2006 06:41:27 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: >=20 > I run an IIR controller on one of our servers just fine ... 4GB of RAM,= =20 > FreeBSD 4.x ... haven't tried 6.x on it yet ... It's known to be broken on any system with >4GB of RAM. Kris >=20 > On Wed, 22 Feb 2006, ray@redshift.com wrote: >=20 > >you might want to check with Eren over at OSS (eniazi@ossmail.com) - I= =20 > >don't > >think he's on the list, but I know they do a lot with ICP and he may hav= e=20 > >some > >clients using it under FreeBSD. I believe they use 3ware and ICP, so I= =20 > >would > >bet they could toss their 2 cents in. > > > >Just a thought. Hope that helps :) > > > >ray > > > >cc: eniazi@ossmail.com > > > >At 06:40 PM 2/22/2006 +0100, V. T. Mueller wrote: > >| > >| Hello, > >| > >| is there anyone here successfully using a raid-controller that's > >| supported by iir(4) in a system with >=3D 4GB RAM? > >| > >| After a couple of days testing with both GDT8500RZ and GDT8114RZ it > >| seems as if the iir driver is broken. Disk access crashes the system > >| when there are >=3D4GB of main memory installed. > >| > >| I would reall ylike to here that it's a local problem, but with all > >| the data collected so far I would also be really surprised to hear so. > >| > >| If noone convices me that it's working, I will file a bug report > >| tomorrow. > >| > >| Cheers, > >| vt > >| _______________________________________________ > >| freebsd-amd64@freebsd.org mailing list > >| http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > >| To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.or= g" > >| > >| > >_______________________________________________ > >freebsd-amd64@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > > >=20 > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.or= g) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 76156= 64 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >=20 --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD/qqVWry0BWjoQKURAhc0AKCkHxBQJy4xHTEbVicSFjuPK8QTVwCg6XSa +tj7t5rJ6aZmBhqEnSkP9Xs= =2Xvb -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 07:55:27 2006 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 47B0F16A422 for ; Fri, 24 Feb 2006 07:55:27 +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 6603043D46 for ; Fri, 24 Feb 2006 07:55:25 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k1O7t8xh063998; Fri, 24 Feb 2006 04:55:08 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: Sten Spans Date: Fri, 24 Feb 2006 04:55:06 -0300 User-Agent: KMail/1.9.1 References: <43FCEF9C.5050308@bluelight.org.uk> <43FE094A.8030302@datafarm.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602240455.07500.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 24 Feb 2006 07:55:27 -0000 On Thursday 23 February 2006 19:45, Sten Spans wrote: > On Thu, 23 Feb 2006, V. T. Mueller wrote: > > > > Besides, you should take a look on the compatibilty list again, counting > > the number of server boards with chipsets that can address up to 32 GB = of > > RAM ;) > > Opterons don't use chipsets to access main memory ... > The motherbord just needs enough slots and good > enough traces to support a fully populated memory bus. nonono how much memory a processor can access is one thing but how much is suppor= ted=20 on the system depends on the motherboard capability so you can not put 96GB= =20 on the board if it supports only 32 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 Fri Feb 24 08:01:29 2006 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 D390916A420 for ; Fri, 24 Feb 2006 08:01:29 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 992A543D4C for ; Fri, 24 Feb 2006 08:01:27 +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 mxfep02.bredband.com with ESMTP id <20060224080126.EXDB29994.mxfep02.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se> for ; Fri, 24 Feb 2006 09:01:26 +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 BEFDD67922 for ; Fri, 24 Feb 2006 09:01:25 +0100 (CET) Message-ID: <43FEBD56.4040200@gneto.com> Date: Fri, 24 Feb 2006 09:01:26 +0100 From: Martin Nilsson User-Agent: Thunderbird 1.5 (X11/20060203) MIME-Version: 1.0 CC: freebsd-amd64@freebsd.org References: <43FCEF9C.5050308@bluelight.org.uk> <20060223113840.78b0a1c2.kgunders@teamcool.net> <43FE048F.7030702@datafarm.de> <200602231550.48331.joao@matik.com.br> <43FE094A.8030302@datafarm.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AMD 64 stability 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, 24 Feb 2006 08:01:29 -0000 Sten Spans wrote: > Opterons don't use chipsets to access main memory ... > The motherbord just needs enough slots and > good enough traces to support a fully populated memory bus. ^^^^^^^^^^^^^^^^^^ And it's here where it usually fails when you fill the board with 2GB modules. The Chinese server-wannabee manufacturers products just can't handle the load that these modules puts on the system. They are very much aware of it, but their tech support never admits that it's their crappy motherboard designs that causes the stability problems, instead the come up with all sorts of strange excuses and finally closes all support requests with: "not able to reproduce here - no fault" /Martin From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 08:24:56 2006 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 8802716A420 for ; Fri, 24 Feb 2006 08:24:56 +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 9BC1243D49 for ; Fri, 24 Feb 2006 08:24:55 +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 k1O8OsKd008553; Fri, 24 Feb 2006 01:24:54 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43FEC2D9.7090407@samsco.org> Date: Fri, 24 Feb 2006 01:24:57 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> In-Reply-To: <20060224064125.GA1782@xor.obsecurity.org> 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: eniazi@ossmail.com, freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? 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, 24 Feb 2006 08:24:56 -0000 Kris Kennaway wrote: > On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: > >>I run an IIR controller on one of our servers just fine ... 4GB of RAM, >>FreeBSD 4.x ... haven't tried 6.x on it yet ... > > > It's known to be broken on any system with >4GB of RAM. > > Kris > > I'll strengthen that statement and say that it is completely, 100% unusable with 4GB of RAM or more. You are guaranteed to get data corruption on the second I/O that you send. Fixing this requires re-writing much of the driver, unfortunately. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 08:27:29 2006 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 BC77D16A420 for ; Fri, 24 Feb 2006 08:27:29 +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 1462A43D55 for ; Fri, 24 Feb 2006 08:27:28 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k1O8RQX3065048; Fri, 24 Feb 2006 05:27:27 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: "O. Hartmann" Date: Fri, 24 Feb 2006 05:27:25 -0300 User-Agent: KMail/1.9.1 References: <43FCEF9C.5050308@bluelight.org.uk> <200602240455.07500.joao@matik.com.br> <43FEBD8C.4010602@uni-mainz.de> In-Reply-To: <43FEBD8C.4010602@uni-mainz.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602240527.25483.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: AMD 64 stability 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, 24 Feb 2006 08:27:29 -0000 On Friday 24 February 2006 05:02, O. Hartmann wrote: > > Isn't it an issue of the capabilities of the use technique of memory > sticks? If electrical basics are given for driving a lot of memory, a > mainboard capable of driving 32 GB RAM should be able to run 64 GB RAM > when the appropriate double sized memory sticks get available. > So this questions can not be answered neither from only the point of > view of the processor nor from only the electrical layout of the mainboar= d. > > In most cases, speaking of Opterons (Socket240), the electrical load is > the limiting factor, not the CPU, so the design of the mainboard AND of > the memory sticks are relevant. > I don't know if this would work but if the manufactor says the board suppor= ts=20 2GB or whatever modules per slot then we should believe this trying to put bigger ones in would be a wast of time I guess, most boards=20 would not even boot with incorrect memory modules 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 Fri Feb 24 08:40:35 2006 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 4620A16A423 for ; Fri, 24 Feb 2006 08:40:35 +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 D0C7B43D58 for ; Fri, 24 Feb 2006 08:40:33 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k1O8eWDA065552; Fri, 24 Feb 2006 05:40:32 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Fri, 24 Feb 2006 05:40:30 -0300 User-Agent: KMail/1.9.1 References: <43FCEF9C.5050308@bluelight.org.uk> <43FEBD56.4040200@gneto.com> In-Reply-To: <43FEBD56.4040200@gneto.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602240540.31546.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: AMD 64 stability 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, 24 Feb 2006 08:40:35 -0000 On Friday 24 February 2006 05:01, Martin Nilsson wrote: > > And it's here where it usually fails when you fill the board with 2GB > modules. The Chinese server-wannabee manufacturers products just can't > handle the load that these modules puts on the system. They are very > much aware of it, but their tech support never admits that it's their > crappy motherboard designs that causes the stability problems, instead > the come up with all sorts of strange excuses and finally closes all > support requests with: "not able to reproduce here - no fault" > > the deciding factor what is "crappy" often points out the buyers wallet at = the=20 end because for sure you can't get high tech stuff for a dollar or two so when you buy a MB for US70 and pay US50/GB you may not get what another = one=20 gets using a reliable server board with correct ECC/Reg memory, so when you= =20 buy cheap stuff you can not aspect to get a high reliable system you can see this already with S939 dualchannel boards which simply crash if= =20 you do not use real good dualchannel modules faster the processor is more sensitive the sitem is to all other components= =20 and for that they put big wheels on the fun cars to smoke more than only=20 once ;) 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 Fri Feb 24 10:04:47 2006 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 89B2016A420 for ; Fri, 24 Feb 2006 10:04:47 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21E1543D49 for ; Fri, 24 Feb 2006 10:04:46 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FCZoa-0007pY-8U; Fri, 24 Feb 2006 11:04:44 +0100 Message-ID: <43FEDBC4.3010103@datafarm.de> Date: Fri, 24 Feb 2006 11:11:16 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Scott Long References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> In-Reply-To: <43FEC2D9.7090407@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: anyone successfully using an icp-vortex / iir controller? 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, 24 Feb 2006 10:04:47 -0000 Hello, Scott Long schrieb: > Kris Kennaway wrote: >> On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: >>> I run an IIR controller on one of our servers just fine ... 4GB of >>> RAM, FreeBSD 4.x ... haven't tried 6.x on it yet ... >> It's known to be broken on any system with >4GB of RAM. > I'll strengthen that statement and say that it is completely, 100% > unusable with 4GB of RAM or more. You are guaranteed to get data > corruption on the second I/O that you send. Fixing this requires > re-writing much of the driver, unfortunately. If this is true - and I think so, I wasted a lot of time on it already - so why isn't there a little piece of documentation speaking out a warning. We've been happily using a large number of GDT controllers under FreeBSD for years after we have had a couple of bad experiences with other brands. One of those, a mylex 160lp was just tested to be unfunctional with 6.1b2 (8GB RAM), too. Are there any *good* SCSI RAID controllers out there that are known to be working in server setups (amd64, SMP, >4GB RAM)? When thinking it over, I guess I have to be grateful that over many years I never experienced s/th that made me question the "The Power To Serve" slogan. What I really feel unhappy about right now is that there was no information available so I could take appropriate measures in order to avoid the current situation (at least none that I could find). Well, what's the plan regarding the iir driver now? I would suspect that letting folks rendering their servers unfunctional by upgrading memory is not really a good strategy. The manpage lists two authors/maintainers, I emailed both early this week. Achim Leubner will be back from vacation the 27th. So maybe he can contribute s/th constructive. Kind regards, vt From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 11:30:26 2006 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 C959B16A420 for ; Fri, 24 Feb 2006 11:30:26 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from mail.dc-servers.com (mail.dc-servers.com [83.243.101.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 16B3443D45 for ; Fri, 24 Feb 2006 11:30:25 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: (qmail 4806 invoked by uid 399); 24 Feb 2006 11:30:27 -0000 Received: from unknown (HELO alfie.jigsawhq.com) (work@ashleymoran.me.uk@213.106.224.113) by mail.dc-servers.com with SMTP; 24 Feb 2006 11:30:27 -0000 From: Ashley Moran Organization: Codeweavers Ltd To: freebsd-amd64@freebsd.org Date: Fri, 24 Feb 2006 11:29:02 +0000 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602241129.02374.work@ashleymoran.me.uk> Subject: RAID on Tyan Tomcat K8E 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, 24 Feb 2006 11:30:26 -0000 I'm looking at a Tyan Tomcat K8E (S2865G2NR). Has anyone managed to get the onboard RAID working (mirrored)? The hardware list shows SATA as working but no mention of RAID. Ta Ashley From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 16:49:15 2006 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 90B0116A420 for ; Fri, 24 Feb 2006 16:49:15 +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 3BE2443D45 for ; Fri, 24 Feb 2006 16:49:14 +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 7A162F811 for ; Fri, 24 Feb 2006 09:49:11 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 3F1B0F805 for ; Fri, 24 Feb 2006 09:49:11 -0700 (MST) Date: Fri, 24 Feb 2006 09:49:10 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060224094910.5c51d1bd.kgunders@teamcool.net> In-Reply-To: <200602241129.02374.work@ashleymoran.me.uk> References: <200602241129.02374.work@ashleymoran.me.uk> 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: RAID on Tyan Tomcat K8E 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, 24 Feb 2006 16:49:15 -0000 On Fri, 24 Feb 2006 11:29:02 +0000 Ashley Moran wrote: > I'm looking at a Tyan Tomcat K8E (S2865G2NR). Has anyone managed to get the > onboard RAID working (mirrored)? The hardware list shows SATA as working but > no mention of RAID. I have a couple of these systems. Why would you want to use the POS onboard RAID to set up a mirror when there's gmirror;-) If you're unfamiliar, Ralf E. wrote a how-to available here: -- 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 Feb 24 17:47:01 2006 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 7167916A420 for ; Fri, 24 Feb 2006 17:47:01 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from mail.dc-servers.com (mail.dc-servers.com [83.243.101.206]) by mx1.FreeBSD.org (Postfix) with SMTP id AF5A943D49 for ; Fri, 24 Feb 2006 17:47:00 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: (qmail 14401 invoked by uid 399); 24 Feb 2006 17:47:03 -0000 Received: from unknown (HELO alfie.jigsawhq.com) (work@ashleymoran.me.uk@213.106.224.113) by mail.dc-servers.com with SMTP; 24 Feb 2006 17:47:03 -0000 From: Ashley Moran Organization: Codeweavers Ltd To: freebsd-amd64@freebsd.org Date: Fri, 24 Feb 2006 17:45:37 +0000 User-Agent: KMail/1.9.1 References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> In-Reply-To: <20060224094910.5c51d1bd.kgunders@teamcool.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200602241745.37259.work@ashleymoran.me.uk> Subject: Re: RAID on Tyan Tomcat K8E 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, 24 Feb 2006 17:47:01 -0000 On Friday 24 February 2006 16:49, Ken Gunderson wrote: > I have a couple of these systems. =A0Why would you want to use the POS > onboard RAID to set up a mirror when there's gmirror;-) Do you really think so little of on-board RAID? Is it that board in=20 particular, or on-board RAID in general? I feel safer somehow with anythin= g=20 hardware based as opposed to pure software solutions. Maybe my faith is=20 misplaced... I have to admit I had spontaneous disk corruption recently on a server usin= g=20 motherboard RAID on an MSI K8N Neo2 Platinum (Athlon64 but in i386 mode). = =20 The disks appear to be fine so it looks like the RAID controller went posta= l. =20 I've replaced the board with an Asus A8V Deluxe (which also helps as it run= s=20 in amd64 mode) and the RAID seems fine now but I'll be watching it closely. We're just about to order a batch of new servers and I was asking if the RA= ID=20 works on the K8E to save us =A3100 or so. But network admin lad next to me= =20 says he wouldn't risk it and we're better with the 3ware 8006-2 card so we= =20 will probably go with that. No chances on the database servers though: ARC-1120s RAID-6 in each :D Ashley From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 18:20:00 2006 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 AAD1A16A420 for ; Fri, 24 Feb 2006 18:20:00 +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 A611843D46 for ; Fri, 24 Feb 2006 18:19:59 +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 9F4EDF7CE for ; Fri, 24 Feb 2006 11:19:58 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 7C0DBF7C5 for ; Fri, 24 Feb 2006 11:19:58 -0700 (MST) Date: Fri, 24 Feb 2006 11:19:57 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060224111957.571b8394.kgunders@teamcool.net> In-Reply-To: <200602241745.37259.work@ashleymoran.me.uk> References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> <200602241745.37259.work@ashleymoran.me.uk> 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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: RAID on Tyan Tomcat K8E 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, 24 Feb 2006 18:20:00 -0000 On Fri, 24 Feb 2006 17:45:37 +0000 Ashley Moran wrote: > On Friday 24 February 2006 16:49, Ken Gunderson wrote: > > I have a couple of these systems. =A0Why would you want to use the POS > > onboard RAID to set up a mirror when there's gmirror;-) >=20 > Do you really think so little of on-board RAID? Is it that board in=20 > particular, or on-board RAID in general? I feel safer somehow with anyth= ing=20 > hardware based as opposed to pure software solutions. Maybe my faith is= =20 > misplaced... >=20 > I have to admit I had spontaneous disk corruption recently on a server us= ing=20 > motherboard RAID on an MSI K8N Neo2 Platinum (Athlon64 but in i386 mode).= =20 > The disks appear to be fine so it looks like the RAID controller went pos= tal. =20 > I've replaced the board with an Asus A8V Deluxe (which also helps as it r= uns=20 > in amd64 mode) and the RAID seems fine now but I'll be watching it closel= y. >=20 > We're just about to order a batch of new servers and I was asking if the = RAID=20 > works on the K8E to save us =A3100 or so. But network admin lad next to = me=20 > says he wouldn't risk it and we're better with the 3ware 8006-2 card so w= e=20 > will probably go with that. >=20 > No chances on the database servers though: ARC-1120s RAID-6 in each :D I've been using gmirror for a while now. It rocks. Suggest you _seriously_ take a look at if you want to save some bucks. Especially since those 3ware cards aren't cheap. And especially since all you're doing is a simple mirror. I've had to rebuild a failed mirror w/ gmirror and it's a pleasure. Very easy. Minimal downtime. --=20 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 Feb 24 18:42:04 2006 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 8BC2916A420 for ; Fri, 24 Feb 2006 18:42:04 +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 0F23A43D45 for ; Fri, 24 Feb 2006 18:42:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k1OIfm5p011681; Fri, 24 Feb 2006 11:41:51 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43FF5366.5030002@samsco.org> Date: Fri, 24 Feb 2006 11:41:42 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "V. T. Mueller" References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> <43FEDBC4.3010103@datafarm.de> In-Reply-To: <43FEDBC4.3010103@datafarm.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: anyone successfully using an icp-vortex / iir controller? 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, 24 Feb 2006 18:42:04 -0000 V. T. Mueller wrote: > > Hello, > > Scott Long schrieb: > >> Kris Kennaway wrote: >> >>> On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: >>> >>>> I run an IIR controller on one of our servers just fine ... 4GB of >>>> RAM, FreeBSD 4.x ... haven't tried 6.x on it yet ... >>> >>> It's known to be broken on any system with >4GB of RAM. >> >> I'll strengthen that statement and say that it is completely, 100% >> unusable with 4GB of RAM or more. You are guaranteed to get data >> corruption on the second I/O that you send. Fixing this requires >> re-writing much of the driver, unfortunately. > > > If this is true - and I think so, I wasted a lot of time on it already - > so why isn't there a little piece of documentation speaking out a > warning. We've been happily using a large number of GDT controllers > under FreeBSD for years after we have had a couple of bad experiences > with other brands. > > One of those, a mylex 160lp was just tested to be unfunctional with > 6.1b2 (8GB RAM), too. > > Are there any *good* SCSI RAID controllers out there that are known to > be working in server setups (amd64, SMP, >4GB RAM)? > > When thinking it over, I guess I have to be grateful that over many > years I never experienced s/th that made me question the "The Power To > Serve" slogan. What I really feel unhappy about right now is that there > was no information available so I could take appropriate measures in > order to avoid the current situation (at least none that I could find). > > Well, what's the plan regarding the iir driver now? I would suspect that > letting folks rendering their servers unfunctional by upgrading memory > is not really a good strategy. > > The manpage lists two authors/maintainers, I emailed both early this > week. Achim Leubner will be back from vacation the 27th. So maybe he can > contribute s/th constructive. > > Kind regards, > vt Well, there are several ways that I can answer these questions. I could say that the iir driver was developed and supported by the vendor, and that you should contact the vendor for support questions like this. I could say that the author of this driver didn't understand how to use FreeBSD's driver API's, and that to a casual reviewer, the driver looks like it should work, and that only with a deeper look do the problems become apparent. I could say that while I personally support the vast majority of the RAID drivers in FreeBSD, I only have the time and resources to actively maintain and fix the most popular ones, as taking care of a single driver for a single architecture usually involves an engineering and testing staff of at least a dozen people at most companies, and I try to do the equivalent job for 8 different drivers, all in my 'free time'. So, I understand your frustration over this. There are a number of other RAID solutions that work quite well in FreeBSD. Adaptec AAC, LSI MegaRAID, IBM/Adaptec ServeRAID, Compaq/HP CISS all are very reliable choices for SCSI RAID. I know that that doesn't help you with your ICP/Vortex choice, and I do sympathize with your problem. I've done my best to modernize as many drivers as I can to work with >4GB, but I've had to prioritize my efforts based on the popularity and the future returns of a given architecture. ICP/Vortex basically died when Adaptec bought them, so there isn't a lot of motivation to put energy into the driver since there won't ever be any new cards from them. However, if someone is interested in fixing this driver, I can help guide them. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 18:45:20 2006 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 97D1216A420 for ; Fri, 24 Feb 2006 18:45:20 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from ms-smtp-04-eri0.southeast.rr.com (ms-smtp-04-lbl.southeast.rr.com [24.25.9.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A07143D45 for ; Fri, 24 Feb 2006 18:45:19 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-118-154.sc.res.rr.com [24.211.118.154]) by ms-smtp-04-eri0.southeast.rr.com (8.13.4/8.13.4) with ESMTP id k1OIjHLM016919 for ; Fri, 24 Feb 2006 13:45:18 -0500 (EST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.13.4/8.13.4) with ESMTP id k1OIjHcY003756 for ; Fri, 24 Feb 2006 13:45:17 -0500 (EST) (envelope-from morganw@chemikals.org) Date: Fri, 24 Feb 2006 13:45:17 -0500 (EST) From: Wesley Morgan To: freebsd-amd64@freebsd.org Message-ID: <20060224133404.G780@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Kernel Freezes 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, 24 Feb 2006 18:45:20 -0000 I'm in the process of upgrading to an amd64 machine, and have run into some problems. The system is a Sempron 2600+ running in an ABIT KV-85 board, with 1gb of ram and a Maxtor 300gb SATA drive. So far, I was able to install both 6.1-beta2 and 6.0 without a problem. The system boots fine and seems to idle fine (at least, it idled all last night). The problem occurs when I try to compile something -- a custom kernel, buildworld, a couple ports -- the system freezes solid, with a garbled video display. The network driver doesn't seem to be the problem. I've disabled practically everything I can in the BIOS and I've even installed an old PCI video card, all with the same result. Trying to boot a 5.4 kernel was unsuccessful, the system froze during device detection, although I am not sure where as the screen became unreadable. I'll have to try a serial console later. Unfortunately I don't have the dmesg output handy ATM, but I wanted to know if this problem tickled anyone's brain for a possible answer... I'll post the boot logs later. Thanks, WM -- This .signature sanitized for your protection From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 20:04:15 2006 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 4EB2216A420 for ; Fri, 24 Feb 2006 20:04:15 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DFA043D48 for ; Fri, 24 Feb 2006 20:04:14 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (84zpxoq5xajlsv2a@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k1OK443N038248; Fri, 24 Feb 2006 12:04:04 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k1OK40mM038238; Fri, 24 Feb 2006 12:04:00 -0800 (PST) (envelope-from jmg) Date: Fri, 24 Feb 2006 12:03:59 -0800 From: John-Mark Gurney To: "V. T. Mueller" Message-ID: <20060224200359.GD840@funkthat.com> Mail-Followup-To: "V. T. Mueller" , Scott Long , eniazi@ossmail.com, freebsd-amd64@freebsd.org, Kris Kennaway References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> <43FEDBC4.3010103@datafarm.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43FEDBC4.3010103@datafarm.de> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: eniazi@ossmail.com, freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: anyone successfully using an icp-vortex / iir controller? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2006 20:04:15 -0000 V. T. Mueller wrote this message on Fri, Feb 24, 2006 at 11:11 +0100: > Well, what's the plan regarding the iir driver now? I would suspect > that letting folks rendering their servers unfunctional by upgrading > memory is not really a good strategy. > > The manpage lists two authors/maintainers, I emailed both early this > week. Achim Leubner will be back from vacation the 27th. So maybe he > can contribute s/th constructive. Good lucky with it... The iir has been a pain for us (my employer nCircle) for the last two years... They were completely unhelpful in finding out the v1.10 of iir.c was necessary to stablize our servers (it's worse for us since the servers are at customer's sites).. When we tried to upgrade from 4.x to 5.4-R we were unable to as the iir card would go out to lunch never to return (it has multiple commands outstanding, none would complete).. Oh, and when we told them 5.4-R, they were sorry, we don't support anything past 5.2-R on our cards.. so you might as well stop using their cards... As for driver rewrite.. it's obviously very necessary, and we have been trying to get one done, but have been unable to find the correct people to pay that are able to get it done... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 20:43:19 2006 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 252AC16A420 for ; Fri, 24 Feb 2006 20:43:19 +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 B703743D46 for ; Fri, 24 Feb 2006 20:43:16 +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 A051BF7D0 for ; Fri, 24 Feb 2006 13:43:15 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 7BC8BF7C5 for ; Fri, 24 Feb 2006 13:43:15 -0700 (MST) Date: Fri, 24 Feb 2006 13:43:14 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060224134314.0823742c.kgunders@teamcool.net> In-Reply-To: <43FF5366.5030002@samsco.org> References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> <43FEDBC4.3010103@datafarm.de> <43FF5366.5030002@samsco.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: anyone successfully using an icp-vortex / iir controller? 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, 24 Feb 2006 20:43:19 -0000 On Fri, 24 Feb 2006 11:41:42 -0700 Scott Long wrote: > V. T. Mueller wrote: > > > > Hello, > > > > Scott Long schrieb: > > > >> Kris Kennaway wrote: > >> > >>> On Fri, Feb 24, 2006 at 02:13:56AM -0400, Marc G. Fournier wrote: > >>> > >>>> I run an IIR controller on one of our servers just fine ... 4GB of > >>>> RAM, FreeBSD 4.x ... haven't tried 6.x on it yet ... > >>> > >>> It's known to be broken on any system with >4GB of RAM. > >> > >> I'll strengthen that statement and say that it is completely, 100% [snip] > So, I understand your frustration over this. There are a number of > other RAID solutions that work quite well in FreeBSD. Adaptec AAC, > LSI MegaRAID, IBM/Adaptec ServeRAID, Compaq/HP CISS all are very > reliable choices for SCSI RAID. I know that that doesn't help you Given Vivek's (320-2x) and my (320-1) issues w/the LSI MegaRAID one may want to exclude them from this list. LSI support is great but I'm not so sure about engineering since we still don't have a fix..... -- 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 Feb 24 22:10:19 2006 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 A73F316A420 for ; Fri, 24 Feb 2006 22:10:19 +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 0FE4743D45 for ; Fri, 24 Feb 2006 22:10:18 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5FFC7.dip.t-dialin.net [84.165.255.199]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id k1OMAFNX055073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Feb 2006 23:10:16 +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 k1OMA7pI015197; Fri, 24 Feb 2006 23:10:08 +0100 (CET) Message-ID: <43FF8449.4050907@deadcafe.de> Date: Fri, 24 Feb 2006 23:10:18 +0100 From: Daniel Rock User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Ashley Moran References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> <200602241745.37259.work@ashleymoran.me.uk> In-Reply-To: <200602241745.37259.work@ashleymoran.me.uk> 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: RAID on Tyan Tomcat K8E 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, 24 Feb 2006 22:10:19 -0000 Ashley Moran schrieb: > On Friday 24 February 2006 16:49, Ken Gunderson wrote: >> I have a couple of these systems. Why would you want to use the POS >> onboard RAID to set up a mirror when there's gmirror;-) > > Do you really think so little of on-board RAID? Is it that board in > particular, or on-board RAID in general? I feel safer somehow with anything > hardware based as opposed to pure software solutions. Maybe my faith is > misplaced... The onboard RAID (NvRaid) is no real RAID but relying on a device driver for the RAID functionality and a little help from BIOS for booting. The real RAID functionality lies completely inside the device driver (see /sys/dev/ata/ata-raid.c). So you really just have the choice between two different software solutions: "device ataraid" or "options GEOM_MIRROR". Daniel From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 24 22:57:18 2006 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 9E93316A422 for ; Fri, 24 Feb 2006 22:57:18 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from ms-smtp-03-eri0.southeast.rr.com (ms-smtp-03-lbl.southeast.rr.com [24.25.9.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A04443D67 for ; Fri, 24 Feb 2006 22:57:04 +0000 (GMT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-118-154.sc.res.rr.com [24.211.118.154]) by ms-smtp-03-eri0.southeast.rr.com (8.13.4/8.13.4) with ESMTP id k1OMv06b016645 for ; Fri, 24 Feb 2006 17:57:01 -0500 (EST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.13.4/8.13.4) with ESMTP id k1OMuxFD005972 for ; Fri, 24 Feb 2006 17:57:00 -0500 (EST) (envelope-from morganw@chemikals.org) Date: Fri, 24 Feb 2006 17:56:59 -0500 (EST) From: Wesley Morgan To: freebsd-amd64@freebsd.org In-Reply-To: <20060224133404.G780@volatile.chemikals.org> Message-ID: <20060224175539.H5959@volatile.chemikals.org> References: <20060224133404.G780@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: Kernel Freezes 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, 24 Feb 2006 22:57:18 -0000 On Fri, 24 Feb 2006, Wesley Morgan wrote: > I'm in the process of upgrading to an amd64 machine, and have run into > some problems. The system is a Sempron 2600+ running in an ABIT KV-85 > board, with 1gb of ram and a Maxtor 300gb SATA drive. > > So far, I was able to install both 6.1-beta2 and 6.0 without a problem. > The system boots fine and seems to idle fine (at least, it idled all > last night). The problem occurs when I try to compile something -- a > custom kernel, buildworld, a couple ports -- the system freezes solid, > with a garbled video display. The network driver doesn't seem to be the > problem. I've disabled practically everything I can in the BIOS and I've > even installed an old PCI video card, all with the same result. > > Trying to boot a 5.4 kernel was unsuccessful, the system froze during > device detection, although I am not sure where as the screen became > unreadable. I'll have to try a serial console later. > > Unfortunately I don't have the dmesg output handy ATM, but I wanted to > know if this problem tickled anyone's brain for a possible answer... > I'll post the boot logs later. The boot logs from said system. Anything stand out? The system passes a 256MB 10-loop memtest as well, so RAM doesn't seem the likely culprit. Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80972000. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193177 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1599827782 Hz CPU: AMD Sempron(tm) Processor 2600+ (1599.83-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20fc2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 128 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 1006567424 (959 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000a6f000 - 0x000000003a38ffff, 965873664 bytes (235809 pages) avail memory = 960376832 (915 MB) APIC: CPU 0 has ACPI ID 0 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050010 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device mem: io: acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80007804 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=02041106) AcpiOsDerivePciId: bus 0 dev 17 func 0 AcpiOsDerivePciId: bus 0 dev 15 func 1 AcpiOsDerivePciId: bus 0 dev 17 func 1 AcpiOsDerivePciId: bus 0 dev 15 func 0 AcpiOsDerivePciId: bus 0 dev 17 func 2 AcpiOsDerivePciId: bus 0 dev 17 func 3 AcpiOsDerivePciId: bus 0 dev 17 func 4 AcpiOsDerivePciId: bus 0 dev 16 func 0 AcpiOsDerivePciId: bus 0 dev 16 func 1 AcpiOsDerivePciId: bus 0 dev 16 func 2 AcpiOsDerivePciId: bus 0 dev 16 func 3 AcpiOsDerivePciId: bus 0 dev 16 func 4 AcpiOsDerivePciId: bus 0 dev 17 func 0 acpi0: Power Button (fixed) pci_link0: irq 10 on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 6 7 10 11 12 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 6 7 10 11 12 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link1: irq 11 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 6 7 10 11 12 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 6 7 10 11 12 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link2: irq 12 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 6 7 10 11 12 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 12 N 0 3 4 6 7 10 11 12 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link3: on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link4: on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link5: on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link6: on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link7: on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 6 7 10 11 12 pci_link8: irq 20 on acpi0 pci_link8: Links after initial probe: Index IRQ Rtd Ref IRQs 0 20 N 0 20 pci_link8: Links after initial validation: Index IRQ Rtd Ref IRQs 0 20 N 0 20 pci_link8: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 20 pci_link9: irq 21 on acpi0 pci_link9: Links after initial probe: Index IRQ Rtd Ref IRQs 0 21 N 0 21 pci_link9: Links after initial validation: Index IRQ Rtd Ref IRQs 0 21 N 0 21 pci_link9: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 21 pci_link10: irq 22 on acpi0 pci_link10: Links after initial probe: Index IRQ Rtd Ref IRQs 0 22 N 0 22 pci_link10: Links after initial validation: Index IRQ Rtd Ref IRQs 0 22 N 0 22 pci_link10: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 22 pci_link11: irq 23 on acpi0 pci_link11: Links after initial probe: Index IRQ Rtd Ref IRQs 0 23 N 0 23 pci_link11: Links after initial validation: Index IRQ Rtd Ref IRQs 0 23 N 0 23 pci_link11: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 23 ACPI timer: 1/2 1/1 1/2 1/2 1/2 1/2 1/2 1/1 1/2 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI: Found matching pin for 0.16.INTA at func 0: 255 ACPI: Found matching pin for 0.16.INTA at func 1: 255 ACPI: Found matching pin for 0.16.INTB at func 2: 255 ACPI: Found matching pin for 0.16.INTB at func 3: 255 ACPI: Found matching pin for 0.16.INTC at func 4: 255 ACPI: Found matching pin for 0.17.INTC at func 5: 12 pci_link10: BIOS IRQ 12 for -2145774616.17.INTC is invalid ACPI: Found matching pin for 0.18.INTA at func 0: 10 pci_link11: BIOS IRQ 10 for -2145774616.18.INTA is invalid ACPI: Found matching pin for 0.15.INTA at func 1: 255 ACPI: Found matching pin for 0.15.INTB at func 0: 11 pci_link8: BIOS IRQ 11 for -2145774616.15.INTB is invalid pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1106, dev=0x0204, revid=0x00 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x2230, cachelnsz=0 (dwords) lattimer=0x08 (240 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[10]: type 3, range 32, base e0000000, size 27, enabled found-> vendor=0x1106, dev=0x1204, revid=0x00 bus=0, slot=0, func=1 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0x2204, revid=0x00 bus=0, slot=0, func=2 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0x3204, revid=0x00 bus=0, slot=0, func=3 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0x4204, revid=0x00 bus=0, slot=0, func=4 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0x7204, revid=0x00 bus=0, slot=0, func=7 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0xb188, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0e (3500 ns), maxlat=0x00 (0 ns) found-> vendor=0x1106, dev=0x3149, revid=0x80 bus=0, slot=15, func=0 class=01-01-8f, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000b000, size 3, enabled map[14]: type 4, range 32, base 0000b400, size 2, enabled map[18]: type 4, range 32, base 0000b800, size 3, enabled map[1c]: type 4, range 32, base 0000bc00, size 2, enabled map[20]: type 4, range 32, base 0000c000, size 4, enabled map[24]: type 4, range 32, base 0000c400, size 8, enabled pcib0: matched entry for 0.15.INTB (src \\_SB_.PCI0.ALKA:0) pcib0: slot 15 INTB routed to irq 20 via \\_SB_.PCI0.ALKA found-> vendor=0x1106, dev=0x0571, revid=0x06 bus=0, slot=15, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000c800, size 4, enabled found-> vendor=0x1106, dev=0x3038, revid=0x81 bus=0, slot=16, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type 4, range 32, base 0000cc00, size 5, enabled found-> vendor=0x1106, dev=0x3038, revid=0x81 bus=0, slot=16, func=1 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type 4, range 32, base 0000d000, size 5, enabled found-> vendor=0x1106, dev=0x3038, revid=0x81 bus=0, slot=16, func=2 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type 4, range 32, base 0000d400, size 5, enabled found-> vendor=0x1106, dev=0x3038, revid=0x81 bus=0, slot=16, func=3 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[20]: type 4, range 32, base 0000d800, size 5, enabled found-> vendor=0x1106, dev=0x3104, revid=0x86 bus=0, slot=16, func=4 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base ee000000, size 8, enabled found-> vendor=0x1106, dev=0x3227, revid=0x00 bus=0, slot=17, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 found-> vendor=0x1106, dev=0x3059, revid=0x60 bus=0, slot=17, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=12 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000dc00, size 8, enabled pcib0: matched entry for 0.17.INTC (src \\_SB_.PCI0.ALKC:0) pcib0: slot 17 INTC routed to irq 22 via \\_SB_.PCI0.ALKC found-> vendor=0x1106, dev=0x3065, revid=0x78 bus=0, slot=18, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x03 (750 ns), maxlat=0x08 (2000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000e400, size 8, enabled map[14]: type 1, range 32, base ee001000, size 8, enabled pcib0: matched entry for 0.18.INTA (src \\_SB_.PCI0.ALKD:0) pcib0: slot 18 INTA routed to irq 23 via \\_SB_.PCI0.ALKD found-> vendor=0x1022, dev=0x1100, revid=0x00 bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) agp0: mem 0xe0000000-0xe7ffffff at device 0.0 on pci0 AMD64: 1 Misc. Control unit(s) found. agp0: Reserved 0x8000000 bytes for rid 0x10 type 3 at 0xe0000000 agp0: allocating GATT for aperture of size 128M pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xec000000-0xedffffff pcib1: prefetched decode 0xe8000000-0xebffffff pci1: on pcib1 pci1: physical bus=1 found-> vendor=0x1106, dev=0x3108, revid=0x01 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base e8000000, size 26, enabled pcib1: (null) requested memory range 0xe8000000-0xebffffff: good map[14]: type 1, range 32, base ec000000, size 24, enabled pcib1: (null) requested memory range 0xec000000-0xecffffff: good pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 16 pcib1: slot 0 INTA is routed to irq 16 pci1: at device 0.0 (no driver attached) atapci0: port 0xb000-0xb007,0xb400-0xb403,0xb800-0xb807,0xbc00-0xbc03,0xc000-0xc00f,0xc400-0xc4ff irq 20 at device 15.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc000 atapci0: [MPSAFE] atapci0: Reserved 0x100 bytes for rid 0x24 type 4 at 0xc400 ata2: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xb000 atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0xb400 ata2: SATA connect ready time=0ms ata2: sata_connect devices=0x1 ata2: [MPSAFE] ata3: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xb800 atapci0: Reserved 0x4 bytes for rid 0x1c type 4 at 0xbc00 ata3: SATA connect status=00000000 ata3: [MPSAFE] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc800-0xc80f at device 15.1 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc800 ata0: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=7f ostat1=50 ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat1=0x10 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=ff stat1=10 devices=0x8 ata0: [MPSAFE] ata1: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=60 ostat1=70 ata1: stat0=0x20 err=0x20 lsb=0x20 msb=0x20 ata1: stat1=0x30 err=0x30 lsb=0x30 msb=0x30 ata1: reset tp2 stat0=20 stat1=30 devices=0x0 ata1: [MPSAFE] uhci0: port 0xcc00-0xcc1f at device 16.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xcc00 pcib0: matched entry for 0.16.INTA (src \\_SB_.PCI0.ALKB:0) pcib0: slot 16 INTA routed to irq 21 via \\_SB_.PCI0.ALKB uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f at device 16.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd000 pcib0: matched entry for 0.16.INTA (src \\_SB_.PCI0.ALKB:0) pcib0: slot 16 INTA routed to irq 21 via \\_SB_.PCI0.ALKB uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f at device 16.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd400 pcib0: matched entry for 0.16.INTB (src \\_SB_.PCI0.ALKB:0) pcib0: slot 16 INTB routed to irq 21 via \\_SB_.PCI0.ALKB uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd800-0xd81f at device 16.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0xd800 pcib0: matched entry for 0.16.INTB (src \\_SB_.PCI0.ALKB:0) pcib0: slot 16 INTB routed to irq 21 via \\_SB_.PCI0.ALKB uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xee000000-0xee0000ff at device 16.4 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xee000000 pcib0: matched entry for 0.16.INTC (src \\_SB_.PCI0.ALKB:0) pcib0: slot 16 INTC routed to irq 21 via \\_SB_.PCI0.ALKB ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 pci0: at device 17.5 (no driver attached) vr0: port 0xe400-0xe4ff mem 0xee001000-0xee0010ff irq 23 at device 18.0 on pci0 vr0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xe400 miibus0: on vr0 ukphy0: on miibus0 ukphy0: OUI 0x004063, model 0x0032, rev. 10 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: bpf attached vr0: Ethernet address: 00:50:8d:84:b2:51 vr0: [MPSAFE] acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0x4041 0x4041 0x4041 0x4041 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: using extended I/O port range ppc0: ECP SPP SPP ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x1d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ ex_isa_identify() atkbdc: atkbdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete ahc_isa_probe 11: ioport 0xbc00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered linprocfs registered lapic: Divisor 2, Frequency 99989114 hz Timecounter "TSC" frequency 1599827782 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on VIA 8237 chip acd0: setting UDMA33 on VIA 8237 chip fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout acd0: DVDROM drive at ata0 as slave acd0: 512KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 286188MB at ata2-master SATA150 ad4: 586114704 sectors [581463C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ad4: VIA check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ATA PseudoRAID loaded ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 23 (PCI IRQ 23) to cluster 0 Trying to mount root from ufs:/dev/ad4s1a start_init: trying /sbin/init -- This .signature sanitized for your protection From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 25 00:39:41 2006 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 557A616A422 for ; Sat, 25 Feb 2006 00:39:41 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id D206E43D53 for ; Sat, 25 Feb 2006 00:39:40 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id D707D67; Fri, 24 Feb 2006 18:39:39 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id EF48161C38; Fri, 24 Feb 2006 18:39:38 -0600 (CST) Date: Fri, 24 Feb 2006 18:39:38 -0600 From: "Matthew D. Fuller" To: Daniel Rock Message-ID: <20060225003938.GN60618@over-yonder.net> References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> <200602241745.37259.work@ashleymoran.me.uk> <43FF8449.4050907@deadcafe.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43FF8449.4050907@deadcafe.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: freebsd-amd64@freebsd.org Subject: Re: RAID on Tyan Tomcat K8E 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: Sat, 25 Feb 2006 00:39:41 -0000 On Fri, Feb 24, 2006 at 11:10:18PM +0100 I heard the voice of Daniel Rock, and lo! it spake thus: > > So you really just have the choice between two different software > solutions: "device ataraid" or "options GEOM_MIRROR". Except that the ataraid solution will boot off the second drive if the first fails, and the RAID can be setup in the BIOS and be ready for the OS when you fire up sysinstall the first time. (assuming the nvidia RAID is supported, which I think it is, but I don't really know) -- 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 Sat Feb 25 01:51:38 2006 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 D6A6F16A420 for ; Sat, 25 Feb 2006 01:51: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 7638843D45 for ; Sat, 25 Feb 2006 01:51:38 +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 7E862F7CE for ; Fri, 24 Feb 2006 18:51:37 -0700 (MST) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 49967F7C5 for ; Fri, 24 Feb 2006 18:51:37 -0700 (MST) Date: Fri, 24 Feb 2006 18:51:36 -0700 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20060224185136.1411baaa.kgunders@teamcool.net> In-Reply-To: <20060225003938.GN60618@over-yonder.net> References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> <200602241745.37259.work@ashleymoran.me.uk> <43FF8449.4050907@deadcafe.de> <20060225003938.GN60618@over-yonder.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: Re: RAID on Tyan Tomcat K8E 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: Sat, 25 Feb 2006 01:51:39 -0000 On Fri, 24 Feb 2006 18:39:38 -0600 "Matthew D. Fuller" wrote: > On Fri, Feb 24, 2006 at 11:10:18PM +0100 I heard the voice of > Daniel Rock, and lo! it spake thus: > > > > So you really just have the choice between two different software > > solutions: "device ataraid" or "options GEOM_MIRROR". > > Except that the ataraid solution will boot off the second drive if the > first fails, and the RAID can be setup in the BIOS and be ready for > the OS when you fire up sysinstall the first time. > > (assuming the nvidia RAID is supported, which I think it is, but I > don't really know) gmirror will boot off the second drive no problem. -- 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 Sat Feb 25 02:03:05 2006 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 D1F4416A420 for ; Sat, 25 Feb 2006 02:03:05 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DEF143D79 for ; Sat, 25 Feb 2006 02:02:50 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 193DA168; Fri, 24 Feb 2006 20:02:50 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 0E5AC61C39; Fri, 24 Feb 2006 20:02:49 -0600 (CST) Date: Fri, 24 Feb 2006 20:02:48 -0600 From: "Matthew D. Fuller" To: Ken Gunderson Message-ID: <20060225020248.GP60618@over-yonder.net> References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> <200602241745.37259.work@ashleymoran.me.uk> <43FF8449.4050907@deadcafe.de> <20060225003938.GN60618@over-yonder.net> <20060224185136.1411baaa.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060224185136.1411baaa.kgunders@teamcool.net> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 Cc: freebsd-amd64@freebsd.org Subject: Re: RAID on Tyan Tomcat K8E 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: Sat, 25 Feb 2006 02:03:06 -0000 On Fri, Feb 24, 2006 at 06:51:36PM -0700 I heard the voice of Ken Gunderson, and lo! it spake thus: > > gmirror will boot off the second drive no problem. Well, gmirror never will, since it's not involved at that level ;) The BIOS may, but a lot of them don't. -- 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 Sat Feb 25 10:33:28 2006 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 6D2BB16A420 for ; Sat, 25 Feb 2006 10:33:28 +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 8464143D45 for ; Sat, 25 Feb 2006 10:33:27 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5FFC7.dip.t-dialin.net [84.165.255.199]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id k1PAXOXx055696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 25 Feb 2006 11:33:25 +0100 (CET) X-Envelope-To: 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 k1PAXICZ049140 for ; Sat, 25 Feb 2006 11:33:18 +0100 (CET) Message-ID: <44003270.1040904@deadcafe.de> Date: Sat, 25 Feb 2006 11:33:20 +0100 From: Daniel Rock User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <200602241129.02374.work@ashleymoran.me.uk> <20060224094910.5c51d1bd.kgunders@teamcool.net> <200602241745.37259.work@ashleymoran.me.uk> <43FF8449.4050907@deadcafe.de> <20060225003938.GN60618@over-yonder.net> <20060224185136.1411baaa.kgunders@teamcool.net> <20060225020248.GP60618@over-yonder.net> In-Reply-To: <20060225020248.GP60618@over-yonder.net> 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 Subject: Re: RAID on Tyan Tomcat K8E 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: Sat, 25 Feb 2006 10:33:28 -0000 Matthew D. Fuller schrieb: > On Fri, Feb 24, 2006 at 06:51:36PM -0700 I heard the voice of > Ken Gunderson, and lo! it spake thus: >> gmirror will boot off the second drive no problem. > > Well, gmirror never will, since it's not involved at that level ;) > > The BIOS may, but a lot of them don't. All BIOSes I have seen in the past few years offer the option to select multiple boot devices with different priorities. Many BIOSes offer at least four different boot devices, some even eight. By reading the source I have the feeling that ataraid is in some respects incomplete (e.g. degraded RAID 5 mode). Daniel From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 25 14:24:03 2006 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 B9D7016A441 for ; Sat, 25 Feb 2006 14:24:03 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B5F643D5A for ; Sat, 25 Feb 2006 14:23:52 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FD0Kt-000L4j-H4; Sat, 25 Feb 2006 15:23:51 +0100 Message-ID: <44006A03.7030500@datafarm.de> Date: Sat, 25 Feb 2006 15:30:27 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Scott Long References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> <43FEDBC4.3010103@datafarm.de> <43FF5366.5030002@samsco.org> In-Reply-To: <43FF5366.5030002@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? 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: Sat, 25 Feb 2006 14:24:04 -0000 Scott Long schrieb: > V. T. Mueller wrote: >> Are there any *good* SCSI RAID controllers out there that are known to >> be working in server setups (amd64, SMP, >4GB RAM)? >> >> When thinking it over, I guess I have to be grateful that over many >> years I never experienced s/th that made me question the "The Power To >> Serve" slogan. What I really feel unhappy about right now is that >> there was no information available so I could take appropriate >> measures in order to avoid the current situation (at least none that I >> could find). >> >> Well, what's the plan regarding the iir driver now? I would suspect >> that letting folks rendering their servers unfunctional by upgrading >> memory is not really a good strategy. >> >> The manpage lists two authors/maintainers, I emailed both early this >> week. Achim Leubner will be back from vacation the 27th. So maybe he >> can contribute s/th constructive. > > Well, there are several ways that I can answer these questions. I could > say that the iir driver was developed and supported by the vendor, and > that you should contact the vendor for support questions like this. I > could say that the author of this driver didn't understand how to use > FreeBSD's driver API's, and that to a casual reviewer, the driver looks > like it should work, and that only with a deeper look do the problems > become apparent. I could say that while I personally support the vast > majority of the RAID drivers in FreeBSD, I only have the time and > resources to actively maintain and fix the most popular ones, as taking > care of a single driver for a single architecture usually involves an > engineering and testing staff of at least a dozen people at most > companies, and I try to do the equivalent job for 8 different drivers, > all in my 'free time'. Scott, all this is clear and also the reason why I myself (along with a very large number of other people I suppose) am very grateful that there are people like you. Not many with special abilities (I can't speak C) do use those for the benefit of others. If there weren't people like you, we all would be sitting around using one IT platform. No competition, no freedom of choice, little progress and innovation... > So, I understand your frustration over this. There are a number of > other RAID solutions that work quite well in FreeBSD. Adaptec AAC, > LSI MegaRAID, IBM/Adaptec ServeRAID, Compaq/HP CISS all are very > reliable choices for SCSI RAID. I know that that doesn't help you > with your ICP/Vortex choice, and I do sympathize with your problem. We have been using SCSI RAID for 14 years now and have a ton of good reasons to stick with icp-vortex. You know, RAID controllers are the kind of gear where you don't easily forget bad experiences. In all the (approx. 10) years we've been using icp now, we never had a reason to doubt the superior reliabilty of their controllers. > I've done my best to modernize as many drivers as I can to work with > >4GB, but I've had to prioritize my efforts based on the popularity and > the future returns of a given architecture. Agreed, this is why I emailed the original authors and am also evaluating possibilities for contracting someone to do the 'port'. > ICP/Vortex basically died > when Adaptec bought them, so there isn't a lot of motivation to put > energy into the driver since there won't ever be any new cards from > them. However, if someone is interested in fixing this driver, I can > help guide them. Hm, this isn't really true. There are current/new products. I will try to contact Adaptec in order to find out what their official attitude is, if they have any, though. One goal remains unmet - as far as I know there is no web-ressource that lists hardware that is likely to be unfunctional with >=4GB of main memory. Even if iir is the only driver which has these problems (I don't think so) I think people should be able to find this information before they find out their hardware is not supported. Especially the fact that drivers do first work with setups below 4G might trick people into taking a road that leeds them to doom sooner or later. So for the benefit of the 'still-unaware' I'd like to ask you to forward the information you have to someone who maintains the website and/or the release notes. And thanks a lot for your offer to help guiding someone to fix the driver. I will let you know if I manage to find somebody. With best regards, vt From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 25 14:29:56 2006 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 5F9C916A420 for ; Sat, 25 Feb 2006 14:29:56 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from mr0.continum.net (mr0.continum.net [80.72.128.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0039143D64 for ; Sat, 25 Feb 2006 14:29:43 +0000 (GMT) (envelope-from freebsd-amd64@datafarm.de) Received: from tecgate.frbh.continum.net ([80.72.130.254] helo=[192.168.100.70]) by mr0.continum.net with asmtp (Exim 4.30) id 1FD0QZ-000L6P-CN; Sat, 25 Feb 2006 15:29:43 +0100 Message-ID: <44006B63.9040503@datafarm.de> Date: Sat, 25 Feb 2006 15:36:19 +0100 From: "V. T. Mueller" User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: John-Mark Gurney References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> <43FEDBC4.3010103@datafarm.de> <20060224200359.GD840@funkthat.com> In-Reply-To: <20060224200359.GD840@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? 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: Sat, 25 Feb 2006 14:29:56 -0000 Hello John-Mark, John-Mark Gurney schrieb: > V. T. Mueller wrote this message on Fri, Feb 24, 2006 at 11:11 +0100: >>Well, what's the plan regarding the iir driver now? I would suspect >>that letting folks rendering their servers unfunctional by upgrading >>memory is not really a good strategy. >>The manpage lists two authors/maintainers, I emailed both early this >>week. Achim Leubner will be back from vacation the 27th. So maybe he >>can contribute s/th constructive. > > Good lucky with it... The iir has been a pain for us (my employer > nCircle) for the last two years... They were completely unhelpful in > finding out the v1.10 of iir.c was necessary to stablize our servers > (it's worse for us since the servers are at customer's sites).. When > we tried to upgrade from 4.x to 5.4-R we were unable to as the iir card > would go out to lunch never to return (it has multiple commands > outstanding, none would complete).. Oh, and when we told them 5.4-R, > they were sorry, we don't support anything past 5.2-R on our cards.. > so you might as well stop using their cards... Not before I did try all possible means... ;) > As for driver rewrite.. it's obviously very necessary, and we have > been trying to get one done, but have been unable to find the correct > people to pay that are able to get it done... I think I have someone. maybe we could team up in hiring them. Monday I should have more information, gonna get back to you then. Kind regards, vt From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 25 21:46:40 2006 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 9611916A422 for ; Sat, 25 Feb 2006 21:46:40 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6509E43D49 for ; Sat, 25 Feb 2006 21:46:39 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (7jx7j0w24c3q5epz@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k1PLkXcx076360; Sat, 25 Feb 2006 13:46:33 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k1PLkTrK076342; Sat, 25 Feb 2006 13:46:29 -0800 (PST) (envelope-from jmg) Date: Sat, 25 Feb 2006 13:46:29 -0800 From: John-Mark Gurney To: "V. T. Mueller" Message-ID: <20060225214629.GF840@funkthat.com> Mail-Followup-To: "V. T. Mueller" , Scott Long , freebsd-amd64@freebsd.org References: <3.0.1.32.20060222094147.00a928a0@pop.redshift.com> <20060224021327.H1005@ganymede.hub.org> <20060224064125.GA1782@xor.obsecurity.org> <43FEC2D9.7090407@samsco.org> <43FEDBC4.3010103@datafarm.de> <43FF5366.5030002@samsco.org> <44006A03.7030500@datafarm.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44006A03.7030500@datafarm.de> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-amd64@freebsd.org Subject: Re: anyone successfully using an icp-vortex / iir controller? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2006 21:46:40 -0000 V. T. Mueller wrote this message on Sat, Feb 25, 2006 at 15:30 +0100: > One goal remains unmet - as far as I know there is no web-ressource > that lists hardware that is likely to be unfunctional with >=4GB of > main memory. Even if iir is the only driver which has these problems > (I don't think so) I think people should be able to find this > information before they find out their hardware is not supported. > Especially the fact that drivers do first work with setups below 4G > might trick people into taking a road that leeds them to doom sooner > or later. > > So for the benefit of the 'still-unaware' I'd like to ask you to > forward the information you have to someone who maintains the > website and/or the release notes. I tried looking for it last time, but this time found it: http://www.freebsd.org/projects/busdma/ That should contain the latest driver information on what has been converted to be safe, etc... (Shame on the driver developers who have fixed issues and not updated the page)... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."