From: Mathieu Chouquet-Stringer <me@mathieu.digital>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Mel Gorman <mgorman@techsingularity.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-rtc@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: Intermittent boot failure after 6492fed7d8c9 (v6.0-rc1)
Date: Mon, 12 Dec 2022 19:24:50 +0100 [thread overview]
Message-ID: <Y5dx8pskqpaQU8kk@paranoid-android> (raw)
In-Reply-To: <20221011092050.gnh3dr5iqdvvrgs5@techsingularity.net>
Hello Rafael,
On Tue, Oct 11, 2022 at 10:20:50AM +0100, Mel Gorman wrote:
> On Mon, Oct 10, 2022 at 08:29:05PM +0200, Rafael J. Wysocki wrote:
> > > That's less than the previous 5/10 failures but I
> > > cannot be certain it helped without running a lot more boot tests. The
> > > failure happens in the same function as before.
> >
> > I've overlooked the fact that acpi_install_fixed_event_handler()
> > enables the event on success, so it is a bug to call it when the
> > handler is not ready.
> >
> > It should help to only enable the event after running cmos_do_probe()
> > where the driver data pointer is set, so please try the attached
> > patch.
I'm hitting this issue on the 6.0 stable releases (aka 6.0.y) and
looking at the stable tree I see this hasn't been merged... I just got
bitten by this on 6.0.12.
Greg, if Rafael agrees, I think you should apply 4919d3eb2ec0 and
0782b66ed2fb to the 6.0.y tree.
Thank you in advance.
Cheers,
--
Mathieu Chouquet-Stringer me@mathieu.digital
The sun itself sees not till heaven clears.
-- William Shakespeare --
next prev parent reply other threads:[~2022-12-12 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 14:16 Intermittent boot failure after 6492fed7d8c9 (v6.0-rc1) Mel Gorman
2022-10-10 14:47 ` Rafael J. Wysocki
2022-10-10 17:45 ` Mel Gorman
2022-10-10 18:29 ` Rafael J. Wysocki
2022-10-11 9:20 ` Mel Gorman
2022-12-12 18:24 ` Mathieu Chouquet-Stringer [this message]
2022-12-12 18:34 ` Rafael J. Wysocki
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=Y5dx8pskqpaQU8kk@paranoid-android \
--to=me@mathieu.digital \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stable@vger.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