From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: [PATCH] sata_mv: Fix broken Marvell 7042 support. Date: Mon, 03 Dec 2007 12:26:48 -0500 Message-ID: <47543C58.4040106@rtr.ca> References: <4751A2DA.6030403@rtr.ca> <20071203154749.6lah7pulw8ow0s84@email.syntomax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rtr.ca ([76.10.145.34]:4898 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750763AbXLCR0u (ORCPT ); Mon, 3 Dec 2007 12:26:50 -0500 In-Reply-To: <20071203154749.6lah7pulw8ow0s84@email.syntomax.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: hp@syntomax.com Cc: "Morrison, Tom" , IDE/ATA development list , Jeff Garzik , Tejun Heo , Alan Cox hp@syntomax.com wrote: > It doesn't quite work for me, the system locks up without discernible > error messages (Highpoint RocketRaid 2300 PCIe) . The drives come up, > and immediately get hyper active, and I get dumped in an initrd busybox > shell, when I try to tail /dev/sda it hangs, pvscan doesn't find any > physical volumes for LVM, on the upside, I don't get the PCI ERROR > messages anymore :) I'll try and get netconsole to work to get a proper > log. ... Before this, you were booting from some other device, and the sata_mv mostly worked for you there, right ? Specifically, you wrote: > Now, because the chip on the thing is a Marvell 7042 I figured I just > add the PCI ID to the driver. I tried this, and, if I do not boot from > the device it does seem to work. I did however get the following errors > (a lot): > > 02:00.0 sata_mv PCI ERROR; PCI IRQ reason=0x00000000 > > I write this from memory, but the numbers are correct, sorry if they do > not EXACTLY match. > > The disk drives do work, but they are dog slow, and when I try to boot > my ubuntu 7.10 system with this driver, it hangs during boot, right > after it tried to enable my software raid volumes. > > I have tried both the 'stock' ubuntu kernel 2.6.22-14-generic (I guess > that won't mean much) but I also tried vanilla kernel.org 2.6.23.1 .. So at least that much should now be working much better for you. I have not actually ever booted from a sata_mv controller yet, so maybe there's still something peculiar about libata::sata_mv early in the boot stages ? I'm using sata_mv as a module here, but I *never* use initrd/initramfs images. They just complicate things needlessly once I know my hardware config. But it should work. I'll try booting from a sata_mv drive here on your board and see what's up. Cheers