Networking Forums

Networking Forums > Computer Networking > Linux Networking > ping (and others) fail above a certain size

Reply
Thread Tools Display Modes

ping (and others) fail above a certain size

 
 
Guillaume Dargaud
Guest
Posts: n/a

 
      04-21-2008, 03:59 PM
Check this out:

# ping -s 2952 192.168.1.185
PING 192.168.1.185 (192.168.1.185): 2952 data bytes
2960 bytes from 192.168.1.185: seq=0 ttl=64 time=1.580 ms
2960 bytes from 192.168.1.185: seq=1 ttl=64 time=1.321 ms
2960 bytes from 192.168.1.185: seq=2 ttl=64 time=1.351 ms
2960 bytes from 192.168.1.185: seq=3 ttl=64 time=1.363 ms
2960 bytes from 192.168.1.185: seq=4 ttl=64 time=1.349 ms

--- 192.168.1.185 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1.321/1.392/1.580 ms


# ping -s 2953 192.168.1.185
PING 192.168.1.185[ 2340.660892] ------------[ cut here ]------------
[ 2340.664293] Badness at net/core/skbuff.c:317
[ 2340.668479] **bleep**: c015bd24 LR: c015b3f4 CTR: 00000000
[ 2340.673410] REGS: c7d0fd20 TRAP: 0700 Not tainted (2.6.24-rc8-xlnx)
[ 2340.679876] MSR: 00029030 <EE,ME,IR,DR> CR: 28000048 XER: 20000000
[ 2340.686189] TASK = c7c35810[243] 'ping' THREAD: c7d0e000
[ 2340.691279] GPR00: 00000001 c7d0fdd0 c7c35810 c7d318e0 80000009 00000004
c027bd38 00000200
[ 2340.699571] GPR08: c7d0fdb8 c7d0e000 c027bd1c c0159910 c7d0fdb8 100b46f4
ffffffff 00000000
[ 2340.707864] GPR16: 10090000 100bd6e0 100b0000 100b0000 00000c11 7fbcf9a0
00000000 10004634
[ 2340.716158] GPR24: 1007d370 7fbced90 10003fbc 100adf18 00000000 00000000
c7c9e000 c7d318e0
[ 2340.724625] **bleep** [c015bd24] skb_release_all+0x6c/0x94
[ 2340.729551] LR [c015b3f4] __kfree_skb+0x18/0xc0
[ 2340.734042] Call Trace:
[ 2340.736465] [c7d0fdd0] [c0161b6c] netif_rx+0x124/0x158 (unreliable)
[ 2340.742684] [c7d0fde0] [c015b3f4] __kfree_skb+0x18/0xc0
[ 2340.747866] [c7d0fdf0] [c01466a0] SendHandler+0x44/0x94
[ 2340.753050] [c7d0fe10] [c0147284] XEmacLite_InterruptHandler+0x12c/0x140
[ 2340.759702] [c7d0fe20] [c0146078] xemaclite_interrupt+0x20/0x34
[ 2340.765577] [c7d0fe30] [c003c98c] handle_IRQ_event+0x4c/0xa0
[ 2340.771193] [c7d0fe50] [c003ca94] __do_IRQ+0xb4/0x130
[ 2340.776203] [c7d0fe70] [c0006990] do_IRQ+0x6c/0xa4
[ 2340.780954] [c7d0fe80] [c000329c] ret_from_except+0x0/0x18
[ 2340.786397] [c7d0ff40] [c0002c50] ret_from_syscall+0x0/0x3c
[ 2340.791923] Instruction dump:
[ 2340.794865] 3000ffff 7c005a2c 7c00592d 40a2fff0 817f006c 54290024
2f8b0000 419e0024
[ 2340.802549] 8009000c 5400011e 7c0000d0 54000ffe <0f000000> 7fe3fb78
7d6903a6 4e800421
(192.168.1.185): 2953 data bytes
[ 2341.832397] ------------[ cut here ]------------
[ 2341.835801] Badness at net/core/skbuff.c:317
[ 2341.839992] **bleep**: c015bd24 LR: c015b3f4 CTR: 00000000
[ 2341.844923] REGS: c7d0fd20 TRAP: 0700 Not tainted (2.6.24-rc8-xlnx)
[ 2341.851388] MSR: 00029030 <EE,ME,IR,DR> CR: 28000048 XER: 20000000
[ 2341.857702] TASK = c7c35810[243] 'ping' THREAD: c7d0e000
[ 2341.862792] GPR00: 00000001 c7d0fdd0 c7c35810 c7d31840 80000009 00000004
c027bd38 00000200
[ 2341.871084] GPR08: c7d0fdb8 c7d0e000 c027bd1c c0159910 c7d0fdb8 100b46f4
ffffffff 00000000
[ 2341.879377] GPR16: 10090000 100bd6e0 100b0000 300b4e20 00000c11 7fbcf9a0
00000000 10004634
[ 2341.887671] GPR24: 1007d370 7fbced90 10003fbc 100adf18 00000000 00000000
c7c9e000 c7d31840
[ 2341.896138] **bleep** [c015bd24] skb_release_all+0x6c/0x94
[ 2341.901064] LR [c015b3f4] __kfree_skb+0x18/0xc0
[ 2341.905555] Call Trace:
[ 2341.907978] [c7d0fdd0] [c0161b6c] netif_rx+0x124/0x158 (unreliable)
[ 2341.914197] [c7d0fde0] [c015b3f4] __kfree_skb+0x18/0xc0
[ 2341.919379] [c7d0fdf0] [c01466a0] SendHandler+0x44/0x94
[ 2341.924563] [c7d0fe10] [c0147284] XEmacLite_InterruptHandler+0x12c/0x140
[ 2341.931215] [c7d0fe20] [c0146078] xemaclite_interrupt+0x20/0x34
[ 2341.937089] [c7d0fe30] [c003c98c] handle_IRQ_event+0x4c/0xa0
[ 2341.942705] [c7d0fe50] [c003ca94] __do_IRQ+0xb4/0x130
[ 2341.947716] [c7d0fe70] [c0006990] do_IRQ+0x6c/0xa4
[ 2341.952467] [c7d0fe80] [c000329c] ret_from_except+0x0/0x18
[ 2341.957910] [c7d0ff40] [c0002c50] ret_from_syscall+0x0/0x3c
[ 2341.963436] Instruction dump:
[ 2341.966378] 3000ffff 7c005a2c 7c00592d 40a2fff0 817f006c 54290024
2f8b0000 419e0024
[ 2341.974062] 8009000c 5400011e 7c0000d0 54000ffe <0f000000> 7fe3fb78
7d6903a6 4e800421

--- 192.168.1.185 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss


What could be the problem ? MTU limits ? Packet fragmentation ? Wrong buffer
size ?
Hardware problem ?
--
Guillaume Dargaud
http://www.gdargaud.net/


 
Reply With Quote
 
 
 
 
Unruh
Guest
Posts: n/a

 
      04-21-2008, 05:09 PM
"Guillaume Dargaud" <(E-Mail Removed) t> writes:

>Check this out:


># ping -s 2952 192.168.1.185
>PING 192.168.1.185 (192.168.1.185): 2952 data bytes
>2960 bytes from 192.168.1.185: seq=0 ttl=64 time=1.580 ms
>2960 bytes from 192.168.1.185: seq=1 ttl=64 time=1.321 ms
>2960 bytes from 192.168.1.185: seq=2 ttl=64 time=1.351 ms
>2960 bytes from 192.168.1.185: seq=3 ttl=64 time=1.363 ms
>2960 bytes from 192.168.1.185: seq=4 ttl=64 time=1.349 ms


>--- 192.168.1.185 ping statistics ---
>5 packets transmitted, 5 packets received, 0% packet loss
>round-trip min/avg/max = 1.321/1.392/1.580 ms



># ping -s 2953 192.168.1.185
>PING 192.168.1.185[ 2340.660892] ------------[ cut here ]------------
>[ 2340.664293] Badness at net/core/skbuff.c:317
>[ 2340.668479] **bleep**: c015bd24 LR: c015b3f4 CTR: 00000000
>[ 2340.673410] REGS: c7d0fd20 TRAP: 0700 Not tainted (2.6.24-rc8-xlnx)
>[ 2340.679876] MSR: 00029030 <EE,ME,IR,DR> CR: 28000048 XER: 20000000
>[ 2340.686189] TASK = c7c35810[243] 'ping' THREAD: c7d0e000
>[ 2340.691279] GPR00: 00000001 c7d0fdd0 c7c35810 c7d318e0 80000009 00000004
>c027bd38 00000200
>[ 2340.699571] GPR08: c7d0fdb8 c7d0e000 c027bd1c c0159910 c7d0fdb8 100b46f4
>ffffffff 00000000
>[ 2340.707864] GPR16: 10090000 100bd6e0 100b0000 100b0000 00000c11 7fbcf9a0
>00000000 10004634
>[ 2340.716158] GPR24: 1007d370 7fbced90 10003fbc 100adf18 00000000 00000000
>c7c9e000 c7d318e0
>[ 2340.724625] **bleep** [c015bd24] skb_release_all+0x6c/0x94
>[ 2340.729551] LR [c015b3f4] __kfree_skb+0x18/0xc0
>[ 2340.734042] Call Trace:
>[ 2340.736465] [c7d0fdd0] [c0161b6c] netif_rx+0x124/0x158 (unreliable)
>[ 2340.742684] [c7d0fde0] [c015b3f4] __kfree_skb+0x18/0xc0
>[ 2340.747866] [c7d0fdf0] [c01466a0] SendHandler+0x44/0x94
>[ 2340.753050] [c7d0fe10] [c0147284] XEmacLite_InterruptHandler+0x12c/0x140
>[ 2340.759702] [c7d0fe20] [c0146078] xemaclite_interrupt+0x20/0x34
>[ 2340.765577] [c7d0fe30] [c003c98c] handle_IRQ_event+0x4c/0xa0
>[ 2340.771193] [c7d0fe50] [c003ca94] __do_IRQ+0xb4/0x130
>[ 2340.776203] [c7d0fe70] [c0006990] do_IRQ+0x6c/0xa4
>[ 2340.780954] [c7d0fe80] [c000329c] ret_from_except+0x0/0x18
>[ 2340.786397] [c7d0ff40] [c0002c50] ret_from_syscall+0x0/0x3c
>[ 2340.791923] Instruction dump:
>[ 2340.794865] 3000ffff 7c005a2c 7c00592d 40a2fff0 817f006c 54290024
>2f8b0000 419e0024
>[ 2340.802549] 8009000c 5400011e 7c0000d0 54000ffe <0f000000> 7fe3fb78
>7d6903a6 4e800421
> (192.168.1.185): 2953 data bytes
>[ 2341.832397] ------------[ cut here ]------------
>[ 2341.835801] Badness at net/core/skbuff.c:317
>[ 2341.839992] **bleep**: c015bd24 LR: c015b3f4 CTR: 00000000
>[ 2341.844923] REGS: c7d0fd20 TRAP: 0700 Not tainted (2.6.24-rc8-xlnx)
>[ 2341.851388] MSR: 00029030 <EE,ME,IR,DR> CR: 28000048 XER: 20000000
>[ 2341.857702] TASK = c7c35810[243] 'ping' THREAD: c7d0e000
>[ 2341.862792] GPR00: 00000001 c7d0fdd0 c7c35810 c7d31840 80000009 00000004
>c027bd38 00000200
>[ 2341.871084] GPR08: c7d0fdb8 c7d0e000 c027bd1c c0159910 c7d0fdb8 100b46f4
>ffffffff 00000000
>[ 2341.879377] GPR16: 10090000 100bd6e0 100b0000 300b4e20 00000c11 7fbcf9a0
>00000000 10004634
>[ 2341.887671] GPR24: 1007d370 7fbced90 10003fbc 100adf18 00000000 00000000
>c7c9e000 c7d31840
>[ 2341.896138] **bleep** [c015bd24] skb_release_all+0x6c/0x94
>[ 2341.901064] LR [c015b3f4] __kfree_skb+0x18/0xc0
>[ 2341.905555] Call Trace:
>[ 2341.907978] [c7d0fdd0] [c0161b6c] netif_rx+0x124/0x158 (unreliable)
>[ 2341.914197] [c7d0fde0] [c015b3f4] __kfree_skb+0x18/0xc0
>[ 2341.919379] [c7d0fdf0] [c01466a0] SendHandler+0x44/0x94
>[ 2341.924563] [c7d0fe10] [c0147284] XEmacLite_InterruptHandler+0x12c/0x140
>[ 2341.931215] [c7d0fe20] [c0146078] xemaclite_interrupt+0x20/0x34
>[ 2341.937089] [c7d0fe30] [c003c98c] handle_IRQ_event+0x4c/0xa0
>[ 2341.942705] [c7d0fe50] [c003ca94] __do_IRQ+0xb4/0x130
>[ 2341.947716] [c7d0fe70] [c0006990] do_IRQ+0x6c/0xa4
>[ 2341.952467] [c7d0fe80] [c000329c] ret_from_except+0x0/0x18
>[ 2341.957910] [c7d0ff40] [c0002c50] ret_from_syscall+0x0/0x3c
>[ 2341.963436] Instruction dump:
>[ 2341.966378] 3000ffff 7c005a2c 7c00592d 40a2fff0 817f006c 54290024
>2f8b0000 419e0024
>[ 2341.974062] 8009000c 5400011e 7c0000d0 54000ffe <0f000000> 7fe3fb78
>7d6903a6 4e800421


>--- 192.168.1.185 ping statistics ---
>2 packets transmitted, 0 packets received, 100% packet loss



>What could be the problem ? MTU limits ? Packet fragmentation ? Wrong buffer
>size ?
>Hardware problem ?


Nope, the problem is behind the keyboard. Why in the world are you sending
ping packets of that size?

(Mind you I agree that a crash is hardly the right response from ping)


 
Reply With Quote
 
David Schwartz
Guest
Posts: n/a

 
      04-21-2008, 11:01 PM
On Apr 21, 10:09 am, Unruh <unruh-s...@physics.ubc.ca> wrote:

> Nope, the problem is behind the keyboard. Why in the world are you sending
> ping packets of that size?


Umm, what?! What's wrong with 2,953-byte ping packets? I routinely use
large pings to test fragmentation, reassembly, path MTU blackholes,
and the like. I don't think I'm alone.

> (Mind you I agree that a crash is hardly the right response from ping)


Umm, what?! Ping didn't crash. It continued all the way to the end and
wrote out its statistics.

Congratulations on a completely useless reply.

DS
 
Reply With Quote
 
Guillaume Dargaud
Guest
Posts: n/a

 
      04-22-2008, 12:07 PM
Well, except for someone who had the same issue in a '96 BSD message, I
tracked it down to wrong (?) firmware on the network card (EmacLite).
Anyway, using another firmware (LLTEMAC) seems to have solved at least that
issue.

And why large packets with ping ? Because sending anything small with most
protocols was working also, but anything above a certain size would fail.
--
Guillaume Dargaud
http://www.gdargaud.net/


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Fail 0x00038012 Stephane Wireless Networks 0 02-17-2008 08:50 AM
How to set Max UDP Receive Buffer Size and Max UDP Transmit Buffer Size under Windows 2000 and Windows 2003 ? msnews.microsoft.com Windows Networking 0 09-14-2005 07:20 PM
Ping works, TCP/IP transfers fail jro Linux Networking 5 06-02-2005 04:04 PM
connection fail via vpn ms Windows Networking 1 10-10-2004 07:55 AM
ping size and mtu size u.dahms Linux Networking 4 10-01-2003 12:35 PM



1 2 3 4 5 6 7 8 9 10 11