Segmentation fault when using ping6
Subsystems (2)
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@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@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
Le jeudi 07 octobre 2010 ? 09:26 -0300, Rogerio Pimentel a ?crit :
Quoted 20 lines
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 faultWhen 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
Quoted 4 lines
On all cases, I'm using Linux Kernel 2.6.35 (from Mainline) and Busybox 1.15.0
Does anybody have any idea?
Do you have something displayed on console ? ( dmesg output )
gdb could tell you where segmentation takes place.
Quoted 20 lines · Rogerio Pimentel
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 faultWhen 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
Quoted 4 lines
On all cases, I'm using Linux Kernel 2.6.35 (from Mainline) and Busybox 1.15.0
Does anybody have any idea?
Random guess is that you may be using a userland tuned for ARMv6 or later but trying to run that on <ARMv6 machines.
You can enable this to see what's going wrong:
config DEBUG_USER
bool "Verbose user fault messages"
help
When a user program crashes due to an exception, the kernel can print a brief message explaining what the problem was. This is sometimes helpful for debugging but serves no purpose on a production system. Most people should say N here.
In addition, you need to pass user_debug=N on the kernel command line to enable this feature. N consists of the sum of:
1 - undefined instruction events
2 - system calls
4 - invalid data aborts
8 - SIGSEGV faults
16 - SIGBUS faults
--
Regards,
George
Quoted 10 lines
Thanks in advance,
Rogerio Pimentel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel