From: Mike Christie <michaelc@cs.wisc.edu>
To: Jonathan McDowell <noodles@earth.li>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)
Date: Tue, 02 Oct 2012 22:46:22 -0500 [thread overview]
Message-ID: <506BB50E.7090707@cs.wisc.edu> (raw)
In-Reply-To: <20121003004309.GA2289@earth.li>
On 10/02/2012 07:43 PM, Jonathan McDowell wrote:
> Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN
> go down and come back up (due to an expected reboot) I started getting
> the following in my logs. It continues even after the array is back and
> functioning - I'm seeing:
>
> kernel:[109104.348034] BUG: soft lockup - CPU#6 stuck for 23s!
> [kworker/6:0:30692]
>
> repeated on logged in sessions and backtraces like the following (this
> is the first). I don't see the same problem under 3.5.
>
I think you need this patch
http://marc.info/?l=linux-scsi&m=134621716223056&w=2
next prev parent reply other threads:[~2012-10-03 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 0:43 Soft lockup in scsi_remove_target under 3.6 (regression from 3.5) Jonathan McDowell
2012-10-03 3:46 ` Mike Christie [this message]
2012-10-04 1:03 ` Jonathan McDowell
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=506BB50E.7090707@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=noodles@earth.li \
/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.