All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: linux-xfs@vger.kernel.org
Cc: Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: Tasks blocking forever with XFS stack traces
Date: Wed, 23 Dec 2020 08:45:52 +0000	[thread overview]
Message-ID: <CALjAwxjfTTacvGCi86atT_2SQjjKXRCNC2ta_TqxzLZ3YEstBg@mail.gmail.com> (raw)
In-Reply-To: <CALjAwxhK1OSioY1xChRRb6ruk7bGSJXMtMDRcCn=XgSmtOdFKg@mail.gmail.com>

On Wed, 13 Nov 2019 at 10:04, Sitsofe Wheeler <sitsofe@gmail.com> wrote:
>
> Nov 12 16:45:02 <host> kernel: [27678.931551] INFO: task
> kworker/50:0:20430 blocked for more than 120 seconds.
> Nov 12 16:45:02 <host> kernel: [27678.931613]       Tainted: G
>   OE     5.0.0-32-generic #34~18.04.2-Ubuntu
> Nov 12 16:45:02 <host> kernel: [27678.931667] "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Nov 12 16:45:02 <host> kernel: [27678.931723] kworker/50:0    D    0
> 20430      2 0x80000080
> Nov 12 16:45:02 <host> kernel: [27678.931801] Workqueue:
> xfs-sync/md126 xfs_log_worker [xfs]
> Nov 12 16:45:02 <host> kernel: [27678.931804] Call Trace:
> Nov 12 16:45:02 <host> kernel: [27678.931814]  __schedule+0x2c0/0x870
> Nov 12 16:45:02 <host> kernel: [27678.931819]  schedule+0x2c/0x70
> Nov 12 16:45:02 <host> kernel: [27678.931823]  schedule_timeout+0x1db/0x360
> Nov 12 16:45:02 <host> kernel: [27678.931829]  ? ttwu_do_activate+0x77/0x80
> Nov 12 16:45:02 <host> kernel: [27678.931833]  wait_for_completion+0xba/0x140
> Nov 12 16:45:02 <host> kernel: [27678.931837]  ? wake_up_q+0x80/0x80
> Nov 12 16:45:02 <host> kernel: [27678.931843]  __flush_work+0x15c/0x210

(Quite some time later) This issue went away after switching to an
Ubuntu 18.04 5.3 LTS kernel. Later kernels (e.g. 5.4) have not
manifested the issue either.

-- 
Sitsofe

      reply	other threads:[~2020-12-23  8:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  7:27 Tasks blocking forever with XFS stack traces Sitsofe Wheeler
2019-11-05  8:54 ` Carlos Maiolino
2019-11-05  9:32   ` Sitsofe Wheeler
2019-11-05 10:36     ` Carlos Maiolino
2019-11-05 11:58       ` Carlos Maiolino
2019-11-05 14:12       ` Sitsofe Wheeler
2019-11-05 16:09         ` Carlos Maiolino
2019-11-07  0:12         ` Chris Murphy
2019-11-13 10:04       ` Sitsofe Wheeler
2020-12-23  8:45         ` Sitsofe Wheeler [this message]

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=CALjAwxjfTTacvGCi86atT_2SQjjKXRCNC2ta_TqxzLZ3YEstBg@mail.gmail.com \
    --to=sitsofe@gmail.com \
    --cc=cmaiolino@redhat.com \
    --cc=linux-xfs@vger.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 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.