Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: floppy on July 15, 2011, 01:32:46 PM

Title: What mean the last message in dmesg after boot? (PC connected to LAN)
Post by: floppy on July 15, 2011, 01:32:46 PM

Hello,

after boot of 2 different versions of mc 3.7.1 (on 2 different HDDs; having different boot codes; different extension numbers), I have

first dmesg
....
[    9.779804] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   16.440618] EXT4-fs (hdd3): warning: maximal mount count reached, running e2fsck is recommended
[   16.441108] EXT4-fs (hdd3): mounted filesystem with ordered data mode
[   16.561091] Adding 98272k swap on /dev/hdd2.  Priority:-1 extents:1 across:98272k
[   16.837903] EXT4-fs (hda2): warning: checktime reached, running e2fsck is recommended
[   16.838539] EXT4-fs (hda2): mounted filesystem with ordered data mode
[   17.023990] JBD: barrier-based sync failed on hda2-8 - disabling barriers
[   38.635141] JBD: barrier-based sync failed on hdd3-8 - disabling barriers
[   61.854282] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

second dmesg
....
[    9.843492] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   16.499395] EXT4-fs (hdd3): warning: maximal mount count reached, running e2fsck is recommended
[   16.499897] EXT4-fs (hdd3): mounted filesystem with ordered data mode
[   16.608709] Adding 98272k swap on /dev/hdd2.  Priority:-1 extents:1 across:98272k
[   17.540913] JBD: barrier-based sync failed on hdd3-8 - disabling barriers
[   83.900829] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

Question 1: squashfs runs before extension loading. correct?
Question 2: LAN connection is the last process starting (before apps are started, or script are started with bootlocal.sh).
                  correct? if not, at which stage the dhcp was started? http://wiki.tinycorelinux.net/wiki:the_boot_process
Question 3: for the first it takes 61,85s, the second 83,9s for the sytem screen to be activ (after Xvesa, jwm & wbar). Correct?
                  or this is a timing of a process which was started before (at which stage?) and which runs in parallel to others?

I try to understand a bit more regarding the timing data indicated in dmesg.

Title: Re: What mean the last message in dmesg after boot? (PC connected to LAN)
Post by: curaga on July 15, 2011, 02:35:58 PM

Quote

Question 1: squashfs runs before extension loading. correct?

Yes

Quote

Question 2: LAN connection is the last process starting (before apps are started, or script are started with bootlocal.sh).
                  correct? if not, at which stage the dhcp was started? http://wiki.tinycorelinux.net/wiki:the_boot_process

DHCP is started before bootsync.sh, but it is backgrounded.

Quote

Question 3: for the first it takes 61,85s, the second 83,9s for the sytem screen to be activ (after Xvesa, jwm & wbar). Correct?
                  or this is a timing of a process which was started before (at which stage?) and which runs in parallel to others?

Not correct. When the ethernet is up has no correlation to the rest of the system, it may be up before X or long after.


For proper measurements, you should use bootchart. Kernel timing messages aren't that useful for timing the other parts of the system.