linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@comcast.net>
To: srideep.devireddy@wipro.com
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Problems starting /sbin/init
Date: Sun, 15 Jan 2006 04:13:38 -0500	[thread overview]
Message-ID: <43CA1242.6030101@comcast.net> (raw)
In-Reply-To: <6AD9F6A5F6E096408F0B703773355A070E705B@CHN-SNR-MBX01.wipro.com>

srideep.devireddy@wipro.com wrote:
> Hello David ,
> 
>   I am bringing up  Montavista Linux on mpc8272 custom board .But as we completed almost all the configurations and linux is booting well till the NFS or Ramdisk file system is mounted . then it hangs  .. when i tried to debug i saw the /sbin/init in the init/main.c is not getting executed . i had printk and checked all the printks are executed but not the /sbin/init and the printks after the init is also executed .so this /sbin/init is not getting excecuting and i am not getting any messages .
> 
> Thanks & Regards
> Srideep Reddy D
> Wipro Technologies
> 
> 
Srideep;

	I was eventually able to resolve my problem. My serial console driver
was inadvertently using the physical address of the uart and not the
virtual address. When the TLB entry created in head_4xx.S for that
physical address eventually got overwritten - which coincidentally
occured after loading /init (or /bin/sh or ....) but prior to their
outputting anything.

	It is possible but unlikely you are having a similar problem.

	Regardless, you can isolate your problem further. You can sprinkle
prink's inside init/main.c to figure out exactly how far you are getting.
	If you are actually getting to attempting to start /init, you can
change main.c to start the program of your choice instead of init.
I started with "Hello World" in ppc assmebler with no library dependencies.
	You can enable SHOW_SYSCALLS and find out what system calls are
occuring immeditely prior to your system running off the rails.

	And I am sure others may have even more and better ideas.


Dave

  parent reply	other threads:[~2006-01-15  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 15:19 Need help for Linux hangs jimmy liu
2005-12-08 16:05 ` Vitaly Bordug
2005-12-08 23:21   ` Wolfgang Denk
2005-12-08 23:19 ` Wolfgang Denk
2006-01-04  7:05   ` Problems starting /init David H. Lynch Jr.
     [not found]     ` <6AD9F6A5F6E096408F0B703773355A070E705B@CHN-SNR-MBX01.wipro.com>
2006-01-15  9:13       ` David H. Lynch Jr. [this message]
2006-01-04 23:03   ` David H. Lynch Jr.
2006-01-04 23:20     ` Geoff Thorpe
2006-01-04 23:19   ` RESEND:Problems " David H. Lynch Jr.
2006-01-09 18:45     ` Shawn Jin

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=43CA1242.6030101@comcast.net \
    --to=dhlii@comcast.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=srideep.devireddy@wipro.com \
    /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;
as well as URLs for NNTP newsgroup(s).