From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Joseph Glanville
<joseph.glanville-2MxvZkOi9dvvnOemgxGiVw@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
scst-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Kernel panic under 3.2.14 Xen dom0 and SCST trunk
Date: Tue, 24 Jul 2012 19:59:47 +0000 [thread overview]
Message-ID: <500EFEB3.5020806@acm.org> (raw)
In-Reply-To: <CAOzFzEiiiEsUqLjRM-TFsVZhQyvQi=abX0ufS6obvuZxtWgB-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 07/24/12 19:50, Joseph Glanville wrote:
> On 25 July 2012 03:53, Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org> wrote:
>> On 07/24/12 15:16, Joseph Glanville wrote:
>>> I have been seeing this KP occur about every 3 days on our staging cluster.
>>> I am not exactly sure what the root cause would be.. I assume this
>>> would be a bug in SCST.
>>> The kernel is a 3.2.14 with Ubuntu patch series applied and Bart's SRP
>>> HA patches.
>>
>> It would help if you could tell us a bit more about your setup. It looks
>> like SCST is running in dom0, and an IB workload in domU ? If so, which
>> workload was running in domU ?
>
> There is no IB workload in the domU's.
> In this particular case there are 2 dom0s connected together both
> acting as SRP targets and initators.
> Their are sometimes vms running on these dom0s but they aren't
> currently in production so they aren't doing very much at the moment.
>
> The workload is typically one of adding and removing luns to
> ini_groups, rescan the host to ensure they are removed cleanly etc.
> As far as I can tell this would have to manifest as a race condition
> as it can go for about 2 or so weeks without occuring.
> Also worth noting is that I have a similar setup running on 2.6.32
> with no issues also a pvops dom0 using SCST and ib_srp.
>
> Could it be your patch series introduced the bug? Those are the only
> patches we have in our tree that effect SRP.
You might be hitting a device removal bug in the SCSI core. It would be
appreciated if you could retest with the srp-ha branch of this kernel
tree: http://github.com/bvanassche/linux. That tree contains Linux
kernel 3.5 + SCSI 3.6-rc1 + latest (yet to be posted) srp-ha patch series.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-24 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 15:16 Kernel panic under 3.2.14 Xen dom0 and SCST trunk Joseph Glanville
2012-07-24 15:43 ` Joseph Glanville
[not found] ` <CAOzFzEjDHpTROUcKg9cOZkNSX1LnShSombgt26+VOptVdy5i-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-02 11:04 ` Bart Van Assche
[not found] ` <501A5EB0.4060904-HInyCGIudOg@public.gmane.org>
2012-08-02 15:45 ` Joseph Glanville
2012-08-02 20:12 ` David Dillow
[not found] ` <1343938328.25205.17.camel-zHLflQxYYDO4Hhoo1DtQwJ9G+ZOsUmrO@public.gmane.org>
2012-08-02 22:51 ` Joseph Glanville
2012-08-03 11:12 ` Bart Van Assche
2012-07-24 17:53 ` Bart Van Assche
[not found] ` <500EE108.2090605-HInyCGIudOg@public.gmane.org>
2012-07-24 19:50 ` Joseph Glanville
[not found] ` <CAOzFzEiiiEsUqLjRM-TFsVZhQyvQi=abX0ufS6obvuZxtWgB-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-24 19:52 ` Joseph Glanville
2012-07-24 19:59 ` Bart Van Assche [this message]
[not found] ` <500EFEB3.5020806-HInyCGIudOg@public.gmane.org>
2012-07-24 20:14 ` Joseph Glanville
[not found] ` <CAOzFzEi8rnbTyomWEByJL3J_7QnCJSj-yWhMdh8d5mHnBRLVzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-25 1:09 ` Joseph Glanville
2012-07-25 2:30 ` Roland Dreier
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=500EFEB3.5020806@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=joseph.glanville-2MxvZkOi9dvvnOemgxGiVw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=scst-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.