From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: i8042 error at booting an Intel Cherry Trail-based device
Date: Wed, 30 Nov 2016 18:29:23 -0800 [thread overview]
Message-ID: <20161201022923.GG31934@dtor-ws> (raw)
In-Reply-To: <s5hk2bn908b.wl-tiwai@suse.de>
Hi Takashi,
On Mon, Nov 28, 2016 at 02:56:36PM +0100, Takashi Iwai wrote:
> Hi Dmitry,
>
> I've been testing a small machine with Intel Cherry Trail chipset, and
> noticed that the kernel spews errors always like:
>
> i8042: PNP: No PS/2 controller found. Probing ports directly.
> i8042: Can't read CTR while initializing i8042
> i8042: probe of i8042 failed with error -5
>
> Especially the second one ("Can't read CTR...") is annoying since it's
> in KERN_ERR level and thus appears even booted with quiet boot
> option. Actually this is the only error message appearing at boot, so
> I'd love to get rid of it.
>
> What is the preferred way to reduce this? For example, is a patch
> like below OK to simply change the log level and the error code?
No, because if controller is actually present this is a hard failure and
we should be reporting it, not suppressing it.
The issue is that we did not believe PNP data and in this case we should
have. Unfortunately in old days there was a lot of crap in PNP/ACPI
tables, but it could be better now. We can try, in addition to PNP
matching, checking 8042 flag in "Fixed ACPI Description Table Boot
Architecture Flags" in FADT and if it also shows there is no 8042 then
bail.
Thanks.
>
>
> thanks,
>
> Takashi
>
> -- 8< --
> From: Takashi Iwai <tiwai@suse.de>
> Subject: [PATCH] i8042: Reduce the log level of i8042 CTR read error
>
> The error message "Can't read CTR while initializing i8042" appears on
> Cherry Trail-based devices at each boot time:
>
> i8042: PNP: No PS/2 controller found. Probing ports directly.
> i8042: Can't read CTR while initializing i8042
> i8042: probe of i8042 failed with error -5
>
> This is annoying, since it's the only error message with KERN_ERR
> level appearing during the boot.
>
> This patch changes the kernel log level to KERN_INFO for that message,
> and replaces the error code to -ENODEV so that this probe failure
> won't be complained like the above.
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
> drivers/input/serio/i8042.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
> index b4e1ac5c9ea8..2c2683e357e9 100644
> --- a/drivers/input/serio/i8042.c
> +++ b/drivers/input/serio/i8042.c
> @@ -980,8 +980,8 @@ static int i8042_controller_init(void)
> udelay(50);
>
> if (i8042_command(&ctr[n++ % 2], I8042_CMD_CTL_RCTR)) {
> - pr_err("Can't read CTR while initializing i8042\n");
> - return -EIO;
> + pr_info("Can't read CTR while initializing i8042\n");
> + return -ENODEV;
> }
>
> } while (n < 2 || ctr[0] != ctr[1]);
> --
> 2.10.2
>
--
Dmitry
next prev parent reply other threads:[~2016-12-01 2:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 13:56 i8042 error at booting an Intel Cherry Trail-based device Takashi Iwai
2016-11-30 14:19 ` Takashi Iwai
2016-12-01 2:29 ` Dmitry Torokhov [this message]
2016-12-01 7:19 ` Takashi Iwai
2016-12-02 10:55 ` Takashi Iwai
2016-12-06 0:56 ` Marcos Paulo de Souza
2016-12-06 6:07 ` Dmitry Torokhov
2016-12-06 10:36 ` Takashi Iwai
2016-12-06 17:07 ` Dmitry Torokhov
2016-12-06 19:05 ` Takashi Iwai
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=20161201022923.GG31934@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).