From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Vasiliy Tolstov <v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org>
Cc: Or Gerlitz <or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jack Morgenstein
<jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Subject: Re: Need help with strange mlx4_core error
Date: Sat, 01 Mar 2014 13:50:33 +0100 [thread overview]
Message-ID: <5311D799.2090607@acm.org> (raw)
In-Reply-To: <CACaajQuQ+mbwhp4jxUt+9r4Rq=14oBUqC-=xx6J3EGpAfecG-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/28/14 19:35, Vasiliy Tolstov wrote:
> [292670.940309] WARNING: at
> /tmp/buildd/linux-3.10.11/net/sched/sch_generic.c:255
> dev_watchdog+0xe3/0x153()
> [292670.940359] NETDEV WATCHDOG: ib0 (mlx4_core): transmit queue 0 timed out
I'm not sure but I think there is a fix in kernel 3.11 for this issue.
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:[~2014-03-01 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 3:35 Need help with strange mlx4_core error Vasiliy Tolstov
[not found] ` <CAJZOPZJmdGutUQZ4icBrKRq-YPwD8TqtoLH9SgqNVx_CDjL0TQ@mail.gmail.com>
[not found] ` <CAJZOPZJmdGutUQZ4icBrKRq-YPwD8TqtoLH9SgqNVx_CDjL0TQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-03 7:27 ` Vasiliy Tolstov
[not found] ` <CACaajQtHzF9g2kp9MrAaQsvKUQdr10YVa+Np1danmAcR_rvLqg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-03 10:54 ` Or Gerlitz
2014-02-03 21:19 ` Vasiliy Tolstov
[not found] ` <CACaajQs9ANqLX7m=TcR2wT6wkiS-M5uVvAnQrvGWPmukZnLqcg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-04 14:19 ` Vasiliy Tolstov
[not found] ` <CACaajQuRzBy3oV+-3+NjyE9muGKPN3YQUd5wnkkcoak0GSP=uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-28 18:24 ` Vasiliy Tolstov
[not found] ` <CACaajQtKvihFu6X-+9N3VvVKK4Jw3eADBOENhuM+-4s8s=PsUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-28 18:35 ` Vasiliy Tolstov
[not found] ` <CACaajQuQ+mbwhp4jxUt+9r4Rq=14oBUqC-=xx6J3EGpAfecG-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-01 12:50 ` Bart Van Assche [this message]
[not found] ` <5311D799.2090607-HInyCGIudOg@public.gmane.org>
2014-03-01 16:55 ` Vasiliy Tolstov
[not found] ` <CACaajQuPrAFNAR8d4NphuVRH+pVGC-Yv=afS1cbkrg=48M8ROg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-01 17:16 ` Vasiliy Tolstov
[not found] ` <CACaajQuXn5+-KQh_XtB3bb-1q9C+5ezAEh26C1TYT=5ncYJvCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-01 17:23 ` Bart Van Assche
[not found] ` <531217AD.3030807-HInyCGIudOg@public.gmane.org>
2014-03-01 20:06 ` Vasiliy Tolstov
-- strict thread matches above, loose matches on Subject: below --
2014-06-26 16:59 Mark Lehrer
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=5311D799.2090607@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=v.tolstov-+9FY0jupvH6HXe+LvDLADg@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.