[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Driver domain - NEW issue: IRQ handling error

  • To: bgb@xxxxxxxxx
  • From: Christian Limpach <christian.limpach@xxxxxxxxx>
  • Date: Wed, 2 Feb 2005 01:28:04 +0000
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 02 Feb 2005 01:34:13 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=kUme+sdGt7+okn3EupxQWzfjAWZrdbBQ4g+jkV0hBr4KL9/q+8SSmy4VEgSGPvBmfCFwTKeFfKj/qvkl8SZVnB01I0eLfljvwCVOY8iJ6b06b59W/dAWM6KIsIxhWlzX0SdyBcfUly+kUxyCZpfs0oypwI4yj2vf7C/aDmHjenM=
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>

On Tue, 01 Feb 2005 09:11:34 -0400, B.G. Bruce <bgb@xxxxxxxxx> 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.


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
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.