From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Please test xen/stable-2.6.32.x in xen.git
Date: Thu, 1 Apr 2010 14:55:45 -0300 [thread overview]
Message-ID: <o2h6b7f6eb1004011055rae49d0f0r60c3f1bbda78b301@mail.gmail.com> (raw)
In-Reply-To: <4BB44D6F.8060008@access.denied>
[-- Attachment #1.1: Type: text/plain, Size: 7240 bytes --]
Hi!
I can't compile it:
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@gmx.net> 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,
>
> > You mean this patch?
> > http://lists.xensource.com/archives/html/xen-devel/2010-02/msg00832.html
> >
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 8384 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-04-01 17:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 17:58 Please test xen/stable-2.6.32.x in xen.git Jeremy Fitzhardinge
2010-03-31 18:14 ` Stefan Kuhne
2010-03-31 19:06 ` Jeremy Fitzhardinge
2010-03-31 20:26 ` Stefan Kuhne
2010-03-31 20:31 ` Jeremy Fitzhardinge
2010-04-01 7:38 ` Stefan Kuhne
2010-04-01 17:55 ` Martinx - ジェームズ [this message]
2010-04-01 19:35 ` Jeremy Fitzhardinge
2010-04-01 20:29 ` Martinx - ジェームズ
2010-04-01 20:06 ` Konrad Rzeszutek Wilk
2010-04-01 19:06 ` Jeremy Fitzhardinge
2010-04-01 19:55 ` Stefan Kuhne
2010-04-01 20:08 ` Jeremy Fitzhardinge
2010-04-01 21:04 ` Stefan Kuhne
2010-04-01 21:49 ` Jeremy Fitzhardinge
2010-04-01 21:54 ` Stefan Kuhne
2010-04-01 22:02 ` Jeremy Fitzhardinge
2010-04-01 22:08 ` Stefan Kuhne
2010-04-02 10:51 ` Pasi Kärkkäinen
2010-04-03 14:10 ` X-Server doesn't start under Xen 4.0-rc9 & 2.6.31.11 pvops on top of F12 Boris Derzhavets
2010-04-06 18:30 ` Jeremy Fitzhardinge
2010-04-06 21:37 ` Boris Derzhavets
2010-04-06 22:01 ` Jeremy Fitzhardinge
2010-04-06 22:40 ` Mark Hurenkamp
2010-04-06 22:41 ` Jeremy Fitzhardinge
2010-04-06 23:08 ` Mark Hurenkamp
2010-04-07 11:30 ` Boris Derzhavets
2010-04-07 16:20 ` Boris Derzhavets
2010-04-06 22:38 ` Mark Hurenkamp
2010-04-06 22:40 ` Jeremy Fitzhardinge
2010-04-02 13:11 ` Bugs in 2.6.31.12-pvops Carsten Schiers
2010-04-02 18:11 ` Jeremy Fitzhardinge
2010-04-08 0:30 ` Please test xen/stable-2.6.32.x in xen.git Konrad Rzeszutek Wilk
[not found] ` <4BBD9DC7.603@access.denied>
2010-04-08 14:59 ` Konrad Rzeszutek Wilk
2010-03-31 18:45 ` Pasi Kärkkäinen
2010-03-31 20:10 ` Olivier B.
2010-03-31 20:32 ` Olivier B.
2010-03-31 20:35 ` Jeremy Fitzhardinge
2010-03-31 20:43 ` Olivier B.
2010-04-05 16:53 ` Guillaume Rousse
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=o2h6b7f6eb1004011055rae49d0f0r60c3f1bbda78b301@mail.gmail.com \
--to=thiagocmartinsc@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).