From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751071AbWDTROt (ORCPT ); Thu, 20 Apr 2006 13:14:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751183AbWDTROt (ORCPT ); Thu, 20 Apr 2006 13:14:49 -0400 Received: from EXCHG2003.microtech-ks.com ([24.124.14.122]:38619 "EHLO EXCHG2003.microtech-ks.com") by vger.kernel.org with ESMTP id S1751071AbWDTROt (ORCPT ); Thu, 20 Apr 2006 13:14:49 -0400 Message-ID: <4447C183.3040000@atipa.com> Date: Thu, 20 Apr 2006 12:14:43 -0500 From: Roger Heflin User-Agent: Thunderbird 1.5 (X11/20060313) MIME-Version: 1.0 To: Linux-Kernel Subject: sata_mv issues with more than 1 disk in FC5 2.6.16-1.2096 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Apr 2006 17:06:44.0137 (UTC) FILETIME=[CCDD5190:01C6649C] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello, I know the FC5 2.6.16-1.2096 is based off of one of the 2.6.16 stable releases. I am not sure exactly which one this is based on. I have several machines with this controller, the ones with a single disks all work correctly using the Marvell controller. An identical MB/controller/chassis fails when there are 2 disks using software mirroring. We have tested with 2 separate chassis, both exhibit the same failure. Moving the 2 disks to a different built-in sata controller (sata_nv) results in the disks and the mirror working correctly. The errors that it returns are: ata4: status=0xd0 { Busy } ata2: status=0xd0 { Busy } And the machine is terribly slow while this error is happening. The error appears to be happening when the disks are trying to be mounted. We have tested the disk on a couple of different combinations of ports and this does not seem to change anything. The single disk machines don't get this error like the 2 disk machines, though they do get this error, every 30 minutes or so (probably from smartd), but this error does not appear to be causing issues. Apr 19 16:26:19 lab229 kernel: ata1: status=0xd0 { Busy } Apr 19 16:26:19 lab229 kernel: ATA: abnormal status 0xD0 on port 0xFFFFC2001012211C Any thoughts? Roger