linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Chris Vine <chris@cvine.freeserve.co.uk>,
	Dan Williams <dcbw@redhat.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] 2.6.25-rc2 regression in rt61pci wireless driver
Date: Thu, 21 Feb 2008 23:04:28 +0000	[thread overview]
Message-ID: <200802212304.28731.chris2553@googlemail.com> (raw)
In-Reply-To: <200802212251.26897.IvDoorn@gmail.com>

On Thursday 21 February 2008, Ivo van Doorn wrote:
> On Thursday 21 February 2008, Chris Vine wrote:
> > On Wed, 2008-02-20 at 21:16 +0000, 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 syncing: Aiee, killing interrupt handler!
> > > > 
> > > > 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.
> > > 
> > > The patch applied OK (with some offsets as you say) but it doesn't help.
> > > The kernel panic still occurs when association is attempted.
> > 
> > Here's some further information.
> > 
> > I have a fully functioning version of rt2x00-2.0.14 and mac80211 from
> > wireless-2.6/compat-wireless-2.6 of mid January which works fine on
> > kernel 2.6.24.  On doing a comparison with the rt2x00 in vanilla kernel
> > 2.6.25-rc2, there are no material differences.  (There was a slight
> > change in the declaration a variable in rt2x00usb.c but it is
> > immaterial.)
> > 
> > I compiled up the working mid-January version of rt2x00 and mac80211
> > under kernel 2.6.25-rc2 and I get exactly the same result as I reported
> > earlier, namely I get a kernel panic as soon as I try to associate.  It
> > looks therefore as if something has changed within the remainder of the
> > kernel which has caused rt2x00 (and possibly mac80211?) to break.
> > 
> > This probably explains the problem another user reported with rt61.
> 
> Perhaps something similar like:
> http://bugzilla.kernel.org/show_bug.cgi?id=10058
> in there a reference is made to the following patch:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc2/2.6.25-rc2-mm1/broken-out/revert-send-a-single-notification-on-device-state-changes.patch
> 
> Does applying that help?

I'm afraid not, Ivo. The test I ran last night was against 2.6.25.-rc2-git4 and
that already has this patch applied. Furthermore, I have another card that uses
the rtl8180 driver and that works reliably. I, therefore, suspect that my problem
lies within the rt61pci driver or the rt2x00 infrastructure.

Chris
> 
> Ivo
> 



-- 
Beauty is in the eye of the beerholder.

  parent reply	other threads:[~2008-02-21 23:05 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 12:06 2.6.25-rc2 regression in rt61pci wireless driver 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 [this message]
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
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=200802212304.28731.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=chris@cvine.freeserve.co.uk \
    --cc=dcbw@redhat.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).