linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Arthur Marsh <arthur.marsh@internode.on.net>
Cc: shli@kernel.org, neilb@suse.de, linux-kernel@vger.kernel.org
Subject: Re: git-bisect points to block: discard granularity might not be power of 2
Date: Thu, 20 Dec 2012 14:40:22 +0100	[thread overview]
Message-ID: <50D31546.7020402@kernel.dk> (raw)
In-Reply-To: <5806f82593938f8c5ec753ef9f1f27cbc5508ddc@webmail.internode.on.net>

On 2012-12-20 14:33, Arthur Marsh wrote:
> Hi,
>       one of my machines is locking up fairly early in the boot process (about 1.4 seconds in) with recent kernels and a git-bisect lead to:
> commit 8dd2cb7e880d2f77fba53b523c99133ad5054cfd
> 
> Author: Shaohua Li <shli@kernel.org>
> Date:   Fri Dec 14 11:15:36 2012 +0800
> 
>     block: discard granularity might not be power of 2
> 
>     In MD raid case, discard granularity might not be power of 2, for example, a
>     4-disk raid5 has 3*chunk_size discard granularity. Correct the calculation for
>     such cases.
> 
>     Reported-by: Neil Brown <neilb@suse.de>
>     Signed-off-by: Shaohua Li <shli@fusionio.com>
>     Signed-off-by: Jens Axboe <axboe@kernel.dk>
> 
> The machine is a dual core Pentium IV with 2 IDE and one SCSI disk. I've tried pulling the SCSI card out and the problem still occurs.
> 
> There are no software raid arrays assembled in the boot process.
> 
> Short of taking a photo of the monitor with the dump on it I'm a bit stuck as to what to do to further identify the problem.

Should be fixed in Linus' tree as-of yesterday. So please try that and
report back if it doesn't work.

-- 
Jens Axboe


           reply	other threads:[~2012-12-20 13:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5806f82593938f8c5ec753ef9f1f27cbc5508ddc@webmail.internode.on.net>]

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=50D31546.7020402@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=arthur.marsh@internode.on.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=shli@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).