From: keith.busch@intel.com (Keith Busch)
Subject: Hang when running LLVM+clang test suite
Date: Sat, 20 Jan 2018 19:50:31 -0700 [thread overview]
Message-ID: <20180121025030.GK12043@localhost.localdomain> (raw)
In-Reply-To: <7F6A25BD-AA87-4800-886F-1A256FFD8967@znu.io>
On Sat, Jan 20, 2018@05:47:06AM -0500, David Zarzycki wrote:
> Hello NVMe developers,
>
> The LLVM+clang the test suite regularly (but not reliably) hangs the kernel (version 4.14.13-300.fc27.x86_64). I don?t see this hang when running the test suite in /tmp (tmpfs) or on a SATA SSD.
>
> Here are photos of the console debug info, with the NVMe driver in the backtrace:
>
> http://znu.io/dual8168hang.tar
>
> Here is another instance of the hang, again with NVMe in the backtrace:
>
> http://znu.io/IMG_0362.jpg
It looks like the scheduler is stuck or a task struct is corrupt. I can't
think of anything off the top of my head what nvme has to do with that,
though. It just invokes the callback associated with a command and
doesn't directly manipulate any scheduler structs.
next prev parent reply other threads:[~2018-01-21 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 10:47 Hang when running LLVM+clang test suite David Zarzycki
2018-01-21 2:50 ` Keith Busch [this message]
2018-01-21 13:49 ` David Zarzycki
2018-01-21 14:13 ` David Zarzycki
2018-01-22 18:37 ` Keith Busch
2018-01-22 23:33 ` David Zarzycki
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=20180121025030.GK12043@localhost.localdomain \
--to=keith.busch@intel.com \
/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