Lots of checkPacketInID: packet_out_of_order warnings

Hi. Does anyone know a likely cause for this:

13936 from 63.210.159.181:12035
2008-04-29T23:14:31Z INFO: checkPacketInID: packet_out_of_order - got packet 13936 expecting 13861 from 63.210.159.181:12035
2008-04-29T23:14:31Z INFO: checkPacketInID: packet_out_of_order - got packet 13861 expecting 13938 from 63.210.159.181:12035
2008-04-29T23:14:31Z INFO: checkPacketInID: packet_out_of_order - got packet 13938 expecting 13862 from 63.210.159.181:12035

I get a constant stream of those when SL is running. The summary when I quit says:

2008-04-29T23:14:35Z INFO: end_messaging_system: START MESSAGE LOG SUMMARY
Run time: 274.299 seconds
Incoming:
Total bytes received: 8557100 (249.57 kbits per second)
Total packets received: 11880 (43.31 packets per second)
Average packet size: 720 bytes
Total reliable packets: 9418 (79.27%)
Total compressed packets: 1332 (11.21%)
Total compression savings: 601719 bytes
Avg comp packet savings: 451 ( 1.69 : 1)
Avg overall comp savings: 50 ( 1.07 : 1)

Outgoing:
Total bytes sent: 0 ( 0.00 kbits per second)
Total packets sent: 9664 (35.23 packets per second)
Average packet size: 0 bytes
Total reliable packets: 840 ( 8.69%)
Total compressed packets: 0 ( 0.00%)
Total compression savings: 0 bytes
Avg comp packet savings: 0 ( 0.00 : 1)
Avg overall comp savings: 0 ( 0.00 : 1)

SendPacket failures: 0
Dropped packets: 567
Resent packets: 60
Failed reliable resends: 108
Off-circuit rejected packets: 0
On-circuit invalid packets: 0

Decoding:
Message Count Time Max Avg
END MESSAGE LOG SUMMARY

2008-04-29T23:14:35Z INFO: cleanup: Goodbye
2008-04-29T23:14:35Z INFO: removeMarkerFile()
2008-04-29T23:14:35Z INFO: LLThread::staticRun() Exiting: Error
2008-04-29T23:14:35Z INFO: ll_cleanup_apr: Cleaning up APR

*******************************************************
This is a BETA release of the Second Life linux client.
Thank you for testing!
Please see README-linux.txt before reporting problems.


Is this something due to my internet connection? Is it just to be ignored, or is there a way to improve things?

SL works OK, but it seems sluggish and jerky. My 'net connection isn't the best in the world - top DL speed is usually 62KiB/s. But when SL is running, my connection isn't totally saturated.

SL version is 1_20_4_85828_RELEASECANDIDATE.

Computer is Intel Core2 Duo w/ 4G RAM, Nvidia 7900GS. OS is x86_64 Ubuntu 8.04 (2.6.24 kernel) w/ Nvidia drivers version 169.12.

Any other info that would be helpful?

Thanks,

Sand

No one else sees this? Thanks for looking!

- Sand

I had them a kazilion times. But then uploading and rezzing went slow an then came the linden only login so... SL server side isues lool

OK, thanks for the response. I'll try again some time and post more info if I can find it.

I thought the protocols had a built in way to deal with the arrival order of packets or in cases of lag and issues lack thereof, If after rechecking it continues file a JIRA and post a link to it here (or feel free to IM me the link) so we can get some more eyes on the issue.

SL uses UDP for its data transmission over the network. UDP cares neither about order or delivery. So some packets may get lost and never get a rebroadcast and they may come out of order. This is the nature of the protocol.

Check to see that you have networking capable of handling the traffic that SL generates. Due to the large amount of traffic SL generates it's better to drop packets then to clog the network up. The client handles asking for parts it really needs again, which is also why you get disconnected when you lose too many packets.

http://en.wikipedia.org/wiki/User_Datagram_Protocol