public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: rt2400-devel@lists.sourceforge.net,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Paul Eddington <eddingtonpaul@googlemail.com>,
	linux-kernel@vger.kernel.org,
	Iwo Mergler <iwo@call-direct.com.au>
Subject: Re: [Rt2400-devel] Bug in rt2x00 rt73usb driver in latest git kernel
Date: Fri, 26 Sep 2008 21:22:34 +0200	[thread overview]
Message-ID: <200809262122.34259.IvDoorn@gmail.com> (raw)
In-Reply-To: <20080926190408.GE3483@tuxdriver.com>

On Friday 26 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?

It is at least this one, I need to double check if there are any others as well.

rt2x00: Fix race conditions in flag handling
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commit;h=9fe32736d2cf27dfbf25cb7536c4358cd0dab6de

> 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.

Exactly, the bug has been there since rt2x00 arrived in 2.6.24 but because
it is a race condition which occurs on rare occasions only it isn't reported that
often. In 2.6.26 were some fixes which made the occurence rate even smaller,
but they were still there for some users.

Ivo

  reply	other threads:[~2008-09-26 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 18:02 Bug in rt2x00 rt73usb driver in latest git kernel Paul Eddington
2008-09-26  5:29 ` Iwo Mergler
2008-09-26 12:52   ` Rafael J. Wysocki
2008-09-26 18:24     ` [Rt2400-devel] " Ivo van Doorn
2008-09-26 18:53       ` Ivo van Doorn
2008-09-26 19:04         ` John W. Linville
2008-09-26 19:22           ` Ivo van Doorn [this message]
2008-09-26 20:48             ` John W. Linville

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=200809262122.34259.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=eddingtonpaul@googlemail.com \
    --cc=iwo@call-direct.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rjw@sisk.pl \
    --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