>Looking at this one, I am still puzzeled where 0xffffffffa008772b and >0xffffffffa008772b comes from ... some driver, bridge ...?
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? -- 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
