Thread: Re: [zd1211-devs] Disconnection during ftp upload : regression in compat-wireless-2009-11-03
Status: Beta
Brought to you by:
mayne
From: Hin-Tak L. <hin...@ya...> - 2010-10-28 12:31:57
|
--- On Thu, 28/10/10, julien cubizolles <j.c...@fr...> wrote: > First : I have to manually set the bitrate like it was > before. > > But the bug remains : I get deconnected after a few Mo > uploaded. Overriding bitrate is probably not advisable - why do you do that. (also, please keep the cc to the list - this is not a private consultancy). > > > 2) It is not very useful posting > compat-wireless-2009-10-28 vs > > compat-wireless-2009-11-03 - it is more useful posting > the content of > > "master-tag", "git-describe", and "compat-release" > (and maybe other small files) > > at the top of the tarball which contains the git tags > or sha1 sum of where they > > derives (this may it easier to pin point what it was > made of and the difference > > between it and the other). > > For the first occurence of the bug : > > master-tag : master-2009-11-02 > git-describe : v2.6.32-rc5-40735-g8573aa6 > compat-release : master-2009-10-30-1-g357b74e > > Is this the information you need ? And the corresponding "last working" version of these. |
From: julien c. <j.c...@fr...> - 2010-10-28 13:21:33
|
Le jeudi 28 octobre 2010 à 13:31 +0100, Hin-Tak Leung a écrit : > --- On Thu, 28/10/10, julien cubizolles <j.c...@fr...> wrote: > > > First : I have to manually set the bitrate like it was > > before. > > > > But the bug remains : I get deconnected after a few Mo > > uploaded. > > Overriding bitrate is probably not advisable - why do you do that. By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or upload is ridiculously slow. That's what I've been doing with kernel 2.6.32 for a year or so. > > For the first occurence of the bug : > > > > master-tag : master-2009-11-02 > > git-describe : v2.6.32-rc5-40735-g8573aa6 > > compat-release : master-2009-10-30-1-g357b74e > > > > Is this the information you need ? > > And the corresponding "last working" version of these. master-tag : master-2009-10-16 git-describe : v2.6.32-rc5-40584-g9b469da compat-release : master-2009-10-16 |
From: Hin-Tak L. <hin...@ya...> - 2010-10-28 23:38:09
|
julien cubizolles wrote: > By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or > upload is ridiculously slow. That's what I've been doing with kernel > 2.6.32 for a year or so. By default, the bitrate is set to 1Mb/s *when you are not using your connection*. It should shift up when you start using it, otherwise the rate control algorithm is not working. That's what "rate control algorithm" means. >>> For the first occurence of the bug : >>> >>> master-tag : master-2009-11-02 >>> git-describe : v2.6.32-rc5-40735-g8573aa6 >>> compat-release : master-2009-10-30-1-g357b74e >>> >>> Is this the information you need ? >> And the corresponding "last working" version of these. > > master-tag : master-2009-10-16 > git-describe : v2.6.32-rc5-40584-g9b469da > compat-release : master-2009-10-16 that's it. Now everybody can have a look at the diff. (I am not promising to look at it any time soon...) |
From: julien c. <j.c...@fr...> - 2010-10-29 07:05:52
|
Le vendredi 29 octobre 2010 à 00:38 +0100, Hin-Tak Leung a écrit : > julien cubizolles wrote: > > By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or > > upload is ridiculously slow. That's what I've been doing with kernel > > 2.6.32 for a year or so. > > By default, the bitrate is set to 1Mb/s *when you are not using your > connection*. It should shift up when you start using it, otherwise the rate > control algorithm is not working. That's what "rate control algorithm" means. Tha'ts what i had understood : the previous rate control algorithm (pid from what you said) doesn't work. |
From: Hin-Tak L. <hin...@ya...> - 2010-10-30 05:22:30
|
julien cubizolles wrote: > Le vendredi 29 octobre 2010 à 00:38 +0100, Hin-Tak Leung a écrit : >> julien cubizolles wrote: >>> By default, the bitrate is set to 1Mb/s. I usually set it to 48Mb/s or >>> upload is ridiculously slow. That's what I've been doing with kernel >>> 2.6.32 for a year or so. >> By default, the bitrate is set to 1Mb/s *when you are not using your >> connection*. It should shift up when you start using it, otherwise the rate >> control algorithm is not working. That's what "rate control algorithm" means. > > Tha'ts what i had understood : the previous rate control algorithm (pid > from what you said) doesn't work. That's not what I said - I said there is some evidence that the *new* minstrel rate control algorithm doesn't work, so older kernel kernel releases work better for some people. |
From: julien c. <j.c...@fr...> - 2010-10-30 08:23:41
|
Le samedi 30 octobre 2010 à 06:22 +0100, Hin-Tak Leung a écrit : > That's not what I said - I said there is some evidence that the *new* minstrel > rate control algorithm doesn't work, so older kernel kernel releases work better > for some people. That's not what I experience : * with minstrel, there is some rate control going on since the rate isn't stuck at 1Mb * with pid (stock driver from kernel 2.6.32 and 2.6.35 when I set it at build time), there wasn't any rate control : rate stayed at 1Mb/s if I didn't set it otherwise. However, with minstrel (stock driver from 2.6.35) I get these disconnections during upload. I also get them with pid when I set it at build time so maybe the two issues (rate control and disconnections) aren't related. |