ITEM: BM6571L

Trying to configure console for kernel debug

Env:
  AIX 4.1.4
  Sysback 3.3.3.6
  RISC 43P and 370

Desc:
  Customer tried boot a 43p over the network from a 370 using sysback.
  It hangs on the boot up.

The customer followed these steps on debugging a network boot using
sysback:

How to debug a network boot...

REQUIREMENTS
  Sysback 3.3.2+
  Any Ascii Terminal 

STEPS TO BE DONE ON THE SERVER SYSTEM
-------------------------------------

1.  cd /usr/sbin
2.  cp mksbnetboot mksbnetboot.org
3.  vi mksbnetboot
      Search on bosboot (It should be found on your second hit)

    Change:

     bosboot -a -d $DEVICE -p $tmp_proto -b $BOOTIMAGE \\
             -k $bootdir/unix_$kernel -T $platform

   To:
    bosboot -I -a -d $DEVICE -p $tmp_proto -b $BOOTIMAGE \\
            -k $bootdir/unix_$kernel -T $platform

(Add a -I (upper case i) flag to the command)
 Save the file

4.  Create your boot image:
    /usr/sbin/mksbnetboot -B -d'ethernet' -T'rspc'
   (if your client is using a ethernet network) 

   /usr/sbin/mksbnetboot -B -d'token-ring' -T'rspc'
   (if your client is using a token-ring network) 

5.  nm -x /usr/lib/boot/unix_up | grep enter_dbg

    Example output:

    enter_dbg            D 0x0013d410  0x0004

    Write down the second fields number

    From the example above write this number down.
    13d410 

    

STEPS TO BE DONE ON THE CLIENT SYSTEM
-------------------------------------

6.  Connect a ascii terminal to S1 port on the RSPC system (40p, 43P or E20)
    Settings on the terminal have to be: 9600, 8, 1, and N
    You have to have a cable with a interposer on it or a cable and a 
    interposer.

7.  Start the network boot of the RSPC system (40p, 43P or E20)

8.  After the bootp and tftp are done the ascii terminal will display
    the kernal debugger information.
    Type this from the command prompt:
     st 13d410 2
    g

The led information and commands should then display durning the boot
on the ascii terminal.

NOTE: remember to change your mksbnetboot command back after this process
     has bee resolved.

It never got to the kernal debug part.  

Action:
Customer had been trying to use a PC as his console.  He 
went from a nine pin connection to a 25 pin and then back to
a 9 pin and this caused the problem.

Consulting with the group showed that a cable gets crossed
in this transfer.  Once the customer put the correct cable on
it worked

Next:
CWCA



Support Line: Trying to configure console for kernel debug ITEM: BM6571L

Dated: August 1996 Category: N/A

This HTML file was generated 99/06/24~13:30:21

Comments or suggestions?
Contact us