public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Neil Brown <neilb@suse.de>, Grant Wilson <grant.wilson@zen.co.uk>
Subject: Re: 2.6.17-mm5 dislikes raid-1, just like mm4
Date: Sun, 02 Jul 2006 17:13:47 +1200	[thread overview]
Message-ID: <44A7560B.3050000@reub.net> (raw)
In-Reply-To: <20060701152258.bea091a6.akpm@osdl.org>


On 2/07/2006 10:22 a.m., Andrew Morton wrote:
> I assume this is still the broken-barriers bug.  Thanks for all the help on
> this, guys.  More is to be asked for, I'm afraid.
> 
> I've prepared a tree which is basically 2.6.17-mm5, only the git-scsi-misc
> and git-libata-all trees have been omitted.  It's at 
> 
> http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.17-mm5-no-sata-scsi.bz2
> 
> (That's a diff against 2.6.17)
> 
> If that kernel works, then the next step is to test
> 
> http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.17-mm5-no-scsi.bz2
> 
> which is 2.6.17-mm5 without git-scsi-misc, but with git-libata-all.

Just for kicks, after testing those two trees (see previous email) I took my 
2.6.17-mm5 without git-scsi-misc and then patched git-scsi-misc.patch back in, 
rebuilt and rebooted and noted that RAID broke again.  Reverted the patch and it 
all worked.

So I can conclude that definitely and reproduceably that's the one.........

reuben



  parent reply	other threads:[~2006-07-02  5:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060701033524.3c478698.akpm@osdl.org>
     [not found] ` <20060701142419.GB28750@tlg.swandive.local>
2006-07-01 21:30   ` 2.6.17-mm5 Andrew Morton
2006-07-01 22:26     ` 2.6.17-mm5 James Bottomley
2006-07-01 22:32       ` 2.6.17-mm5 Neil Brown
2006-07-01 22:56         ` 2.6.17-mm5 Jeff Garzik
2006-07-02  0:10           ` 2.6.17-mm5 James Bottomley
2006-07-01 22:29     ` More RAID / SATA / barrier problems [ Re: 2.6.17-mm5 ] Neil Brown
2006-07-01 22:54     ` 2.6.17-mm5 Jeff Garzik
2006-07-27 21:02     ` 2.6.17-mm5 Ming Zhang
     [not found] ` <20060701181455.GA16412@aitel.hist.no>
2006-07-01 22:22   ` 2.6.17-mm5 dislikes raid-1, just like mm4 Andrew Morton
2006-07-01 22:52     ` Jeff Garzik
2006-07-01 22:58       ` Andrew Morton
2006-07-02  4:43     ` Reuben Farrelly
2006-07-02  6:09       ` Andrew Morton
2006-07-02  5:13     ` Reuben Farrelly [this message]
2006-07-02 13:53       ` James Bottomley
2006-07-02 14:28         ` Grant Wilson
2006-07-02 15:06           ` James Bottomley
2006-07-02 15:43             ` Grant Wilson
2006-07-02 19:07               ` Helge Hafting
2006-07-03  6:52                 ` Reuben Farrelly

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=44A7560B.3050000@reub.net \
    --to=reuben-lkml@reub.net \
    --cc=akpm@osdl.org \
    --cc=grant.wilson@zen.co.uk \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=neilb@suse.de \
    /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