From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wf-out-1314.google.com ([209.85.200.174]:34048 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761414AbZEMVpY convert rfc822-to-8bit (ORCPT ); Wed, 13 May 2009 17:45:24 -0400 Received: by wf-out-1314.google.com with SMTP id 26so589625wfd.4 for ; Wed, 13 May 2009 14:45:25 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <9b2b86520905120709v4bd00e1eo4da26e6c5f75c4ba@mail.gmail.com> References: <1242030669.6930.10.camel@johannes.local> <9b2b86520905120709v4bd00e1eo4da26e6c5f75c4ba@mail.gmail.com> From: "Luis R. Rodriguez" Date: Wed, 13 May 2009 14:45:05 -0700 Message-ID: <43e72e890905131445s5583481bgb556a925247368db@mail.gmail.com> Subject: Re: [RFT v9] rfkill: rewrite To: Alan Jenkins Cc: Johannes Berg , linux-wireless , Vivek Natarajan , Easwar Krishnan , Nataraj Sadasivam , Kathir Ganapthy , Ponmudi Ramachandran , Senthilkumar Balasubramanian Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, May 12, 2009 at 7:09 AM, Alan Jenkins wrote: > On 5/11/09, Johannes Berg wrote: >> This patch completely rewrites the rfkill core to address >> the following deficiencies: > > Btw, git-apply nitpicks on your whitespace > > =C2=A0 =C2=A0rfkill-rewrite.patch:4335: space before tab in indent. > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mutex_unlock(&rfkill_global_= mutex); > =C2=A0 =C2=A0warning: 1 line adds whitespace errors. > > > I tested on todays wireless-testing, aka v2.6.30-rc5-23297-gbf2c6a3. > Somehow, it triggers an OOPS > > Function: req_reg_info_regd > Process: modprobe > > Call trace: > wiphy_apply_custom_regulatory > ath5k_regd_init > ath5k_reg_notifier > ath5k_pci_probe > ... > > Photo: > > The kernel then hangs later on in the boot process. =C2=A0It responds= to > SysRq, but does not echo normal keypresses. =C2=A0SysRq+P shows that = the > kernel is in the idle task. =C2=A0I left it for three minutes, but I = didn't > get any trace from the hung task detector or soft lockup detector. > > At first I thought it must be a problem with wireless-testing. > However, it went away when I eventually tried un-applying the rfkill > rewrite patch. I think my new 4 patches should address this and it'd be great to hear your tests as you can reproduce easily. We are able to see something like this but only after 3 hours of testing. Since it seems you might be able to reproduce quickly it would help. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html