mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Clayton" <chris2553@googlemail.com>
To: ivdoorn@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.25-rc2 regression in rt61pci wireless driver
Date: Fri, 22 Feb 2008 15:46:54 +0000	[thread overview]
Message-ID: <c6b1100b0802220746s3441d28cj92896618bbb57bde@mail.gmail.com> (raw)
In-Reply-To: <200802181911.32128.IvDoorn@gmail.com>

Hi Ivo,

On 18/02/2008, Ivo van Doorn <ivdoorn@gmail.com> 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   2d68de3efa62655d551092f5c787505735d561ad
>  rt2x00 2.0.12   a3c7aa58df7df80aa05f166fe3e42482247164cf
>  rt2x00 2.0.13   5a6012e105ae1664cd2841c33bf59fbdd8d4dbcc
>
>  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 :-)

Thanks

Chris
>  Thanks.
>
>
>  Ivo
>
>


-- 
Beauty is in the eye of the beerholder.

  parent reply	other threads:[~2008-02-22 15:47 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 [this message]
2008-02-22 19:47     ` Ivo van Doorn
2008-02-25 21:04       ` Chris Clayton
2008-02-25 22:09         ` Ivo Van Doorn
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=c6b1100b0802220746s3441d28cj92896618bbb57bde@mail.gmail.com \
    --to=chris2553@googlemail.com \
    --cc=ivdoorn@gmail.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®