From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
huang ying <huang.ying.caritas@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: bisected bd4c82c22c367e is the first bad commit (was [Bug 198617] New: zswap causing random applications to crash)
Date: Mon, 5 Feb 2018 21:43:23 +0900 [thread overview]
Message-ID: <20180205124323.GB426@jagdpanzerIV> (raw)
In-Reply-To: <20180205123947.GA426@jagdpanzerIV>
On (02/05/18 21:39), Sergey Senozhatsky wrote:
> > I have successfully reproduced the issue and find the problem. The
> > following patch fix the issue for me, can you try it?
>
> That was quick ;)
>
> > ---------------------------------8<-------------------------------
> > From 4c52d531680f91572ebc6f4525a018e32a934ef0 Mon Sep 17 00:00:00 2001
> > From: Huang Ying <huang.ying.caritas@gmail.com>
> > Date: Mon, 5 Feb 2018 19:27:43 +0800
> > Subject: [PATCH] fontswap thp fix
>
> Seems to be fixing the problem on my x86 box. Executed several tests, no
> crashes were observed. Can run more tests tomorrow.
>
>
> ============================================================================
>
> Probably unrelated, but may be it is related: my X server used to hang
> sometimes (rarely) which I suspect was/is caused by nouveau driver. It,
> surprisingly, didn't hang this time around. Nouveau spitted a number
> of backtraces, but X server managed to survive it. Any chance that
> nouveau-X server thing was caused by THP?
No, wait. How could it be... I don't even use frontswap usually.
Sorry for the silly question.
-ss
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-05 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180130114841.aa2d3bd99526c03c6a5b5810@linux-foundation.org>
2018-02-03 1:34 ` bisected bd4c82c22c367e is the first bad commit (was [Bug 198617] New: zswap causing random applications to crash) Sergey Senozhatsky
2018-02-03 2:38 ` Sergey Senozhatsky
2018-02-04 14:21 ` huang ying
2018-02-05 1:37 ` Sergey Senozhatsky
2018-02-05 1:42 ` Huang, Ying
2018-02-05 12:00 ` Huang, Ying
2018-02-05 12:39 ` Sergey Senozhatsky
2018-02-05 12:43 ` Sergey Senozhatsky [this message]
2018-02-06 0:24 ` Andrew Morton
2018-02-06 0:31 ` Huang, Ying
2018-02-06 2:31 ` Sergey Senozhatsky
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=20180205124323.GB426@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=huang.ying.caritas@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sjenning@redhat.com \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.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 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).