On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: >> Hi all, >> >> Changes since 20130417: >> >> New Trees: rpmsg (actually added yesterday) >> ppc-temp (replacing powerpc for this week) >> >> The ceph tree gained a conflict against Linus' tree. >> >> The net-next tree gained a conflict against the infiniband tree. >> >> The usb tree gained a build failure so I used the version from >> next-20130417. >> >> I added two merge fix patches after the gen-gpio tree. >> >> The ppc-temp tree gained a conflict against the metag tree. >> >> The akpm tree lost a patch that turned up elsewhere. >> >> ---------------------------------------------------------------------------- >> > > Not sure what the root-cause for this call-trace is (see screenshot). > > This is reproducible when running my kernel build-script (4 parallel-make-jobs). > > Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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
