|
Well, apic was, indeed, disabled, however after re-enabling it, deleting the domain, and recreating the domain, the issue persists, and the network card is still using IRQ 5. Also, I have another domU that has the same behavior that has apic enabled. I'm attempting to delete the network device and re-add it now and see if that works, but I've tried this in the other domU and it doesn't seem to have made a difference.
-Nick
>>> "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 2008/11/10 17:04 >>>
Interesting... you are using irq 5. Are you not running with apic=1 in
the config?
I suspect that the problems you are seeing are because you are using an
interrupt < 16, which behave a little differently than those > 16. On my
system (apic and acpi left at the default of enabled) the Xen PCI Device
gets IRQ 28 and all the sub-devices use the same IRQ (even though device
manager reports the IRQ as ISA).
James
> -----Original Message-----
> From: Nick Couchman [mailto:Nick.Couchman@xxxxxxxxx]
> Sent: Tuesday, 11 November 2008 11:00
> To: James Harper; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] GPL PV Intermitent Network Problems
>
> Here you go. I ran the command a few times - not sure if that matters
or
> not.
>
> -Nick
>
> >>> "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 2008/11/10 16:13
>>>
> >
> > Version shows as 0.9.11.
>
> Pity.
>
> Okay, please fire up DebugView and in Dom0 type "xm sysrq <domain> C".
> That will cause some debug information to be dumped. Please put that
in
> an email to me. It should look something like:
>
> XenPCI --> XenPci_SysrqHandler
> XenPCI SysRq Value = C
> XenPCI path = device/vfb/0
> XenPCI backend_path = /local/domain/0/backend/vfb/82/0
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI path = device/vbd/768
> XenPCI backend_path = /local/domain/0/backend/vbd/82/768
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI path = device/vbd/5632
> XenPCI backend_path = /local/domain/0/backend/vbd/82/5632
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI path = device/vif/0
> XenPCI backend_path = /local/domain/0/backend/vif/82/0
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI path = device/vif/1
> XenPCI backend_path = /local/domain/0/backend/vif/82/1
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI path = device/vif/2
> XenPCI backend_path = /local/domain/0/backend/vif/82/2
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI path = device/console/0
> XenPCI backend_path = /local/domain/0/backend/console/82/0
> XenPCI irq_number = 28
> XenPCI irq_level = 9
> XenPCI irq_vector = 1a3
> XenPCI <-- XenPci_SysrqHandler
>
> Thanks
>
> James
>
>
> ________________________________
>
> This e-mail may contain confidential and privileged material for the
sole
> use of the intended recipient. If this email is not intended for you,
or
> you are not responsible for the delivery of this message to the
intended
> recipient, please note that this message may contain SEAKR Engineering
> (SEAKR) Privileged/Proprietary Information. In such a case, you are
> strictly prohibited from downloading, photocopying, distributing or
> otherwise using this message, its contents or attachments in any way.
If
> you have received this message in error, please notify us immediately
by
> replying to this e-mail and delete the message from your mailbox.
> Information contained in this message that does not relate to the
business
> of SEAKR is neither endorsed by nor attributable to SEAKR.
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|
