From: Dave Chinner <david@fromorbit.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [Bug 202441] Possibly vfs cache related replicable xfs regression since 4.19.0 on sata hdd:s
Date: Wed, 30 Jan 2019 08:44:05 +1100 [thread overview]
Message-ID: <20190129214405.GA4205@dastard> (raw)
In-Reply-To: <bug-202441-201763-GRtP2T87ne@https.bugzilla.kernel.org/>
On Tue, Jan 29, 2019 at 09:19:52PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=202441
>
> --- Comment #13 from Roger (rogan6710@gmail.com) ---
> Considering that rc8 which I believe was released as 4.19.0 did not show any
> problems on my 24G machine I must have managed to get a false positive on
> 4.19.0. The machine I tested that on has less ram (8G) but I don't know if that
> matters.
>
> Anyhow, after a filthy amount of copying and compiling I can say that
> something probably went wrong between 4.19.2, which is ok, and 4.19.3
> which is not, at least on this 9590.
Thank you!
We crossed streams - I was writing the email suggesting this when,
in fact, your were way ahead of me.
> I downloaded, compiled, and tested all rc versions, 4.19.{2,3,5,9} and verified
> that 4.19.{3,5,9,18} all have the problems described above on the 9590.
> All tests were done in console (nomodeset) directly after boot.
Ok, I'll have a look at the 4.19.2 -> 4.19.3 history now and see
what pops out.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-01-29 21:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 20:41 [Bug 202441] New: Possibly vfs cache related replicable xfs regression since 4.19.0 on sata hdd:s bugzilla-daemon
2019-01-28 22:00 ` Dave Chinner
2019-01-28 22:00 ` [Bug 202441] " bugzilla-daemon
2019-01-28 23:26 ` bugzilla-daemon
2019-01-29 0:29 ` Dave Chinner
2019-01-29 0:29 ` bugzilla-daemon
2019-01-29 0:43 ` bugzilla-daemon
2019-01-29 1:23 ` Dave Chinner
2019-01-29 0:47 ` bugzilla-daemon
2019-01-29 1:23 ` bugzilla-daemon
2019-01-29 3:36 ` bugzilla-daemon
2019-01-29 9:09 ` bugzilla-daemon
2019-01-29 9:11 ` bugzilla-daemon
2019-01-29 9:27 ` bugzilla-daemon
2019-01-29 9:29 ` bugzilla-daemon
2019-01-29 17:55 ` bugzilla-daemon
2019-01-29 21:41 ` Dave Chinner
2019-01-29 21:19 ` bugzilla-daemon
2019-01-29 21:44 ` Dave Chinner [this message]
2019-01-29 21:41 ` bugzilla-daemon
2019-01-29 21:53 ` Dave Chinner
2019-01-29 21:44 ` bugzilla-daemon
2019-01-29 21:53 ` bugzilla-daemon
2019-01-29 22:07 ` bugzilla-daemon
2019-01-29 22:19 ` bugzilla-daemon
2019-01-29 22:23 ` bugzilla-daemon
2019-01-29 22:39 ` bugzilla-daemon
2019-01-29 23:03 ` bugzilla-daemon
2019-01-29 23:28 ` Dave Chinner
2019-01-29 23:28 ` bugzilla-daemon
2019-01-29 23:35 ` bugzilla-daemon
2019-01-30 10:50 ` bugzilla-daemon
2019-01-30 12:00 ` bugzilla-daemon
2019-02-01 21:59 ` bugzilla-daemon
2019-02-03 8:12 ` bugzilla-daemon
2021-11-23 15:43 ` bugzilla-daemon
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=20190129214405.GA4205@dastard \
--to=david@fromorbit.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@vger.kernel.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).