From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 196223] jdb2 journal - hung after suspend-resume test
Date: Mon, 10 Jul 2017 12:58:31 +0000 [thread overview]
Message-ID: <bug-196223-13602-RXtzCr66F1@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 #18 from Tomi Sarvela (tomi.p.sarvela@intel.com) ---
I managed to reproduce the bug on next-20170626 and earlier by running
igt@gem_exec_suspend@basic-s3 test back-to-back, takes ~5 runs. Later
next-kernels reproduce this issue on 1-2 runs.
./scripts/run-tests.sh -vt igt@gem_exec_suspend@basic-s3 -x devices
Issue is seen when igt test returns 'pass', but doesn't drop back to command
line. Repeated Ctrl-C gets to the command prompt. Cached commands work, but
anything that needs disk access doesn't.
linus-v4.12 handled ~10 runs without a problem, then same issue.
Dmesg shows in usual case something like:
[ 137.351829] nvme nvme0: I/O 197 QID 0 timeout, disable controller
[ 137.464115] nvme nvme0: failed to set APST feature (-4)
[ 137.861403] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:322: I/O error
10 writing to inode 1453376 (offset 0 size 4096 starting block 5949696)
[ 137.861406] Buffer I/O error on device nvme0n1p2, logical block 5818368
I'm concerned about the 'disable controller' part.
Setup on this testing: KBL-7700K on MSI Z170 mb. Ubuntu base, Intel 600p M.2,
one DP connected to monitor.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-07-10 12:58 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
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 [this message]
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-RXtzCr66F1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.