From mboxrd@z Thu Jan 1 00:00:00 1970 From: "B.G. Bruce" Subject: Driver domain - NEW issue: IRQ handling error Date: Tue, 01 Feb 2005 09:11:34 -0400 Message-ID: <1107263493.4411.22.camel@master.vms.security> Reply-To: bgb@nt-nv.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel List-Id: xen-devel@lists.xenproject.org Okay, I'm using a bk snapshot of testing as of 20:40 (-4:00) yesterday so I'm pretty sure this hasn't been addressed already. Symptom: While running a "ping -f " from dom0 where the physical nic is in a driver dom (bridged), after about 1 minute the connection dies and won't restart. (even with a reboot of the driver domain). ex. Dom0 vif1.0=10.1.1.1/24 outside host=10.1.1.2/24 e1000 driver dom = bridge containing physical e1000(eth0) and virtual nic (eth1) dmesg on dom0 gives: irq 18: nobody cared! [] [] [] [] [] [] [] [] [] handlers: [] [] 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 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? Thanks, 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