All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.24 says "serial8250: too much work for irq4" a lot.
Date: Tue, 5 Feb 2008 14:55:10 -0600	[thread overview]
Message-ID: <200802051455.10831.rob@landley.net> (raw)

When running a 2.6.24 kernel built for x86-64 under qemu via serial console, 
doing CPU-intensive things that also produce a lot of output (such as 
compiling software) tends to produce the error message in the title.

Anybody have a clue why?  It doesn't seem to cause an actual problem, but it's 
kind of annoying.

(If it's a qemu issue, I can go bother them.  It's possible that qemu isn't 
delivering interrupts as often as it expects, since that's limited by the 
granularity of the host timer; I know the clock in qemu can run a bit slow 
because it only gets clock interrupts when the host system isn't too busy to 
schedule the emulator.  But this doesn't usually cause a problem.  I _think_ 
the message is just a "this should never happen" type warning, which is 
happening to me.  But I break stuff. :)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

             reply	other threads:[~2008-02-05 20:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 20:55 Rob Landley [this message]
2008-02-05 21:07 ` 2.6.24 says "serial8250: too much work for irq4" a lot H. Peter Anvin
2008-02-06  0:43   ` [Qemu-devel] " Rob Landley
2008-02-07 12:39   ` Ingo Molnar
2008-02-07 17:37     ` H. Peter Anvin
2008-02-07 20:13       ` Rob Landley
2008-02-07 20:53         ` H. Peter Anvin
2008-02-07 21:19         ` H. Peter Anvin
2008-02-08  7:04           ` Rob Landley
2008-02-09  5:49           ` [Qemu-devel] " Rob Landley
2008-02-09  7:04             ` Blue Swirl
2008-02-09  7:12               ` H. Peter Anvin
2008-02-09 11:15                 ` Blue Swirl
2008-02-09 21:36                   ` H. Peter Anvin
2008-02-10  8:01                     ` Blue Swirl
2008-02-10 11:26                       ` Paul Brook
2008-03-11 23:51                         ` Aurelien Jarno

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=200802051455.10831.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.