Skip to contentSkip to conversation

system hangs after reboot

DISCUSSION Arno Seitzinger 3 participants 4 messages Dec 16, 2002

lore
Share & tools
lore
#0 lore raw

Hi NG,

for a couple of days, my Suse Linux 8.1 (2.4.19) on a HP Omnibook XE3 Laptop shows a strange behaviour: it hangs after a reboot (shutdown -r now od from KDE). First it starts as usual, but freezes after "switching to runlevel 5", when initializing the random number generator and the network. I pasted the output of a good and a bad boot.msg below.

My last actions, before I noticed it doesn't reboot anymore, were:
- use the cellphone to access internet
- create a new user because of OpenOffice store failure
- clear tmp directory in single user mode (because of OpenOffice store failure - was this stupid?)
- new (workstation) installation of OpenOffice

Nayone around who can give me a clou where to look next? Arno

***boot.msg when system hangs
=============================
[...]
Master Resource Control: previous runlevel: N, switching to runlevel:
5

done<notice>killproc: kill(30,3)

INIT: Entering runlevel: 5

<notice>/etc/init.d/rc5.d/S01isdn start <notice>'/etc/init.d/rc5.d/S01isdn start' exits with status 0 <notice>/etc/init.d/rc5.d/S01random start <notice>'/etc/init.d/rc5.d/S01random start' exits with status 0 <notice>/etc/init.d/rc5.d/S05network start

***boot.msg normally
====================
[...]
Master Resource Control: previous runlevel: N, switching to runlevel:
5

done<notice>killproc: kill(30,3)

INIT: Entering runlevel: 5

<notice>/etc/init.d/rc5.d/S01isdn start <notice>'/etc/init.d/rc5.d/S01isdn start' exits with status 0 <notice>/etc/init.d/rc5.d/S01random start <notice>'/etc/init.d/rc5.d/S01random start' exits with status 0 <notice>/etc/init.d/rc5.d/S05network start <notice>Initializing random number generator
done

Setting up network interfaces:

lo
done

eth0 (DHCP) startproc: execve (/sbin/dhcpcd) [ /sbin/dhcpcd -H -D
-N -Y -t 999999 -h esw44 eth0 ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh OLDPWD=/etc/sysconfig/network INIT_VERSION=sysvinit-2.82 RUN_FROM_RC=yes REDIRECT=/dev/tty1 COLUMNS=106 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/etc/sysconfig/network/scripts vga=791 RUNLEVEL=5 PWD=/etc/sysconfig/network PREVLEVEL=N LINES=34 HOME=/ SHLVL=4 _=/sbin/startproc DAEMON=/sbin/dhcpcd ]
<notice>pidofproc: dhcpcd 347

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#1 lore raw

Four questions about what you posted ...

1. In the "good init" sequence, what happens next? You're asking us to compare a bad init to nothing (as regards the part that is bad).

2. When you say the system "hangs" and "freezes", how carefully have you assessed that? How long have you waited before giving up? What happens if you CRTL-C when the system is "hung"?

3. What is eth0 and how does it connect to the Internet? If the problem is associated with a DHCP failure of some type, the details of the interface it is using may matter.

4. Is the problem only associated with a soft ("shutdown -r") reboot? If you do a power-down reboot, does the system boot and init properly?

Quoted 59 lines · Arno Seitzinger

Hi NG,

for a couple of days, my Suse Linux 8.1 (2.4.19) on a HP Omnibook XE3 Laptop shows a strange behaviour: it hangs after a reboot (shutdown -r now od from KDE). First it starts as usual, but freezes after "switching to runlevel 5", when initializing the random number generator and the network. I pasted the output of a good and a bad boot.msg below.

My last actions, before I noticed it doesn't reboot anymore, were:
- use the cellphone to access internet
- create a new user because of OpenOffice store failure
- clear tmp directory in single user mode (because of OpenOffice store failure - was this stupid?)
- new (workstation) installation of OpenOffice

Nayone around who can give me a clou where to look next? Arno

***boot.msg when system hangs
=============================
[...]
Master Resource Control: previous runlevel: N, switching to runlevel:
5

done<notice>killproc: kill(30,3)

INIT: Entering runlevel: 5

<notice>/etc/init.d/rc5.d/S01isdn start <notice>'/etc/init.d/rc5.d/S01isdn start' exits with status 0 <notice>/etc/init.d/rc5.d/S01random start <notice>'/etc/init.d/rc5.d/S01random start' exits with status 0 <notice>/etc/init.d/rc5.d/S05network start

***boot.msg normally
====================
[...]
Master Resource Control: previous runlevel: N, switching to runlevel:
5

done<notice>killproc: kill(30,3)

INIT: Entering runlevel: 5

<notice>/etc/init.d/rc5.d/S01isdn start <notice>'/etc/init.d/rc5.d/S01isdn start' exits with status 0 <notice>/etc/init.d/rc5.d/S01random start <notice>'/etc/init.d/rc5.d/S01random start' exits with status 0 <notice>/etc/init.d/rc5.d/S05network start <notice>Initializing random number generator
done

Setting up network interfaces:

lo
done

Quoted 8 lines

eth0 (DHCP) startproc: execve (/sbin/dhcpcd) [ /sbin/dhcpcd -H -D
-N -Y -t 999999 -h esw44 eth0 ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh OLDPWD=/etc/sysconfig/network INIT_VERSION=sysvinit-2.82 RUN_FROM_RC=yes REDIRECT=/dev/tty1 COLUMNS=106 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/etc/sysconfig/network/scripts vga=791 RUNLEVEL=5 PWD=/etc/sysconfig/network PREVLEVEL=N LINES=34 HOME=/ SHLVL=4 _=/sbin/startproc DAEMON=/sbin/dhcpcd ]
<notice>pidofproc: dhcpcd 347

--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#2 lore raw

Here's yet another set of questions to look at :)

1. If you change /etc/init.tab so that the system boots into run level 3, then reboot, do you get any errors?
2. If not, try logging in as a user and running "startx" to see what errors you get (if any) on the terminal.
3. It sounds like you have a network thing going on. If you wait long enough, it might start anyway. sendmail often does this when your host table doesn't agree with your IP address. Other programs also have this problem. Therefore, check that you have an "/etc/hosts" file and that it is correct and complete (at least as far as info about the problem machine goes).

P.

Quoted 98 lines · Ray Olszewski

Four questions about what you posted ...

1. In the "good init" sequence, what happens next? You're asking us to compare a bad init to nothing (as regards the part that is bad).

2. When you say the system "hangs" and "freezes", how carefully have you assessed that? How long have you waited before giving up? What happens if you CRTL-C when the system is "hung"?

3. What is eth0 and how does it connect to the Internet? If the problem is associated with a DHCP failure of some type, the details of the interface it is using may matter.

4. Is the problem only associated with a soft ("shutdown -r") reboot? If you do a power-down reboot, does the system boot and init properly?

Quoted 59 lines · Arno Seitzinger

Hi NG,

for a couple of days, my Suse Linux 8.1 (2.4.19) on a HP Omnibook XE3 Laptop shows a strange behaviour: it hangs after a reboot (shutdown -r now od from KDE). First it starts as usual, but freezes after "switching to runlevel 5", when initializing the random number generator and the network. I pasted the output of a good and a bad boot.msg below.

My last actions, before I noticed it doesn't reboot anymore, were:
- use the cellphone to access internet
- create a new user because of OpenOffice store failure
- clear tmp directory in single user mode (because of OpenOffice store failure - was this stupid?)
- new (workstation) installation of OpenOffice

Nayone around who can give me a clou where to look next? Arno

***boot.msg when system hangs
=============================
[...]
Master Resource Control: previous runlevel: N, switching to runlevel:
5

done<notice>killproc: kill(30,3)

INIT: Entering runlevel: 5

<notice>/etc/init.d/rc5.d/S01isdn start <notice>'/etc/init.d/rc5.d/S01isdn start' exits with status 0 <notice>/etc/init.d/rc5.d/S01random start <notice>'/etc/init.d/rc5.d/S01random start' exits with status 0 <notice>/etc/init.d/rc5.d/S05network start

***boot.msg normally
====================
[...]
Master Resource Control: previous runlevel: N, switching to runlevel:
5

done<notice>killproc: kill(30,3)

INIT: Entering runlevel: 5

<notice>/etc/init.d/rc5.d/S01isdn start <notice>'/etc/init.d/rc5.d/S01isdn start' exits with status 0 <notice>/etc/init.d/rc5.d/S01random start <notice>'/etc/init.d/rc5.d/S01random start' exits with status 0 <notice>/etc/init.d/rc5.d/S05network start <notice>Initializing random number generator
done

Setting up network interfaces:

lo
done

Quoted 8 lines

eth0 (DHCP) startproc: execve (/sbin/dhcpcd) [ /sbin/dhcpcd -H -D
-N -Y -t 999999 -h esw44 eth0 ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh OLDPWD=/etc/sysconfig/network INIT_VERSION=sysvinit-2.82 RUN_FROM_RC=yes REDIRECT=/dev/tty1 COLUMNS=106 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/etc/sysconfig/network/scripts vga=791 RUNLEVEL=5 PWD=/etc/sysconfig/network PREVLEVEL=N LINES=34 HOME=/ SHLVL=4 _=/sbin/startproc DAEMON=/sbin/dhcpcd ]
<notice>pidofproc: dhcpcd 347

--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Signature · 11 lines
Paul Furness

Systems Manager

Steepness is an illusion caused by flat things leaning over.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#3 lore raw

Hi Ray and Paul,
thanks for your interest.

I investigated a little bit deeper, but am stil clueless:

_changed 20:20 CET: no more clueless._ A couple of days ago I removed the PCMCIA CAN-Card which was innocently sitting in my cardslot for months. Maybe it received a different configuration when I re-inserted it. After removal of the CAN-Card, the system reboots as usual. Thank you for your assistance.

Quoted 2 lines

1. If you change /etc/init.tab so that the system boots into run level 3, then reboot, do you get any errors?

Errors (errormessages), no, but the system hangs like before.

Quoted 6 lines

3. It sounds like you have a network thing going on. If you wait long enough, it might start anyway. sendmail often does this when your host table doesn't agree with your IP address. Other programs also have this problem. Therefore, check that you have an "/etc/hosts" file and that it is correct and complete (at least as far as info about the problem machine goes).

I also think it is a network problem because if I boot into a runlevel w/o network, the system does not freeze. It also does not freeze when I remove the network card from the configuration.
My /etc/hosts is

127.0.0.1       localhost
::1             localhost ipv6-localhost ipv6-loopback
fe00::0         ipv6-localnet
ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
127.0.0.2       esw44.mdom1     esw44

and was set up automatically by yast-setuptool

When the freeze occurs, the cursor stops blinking, the animated ball on the boot screen stops jumping and the system won't react to anything (ctrl-c, ctrl-alt-del etc), only power-off and display brightness. A cold boot always works, and it also boots up correctly when I do a warm reboot (shutdown -r now) but switch off the power the moment the bios screen appears.

Quoted 2 lines
Quoted 2 lines

1. In the "good init" sequence, what happens next? You're asking us to compare a bad init to nothing (as regards the part that is bad).

In the "bad init" sequence, the file ends after
<notice>/etc/init.d/rc5.d/S05network start

In the "good init" sequence, I cut the rest of the file after the configuration of eth0. ppp0 is started next (manual dialup w/ cellphone). After that, hotplugging services are started.

Quoted 3 lines
Quoted 3 lines

2. When you say the system "hangs" and "freezes", how carefully have you assessed that? How long have you waited before giving up? What happens if you CRTL-C when the system is "hung"?

I waited for about 15 minutes. ctrl-c does not do anything... but it doesn't do anything elsewhere in the bootup process anyhow...
I will let the machine sit overnight trying to boot, but I dont think it will bring us further. Is there a possibility to redirect

Quoted 3 lines
Quoted 3 lines

3. What is eth0 and how does it connect to the Internet? If the problem is associated with a DHCP failure of some type, the details of the interface it is using may matter.

eth0 is the only ethernet port on that machine (builtin Accton EN1216 card). The problem is not associated with a DHCP failure because the freeze also occurs when the machine is assigned a fixed IP-address

Quoted 2 lines
Quoted 2 lines

4. Is the problem only associated with a soft ("shutdown -r") reboot? If you do a power-down reboot, does the system boot and init properly?

2*Yes

Greets and thanks

Arno

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs