linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vitalywool@gmail.com>
To: "Agustín DallʼAlba" <agustin@dallalba.com.ar>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	Seth Jennings <sjenning@redhat.com>,
	 Dan Streetman <ddstreet@ieee.org>, Linux-MM <linux-mm@kvack.org>,
	 Henry Burns <henrywolfeburns@gmail.com>
Subject: Re: CRASH: General protection fault in z3fold
Date: Mon, 9 Sep 2019 09:17:33 +0200	[thread overview]
Message-ID: <CAMJBoFNiu6OMrKvMU1mF-sAX1QmGk9fq4UMsZT7bqM+QOd6cAA@mail.gmail.com> (raw)
In-Reply-To: <501f9d274cbe1bcf1056bfd06389bd9d4e00de2a.camel@dallalba.com.ar>

On Mon, Sep 9, 2019 at 2:14 AM Agustín DallʼAlba
<agustin@dallalba.com.ar> wrote:
>
> Hello,
>
> > Would you care to test with
> > https://bugzilla.kernel.org/attachment.cgi?id=284883 ? That one
> > should
> > fix the problem you're facing.
>
> Thank you, my machine doesn't crash when stressed anymore. :)

That's good to hear :) I hope the fix gets into 5.3.

> However trace 2 (__zswap_pool_release blocked for more than xxxx
> seconds) still happens.

That one is pretty new and seems to have been caused by
d776aaa9895eb6eb770908e899cb7f5bd5025b3c ("mm/z3fold.c: fix race
between migration and destruction").
I'm looking into this now and CC'ing Henry just in case.

~Vitaly

> > > > =====================================
> > > > TRACE 2: z3fold_zpool_destroy blocked
> > > > =====================================
> > > >
> > > > INFO: task kworker/2:3:335 blocked for more than 122 seconds.
> > > >       Not tainted 5.3.0-rc7-1-ARCH #1
> > > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > > > kworker/2:3     D    0   335      2 0x80004080
> > > > Workqueue: events __zswap_pool_release
> > > > Call Trace:
> > > >  ? __schedule+0x27f/0x6d0
> > > >  schedule+0x43/0xd0
> > > >  z3fold_zpool_destroy+0xe9/0x130
> > > >  ? wait_woken+0x70/0x70
> > > >  zpool_destroy_pool+0x5c/0x90
> > > >  __zswap_pool_release+0x6a/0xb0
> > > >  process_one_work+0x1d1/0x3a0
> > > >  worker_thread+0x4a/0x3d0
> > > >  kthread+0xfb/0x130
> > > >  ? process_one_work+0x3a0/0x3a0
> > > >  ? kthread_park+0x80/0x80
> > > >  ret_from_fork+0x35/0x40
>
> Kind regards.
>


  reply	other threads:[~2019-09-09  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05  4:05 CRASH: General protection fault in z3fold Agustín DallʼAlba
2019-09-05 11:55 ` Vlastimil Babka
2019-09-08 11:09   ` Vitaly Wool
2019-09-09  0:14     ` Agustín DallʼAlba
2019-09-09  7:17       ` Vitaly Wool [this message]
2019-09-09 12:44         ` Vitaly Wool
2019-09-09 17:51           ` Henry Burns
2019-09-09 22:59           ` Agustín DallʼAlba
2019-09-10  1:08             ` Henry Burns

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=CAMJBoFNiu6OMrKvMU1mF-sAX1QmGk9fq4UMsZT7bqM+QOd6cAA@mail.gmail.com \
    --to=vitalywool@gmail.com \
    --cc=agustin@dallalba.com.ar \
    --cc=ddstreet@ieee.org \
    --cc=henrywolfeburns@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=sjenning@redhat.com \
    --cc=vbabka@suse.cz \
    /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).