From: Borislav Petkov <bp@alien8.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: INFO: task systemd-udevd:94 blocked for more than 120 seconds.
Date: Fri, 23 Sep 2022 21:42:46 +0200 [thread overview]
Message-ID: <Yy4MNp6yiRTJxeXa@zn.tnic> (raw)
In-Reply-To: <Yy4GoMMwiBaq3oJf@dev-arch.thelio-3990X>
On Fri, Sep 23, 2022 at 12:18:56PM -0700, Nathan Chancellor wrote:
> I have not seen a stacktrace like this on my machines (although I
> suspect that is because I don't have CONFIG_DETECT_HUNG_TASK enabled in
> my configs) but my Honeycomb LX2 hangs while booting after commit
> 78ffa3e58d93 ("thermal/core: Add a generic thermal_zone_get_trip()
> function") according to my bisect, which certainly seems like it could
> be related to the trace you are seeing.
Don't you just love how well our community works - one reports a bug and
someone else has already bisected it and thus saves one the work?!
:-)))
Thanks Nathan, I can confirm your bisection. The commit above doesn't
revert cleanly ontop of linux-next so I tried it and the patch before
it:
78ffa3e58d93 ("thermal/core: Add a generic thermal_zone_get_trip() function") <- BAD
62022c15f627 ("Merge branch 'pm-opp' into linux-next") <- GOOD
so it looks like that one is somehow b0rked.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-09-23 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 18:59 INFO: task systemd-udevd:94 blocked for more than 120 seconds Borislav Petkov
2022-09-23 19:18 ` Nathan Chancellor
2022-09-23 19:42 ` Borislav Petkov [this message]
2022-09-24 7:40 ` Hugh Dickins
2022-09-24 8:16 ` Daniel Lezcano
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=Yy4MNp6yiRTJxeXa@zn.tnic \
--to=bp@alien8.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=rafael@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox