[lkml]   [2012]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Oops in ext3_block_to_path.isra.40+0x26/0x11b
    On Fri, Mar 16, 2012 at 2:04 PM, George Spelvin <> wrote:
    > Unfortunately, this is the only time it's happened to me with kernel
    > modesetting *on*.  Would repeated checksums of a kernel tree be a good
    > way to detect random memory stomping?

    Yes, doing filesystem checksums tends to be a good way to find memory
    corruption, since a lot of memory tends to be caches.

    Another approach is to have a stupid program that allocates an array
    of say about half the physical memory, and writes some nicely
    recognizable pattern to it. Then, every minute or two, re-check the

    The advantage of the pattern approach is that it makes it possible to
    show things like "these X bytes at offset Y in the page changed",
    which can give hints about the source of corruption. The full virtual
    address is obviously useless, but the "offset within page" can be
    quite useful for figuring out corruption patterns even if you can't
    necessarily see which physical page it actually is.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2012-03-16 22:13    [W:0.020 / U:4.904 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site