init process freezed after run_init_process

From: rjy (rjy_at_angelltech.com)
Date: 03/31/05

  • Next message: Nick Orlov: "Re: 2.6.12-rc1-mm3: class_simple API" 
    Date:	Thu, 31 Mar 2005 12:20:23 +0800
To: linux-kernel@vger.kernel.org

    Hi,

    My computer freezed after the kernel start. It started
    with normal console messages and stopped with these messages:
    ------------------------------
    ... (just as the normal ones.)
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    Bridge firewalling registered
    802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    All bugs added by David S. Miller <davem@redhat.com>
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    VFS: Mounted root (ext3 filesystem) readonly.
    Freeing unused kernel memory: 136k freed
    ------------------------------
    The kernel started successfully: it echos on keyboard pressing.
    But the init process just REFUSE to work. GOD !

    This is my grub config:
    -----------------------------
    root (hd0,0)
    kernel /bzImage.via.386 root=/dev/ram0 rw ramdisk=49152
    initrd /initrd.gz
    -----------------------------

    My CPU is VIA Samuel 2. Memory 128M. Chipset VIA VT82C686.
    I configed my kernel with CyrixIII CPU family type,
    and with RAM, INITRD and ext2/3 also on.

    This kernel can work properly without initrd and ramdisk.
    This kernel can work properly on intel CPU and chipset
    even with initrd and ramdisk. :( Have I missed something?

    I have KGDBed the starting process and run_init_process
    returned OK: initrd decompressed properly and open_exec
    returned non-zero.

    Any instructions, references, or insight much appreciated.

    Thanks
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Nick Orlov: "Re: 2.6.12-rc1-mm3: class_simple API"

    Relevant Pages

    • Re: booting from ISO image on HD?
      ... >> through customized initrd files for each one. ... > between the loopback device and the underlying file (the iso image). ... I have to insmod the loop kernel module(e.g. ... how can you boot it from an initrd??? ...
      (comp.os.linux.misc)
    • Re: fsck fails during boot with 2.6.9-34.0.1.EL kernel because root filesystem is already rw mou
      ... I think there was a little fault in building the new initrd. ... The mount-command of the init-script is wrong and makes confusing, e.g.: first the root-filesystem must mount read/write, it accepts. ... It looks like in the early stage of the booting, when the kernel is using the initrd to load the ... I still do not understand why in my new initrd file, with the new kernel, the root filesystem is ...
      (RedHat)
    • Re: booting from ISO image on HD?
      ... I'm not going to write the pivot root script, ... > through customized initrd files for each one. ... I have to insmod the loop kernel module(e.g. ... The idea is that either you build what you need to boot into your ...
      (comp.os.linux.misc)
    • Re: 2.6.26-rc5-mm1
      ... In my case it turns out to be gcov patches - in which I'm interested ... initrd overwrites kernel: When kernel and initrd are loaded to static ... minimal memory configuration any more. ...
      (Linux-Kernel)
    • Re: 2.6.8 stock kernel bug
      ... >> If you make the new initrd the same file name as the old one, grub should ... The shipped initrd ... Look in the kernel devices file. ... Kernel executes the commands from /linuxrc on the initrd file system. ...
      (comp.os.linux.hardware)