kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Chan Kim" <ckim@etri.re.kr>
To: <kernelnewbies@kernelnewbies.org>
Subject: RE: busybox shell doesn't come up or get stuck.. where should I look or how should I debug it?
Date: Fri, 19 Aug 2022 20:50:58 +0900	[thread overview]
Message-ID: <074001d8b3c1$f2e343f0$d8a9cbd0$@etri.re.kr> (raw)
In-Reply-To: <063501d8b2c8$1381b2e0$3a8518a0$@etri.re.kr>


[-- Attachment #1.1: Type: text/plain, Size: 1687 bytes --]

Hi, all,

I set a variable to true just before calling the ramdisk_exeucte_cmd (which
is /init in this case) in the kernel_init function, 

And added printk in schedule() function so that it prints something it is
called and when the previous variable is true.

And found the program stops after the schedule function is called. Like
this.

 

Hello! i=115

Hello! i=116

Helloschedule!

schedule!

 

I checked the timer interrupt number was given correctly in the device tree
(that's why schedule was called by the timer..).

I stopped the experiment to do something else but will resume it next week
by adding some prints. 

If anyone has any idea about what might be wrong, please tell me.

Thanks for reading.

 

Chan Kim

From: Chan Kim <ckim@etri.re.kr> 
Sent: Thursday, August 18, 2022 3:02 PM
To: kernelnewbies@kernelnewbies.org
Subject: RE: busybox shell doesn't come up or get stuck.. where should I
look or how should I debug it?

 

I had mistakenly omitted '-static' option when making init program.(repeated
Hello! Print).

So now the board output looks like this.

(...)

### point 106-1

Run /init as init process

### point 106-2, ret = 0

Hello! i=0

Hello! i=1

Hello! i=2

...

Hello! i=115

Hello! i=116

Hello! i=117

He            <=== hangs.

So the running the 'init' program (whether it's a script or a binary
program) is ok.

The binary 'init' program stops after printing Hello 117 times so there
seems to be more basic problem in H/W or device tree.  And when the init
script ran 'exec /bin/sh', the shell didn't start so 'running exec inside a
script' can have a problem. 

If anyone has a suggestion or advice, I welcome it.

 

Thank you!

Chan Kim

 


[-- Attachment #1.2: Type: text/html, Size: 10806 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2022-08-19 11:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  8:32 busybox shell doesn't come up or get stuck.. where should I look or how should I debug it? Chan Kim
2022-08-18  5:19 ` Chan Kim
2022-08-18  6:02   ` Chan Kim
2022-08-19 11:50     ` Chan Kim [this message]

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='074001d8b3c1$f2e343f0$d8a9cbd0$@etri.re.kr' \
    --to=ckim@etri.re.kr \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).