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

Am Donnerstag, 20. Dezember 2018, 14:07:45 CET schrieb Martin Townsend:
> Hi Richard,
> 
> On Thu, Dec 20, 2018 at 10:54 AM Richard Weinberger
> <richard.weinberger@gmail.com> wrote:
> >
> > On Thu, Dec 20, 2018 at 10:49 AM Martin Townsend
> > <mtownsend1973@gmail.com> wrote:
> > > 5 locks held by programmingapp/930:>  #0:  (&mm->mmap_sem){......}, at: [<80113ef0>] do_page_fault+0xb8/0x350
> > >  #1:  (&le->mutex){......}, at: [<80568150>] ubi_eba_read_leb+0x34/0x438
> > >  #2:  (of_dma_lock){......}, at: [<804ab890>]
> > > of_dma_request_slave_channel+0x140/0x228
> > >  #3:  (dma_list_mutex){......}, at: [<804a9d3c>] __dma_request_channel+0x24/0x8c
> > >  #4:  (cma_mutex){......}, at: [<80246814>] cma_alloc+0xc8/0x29c
> >
> > The system seems to block in CMA, therefore make_reservation() does not make any
> > progress and all write back blocks too.
> > Do you have CONFIG_MIGRATION enabled?
> >
> > If possible, enable LOCKDEP, it can give us more details what is going on.
> >
> > --
> > Thanks,
> > //richard
> 
> I just checked and CONFIG_MIGRATION=y.

Hmm, that should be ok.
I expected CONFIG_MIGRATION=n.

In the meanwhile you can also try that patch:
http://lists.infradead.org/pipermail/linux-mtd/2018-December/086389.html

It fixes allocation failures of CMA.
But I'm not sure whether you're facing the same problem.

> Interesting that it seems to block in the CMA, could it be that the
> programmingapp process has used up all the CMA memory?  I'll ask for a
> complete log file.

I don't know what the system is doing.
Does it really(!) deadlock or does it just take very long to continue?
(Lockdep should be able to tell...)

The MTD driver seems to do DMA which uses CMA to allocate memory.
So we need to understand why the CMA allocation blocks (forever?).
>From the current picture I cannot tell whether UBIFS is the root cause
or just a victim.

Thanks,
//richard

  reply	other threads:[~2018-12-20 13:15 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 [this message]
2018-12-20 14:19       ` Martin Townsend
2018-12-20 14:28         ` Richard Weinberger
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=2102406.fBQmoxhIU4@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.