LinuxQuestions.org - Startup Hang after "Using /etc/random-seed to initialize /dev/urandom"

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Startup Hang after "Using /etc/random-seed to initialize /dev/urandom" (https://www.linuxquestions.org/questions/slackware-14/startup-hang-after-using-etc-random-seed-to-initialize-dev-urandom-790126/)

Startup Hang after "Using /etc/random-seed to initialize /dev/urandom"

Hi,

I recently tried to upgrade from 2.6.23 to 2.6.32 but
kept on getting VFS errors. I had overwritten the
old 2.6.23 kernel so there was no going back. Luckily,
I had the 2.4.31 kernel still in the /boot directory.

Anyway, I finally got some time to figure out the VFS
issues and I managed to solve the VFS kernel panics.
It was probably a forgotten configuration setting
during the make menuconfig. Now it boots up
only to hang right after the "Using /etc/random-seed
to initialize /dev/urandom".

Looking at the rc.S script, the next section
does the dd if=/dev/urandom of=/etc/random-seed count=1 ...

I know for a fact that it isn't that line that
hangs the system. I commented out that line and
it still hangs.

Strange thing is that I can boot up 2.4.31 with no
problem; but with 2.6.x, I get a hang-up. I did a
google and came up with something about rc.udev.new,
which I don't have.

Can someone point out to me what is executed right after
/etc/rc.d/rc.S? Or maybe point out where it might
be hanging? (To be honest, it's either a hang up or
a process that's taking an extraordinary long time to
run.)

Any help appreciated.

Dm

AFAIK it is /etc/rc.d/rc.M. On Slackware 13.0, rc.M has this after the initial comment block (line number included)

Code:

 16 # Tell the viewers what's going to happen.

17 echo "Going multiuser..."

Presumably you don't see "Going multiuser...". It might help to add this at the end of rc.S

Code:

echo 'rc.S ending'

Quote:

Originally Posted by catkin (Post 3869232)

AFAIK it is /etc/rc.d/rc.M. On Slackware 13.0, rc.M has this after the initial comment block (line number included)

Code:

 16 # Tell the viewers what's going to happen.

17 echo "Going multiuser..."

Presumably you don't see "Going multiuser...". It might help to add this at the end of rc.S

Code:

echo 'rc.S ending'

Hi catkin,

I added the "End of rc.S" to the end of the rc.S file and then
"Beginning of rc.M" to the rc.M file. Now when the system boots up,
it goes to display "End of rc.S" and just stays there.

Since everything above the 'Beginning of rc.M' line are comments,
therefore, it isn't going directly to the rc.M right after rc.S.
So I'm pretty much stumped. Just wondering. Is it normal to have
devpts mounted to /dev/pts?

Now that I've setup a backup Internet route, I can take my time
to figure this problem out while having the ability to go online.

[--Edit--]
After looking at it boot to 2.4.32 with no problems, I noticed
that in the 2.4.32 bootup sequence, right after the 'End of rc.S',
it goes to "INIT: runtime 3" (or something like that.. I mistakenly
changed the terminal and now cannot page up to see the message.)
Then it displays "Beginning of rc.M". So between rc.S and rc.M,
something else is running (or is being executed).

Dm.

Quote:

After looking at it boot to 2.4.32 with no problems, I noticed
that in the 2.4.32 bootup sequence, right after the 'End of rc.S',
it goes to "INIT: runtime 3" (or something like that.. I mistakenly
changed the terminal and now cannot page up to see the message.)
Then it displays "Beginning of rc.M". So between rc.S and rc.M,
something else is running (or is being executed).

This will be /sbin/init the main init process PID 1 that runs what it finds in /etc/inittab. This is the main controlling process calling /etc/rc.d/rc.S then /etc/rc.d/rc.M.

Quote:

Originally Posted by bgeddy (Post 3875768)

This will be /sbin/init the main init process PID 1 that runs what it finds in /etc/inittab. This is the main controlling process calling /etc/rc.d/rc.S then /etc/rc.d/rc.M.

So the init process is hanging between rc.S and rc.M or rather
it's stuck after running rc.S. Could something make init stick?

I'm not even sure where to debug this issue.

Any help very much appreciated.

Dm

Something in inittab? Here's Slackware 13.0's as-installed with non-functional lines stripped:

Code:

c@CW8:~$ cat /etc/inittab.org | grep -E -v '(^$)|(^#)'

id:3:initdefault:

si:S:sysinit:/etc/rc.d/rc.S

su:1S:wait:/etc/rc.d/rc.K

rc:2345:wait:/etc/rc.d/rc.M

ca::ctrlaltdel:/sbin/shutdown -t5 -r now

l0:0:wait:/etc/rc.d/rc.0

l6:6:wait:/etc/rc.d/rc.6

pf::powerfail:/sbin/genpowerfail start

pg::powerokwait:/sbin/genpowerfail stop

c1:1235:respawn:/sbin/agetty 38400 tty1 linux

c2:1235:respawn:/sbin/agetty 38400 tty2 linux

c3:1235:respawn:/sbin/agetty 38400 tty3 linux

c4:1235:respawn:/sbin/agetty 38400 tty4 linux

c5:1235:respawn:/sbin/agetty 38400 tty5 linux

c6:12345:respawn:/sbin/agetty 38400 tty6 linux

x1:4:respawn:/etc/rc.d/rc.4