linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Darcy <kernel-lists@projecthugo.co.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patch] 2.6.x libata fix
Date: Wed, 11 Jan 2006 10:18:46 +0000	[thread overview]
Message-ID: <43C4DB86.7030603@projecthugo.co.uk> (raw)
In-Reply-To: <20060109171104.GA25793@havoc.gtf.org>

Jeff Garzik wrote:

>Please pull from 'upstream-linus' branch of
>master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
>to receive the following updates:
>
> drivers/scsi/sata_nv.c |   30 ++++++++++++++++++++++++------
> 1 files changed, 24 insertions(+), 6 deletions(-)
>
>Andrew Chew:
>      sata_nv, spurious interrupts at system startup with MAXTOR 6H500F0 drive
>
>diff --git a/drivers/scsi/sata_nv.c b/drivers/scsi/sata_nv.c
>index c0cf52c..bbbb55e 100644
>--- a/drivers/scsi/sata_nv.c
>+++ b/drivers/scsi/sata_nv.c
>
> <snip reset of patch>
>  
>
Hi Jeff, et all

I pulled this down last night from 
git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
as I don't have an account on master.kernel.org, I assume these are the 
same physical tree.

This built fine and seemed aware of all the SATA disks on my controller 
(as did previous git branches).

Again using my raid5 (7 disks 1.4tb) example, I am unable to build an 
array without the machine hanging.

I am able to access the individual disks for a short period of time 
before the box hangs totally which I assume is why the raid array will 
not build as the access for the disks hangs, not the actual building of 
the array.

I havn't got any output yet on the errors (if there are any) as I left 
the array building overnight (300+ minutes) and when I woke up this 
morning the box had hung, but power saver had come on the screen so I 
couldn't see the messages.

I'll do another test this afternoon and try to get some output for you, 
but I just thought I'd let you know this was coming.

Aslo FYI: I'm using maxtor SATA disks, so your patch was of particular 
interesting to me.

Many thanks,

Matt




  reply	other threads:[~2006-01-11 10:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 17:11 [git patch] 2.6.x libata fix Jeff Garzik
2006-01-11 10:18 ` Matt Darcy [this message]
2006-01-12 10:01   ` Matt Darcy
2006-01-12 10:57     ` PFC
2006-01-13  9:26       ` Matt Darcy
2006-01-12 11:46     ` Matt Darcy
2006-01-13 11:26       ` [git patch] 2.6.x libata fix more information (sata_mv problems continued) Matt Darcy
2006-01-13 11:42         ` Jens Axboe
2006-01-13 17:14         ` Sebastian Kuzminsky
2006-01-13 19:51           ` Matt Darcy
2006-01-13 21:06             ` [git patch] 2.6.x libata fix more information DEBUG INFO !!! Matt Darcy
  -- strict thread matches above, loose matches on Subject: below --
2005-12-04  1:57 [git patch] 2.6.x libata fix Jeff Garzik
2005-08-30  4:49 Jeff Garzik
2005-07-29  6:31 Jeff Garzik
2005-06-27 12:21 Jeff Garzik
2005-05-26 16:56 Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43C4DB86.7030603@projecthugo.co.uk \
    --to=kernel-lists@projecthugo.co.uk \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).