guina wrote:
I am having the same problem, with great frequency, since mine linode still is not being used in production.
The problem seems to be resolved when I originate one tcp connection at linode.
You're seeing a different problem from something I forgot to configure on the (new) host server your Linode is on that came online last evening.
This has been corrected, thanks for bringing that to my attention.
Also, a note on the status of the new kernel: It seems stable and much better performing under high I/O load. Thanks to the kernel developers who fixed this long-running issue.
-Chris