lkml.org 
[lkml]   [2011]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: iotop: khugepaged at 99.99% (2.6.38.X)
    > Aaarg, wrong kernel tree. I patched and compiled 2.6.38.5.
    > Do you think it is important to stay with 2.6.38.2, after
    > we know 2.6.38.4 is also affected?

    I bootet 2.6.38.5.aa1 ("aa1" for the "make-it-worse-patch")
    but nothing happened within an hour. So I put some stress
    on the system:

    $ stress --cpu 80 --io 40 --vm 20 --vm-bytes 1280M --timeout 5s
    stress: info: [31924] dispatching hogs: 80 cpu, 40 io, 20 vm, 0 hdd

    The command _did_not_end_ after five seconds. I tried to
    kill it after ~15 minutes. I had no success killing it.

    "nr_isolated_anon" was "0" all the time. 'ps xal' hung its
    terminal. Just like 'pkill stress', 'pkill firefox', 'pkill
    thunderbird', 'pkill pkill' and 'pkill -9 stress'.

    top/iotop: http://pastebin.com/raw.php?i=BCtmHpmX
    ps xal: http://pastebin.com/raw.php?i=ED71cuKe
    zoneinfo: http://pastebin.com/raw.php?i=aBNjz1Up

    I hit SysRq-[lmtw] several times, you'll find all kernel
    messages (/var/log/messages) from boot to reboot here:

    http://pastebin.com/raw.php?i=VG28YRbi

    The system did not shutdown properly, I waited some time
    for sshd to stop and eventually hit SysRq-sub.

    Thomas


    \
     
     \ /
      Last update: 2011-05-06 15:35    [W:0.037 / U:0.252 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site