From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Huub Reuver <h_reuver@mantell.xs4all.nl>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [Oops-report] problem with ath9k at shutdown
Date: Tue, 18 May 2010 09:53:30 -0700 [thread overview]
Message-ID: <20100518165330.GC4209@tux> (raw)
In-Reply-To: <20100518054140.GA15675@navi.boekerij>
On Mon, May 17, 2010 at 10:41:40PM -0700, Huub Reuver wrote:
> On Mon, May 17, 2010 at 01:24:04PM -0400, John W. Linville wrote:
> > On Mon, May 17, 2010 at 09:55:31AM -0700, Luis R. Rodriguez wrote:
> > > On Mon, May 17, 2010 at 07:32:41AM -0700, John W. Linville wrote:
> > > > Did you try 2.6.34? I'm pretty sure we merged a fix for this...
> > >
> > > Ditto, and I think it was not related to ath9k but mac80211.
> > >
> > > Was it this maybe?
> > >
> > > commit a9f042cbe5284f34ccff15f3084477e11b39b17b
> > > Author: Ming Lei <tom.leiming@gmail.com>
> > > Date: Sun Feb 28 00:56:24 2010 +0800
> > >
> > > ath9k: fix lockdep warning when unloading module
> > >
> > > Johannes had noted:
> > >
> > > "I think the problem is that the locking for sta_notify changed, and a
> > > patch that was written for the new locking was backported to the old,
> > > irq-disabled, locking."
> >
> > Yeah, maybe that is what I was thinking about....
>
> The traces do not look similar to me, but I'm not a programmer.
>
> I have done a few tests:
> 2.6.32.9 not affected
> 2.6.32.13 affected
> 2.6.33.3 affected
> 2.6.33.4 affected
> 2.6.34 the problem seems to have been fixed.
>
> Sorry for my slow report and response.
> Thanks for your quick answer, I'll have to switch to 2.6.34 for a
> production kernel.
Eh, I am not sure what happened here... this must've been a fix
regression as I do not recall seeing this on earlier 2.6.32.y releases.
Can you try an earlier 2.6.32.y?
Luis
next parent reply other threads:[~2010-05-18 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100516172012.GA8607@chidori>
[not found] ` <20100517143240.GA2436@tuxdriver.com>
[not found] ` <20100517165531.GE12203@tux>
[not found] ` <20100517172403.GB2436@tuxdriver.com>
[not found] ` <20100518054140.GA15675@navi.boekerij>
2010-05-18 16:53 ` Luis R. Rodriguez [this message]
2010-05-19 18:40 ` [Oops-report] problem with ath9k at shutdown Luis R. Rodriguez
2010-05-19 21:35 ` Luis R. Rodriguez
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=20100518165330.GC4209@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=h_reuver@mantell.xs4all.nl \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.