System boots slowly

[dundir]

After updating to the latest kernel (5.3 general/lowlatency) my W510 Thinkpad is taking forever to load gdm3. After some reading I installed haveged as some issues indicated this as a possible fix. No dice, still have the issue, no improvement.

On average it takes about 40 seconds to a minute between plymouth switching and the mouse cursor being drawn, about a minute and a half to two minutes for the greeter to launch. I've disabled Wayland which seems to speed up the latter process slightly but its barely noticeable.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-05-24 (294 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Package: gdm3 3.28.3-0ubuntu18.04.4
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-lowlatency 5.3.18
Tags: bionic
Uname: Linux 5.3.0-40-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
mtime.conffile..etc.gdm3.custom.conf: 2020-03-13T17:07:44.727975

[dundir (dundir)]

apport information

[dundir (dundir)]

apport information

[dundir (dundir)]

apport information

[dundir (dundir)]

apport information

[Daniel van Vugt (vanvugt)]

Please reboot again and then run this command to collect a fresh log of a slow boot:

  dmesg > dmesg.txt

And then attach the resulting file 'dmesg.txt' here.

[Daniel van Vugt (vanvugt)]

Please also try some older kernels and tell us which, if any, are significantly faster:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

[dundir (dundir)]

I've attached the requested fresh dmesg.txt.

I'll be reverting the kernel to see if anything improves and will post back with the details.

As a side note, and its probably not related, I'm also seeing sporadic temporary lockups which seem to correspond with the CE: hpet3 warning in dmesg but even when disabling hpet at grub the lockups still occur but as I mentioned; probably not related.

[dundir (dundir)]

I tested the kernels. Unfortunately none of them seemed to correct the
issue, 4.18-13 was a few seconds faster loading but not by much.
I updated the kernel at the same time as the software so its possible this
is related to one of the packages being updated.

I reverted back to my previous kernel (4.18.0-20) and see the exact same
issue so I'm thinking that it may not be the kernel. Though I find testing
that might be difficult since removing and reinstalling specific package
versions and getting their dependencies right can be problematic.

I also tested 4.15.0-88-lowlatency, 4.18.0-13-lowlatency, and the issue
persists.

On Sat, Mar 14, 2020 at 2:05 AM Daniel van Vugt <
<email address hidden>> wrote:

> Please also try some older kernels and tell us which, if any, are
> significantly faster:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867405
>
> Title:
> gdm3 loads very slowly with newer kernels
>
> Status in Ubuntu:
> Incomplete
>
> Bug description:
> After updating to the latest kernel (5.3 general/lowlatency) my W510
> Thinkpad is taking forever to load gdm3. After some reading I
> installed haveged as some issues indicated this as a possible fix. No
> dice, still have the issue, no improvement.
>
> On average it takes about 40 seconds to a minute between plymouth
> switching and the mouse cursor being drawn, about a minute and a half to
> two minutes for the greeter to launch. I've disabled Wayland which seems to
> speed up the latter process slightly but its barely noticeable.
> ---
> ProblemType: Bug
> ApportVersion: 2.20.9-0ubuntu7.11
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> InstallationDate: Installed on 2019-05-24 (294 days ago)
> InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
> Package: gdm3 3.28.3-0ubuntu18.04.4
> PackageArchitecture: amd64
> ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-lowlatency 5.3.18
> Tags: bionic
> Uname: Linux 5.3.0-40-lowlatency x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> mtime.conffile..etc.gdm3.custom.conf: 2020-03-13T17:07:44.727975
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1867405/+subscriptions
>

[Daniel van Vugt (vanvugt)]

Thanks for doing that so quickly.

I can't see any obvious problems in the attached kernel log but it is taking a minute or two to fully boot. It's also unclear if the login screen is appearing after all of that or part-way through.

To better answer this, please reboot again and then immediately run:

  journalctl -b0 > journal.txt

and then attach the file 'journal.txt'.

[dundir (dundir)]

Apologies for the delayed response, things have been pretty crazy.

I've attached the journal.txt you requested.

[Daniel van Vugt (vanvugt)]

Thanks. I can't see anything obviously wrong, just everything seems to be slow. I guess what's unusual in that log is the amount of networking, virtualization and docker stuff starting up on boot.

Next we really need a way to prove there is a definite bug in some package here. The current bug title "loads very slowly with newer kernels" is contradicted by your findings in previous comments that older kernels don't fix the problem. So I think the bug title is wrong and will change that...

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]

[Paul White (paulw2u)]

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

Further to comment #12 and with no additional comment after over three
years I'm closing this bug report as 'Invalid'.

Please feel free to report any issues that you might find with currently
supported releases of Ubuntu: https://wiki.ubuntu.com/Releases

[dundir (dundir)]

Paul,

I understand that need to close out old tickets, it is normally problematic
setting it to invalid as that category is typically reserved for issues
that were checked and confirmed as being invalid or out of scope.
It is however; EOL as you say. Closing tickets is completely
understandable for an EOL project, it might be better to create a new
category in light of reasons that follow.

You should be aware that many people are unable to log into launchpad to
report bugs or comment further, and this has been the case for at least two
years now, almost three. Initially anyone could report issues from their
email addresses.

External email addresses such as mine can no longer log in to launchpad,
this appears to be by design because no action has been taken in the
intervening years, and I've reached out to several people without response.

This also coincided with Canonical's push to have only canonical one
accounts. Even today, trying to log into the account I am emailing from
only allows me to proceed by signing up for a new canonical account and
supplying additional personal information again.

Put simply, I am not going to be doing that just to provide more free labor
in the form of testing, just to have that information monetized or leaked
from a poorly secured server. I previously reported many look and feel
issues with your desktop on hardware I owned, but I stopped when once your
launchpad was changed without notice.

Being unable to report bugs is one of the many reasons I and many of my
System Admin colleagues have stopped using Ubuntu as a production ready
platform. 18.04 LTS was the last viable version that met requirements, and
we've had to replace our systems in the interim and chosen to go another
direction. My background is as a Systems Engineer/Administrator, when I
found bugs I'd report them but overall rarely was any action taken so not a
lot of effort beyond the initial report was made to generate documentation.
This was provided for free.

As most people are unable to comment or even check open existing bugs that
may have been created and this was the case for at least the last 3 years,
even if they were valid at the time, its probably best if you just close
all the tickets from non-canonical email addresses if that is what you are
seeking to do as clean up.

Even now, I'm only able to respond to this because I received an email of
your recent action.

Best Regards,
N

On Wed, Jun 21, 2023 at 7:55 AM Paul White <email address hidden>
wrote:

> Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
>
> Further to comment #12 and with no additional comment after over three
> years I'm closing this bug report as 'Invalid'.
>
> Please feel free to report any issues that you might find with currently
> supported releases of Ubuntu: https://wiki.ubuntu.com/Releases
>
>
> ** Changed in: ubuntu
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867405
>
> Title:
> System boots slowly
>
> Status in Ubuntu:
> Invalid
>
> Bug description:
> After updating to the latest kernel (5.3 general/lowl...

[dundir (dundir)]

I should have added that Daniel was often the exception regarding action
taken and responses.

OAuth was once available to report bugs, it was changed without
notification to require signing up for Canonical accounts late 2020.
The change was at first sign-in was broken, just locking people out,
claiming an error, and then the page was changed to require only Canonical
accounts.

If you have any further questions feel free to contact me, but as I said I
have since moved on from your platform.

The bug reporting was just one of many major failures. There were quite a
number of really boneheaded decisions which were not possible to relay
since everyone was locked out; such as snap and the choice to corrupt the
package repository in a way that packages pose as software while instead
fixing up snap (without notification/prompt) after it had been disabled to
comply with written security policy.

Updating a firefox package from apt shouldn't cause audit alarm bells to go
off. Missed opportunities.

Regards,
N

On Mon, May 25, 2020 at 9:25 PM Launchpad Bug Tracker <
<email address hidden>> wrote:

> [Expired for Ubuntu because there has been no activity for 60 days.]
>
> ** Changed in: ubuntu
> Status: Incomplete => Expired
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1867405
>
> Title:
> System boots slowly
>
> Status in Ubuntu:
> Expired
>
> Bug description:
> After updating to the latest kernel (5.3 general/lowlatency) my W510
> Thinkpad is taking forever to load gdm3. After some reading I
> installed haveged as some issues indicated this as a possible fix. No
> dice, still have the issue, no improvement.
>
> On average it takes about 40 seconds to a minute between plymouth
> switching and the mouse cursor being drawn, about a minute and a half to
> two minutes for the greeter to launch. I've disabled Wayland which seems to
> speed up the latter process slightly but its barely noticeable.
> ---
> ProblemType: Bug
> ApportVersion: 2.20.9-0ubuntu7.11
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> InstallationDate: Installed on 2019-05-24 (294 days ago)
> InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
> Package: gdm3 3.28.3-0ubuntu18.04.4
> PackageArchitecture: amd64
> ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-lowlatency 5.3.18
> Tags: bionic
> Uname: Linux 5.3.0-40-lowlatency x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> mtime.conffile..etc.gdm3.custom.conf: 2020-03-13T17:07:44.727975
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1867405/+subscriptions
>