[lkml]   [2012]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectchroot under kernel 3.4.x gives core dumps
    When I try under both kernel versions to chroot into a user mode linux
    image, I often get this :

    + mount -o loop /home/tfoerste/virtual/uml/gentoo_unstable /mnt/loop
    + mount -t proc none /mnt/loop/proc
    + mount -o bind /dev /mnt/loop/dev
    + mount -o bind /dev/pts /mnt/loop/dev/pts
    + mount -o bind /usr/portage /mnt/loop/usr/portage
    + mount -o bind /usr/local/portage /mnt/loop/usr/local/portage
    + mount -o bind /tmp/uml_portage /mnt/loop/var/tmp/portage
    + chroot /mnt/loop /bin/bash
    /home/tfoerste/workspace/bin/ line 55: 4143 Segmentation
    fault (core dumped) chroot /mnt/loop /bin/bash

    The core file itself is only 400 KB in size and the back trace with gbd
    is meaningless :

    Core was generated by `/bin/bash'.
    Program terminated with signal 11, Segmentation fault.
    #0 0xb75cac00 in ?? ()
    (gdb) bt
    #0 0xb75cac00 in ?? ()
    #1 0xb76f4ff4 in ?? ()
    Cannot access memory at address 0xffffffdc

    In the rare cases, where the chroot doesn't crash, all subsequent
    commands cores instead.

    Furthermore it seems, that the boinc grid software has problems too
    under kernel 3.4.1.

    All kernel 3.3.x works fine.

    Toralf Förster
    pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
    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-06-05 00:01    [W:0.042 / U:3.404 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site