From: rogerio.pimentel@freescale.com (Rogerio Pimentel)
To: linux-arm-kernel@lists.infradead.org
Subject: Segmentation fault when using ping6
Date: Wed, 6 Oct 2010 17:27:29 -0300 [thread overview]
Message-ID: <4CACDBB1.9050305@freescale.com> (raw)
Hi,
I'm having a "segmentation fault" problem when using ping6.
When testing on ARM9 platforms (i.MX25 and i.MX27), it returns the error:
root at freescale ~$ ping6 ::1
PING ::1 (::1): 56 data bytes
Segmentation fault
When testing on ARM11 and ARM Cortex A8 platforms (i.MX31 and i.MX51),
it works:
root at freescale ~$ ping6 ::1
PING ::1 (::1): 56 data bytes
64 bytes from ::1: seq=0 ttl=64 time=0.331 ms
64 bytes from ::1: seq=1 ttl=64 time=0.214 ms
64 bytes from ::1: seq=2 ttl=64 time=0.176 ms
64 bytes from ::1: seq=3 ttl=64 time=0.155 ms
On all cases, I'm using Linux Kernel 2.6.35 (from Mainline) and Busybox
1.15.0
Does anybody have any idea?
Thanks in advance,
Rogerio Pimentel
next reply other threads:[~2010-10-06 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 20:27 Rogerio Pimentel [this message]
2010-10-07 5:32 ` Segmentation fault when using ping6 Baruch Siach
-- strict thread matches above, loose matches on Subject: below --
2010-10-07 12:26 Rogerio Pimentel
2010-10-07 12:36 ` Eric Dumazet
2010-10-07 13:04 ` George G. Davis
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=4CACDBB1.9050305@freescale.com \
--to=rogerio.pimentel@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).