On 03/09/2015 13:10, "Eric Dumazet" <eric.duma...@gmail.com> wrote:
>On Thu, 2015-09-03 at 10:09 +0000, Shaun Crampton wrote: >> >... >> >> Is there anything I can do on a running system to help figure this >>out? >> >> Some sort of kernel equivalent to pmap to find out what module or >>device >> >> owns that chunk of memory? >> > >> >Hmm, perhaps /proc/kallsyms could point to something. >>0xffffffffa0087d81 >> >and 0xffffffffa008772b could be from the same module, if any. >> >> Any good: https://transfer.sh/szGRE/kallsyms ? >> > >seems to be cryptd module. > >Have you tried to run an pristine upstream kernel ? No, I haven't tried that; I'm not sure if it's feasible with CoreOS. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
