From: Greg KH <gregkh@linuxfoundation.org>
To: Alvaro Kuolas <kuolas@gmail.com>
Cc: regressions@lists.linux.dev
Subject: Re: Longer boot times with kernel 6.11.7 and newer (including 6.12.6).
Date: Fri, 27 Dec 2024 13:40:58 +0100 [thread overview]
Message-ID: <2024122716-previous-plethora-0ebb@gregkh> (raw)
In-Reply-To: <CAKUwrzA2ue3g3Ys=Vg=eeunE1mw-RSockLPoqnU=F6jB1jjVBw@mail.gmail.com>
On Fri, Dec 27, 2024 at 09:35:31AM -0300, Alvaro Kuolas wrote:
> "as expected" is what, faster boot?
>
> Sorry for my wording. I mean the system boots faster and it is more
> responsive without commit cfc72b86fa20cbf44d2b6cc27b35eb15080232ab.
>
> I noticed this problem on my system when logging in after a Fedora 41
> update. From GDM login screen to Gnome desktop running with the commit is
> roughly ~19sec and without it is ~5sec. This freeze on GDM login is why I
> started debugging.
>
> At first I reinstalled from the latest iso F41, then tried to block upower
> update, and later I tried different kernel versions. That is when I hit
> this commit.
>
> I have compiled 6.13-rc4 with commit
> cfc72b86fa20cbf44d2b6cc27b35eb15080232ab and without, I will start testing
> why this behaviour is on my machine and in other machines I have access to.
> I will try to look at why upower takes that much time, and why Gnome loses
> responsiveness, and check if it is only on my system (Ryzen 7900X, B650E,
> Vega10GL) or if it happens on other systems as well. I can change this
> testing to 6.12 stable if it is for the better.
>
> Thank you for your time and comments on this subject, I really appreciate
> it.
If you look at commit 15fffc6a5624 ("driver core: Fix uevent_show() vs
driver detach race"), it shows what the original fix was attempting to
resolve, by removing a lock on the path of reading the uevent sysfs
file.
It's odd that gnome wants to read that file so much, so perhaps you
should look into what is happening there. That file should ONLY be read
once at boot, during the "cold plug" portion of the boot process, and
not afterward as that wouldn't make much sense. Perhaps a speed up
could be just fixing userspace to not do that anymore.
good luck!
greg k-h
next prev parent reply other threads:[~2024-12-27 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 17:51 Longer boot times with kernel 6.11.7 and newer (including 6.12.6) Alvaro Kuolas
2024-12-26 21:33 ` Alvaro Kuolas
2024-12-27 8:01 ` Greg KH
2024-12-27 12:37 ` Alvaro Kuolas
[not found] ` <CAKUwrzA2ue3g3Ys=Vg=eeunE1mw-RSockLPoqnU=F6jB1jjVBw@mail.gmail.com>
2024-12-27 12:40 ` Greg KH [this message]
2024-12-27 15:28 ` Alvaro Kuolas
2024-12-27 7:58 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024122716-previous-plethora-0ebb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuolas@gmail.com \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.