From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 30 04:30:02 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B23C16A419 for ; Tue, 30 Oct 2007 04:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4AEC113C494 for ; Tue, 30 Oct 2007 04:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l9U4U22D049075 for ; Tue, 30 Oct 2007 04:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l9U4U21d049070; Tue, 30 Oct 2007 04:30:02 GMT (envelope-from gnats) Resent-Date: Tue, 30 Oct 2007 04:30:02 GMT Resent-Message-Id: <200710300430.l9U4U21d049070@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Simon Dircks Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB0EF16A417 for ; Tue, 30 Oct 2007 04:21:53 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 9ADDE13C4AA for ; Tue, 30 Oct 2007 04:21:53 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.1/8.14.1) with ESMTP id l9U4LqXo027544 for ; Tue, 30 Oct 2007 04:21:52 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.1/8.14.1/Submit) id l9U4LqlB027543; Tue, 30 Oct 2007 04:21:52 GMT (envelope-from nobody) Message-Id: <200710300421.l9U4LqlB027543@www.freebsd.org> Date: Tue, 30 Oct 2007 04:21:52 GMT From: Simon Dircks To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/117656: SATA issues on amd64 freebsd 7 (right before beta1) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 04:30:02 -0000 >Number: 117656 >Category: kern >Synopsis: SATA issues on amd64 freebsd 7 (right before beta1) >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 30 04:30:01 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Simon Dircks >Release: current 7 before the branch, after the branch >Organization: KSD >Environment: carp0# uname -a FreeBSD carp0.ksdhost.com 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon Oct 29 02:36:11 EDT 2007 graff@carp0.ksdhost.com:/usr/obj/usr/src/sys/CARP0 amd64 >Description: Hi, i am having some trouble with freebsd on the Tyan Transport TA26 (B3992). Motherboard Thunder h2000M (S3992). I have several of these machines and all the hardware i have been using to test with. I have also spent a couple weeks going though this and testing. I hope that this email will lead to a solution for me and some other people, and i would like to help test and fix this as best as i can. (time, hardware, money if i can spare) Basicly the controller in question is onboard . It was added here: http://lists.freebsd.org/pipermail/freebsd-bugs/2006-August/019853.html And said it works well here: http://lists.freebsd.org/pipermail/freebsd-www/2007-January/004686.html Now whats funny is nicole at unixgirl.com was a big clue that i wasn't doing something wrong. She reported trouble here: See this thread here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-February/141725.html Here is my personal experences: I am testing with about 10 new western digital 500G SATA drives. And 2 of the said tyan servers. Identical hardware runs perfectly on freebsd 6.2 SMP amd64 when this drive controller is in PATA mode. (Both of these servers have been up for 20 days now slammed with mysql and apache, no crashes, nothing) On freebsd 6.2 SMP amd64 when the controller is in SATA mode it will sometimes fail during install, or after a build world. On freebsd 7.x SMP amd64 in PATA mode, the install will fail 9 out of 10 times, and most of the time wont boot after 1-2 times. (missing files or just alot of g_vfs_done() errors. On freebsd 7.x SMP amd64 in SATA mode, the install will fail right away, and never goes through. Another piece of information I hope helps, i had both of these servers booted up over PXE running 7.x and they worked perfectly. I mounted the drives in all of them localy with ZFS and it lead to tons of checksum errors, and eventually a crash so zfs did not return bad data. (4 disks in a zfs mirror pool). I though it was a ZFS problem, but it turns out zfs was fine, and just this combination of hardware / drivers is not working correctly. I can provide unlimited access to this hardware remotely to any developer willing to try and fix this. Thank you very much >How-To-Repeat: Try to install freebsd 7 amd64 on a tyan broadcom chipset machine, with the onboard SATA controller in SATA mode, or PATA mode. >Fix: none known >Release-Note: >Audit-Trail: >Unformatted: