All of lore.kernel.org
 help / color / mirror / Atom feed
From: "B.G. Bruce" <bgb@nt-nv.com>
To: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Driver domain - NEW issue: IRQ handling error
Date: Wed, 02 Feb 2005 14:00:18 -0400	[thread overview]
Message-ID: <1107367218.4411.134.camel@master.vms.security> (raw)
In-Reply-To: <20050202024716.GP13868@cl.cam.ac.uk>

What I've actually found is that if is disable the disabling of the
interrupt in kernel/irq/spurious.c, everything works fine.  I still get
the error messages (I didn't comment them out) about every
50.000-100.000 packets but I don't drop a packet and everything works as
it should.  Now obviously I don't want to keep the disabling irq
disabled, but I'm at a loss for how to fix this otherwise.

B.


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-02-02 18:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01 13:11 Driver domain - NEW issue: IRQ handling error B.G. Bruce
2005-02-01 13:10 ` Mark Williamson
2005-02-01 13:48   ` B.G. Bruce
2005-02-01 16:13   ` B.G. Bruce
2005-02-01 17:01     ` B.G. Bruce
2005-02-02  1:01       ` B.G. Bruce
2005-02-01 19:19 ` Anonymous
2005-02-02  1:28 ` Christian Limpach
2005-02-02  2:09   ` B.G. Bruce
2005-02-02  2:47     ` Christian Limpach
2005-02-02 17:48       ` B.G. Bruce
2005-02-02 18:00       ` B.G. Bruce [this message]
2005-02-02 20:04         ` Christian Limpach
2005-02-02 21:26           ` B.G. Bruce
  -- strict thread matches above, loose matches on Subject: below --
2005-02-02 22:43 Ian Pratt

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=1107367218.4411.134.camel@master.vms.security \
    --to=bgb@nt-nv.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.