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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
