From: guenther@tum.de (Stephan Günther)
Subject: nvme: controller resets
Date: Tue, 10 Nov 2015 15:30:43 +0100 [thread overview]
Message-ID: <33aa688b8da3f41960d36e66aa1703d8@localhost> (raw)
Hello,
recently we submitted a small patch that enabled support for the Apple
NVMe controller. More testing revealed some interesting behavior we
cannot explain:
1) Formatting a partition as vfat or ext2 works fine and so far,
arbitrary loads are handled correctly by the controller.
2) ext3/4 fails, but may be not immediately.
3) mkfs.btrfs fails immediately.
The error is the same every time:
| nvme 0000:03:00.0: Failed status: 3, reset controller
| nvme 0000:03:00.0: Cancelling I/O 38 QID 1
| nvme 0000:03:00.0: Cancelling I/O 39 QID 1
| nvme 0000:03:00.0: Device not ready; aborting reset
| nvme 0000:03:00.0: Device failed to resume
| blk_update_request: I/O error, dev nvme0n1, sector 0
| blk_update_request: I/O error, dev nvme0n1, sector 977104768
| Buffer I/O error on dev nvme0n1p3, logical block 120827120, async page read
While trying to isolate the problem we found that running 'partprobe -d'
also causes the problem.
So we attached strace to determine the failing ioctl/syscall. However,
running 'strace -f partprobe -d' suddenly worked fine. Similar to that
'strace -f mkfs.btrfs' worked. However, mounting the file system caused
the problem again.
Due to the different behavior with and without strace we assume there
could be some kind of race condition.
Any ideas how we can track the problem further?
Best,
Stephan
next reply other threads:[~2015-11-10 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 14:30 Stephan Günther [this message]
2015-11-10 15:51 ` nvme: controller resets Keith Busch
2015-11-10 20:45 ` Stephan Günther
2015-11-10 21:16 ` Vedant Lath
2015-11-10 21:34 ` Stephan Günther
2015-11-10 21:43 ` Vedant Lath
2015-11-10 22:02 ` Stephan Günther
2015-11-10 22:28 ` Vedant Lath
2015-11-11 21:56 ` Vedant Lath
2015-11-11 22:09 ` Stephan Günther
2015-11-12 14:02 ` Vedant Lath
2015-11-11 22:14 ` Keith Busch
2015-11-12 9:45 ` Vedant Lath
2015-11-12 11:26 ` Vedant Lath
2015-11-16 21:33 ` Stephan Günther
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=33aa688b8da3f41960d36e66aa1703d8@localhost \
--to=guenther@tum.de \
/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).