I know the time in
dmesg is the time since boot. But my specific question is this time is calculated at the start or end of the process mentioned in the line?
Why this is important?
take this example:
[ 4.352025] floppy0: no floppy controllers found [ 5.718270] random: nonblocking pool is initialized [ 94.134265] Adding 2094076k swap on /dev/sda5. Priority:-1 extents:1 across:2094076k FS** [ 96.988453] init: bootchart main process (274) terminated with status 127
If the time, is calculated after finishing the process, the process in the 3rd line should be taken responsible for slow boot.
But if time is calculated from the beginning of the process, the 2nd line should be taken responsible for it.
But it become more complicated when we check
dmesg long after boot.
Take this for example:
[28047.749604] wlp3s0: associated [28941.112855] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=757985 end=757986) [31407.938694] cfg80211: World regulatory domain updated: [31407.938699] cfg80211: DFS Master region: unset
This 2466s gap shouldn't have any useful meaning.
I see many times there is confusion about which line in
dmesg should be hold responsible for a slow boot.
How can we make sense of time in dmesg?