LKML Archive on
help / color / mirror / Atom feed
From: Alan Cox <>
To: Benjamin LaHaise <>
Subject: Re: [PATCH] serial: remove "too much work for irq" printk
Date: Sat, 12 Jan 2008 21:24:57 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, 12 Jan 2008 15:15:43 -0500
Benjamin LaHaise <> wrote:

> When using kvm with a serial console, the serial driver will print out 
> "too much work for irq4" on any heavy activity (ie vi on a file repainting 
> the terminal).  This message is entirely spurious, as output continues to 
> work fine.  Remove the message as it corrupts screen output and is far too 
> easy to trigger.

NAK. This is a qemu/kvm emulation bug. The real check is there to catched
jammed IRQs and combined with the IRQ bug handling nowdays does actually
do the intended job.

Our serial port code (correctly) interprets a continuous stream of bytes
at an impossible bit rate as an error. KVM should be emulating to some
extent at least the timing on serial interfaces or using a virtualised


  parent reply	other threads:[~2008-01-12 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12 20:15 [PATCH] serial: remove "too much work for irq" printk Benjamin LaHaise
2008-01-12 20:21 ` Christoph Hellwig
2008-01-12 21:24 ` Alan Cox [this message]
2008-01-12 21:39   ` H. Peter Anvin
2008-01-12 21:42     ` Alan Cox
2008-01-12 21:58       ` H. Peter Anvin
2008-01-13 22:03   ` Pavel Machek

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).