From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Hugh Dickins <hughd@google.com>, Borislav Petkov <bp@alien8.de>
Cc: Nathan Chancellor <nathan@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: INFO: task systemd-udevd:94 blocked for more than 120 seconds.
Date: Sat, 24 Sep 2022 10:16:51 +0200 [thread overview]
Message-ID: <607cab94-ca0b-c7ea-b603-12d933e42ced@linaro.org> (raw)
In-Reply-To: <28d03f8d-ed70-cdc8-70d3-7b1723e5715@google.com>
Hi Hugh,
On 24/09/2022 09:40, Hugh Dickins wrote:
> On Fri, 23 Sep 2022, Borislav Petkov wrote:
>> 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.
>
> Yes, Nathan was alert, and saved me too from bisecting failure to boot
> linux-next in another thread.
>
> And I see from
> https://lore.kernel.org/lkml/c85a77a3-409b-3e83-08a7-ac7e1888790d@samsung.com/
> that Marek also found it: and tried to fix it, but found it goes too wide.
>
> I made a patch of the offending series with
> git diff 78ffa3e58d93^ 2b109cffe683
> and then reverted that cleanly from next-20220923: works for me.
Thanks for investigating. I believe I found from where is coming the
deadlock. I'll send a fix for that.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2022-09-24 8:18 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
2022-09-24 7:40 ` Hugh Dickins
2022-09-24 8:16 ` Daniel Lezcano [this message]
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=607cab94-ca0b-c7ea-b603-12d933e42ced@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=bp@alien8.de \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--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