Re: [Rt2400-devel] 2.6.25-rc2 regression in rt61pci wireless driver

[Chris Vine <chris@cvine.freeserve.co.uk>]

On Wed, 2008-02-20 at 11:05 -0500, Dan Williams wrote: 
> On Tue, 2008-02-19 at 23:04 +0000, 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 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 2.6.24 (last known working version for you).
> > > > > > > - kernel 2.6.25-rc2 (after ifup, before TX dies)
> > > > > > > - kernel 2.6.25-rc2 (after ifup, after TX dies)
> > > > > > >  
> > > > > > 
> > > > > > These diagnostics are attached, with obvious filenames.
> > > > > 
> > > > > Thanks. I think I found something, please test below patch:
> > > > > 
> > > > 
> > > > I've tried the patch but, unfortunately, my wireless LAN still dies after a few pings.
> > 
> > rt2x00 2.0.14 is broken with my rt73 stick in the vanilla 2.6.25-rc2
> > kernel (not wireless-2.6/rt2x00 git).  The modules load when I plug the
> > stick in but I then get a complete kernel lock up with two flashing
> > leds.  Nothing is recorded to system logs.  The last logged messages are
> > that usbcore has registered new interface driver rt73usb, and that the
> > rate control algorithm has been selected on phy0.  This happens whether
> > the simple or pid mac80211 rate control algorithms have been chosen.
> > 
> > This is a shame because 2.0.14 was working really well for me until the
> > mac80211 changes 2 or 3 weeks ago broke it.  (Shortly followed by the
> > release of 2.1.*).
> 
> Switch to a VT with Ctl+Alt+1, then plug the stick in, and take a
> picture of the panic if one shows up.  _Something_ should show up on the
> VT.

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!

There is a complete lock up.  Even the two leds don't send a dump in
morse code (if that is still a feature of the 2.6 kernels).  They just
flash together at 1 second intervals.

However, I do not have debugging enabled on 2.6.25-rc2 (I was just
interested to see how it worked).  If it is thought to be useful I can
recompile the kernel with debugging enabled, but this should be
reproducible by anyone with a rt73 stick.

By way of a further data point, I can scan OK using 2.6.25-rc2 and it
will report all the available access points in my area.  But as soon as
association is attempted, it blows up.

Chris