From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@bombadil.infradead.org>,
Bob Copeland <me@bobcopeland.com>, Pavel Roskin <proski@gnu.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] Crda oopses the system
Date: Mon, 01 Jun 2009 01:48:30 +0300 [thread overview]
Message-ID: <1243810110.5298.5.camel@maxim-laptop> (raw)
In-Reply-To: <43e72e890905311524m6bab2648qb778dd9952da8537@mail.gmail.com>
On Sun, 2009-05-31 at 15:24 -0700, Luis R. Rodriguez wrote:
> On Sun, May 31, 2009 at 1:54 PM, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> > On Sun, 2009-05-31 at 15:47 +0300, Maxim Levitsky wrote:
> >> On Sun, 2009-05-31 at 02:22 -0400, Luis R. Rodriguez wrote:
> >> > On Fri, May 22, 2009 at 01:08:22PM +0300, Maxim Levitsky wrote:
> >> > > I am talking about
> >> > >
> >> > > BUG_ON(!country_ie_regdomain);
> >> > > in net/wireless/reg.c
> >> >
> >> > Please try this patch and leave a window open with this running:
> >> >
> >> > iw event
> >> >
> >> > Please be sure to grab iw from git, not sure if the reg events
> >> > have all gone into an official release yet. What I'm looking for
> >> > is whether or not a previous 11d setting was already processed
> >> > or if the !country_ie_regdomain condition happens from the first
> >> > 11d processing.
> >> >
> >> > Luis
> >> >
> >> > diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> >> > index f87ac1d..1b60dfc 100644
> >> > --- a/net/wireless/reg.c
> >> > +++ b/net/wireless/reg.c
> >> > @@ -2171,7 +2171,11 @@ static int __set_regdom(const struct ieee80211_regdomain *rd)
> >> > * the country IE rd with what CRDA believes that country should have
> >> > */
> >> >
> >> > - BUG_ON(!country_ie_regdomain);
> >> > + if (WARN_ON(!country_ie_regdomain)) {
> >> > + kfree(rd);
> >> > + rd = NULL;
> >> > + return -EINVAL;
> >> > + }
> >> > BUG_ON(rd == country_ie_regdomain);
> >> >
> >> > /*
> >> > @@ -2268,6 +2272,8 @@ int regulatory_init(void)
> >> > if (IS_ERR(reg_pdev))
> >> > return PTR_ERR(reg_pdev);
> >> >
> >> > + country_ie_regdomain = NULL;
> >> > +
> >> > spin_lock_init(®_requests_lock);
> >> > spin_lock_init(®_pending_beacons_lock);
> >> >
> >>
> >>
> >> I'll test this today.
> >> I have iw from git.
> >>
> >> Best regards,
> >> Maxim Levitsky
> >>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Here it is:
> >
> >
> >> wlan0 (phy #0): assoc 00:1b:9e:d8:77:02 -> 00:1b:77:f1:7c:29 status: 0: Successful
> >> wlan0 (phy #0): disassoc 00:1b:77:f1:7c:29 -> 00:1b:9e:d8:77:02 reason 3: Deauthenticated because sending station is leaving (or has left) the IBSS or ESS
> >> wlan0 (phy #0): scan finished
> >> wlan0 (phy #0): auth 00:23:4d:3c:80:27 -> 00:1b:77:f1:7c:29 status: 0: Successful
> >> wlan0 (phy #0): assoc 00:23:4d:3c:80:27 -> 00:1b:77:f1:7c:29 status: 0: Successful
> >> phy #0: regulatory domain change: intersection used due to a request made by a country IE on phy0
> >>
> > dmesg attached (I use nvidia drivers)
>
> I see only one userspace request *attempt* sent for the country IE in
> your log ("Calling CRDA" bits). So my assumption that we were only
> "trying" to send to userspace one request for the given country IE as
> far as cfg80211 is concerned is accurate however it does not seem
> accurate that the kernel won't send two requests or that userspace
> will not respond twice.
>
> > On top of that there are few more very bold bugs in ath5k AP mode:
>
> Your best bet is to report these separately.
I did report some, I will report the reset, this is just a remainder,
cause today I had really bad time with ath5k. I was trying to compile
kernel on aspire one using distcc.
Thanks a lot for fixing the crda bug. I guess there is no need to test
it, I already had that test removed, and everything did work fine.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-31 22:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 5:04 [BUG] Crda oopses the system Maxim Levitsky
2009-05-05 18:46 ` Luis R. Rodriguez
2009-05-06 10:47 ` Maxim Levitsky
2009-05-06 20:34 ` Pavel Roskin
2009-05-10 12:20 ` Maxim Levitsky
2009-05-10 18:33 ` Luis R. Rodriguez
2009-05-10 19:34 ` Maxim Levitsky
2009-05-10 19:36 ` Luis R. Rodriguez
2009-05-12 15:05 ` Maxim Levitsky
2009-05-12 17:24 ` Luis R. Rodriguez
2009-05-12 17:34 ` Maxim Levitsky
2009-05-12 22:00 ` Luis R. Rodriguez
2009-05-12 22:07 ` Maxim Levitsky
2009-05-13 21:28 ` Luis R. Rodriguez
2009-05-13 23:08 ` Maxim Levitsky
2009-05-13 23:12 ` Luis R. Rodriguez
2009-05-13 23:22 ` Maxim Levitsky
2009-05-13 23:28 ` Luis R. Rodriguez
2009-05-13 23:47 ` Maxim Levitsky
2009-05-14 0:07 ` Luis R. Rodriguez
2009-05-14 14:20 ` Bob Copeland
2009-05-19 14:17 ` Maxim Levitsky
2009-05-22 0:20 ` Maxim Levitsky
2009-05-22 0:36 ` Luis R. Rodriguez
2009-05-22 10:08 ` Maxim Levitsky
2009-05-31 6:22 ` Luis R. Rodriguez
2009-05-31 12:47 ` Maxim Levitsky
2009-05-31 20:54 ` Maxim Levitsky
2009-05-31 21:13 ` Maxim Levitsky
2009-05-31 22:24 ` Luis R. Rodriguez
2009-05-31 22:48 ` Maxim Levitsky [this message]
2009-06-01 0:32 ` Bob Copeland
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=1243810110.5298.5.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@bombadil.infradead.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=proski@gnu.org \
/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