public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Lee Revell <rlrevell@joe-job.com>,
	Hugh Dickins <hugh@veritas.com>, Andi Kleen <ak@suse.de>,
	vojtech@suse.cz, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable the most annoying printk in the kernel
Date: Fri, 28 Oct 2005 23:23:05 +0200	[thread overview]
Message-ID: <20051028212305.GA2447@elf.ucw.cz> (raw)
In-Reply-To: <20051028205916.GL4464@flint.arm.linux.org.uk>

Hi!

> > Well, keyboard detected and reported an error. Kernel reacted with
> > printk(). You are removing that printk(). I can understand that,
> > printk is really annoying, but I really believe _some_ error handling
> > should be added there if you remove the printk.
> 
> What do you suggest?

Well, having error counter for each input device would probably be
enough. Or perhaps add some rate-limiting. One message per boot should
be adequate.

> Having a TP 380XD which regularly produces this annoying message,
> it's just logspam.  There's no noticable failure.

I do notice lost keys on x32 here. You need to press some weird
combination...
							Pavel
-- 
Thanks, Sharp!

  parent reply	other threads:[~2005-10-28 21:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27  8:26 [PATCH] Disable the most annoying printk in the kernel Andi Kleen
2005-10-27 14:04 ` Keenan Pepper
2005-10-27 14:39   ` Steven Rostedt
2005-10-27 22:00     ` Jan Engelhardt
2005-10-27 18:03 ` Ingo Oeser
2005-10-27 23:23   ` jerome lacoste
2005-10-28  7:20 ` Pavel Machek
2005-10-28 18:43   ` Andi Kleen
2005-10-28 18:52     ` Andre Eisenbach
2005-10-28 18:50   ` Hugh Dickins
2005-10-28 20:43     ` Lee Revell
2005-10-28 20:51       ` Pavel Machek
2005-10-28 20:59         ` Russell King
2005-10-28 21:20           ` Jan Engelhardt
2005-10-28 21:22           ` Andi Kleen
2005-10-28 21:40             ` Russell King
2005-10-28 22:41             ` Jon Masters
2005-10-28 21:23           ` Pavel Machek [this message]
2005-10-28 21:36             ` Russell King
2005-10-29 15:40             ` Ingo Oeser
2005-10-29  7:45           ` Pavel Machek
2005-10-29 15:36       ` Ingo Oeser
     [not found] <52bjf-680-9@gated-at.bofh.it>
     [not found] ` <52Hj9-3e6-27@gated-at.bofh.it>
     [not found]   ` <52HCr-3CO-7@gated-at.bofh.it>
     [not found]     ` <52JkU-6gS-29@gated-at.bofh.it>
     [not found]       ` <52JuY-6s7-21@gated-at.bofh.it>
2005-10-28 22:18         ` Bodo Eggert

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=20051028212305.GA2447@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=vojtech@suse.cz \
    /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