From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
linux acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: ACPI: EC: Fix logspam in "GPE storm avoidance" code
Date: Tue, 28 Oct 2008 22:12:31 -0200 [thread overview]
Message-ID: <20081029001231.GA22985@khazad-dum.debian.net> (raw)
In-Reply-To: <4907590E.4070104@suse.de>
On Tue, 28 Oct 2008, Alexey Starikovskiy wrote:
> Alan Jenkins wrote:
>> <http://bugzilla.kernel.org/show_bug.cgi?id=11841>
>> "plenty of line "ACPI: EC: non-query interrupt received,
>> switching to interrupt mode" in dmesg"
> Probably, it is better to make pr_debug().
Please don't do that. This code has had a lot of churn, and *regressions*
as of lately, and sometimes we only notice these because we see those
messages in the logs. Moving them to pr_debug() pretty much makes them
utterly useless in a large number of the cases they could be of help.
Besides, I very much doubt we will stop seing EC interrupt crappage. Not
only our code is NOT good and resilient enough yet (if it were, there
wouldn't be so many patches flying about it), the vendors are obviously
getting this wrong at a fast rate.
We need those messages. Rate-limit them, but don't hide them or move them
to pr_debug, please.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-10-29 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 14:05 ACPI: EC: Fix logspam in "GPE storm avoidance" code Alan Jenkins
2008-10-28 18:25 ` Alexey Starikovskiy
2008-10-28 20:18 ` Alan Jenkins
2008-10-29 0:12 ` Henrique de Moraes Holschuh [this message]
2008-10-29 9:51 ` Alan Jenkins
2008-10-29 15:08 ` Henrique de Moraes Holschuh
2008-10-29 16:35 ` Alan Jenkins
2008-10-29 19:00 ` Alexey Starikovskiy
2008-11-01 11:03 ` Alan Jenkins
2008-10-30 1:47 ` Zhao Yakui
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=20081029001231.GA22985@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=astarikovskiy@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@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