lray@CIVILGATE.CE.UIUC.EDU (Ray) (09/30/89)
I've been having considerable problems with /etc/reboot. Over 50% of the
time, the node being rebooted fails to come up with one of the
following symptoms:
1. The node says the clock is off and waits forever for a y/n.
2. The node freezes prior to going into self tests.
3. The node fails to shut down at all.
Condition 1 is the most understandable. If there has been a crash and
the hardware clock has been scrambled, then it seems clear a sanity
check is in order.
Condition 2 could be something to do with the ROM level of the cpu.
I have not done enough testing to verify when this happens.
Condition 3. is the strangest. It acts like the node is in service mode
when I know for a fact it is in normal mode (yes, pressing the reset
button works as expected).
The problem with all this is that I simply cannot easily get access to
the offices where there is a node at all times. This means the node
stays down for an unacceptably long period of time while I wait for
a key to become available.
---------------------------------------------------------------------
Does anyone know how /etc/reboot works, enough to give me some insight
as to whats going on here?
Leland Ray
UIUC - CE Dept.
(217) 333-3821kts@quintro.uucp (Kenneth T. Smelcer) (10/01/89)
In article <8909291722.AA00609@civilgate.ce.uiuc.edu> lray@CIVILGATE.CE.UIUC.EDU (Ray) writes: > >I've been having considerable problems with /etc/reboot. Over 50% of the >time, the node being rebooted fails to come up with one of the >following symptoms: > > 1. The node says the clock is off and waits forever for a y/n. > 2. The node freezes prior to going into self tests. > 3. The node fails to shut down at all. > [ explanations of above conditions ] >--------------------------------------------------------------------- > >Does anyone know how /etc/reboot works, enough to give me some insight >as to whats going on here? > Have you tried /etc/reboot with different types of nodes? I've noticed on our system that 'reboot' works fine with our DN3000s, but fails 90% of the time on our DN3500 nodes. Note: all our nodes had SR10.1 loaded from one AA on a 3500, so I don't think it's a garbled/out-dated version problem. Just for the record, I really enjoy having the /etc/reboot option available. It makes my life much easier, especially when I can dial in from home and reset things, instead of always having to be on the scene. > Leland Ray > UIUC - CE Dept. > (217) 333-3821 -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ken Smelcer Quintron Corp. quintro!kts@lll-winken Quincy, IL tiamat!quintro!kts@uunet
jnp@mjolner.tele.nokia.fi (J|rgen N|rgaard) (10/11/89)
(System: DN3500/SR10.1/BSD4.3/ADUS X11R3) Okay, my experience is that reboot'ing from the DM is unlikely to work; ends with trashed screen. Cure: reset ! Run via rlogin's or xterm's work in more (>>90%) of the cases. Whereas shutdown -r doesn't in either case. -- -- -- | Regards, J|rgen N|rgaard ('|' is '\o{}' in \LaTeX{}) | | e-mail: jnp@tele.nokia.fi | telephone: <..>-358-0-511-5671 | -- mail: Nokia Telecommunications, PL 33, SF-02601 Espoo, Suomi Finland --