From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Mohammed Naser <mnaser-0fRLFNSEtVVWk0Htik3J/w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: iSER + CentOS 5.7 + Xen lockup
Date: Tue, 8 Nov 2011 09:35:53 +0200 [thread overview]
Message-ID: <4EB8DBD9.4000008@mellanox.com> (raw)
In-Reply-To: <CAEs876g0rRBzZN59ZWZ4AQTauVbip82BYAXVNOzahojODfO3Bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 11/8/2011 3:14 AM, Mohammed Naser wrote:
> Hello everyone, we had this server crash a couple of times because of (what seems to
> me) some iSER problems. This node runs all the default drivers that ship with CentOS 5.7
You mentioned Xen in your subject line, but later say CentOS 5.7, what
kernel are you using? is that kernel-xen-2.6.18-274.el5.x86_64.rpm or
kernel-2.6.18-274.el5.x86_64.rpm or anything else? can you provide some high
level description for what does it take to get that crash?
Or.
Also, could you run with debug prints open and in case the crash still
reproduces,
send me the kernel log (in case it becomes big, compressed offlist will
be fine...
also I guess vger.kernel.org drops attachments anyway)
You should open libiscsi2 and ib_iser logs, use
"echo 1 > /sys/module/libiscsi2/parameters/debug_libiscsi" and
"echo 2 > /sys/module/ib_iser/parameters/debug_level"
--
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
prev parent reply other threads:[~2011-11-08 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 1:14 iSER + CentOS 5.7 + Xen lockup Mohammed Naser
[not found] ` <CAEs876g0rRBzZN59ZWZ4AQTauVbip82BYAXVNOzahojODfO3Bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-08 7:35 ` Or Gerlitz [this message]
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=4EB8DBD9.4000008@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mnaser-0fRLFNSEtVVWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox