From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S940750AbXGaDxR (ORCPT ); Mon, 30 Jul 2007 23:53:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933798AbXGaDxF (ORCPT ); Mon, 30 Jul 2007 23:53:05 -0400 Received: from dsl081-058-254.sfo1.dsl.speakeasy.net ([64.81.58.254]:38520 "EHLO gutschke.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752929AbXGaDxE (ORCPT ); Mon, 30 Jul 2007 23:53:04 -0400 X-Greylist: delayed 1892 seconds by postgrey-1.27 at vger.kernel.org; Mon, 30 Jul 2007 23:53:03 EDT Message-ID: <46AEAAB1.801@gutschke.com> Date: Mon, 30 Jul 2007 20:21:21 -0700 From: Markus Gutschke User-Agent: Mozilla-Thunderbird 2.0.0.4 (X11/20070622) MIME-Version: 1.0 To: Jeff Garzik CC: Linux Kernel Mailing List Subject: Marvell 7042 (sata_mv) fails to initialize drive Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I just tried hooking up a Hitachi 1TB SATA-II drive to a Marvell 7042 based controller, and the most recent Linux kernel (2.6.23-rc1) fails to properly initialize the interface. Here are the relevant kernel messages: > kernel: [43.312417] sata_mv 0000:06:00.0: version 0.81 > kernel: [43.312752] ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16 > kernel: [43.312757] ACPI: PCI Interrupt 0000:06:00.0[A] -> Link [APC5] -> GSI 16 (level, low) -> IRQ 16 > kernel: [43.312788] sata_mv 0000:06:00.0: Applying 60X1C0 workarounds to unknown rev > kernel: [43.314443] sata_mv 0000:06:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx > kernel: [43.314535] scsi0 : sata_mv > kernel: [43.314581] scsi1 : sata_mv > kernel: [43.314614] scsi2 : sata_mv > kernel: [43.314640] scsi3 : sata_mv > kernel: [43.314660] ata1: SATA max UDMA/133 cmd 0x0000000000000000 ctl 0xffffc20003522120 bmdma 0x0000000000000000 irq 16 > kernel: [43.314663] ata2: SATA max UDMA/133 cmd 0x0000000000000000 ctl 0xffffc20003524120 bmdma 0x0000000000000000 irq 16 > kernel: [43.314666] ata3: SATA max UDMA/133 cmd 0x0000000000000000 ctl 0xffffc20003526120 bmdma 0x0000000000000000 irq 16 > kernel: [43.314669] ata4: SATA max UDMA/133 cmd 0x0000000000000000 ctl 0xffffc20003528120 bmdma 0x0000000000000000 irq 16 > kernel: [53.409086] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > kernel: [59.741602] ata1: EH pending after completion, repeating EH (cnt=4) > kernel: [59.777642] ata2: SATA link down (SStatus 0 SControl 300) > kernel: [59.809752] ata3: SATA link down (SStatus 0 SControl 300) > kernel: [59.841740] ata4: SATA link down (SStatus 0 SControl 300) The kernel never even registers the drive as an available disk device, whereas everything appears to work fine, if I connect the disk to one of the other controllers (JMicron AHCI, or NVidia sata_nv) on this motherboard. As I have two of those disks (in a RAID-1 array) and multiple independent controllers, it is relatively easy for me to do some testing here. The worst case scenario is that I need to wait a couple of hours for the array to rebuild itself after I am done experimenting. Let me know, if there is anything I can do to help you diagnose the root cause, or whether this is a known bug and you don't need any help testing at this point. Markus