Messages in this thread |  | | | Date | Thu, 09 Jul 1998 19:04:01 -0000 (???) | | From | Meino Christian Cramer <> | | Subject | v2.1.108: Socket destroy delayed, bad checksums -- Addition |
| |
Hi!
Addition:
The "socket destroy delayed" -- appears alos on 2.1.107 with a immense slowdown of tranfer rates.
Any help ???
KEEP HACKING! meino
On 09-Jul-98 Meino Christian Cramer wrote: > Hi! > > With v2.1.108 of Linux I get tons of: > > > registered device ppp0 > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=506/506/526 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=782/782/802 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > TCPv4 bad checksum from 195.37.76.19:0014 to 194.195.220.240:0409, > len=1480/1480/1500 > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043031632) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043030960) > Socket destroy delayed (r=0 w=-1043031632) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043030960) > Socket destroy delayed (r=0 w=-1043031632) > Socket destroy delayed (r=0 w=-1043033648) > Socket destroy delayed (r=0 w=-1043030960) > Socket destroy delayed (r=0 w=-1043031632) > > > What is giong on there? > > With 2.1.107, the "Socket destroy delayed" are missing, bad checksum > I get with 107 also. > > How can I help ? > > KEEP HACKING! > meino > > > > > ---------------------------------- > E-Mail: Meino Christian Cramer <root@solfire.ludwigsburg.netsurf.de> > Date: 09-Jul-98 > Time: 04:30:14 > > This message was sent by XFMail > ---------------------------------- > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu >
---------------------------------- E-Mail: Meino Christian Cramer <root@solfire.ludwigsburg.netsurf.de> Date: 09-Jul-98 Time: 19:04:01 This message was sent by XFMail ---------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
|  |