From owner-freebsd-stable@FreeBSD.ORG Thu Sep 8 21:35:41 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB29516A41F; Thu, 8 Sep 2005 21:35:41 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4869043D46; Thu, 8 Sep 2005 21:35:41 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from adsl-065-013-105-239.sip.tys.bellsouth.net ([65.13.105.239]:1496 helo=[192.168.1.33]) by audi.websitewelcome.com with esmtpa (Exim 4.52) id 1EDU3S-000491-0C; Thu, 08 Sep 2005 16:35:34 -0500 Message-ID: <4320AECD.8080004@goldsword.com> Date: Thu, 08 Sep 2005 17:36:13 -0400 From: "J. T. Farmer" Organization: GoldSword Systems User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <28edec3c05090804373a134e01@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Cc: sos@freebsd.org Subject: Re: SiI 3114 woes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2005 21:35:41 -0000 Jon Dama wrote: >Yes, but only in a configuration <=3GB. But I thought those problems were >ironed out? I've been looking to switch that machine back to >FreeBSD/amd64 but haven't had a chance yet. Would love to know if there >are issues ahead. > >-Jon > >On Thu, 8 Sep 2005, Mars G. Miro wrote: > >>Yo list/Soren! >> >> Has anybody successfully installed FreeBSD on the dual-Opteron TYAN >>ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html ) >> using the onboard SiI 3114 SATA controller? This mobo is supposedly >>supported: >>http://www.freebsd.org/cgi/query-pr.cgi?pr=80857 >> >> But I have never been able to successfully install >>FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA. >> >>In my last attempt at installing 6.0Beta4 AMD64 on it, I get: >> >> ad4: FAILURE - WRITE_DMA status=51 error=4 >>LBA=105819039 >> g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5 >> >> at the debugging console >> >> and >> >> panic:bundirty: buffer 0xffffffff9a7faff0 still on queue 1 >> cpuid = 0 >> KDB: enter: panic >> [ thread pid 3 tid 100021 ] >> Stopped at kdb_enter+0x2f: nop >> db> trace >> Tracing pid 3 tid 100021 td 0xffffff007ba14be0 >> kdb_enter() at kdb_enter+0x2f >> panic() at panic+0x249 >> bundirty() at bundirty+0x128 >> brelse() at brelse+0x831 >> bufdone() at bufdone+0x225 >> ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7 >> bufdone() at bufdone+0x2ad >> g_vfs_done() at g_gvfs_done+0x63 >> g_io_schedule_up() at g_io_schedule_up+0xd4 >> g_up_procbody() at g_up_procbody+0x7a >> fork_exit() at fork_exit+0xbb >> fork_trampoline() at fork_tramploine+0xe >> --- trap 0, rip = 0, rsp = 0xffffffffb2160d00, rbp = 0 --- >> db> >> >> Some months ago, I did successfully install FreeBSD 5.4/amd64 on it, >>using PATA IDE drives, and no problems whatsoever, so I think this has >>something to do w/ the SiI 3114 driver. >> >> Any help is much appreciated. >> >> I do apologize for cross-posting but this concerns -stable and -amd64. >> It looks like the same issue that we have been complaining about irt the ATA driver in 5.4/stable.. Several people have also found it to be a problem under 6.0. In my case, it happens with a plain old PATA drive (via 8235 controller). It runs fine under PIO4 mode, any DMA modes result in the same errors you got. I was working on updating and installing the ataMkIII patches since that's the only version that is being supported :^< But they are supposed to merge the beta code that is in 6.0 into 5.stable and it sound like the same errors are occurring. I'm seriously considering installing Gentoo and wash my hands of it. John ---------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software