From: Sebastian Herbszt <herbszt@gmx.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-scsi@vger.kernel.org,
Bart Van Assche <bart.vanassche@sandisk.com>,
Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kworker/1:1:29]
Date: Sun, 3 Jan 2016 19:03:41 +0100 [thread overview]
Message-ID: <20160103190341.0000387b@localhost> (raw)
In-Reply-To: <20160103114628.GA10582@lst.de>
Christoph Hellwig wrote:
> 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?
Do you mean the following patch?
"[PATCH v2] Separate target visibility from reaped state information" [1]
I can give it a try but it will likely take a few days.
[1] http://marc.info/?l=linux-scsi&m=144771953020415&w=2
Sebastian
next prev parent reply other threads:[~2016-01-03 18:03 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
2016-01-03 18:03 ` Sebastian Herbszt [this message]
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=20160103190341.0000387b@localhost \
--to=herbszt@gmx.de \
--cc=bart.vanassche@sandisk.com \
--cc=hch@lst.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 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.