From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 196223] jdb2 journal - hung after suspend-resume test
Date: Mon, 03 Jul 2017 13:49:12 +0000 [thread overview]
Message-ID: <bug-196223-13602-Kk2U7tC61O@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196223-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196223
--- Comment #5 from Marta Löfstedt (marta.lofstedt@intel.com) ---
Unfortunately, this is not a fast way to bisect. Running the testlist takes ~20
minutes. I usually hit the issue on the second repetition and usually on a
suspend-resume related tests. So, I am still searching for a reasonably new
good commit to start git bisect.
4.12.0-rc7-next-20170703 is bad
4.12.0-rc7-next-20170628 is bad
I will spin 4.12.0-rc7-next-20170627 over night.
Are there some fs/ext4 specific test that may give a faster reproducer?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-07-03 13:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 6:11 [Bug 196223] New: jdb2 journal - hung after suspend-resume test bugzilla-daemon
2017-06-30 7:41 ` [Bug 196223] " bugzilla-daemon
2017-06-30 7:51 ` bugzilla-daemon
2017-06-30 14:55 ` bugzilla-daemon
2017-07-03 6:15 ` bugzilla-daemon
2017-07-03 13:49 ` bugzilla-daemon [this message]
2017-07-04 5:56 ` bugzilla-daemon
2017-07-04 22:49 ` bugzilla-daemon
2017-07-05 13:12 ` bugzilla-daemon
2017-07-07 8:20 ` bugzilla-daemon
2017-07-07 14:14 ` bugzilla-daemon
2017-07-08 18:58 ` bugzilla-daemon
2017-07-08 19:22 ` bugzilla-daemon
2017-07-09 5:05 ` bugzilla-daemon
2017-07-09 5:27 ` bugzilla-daemon
2017-07-10 5:04 ` bugzilla-daemon
2017-07-10 5:10 ` bugzilla-daemon
2017-07-10 5:14 ` bugzilla-daemon
2017-07-10 12:58 ` bugzilla-daemon
2017-07-10 22:52 ` bugzilla-daemon
2017-07-11 8:12 ` bugzilla-daemon
2017-07-11 8:40 ` bugzilla-daemon
2017-07-11 9:59 ` bugzilla-daemon
2017-07-11 13:15 ` bugzilla-daemon
2017-07-11 17:17 ` bugzilla-daemon
2017-07-12 7:52 ` bugzilla-daemon
2017-07-12 14:17 ` 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=bug-196223-13602-Kk2U7tC61O@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).