Sun Microsystems, Inc.  Sun System Handbook - CD 2.1.8 April 2005 Internal/Partner Edition
   Home | Systems | Components | General Info | Search | Feedback

Asset ID:1-25-40646-1
Update Date:Tue Sep 14 00:00:00 MDT 2004
Keywords:Netra X1, V100, V120, V210, V240, V440, stair stepping, stair step, /etc/path_to_inst, 

console output stair steps during boot due to incorrect serial port entries in /etc/path_to_inst

Tim Sutton

2004-09-14


Problem Statement

Incorrect serial port entries in /etc/path_to_inst may cause boot problems on the Netra[TM] X1, V100, V120, V210, V240 and V440 with the below scenarios.

Scenario #1:

Console is attached to the serial port, and console messages may stair step during boot.
For example:
	Executing last command: boot                                          
	Boot device: disk:a  File and args: 
	SunOS Release 5.8 Version Generic_108528-06 64-bit
	Copyright 1983-2000 Sun Microsystems, Inc.  All rights reserved.
	configuring IPv4 interfaces: dmfe0.
                                   Hostname: greenlantern
                                                         NOTICE: dmfe0: PHY 1 link down
       		NOTICE: dmfe1: PHY 1 link down
                                     NOTICE: dmfe0: PHY 1 link up 10 Mbps Half-Duplex
     	The system is coming up.  Please wait.
                                           checking ufs filesystems
                                                                   /dev/rdsk/c0t0d0s7: is clean.

	LOM event: 10/12/2001 20:39:49 LOM time reference
	01 20:39:49 GMT LOM time reference
                                  NIS domainname is csclab.Central.Sun.COM
                                                   starting rpc services: rpcbind keyserv ypbind done.
                                             Setting netmask of dmfe0 to 255.255.255.0
      Setting default IPv4 interface for multicast: add net 224.0/4: gateway greenlantern
         syslog service starting.
                                 Print services started.
                                                        volume management starting.
   		The system is ready.

	greenlantern console login:             

Scenario #2:

If nothing is attached to the serial port - boot will hang until a console is attached. 
The boot will then resume at "configuring IPv4 interfaces: dmfe0".  
For example:      
	configuring IPv4 interfaces: dmfe0.
                                                               Hostname: greenlantern
	     NOTICE: dmfe0: PHY 1 link down
                                   NOTICE: dmfe1: PHY 1 link down
                                                         NOTICE: dmfe0: PHY 1 link up 10 Mbps Half-Duplex
                                 The system is coming up.  Please wait.
                                                                       checking ufs filesystems
               /dev/rdsk/c0t0d0s7: is clean.

	LOM event: 10/12/2001 20:48:9 LOM time reference
	001 20:48:9 GMT LOM time reference
                                  NIS domainname is csclab.Central.Sun.COM
                                                   starting rpc services: rpcbind keyserv ypbind done.
                                             Setting netmask of dmfe0 to 255.255.255.0
    	  Setting default IPv4 interface for multicast: add net 224.0/4: gateway greenlantern
         syslog service starting.
                                 Print services started.
                                                        volume management starting.
	   The system is ready.
	greenlantern console login: 
            

Resolution

Check the serial port entries in /etc/path_to_inst:

# grep serial /etc/path_to_inst

The entries should look like:

	"/pci@1f,0/isa@7/serial@0,2e8" 1 "su"
	"/pci@1f,0/isa@7/serial@0,3f8" 0 "su"

If these entries are incorrect or missing, then take one of actions below:

1) If this system was just installed with JumpStart[TM], then most likely the jumpstart
   image is corrupt. Recreate the image and jumpstart the client again.


2) If the system had been functioning normally before this problem occurred, then 
   recreate the path_to_inst file:       
	# mv /etc/path_to_inst ..
  	# init 0
  	ok boot -a

  	[Press Return to select default values for everything except /etc/path_to_inst.
  	Enter y to rebuild /etc/path_to_inst when prompted]:
  
  	The /etc/path_to_inst on your system does not exist or is empty.
  	Do you want to rebuild this file [n]? y

      

Internal Only

 Copyright 1994-2005 Sun Microsystems, Inc.    All rights reserved.
 Legal Terms Privacy Policy Feedback