From: "Paul E. McKenney" <paulmck@kernel•org>
To: rjw@rjwysocki•net, lenb@kernel•org, linux-acpi@vger•kernel.org,
sfr@canb•auug.org.au
Cc: linux-next@vger•kernel.org
Subject: Re: next-20191118 rcutorture gets lots of "ACPI: Masking GPE 0x0"
Date: Tue, 19 Nov 2019 08:42:25 -0800 [thread overview]
Message-ID: <20191119164225.GA30878@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20191119145146.GA25855@paulmck-ThinkPad-P72>
On Tue, Nov 19, 2019 at 06:51:46AM -0800, Paul E. McKenney wrote:
> Hello!
>
> I had occasion to run rcutorture on next-20191118, and in a five-minute
> run got 1,810,735 instances of "ACPI: Masking GPE 0x0" printed to the
> console. This run is under qemu on an ordinary x86 laptop.
>
> Is this a known issue?
Apparently it is, apologies for the noise:
https://lkml.org/lkml/2019/11/18/163
Thanx, Paul
prev parent reply other threads:[~2019-11-19 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 14:51 next-20191118 rcutorture gets lots of "ACPI: Masking GPE 0x0" Paul E. McKenney
2019-11-19 16:25 ` Rafael J. Wysocki
2019-11-19 16:42 ` Paul E. McKenney [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=20191119164225.GA30878@paulmck-ThinkPad-P72 \
--to=paulmck@kernel$(echo .)org \
--cc=lenb@kernel$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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