Nokia

Printouts of Starting phases in

Linux Units
DN0965958
Issue 3-0
 Printouts of Starting phases in Linux Units

The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.

Copyright © 2016 Nokia. All rights reserved.

f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.

2 © 2016 Nokia DN0965958 Issue: 3-0

Printouts of Starting phases in Linux Units

Table of Contents
This document has 12 pages

Summary of changes..................................................................... 4

1 Starting phases in Linux units........................................................ 5

1.1 Example of starting phases............................................................6

DN0965958 Issue: 3-0 © 2016 Nokia 3

Summary of changes Printouts of Starting phases in Linux Units

Summary of changes
Changes made between issues 3-0 and 2-0
Editorial changes.
Changes made between issues 2-0 and 1-0
The title of the document has been changed from Boot Phases in Linux units to Printouts
of Starting phases in Linux units.
LCP platform software in figure has been changed to LinDX platform software.
Information regarding starting of kernel and four starting phases have been updated.
Section Example of starting phases of the CPPU unit has been changed to Example of
starting phases.
Reference to the CPPU unit in section Example of starting phases has been removed.
From line LINUX VERSION until line... and After the Linux Kernel began to boot... has
been removed from LINUX KERNEL description.
Lines RENAMED ETH2 TO EMB0 and RENAMED ETH3 TO EMB1 are printed... and
Lines RENAMED ETH2 TO EMB0 and RENAMED ETH3 to EMB1 indicate... have been
removed from PLATFORM PROGRAMS description.
Changes made in issue 1-0
This is the first issue.

4 © 2016 Nokia DN0965958 Issue: 3-0

Printouts of Starting phases in Linux Units Starting phases in Linux units

1 Starting phases in Linux units

The following figure presents the starting phases of Linux units.

BOLERO

Start

DMXRTE LNINST

run
Start
diagnostics

Diagnostics Linuxkernel

Extractsoftware
modules

Lnx-launcher-d

Start

LinDXplatform
software

1. The boot loader, BOLERO, initializes the hardware after a system restart, and loads
and starts the operating system.
2. The boot includes initializing the hardware (CPU hardware and memory system)
determining the unit type, loading a load list based on the unit type, loading software
modules based on the load list, and starting the DMX runtime, DMXRTE.
3. DMXRTE checks if the Linux installer, LNINST, is loaded during the boot. In Linux
units, the execution is then transferred to LNINST. If LNINST determines that
diagnostics should be run, the execution returns to DMXRTE and diagnostics is
executed. Otherwise LNINST starts the Linux kernel.
4. When the kernel has been started and platform load modules have been extracted
from load chain to the RAM disk, the platform start-up service Lnx-launcher-d begins
to start the platform programs. Lnx-launcher-d starts all programs that belong to
Linux Computing Platform (LinDX), but it can also start other application programs
that are not related to the platform.

Four starting phases are defined:

L0 LinDX programs: System startup, Post office, Recovery

L1 LinDX programs requiring DMX messaging services

L2 and L3 application software

DN0965958 Issue: 3-0 © 2016 Nokia 5

Starting phases in Linux units Printouts of Starting phases in Linux Units

g Note: DMX messaging is not available before Post office is running in phase L0.
Process supervision is not available before phase L1.

1.1 Example of starting phases

The following printout example shows the starting phases until the end of phase L1. The
printout of phases L2 and L3 depend on which applications are started in them.
AMIBIOS(C) American Megatrends, Inc.
KONTRON AT8050/FYA BIOS Version 3.12

(C) American Megatrends, Inc.

64-3047-009999-00101111-102810-TYLSBURG-FYA_V312-Y2KC

Physical Processors Package: 1

Active Processors Cores: 4
Logical Processors: 8
Intel HT Technology: Enabled
QPI Speed: 5.866GT
CPU : Intel(R) Xeon)R) CPU :5518 @ 2.13GHz
Speed : 2.13 GHz

Reset type: Cold Reset

Currently Running on Primary BIOS.
Modified CMOS setup is used.

Press DEL to run Setup (F4 on Remote Keyboard)

Press F12 if you want to boot from the network
Press F11 for BBS POPUP (F3 on Remote Keyboard)
Initializing USB Controllers .. Done.

Memory Channel 0 DIMM 0 Size 1024MB

Memory Channel 0 DIMM 1 Size Not Installed
Memory Channel 1 DIMM 0 Size 1024MB
Memory Channel 1 DIMM 1 Size Not Installed
Memory Channel 2 DIMM 0 Size 1024MB
Memory Channel 2 DIMM 1 Size Not Installed
DDR3: 3072MB OK, Speed: 1066MHz

Auto-detecting USB Mass Storage Devices ..

00 USB mass storage devices found and configured.

Initializing Intel(R) Boot Agent GE v1.3.38

PXE 2.1 Build 088 (WfM 2.0)

Initializing Intel(R) Boot Agent GE v1.3.38

PXE 2.1 Build 088 (WfM 2.0

IPMC Responding
Checking NVRAM..

Intel(R) Boot Agent GE v1.3.38

Copyright (C) 1997-2009, Intel Corporation

6 © 2016 Nokia DN0965958 Issue: 3-0

Printouts of Starting phases in Linux Units Starting phases in Linux units

Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 088 LAL_ABF)
Copyright (C) 1997-2009, Intel Corporation

CLIENT MAC ADDR: 00 A0 64 0c 12 GUID: 01410100 0C00 0C01 b300FFFFFFFF

CLIENT IP: 10.200.200.32 MASK: 255.255.255.0 DHCP IP: 10.200.200.1
GATEWAY IP: 10.200.200.1
TFTP./

DMX SYSTEM START-UP TESTS

SELF TEST RESULT: 0, CPU RESET STATUS: 0000, PROCESSOR ID & REV: 106A5

COM1 initialized to 38400 baud, 8 bits, no parity, 1 stop bit(s)

COM2 initialized to 38400 baud, 8 bits, no parity, 1 stop bit(s)

Host bridge dev id = 3406

CPU PIU TYPE: ACPI4-A, VENDOR: K, NO DMX-FPGA
SYSTEM RAM OK

MULTIPROCESSOR SYSTEM DETECTED

PCI 2.x FOUND

SCANNING PCI BRIDGES

BUS 0 DEV 3 FUNC 0 TO BUSES 8-8
BUS 0 DEV 4 FUNC 0 TO BUSES 9-9
BUS 0 DEV 5 FUNC 0 TO BUSES 4-5
BUS 0 DEV 7 FUNC 0 TO BUSES B-B
BUS 0 DEV 8 FUNC 0 TO BUSES A-A
BUS 0 DEV 9 FUNC 0 TO BUSES 6-7
BUS 0 DEV A FUNC 0 TO BUSES 2-3
BUS 0 DEV 1E FUNC 0 TO BUSES 1-1
Highest bus number B

CONFIGURING PCI DEVICES

BUS 0 DEV 0 FUN 0
BUS 0 DEV 14 FUN 0
BUS 0 DEV 14 FUN 1
BUS 0 DEV 14 FUN 2
BUS 0 DEV 14 FUN 3
BUS 0 DEV 16 FUN 0
BUS 0 DEV 16 FUN 1
BUS 0 DEV 16 FUN 2
BUS 0 DEV 16 FUN 3
BUS 0 DEV 16 FUN 4
BUS 0 DEV 16 FUN 5
BUS 0 DEV 16 FUN 6
BUS 0 DEV 16 FUN 7
BUS 0 DEV 1d FUN 0
BUS 0 DEV 1d FUN 1
BUS 0 DEV 1d FUN 2
BUS 0 DEV 1d FUN 7
BUS 0 DEV 1f FUN 0
BUS 0 DEV 1f FUN 2
BUS 0 DEV 1f FUN 3
BUS 2 DEV 0 FUN 0
BUS 2 DEV 0 FUN 1
BUS 4 DEV 0 FUN 0

DN0965958 Issue: 3-0 © 2016 Nokia 7

Starting phases in Linux units Printouts of Starting phases in Linux Units

BUS 4 DEV 0 FUN 1

BUS 6 DEV 0 FUN 0
BUS 6 DEV 0 FUN 1
PCI DEVICE MAP RECTIFIED
UNIT ADDRESS SET FROM IPMI: 0082
EMB-0: link came up: 1000 Mbit/s, full duplex, full flow control.
EMB-1: link came up: 1000 Mbit/s, full duplex, full flow control.
BOLEROGX.PAC 33.53-0 11/02/16 PLAENVY1.PAC 2.7.0
DRAM SIZE = 3064 MEGABYTES (BF7B0000H BYTES)
RESET TYPE = COLD, RESET CAUSE = 00
RAM OK

BLACKBOX FORMING SKIPPED

UNIT = 0083
EMB-0 AT ETH PORT 02: LINK OK, 1000 Mbit/S
EMB-1 AT ETH PORT 03: LINK OK, 1000 Mbit/S
REGISTRATION TO COMPUTER 0000 OK
LOADING NET CONFIGURATION FROM COMPUTER 0000
NET CONFIGURATION LOADED
EMB SELECTED AS MEDIA BASED ON NET CONFIGURATION
PACKET: Y1 2.7-0
LOADING LOADLIST BOOLISC5.IMG FROM COMPUTER 0000
LOAD LIST LOADED
MODULE LOADING STARTS
LOADING MODULES FROM COMPUTER 0000
NEW LOADING SOURCE GIVEN WITH WAIT TIME
LOADING MODULES FROM COMPUTER 0084
DMX LIB PAG RAU BSP EPC FLL FSY KDD KDD KPA LGR LMG MEF NEC PO3 PO5 PO
D PXP QWE THP UNF APP ASY DEB CLU BUE BOM BBO BJO BOS BOX C1R CAT CEP CPF
CPU CSO DAE DBU DPA DGX DIK DOC DME DUF DUM DUZ EBS DYT EFI EHF EIO ENA
EOP ETH FAM FEM FIZ FIS FIR FLM FMN FUT FUN FUZ GIV HAP HRL HWO HWI IE1 I
LI IIM IKE INV IPB IPD ISR JAG JAP JAS JUP KGP LG4 LSE LOG LNI LMX LN1
LN1 LN1 LN1 LN1 LN1 LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX
LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX L
NX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LN
X LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX LNX
LNX LNX LNX LNX LNX LNX LNX LNX OCE OSI PBL PBH PBM PFM PGE PLU PMT P
ON POM POZ POX PRS PRT QMD RCA RCB RCK RCP RE7 REQ RME RIE RIO SAV RYS SE
K STK ST6 SUP SUY SYF SYS SYK TOP THE TIS TLX TLY TUT UBS USA WEE WYN WUP
XML XIP ZSK YAN YLE ZLI DXP
ALL MODULES LOADED

DEBUG MODE = 00000000

BOLERO RUN TIME: 00:40

LOADING TIME: 00:37

STARTING OS ...

DMX STARTING UP
- Initializing statical dmxrte data areas
- Reading DMX configuration file
- Initializing oslog
- Initializing exception handler TSS’s
- Setting up GDT entries
- Setting up LDT entries
Starting standalone OS

8 © 2016 Nokia DN0965958 Issue: 3-0

Printouts of Starting phases in Linux Units Starting phases in Linux units

Relocating data to 00008000

Install desc 80002076 00409200 @ 33c8
LNINST starting ... ok!
Identifying architecture ... PIU type 0x1B3, BSP id 04, arch id 2
BOLERO E820[0]: 0000000000000000+000000000009b800 type=1
BOLERO E820[1]: 000000000009b800+0000000000004800 type=2
BOLERO E820[2]: 00000000000e4000+000000000001c000 type=2
BOLERO E820[3]: 0000000000100000+00000000bf6b0000 type=1
BOLERO E820[4]: 00000000bf7b0000+000000000000e000 type=3
BOLERO E820[5]: 00000000bf7be000+0000000000012000 type=4
BOLERO E820[6]: 00000000bf7d0000+0000000000010000 type=2
BOLERO E820[7]: 00000000bf7ed000+0000000000013000 type=2
BOLERO E820[8]: 00000000bf800000+0000000000800000 type=2
BOLERO E820[9]: 00000000e0000000+0000000010000000 type=2
BOLERO E820[10]: 00000000fee00000+0000000000001000 type=2
BOLERO E820[11]: 00000000ffb00000+0000000000500000 type=2
Searching for VLX ELF image ... not found
Searching for ELF image ... found at 0008:bc8b36ac
WARNING: ELF image overlaps DMX allocated memory
WARNING: [0x2000000, 0x2666d4b] not in [0x57d3118, 0xbb4bf7c8[
copying section from 0008:bcab36ac to 0008:02000000 (size=494000)
copying section from 0008:bcf476ac to 0008:02494000 (size=795b0)
copying section from 0008:bd0b36ac to 0008:0250e000 (size=888)
copying section from 0008:bd2b36ac to 0008:0250f000 (size=13b84)
copying section from 0008:bd3d623c to 0008:02522b90 (size=5a470)
install descr 8100ffff 00009b00 @ 33b0
install descr 2720ffff 004e9b1c @ 33b8
install descr 0000ffff 00cf9a00 @ 0010
install descr 0000ffff 00cf9200 @ 0018
install descr 0000ffff 00af9a00 @ 0030
install descr 0000ffff 00af9200 @ 0038
Image installed
E820[0](8df0): 0000000000000000+0000000000010000 type=2
E820[1](8e04): 0000000000010000+0000000000080000 type=1
E820[2](8e18): 0000000000090000+0000000000010000 type=2
E820[3](8e2c): 00000000000a0000+0000000000060000 type=2
E820[4](8e40): 0000000000100000+0000000003f00000 type=1
E820[5](8e54): 0000000004000000+0000000000200000 type=2
E820[6](8e68): 0000000004200000+00000000b72bf000 type=1
E820[7](8e7c): 00000000bb4bf000+00000000042f1000 type=2
E820[8](8e90): 00000000bf7b0000+000000000000e000 type=3
E820[9](8ea4): 00000000bf7be000+0000000000012000 type=4
E820[10](8eb8): 00000000bf7d0000+0000000000010000 type=2
E820[11](8ecc): 00000000bf7ed000+0000000000013000 type=2
E820[12](8ee0): 00000000bf800000+0000000000800000 type=2
E820[13](8ef4): 00000000e0000000+0000000010000000 type=2
E820[14](8f08): 00000000fee00000+0000000000001000 type=2
E820[15](8f1c): 00000000ffb00000+0000000000500000 type=2
Searching for parameters ... found at 0008:bc8b3508
Searching for initial ramdisk ... found at 0008:bbec8dc0
Moving to 0008:37fb4000 (306294 bytes)
BOLERO: I/O Base set to 0x0
Starting the image! calling 0x02000000(0x00008b20 sz=1360 33c8:00000b20)
Primary chain start at 0x04008908
Looking for LNX%%%.2 and LN%%%%04
Looking for modules
Extracting module LNX92CG2 at bbf5bb98

DN0965958 Issue: 3-0 © 2016 Nokia 9

Starting phases in Linux units Printouts of Starting phases in Linux Units

Extracting module LNX929G2 at bbf616e4

Extracting module LNX928G2 at bbf8965c
Extracting module LNX921G2 at bc3b90cc
Extracting module LNX90BG2 at bc3c8680
Extracting module LNX90AG2 at bc3cb180
Extracting module LNX71BG2 at bc3dbaa4
Extracting module LNX71AG2 at bc3e2dec
Extracting module LNX718G2 at bc3f5fc4
Extracting module LNX716G2 at bc3f7fc8
Extracting module LNX715G2 at bc41d0a4
Extracting module LNX714G2 at bc43c3c8
Extracting module LNX712G2 at bc4597b0
Extracting module LNX710G2 at bc4627d8
Extracting module LNX70FG2 at bc471200
Extracting module LNX70EG2 at bc4748ac
Extracting module LNX70DG2 at bc483c38
Extracting module LNX70CG2 at bc48b30c
Extracting module LNX70BG2 at bc496de4
Extracting module LNX70AG2 at bc4b3b08
Extracting module LNX709G2 at bc4cf1bc
Extracting module LNX708G2 at bc515d80
Extracting module LNX707G2 at bc51cc50
Extracting module LNX706G2 at bc58a000
Extracting module LNX705G2 at bc58f344
Extracting module LNX704G2 at bc5d5148
Extracting module LNX703G2 at bc5dc704
Extracting module LNX702G2 at bc5e6f54
Extracting module LNX701G2 at bc83b0d4
Extracting module LNX6FFG2 at bc84b3fc
Extracting module LNX6F8G2 at bc882ce8
31 modules extracted
Looking for modules
Extracting module LN171C04 at bd88fcdc
1 modules extracted
Executing 2nd stage init
Populating /dev
Updating ld.so.cache
Reading time from hardware clock
Startup phase: L0
Starting family 'lnx-log-syslog-d'
Starting family 'lnx-setup'
Starting family 'lnx-log-klog-d'
hwapi_ipmi_get_emb_address
Sending message: 00
Got ack: 00,00,48,90,FF,00,0C,00
Sending message: 0A,40,00,2A,6F,00,07,00,1D,02
Got ack: 00,0A,40,00,02,00,83
Running in: ACPI4A (KONTRON)
Sending message: 04,01,00,00,64,00
Got ack: 00
Press return to login...
Creating bridges...
Family 'lnx-setup' finished
Starting family 'lnx-dmxmsg-epo-d'
Starting family 'lnx-rsterm-d-bf'
Starting family 'lnx-rsterm-d-be'
Starting family 'lnx-dmxrtemu-d'

10 © 2016 Nokia DN0965958 Issue: 3-0

Printouts of Starting phases in Linux Units Starting phases in Linux units

sh: cannot create /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:

Directory nonexistent
Starting family 'lnx-fu-fuzzi-d'
Starting family 'lnx-unabom-d'
Starting family 'lnx-dxfile-femser-d'
Starting family 'lnx-dxfile-rmemfs-d'
Starting family 'lnx-fu-rcy-d'
Initial unit state: WO-RE(1)
File loading activated
Loading SCDFLE successfully
Loading UNFILE successfully
Loading NECONF successfully
Starting family 'lnx-lieser-d'
Starting family 'lnx-lalarm-d'
Starting family 'lnx-dxfile-loader'
Starting to load group 1000
Load from unit 4C02 (source 2, disk FF)
Loading file 'DXS' from 0000
lnx-dxfile-loader: File loading finished.
Family 'lnx-dxfile-loader' finished
Startup phase: L1
Starting family 'lnx-sysmon-d'
Starting family 'lnx-dmxmsg-distmon-d'
Starting family 'lnx-dxerr-load'
Starting family 'lnx-dxfile-iomana-d'
Starting family 'lnx-ipconf-d'
Family 'lnx-dxerr-load' finished
Starting family 'lnx-log-sender-d'
Starting family 'lnx-ns-d'
Starting family 'lnx-swlist-d'
Starting family 'lnx-csagent-d'
Starting family 'lnx-ethmana-d'
Starting family 'lnx-dxdiag-d'
Starting family 'lnx-sysmon-diq-d'
Starting family 'lnx-sysmon-cpupro-d'
Starting family 'lnx-sysmon-lmp-d'
Starting family 'lnx-sysmon-lrm-d'
********** SYSTEM READY **********

Read the following description to better understand the meaning of printouts during the
starting phases in Linux units:

• LNINST
The Starting standalone OS line indicates the point where Linux installer
(LNINST) is started, and the Starting the image! line indicates the point
where it ends.
• LINUX KERNEL
If an error occurs during this phase, specific error messages or alarms cannot be
given but some extra lines are shown in the printout, which might help you identify
the cause of the problem. Errors occurring in this phase are related either to
hardware or to the software configuration, and are very rare.
• PLATFORM PROGRAMS
In the beginning of starting phase L0, the message bus is not available yet.
Therefore, if errors occur at this point, alarms cannot be given.

DN0965958 Issue: 3-0 © 2016 Nokia 11

Starting phases in Linux units Printouts of Starting phases in Linux Units

The File loading activated line is printed out by the recovery program. If
abnormal lines are printed out at this point, it might indicate that the recovery system
is not able to initialize.

12 © 2016 Nokia DN0965958 Issue: 3-0