<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX Processors中的主题 Between bootarg and systemd service</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Between-bootarg-and-systemd-service/m-p/884398#M134012</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on imx6solo + Orion Linux. I got some observation when setting boot argument.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i&amp;gt;&amp;nbsp;&lt;SPAN&gt;ii&amp;gt; bootarg with ip parameter&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if "&lt;STRONG&gt;setenv bootargs 'console=ttymxc0,115200&amp;nbsp; ip=dhcp&amp;nbsp; nosmp root=/dev/mmcblk2p1 rootwait&lt;/STRONG&gt;'"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;systemd-analyze blame&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;54.909s systemd-journald.service&lt;BR /&gt;48.501s dev-mmcblk0p1.device&lt;BR /&gt; 16.426s systemd-journal-flush.service&lt;BR /&gt; 10.382s udev-trigger.service&lt;BR /&gt; 9.470s systemd-tmpfiles-setup.service&lt;BR /&gt; 9.398s systemd-timesyncd.service&lt;BR /&gt; 8.495s systemd-udevd.service&lt;BR /&gt; 6.603s systemd-update-utmp.service&lt;BR /&gt; 3.911s systemd-logind.service&lt;BR /&gt; 3.527s remount-rfs-rw.service&lt;BR /&gt; 3.448s systemd-tmpfiles-setup-dev.service&lt;BR /&gt; 3.303s sys-fs-fuse-connections.mount&lt;BR /&gt; 3.139s systemd-sysctl.service&lt;BR /&gt; 2.358s systemd-remount-fs.service&lt;BR /&gt; 2.175s udev.service&lt;BR /&gt; 1.590s sys-kernel-debug.mount&lt;BR /&gt; 1.369s systemd-random-seed.service&lt;BR /&gt; 1.210s tmp.mount&lt;BR /&gt; 1.113s systemd-update-utmp-runlevel.service&lt;BR /&gt; 193ms systemd-networkd.service&lt;BR /&gt; 191ms systemd-resolved.service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ii&amp;gt; bootarg without ip parameter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if "&lt;STRONG&gt;setenv bootargs 'console=ttymxc0,115200 nosmp root=/dev/mmcblk2p1 rootwait&lt;/STRONG&gt;'"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;systemd-analyze blame&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;5.306s systemd-udev-trigger.service&lt;BR /&gt;5.293s dev-mmcblk0p1.device&lt;BR /&gt;3.332s systemd-journald.service&lt;BR /&gt;3.258s systemd-timesyncd.service&lt;BR /&gt;3.208s systemd-journal-flush.service&lt;BR /&gt;2.226s systemd-tmpfiles-setup.service&lt;BR /&gt;2.002s systemd-update-utmp.service&lt;BR /&gt;1.440s systemd-udevd.service&lt;BR /&gt;1.321s systemd-sysusers.service&lt;BR /&gt;1.065s udev-trigger.service&lt;BR /&gt;867ms sys-fs-fuse-connections.mount&lt;BR /&gt;864ms systemd-update-utmp-runlevel.service&lt;BR /&gt;769ms systemd-remount-fs.service&lt;BR /&gt;768ms sys-kernel-debug.mount&lt;BR /&gt;742ms systemd-sysctl.service&lt;BR /&gt;738ms remount-rfs-rw.service&lt;BR /&gt;708ms systemd-tmpfiles-setup-dev.service&lt;BR /&gt;641ms systemd-update-done.service&lt;BR /&gt;353ms udev.service&lt;BR /&gt;258ms systemd-journal-catalog-update.service&lt;BR /&gt;231ms ldconfig.service&lt;BR /&gt;117ms systemd-random-seed.service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be the reason ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;VinothS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 23 Feb 2019 10:35:46 GMT</pubDate>
    <dc:creator>vinothkumars</dc:creator>
    <dc:date>2019-02-23T10:35:46Z</dc:date>
    <item>
      <title>Between bootarg and systemd service</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Between-bootarg-and-systemd-service/m-p/884398#M134012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on imx6solo + Orion Linux. I got some observation when setting boot argument.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i&amp;gt;&amp;nbsp;&lt;SPAN&gt;ii&amp;gt; bootarg with ip parameter&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if "&lt;STRONG&gt;setenv bootargs 'console=ttymxc0,115200&amp;nbsp; ip=dhcp&amp;nbsp; nosmp root=/dev/mmcblk2p1 rootwait&lt;/STRONG&gt;'"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;systemd-analyze blame&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;54.909s systemd-journald.service&lt;BR /&gt;48.501s dev-mmcblk0p1.device&lt;BR /&gt; 16.426s systemd-journal-flush.service&lt;BR /&gt; 10.382s udev-trigger.service&lt;BR /&gt; 9.470s systemd-tmpfiles-setup.service&lt;BR /&gt; 9.398s systemd-timesyncd.service&lt;BR /&gt; 8.495s systemd-udevd.service&lt;BR /&gt; 6.603s systemd-update-utmp.service&lt;BR /&gt; 3.911s systemd-logind.service&lt;BR /&gt; 3.527s remount-rfs-rw.service&lt;BR /&gt; 3.448s systemd-tmpfiles-setup-dev.service&lt;BR /&gt; 3.303s sys-fs-fuse-connections.mount&lt;BR /&gt; 3.139s systemd-sysctl.service&lt;BR /&gt; 2.358s systemd-remount-fs.service&lt;BR /&gt; 2.175s udev.service&lt;BR /&gt; 1.590s sys-kernel-debug.mount&lt;BR /&gt; 1.369s systemd-random-seed.service&lt;BR /&gt; 1.210s tmp.mount&lt;BR /&gt; 1.113s systemd-update-utmp-runlevel.service&lt;BR /&gt; 193ms systemd-networkd.service&lt;BR /&gt; 191ms systemd-resolved.service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ii&amp;gt; bootarg without ip parameter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if "&lt;STRONG&gt;setenv bootargs 'console=ttymxc0,115200 nosmp root=/dev/mmcblk2p1 rootwait&lt;/STRONG&gt;'"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;systemd-analyze blame&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;5.306s systemd-udev-trigger.service&lt;BR /&gt;5.293s dev-mmcblk0p1.device&lt;BR /&gt;3.332s systemd-journald.service&lt;BR /&gt;3.258s systemd-timesyncd.service&lt;BR /&gt;3.208s systemd-journal-flush.service&lt;BR /&gt;2.226s systemd-tmpfiles-setup.service&lt;BR /&gt;2.002s systemd-update-utmp.service&lt;BR /&gt;1.440s systemd-udevd.service&lt;BR /&gt;1.321s systemd-sysusers.service&lt;BR /&gt;1.065s udev-trigger.service&lt;BR /&gt;867ms sys-fs-fuse-connections.mount&lt;BR /&gt;864ms systemd-update-utmp-runlevel.service&lt;BR /&gt;769ms systemd-remount-fs.service&lt;BR /&gt;768ms sys-kernel-debug.mount&lt;BR /&gt;742ms systemd-sysctl.service&lt;BR /&gt;738ms remount-rfs-rw.service&lt;BR /&gt;708ms systemd-tmpfiles-setup-dev.service&lt;BR /&gt;641ms systemd-update-done.service&lt;BR /&gt;353ms udev.service&lt;BR /&gt;258ms systemd-journal-catalog-update.service&lt;BR /&gt;231ms ldconfig.service&lt;BR /&gt;117ms systemd-random-seed.service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What could be the reason ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;VinothS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Feb 2019 10:35:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Between-bootarg-and-systemd-service/m-p/884398#M134012</guid>
      <dc:creator>vinothkumars</dc:creator>
      <dc:date>2019-02-23T10:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: Between bootarg and systemd service</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Between-bootarg-and-systemd-service/m-p/884399#M134013</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please note that "systemd-analyze blame" provides only an estimation.&lt;BR /&gt;Also please note that some services take a time but are not listed clearly in the log and their time may be noted as spent by some another service.&lt;BR /&gt;So you need to compare total boot time with and without networking.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2019 07:37:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Between-bootarg-and-systemd-service/m-p/884399#M134013</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2019-02-27T07:37:49Z</dc:date>
    </item>
  </channel>
</rss>

