From: Meelis Roos <mroos@linux.ee>
To: Jan Kara <jack@suse.cz>
Cc: Matthew Wilcox <willy@infradead.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
linux-alpha@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, linux-mm@kvack.org
Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28
Date: Thu, 21 Feb 2019 01:23:50 +0200 [thread overview]
Message-ID: <2381c264-92f5-db43-b6a5-8e00bd881fef@linux.ee> (raw)
In-Reply-To: <20190220094813.GA27474@quack2.suse.cz>
>> First, I found out that both the problematic alphas had memory compaction and
>> page migration and bounce buffers turned on, and working alphas had them off.
>>
>> Next, turing off these options makes the problematic alphas work.
>
> OK, thanks for testing! Can you narrow down whether the problem is due to
> CONFIG_BOUNCE or CONFIG_MIGRATION + CONFIG_COMPACTION? These are two
> completely different things so knowing where to look will help. Thanks!
Tested both.
Just CONFIG_MIGRATION + CONFIG_COMPACTION breaks the alpha.
Just CONFIG_BOUNCE has no effect in 5 tries.
--
Meelis Roos
next prev parent reply other threads:[~2019-02-20 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb63a4d0-d124-21c8-7395-90b34b57c85a@linux.ee>
2019-02-10 20:27 ` ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28 Meelis Roos
2019-02-15 16:59 ` Meelis Roos
2019-02-16 17:45 ` Theodore Y. Ts'o
2019-02-16 22:29 ` Meelis Roos
2019-02-18 12:02 ` Jan Kara
2019-02-18 12:37 ` Meelis Roos
2019-02-19 12:17 ` Meelis Roos
2019-02-19 13:20 ` Jan Kara
2019-02-19 13:49 ` Meelis Roos
2019-02-19 14:44 ` Matthew Wilcox
2019-02-20 6:31 ` Meelis Roos
2019-02-20 9:48 ` Jan Kara
2019-02-20 23:23 ` Meelis Roos [this message]
2019-02-21 13:29 ` Jan Kara
2022-08-25 15:05 ` matoro
2022-08-26 10:55 ` Jan Kara
2022-08-26 11:04 ` Vlastimil Babka
2022-08-26 16:16 ` matoro
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=2381c264-92f5-db43-b6a5-8e00bd881fef@linux.ee \
--to=mroos@linux.ee \
--cc=jack@suse.cz \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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 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).