With the first one, I got no idea what is going on. My filesystem is being remounted?The second one seems to be the Bluetooth hogging time. Haven't managed to find any info on how to disable this. Don't really use bluetooth on my laptop, so can manually activate it when I need it.

"With the first one, I got no idea what is going on. My filesystem is being remounted?" It looks like Linux found something that needed read-only access to the OS file system, which it fixed, then remounted it read-write. Ten seconds is about right for a fsck when there's nothing seriously wrong, just a not-marked-as-empty journal after the last shutdown is my guess.

Strange women lying in ponds distributing swords is no basis for a system of government.

Mute Ant wrote:"With the first one, I got no idea what is going on. My filesystem is being remounted?" It looks like Linux found something that needed read-only access to the OS file system, which it fixed, then remounted it read-write. Ten seconds is about right for a fsck when there's nothing seriously wrong, just a not-marked-as-empty journal after the last shutdown is my guess.

My gap is actually before, so is it the driver being loaded that hangs? I.e is the log written at begining of action or after action?I have a quad core i7 (i7-4702MQ @ 2.2GHz) and 8GB ram, but regular HDD. This is why I am concerned about my almost 1 minute long boot time.

LnX wrote:My gap is actually before, so is it the driver being loaded that hangs? I.e is the log written at begining of action or after action?

It says re-mountED so in this case and in theory, after. Not sure you should place complete faith in the remount being fully synchronous anyway though (i.e., necessary completed before the message appears in the kernel message buffer).

I expected the HDD to be enough explanation but must say I just booted up an old P4 which is still using an HDD and only find a 4 second pause shortly after the root remount (it's running Debian 9). So, frankly, "dunno". It won't be the ppdev driver if that's the driver you were referring to. Your later pause I expect to related to IPv6 rather than Bluetooth. Is this Mint 18.x? If so, systemd-analyze blame could be semi-useful for the userspace part at least.

"Semi" since I do wonder a bit why you're concerned. 1 minute is faster than what I used to have on my (first gen) Core i7 2.8GHz, 8GiB when it was still running on HDD; a spiffy WD Black one, even. It seems you have little to be concerned about, certainly after disabling IPv6 if you don't use it. In your router would be most effective, alternatively supposedly see "the right fix" subheader at https://www.techrepublic.com/article/how-to-fix-the-slow-apt-get-update-issue-on-linux-machines/.

LnX wrote:My gap is actually before, so is it the driver being loaded that hangs? I.e is the log written at begining of action or after action?

It says re-mountED so in this case and in theory, after. Not sure you should place complete faith in the remount being fully synchronous anyway though (i.e., necessary completed before the message appears in the kernel message buffer).

I expected the HDD to be enough explanation but must say I just booted up an old P4 which is still using an HDD and only find a 4 second pause shortly after the root remount (it's running Debian 9). So, frankly, "dunno". It won't be the ppdev driver if that's the driver you were referring to. Your later pause I expect to related to IPv6 rather than Bluetooth. Is this Mint 18.x? If so, systemd-analyze blame could be semi-useful for the userspace part at least.

"Semi" since I do wonder a bit why you're concerned. 1 minute is faster than what I used to have on my (first gen) Core i7 2.8GHz, 8GiB when it was still running on HDD; a spiffy WD Black one, even. It seems you have little to be concerned about, certainly after disabling IPv6 if you don't use it. In your router would be most effective, alternatively supposedly see "the right fix" subheader at https://www.techrepublic.com/article/how-to-fix-the-slow-apt-get-update-issue-on-linux-machines/.

Turned off IPv6 according to you link, but it is still active it seems. I am on a school network most of the time with the laptop, so I can't really turn off IPv6 on the router.