All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: Alexander Lyakas <alex.bolshoy@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>, liu.song.a23@gmail.com
Subject: Re: hung-task panic in raid5_make_request
Date: Mon, 13 Jan 2020 12:10:47 +0100	[thread overview]
Message-ID: <2a9e8231-c5e2-8f63-2fc4-bed24fc21959@cloud.ionos.com> (raw)
In-Reply-To: <CAGRgLy6xx5dT0StoiUNLThVknLvNUR5Emc0mEg_dnJmWth3=9A@mail.gmail.com>

Hi Alex,

On 1/12/20 8:46 AM, Alexander Lyakas wrote:
> Hi Guoqing,
>
> We have tried the proposed patch, but still hit the hung-task panic in
> the same place[1]. How can we debug this further?

Can you print the information (atomic_read(&conf->active_stripes),
conf->max_nr_stripes and conf->cache_state)  just before the
wait_event_lock_irq? Then we can verify which condition is not meet
here. Also pls dump the value of sysfs nodes, something like.

linux:/sys/block/md5/md # find -mindepth 1 -maxdepth 1 -type 
f|sort|xargs -r egrep .


BTW, could you try latest kernel? And is it possible to reproduce the panic?

Thanks,
Guoqing

  reply	other threads:[~2020-01-13 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGRgLy4Yi1HNqNO0MLq5xjRRgWe7EaByRYF5sA3fFVa1tmpNvA@mail.gmail.com>
     [not found] ` <09e8a682-3f91-6b34-58a0-235dbb130901@cloud.ionos.com>
     [not found]   ` <CAGRgLy4netkysnF6CS2MkVBp17ipZr5D4Z4wQ6B0w2XXg51OkQ@mail.gmail.com>
2020-01-12  7:46     ` hung-task panic in raid5_make_request Alexander Lyakas
2020-01-13 11:10       ` Guoqing Jiang [this message]
2020-01-13 13:58 ` Guoqing Jiang

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=2a9e8231-c5e2-8f63-2fc4-bed24fc21959@cloud.ionos.com \
    --to=guoqing.jiang@cloud.ionos.com \
    --cc=alex.bolshoy@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=liu.song.a23@gmail.com \
    /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.