lkml.org 
[lkml]   [1998]   [Mar]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
Subject[2.1.91-pre1] tcp wierdness and lockup

Hi there.

Ran into an oddity last night with 2.1.91-pre1, and a total machine
lockup this morning. (read on)

I have a friend that logs into my machine from a local ISP.
This ISP doesn't allow ping packets (perhaps any icmp, not sure?).

My friend can connect fine, enter login and password fine, and get
logged in. However, after that, anything that requires a lot of output
(more than a few lines) locks his connection up hard.
(ls -la, xemacs, etc...)

Dunno if this has anything to do with the fact that he is coming in
from a ppp connect (mtu 552), his provider doesn't allow ping/icmp, or
something else. Every other connect seems to work fine. Even other
dialups. I suspect there is something with the icmp blocking that is
causing this, but I don't know for sure...

here is a tcpdump of the "connection lockup":

tcpdump: listening on eth0
22:42:30.866556 scrye.telnet > ppp4.hemi.com.1151: P 2161145665:2161146189(524) ack 1291925057 win 32488 (DF)
22:43:19.280168 scrye.telnet > ppp4.hemi.com.1162: P 2340376469:2340376993(524) ack 4026931435 win 32488 (DF)
22:43:47.538145 ppp4.hemi.com.1117 > scrye.telnet: P 1660956328:1660956330(2) ack 664017614 win 2208 (DF)
22:43:47.540872 scrye.telnet > ppp4.hemi.com.1117: P 1:24(23) ack 2 win 32488 (DF)
22:43:47.795762 ppp4.hemi.com.1117 > scrye.telnet: . ack 24 win 2208 (DF)
22:43:47.970129 ppp4.hemi.com.1117 > scrye.telnet: P 2:4(2) ack 24 win 2208 (DF)
22:43:47.971954 scrye.telnet > ppp4.hemi.com.1117: P 24:47(23) ack 4 win 32488 (DF)
22:43:48.386427 ppp4.hemi.com.1117 > scrye.telnet: . ack 47 win 2208 (DF)
22:43:53.683697 ppp4.hemi.com.1117 > scrye.telnet: P 4:5(1) ack 47 win 2208 (DF)
22:43:53.684616 scrye.telnet > ppp4.hemi.com.1117: P 47:48(1) ack 5 win 32488 (DF)
22:43:53.860180 ppp4.hemi.com.1117 > scrye.telnet: P 5:7(2) ack 48 win 2208 (DF)
22:43:53.861088 scrye.telnet > ppp4.hemi.com.1117: P 48:50(2) ack 7 win 32488 (DF)
22:43:54.043125 ppp4.hemi.com.1117 > scrye.telnet: P 7:9(2) ack 50 win 2208 (DF)
22:43:54.044727 scrye.telnet > ppp4.hemi.com.1117: P 50:52(2) ack 9 win 32488 (DF)
22:43:54.312242 ppp4.hemi.com.1117 > scrye.telnet: P 9:12(3) ack 52 win 2208 (DF)
22:43:54.317181 scrye.telnet > ppp4.hemi.com.1117: P 52:55(3) ack 12 win 32488 (DF)
22:43:54.357384 scrye.telnet > ppp4.hemi.com.1117: P 55:364(309) ack 12 win 32488 (DF)
22:43:54.360837 scrye.telnet > ppp4.hemi.com.1117: P 364:631(267) ack 12 win 32488 (DF)
22:43:54.363178 scrye.telnet > ppp4.hemi.com.1117: P 631:904(273) ack 12 win 32488 (DF)
22:43:54.506879 ppp4.hemi.com.1117 > scrye.telnet: . ack 55 win 2208 (DF)
22:43:54.507150 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:43:54.663678 ppp4.hemi.com.1117 > scrye.telnet: . ack 364 win 2208 (DF)
22:43:54.663853 scrye.telnet > ppp4.hemi.com.1117: P 1428:1952(524) ack 12 win 32488 (DF)
22:43:54.738158 ppp4.hemi.com.1117 > scrye.telnet: . ack 631 win 2208 (DF)
22:43:54.738353 scrye.telnet > ppp4.hemi.com.1117: P 1952:2476(524) ack 12 win 32488 (DF)
22:43:54.810897 ppp4.hemi.com.1117 > scrye.telnet: . ack 904 win 2208 (DF)
22:43:54.811066 scrye.telnet > ppp4.hemi.com.1117: P 2476:3000(524) ack 12 win 32488 (DF)
22:43:56.515360 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:44:00.534762 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:44:08.573715 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:44:24.651682 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:44:30.851045 scrye.telnet > ppp4.hemi.com.1151: P 0:524(524) ack 1 win 32488 (DF)
22:44:56.807437 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:45:19.264491 scrye.telnet > ppp4.hemi.com.1162: P 0:524(524) ack 1 win 32488 (DF)
22:46:01.119606 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:46:30.836495 scrye.telnet > ppp4.hemi.com.1151: P 0:524(524) ack 1 win 32488 (DF)
22:47:19.251478 scrye.telnet > ppp4.hemi.com.1162: P 0:524(524) ack 1 win 32488 (DF)
22:48:01.107288 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 12 win 32488 (DF)
22:48:22.156225 ppp4.hemi.com.1117 > scrye.telnet: F 12:12(0) ack 904 win 2208
22:48:22.156441 scrye.telnet > ppp4.hemi.com.1117: . ack 13 win 32488 (DF)
22:48:30.824642 scrye.telnet > ppp4.hemi.com.1151: P 0:524(524) ack 1 win 32488 (DF)
22:49:19.240544 scrye.telnet > ppp4.hemi.com.1162: P 0:524(524) ack 1 win 32488 (DF)
22:50:01.097291 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 13 win 32488 (DF)
22:50:30.814904 scrye.telnet > ppp4.hemi.com.1151: P 0:524(524) ack 1 win 32488 (DF)
22:51:19.231278 scrye.telnet > ppp4.hemi.com.1162: P 0:524(524) ack 1 win 32488 (DF)
22:52:01.088360 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 13 win 32488 (DF)
22:52:30.806320 scrye.telnet > ppp4.hemi.com.1151: P 0:524(524) ack 1 win 32488 (DF)
22:53:19.222965 scrye.telnet > ppp4.hemi.com.1162: P 0:524(524) ack 1 win 32488 (DF)
22:54:01.080541 scrye.telnet > ppp4.hemi.com.1117: P 904:1428(524) ack 13 win 32488 (DF)
22:54:30.798843 scrye.telnet > ppp4.hemi.com.1151: P 0:524(524) ack 1 win 32488 (DF)
22:55:19.216180 scrye.telnet > ppp4.hemi.com.1162: P 0:524(524) ack 1
win 32488 (DF)

so, I basically tabled this until I could look at it in more detail.
This morning I had some time, so I whipped out the ol pilot and logged
in via pilot modem with a mtu 552 (modem local to the linux box).

Seemed to work fine. Did an ls -l, great (pretty zippy for 14.4).
Then, I tried to get some mail via pop on another machine and
everything stopped responding. The linux box had totally locked up. ;(

Got someone to go in and reboot it (had to hit reset).
When it came back up, there were no oopses, just:

Mar 25 10:15:36 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:36 jelerak kernel:
Mar 25 10:15:36 jelerak kernel: IP: No memory available for IP forward
Mar 25 10:15:37 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:37 jelerak kernel:
Mar 25 10:15:37 jelerak kernel: IP: No memory available for IP forward
Mar 25 10:15:38 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:38 jelerak kernel:
Mar 25 10:15:38 jelerak kernel: IP: No memory available for IP forward
Mar 25 10:15:40 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:40 jelerak kernel:
Mar 25 10:15:40 jelerak kernel: IP: No memory available for IP forward
Mar 25 10:15:40 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:40 jelerak kernel:
Mar 25 10:15:40 jelerak kernel: IP: No memory available for IP forward
Mar 25 10:15:41 jelerak innd[358]: s
Mar 25 10:15:46 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:46 jelerak kernel:
Mar 25 10:15:46 jelerak kernel: IP: No memory available for IP forward
Mar 25 10:15:46 jelerak kernel: kmalloc: Size (4294967220) too large
Mar 25 10:15:46 jelerak kernel:
Mar 25 10:15:46 jelerak kernel: IP: No memory available for IP forward

Hopefully this will help someone out tracking things down.
More information of any kind avail via email.

I am back in 2.0.33 (if reset thats the default lilo boot kernel), but
will likely boot back into 2.1.90 later tonight, or 2.1.91-pre1 if
someone wants me to try something. let me know...

keep up the good work!

kevin
--
Kevin Fenzi
kevin@scrye.com
WWW -> http://scrye.com/~kevin/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:41    [W:0.050 / U:6.188 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site