On Tue, Apr 18, 2017 at 3:03 PM, Linda Knippers <linda.knippers@xxxxxxx> wrote: > On 04/18/2017 02:06 PM, Dan Williams wrote: >> The workqueue may still be running when the devres callbacks start >> firing to deallocate an acpi_nfit_desc instance. Stop and flush the >> workqueue before letting any other devres de-allocations proceed. >> >> Reported-by: Linda Knippers <linda.knippers@xxxxxxx> >> Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx> >> --- >> >> I was able to produce a reliable nfit_test crash failure by running the >> tests on hardware *and* disabling all debug messages. That last detail >> may be why I have been seeing much less frequent failures. With this >> change, in addition to the previous fix [1], I was again able to >> complete a successful run. > > It seems a bit better because I can sometimes get a test to complete > but then I'll get a panic when I try again. Some forward progress... let me go back and try your test script on my bare metal config because this patch only addressed the reliable failure I was seeing for a single run of "make check". > The footprints are the same > as before, sometimes when unloading the module but sometimes in a kfree > or related function. > > I'd be interested in your .config file and exactly how you're building > your bare metal kernel. Here's the config and build + install steps I'm performing. https://gist.github.com/djbw/73946ed4e8623aa1ded1b3615ba6d82b -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
