[lkml]   [2007]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted
    > __get_free_pages() of swiotlb_alloc_coherent() fails in rc3-mm1.
    > But, it doesn't fail on rc2-mm2, and kernel can boot up.

    That looks to be part of the problem here ... failing an order=3
    allocation during boot on a system that just a few lines earlier
    in the boot log reported "Memory: 37474000k/37680640k available"
    looks bad ... but perhaps having *more* memory is part of your problem.
    You may have run low on GFP_DMA memory because some allocation
    scaled by memory size has chewed up a lot of your memory. To check
    this try booting with a "mem=4G" parameter and see if that helps

    But it is also bad that the swiotlb() code failed to handle this.
    Can you check whether the problem is related to the size of the
    allocation being just over 256K (a magic number for swiotlb since
    IO_TLB_SEGSIZE is 128 times a slab size of 2k). Try changing
    lib/swiotlb.c to set IO_TLB_SEGSIZE to 256 instead.

    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: 2007-08-23 19:25    [W:0.021 / U:11.704 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site