On 2 October 2012 14:30, Lucas De Marchi <lucas.demarchi@xxxxxxxxxxxxxx> wrote: >>> Sorry, I couldn't really test this. Did the patch I sent solve the issue? >> >> no, depmod doesn't work anymore. It display the following and then remains >> stuck on a futex: >> *** glibc detected *** depmod: malloc(): memory corruption: >> 0x00000000016e7db0 *** > > argh... sorry, my bad. The attached patch should fix this crash. It does revert the order of output of "modprobe -R pci:v0000103Cd00003238sv0000103Csd00003211bc01sc04i00" so modules.order seems to be enforced. output is the same as before for the hardware I tested. I'll ask the original reporter to test a new install ISO with patched kmod that I'm currently uploading. Thx -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
