On Tue, Feb 26, 2008 at 07:11:39PM +, Chris Clayton wrote:
> Sorry, but that's not the case. I find the same results as without the
> patches. With the parameter set to 'pid', the network connection fails very
> quickly, but with it set to 'simple' I can ping and ftp files to and from my
>
Hi,
> > 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
Hi,
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
On Tue, Feb 26, 2008 at 07:11:39PM +, Chris Clayton wrote:
Sorry, but that's not the case. I find the same results as without the
patches. With the parameter set to 'pid', the network connection fails very
quickly, but with it set to 'simple' I can ping and ftp files to and from my
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
Hi,
Firstly apologies for trimming linux-kernel and linux-wireless from my reply
to Ivo yesterday. Basically, I replied saying that the patch below didn't fix
the problem. But please do read on...
On Friday 22 February 2008, Ivo van Doorn wrote:
> On Friday 22 February 2008, Chris Clayton
Hi,
Firstly apologies for trimming linux-kernel and linux-wireless from my reply
to Ivo yesterday. Basically, I replied saying that the patch below didn't fix
the problem. But please do read on...
On Friday 22 February 2008, Ivo van Doorn wrote:
On Friday 22 February 2008, Chris Clayton
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
On Fri, 2008-02-22 at 07:39 +, Chris Clayton wrote:
> On Thursday 21 February 2008, Chris Vine wrote:
[snip]
> >
> > Does the same happen with 2.0.14 under kernel 2.6.24?
>
> Unfortunately, a 2.6.24.2 tree with the drivers/net/wireless/rt2x00 directory
> replaced with that from
On Friday 22 February 2008, Chris Clayton wrote:
> Hi Ivo,
>
> On 18/02/2008, Ivo van Doorn <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
>
> [...]
>
> > Above traces should be enough, but to determine where rt2x00 broke
> > down approximatly I need to have a few test result on specific moments.
> >
On Friday 22 February 2008, Chris Clayton wrote:
> On Thursday 21 February 2008, Chris Vine wrote:
> > On Thu, 2008-02-21 at 23:04 +, Chris Clayton wrote:
> > > On Thursday 21 February 2008, Ivo van Doorn wrote:
> > > > On Thursday 21 February 2008, Chris Vine wrote:
> > [snip]
> > > > > This
Hi Ivo,
On 18/02/2008, Ivo van Doorn <[EMAIL PROTECTED]> wrote:
> Hi,
>
[...]
> Above traces should be enough, but to determine where rt2x00 broke
> down approximatly I need to have a few test result on specific moments.
> Could you test the kernel with the following versions:
>
> rt2x00
Hi Ivo,
On 18/02/2008, Ivo van Doorn [EMAIL PROTECTED] wrote:
Hi,
[...]
Above traces should be enough, but to determine where rt2x00 broke
down approximatly I need to have a few test result on specific moments.
Could you test the kernel with the following versions:
rt2x00 2.0.11
On Friday 22 February 2008, Chris Clayton wrote:
On Thursday 21 February 2008, Chris Vine wrote:
On Thu, 2008-02-21 at 23:04 +, Chris Clayton wrote:
On Thursday 21 February 2008, Ivo van Doorn wrote:
On Thursday 21 February 2008, Chris Vine wrote:
[snip]
This probably explains
On Friday 22 February 2008, Chris Clayton wrote:
Hi Ivo,
On 18/02/2008, Ivo van Doorn [EMAIL PROTECTED] wrote:
Hi,
[...]
Above traces should be enough, but to determine where rt2x00 broke
down approximatly I need to have a few test result on specific moments.
Could you test
On Fri, 2008-02-22 at 07:39 +, Chris Clayton wrote:
On Thursday 21 February 2008, Chris Vine wrote:
[snip]
Does the same happen with 2.0.14 under kernel 2.6.24?
Unfortunately, a 2.6.24.2 tree with the drivers/net/wireless/rt2x00 directory
replaced with that from 2.6.25-rc2-git4
On Thursday 21 February 2008, Chris Vine wrote:
> On Thu, 2008-02-21 at 23:04 +, Chris Clayton wrote:
> > On Thursday 21 February 2008, Ivo van Doorn wrote:
> > > On Thursday 21 February 2008, Chris Vine wrote:
> [snip]
> > > > This probably explains the problem another user reported with
On Thursday 21 February 2008, Chris Vine wrote:
> On Wed, 2008-02-20 at 21:16 +, Chris Vine wrote:
> > On Wed, 2008-02-20 at 21:50 +0100, Ivo van Doorn wrote:
> > [snip]
> > > On Wednesday 20 February 2008, Chris Vine wrote:
> > > > I did that yesterday and it just reported a kernel panic on
On Wed, 2008-02-20 at 21:16 +, Chris Vine wrote:
> On Wed, 2008-02-20 at 21:50 +0100, Ivo van Doorn wrote:
> [snip]
> > On Wednesday 20 February 2008, Chris Vine wrote:
> > > I did that yesterday and it just reported a kernel panic on the terminal
> > > with the message:
> > >
> > > Kernel
On Wed, 2008-02-20 at 21:16 +, Chris Vine wrote:
On Wed, 2008-02-20 at 21:50 +0100, Ivo van Doorn wrote:
[snip]
On Wednesday 20 February 2008, Chris Vine wrote:
I did that yesterday and it just reported a kernel panic on the terminal
with the message:
Kernel panic - not
On Thursday 21 February 2008, Chris Vine wrote:
On Wed, 2008-02-20 at 21:16 +, Chris Vine wrote:
On Wed, 2008-02-20 at 21:50 +0100, Ivo van Doorn wrote:
[snip]
On Wednesday 20 February 2008, Chris Vine wrote:
I did that yesterday and it just reported a kernel panic on the terminal
On Thursday 21 February 2008, Chris Vine wrote:
On Thu, 2008-02-21 at 23:04 +, Chris Clayton wrote:
On Thursday 21 February 2008, Ivo van Doorn wrote:
On Thursday 21 February 2008, Chris Vine wrote:
[snip]
This probably explains the problem another user reported with rt61.
Hi Ivo,
[...]
>
> I have an idea, could you try below patch?
> Note that while applying it will mention something about a line offset, but
> that can be ignored.
>
> This could perhaps also fix the TX/RX issue mentioned earlier in the thread,
> but I am not
> quite sure about that.
>
Sorry,
On Wed, 2008-02-20 at 21:50 +0100, Ivo van Doorn wrote:
[snip]
> On Wednesday 20 February 2008, Chris Vine wrote:
> > I did that yesterday and it just reported a kernel panic on the terminal
> > with the message:
> >
> > Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> I have
On Wednesday 20 February 2008, Chris Vine wrote:
>
> On Wed, 2008-02-20 at 11:05 -0500, Dan Williams wrote:
> > On Tue, 2008-02-19 at 23:04 +, Chris Vine wrote:
> > > On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
> > > > Hi,
> > > >
> > > > [added rt2400-devel (rt2x00 development
On Wed, 2008-02-20 at 11:05 -0500, Dan Williams wrote:
> On Tue, 2008-02-19 at 23:04 +, Chris Vine wrote:
> > On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
> > > Hi,
> > >
> > > [added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
> > >
> > > > > > > I have a
On Tue, 2008-02-19 at 23:04 +, Chris Vine wrote:
> On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
> > Hi,
> >
> > [added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
> >
> > > > > > I have a series of tests I would like to request from you,
> > > > > > you
On Tue, 2008-02-19 at 23:04 +, Chris Vine wrote:
On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
Hi,
[added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
I have a series of tests I would like to request from you,
you mentioned you already enabled
On Wed, 2008-02-20 at 11:05 -0500, Dan Williams wrote:
On Tue, 2008-02-19 at 23:04 +, Chris Vine wrote:
On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
Hi,
[added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
I have a series of tests I would
On Wednesday 20 February 2008, Chris Vine wrote:
On Wed, 2008-02-20 at 11:05 -0500, Dan Williams wrote:
On Tue, 2008-02-19 at 23:04 +, Chris Vine wrote:
On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
Hi,
[added rt2400-devel (rt2x00 development mailinglist) to the
On Wed, 2008-02-20 at 21:50 +0100, Ivo van Doorn wrote:
[snip]
On Wednesday 20 February 2008, Chris Vine wrote:
I did that yesterday and it just reported a kernel panic on the terminal
with the message:
Kernel panic - not syncing: Aiee, killing interrupt handler!
I have an idea,
Hi Ivo,
[...]
I have an idea, could you try below patch?
Note that while applying it will mention something about a line offset, but
that can be ignored.
This could perhaps also fix the TX/RX issue mentioned earlier in the thread,
but I am not
quite sure about that.
Sorry, but
On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
> Hi,
>
> [added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
>
> > > > > I have a series of tests I would like to request from you,
> > > > > you mentioned you already enabled debugfs, and that is just what we
> > > > >
Hi,
> > > I've tried the patch but, unfortunately, my wireless LAN still dies after
> > > a few pings.
> >
> > Could you use below patch instead, and make a new dump of the register?
> > I'm still convinced the breakage occurs in the antenna diversity (or
> > rather, I believe
> > it attempts
Hi,
On Tuesday 19 February 2008, Ivo van Doorn wrote:
> Hi,
>
[...]
> >
> > I've tried the patch but, unfortunately, my wireless LAN still dies after a
> > few pings.
>
> Could you use below patch instead, and make a new dump of the register?
> I'm still convinced the breakage occurs in the
Hi,
[added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
> > > > I have a series of tests I would like to request from you,
> > > > you mentioned you already enabled debugfs, and that is just what we
> > > > need. ;)
> > > > Please use attached script to create dumps of the
Hi,
> > I have a series of tests I would like to request from you,
> > you mentioned you already enabled debugfs, and that is just what we need. ;)
> > Please use attached script to create dumps of the hardware register
> > contents.
> >
> > There are specific moments that should be dumped:
> >
Hi,
I have a series of tests I would like to request from you,
you mentioned you already enabled debugfs, and that is just what we need. ;)
Please use attached script to create dumps of the hardware register
contents.
There are specific moments that should be dumped:
- kernel
Hi,
[added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
I have a series of tests I would like to request from you,
you mentioned you already enabled debugfs, and that is just what we
need. ;)
Please use attached script to create dumps of the hardware register
Hi,
On Tuesday 19 February 2008, Ivo van Doorn wrote:
Hi,
[...]
I've tried the patch but, unfortunately, my wireless LAN still dies after a
few pings.
Could you use below patch instead, and make a new dump of the register?
I'm still convinced the breakage occurs in the antenna
Hi,
I've tried the patch but, unfortunately, my wireless LAN still dies after
a few pings.
Could you use below patch instead, and make a new dump of the register?
I'm still convinced the breakage occurs in the antenna diversity (or
rather, I believe
it attempts a software
On Tue, 2008-02-19 at 20:46 +0100, Ivo van Doorn wrote:
Hi,
[added rt2400-devel (rt2x00 development mailinglist) to the CC list.]
I have a series of tests I would like to request from you,
you mentioned you already enabled debugfs, and that is just what we
need. ;)
Hi Ivo,
On Monday 18 February 2008, Ivo van Doorn wrote:
> Hi,
>
> > In 2.6.25 kernels, my wireless LAN dies after even the smallest amount
> > of network activity. The following screen cut shows what I typically
> > see:
>
> How complete is this failure? Just TX or also RX?
>
> Could you use
Almost forgot:
> > In 2.6.25 kernels, my wireless LAN dies after even the smallest amount
> > of network activity. The following screen cut shows what I typically
> > see:
>
> How complete is this failure? Just TX or also RX?
>
> Could you use the tools found here:
>
Hi,
> In 2.6.25 kernels, my wireless LAN dies after even the smallest amount
> of network activity. The following screen cut shows what I typically
> see:
How complete is this failure? Just TX or also RX?
Could you use the tools found here:
Hi,
In 2.6.25 kernels, my wireless LAN dies after even the smallest amount
of network activity. The following screen cut shows what I typically
see:
How complete is this failure? Just TX or also RX?
Could you use the tools found here:
http://www-user.rhrk.uni-kl.de/~nissler/rt2x00/index.html
Almost forgot:
In 2.6.25 kernels, my wireless LAN dies after even the smallest amount
of network activity. The following screen cut shows what I typically
see:
How complete is this failure? Just TX or also RX?
Could you use the tools found here:
Hi Ivo,
On Monday 18 February 2008, Ivo van Doorn wrote:
Hi,
In 2.6.25 kernels, my wireless LAN dies after even the smallest amount
of network activity. The following screen cut shows what I typically
see:
How complete is this failure? Just TX or also RX?
Could you use the tools
48 matches
Mail list logo
