From: Christoph Hellwig <hch@lst.de>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworker/1:1:29]
Date: Sun, 3 Jan 2016 12:46:28 +0100 [thread overview]
Message-ID: <20160103114628.GA10582@lst.de> (raw)
In-Reply-To: <20151231180415.00000bfc@localhost>
On Thu, Dec 31, 2015 at 06:04:15PM +0100, Sebastian Herbszt wrote:
> I still get this on 4.4.0-rc7-1.g276c9f4-default. Since this did not
> happen on 4.3 I checked the scsi changes and found the following commit:
>
> scsi: restart list search after unlock in scsi_remove_target
>
> Christoph, can it cause this issue?
Apparently yes. Bad hard a patch to avoid this when he resubmitted
my patch, which for some reason didn't get apply. Can you grab it
from the list archives and give it a try?
next prev parent reply other threads:[~2016-01-03 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 21:27 NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworker/1:1:29] Sebastian Herbszt
2015-12-31 17:04 ` Sebastian Herbszt
2016-01-03 11:46 ` Christoph Hellwig [this message]
2016-01-03 18:03 ` Sebastian Herbszt
2016-01-05 20:06 ` Sebastian Herbszt
2016-01-06 6:10 ` Christoph Hellwig
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=20160103114628.GA10582@lst.de \
--to=hch@lst.de \
--cc=herbszt@gmx.de \
--cc=linux-scsi@vger.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).