lkml.org 
[lkml]   [1998]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.1.123-2 TCP Oops
SK> This oops has happened before with 2.1.122 as well.  I believe it is an
SK> actual bug in the TCP stack... This machine is one of our most
SK> heavily-loaded webservers. It's still running, but it only spat out the
SK> oops a few minutes ago. Anybody have any ideas?

>>>EIP: c010ed83 <del_timer+13/3c>

It seems that we are the only ones seeing it. And I dont see it unless I
try hard. I considered possible memory corruption but this seems very
unlikely now as you have it on exactly the same address.

I tried to look at the code and found that something must corrupt the tcp
probe timer - it's not NULL but it's not valid either.

UP kernel on UP machine, tcp path mtu discovery turned off. I can reproduce
it with only tcp timestamps off, maybe I would need higher load to
reproduce it with timestamps on.

--
Meelis Roos (mroos@tartu.cyber.ee)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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