On Thu, Jun 13, 2013 at 10:09:58AM +0200, Arend van Spriel wrote: > On 06/12/2013 11:19 PM, Stephen Warren wrote: > >On 06/06/2013 03:36 PM, Stephen Warren wrote: > >>On 06/06/2013 03:10 PM, Arend van Spriel wrote: > >>>On 06/04/13 14:58, Arend van Spriel wrote: > >>>>On 06/04/2013 12:56 AM, Stephen Warren wrote: > >>>>>(John, note that this commit is part of the pull request you sent to > >>>>>Dave today) > >>>>> > >>>>>Arend, > >>>>> > >>>>>Commit 9390ace "brcmfmac: free net device when registration fails" > >>>>>causes a regression. > >>>>> > >>>>>I had the BCM4330 firmware present in my root fs, whereas my HW is a > >>>>>BCM4329. With this patch applied, I get a kernel panic on boot. With it > >>>>>reverted, I see that no issues of that nature. This is true in > >>>>>next-20130531 (and also 5/30 and 6/1 but not earlier). A bisect of > >>>>>Linus's tree followed by a merge of John's wireless pull request from > >>>>>today pointed at this same commit. > >>>> > >>>>Thanks, Stephen > >>>> > >>>>I will look into this. > >>> > >>>Hi Stephen, > >>> > >>>Can you try the attached patch? If it does not solve the issue, could > >>>you provide a log. > >> > >>Yes, that works great, thanks. > >> > >>Tested-by: Stephen Warren <swarren@xxxxxxxxxx> > > > >Did this patch get applied anywhere? I was hoping it'd go into 3.10-rc* > >given it's a user-triggerable backtrace introduced in 3.10-rc*. > > Hi Stephen, > > The patch went into the wireless-next tree. Given recent events with > our patch series I am a bit more carsful to tag patches for 3.10. > Your issue is user-triggerable but the scenario to get there can be > avoided. But you are right it was introduced in the 3.10-rc cycle. I > leave it to John to decide. > > Regards, > Arend I've just applied it to the wireless tree. I doubt if it will make -rc6, but it might make the final 3.10. John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
