LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-19-2010, 02:01 AM   #1
DotMatrix
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackware
Posts: 6

Rep: Reputation: 0
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
 
Old 02-19-2010, 05:46 AM   #2
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
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'
 
Old 02-23-2010, 07:12 PM   #3
DotMatrix
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackware
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by catkin View Post
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.

Last edited by DotMatrix; 02-23-2010 at 07:52 PM.
 
Old 02-24-2010, 07:34 PM   #4
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 227Reputation: 227Reputation: 227
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.
 
Old 02-26-2010, 12:14 AM   #5
DotMatrix
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackware
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by bgeddy View Post
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
 
Old 02-26-2010, 12:34 AM   #6
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NOOB - DNS latency on FC6 - seems to "hang" eth0 at random intervals? How to fix? rylan76 Linux - Newbie 4 12-22-2006 12:34 PM
NOOB - DNS latency on FC6 - seems to "hang" eth0 at random intervals? How to fix? rylan76 Red Hat 1 12-22-2006 05:07 AM
NOOB - DNS latency on FC6 - seems to "hang" eth0 at random intervals? How to fix? rylan76 Linux - Networking 1 12-22-2006 04:45 AM
What is adsp0? and why cat /dev/urandom >/dev/adsp0 give me "no such device"? haimeltjnfg Linux - Hardware 2 05-09-2004 10:54 PM


All times are GMT -5. The time now is 06:17 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration