public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Pavel Roskin <proski@gnu.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] Crda oopses the system
Date: Wed, 13 May 2009 01:07:31 +0300	[thread overview]
Message-ID: <1242166051.26484.7.camel@maxim-laptop> (raw)
In-Reply-To: <43e72e890905121500k61545ff3mcdf099a08178b72c@mail.gmail.com>

On Tue, 2009-05-12 at 15:00 -0700, Luis R. Rodriguez wrote:
> On Tue, May 12, 2009 at 10:34 AM, Maxim Levitsky
> <maximlevitsky@gmail.com> wrote:
> > On Tue, 2009-05-12 at 10:24 -0700, Luis R. Rodriguez wrote:
> >> On Tue, May 12, 2009 at 8:05 AM, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> >> > On Sun, 2009-05-10 at 12:36 -0700, Luis R. Rodriguez wrote:
> >> >> On Sun, May 10, 2009 at 12:34 PM, Maxim Levitsky
> >> >> <maximlevitsky@gmail.com> wrote:
> >> >> > On Sun, 2009-05-10 at 11:33 -0700, Luis R. Rodriguez wrote:
> >> >> >> On Sun, May 10, 2009 at 5:20 AM, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> >> >> >> > On Wed, 2009-05-06 at 16:34 -0400, Pavel Roskin wrote:
> >> >> >> >> gdb /lib/modules/`uname -r`/kernel/net/wireless/cfg80211.ko
> >> >> >> >
> >> >> >> > I have recompiled the kernel with debugging info.
> >> >> >> >
> >> >> >> > This is new backtrace:
> >> >
> >> > Ok, here is what I found:
> >> >
> >> > The real BUG_ON that fires up is at
> >> >
> >> > wireless/reg.c: __set_regdom: BUG_ON(!country_ie_regdomain)
> >> >
> >> > Confirmed by replacing it with printk.
> >> >
> >> >
> >> > I attach a beacon sample that triggers this:
> >>
> >> Thanks for that. Was this from wireless-testing? If so as of what SHA1
> >> sum? Can you provide steps to reproduce? What AP? What card?
> > wireless-testing, b2382a4aeff07a481ccf860e4f716b48b52e3781
> 
> That HEAD is buggy, its missing a fix for the minstrel/pid fix.
> Although since you are running iwl3945 it explains why you haven't
> seen that oops.
> 
> Will look into this -- thanks. How easy can you reproduce BTW? Does it
> happen immediately upon assoc? Does it happen with other APs at the
> university?
Happens always when I try to associate.
In fact, after a boot, this oops is in dmesg, and whole system
semi-frozen. (can't get root, etc probably due to locks held)


Other APs, I don't see many other APs there, (you mean other essids,
right?)

Most of them are encrypted anyway.


I have just compiled HEAD of wireless-testing, I see how well it will
work tomorrow.


Thanks in advance,
	Maxim Levitsky
> 
>   Luis


  reply	other threads:[~2009-05-12 22:07 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 [this message]
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
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=1242166051.26484.7.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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