[lkml]   [2006]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.17: networking bug??
Mark Lord wrote:
> Further to this, the current behaviour is badly unpredictable.
> A machine could be working perfectly, not (noticeably) affected
> by this bug. And then the user adds another stick of RAM to it.

This "bug" already existed in 2.6.16 to a certain extent: you were
losing out on a lot of TCP performance. Go back to 2.6.7, measure TCP
performance, and you'll probably find it was significantly better.

Also, there aren't that many broken end-points out there. loads fine for me and does not ignore the window scale

The problem in your case is a broken router in the middle. I had the
same problem: certain sites would not load, but there is absolutely
nothing wrong with the servers that run these sites:

I contacted my ISP and informed them of the issue. They fixed it
nationwide within a few weeks. You might try confirming that your
problem only applies to HTTP like mine did (ISP runs some lame
transparent webcaches), and it was a bug in the software there (NetApp).

We already had the "some routers are broken, should we do anything"
discussion back at the time of 2.6.8:


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-14 10:10    [W:0.096 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site