From owner-freebsd-current@FreeBSD.ORG Sun Oct 31 16:37:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 844B616A4CE for ; Sun, 31 Oct 2004 16:37:57 +0000 (GMT) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F12643D1D for ; Sun, 31 Oct 2004 16:37:57 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.247.57] (helo=[192.168.99.66]) by hobbiton.shire.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1COIiK-000BEj-GJ for freebsd-current@freebsd.org; Sun, 31 Oct 2004 09:37:56 -0700 Mime-Version: 1.0 (Apple Message framework v619) Resent-Date: Sun, 31 Oct 2004 09:37:53 -0700 Message-Id: <36092952-2B5B-11D9-A439-003065A70D30@shire.net> Resent-To: freebsd-current@freebsd.org Resent-Message-Id: <1EE13F84-2B0D-11D9-A439-003065A70D30@shire.net> From: "Chad Leigh -- Shire.Net LLC" Resent-From: "Chad Leigh -- Shire.Net LLC" Date: Sun, 31 Oct 2004 01:18:53 -0600 To: FreeBSD questions list X-Mailer: Apple Mail (2.619) X-SA-Exim-Connect-IP: 67.161.247.57 X-SA-Exim-Mail-From: chad@shire.net Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on hobbiton.shire.net X-Spam-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50 autolearn=disabled version=3.0.0 X-Spam-Level: X-SA-Exim-Version: 4.1+cvs (built Mon, 23 Aug 2004 08:44:05 -0700) X-SA-Exim-Scanned: Yes (on hobbiton.shire.net) Subject: 5.3-RC1 problem with SiI 3114 (Tyan S2882 in i386 mode) with some disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 16:37:57 -0000 Hi I have a Tyan S2882 dual opteron running 5.3-RC1 (I think -- uname says 5.3-STABLE but I did it soon after RC1 came out -- I must have misread which branch to synch with). I have 1 WD 36GB Raptor SATA drive and 2 WD 200GB SATA drives. These are not the boot drives or anything. An Adaptec 2200S with 2 SCSI based RAIDs are the main boot and used disks. The SATA is for swap and backup and "play" space. The SiI 3114 is used in "ultra" mode, which is the "plain disk" mode. It is not in "raid" mode. This machine was running 5.2-CURRENT from about mid summer. The onboard SiI 3114 was not working right at the time I had last updated the system, but I did not get the following error. Under 5.2-CURRENT the Raptor and one of the 200GB drives was hooked to a Promise SATA card and the last WD card was hooked to the SiI 3114 but not used due to some problems. After I updated to 5.3 (I believe RC1 as I said above), the machine will no longer boot with the following errors (if I hook the same drives to a Promise SATA card) this is not a problem and the disks work. (This is with one disk on the SiI 3114) ata7-master: FAILURE - ATA_IDENTIFY status=51 error=4 ata7-master: FAILURE - ATA_IDENTIFY status=51 error=4 ata7-master: FAILURE - ATA_IDENTIFY timed out If I put all 3 disks on the SiI 3114 and remove the promise card, the Raptor drive is found correctly but when it goes to find the first 200GB drive, the same error pops up (the ata bus number changes) ata3-master: FAILURE - ATA_IDENTIFY status=51 error=4 ata3-master: FAILURE - ATA_IDENTIFY status=51 error=4 ata3-master: FAILURE - ATA_IDENTIFY timed out Since the drives seem to work fine with the Promise card, I think the drives are OK. It happens with both 200GB drives, in any order I put them. The 36GB Raptor does seem to be found OK at boot though. I updated the Tyan MB bios (which updated the SiI bios) to the latest available from the Tyan website and the problem still happens. Unfortunately I cannot use the Promise card in production as it is not a 2U compatible card and this is a 2U server. Up to now, since it is in testing for the last 6 months, I have left the lid slightly askew for the cables, but cannot do that when I put the machine into production, which I want to do soon, when 5.3-RELEASE comes out or soon thereafter... It seems that there is some problem in the ATA driver for this chip??? Thanks Chad _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"