Hi Doug, Am Montag, 22. Juni 2015, 16:00:42 schrieb Doug Anderson: > On Thu, Jun 4, 2015 at 6:12 AM, Kaukab, Yousaf <yousaf.kaukab@xxxxxxxxx> wrote: > >> > >>>> Tested-by: Heiko Stuebner <heiko@xxxxxxxxx> > >> > >>>> > >> > >>>> ---------- 8< ------------------ > >> > >>>> [ 19.799200] BUG: sleeping function called from invalid context > >> > >>>> at > >> > >>> > >> > >>> mm/slab.c:2863 > >> > >>> > >> > >>> Will I see a patch for fixing this ? > >> > >> > >> > >> I am currently on a business trip and can't look into this for at > >> > >> least a couple of weeks. > >> > > > >> > > John, since this is your driver, could you fix it up ? > >> > > >> > Hi Felipe, > >> > > >> > I've been out of the office for the past 2 weeks and am catching up on > >> > stuff now. > >> > > >> > I'll take a look at it later this week if I don't hear anything from > >> > Yousaf. > > > > I have patches to fix this issue (and another one). I will send them out > > hopefully tomorrow. > I noticed that (33ad261 usb: dwc2: host: spinlock urb_enqueue) is now > in linuxnext, so I pulled it (and many other) changes into the > chromeos-3.14 kernel for testing. I still see the problem that Heiko > reported. Note that aside from the warning, this causes all sorts of > "spinlock recursion" issues and an eventual freeze on my system. > > Until Yousaf's patch has landed it seems as if we should do a revert > of (33ad261 usb: dwc2: host: spinlock urb_enqueue) to avoid regressing > existing systems. I'm not exactly sure which patches have already landed, but did you try with "usb: dwc2: fix sleep while atomic bugs" [0] from 2015-06-12 by chance? This did seem to fix the issue for me. Heiko [0] http://www.spinics.net/lists/linux-usb/msg125921.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
