Date: Thu, 8 Sep 2005 12:39:30 -0700
From: Andrew Morton <akpm@osdl.org>
To: Michael Thonke <iogl64nx@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-mm2
Message-Id: <20050908123930.5a28f3ff.akpm@osdl.org>
In-Reply-To: <432072C5.8020200@gmail.com>
References: <20050908053042.6e05882f.akpm@osdl.org>
	<432072C5.8020200@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1396
Lines: 36

Michael Thonke <iogl64nx@gmail.com> wrote:
>
> Hello Andrew,
> 
> I found a problem regarding to multi device support (Linux software Raid).
> 
> The problem first appears now in 2.6.13-mm2, that the kernel didn't initialize the md devices.
> 
> 2.6.13-mm1 works very well, and everything is okay.
> 
> Also one strange thing I found was that my SATA devices were initialized a-sync/disordered e.g
> 
> SATA1 with one hdd then something like USB and IPv4 and such and at least SATA3: with 2nd hdd.
> That I've never seen this order init order before. Seems to be mixed all around.
> 
> I tried irqpoll,pci=routeirq with no success.
> 
> I can't provide some logs, because I can't grep the dmesg since it doesn't boot.
> 
> There are changes in libata driver for sata_nv? Or md driver changes that cause that?
> 

There are changes to both sata_nv and to md in 2.6.13-mm2.  To isolate them
it would be great of you could apply 

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/broken-out/linus.patch

to 2.6.13 and see if the problem still happens.  That will separate out the
md changes which are still in -mm.

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/