All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Martin Townsend <mtownsend1973@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: hung task detected in ubifs
Date: Thu, 20 Dec 2018 15:28:45 +0100	[thread overview]
Message-ID: <3974794.HFKrkWXeJj@blindfold> (raw)
In-Reply-To: <CABatt_zp8nzfbCBowr81ZPt48uVJk8pGHstZg6paLu6WHxK+Fw@mail.gmail.com>

Am Donnerstag, 20. Dezember 2018, 15:19:24 CET schrieb Martin Townsend:
> The hung task timeout is the default 2 minutes and it's setup to panic
> so I don't know if it recovers. I'll ask them to try a longer value or
> disable the panic and see if it recovers.

Yes, please.

> I checked and LOCKDEP=y and the held locks are in the original trace.
> Are there particular locking checks you would like? Currently its
> setup like this:
>   │ │    [*] RT Mutex debugging, deadlock detection
>   │ │    -*- Spinlock and rw-lock debugging: basic checks
>   │ │    -*- Mutex debugging: basic checks
>   │ │    [ ] Wait/wound mutex debugging: Slowpath testing
>   │ │    [*] Lock debugging: detect incorrect freeing of live locks
>   │ │    [ ] Lock debugging: prove locking correctness

Hmm, this should be okay.
So it does not look like a traditional deadlock.

Basically we need to figure why and where exactly cma_alloc() hangs.
And of course also we need to know if it is really cma_alloc().

Can you please dig into that?

Thanks,
//richard

  reply	other threads:[~2018-12-20 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  9:49 hung task detected in ubifs Martin Townsend
2018-12-20 10:54 ` Richard Weinberger
2018-12-20 13:07   ` Martin Townsend
2018-12-20 13:15     ` Richard Weinberger
2018-12-20 14:19       ` Martin Townsend
2018-12-20 14:28         ` Richard Weinberger [this message]
2018-12-20 15:04           ` Martin Townsend
2018-12-20 15:42             ` Richard Weinberger
2018-12-20 17:03               ` Martin Townsend
2018-12-20 19:29                 ` Richard Weinberger

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=3974794.HFKrkWXeJj@blindfold \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mtownsend1973@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.