From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"don.brace@microsemi.com" <don.brace@microsemi.com>,
"vlee@freedesktop.org" <vlee@freedesktop.org>
Subject: Re: HP ProLiant DL360p Gen8 hangs with Linux 4.13+.
Date: Fri, 5 Jan 2018 16:32:17 +0000 [thread overview]
Message-ID: <1515169935.3254.2.camel@wdc.com> (raw)
In-Reply-To: <CACKvgLEtPRpAS58kn-Skjn65-ZkDK17_cE+OzJodxQ=XvtQPGg@mail.gmail.com>
On Thu, 2018-01-04 at 14:32 -0800, Vinson Lee wrote:
> HP ProLiant DL360p Gen8 with Smart Array P420i boots to the login
> prompt and hangs with Linux 4.13 or later. I cannot log in on console
> or SSH into the machine. Linux 4.12 and older boot fine.
>
> I see these messages on the console.
>
> [ 242.843206] INFO: task scsi_eh_2:465 blocked for more than 120 seconds.
> [ 242.877835] Not tainted 4.15.0-041500rc6-generic #201712312330
It seems like something got stuck in the block layer. The traditional way to
debug this is to analyze the information that is available under
/sys/kernel/debug/block. However, since login is not possible we can't use
that approach. Would it be possible for you to check whether this has been
resolved in kernel v4.15-rc6, and if not, bisect this?
Thanks,
Bart.
next prev parent reply other threads:[~2018-01-05 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 22:32 HP ProLiant DL360p Gen8 hangs with Linux 4.13+ Vinson Lee
2018-01-05 16:32 ` Bart Van Assche [this message]
2018-01-06 20:45 ` Laurence Oberman
2018-01-11 0:52 ` Vinson Lee
2018-01-17 0:17 ` Vinson Lee
2018-01-14 23:40 ` Laurence Oberman
2018-01-15 12:17 ` Ming Lei
2018-01-15 12:51 ` Laurence Oberman
2018-01-15 15:01 ` Hellwig, Christoph
2018-01-15 16:25 ` Laurence Oberman
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=1515169935.3254.2.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=don.brace@microsemi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=vlee@freedesktop.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.