Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 329 subscribers
  • Views 475 views
  • Users 0 members are here
Related

microzed running pulsar linux stalls on boot up, UTMP

Former Member

We are running pulsar linux on our microzed processor and having very long boot up times.  The boot process stalls on 

"started Update UTMP about System Runlevel Changes"

Has anyone else run into this?  Does anyone know a solution to this?

 

Here is what we see on boot up:

          Starting Network Service...

         Starting Login Service...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Change the tty3 to be the active vt.
[  OK  ] Started Ethernet Bridge Filtering Tables.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Login Service.
[     *] (2 of 2) A start job is running for Network Service (34s / 1min 53s)gre▒ GRE over IPv4 demultiplexor driver
[  OK  ] Started Open vSwitch Internal Unit.
[  OK  ] Started Network Service.
device eth0 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready
         Starting Network Name Resolution...
br0: port 1(eth0) entered forwarding state
br0: port 1(eth0) entered forwarding state
[  OK  ] Reached target Network.r0: link becomes ready
         Starting Open vSwitch...
         Starting Xinetd A Powerful Replacement For Inetd...
         Starting Setup dnsmasq...
[  OK  ] Started Setup dnsmasq.
         Starting LXC Container Initialization and Autoboot Code...
         Starting /etc/rc.local Compatibility...
[  OK  ] Started Network Name Resolution.
[  OK  ] Started Open vSwitch.
[  OK  ] Started Xinetd A Powerful Replacement For Inetd.
[  OK  ] Started /etc/rc.local Compatibility.
         Starting Getty on tty1...
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LXC Container Initialization and Autoboot Code.
[  OK  ] Reached target Multi-User System.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
 
Pulsar Linux 7.0.0.11 cube-21-03-16-cube-server ttyPS0
 
 
 
Parents
  • 0

    Hi Matt,

    Just because the Pulsar-7 boot stalls at "Started Update UTMP about System Runlevel Changes" doesn't necessarily indicate that is the issue.  That is just the last line of status message that is printed before the kernel continues with other boot tasks.  I spoke to an engineer at Wind River and their suggestion is to install and run the systemd-analyze application to get an idea of where the system is spending its time during boot.  Here are some instructions for downloading, installing, and running the application to generate graphs that can be used analyze the time spent at each boot step:

    # Log in as root and run the following commands
cube-console dom0
cube-console essential
smart update > /dev/null
smart download systemd-analyze
mv systemd*.rpm  /var/lib/lxc/cube-server/rootfs/root
rpm -ihv /var/lib/lxc/cube-server/rootfs/root/systemd-analyze*.rpm
lxc-attach -n dom0 -- rpm -ihv /var/lib/lxc/cube-server/rootfs/root/systemd-analyze*.rpm
lxc-attach -n cube-server -- rpm -ihv /root/systemd-analyze*.rpm


systemd-analyze plot > /var/lib/lxc/cube-server/rootfs/root/1.svg
lxc-attach -n dom0 -- systemd-analyze plot > /var/lib/lxc/cube-server/rootfs/root/2.svg
lxc-attach -n cube-server -- systemd-analyze plot > /var/lib/lxc/cube-server/rootfs/root/3.svg
cat<<EOF>/var/lib/lxc/cube-server/rootfs/root/0.html
<img src=1.svg>
<br>
<img src=2.svg>
<br>
<img src=3.svg>
EOF
exit
exit


# Now copy off the data how every you choose.
scp *.html *.svg YOUR_SERVER:/YOUR_DIR

# Now that you have the files on a different machine use Chrome on the 0.html file

google-chrome 0.html

# You will see a full graph of where all the time was spent in the boot process

    For example, here are a couple of example graphs created for Pulsar-7 and Pulsar-8 running on a MicroZed-7010.

    Pulsar-7: http://htmlpreview.github.io/?https://github.com/jwessel/scratch/blob/master/MZ/pulsar-7-7010-boot/0.html

    Pulsar-8: http://htmlpreview.github.io/?https://github.com/jwessel/scratch/blob/master/MZ/pulsar-8-7010-boot/0.html

    It is recommended, if you can, to use Pulsar-8 instead.  Wind River has made some significant improvements to system start in Pulsar-8, and it also prints out much more information about what is going on.

    I hope this helps.

    --Tom

Reply
  • 0

    Hi Matt,

    Just because the Pulsar-7 boot stalls at "Started Update UTMP about System Runlevel Changes" doesn't necessarily indicate that is the issue.  That is just the last line of status message that is printed before the kernel continues with other boot tasks.  I spoke to an engineer at Wind River and their suggestion is to install and run the systemd-analyze application to get an idea of where the system is spending its time during boot.  Here are some instructions for downloading, installing, and running the application to generate graphs that can be used analyze the time spent at each boot step:

    # Log in as root and run the following commands
cube-console dom0
cube-console essential
smart update > /dev/null
smart download systemd-analyze
mv systemd*.rpm  /var/lib/lxc/cube-server/rootfs/root
rpm -ihv /var/lib/lxc/cube-server/rootfs/root/systemd-analyze*.rpm
lxc-attach -n dom0 -- rpm -ihv /var/lib/lxc/cube-server/rootfs/root/systemd-analyze*.rpm
lxc-attach -n cube-server -- rpm -ihv /root/systemd-analyze*.rpm


systemd-analyze plot > /var/lib/lxc/cube-server/rootfs/root/1.svg
lxc-attach -n dom0 -- systemd-analyze plot > /var/lib/lxc/cube-server/rootfs/root/2.svg
lxc-attach -n cube-server -- systemd-analyze plot > /var/lib/lxc/cube-server/rootfs/root/3.svg
cat<<EOF>/var/lib/lxc/cube-server/rootfs/root/0.html
<img src=1.svg>
<br>
<img src=2.svg>
<br>
<img src=3.svg>
EOF
exit
exit


# Now copy off the data how every you choose.
scp *.html *.svg YOUR_SERVER:/YOUR_DIR

# Now that you have the files on a different machine use Chrome on the 0.html file

google-chrome 0.html

# You will see a full graph of where all the time was spent in the boot process

    For example, here are a couple of example graphs created for Pulsar-7 and Pulsar-8 running on a MicroZed-7010.

    Pulsar-7: http://htmlpreview.github.io/?https://github.com/jwessel/scratch/blob/master/MZ/pulsar-7-7010-boot/0.html

    Pulsar-8: http://htmlpreview.github.io/?https://github.com/jwessel/scratch/blob/master/MZ/pulsar-8-7010-boot/0.html

    It is recommended, if you can, to use Pulsar-8 instead.  Wind River has made some significant improvements to system start in Pulsar-8, and it also prints out much more information about what is going on.

    I hope this helps.

    --Tom

Children
No Data