Bug 11650

Summary:	Bug in rt2x00 rt73usb driver in latest git kernel
Product:	Drivers	Reporter:	Rafael J. Wysocki (rjw)
Component:	network-wireless	Assignee:	Ivo van Doorn (IvDoorn)
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	IvDoorn
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.27-rc	Subsystem:
Regression:	---	Bisected commit-id:
Attachments:	0001-rt2x00-Fix-race-conditions-in-flag-handling.patch

Description Rafael J. Wysocki 2008-09-26 05:43:09 UTC

Subject    : Bug in rt2x00 rt73usb driver in latest git kernel
Submitter  : "Paul Eddington" <eddingtonpaul@googlemail.com>
Date       : 2008-09-24 18:02
References : http://marc.info/?l=linux-kernel&m=122227940126260&w=4

This entry is being used for tracking a regression from 2.6.26.  Please don't
close it until the problem is fixed in the mainline.

Comment 1 John W. Linville 2008-09-26 05:52:02 UTC

This bug has lingered forever, I don't think it is a regression.

Comment 2 John W. Linville 2008-09-26 13:54:28 UTC

Created attachment 18061 [details]
0001-rt2x00-Fix-race-conditions-in-flag-handling.patch

Can you try this patch?

Comment 3 Rafael J. Wysocki 2008-09-26 14:08:01 UTC

On Friday, 26 of September 2008, John W. Linville wrote:
> On Fri, Sep 26, 2008 at 08:53:39PM +0200, Ivo van Doorn wrote:
> > On Friday 26 September 2008, Ivo van Doorn wrote:
> > > On Friday 26 September 2008, Rafael J. Wysocki wrote:
> 
> > > > Well, according to the information I've received from Paul this
> particular
> > > > problem is a regression from 2.6.26, so it's been added to the list of
> recent
> > > > regressions.
> > > 
> > > Seriously, this error message is the most annoying rt2x00 error message
> _ever_.
> > > It should have been fixed 3 kernels ago, but it keeps popping up again
> and again.
> > > 
> > > Paul, what is the git commit id with which you encountered this bug?
> > 
> > Oh and please test rt2x00.git as well, since some patches which should fix
> this issue
> > are in there (and in wireless-testing.git) but not in Linus' tree since
> they are scheduled
> > for 2.6.28.
> 
> Can you identify which fixes those are likely to be?
> 
> John
> 
> P.S.  Of course, as you pointed out this isn't a new bug.  Since it
> existed in 2.6.26, then technically it isn't a regression under
> current merging practices as I understand them.

Comment 4 Rafael J. Wysocki 2008-09-26 14:09:20 UTC

Dropped from the list of recent regressions.

Comment 5 John W. Linville 2008-10-07 08:45:09 UTC

Sent email to "Paul Eddington" <eddingtonpaul@googlemail.com> requesting his attention to this bug.

Comment 6 Ivo van Doorn 2009-01-27 15:09:50 UTC

Well this is actually a duplicate of #9622

Comment 7 Ivo van Doorn 2009-01-27 15:10:02 UTC


*** This bug has been marked as a duplicate of bug 9622 ***