CC drivers/pci/xen-pcifront.o
drivers/pci/xen-pcifront.c:373: error: variable ‘pci_frontend_ops’ has initializer but incomplete type
drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’ specified in initializer
drivers/pci/xen-pcifront.c:374: warning: excess elements in struct initializer
drivers/pci/xen-pcifront.c:374: warning: (near initialization for ‘pci_frontend_ops’)
drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’ specified in initializer
drivers/pci/xen-pcifront.c:375: warning: excess elements in struct initializer
drivers/pci/xen-pcifront.c:375: warning: (near initialization for ‘pci_frontend_ops’)
drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’ specified in initializer
drivers/pci/xen-pcifront.c:376: warning: excess elements in struct initializer
drivers/pci/xen-pcifront.c:376: warning: (near initialization for ‘pci_frontend_ops’)
drivers/pci/xen-pcifront.c:377: error: unknown field ‘disable_msix’ specified in initializer
drivers/pci/xen-pcifront.c:377: warning: excess elements in struct initializer
drivers/pci/xen-pcifront.c:377: warning: (near initialization for ‘pci_frontend_ops’)
drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’ undeclared (first use in this function)
drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is reported only once
drivers/pci/xen-pcifront.c:383: error: for each function it appears in.)
make[2]: *** [drivers/pci/xen-pcifront.o] Error 1
make[1]: *** [drivers/pci] Error 2
make: *** [drivers] Error 2
Thanks!
Thiago
On 1 April 2010 04:38, Stefan Kuhne
<stefan.kuhne@xxxxxxx> wrote:
Am 31.03.2010 22:31, schrieb Jeremy Fitzhardinge:
> On 03/31/2010 01:26 PM, Stefan Kuhne wrote:
>> Am 31.03.2010 21:06, schrieb Jeremy Fitzhardinge:
>>> On 03/31/2010 11:14 AM, Stefan Kuhne wrote:
Hi Jeremy,
Yes.
> OK, but can you post all the output before the hang? And also the
> content of /proc/interrupts (ideally before and after starting the
> domain with the passthrough WLAN card).
>
I've take a look on the real console.
I got:
irq 18: nobody cared (try booting with the "irqpoll" option)
handlers:
[<edb28270>] (usb_hcd_irq+0x0/0x80 [usbcore])
Disabling IRQ #18
This is 2.6.32.x on xen-4.0.0-rc9 an 2.6.20 (Gentoo) domU kernel with
more patches.
Another question, cpufreq isn't running with 2.6.32 from you (Intel
T5200 CPU). 2.6.31 works fine.
The interrupts:
maxdata # cat /interrupts.txt
CPU0 CPU1
1: 8 0 xen-pirq-ioapic-edge i8042
9: 73 0 xen-pirq-ioapic-edge acpi
12: 13 0 xen-pirq-ioapic-edge i8042
14: 98 0 xen-pirq-ioapic-edge ata_piix
15: 0 0 xen-pirq-ioapic-edge ata_piix
16: 1415 0 xen-pirq-ioapic-level uhci_hcd:usb4, peth0
18: 0 0 xen-pirq-ioapic-level uhci_hcd:usb3
19: 10198 0 xen-pirq-ioapic-level uhci_hcd:usb2, ahci
22: 92 0 xen-pirq-ioapic-level HDA Intel
23: 57 0 xen-pirq-ioapic-level uhci_hcd:usb1,
ehci_hcd:usb5
754: 0 0 xen-dyn-event evtchn:xenstored
755: 66 0 xen-dyn-event evtchn:xenstored
757: 89 0 xen-dyn-event xenbus
758: 0 1013 xen-dyn-ipi callfuncsingle1
759: 0 0 xen-dyn-virq debug1
760: 0 0 xen-dyn-ipi callfunc1
761: 0 4454 xen-dyn-ipi resched1
762: 0 67636 xen-dyn-virq timer1
763: 306 0 xen-dyn-ipi callfuncsingle0
764: 0 0 xen-dyn-virq debug0
765: 0 0 xen-dyn-ipi callfunc0
766: 3788 0 xen-dyn-ipi resched0
767: 67642 0 xen-dyn-virq timer0
NMI: 0 0 Non-maskable interrupts
LOC: 0 0 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
PND: 0 0 Performance pending work
RES: 3788 4454 Rescheduling interrupts
CAL: 306 1013 Function call interrupts
TLB: 0 0 TLB shootdowns
ERR: 0
MIS: 0
Start Domu
CPU0 CPU1
1: 8 0 xen-pirq-ioapic-edge i8042
9: 83 0 xen-pirq-ioapic-edge acpi
12: 13 0 xen-pirq-ioapic-edge i8042
14: 98 0 xen-pirq-ioapic-edge ata_piix
15: 0 0 xen-pirq-ioapic-edge ata_piix
16: 2025 0 xen-pirq-ioapic-level uhci_hcd:usb4, peth0
18: 2322 0 xen-pirq-ioapic-level uhci_hcd:usb3
19: 10960 0 xen-pirq-ioapic-level uhci_hcd:usb2, ahci
22: 92 0 xen-pirq-ioapic-level HDA Intel
23: 57 0 xen-pirq-ioapic-level uhci_hcd:usb1,
ehci_hcd:usb5
749: 31 0 xen-dyn-event vif1.0
750: 125 0 xen-dyn-event blkif-backend
751: 93 0 xen-dyn-event pciback
752: 188 0 xen-dyn-event evtchn:xenconsoled
753: 168 0 xen-dyn-event evtchn:xenstored
754: 0 0 xen-dyn-event evtchn:xenstored
755: 586 0 xen-dyn-event evtchn:xenstored
757: 1071 0 xen-dyn-event xenbus
758: 0 1229 xen-dyn-ipi callfuncsingle1
759: 0 0 xen-dyn-virq debug1
760: 0 0 xen-dyn-ipi callfunc1
761: 0 6805 xen-dyn-ipi resched1
762: 0 79188 xen-dyn-virq timer1
763: 322 0 xen-dyn-ipi callfuncsingle0
764: 0 0 xen-dyn-virq debug0
765: 0 0 xen-dyn-ipi callfunc0
766: 5531 0 xen-dyn-ipi resched0
767: 79189 0 xen-dyn-virq timer0
NMI: 0 0 Non-maskable interrupts
LOC: 0 0 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
PND: 0 0 Performance pending work
RES: 5531 6805 Rescheduling interrupts
CAL: 322 1229 Function call interrupts
TLB: 0 0 TLB shootdowns
ERR: 0
MIS: 0
maxdata #
Regards,
Stefan Kuhne
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
