All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Reuben Farrelly <reuben-lkml@reub.net>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: Breakage with raid in 2.6.11-rc1-mm1 [Regression in mm]
Date: Fri, 14 Jan 2005 08:56:59 -0800	[thread overview]
Message-ID: <41E7F9DB.8070707@osdl.org> (raw)
In-Reply-To: <6.2.0.14.2.20050115014139.01dab5e0@tornado.reub.net>

Reuben Farrelly wrote:
> At 12:58 a.m. 15/01/2005, Andrew Morton wrote:
> 
>> Reuben Farrelly <reuben-lkml@reub.net> wrote:
>> >
>> > Something seems to have broken with 2.6.11-rc1-mm1, which worked ok 
>> with
>> > 2.6.10-mm3.
>> >
>> > NET: Registered protocol family 17
>> > Starting balanced_irq
>> > BIOS EDD facility v0.16 2004-Jun-25, 2 devices found
>> > md: Autodetecting RAID arrays.
>> > md: autorun ...
>> > md: ... autorun DONE.
>> > VFS: Waiting 19sec for root device...
>> > VFS: Waiting 18sec for root device...
>> > VFS: Waiting 17sec for root device...
>> > VFS: Waiting 16sec for root device...
>> > VFS: Waiting 15sec for root device...
>> > VFS: Waiting 14sec for root device...
>> > VFS: Waiting 13sec for root device...
>> > VFS: Waiting 12sec for root device...
>> > VFS: Waiting 11sec for root device...
>> > VFS: Waiting 10sec for root device...
>> > VFS: Waiting 9sec for root device...
>> > VFS: Waiting 8sec for root device...
>> > VFS: Waiting 7sec for root device...
>> > VFS: Waiting 6sec for root device...
>> > VFS: Waiting 5sec for root device...
>> > VFS: Waiting 4sec for root device...
>> > VFS: Waiting 3sec for root device...
>> > VFS: Waiting 2sec for root device...
>> > VFS: Waiting 1sec for root device...
>> > VFS: Cannot open root device "md2" or unknown-block(0,0)
>> > Please append a correct "root=" boot option
>> > Kernel panic - not syncing: VFS: Unable to mount root fs on 
>> unknown-block(0,0)
>> >
>> > The system is running 5 RAID-1 partitions, and md2 is the root as per
>> > grub.conf.  Problem seems to be that raid autodetection finds no raid
>> > partitions :(
>> >
>> > The two ST380013AS SATA drives are detected earlier in the boot, so 
>> I don't
>> > think that's the problem..
>>
>> hm, the only raidy thing we have in there is the below.  Maybe you could
>> try reverting that?
>>
>>
>> --- 25/drivers/md/raid5.c~raid5-overlapping-read-hack   2005-01-09 
>> 22:20:40.211246912 -0800
>> +++ 25-akpm/drivers/md/raid5.c  2005-01-09 22:20:40.216246152 -0800
>> @@ -232,6 +232,7 @@ static struct stripe_head *__find_stripe
>>  }
>>
>>  static void unplug_slaves(mddev_t *mddev);
>> +static void raid5_unplug_device(request_queue_t *q);
>>
>>  static struct stripe_head *get_active_stripe(raid5_conf_t *conf, 
>> sector_t sector,
>>                                              int pd_idx, int noblock)
> 
> 
> Ok the breakage occurred somewhere between 2.6.10-mm3 (works) and 
> 2.6.11-rc1 (doesn't work) ie wasn't introduced into the latest -mm 
> patchset as I first thought.
> 
> Are there any other patches that might be worth a try backing out?

Someone else reported that they had to back out this one:
waiting-10s-before-mounting-root-filesystem.patch

Can you revert that one and let us know how it goes?

-- 
~Randy

  reply	other threads:[~2005-01-14 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 10:50 Breakage with raid in 2.6.11-rc1-mm1 [Regression in mm] Reuben Farrelly
2005-01-14 11:58 ` Andrew Morton
2005-01-14 12:18   ` Reuben Farrelly
2005-01-14 12:43   ` Reuben Farrelly
2005-01-14 16:56     ` Randy.Dunlap [this message]
2005-01-15 12:21       ` Sander
     [not found] <fa.h2tu7ia.m3ir1o@ifi.uio.no>
     [not found] ` <fa.kv41q3p.1nn82gh@ifi.uio.no>
2005-01-16 11:02   ` 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=41E7F9DB.8070707@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=reuben-lkml@reub.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.