From: Martin Weiser <martin.weiser-CF7bWO6jhOGIrnxuYX0bhEEOCMrvLtNR@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Segmentation fault in ixgbe_rxtx_vec.c:444 with 1.8.0
Date: Mon, 19 Jan 2015 11:26:57 +0100 [thread overview]
Message-ID: <54BCDBF1.8020909@allegro-packets.com> (raw)
Hi everybody,
we quite recently updated one of our applications to DPDK 1.8.0 and are
now seeing a segmentation fault in ixgbe_rxtx_vec.c:444 after a few minutes.
I just did some quick debugging and I only have a very limited
understanding of the code in question but it seems that the 'continue'
in line 445 without increasing 'buf_idx' might cause the problem. In one
debugging session when the crash occurred the value of 'buf_idx' was 2
and the value of 'pkt_idx' was 8965.
Any help with this issue would be greatly appreciated. If you need any
further information just let me know.
Martin
next reply other threads:[~2015-01-19 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 10:26 Martin Weiser [this message]
[not found] ` <54BCDBF1.8020909-CF7bWO6jhOGIrnxuYX0bhEEOCMrvLtNR@public.gmane.org>
2015-01-20 10:39 ` Segmentation fault in ixgbe_rxtx_vec.c:444 with 1.8.0 Martin Weiser
[not found] ` <54BE3047.9060909-CF7bWO6jhOGIrnxuYX0bhEEOCMrvLtNR@public.gmane.org>
2015-01-21 13:49 ` Bruce Richardson
2015-01-22 14:05 ` Prashant Upadhyaya
[not found] ` <CAPBAu3U6D6UMrgSbzeVwXTXSMDS+K6JNpQqJF6qRAFPU-5MiSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-22 15:19 ` Bruce Richardson
2015-01-23 11:37 ` Martin Weiser
[not found] ` <54C23265.8090403-CF7bWO6jhOGIrnxuYX0bhEEOCMrvLtNR@public.gmane.org>
2015-01-23 11:52 ` Bruce Richardson
2015-01-23 14:59 ` Martin Weiser
[not found] ` <54C261EC.8000104-CF7bWO6jhOGIrnxuYX0bhEEOCMrvLtNR@public.gmane.org>
2015-02-06 13:41 ` [PATCH] ixgbe: fix vector PMD chained mbuf receive Bruce Richardson
[not found] ` <1423230068-10841-1-git-send-email-bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-02-20 11:00 ` Thomas Monjalon
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=54BCDBF1.8020909@allegro-packets.com \
--to=martin.weiser-cf7bwo6jhogirnxuyx0bheeocmrvltnr@public.gmane.org \
--cc=dev-VfR2kkLFssw@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.