From: "Ivo Van Doorn" <ivdoorn@gmail.com>
To: chris2553@googlemail.com
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.25-rc2 regression in rt61pci wireless driver
Date: Mon, 25 Feb 2008 23:09:39 +0100 [thread overview]
Message-ID: <a32f33a40802251409ofbdab60w4a95c8aaefaad70a@mail.gmail.com> (raw)
In-Reply-To: <200802252104.32416.chris2553@googlemail.com>
Hi,
> > > > Checking those out is simply a matter of:
> > > > git branch 2.0.11 2d68de3efa62655d551092f5c787505735d561ad
> > > > git checkout 2.0.11
> > >
> > > OK, we seem to be struggling a little, so I've built an installed git
> > > and cloned Linus' 2.6 tree. My wireless network dies after a few pings
> > > with rt2x00 2.0.11.
> > >
> > > > No further bisecting is needed, but with above tests I can at least
> > > > narrow it down to find the cause of this issue.
> > >
> > > If you need me to bisect, just shout. Please be patient though, I'm
> > > exploring new territory here :-)
> >
> > I don't think bisecting this will help a lot, the rt2x00 2.0.11 release
> > introduced software diversity. And that is already something I suspect
> > of being broken.
> >
> I've bisected anyway and although the results are not absolutely conclusive,
> as I neared the end of the process, I was amongst a bunch of mac80211
> patches. This set me on a path that resulted in me discovering that with the
> rt61pci driver, I can freeze my wireless network connection almost at will if
> I set mac82011's ieee80211_default_rc_algo parameter to 'pid'. if the
> parametre is set to 'simple', the network seems to be reliable. I've just let
> the ping application run on and ping another box on my network almost 1500
> times whilst repeatedly transferring a kernel source tarball by ftp from
> another box and the network connection was mantained That's with the
> parameter set to 'simple', if \I set it to 'pid' the connection rarely
> survives more than 40 pings even without the ftp activity.
>
> If I replace my wireless card with one that uses the rtl8180 driver, the
> network connection seems to be reliable regardless of how I set the
> parameter, although I admit that i have not tested this extensively yet. I'll
> do that now and report later.
I'm about to send 4 patches to this (linux-wireless) list with patches
for rt2x00,
most of them you already tested individually, but several people reported
success after those patches.
Hopefully it will be working for you as well. :)
Ivo
next prev parent reply other threads:[~2008-02-25 22:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 12:06 Chris Clayton
2008-02-18 18:11 ` Ivo van Doorn
2008-02-18 18:16 ` Ivo van Doorn
2008-02-18 22:51 ` Chris Clayton
2008-02-19 9:26 ` Ivo van Doorn
2008-02-19 19:00 ` Chris Clayton
2008-02-19 19:46 ` Ivo van Doorn
2008-02-19 20:44 ` Chris Clayton
2008-02-19 21:03 ` Ivo van Doorn
2008-02-19 23:04 ` [Rt2400-devel] " Chris Vine
2008-02-20 16:05 ` Dan Williams
2008-02-20 20:27 ` Chris Vine
2008-02-20 20:50 ` Ivo van Doorn
2008-02-20 21:16 ` Chris Vine
2008-02-21 21:07 ` Chris Vine
2008-02-21 21:51 ` Ivo van Doorn
2008-02-21 22:46 ` Chris Vine
2008-02-21 22:51 ` Ivo van Doorn
2008-02-21 23:04 ` Chris Clayton
2008-02-21 23:20 ` Chris Vine
2008-02-22 7:39 ` Chris Clayton
2008-02-22 19:11 ` Ivo van Doorn
2008-02-22 20:33 ` Chris Vine
2008-02-20 22:13 ` Chris Clayton
2008-02-22 15:46 ` Chris Clayton
2008-02-22 19:47 ` Ivo van Doorn
2008-02-25 21:04 ` Chris Clayton
2008-02-25 22:09 ` Ivo Van Doorn [this message]
2008-02-26 19:11 ` Chris Clayton
2008-02-26 19:48 ` John W. Linville
2008-02-26 20:30 ` Ivo Van Doorn
2008-02-26 21:44 ` Stefano Brivio
2008-02-26 21:13 ` Chris Clayton
2008-02-26 21:38 ` Stefano Brivio
2008-02-26 22:36 ` Chris Clayton
2008-02-27 7:26 ` Stefano Brivio
2008-02-27 15:51 ` John W. Linville
2008-02-27 17:25 ` John W. Linville
2008-02-27 17:45 ` Chris Clayton
2008-03-02 10:33 ` Stefano Brivio
2008-03-02 15:11 ` Chris Clayton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a32f33a40802251409ofbdab60w4a95c8aaefaad70a@mail.gmail.com \
--to=ivdoorn@gmail.com \
--cc=chris2553@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®