linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jurriaan on adsl-gate <thunder7@xs4all.nl>
To: Neil Brown <neilb@suse.de>
Cc: Jurriaan <thunder7@xs4all.nl>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-mm3 hangs during boot (raid related?)
Date: Thu, 12 Jan 2006 18:29:00 +0100	[thread overview]
Message-ID: <20060112172900.GA3687@gates.of.nowhere> (raw)
In-Reply-To: <17349.63738.220760.681335@cse.unsw.edu.au>

From: Neil Brown <neilb@suse.de>
Date: Thu, Jan 12, 2006 at 05:36:42PM +1100
Sent-To: 
> On Thursday January 12, thunder7@xs4all.nl wrote:
> > 
> > 2.6.15-mm3 hangs during boot for me, after the lines
> > 
> > ========
> > md4: bitmap initialized from disk: read 15/15 pages, set 51 bits, status: 0
> > created bitmap (224 pages) for device md4
> > ========
> > 
> > ctrl-alt-del to reboot works sometimes (2 out of 3). Below is complete
> > dmesg (from 2.6.15-mm2, ver_linux output, .config and raid details).
> 
> Yep, this is probably a known problem with recent changes to the
> 'barrier' code.
> 
> Try to convince md not to use barrier by changing md_super_write in
> drivers/md/md.c.  Simply remove
> 
> 	if (!test_bit(BarriersNotsupp, &rdev->flags)) {
> 		struct bio *rbio;
> 		rw |= (1<<BIO_RW_BARRIER);
> 		rbio = bio_clone(bio, GFP_NOIO);
> 		rbio->bi_private = bio;
> 		rbio->bi_end_io = super_written_barrier;
> 		submit_bio(rw, rbio);
> 	} else
> 
> leaving the
> 		submit_bio(rw, rbio);
> 
> which comes after it.
> 
With this patch, it boots and works just fine.

Kind regards,
Jurriaan
-- 
His pride could withstand anything. He simply wouldn't care.
	Melanie Rawn - Skybowl
Debian (Unstable) GNU/Linux 2.6.15-mm3 2x4802 bogomips 0.31

  reply	other threads:[~2006-01-12 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  6:23 2.6.15-mm3 hangs during boot (raid related?) Jurriaan on adsl-gate
2006-01-12  6:36 ` Neil Brown
2006-01-12 17:29   ` Jurriaan on adsl-gate [this message]
2006-01-12 18:05     ` Jens Axboe

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=20060112172900.GA3687@gates.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).