[lkml]   [2001]   [Dec]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.4.16 deadlock in kswapd
    FORT David wrote:
    > Hi,
    > today i was transfering some files between two drives(reiserfs->ext3) and
    > suddenly everything locked up. I sys-rqed to show the executed IP and
    > every five times i've tryed it was showing the following stack trace:
    > ...
    > >>EIP; c0111657 <flush_tlb_others+e7/110> <=====
    > Trace; c01117b5 <flush_tlb_page+75/80>
    > Trace; c012f052 <swap_out+312/4b0>
    > ...

    Dodgy hardware, I'm afraid - it looks like a cross-CPU interrupt
    was sent but not received. Not uncommon.

    > The interesting thing is that i don't have any swap, so i'm really
    > interested
    > in knowing why kswapd is envolved here.

    Look at the swapout code: it calls flush_tlb_page() in preparation
    for swapping a page out. It then tries to allocate swap space,
    finds there is none and bales out. This can comsume quite a lot
    of CPU under some circumstances.

    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: 2005-03-22 13:14    [W:0.032 / U:177.688 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site