On 28 September 2012 19:40, 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 *** > Your modules.order seems to have been tweaked afterwards because it > contains the compressed module names. I send you the one included in our installer where we now alter it. Here's the files from our regular kernel. > The patch I sent tries to solve > this by indexing the modules by their uncompressed names.
Attachment:
modules.tar.xz
Description: Binary data
