* Segmentation fault when using ping6
@ 2010-10-06 20:27 ` Rogerio Pimentel
0 siblings, 0 replies; 10+ messages in thread
From: Rogerio Pimentel @ 2010-10-06 20:27 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Segmentation fault when using ping6
@ 2010-10-06 20:27 ` Rogerio Pimentel
0 siblings, 0 replies; 10+ messages in thread
From: Rogerio Pimentel @ 2010-10-06 20:27 UTC (permalink / raw)
To: netdev, linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Segmentation fault when using ping6
2010-10-06 20:27 ` Rogerio Pimentel
@ 2010-10-07 5:32 ` Baruch Siach
-1 siblings, 0 replies; 10+ messages in thread
From: Baruch Siach @ 2010-10-07 5:32 UTC (permalink / raw)
To: linux-arm-kernel
Hi Rogerio,
On Wed, Oct 06, 2010 at 05:27:29PM -0300, Rogerio Pimentel wrote:
> 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?
This seems to be a Busybox related issue. I'd suggests you to try the latest
version of Busybox (1.17.2), and if the problem persists, ask at the Busybox
mailing list. Don't forget to add strace output to your message.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Segmentation fault when using ping6
@ 2010-10-07 5:32 ` Baruch Siach
0 siblings, 0 replies; 10+ messages in thread
From: Baruch Siach @ 2010-10-07 5:32 UTC (permalink / raw)
To: Rogerio Pimentel; +Cc: netdev, linux-arm-kernel
Hi Rogerio,
On Wed, Oct 06, 2010 at 05:27:29PM -0300, Rogerio Pimentel wrote:
> 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?
This seems to be a Busybox related issue. I'd suggests you to try the latest
version of Busybox (1.17.2), and if the problem persists, ask at the Busybox
mailing list. Don't forget to add strace output to your message.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
^ permalink raw reply [flat|nested] 10+ messages in thread
* Segmentation fault when using ping6
@ 2010-10-07 12:26 ` Rogerio Pimentel
0 siblings, 0 replies; 10+ messages in thread
From: Rogerio Pimentel @ 2010-10-07 12:26 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Segmentation fault when using ping6
@ 2010-10-07 12:26 ` Rogerio Pimentel
0 siblings, 0 replies; 10+ messages in thread
From: Rogerio Pimentel @ 2010-10-07 12:26 UTC (permalink / raw)
To: linux-arm-kernel, netdev
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Segmentation fault when using ping6
2010-10-07 12:26 ` Rogerio Pimentel
@ 2010-10-07 12:36 ` Eric Dumazet
-1 siblings, 0 replies; 10+ messages in thread
From: Eric Dumazet @ 2010-10-07 12:36 UTC (permalink / raw)
To: linux-arm-kernel
Le jeudi 07 octobre 2010 ? 09:26 -0300, Rogerio Pimentel a ?crit :
> 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?
Do you have something displayed on console ? ( dmesg output )
gdb could tell you where segmentation takes place.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Segmentation fault when using ping6
@ 2010-10-07 12:36 ` Eric Dumazet
0 siblings, 0 replies; 10+ messages in thread
From: Eric Dumazet @ 2010-10-07 12:36 UTC (permalink / raw)
To: Rogerio Pimentel; +Cc: linux-arm-kernel, netdev
Le jeudi 07 octobre 2010 à 09:26 -0300, Rogerio Pimentel a écrit :
> 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?
Do you have something displayed on console ? ( dmesg output )
gdb could tell you where segmentation takes place.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Segmentation fault when using ping6
2010-10-07 12:26 ` Rogerio Pimentel
@ 2010-10-07 13:04 ` George G. Davis
-1 siblings, 0 replies; 10+ messages in thread
From: George G. Davis @ 2010-10-07 13:04 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Oct 07, 2010 at 09:26:34AM -0300, Rogerio Pimentel wrote:
> 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?
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
>
> 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
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Segmentation fault when using ping6
@ 2010-10-07 13:04 ` George G. Davis
0 siblings, 0 replies; 10+ messages in thread
From: George G. Davis @ 2010-10-07 13:04 UTC (permalink / raw)
To: Rogerio Pimentel; +Cc: linux-arm-kernel, netdev
On Thu, Oct 07, 2010 at 09:26:34AM -0300, Rogerio Pimentel wrote:
> 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?
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
>
> Thanks in advance,
>
> Rogerio Pimentel
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2010-10-07 13:04 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-06 20:27 Segmentation fault when using ping6 Rogerio Pimentel
2010-10-06 20:27 ` Rogerio Pimentel
2010-10-07 5:32 ` Baruch Siach
2010-10-07 5:32 ` Baruch Siach
-- strict thread matches above, loose matches on Subject: below --
2010-10-07 12:26 Rogerio Pimentel
2010-10-07 12:26 ` Rogerio Pimentel
2010-10-07 12:36 ` Eric Dumazet
2010-10-07 12:36 ` Eric Dumazet
2010-10-07 13:04 ` George G. Davis
2010-10-07 13:04 ` George G. Davis
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.