MODULE 17

INTERPRETING BOOT SEQUENCE

Overview 17-3
Objective 17-3
Purpose 17-3
Instructions 17-3
Sequoia Boot Sequence 17-4
Overview 17-4
Sequoia Monitor Boot 17-4
LynxOS Boot 17-4
Sequoia Application Boot 17-4
Sequoia 3.nn Boot 17-5
Sequoia 3.nn Boot Details 17-6
Summary 17-6
Anomalies 17-6
Boot Messages 17-7
System Messages 17-7
Error messages 17-9
System Behavior 17-9
Boot Sequence Example 17-10
Worksheet: Boot Sequence 17-14
Module 17 - Interpreting Boot Sequence Acuson Confidential

REVISION HISTORY

QRC P/N-REVISION INITIATOR APPROVAL DATE CHANGE

S. Williams July 1999 Incorporate reviewer comments

A3210 P/N 63326 Rev. 1 J. Madarasz S. Williams Dec. 2000 Initial Release

Module 17-2 Sequoia Service Training Manual P/N 63326 Rev. 1

Acuson Confidential Overview

OVERVIEW
OBJECTIVE To develop skills in interpreting the Sequoia system boot sequence
and using the information to troubleshoot any boot problem when a
system fails to power on or hangs.

PURPOSE If a Sequoia system fails to boot to Imaging, it may be impossible to

invoke SUI/ RSUI and run diagnostics. It is possible that the boot
sequence might be the only information available. The boot
sequence can be accessed on site by using a laptop with a serial Null
Modem cable or remotely by logging in with a serial modem.

INSTRUCTIONS 1 Listen to the presentation.

2 Log on to a Sequoia system with your laptop.
3 Capture a boot sequence.

P/N 63326 Rev. 1 Sequoia Service Training Manual Module 17- 3

Module 17 - Interpreting Boot Sequence Acuson Confidential

SEQUOIA BOOT SEQUENCE

OVERVIEW Sequoia Product Boot is a sequence of events from system power on
to the system ready state. In the system ready state, the ultrasound
imaging application is started and ready for use. Events in the boot
process are grouped into three sections below. Figure 17-1 shows
the simple flow of the Sequoia product boot:

Power On

Sequoia LynxOS Sequoia

Monitor Boot Boot Application Boot

System Ready

Figure 17-1 Sequoia Boot Sequence

SEQUOIA MONITOR The Sequoia Monitor Boot (seqmon) includes of all events from
BOOT system power on to the loading of the operating system. This
includes the basic bootstrapping code, testing of resources required
for booting the OS (PUT), starting image display, selection of boot
device, initialization of other CPUs, loading of monitor code,
processing PUT results, system configuration, and loading of
LynxOS.

LYNXOS BOOT The LynxOS Boot includes all events from the start of the LynxOS to
the start of the program that loads the imaging application. This
includes all the tasks for starting a UNIX OS, such as mount file
system, fsck, initialize device drivers, fork tty jobs, and start
daemons. Once the OS is running, it will fork a program to start
applications.

SEQUOIA The Sequoia Applications Boot includes all events that follow the
APPLICATION BOOT LynxOS Boot, including support for different operating modes,
security checking, initialization/setup of all 486 and C31
processors, hardware setup based on system configuration, starting
all the servers needed for imaging and, finally, start UISC. The
Sequoia application boot is also referred to as seq_boot.

Module 17-4 Sequoia Service Training Manual P/N 63326 Rev. 1

Acuson Confidential Sequoia Boot Sequence

SEQUOIA 3.NN BOOT The Sequoia 3.nn boot-time is about 22 seconds less than in the
previous release, for a current total boot time of about 95 seconds.
Messages to the user are more frequent and can be verbose upon
demand.
Boot messages and details are saved on the hard drive to assist
remote diagnostics. These messages include time stamps, which are
useful in monitoring boot time.

P/N 63326 Rev. 1 Sequoia Service Training Manual Module 17- 5

Module 17 - Interpreting Boot Sequence Acuson Confidential

SEQUOIA 3.NN BOOT DETAILS

SUMMARY The typical sequence of events in the boot process is shown below.
1 Boot monitor reads power-up keystroke, runs PUT, readies SCSI
device, loads OS, and starts OS.
2 LynxOS initializes, OS initializes device drivers, and starts /init,
which starts /bin/rc.
3 /bin/rc.fast starts CM program and rc.fast.
4 /bin/rc.fast checks and mounts file systems, checks system
configuration, then starts SUI, su_sboot (5 - 9), or fboot (8) as
needed.
5 Seq_boot and su_boot are scripts that are processed by the fboot
utility. They load environment variables, then become the sboot
user ID, then fork various tasks.
6 su_sboot script starts the seq_boot. This is an fboot script
7 seq_boot runs as before, and also creates following files:
fboot_env (the environment for forked tasks)
fboot_task (processes for fork before imaging)
fboot_post (processes to fork after imaging)
control_boot (control layer code to download)
8 fboot_task script forks all the imaging processes. It downloads the
control layer using the Sequoia Boot Utility (sbu). Output goes to
CM. This step replaces steps 5 - 9.
9 Application and control layer are started. Output goes to CM.
10 When UISC is imaging, it sends the ,cm.imaging message to CM.
11 CM starts post_boot to get harmony going. Post_boot also indicates
the fboot scripts are viable.
12 post_boot then runs each executable program found in seqdata/
usr/postboot. They are run in the background. These are:
httpd
harmony
network configuration

ANOMALIES Normal boot time at Sequoia 3.n is about 95 seconds. After any
configuration change, boot time ranges from 124-150 seconds, as
indicated by the message VALIDATING THE CONFIGURATION. In
addition, boot time is longer after an abrupt power off, hardware
changes, configuration change, configuration restore, data reset,
network changes, change of keystroke logging, or entering the
advanced tools menu.
For verbose boot sequence output, press MULTIHERTZ and V KEY
during power on.

Module 17-6 Sequoia Service Training Manual P/N 63326 Rev. 1

Acuson Confidential Boot Messages

BOOT MESSAGES
The monitor displays two messages as the system boots up,
including the following:
Title line: shows the current goal of the system (e.g. boot
Sequoia, start SUI, or Reboot); title line is generally black during
boot.
Task line: shows the major step towards that goal; the task line
is generally blue during boot.
Both lines are white when UISC is running, and turn yellow for
some error messages. There is also a graphic thermometer that
shows the approximate progress.

SYSTEM MESSAGES The following messages appear on the monitor as the Sequoia
system boots to imaging:

MESSAGE DESCRIPTION/CAUSE

SYSTEM STARTING... The system has just powered up and is waiting for the disk.
Once the boot device is located, it loads and starts the OS. The
monitor is not integrated with the fast boot code.
DIMAQ INITIALIZING... The OS has checked the disk and performed all actions during
the LynxOS boot. Now it is starting the Acuson specific parts of
the sequence:
eject the MO
manage the boot logs (RAM disk and the BBRAM)
if it is the first boot then it will build the network configuration and
start the SUI
check the system configuration. this step can result in CONPROM,
reboot, SUI, or just fall through
decode the boot key and system configuration to decide what to do

P/N 63326 Rev. 1 Sequoia Service Training Manual Module 17- 7

Module 17 - Interpreting Boot Sequence
The following messages may appear if DIMAQ fails to initialize:
CHECKING DISK INTEGRITY...
CLEARING USER DATA...
CONFIGURING DEVELOPMENT
NETWORK...
POWER UP TEST PROBLEM...
PROGRAMMING RDP: DO NOT
POWER-OFF...
PROGRAMMING DONE...
VALIDATING CONFIGURATION...
SEQUOIA APPLICATION
LOADING...
CLEARING USER DATA...
CLEARING AEGIS DATA...
APPLICATION INITIALIZING...
CALC APPLICATION STARTING...
Module 17-8
Acuson Confidential
The OS needs to check the disk in detail.
Data reset of the user partition was requested upon the last
invocation of the SUI. This operation is now being performed.
The system is in development mode and the network
filesystems are being mounted.
Continuing system boot. Seen if there was a PUT failure.
generally these messages are in yellow text.
Shown if the seqsys checking has decided to perform conprom
on RDP, as an example.
Shown when the CONPROM is complete.
The OS has started seq_boot to build the fboot scripts. The
system boot time will be 30 seconds or so slower. The font color
may change a few times in here.
The OS has started to fboot. The font color may change a few
times in here.
Clearing user data because of the clean option to seq_boot is
unlikely.
Continuing the clear of user data by clearing the AEGIS data.
seq_boot or fboot have completed and the applications are
initializing. UISC has just started and is reading in application
data. This message may flash during graphics initialization.
UISC has started to read in calc-related screen information.
UISC will then start imaging.
UISC has taken control of the screen because imaging is
imminent.
Sequoia Service Training Manual P/N 63326 Rev. 1
Acuson Confidential Boot Messages

ERROR MESSAGES The following messages appear on the Sequoia monitor, in addition
to those previously mentioned:

MESSAGE DESCRIPTION/CAUSE

SYSTEM REBOOTING... Possible causes include:

Rebooting after a software install
Seqsys configuration problem
Boot scrip failure to start SUI

STARTING SERVICE TOOL System boots to SUI when:

First reboot after SW install
Boot error
MULTIHERTZ + S
Configuration problem at boot (Seqsys)
Failure code from fboot or seq_boot
Window Management key during imaging

BOOT ERROR: SAVING SYSTEM
STATE...
APPLICATION BOOT ERROR:
SAVING SYSTEM STATE...
APPLICATION ERROR: SAVING
SYSTEM STATE...
Fatal error occurred during the boot sequence
that was not UISC.
Fatal error in the UISC during the boot
sequence.
Fatal error in the UISC during imaging.
After system state is saved, message is
replaced by the following:
PLEASE CALL (800) 9-ACUSON FOR
ASSISTANCE...

NOTE: Non-application errors during Imaging are indicated by the following

message within the UISC:
SYSTEM HAD AN INTERNAL ERROR...

SYSTEM BEHAVIOR The system performs a slow boot under following circumstances:
There was a file system check (fsck) performed
The accuracy of previous boot wasnt verified. This operation
takes about 100 seconds beyond the time imaging is available.
Any configuration changes: restore, data reset, install, etc.
Improper system shutdown
Security violation
Fatal error in the previous system operation
In all other instances, the system performs a fast boot (fboot).

P/N 63326 Rev. 1 Sequoia Service Training Manual Module 17- 9

Module 17 - Interpreting Boot Sequence Acuson Confidential

BOOT SEQUENCE EXAMPLE

bss_start: 0x1000, bss_end: 0x1008
PUT Loader Version 1.0, Built Jun 14 1996, 13:44:04.
bss_start: 0xd328, bss_end: 0xd8b0
PUT Version 1.09, Built Apr 17 1997, 08:20:22.
1.2.3.4.5.6.7.8.9.10.11.12.13.14.15.16.17.18.19.20.
21.22.23.24.
25.26.27.28.29.30.

Loading [/lynx.os.ssp] from SCSI dev. 1, part. 1, addr. 0x1000, flag 0x0
18.281360 rc a

DIMAQ Starting
20.298900 rc.fast a
0 0 2 0 0 3 0 0 0 0 16 0 0 0 4 480 0 PST+8:00 0xffffff00 SEQ50024 Acu-
sonService 1 0 8 0
19990209-100311 20.991740 date -d0 -z480
21.017880 Checking disk integrity
Checking disk /dev/nsd1c
Filesystem Ok
Checking disk /dev/nsd1d
Filesystem Ok
Mounting all file systems
System SEQ50024
Configuring Network Interface
add net default: gateway AcusonService

Sequoia 3.15
No PUT failures.

Checking system configuration

System Configuration check status 0 fast boot
27.725900 fboot /seqdata/msm/boot/fboot_task
Display Software Starting

fboot
control load
0) usr/sequoia/bin/sbu
1) -f
2) /seqdata/msm/boot/control_boot
/seqdata/msm/boot/control_boot
/seqdata/msm/boot/control_boot 1> # /usr/sequoia/bin/sbu -f /seqdata/
msm/boot/control_boot
/seqdata/msm/boot/control_boot 2> # Generated Fri Feb 5 16:54:23 PST
1999 by
/usr/sequoia/bin/seq_boot
/seqdata/msm/boot/control_boot 3> fdl off

Module 17-10 Sequoia Service Training Manual P/N 63326 Rev. 1

Acuson Confidential Boot Sequence Example

SCPU-style downloading of 486s

/seqdata/msm/boot/control_boot 4> alc
Booting alc with usr/sequoia/lib/rk/alc3.rk
/seqdata/msm/boot/control_boot 5> color
Booting color with usr/sequoia/lib/rk/cc.rk
/seqdata/msm/boot/control_boot 6> iop -r -l usr/sequoia/lib/rk/physio.rk -
x
/seqdata/msm/boot/control_boot 7> pmem f4000204 201
/seqdata/msm/boot/control_boot 8> vdb -l usr/sequoia/lib/rk/vdb.rk -x
/seqdata/msm/boot/control_boot 9> irb
Booting irb with usr/sequoia/lib/rk/irb.rk
/seqdata/msm/boot/control_boot 10> gain
Booting gain with usr/sequoia/lib/rk/gain.rk
/seqdata/msm/boot/control_boot 11> acp
Booting acp with usr/sequoia/lib/rk/acp.rk
/seqdata/msm/boot/control_boot 12> smm -r
/seqdata/msm/boot/control_boot 13> pmem f801ffc0 00000000
/seqdata/msm/boot/control_boot 14> smm -l usr/sequoia/lib/rk/smm.rk -x
/seqdata/msm/boot/control_boot 15> iop
Booting iop with usr/sequoia/lib/rk/iop.rk
/seqdata/msm/boot/control_boot 16> spectral
Booting spectral with usr/sequoia/lib/rk/spectral.rk
/seqdata/msm/boot/control_boot 17> audio
Booting audio with usr/sequoia/lib/rk/audio.rk
/seqdata/msm/boot/control_boot 18> sspIpc

sspIpc -i //usr/sequoia/bin/ipco
/seqdata/msm/boot/control_boot 19> q
X load
acq load
19990209-100331 40.810420
app load starting
19990209-100336 45.986220
Global Error Manager v1.5 built Thu Nov 19 14:47:26 PST 1998
1) *
Using device "/dev/rel" for reliable transport
BBRAM File fsckerr shows no errors
19990209-100237 168.882300 warn ssp-harmony-9991

gem is now: Process 34. Priority 17. Port 82

19990209-100342 51.440700
19990209-100342 51.743900 info ssp-gem-1000
##### GEM starting up #####

19990209-100342 35.957080 warn smm-smm_init-999

/s/ws/981118_3.15_ws/smm/archival/src/sdmMgr/SDMDataSet.cc/569
19990209-100342 35.957080 warn smm-smm_init-999
SDM Transfer Tests Passed!!
The SDM subsystem appears to be functioning correctly.

P/N 63326 Rev. 1 Sequoia Service Training Manual Module 17- 11

Module 17 - Interpreting Boot Sequence Acuson Confidential

19990209-100342 38.019840 error ssp-x_server-1003

v1.2/utils.c/907
19990209-100342 38.019840 error ssp-x_server-1003
X Server, seqSlidersInitCalibration: Unable to open dgc calibration file /
seqsys/config/dgccal.

19990209-100342 38.022920 error ssp-x_server-1003

v1.2/utils.c/907
19990209-100342 38.022920 error ssp-x_server-1003
DGC values will not be calibrated.

19990209-100342 40.126920 error smm-display-80000020

1.26//s/ws/981118_3.15_ws/utility/src/commLib/CommSeqIPC.cc/267

user name:Applications Starting

open X
19990209-100352 61.765040 warn acp-acquisition_session-999
/s/ws/981118_3.15_ws/acq/src/AcqSession/coord/AcqSession.cc/1351
19990209-100352 61.765040 warn acp-acquisition_session-999
--> xdcrIds (Aux/Right/Center/Left): fffffff7 / 3a / ff / 99
ActiveIds (Right/Center/Left): c000003a / ffff / 8000ffff
mxStatus (Flag / Entry / Exit / Motor): 0 / 0 / 0 / 0

Report Application Starting

load calc database
19990209-100408 77.685480 warn ssp-uisc-999
/s/ws/981118_3.15_ws/ui/calc/setupdb/cs_Database.cc/118
19990209-100410 77.685480 warn ssp-uisc-999
calc-calcsetupDB: cs_Database::loadDB called

19990209-100410 77.686300 warn ssp-uisc-999

/s/ws/981118_3.15_ws/ui/calc/setupdb/cs_Database.cc/71
19990209-100413 77.686300 warn ssp-uisc-999
calc-calcsetupDB: cs_Database::clearDB called

19990209-100413 82.517360 warn ssp-uisc-999

/s/ws/981118_3.15_ws/ui/calc/setupdb/cs_Manager.cc/317
get ISM data
init ultrasound apps: SR, Aegis
19990209-100435 82.517360 warn ssp-uisc-999
calc-calcsetupDB: cs_Manager::loadDB has completed
19990209-100435 104.499680 warn ssp-uisc-999
/s/ws/981118_3.15_ws/ui/uisc/LiveApplication.cc/494
19990209-100435 104.502140 warn acp-acquisition_session-999
/s/ws/981118_3.15_ws/acq/src/AcqSession/coord/AcqSession.cc/1557
19990209-100435 104.502140 warn acp-acquisition_session-999
XdcrId = 153 connectorId = 0

UISC: started calc power up thread ID 43

Module 17-12 Sequoia Service Training Manual P/N 63326 Rev. 1

Acuson Confidential Boot Sequence Example

19990209-100442 104.499680 warn ssp-uisc-999

Reading commands from file "startup"

Reading commands from file "revXCbase"
Reading commands from file "revXD"

Done

Reading commands from file "PPSdefs"

Reading commands from file "LineLimits"
Logging completed
19990209-100455 124.706820 error ssp-harmony-4201
Previous shutdown cause: user power off
19990209-100455 124.707160 warn ssp-harmony-4103
System startup #48 since previous BBRAM1 reset
19990209-100455 124.707500 warn ssp-harmony-4104
Up for 0.0 hours
19990209-100455 124.708020 warn ssp-harmony-4105
Cumulative on time 243.5 hours

P/N 63326 Rev. 1 Sequoia Service Training Manual Module 17- 13

 Module 17 - Interpreting Boot Sequence Acuson Confidential

WORKSHEET: BOOT SEQUENCE

LAB OBJECTIVE NOTES SIGN OFF

BOOT Log onto a Sequoia system using a

SEQUENCE laptop.
Capture a boot sequence.
Evaluate the boot sequence.

Module 17-14 Sequoia Service Training Manual P/N 63326 Rev. 1