From: "Chan Kim" <ckim@etri.re.kr>
To: <kernelnewbies@kernelnewbies.org>
Subject: busybox shell doesn't come up or get stuck.. where should I look or how should I debug it?
Date: Fri, 12 Aug 2022 17:32:16 +0900 [thread overview]
Message-ID: <03db01d8ae26$07e35980$17aa0c80$@etri.re.kr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1542 bytes --]
Hi all,
I'm trying to boot linux with minimal config on our FPGA board which is
under development.
After months of trying (but I tried this intermittently) I think I'm about
to see the shell prompt.
(there was a bug in interconnect driver that I found yesterday, this caused
a long delay)
Anyway, when I run linux kernel on a qemu machine, the boot process ends
like this at the shell prompt.
(The echo '### INIT SCRIPT ###' was put in /init script which is in the
initramfs)
Run /init as init process
### INIT SCRIPT ###
mount: mounting none on /tmp failed: Invalid argument
This boot took 2.12 seconds
/bin/sh: can't access tty; job control turned off
/ #
/ #
Now, when I run it on our FPGA board using u-boot, it ends like this.
Run /init as init process
### INIT SCRIPT ###
mount: mounting none on /tmp failed: Invalid argument
This boot took 0.00 seconds
/bin/sh: can't acce
So it seems this init_kernel thread executes /init and /init excutes /bin/sh
at the end.
this is the /init script.
#!/bin/sh
echo "### INIT SCRIPT ###"
mkdir /proc /sys /tmp
mount -t proc none /proc
mount -t sysfs none /sys
mount -t tmpfs none /tmp
echo -e "\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\n"
#ifconfig eth0 10.0.2.15 netmask 255.255.255.0 up
#route add default gw 10.0.2.2
exec /bin/sh
Somehow the busybox applet /bin/sh is stuck somewhere.
Can anybody tell me where I should look? Or how to debug this?
Thanks in advance!
Chan Kim
[-- Attachment #1.2: Type: text/html, Size: 9983 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2022-08-12 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 8:32 Chan Kim [this message]
2022-08-18 5:19 ` busybox shell doesn't come up or get stuck.. where should I look or how should I debug it? Chan Kim
2022-08-18 6:02 ` Chan Kim
2022-08-19 11:50 ` Chan Kim
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='03db01d8ae26$07e35980$17aa0c80$@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.