public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: rjy <rjy@angelltech.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: init process freezed after run_init_process
Date: Fri, 08 Apr 2005 10:40:42 +0800	[thread overview]
Message-ID: <4255EF2A.709@angelltech.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504071341500.27692@yvahk01.tjqt.qr>

> Apply these rules:
> 1.) If you do provide an initrd= thing, the initrd is being looked for 
> /linuxrc.

I have add /linuxrc, /init and /bin/init, all link to /sbin/init.
It just refuses to work ... :(

> Only VIA IDE chipset maybe, but you don't usually need that for just-initrd.
> You'd need that for the harddisks...

My harddisk works fine without initrd.

> 
> Make your own initrd and put a bash into it. Then start that, e.g. (for our 
> linux live cd), initrd=initrd.sqfs root=/dev/ram0 init=/bin/bash

I have tried these kernel parameters:
	init=/bin/bash
	init=/linuxrc
	init=/init
	init=/sbin/init
None works.

Also, after some google, I found that the format of initrd has changed.
I also tried a new initrd with cpio format. The kernel recognized it:
	Boot Logs:
	1) checking if image is initramfs... it is
	   Freeing initrd memory: 17583k freed
	2) loading drivers
	3) Freeing unused kernel memory: 128k freed

After the kernel start, I add breakpoints at cpu_idle and do_schedule.
cpu_idle never reached, only do_schedule did. Is that strange?

  reply	other threads:[~2005-04-08  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  4:20 init process freezed after run_init_process rjy
     [not found] ` <Pine.LNX.4.61.0503311113550.17113@yvahk01.tjqt.qr>
2005-04-07  3:39   ` rjy
2005-04-07 11:46     ` Jan Engelhardt
2005-04-08  2:40       ` rjy [this message]
2005-04-08 17:45         ` Jan Engelhardt
2005-04-19  9:14           ` rjy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4255EF2A.709@angelltech.com \
    --to=rjy@angelltech.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox