mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Jiri Slaby" <jslaby@suse.cz>
Cc: <gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>,
	<linux-serial@vger.kernel.org>
Subject: Re: [PATCH 1/1] serial: 8250, disable "too much work" messages
Date: Tue, 01 Apr 2014 14:43:39 +0200	[thread overview]
Message-ID: <s5hd2h1w77o.wl%tiwai@suse.de> (raw)
In-Reply-To: <1396352220-5031-1-git-send-email-jslaby@suse.cz>

At Tue,  1 Apr 2014 13:37:00 +0200,
Jiri Slaby wrote:
> 
> The 8250 driver now reports many of these:
>   serial8250: too much work for irq4
> These messages turned out to be common these days with a use of
> virtualization. I tried to increase the limit of processed characters
> in commit e7328ae1848966181a7ac47e8ae6cddbd2cf55f3 (serial: 8250,
> increase PASS_LIMIT) in 2011. It was raised from 256 to 512, but it is
> still not enough, apparently.

Actually, it looks like a side-effect of the reduction of tasklet.  In
the earlier code, tty_wakeup() was called via tasklet, and this made
the loop in the interrupt handler finishing once.  Now it's called
directly, thus the irq handler may pick up more than before.

> So disable the warning unless somebody turns on DEBUG (or
> DYNAMIC_DEBUG _and_ the message).
> 
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Reported-by: Martin Pluskal <mpluskal@suse.com>
> Reported-by: Takashi Iwai <tiwai@suse.com>
> References: https://bugzilla.novell.com/show_bug.cgi?id=868394


In case it's still worth:
	Tested-by: Takashi Iwai <tiwai@suse.de>

thanks,

Takashi


> ---
>  drivers/tty/serial/8250/8250_core.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> index 81f909c2101f..139ab1997e06 100644
> --- a/drivers/tty/serial/8250/8250_core.c
> +++ b/drivers/tty/serial/8250/8250_core.c
> @@ -1601,8 +1601,7 @@ static irqreturn_t serial8250_interrupt(int irq, void *dev_id)
>  		l = l->next;
>  
>  		if (l == i->head && pass_counter++ > PASS_LIMIT) {
> -			/* If we hit this, we're dead. */
> -			printk_ratelimited(KERN_ERR
> +			pr_debug_ratelimited(
>  				"serial8250: too much work for irq%d\n", irq);
>  			break;
>  		}
> -- 
> 1.9.1
> 
> 

  reply	other threads:[~2014-04-01 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 11:37 Jiri Slaby
2014-04-01 12:43 ` Takashi Iwai [this message]
2014-04-01 13:40 ` One Thousand Gnomes
2014-04-02  9:45   ` Jiri Slaby
2014-04-02 16:43     ` One Thousand Gnomes

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=s5hd2h1w77o.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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

all inboxes | Powered by JetHome®