From: Christian Limpach <christian.limpach@gmail.com>
To: bgb@nt-nv.com
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Driver domain - NEW issue: IRQ handling error
Date: Wed, 2 Feb 2005 01:28:04 +0000 [thread overview]
Message-ID: <3d8eece205020117282731fd2@mail.gmail.com> (raw)
In-Reply-To: <1107263493.4411.22.camel@master.vms.security>
On Tue, 01 Feb 2005 09:11:34 -0400, B.G. Bruce <bgb@nt-nv.com> wrote:
> dmesg on dom0 gives:
> irq 18: nobody cared!
> Disabling IRQ #18
>
> and a dmesg of the driver domain shows that the nic hooked IRQ 18:
>
> Intel(R) PRO/1000 Network Driver - version 5.5.4-k2-NAPI
> Copyright (c) 1999-2004 Intel Corporation.
> PCI: Obtained IRQ 18 for device 0000:01:01.0
> PCI: Setting latency timer of device 0000:01:01.0 to 64
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Do you have any other devices which get assigned IRQ 18? Xen prints
information about the interrupt routing when it starts, you can read
this information with xm dmesg. Also lspci -v should show for each
device not hidden from dom0 which interrupt is used by the device.
FWIW, I've seen "irq nobody cared" on the IRQ assigned to the USB
controller and a kernel without USB support.
> Am I correct in that the interrupt that should have been sent to the
> driver domain was instead sent to dom0? or what happened? If I don't
> have the driver dom setup correctly, would someone please explain what
> I'm doing wrong?
Yes, it should have been sent to the driver domain. If there's a 2nd
device on IRQ 18 and this device is not hidden from dom0 and the 2nd
device gets an interrupt, it will go to dom0. This should be harmless
but apparently, it's not.
christian
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-02-02 1:28 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 [this message]
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
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=3d8eece205020117282731fd2@mail.gmail.com \
--to=christian.limpach@gmail.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=bgb@nt-nv.com \
--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.