All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
	Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: pv_ops parport trouble
Date: Thu, 19 Feb 2009 15:38:44 +0100	[thread overview]
Message-ID: <499D6EF4.4000801@redhat.com> (raw)

  Hi,

I see on my test box _excessive_ irqs for parport0:

[root@xeni ~]# cat /proc/interrupts
           CPU0
[ ... ]
  7:   37316845  xen-pirq-pirq      parport0
[ ... ]
 24:      17698   xen-dyn-virq      timer0
[ ... ]

Something is seriously wrong here ...

cheers,
  Gerd

             reply	other threads:[~2009-02-19 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 14:38 Gerd Hoffmann [this message]
2009-02-19 15:28 ` pv_ops parport trouble Gerd Hoffmann
2009-02-19 16:07   ` Keir Fraser
2009-02-19 16:23     ` Jeremy Fitzhardinge
2009-02-19 16:31       ` Gerd Hoffmann
2009-02-19 16:37         ` Jeremy Fitzhardinge
2009-02-19 16:45           ` Gerd Hoffmann
2009-02-19 16:49             ` Jeremy Fitzhardinge
2009-02-19 16:56               ` Gerd Hoffmann
2009-02-19 17:11                 ` Keir Fraser
2009-02-19 16:51       ` Keir Fraser
2009-02-19 17:08         ` Jeremy Fitzhardinge

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=499D6EF4.4000801@redhat.com \
    --to=kraxel@redhat.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /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.