From: Thomas Glanzmann <thomas@glanzmann.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: open-iscsi@googlegroups.com,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: some iscsi vendor has been hitting a crash
Date: Fri, 1 Nov 2013 22:28:16 +0100 [thread overview]
Message-ID: <20131101212816.GA27918@glanzmann.de> (raw)
In-Reply-To: <5273BEBF.2090008@cs.wisc.edu>
Hello Mike,
* Mike Christie <michaelc@cs.wisc.edu> [2013-11-01 15:56]:
> On a related note, some iscsi vendor has been hitting a crash with
> your tree.
I hit an 'IO stall' with the tree, but was not able to reproduce this.
Has this vendor information on it (dmesg, OOPS)? I reverted back to
RTSOS for production classes that I do not give myself, but will run the
Nab's tree as soon as I give a VMware class myself in order to reproduce
the issue and than track it down.
Cheers,
Thomas
next prev parent reply other threads:[~2013-11-01 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 22:03 scsi-mq + open-iscsi support patches..? Nicholas A. Bellinger
[not found] ` <1382997816.19256.767.camel-XoQW25Eq2zviZyQQd+hFbcojREIfoBdhmpATvIKMPHk@public.gmane.org>
2013-11-01 14:46 ` Mike Christie
[not found] ` <5273BEBF.2090008-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2013-11-01 20:37 ` Nicholas A. Bellinger
2013-11-02 16:10 ` Jayamohan Kallickal
2013-11-04 18:56 ` Nicholas A. Bellinger
2013-11-27 2:46 ` kedacomkernel
2013-11-27 18:43 ` Nicholas A. Bellinger
2013-11-01 21:28 ` Thomas Glanzmann [this message]
2013-11-01 23:14 ` some iscsi vendor has been hitting a crash Nicholas A. Bellinger
2013-11-02 4:35 ` Thomas Glanzmann
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=20131101212816.GA27918@glanzmann.de \
--to=thomas@glanzmann.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=ogerlitz@mellanox.com \
--cc=open-iscsi@googlegroups.com \
--cc=target-devel@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