Comment 37 for bug 567016

Just to try to speed things up to make it go into that infinite loop of non-connectingness, i decided to transfer 2.9GB of data from my desktop computer to my laptop, and low and behold something so incredibly obvious appears. Right at about 1:50 is where i started the file transfer. Want to guess when it completed? I find it so strange that even outside of those "message repeated" errors, i could set my watch fairly accurately to these debug messages (well, here and there they seem to miss a minute, but still). Granted, i don't loose connection from services (my router, however, is complaining in it's logs) at those times (haven't had a chance to time "talking glitches" with skype yet, but at this point i doubt i have to). If only i knew my way around those drivers and wireless networking hardware, i'd fix the problem myself, however I don't.

While typing this, my connection went out again. I found that before finishing this, though, it inevitably reconnected. So i updated the file accordingly while typing. Anyway, if not all these messages correspond to a single issue, solving them so that they disappear would help the issues come into light more clearly. I originally had a theory written here on what the problem was, but once i got enough data, i realized that connecting all these error messages was a stretch. A new theory, though:

There's a 6 element queue of something called "TX." The driver gets "stuck" whenever it runs out of TX (slowly, but progressively), however it can't free TX because something (that it can't sacrifice because data would end up permanently lost, despite it supposedly not being lost) is using that 6th slot. Now, it'll have a little success, but inevitably because this queue's usage grows and can't be freed at the rate in which it gets used up, it inevitably gets truly stuck and connection is lost and cannot be re-established. Though, my guess is that i'm actually totally wrong, because i'm just making a wild guess on the data, but if all else fails, it's something to go on, because solving any of these messages could clear them up enough to see the real problem.

The only thing i really can't explain is that i did have one good night where nothing happened in syslog for about 8 hours or why these messages appear so consistently.