Hi I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a HP DL385 G6. It booted after some time, but was unuable to access several devices using traditional IO-APIC. The interrupt configuration listed for these is identical between Xen and native except that in the native case several of them are marked as "IO-APIC-fasteoi". Devices using MSI are working fine. Partial /proc/interrupts output with comparation of Xen and native: | 5: IO-APIC-fasteoi ehci_hcd:usb1, ohci_hcd:usb3, ohci_hcd:usb4 | 5: xen-pirq-ioapic-edge ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb4 | 14: IO-APIC-fasteoi sata_svw | 14: xen-pirq-ioapic-edge sata_svw Kernel log showing the setup of this devices: [ 0.000000] xen: registering gsi 5 triggering 1 polarity 0 [ 0.000000] xen: --> irq=5 [ 0.000000] Already setup the GSI :5 [ 0.000000] xen: registering gsi 14 triggering 1 polarity 0 [ 0.000000] xen: --> irq=14 [ 0.000000] Already setup the GSI :14 [ 1.625355] ACPI: PCI Interrupt Link [IUSB] enabled at IRQ 5 [ 1.625594] xen: registering gsi 5 triggering 0 polarity 1 [ 1.625607] xen_allocate_pirq: returning irq 5 for gsi 5 [ 1.625872] xen: --> irq=5 [ 1.625883] Already setup the GSI :5 [ 1.626062] ehci_hcd 0000:00:07.2: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5 [ 1.626506] ehci_hcd 0000:00:07.2: EHCI Host Controller [ 1.626805] ehci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 [ 1.652169] ehci_hcd 0000:00:07.2: irq 5, io mem 0xf3dc0000 [ 1.717401] sata_svw 0000:01:0e.0: version 2.3 [ 1.718282] ACPI: PCI Interrupt Link [ISF0] enabled at IRQ 14 [ 1.718520] xen: registering gsi 14 triggering 0 polarity 1 [ 1.718533] xen_allocate_pirq: returning irq 14 for gsi 14 [ 1.718747] xen: --> irq=14 [ 1.718754] Already setup the GSI :14 [ 1.718903] sata_svw 0000:01:0e.0: PCI INT A -> Link[ISF0] -> GSI 14 (level, low) -> IRQ 14 [ 1.719514] scsi0 : sata_svw [ 1.719922] scsi1 : sata_svw [ 1.720404] scsi2 : sata_svw [ 1.720739] scsi3 : sata_svw [ 1.720996] ata1: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0000 irq 14 [ 1.721272] ata2: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0100 irq 14 [ 1.721536] ata3: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0200 irq 14 [ 1.721809] ata4: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0300 irq 14 Kernel log showing interrupt problems on GSI 5: [ 7.452081] ohci_hcd 0000:00:07.1: Unlink after no-IRQ? Controller is probably using the wrong IRQ. Kernel log showing interrupt problems on GSI 14: [ 2.044101] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.068427] ata1.00: ATAPI: Optiarc DVD RW AD-7561S, AH52, max UDMA/100 [ 2.100357] ata1.00: configured for UDMA/100 [ 7.100098] ata1.00: qc timeout (cmd 0xa0) [ 7.100263] ata1.00: TEST_UNIT_READY failed (err_mask=0x5) [ 7.420101] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 7.476356] ata1.00: configured for UDMA/100 [ 12.476098] ata1.00: qc timeout (cmd 0xa0) [ 12.476264] ata1.00: TEST_UNIT_READY failed (err_mask=0x5) [ 12.476463] ata1: limiting SATA link speed to 1.5 Gbps [ 12.476647] ata1.00: limiting speed to UDMA/100:PIO3 [ 12.796136] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 12.852354] ata1.00: configured for UDMA/100 [ 17.852103] ata1.00: qc timeout (cmd 0xa0) [ 17.852267] ata1.00: TEST_UNIT_READY failed (err_mask=0x5) [ 17.852463] ata1.00: disabled [ 17.852593] ata1: hard resetting link [ 18.172109] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 18.172351] ata1: EH complete [ 18.496032] ata2: SATA link down (SStatus 4 SControl 300) [ 18.824031] ata3: SATA link down (SStatus 4 SControl 300) [ 19.152032] ata4: SATA link down (SStatus 4 SControl 300) IO-APIC info from Xen: (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #8 registers: 16. (XEN) number of IO-APIC #9 registers: 16. (XEN) number of IO-APIC #10 registers: 16. (XEN) testing the IO APIC....................... (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 008 08 0 0 0 0 0 0 0 20 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 28 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 005 05 0 0 0 0 0 0 0 30 (XEN) 06 000 00 0 0 0 0 0 0 0 38 (XEN) 07 000 00 0 0 0 0 0 0 0 40 (XEN) 08 008 08 0 0 0 0 0 0 0 48 (XEN) 09 000 00 0 1 0 1 0 0 0 50 (XEN) 0a 000 00 0 0 0 0 0 0 0 58 (XEN) 0b 000 00 0 0 0 0 0 0 0 60 (XEN) 0c 008 08 0 0 0 0 0 0 0 68 (XEN) 0d 000 00 0 0 0 0 0 0 0 70 (XEN) 0e 00B 0B 0 0 0 0 0 0 0 78 (XEN) 0f 000 00 0 0 0 0 0 0 0 88 (XEN) IO APIC #9...... (XEN) .... register #00: 09000000 (XEN) ....... : physical APIC id: 09 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 09000000 (XEN) ....... : arbitration: 09 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) IO APIC #10...... (XEN) .... register #00: 0A000000 (XEN) ....... : physical APIC id: 0A (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 0A000000 (XEN) ....... : arbitration: 0A (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 1 0 1 0 0 0 C0 (XEN) 01 000 00 1 1 0 1 0 0 0 C8 (XEN) 02 000 00 1 1 0 1 0 0 0 D0 (XEN) 03 000 00 1 1 0 1 0 0 0 D8 (XEN) 04 000 00 1 1 0 1 0 0 0 B8 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 1 0 1 0 0 0 98 (XEN) 07 000 00 1 1 0 1 0 0 0 A0 (XEN) 08 000 00 1 1 0 1 0 0 0 A8 (XEN) 09 000 00 1 1 0 1 0 0 0 B0 (XEN) 0a 000 00 1 1 0 1 0 0 0 90 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 1 0 1 0 0 0 A1 (XEN) 0d 00B 0B 0 1 0 1 0 0 0 91 (XEN) 0e 008 08 0 1 0 1 0 0 0 99 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ32 -> 0:1 (XEN) IRQ40 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ48 -> 0:5 (XEN) IRQ56 -> 0:6 (XEN) IRQ64 -> 0:7 (XEN) IRQ72 -> 0:8 (XEN) IRQ80 -> 0:9 (XEN) IRQ88 -> 0:10 (XEN) IRQ96 -> 0:11 (XEN) IRQ104 -> 0:12 (XEN) IRQ112 -> 0:13 (XEN) IRQ120 -> 0:14 (XEN) IRQ136 -> 0:15 (XEN) IRQ192 -> 2:0 (XEN) IRQ200 -> 2:1 (XEN) IRQ208 -> 2:2 (XEN) IRQ216 -> 2:3 (XEN) IRQ184 -> 2:4 (XEN) IRQ152 -> 2:6 (XEN) IRQ160 -> 2:7 (XEN) IRQ168 -> 2:8 (XEN) IRQ176 -> 2:9 (XEN) IRQ144 -> 2:10 (XEN) IRQ161 -> 2:12 (XEN) IRQ145 -> 2:13 (XEN) IRQ153 -> 2:14 -- Kirk to Enterprise -- beam down yeoman Rand and a six-pack. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2010-Mar-10 16:08 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Wed, 2010-03-10 at 11:19 +0000, Bastian Blank wrote:> Hi > > I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a > HP DL385 G6.Which particular branch of the current tree? There''s a few which involve 2.6.32. I was having some weird issues with my network card (that I suspected were interrupt related) which, I think, went away when I pulled in: commit cdab7a09b1bd682c5b14effd98a6312c8b798297 Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Date: Wed Mar 3 18:05:56 2010 -0500 xen: Make sure to use the physical IRQ (GSI) instead of the irq. The IRQ chip startup handler was using the wrong IRQ number. This fixes it to use the GSI provided. Although it is possible that was a coincidence. BTW, I''m running with the version of the patches you''ve currently got in the Debian kernel repo with no problems other than the SPARSE_IRQ one discussed on xen-devel last week. Thanks! Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-10 16:19 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Wed, Mar 10, 2010 at 04:08:21PM +0000, Ian Campbell wrote:> On Wed, 2010-03-10 at 11:19 +0000, Bastian Blank wrote: > > I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a > > HP DL385 G6. > Which particular branch of the current tree? There''s a few which involve > 2.6.32.xen/stable-2.6.32.x, aka the patch I pulled into the Debian kernel.> I was having some weird issues with my network card (that I suspected > were interrupt related) which, I think, went away when I pulled in: > commit cdab7a09b1bd682c5b14effd98a6312c8b798297Lets try. According to git, this commit is only in xen/next. Bastian -- Witch! Witch! They''ll burn ya! -- Hag, "Tomorrow is Yesterday", stardate unknown _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Mar-10 18:17 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On 03/10/2010 08:19 AM, Bastian Blank wrote:>> I was having some weird issues with my network card (that I suspected >> were interrupt related) which, I think, went away when I pulled in: >> commit cdab7a09b1bd682c5b14effd98a6312c8b798297 >> > Lets try. According to git, this commit is only in xen/next. >OK, I''ve merged it into xen/stable-2.6.32.x. Let me know how it goes. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2010-Mar-10 19:40 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Wed, 2010-03-10 at 16:19 +0000, Bastian Blank wrote:> On Wed, Mar 10, 2010 at 04:08:21PM +0000, Ian Campbell wrote: > > On Wed, 2010-03-10 at 11:19 +0000, Bastian Blank wrote: > > > I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a > > > HP DL385 G6. > > Which particular branch of the current tree? There''s a few which involve > > 2.6.32. > > xen/stable-2.6.32.x, aka the patch I pulled into the Debian kernel.Hmm, which is what I''m running now, suggesting that the cdab7a09 patch is unrelated to your problem (whether its in that tree or not). I guess it means it was unrelated to my problem too... Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Mar-10 20:00 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Wed, Mar 10, 2010 at 07:40:22PM +0000, Ian Campbell wrote:> On Wed, 2010-03-10 at 16:19 +0000, Bastian Blank wrote: > > On Wed, Mar 10, 2010 at 04:08:21PM +0000, Ian Campbell wrote: > > > On Wed, 2010-03-10 at 11:19 +0000, Bastian Blank wrote: > > > > I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a > > > > HP DL385 G6. > > > Which particular branch of the current tree? There''s a few which involve > > > 2.6.32. > > > > xen/stable-2.6.32.x, aka the patch I pulled into the Debian kernel. > > Hmm, which is what I''m running now, suggesting that the cdab7a09 patch > is unrelated to your problem (whether its in that tree or not). I guess > it means it was unrelated to my problem too...It could be an SCI issue or maybe an x2APIC issue.. Can you provide the full serial output? Use these command line arguments: kernel /xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all sync_console console_to_ring com1=115200,8n1 console=com1 lapic=debug apic_verbosity=debug module /vmlinuz-2.6.32.9 ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen nomodeset initcall_debug debug iommu=soft swiotlb=force loglevel=10 module /initrd-2.6.32.9.img Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-10 20:32 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Wed, Mar 10, 2010 at 10:17:39AM -0800, Jeremy Fitzhardinge wrote:> On 03/10/2010 08:19 AM, Bastian Blank wrote: >>> I was having some weird issues with my network card (that I suspected >>> were interrupt related) which, I think, went away when I pulled in: >>> commit cdab7a09b1bd682c5b14effd98a6312c8b798297 > OK, I''ve merged it into xen/stable-2.6.32.x. Let me know how it goes.Nope, does not help. Bastian -- You can''t evaluate a man by logic alone. -- McCoy, "I, Mudd", stardate 4513.3 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-14 14:08 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Wed, Mar 10, 2010 at 12:19:23PM +0100, Bastian Blank wrote:> I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a > HP DL385 G6.It also happens with Xen 4.0.0-rc6. However something caught my attention.> | 5: xen-pirq-ioapic-edge ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb4 > [ 1.626062] ehci_hcd 0000:00:07.2: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5> | 14: xen-pirq-ioapic-edge sata_svw > [ 1.718903] sata_svw 0000:01:0e.0: PCI INT A -> Link[ISF0] -> GSI 14 (level, low) -> IRQ 14The interrupts are enabled as edge driven, but are reported by ACPI as level triggered. Bastian -- There are certain things men must do to remain men. -- Kirk, "The Ultimate Computer", stardate 4929.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-14 15:23 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Sun, Mar 14, 2010 at 03:08:14PM +0100, Bastian Blank wrote:> On Wed, Mar 10, 2010 at 12:19:23PM +0100, Bastian Blank wrote: > > I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a > > HP DL385 G6. > It also happens with Xen 4.0.0-rc6.Oops, I''m blind: -IOAPIC[0]: apic_id 8, version 17, address 0xfec00000, GSI 0-15 +IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0 ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[16]) -IOAPIC[1]: apic_id 9, version 17, address 0xfec01000, GSI 16-31 +IOAPIC[1]: apic_id 9, version 0, address 0xfec01000, GSI 16-16 ACPI: IOAPIC (id[0x0a] address[0xfec02000] gsi_base[32]) -IOAPIC[2]: apic_id 10, version 17, address 0xfec02000, GSI 32-47 +IOAPIC[2]: apic_id 10, version 0, address 0xfec02000, GSI 32-32 +ERROR: Unable to locate IOAPIC for GSI 2 ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) -ACPI: IRQ0 used by override. -ACPI: IRQ2 used by override. -ACPI: IRQ9 used by override. +ERROR: Unable to locate IOAPIC for GSI 9 The kernel running on Xen does not even detect the version and GSI ranges correctly. Bastian -- Knowledge, sir, should be free to all! -- Harry Mudd, "I, Mudd", stardate 4513.3 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Mar-14 15:56 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On 03/14/2010 08:23 AM, Bastian Blank wrote:> On Sun, Mar 14, 2010 at 03:08:14PM +0100, Bastian Blank wrote: > >> On Wed, Mar 10, 2010 at 12:19:23PM +0100, Bastian Blank wrote: >> >>> I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a >>> HP DL385 G6. >>> >> It also happens with Xen 4.0.0-rc6. >> > Oops, I''m blind: > > -IOAPIC[0]: apic_id 8, version 17, address 0xfec00000, GSI 0-15 > +IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0 > ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[16]) > -IOAPIC[1]: apic_id 9, version 17, address 0xfec01000, GSI 16-31 > +IOAPIC[1]: apic_id 9, version 0, address 0xfec01000, GSI 16-16 > ACPI: IOAPIC (id[0x0a] address[0xfec02000] gsi_base[32]) > -IOAPIC[2]: apic_id 10, version 17, address 0xfec02000, GSI 32-47 > +IOAPIC[2]: apic_id 10, version 0, address 0xfec02000, GSI 32-32 > +ERROR: Unable to locate IOAPIC for GSI 2 > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) > -ACPI: IRQ0 used by override. > -ACPI: IRQ2 used by override. > -ACPI: IRQ9 used by override. > +ERROR: Unable to locate IOAPIC for GSI 9 > > The kernel running on Xen does not even detect the version and GSI > ranges correctly. >That''s not necessarily a problem. The normal native IOAPIC code will try to probe for IOAPICs, but they won''t be detected because Xen owns them all. In the Xen case, it still depends on ACPI to get the proper device pin->gsi mapping, but then it just does a hypercall to bind the gsi to an event channel.> However something caught my attention. > > >> > | 5: xen-pirq-ioapic-edge ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb4 >> > [ 1.626062] ehci_hcd 0000:00:07.2: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5 >> >> > | 14: xen-pirq-ioapic-edge sata_svw >> > [ 1.718903] sata_svw 0000:01:0e.0: PCI INT A -> Link[ISF0] -> GSI 14 (level, low) -> IRQ 14 >> > The interrupts are enabled as edge driven, but are reported by ACPI as > level triggered. > >Yep, that''s going to be a problem. I guess there''s some typo in there which is mixing up level and edge in some circumstance (it can''t be global because otherwise nothing would work). It''s interesting your devices both have GSIs in the "legacy ISA" range (< 16); I wonder if something somewhere is misdescribing the interrupts. Could you post full boot logs for the kernel booting both native and under Xen to see how they differ? Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-14 16:17 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Sun, Mar 14, 2010 at 08:56:22AM -0700, Jeremy Fitzhardinge wrote:> global because otherwise nothing would work). It''s interesting your > devices both have GSIs in the "legacy ISA" range (< 16); I wonder if > something somewhere is misdescribing the interrupts.Well, they are connected to the first IO-APIC, which only serves 0-15, so they can''t be bound to other GSI. But I haven''t seem this behaviour on any other machine. Is there a standard that forbids this behaviour?> Could you post full boot logs for the kernel booting both native and > under Xen to see how they differ?Attached. Bastian -- Each kiss is as the first. -- Miramanee, Kirk''s wife, "The Paradise Syndrome", stardate 4842.6 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-14 16:41 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Sun, Mar 14, 2010 at 08:56:22AM -0700, Jeremy Fitzhardinge wrote:> It''s interesting your > devices both have GSIs in the "legacy ISA" range (< 16); I wonder if > something somewhere is misdescribing the interrupts.I found another occurance of this problem. See <87zl6klp06.fsf@frosties.localdomain>. The OP provided me with the input that the devices in question where all using interrupt 10. Bastian -- Well, Jim, I''m not much of an actor either. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhang, Xiantao
2010-Mar-15 04:30 UTC
RE: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
Could you try the following patch ? Currently, the GSI 0-15 ''s
polarity and trigger mode are determined by hypervisor, and maybe hypervisor and
dom0 has no agreement to determin them. Just follow dom0''s setting with
this patch, and I think it maybe work for you.
Xiantao
diff -r 4152a3ce90a7 xen/arch/x86/physdev.c
--- a/xen/arch/x86/physdev.c Thu Mar 11 17:40:35 2010 +0000
+++ b/xen/arch/x86/physdev.c Mon Mar 15 12:27:15 2010 +0800
@@ -477,7 +477,7 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_H
if ( setup_gsi.gsi < 0 || setup_gsi.gsi >= nr_irqs_gsi )
break;
/* GSI < 16 has been setup by hypervisor */
- if ( setup_gsi.gsi >= 16 )
+ if ( setup_gsi.gsi >= 5 )
ret = mp_register_gsi(setup_gsi.gsi, setup_gsi.triggering,
setup_gsi.polarity);
else
Bastian Blank wrote:> On Sun, Mar 14, 2010 at 08:56:22AM -0700, Jeremy Fitzhardinge wrote:
>> global because otherwise nothing would work). It''s
interesting your
>> devices both have GSIs in the "legacy ISA" range (< 16); I
wonder if
>> something somewhere is misdescribing the interrupts.
>
> Well, they are connected to the first IO-APIC, which only serves 0-15,
> so they can''t be bound to other GSI. But I haven''t seem
this
> behaviour on any other machine. Is there a standard that forbids
> this behaviour?
>> Could you post full boot logs for the kernel booting both native and
>> under Xen to see how they differ?
>
> Attached.
>
> Bastian
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-15 10:11 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Mon, Mar 15, 2010 at 12:30:32PM +0800, Zhang, Xiantao wrote:> Could you try the following patch ? Currently, the GSI 0-15 ''s polarity and trigger mode are determined by hypervisor, and maybe hypervisor and dom0 has no agreement to determin them. Just follow dom0''s setting with this patch, and I think it maybe work for you.No, it does not. mp_register_gsi also disallows reprogramming of already setup IO-APIC entries. But if I force it with the following hack, it works. So I would assume this a bug in the hypervisor to setup the GSI without knowing anything about it. Bastian diff -r 4152a3ce90a7 xen/arch/x86/mpparse.c --- a/xen/arch/x86/mpparse.c Thu Mar 11 17:40:35 2010 +0000 +++ b/xen/arch/x86/mpparse.c Mon Mar 15 11:09:27 2010 +0100 @@ -1143,5 +1143,5 @@ if ((1<<bit) & mp_ioapic_routing[ioapic].pin_programmed[idx]) { Dprintk(KERN_DEBUG "Pin %d-%d already programmed\n", mp_ioapic_routing[ioapic].apic_id, ioapic_pin); + if (mp_ioapic_routing[ioapic].apic_id == 8 && ioapic_pin == 14); else return -EEXIST; } -- What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, "Metamorphosis", stardate 3219.8 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-15 10:36 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Mon, Mar 15, 2010 at 11:11:26AM +0100, Bastian Blank wrote:> On Mon, Mar 15, 2010 at 12:30:32PM +0800, Zhang, Xiantao wrote: > > Could you try the following patch ? Currently, the GSI 0-15 ''s polarity and trigger mode are determined by hypervisor, and maybe hypervisor and dom0 has no agreement to determin them. Just follow dom0''s setting with this patch, and I think it maybe work for you. > No, it does not. mp_register_gsi also disallows reprogramming of already > setup IO-APIC entries. But if I force it with the following hack, it > works. So I would assume this a bug in the hypervisor to setup the GSI > without knowing anything about it.Or are they pre-programmed by the BIOS? IO-APIC info from Xen now: (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 0 0 0 0 0 0 0 28 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 000 00 1 0 0 0 0 0 0 38 (XEN) 06 000 00 1 0 0 0 0 0 0 40 (XEN) 07 000 00 1 0 0 0 0 0 0 48 (XEN) 08 000 00 0 0 0 0 0 0 0 50 (XEN) 09 000 00 0 0 0 0 0 0 0 58 (XEN) 0a 000 00 1 0 0 0 0 0 0 60 (XEN) 0b 000 00 1 0 0 0 0 0 0 68 (XEN) 0c 000 00 0 0 0 0 0 0 0 70 (XEN) 0d 000 00 1 0 0 0 0 0 0 78 (XEN) 0e 00A 0A 0 1 0 1 0 0 0 9A (XEN) 0f 000 00 1 0 0 0 0 0 0 90 If I read the code correctly, the 1 in the trigger line means level triggered. But the Linux kernel still lists it as edge triggered. Bastian -- "We have the right to survive!" "Not by killing others." -- Deela and Kirk, "Wink of An Eye", stardate 5710.5 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhang, Xiantao
2010-Mar-15 13:48 UTC
RE: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
With my previous patch, seems you still need to apply the following patch to
xen.git. In this way, the GSI 0-15 are still setup by hypervisor, but it also
give one chance for dom0 to re-programme its polarity and trigger mode.
Xiantao
diff --git a/arch/x86/xen/pci.c b/arch/x86/xen/pci.c
index f999ad8..409bb66 100644
--- a/arch/x86/xen/pci.c
+++ b/arch/x86/xen/pci.c
@@ -80,17 +80,6 @@ void __init xen_setup_pirqs(void)
return;
}
- /* Pre-allocate legacy irqs */
- for (irq = 0; irq < NR_IRQS_LEGACY; irq++) {
- int trigger, polarity;
-
- if (acpi_get_override_irq(irq, &trigger, &polarity) ==
-1)
- continue;
-
- xen_register_gsi(irq,
- trigger ? ACPI_LEVEL_SENSITIVE : ACPI_EDGE_SENSITIVE,
- polarity ? ACPI_ACTIVE_LOW : ACPI_ACTIVE_HIGH);
- }
}
#ifdef CONFIG_PCI_MSI
Bastian Blank wrote:> On Mon, Mar 15, 2010 at 12:30:32PM +0800, Zhang, Xiantao wrote:
>> Could you try the following patch ? Currently, the GSI 0-15
''s
>> polarity and trigger mode are determined by hypervisor, and maybe
>> hypervisor and dom0 has no agreement to determin them. Just follow
>> dom0''s setting with this patch, and I think it maybe work for
you.
>
> No, it does not. mp_register_gsi also disallows reprogramming of
> already
> setup IO-APIC entries. But if I force it with the following hack, it
> works. So I would assume this a bug in the hypervisor to setup the GSI
> without knowing anything about it.
>
> Bastian
>
> diff -r 4152a3ce90a7 xen/arch/x86/mpparse.c
> --- a/xen/arch/x86/mpparse.c Thu Mar 11 17:40:35 2010 +0000
> +++ b/xen/arch/x86/mpparse.c Mon Mar 15 11:09:27 2010 +0100
> @@ -1143,5 +1143,5 @@
> if ((1<<bit) &
mp_ioapic_routing[ioapic].pin_programmed[idx])
> { Dprintk(KERN_DEBUG "Pin %d-%d already
programmed\n",
> mp_ioapic_routing[ioapic].apic_id,
> ioapic_pin); + if (mp_ioapic_routing[ioapic].apic_id
> == 8 && ioapic_pin == 14); else return -EEXIST;
> }
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-15 14:18 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Mon, Mar 15, 2010 at 09:48:15PM +0800, Zhang, Xiantao wrote:> With my previous patch, seems you still need to apply the following patch to xen.git. In this way, the GSI 0-15 are still setup by hypervisor, but it also give one chance for dom0 to re-programme its polarity and trigger mode.But the hypervisor would ignore this gsi registrations anyway. Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhang, Xiantao
2010-Mar-15 14:38 UTC
RE: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
Bastian Blank wrote:> On Mon, Mar 15, 2010 at 09:48:15PM +0800, Zhang, Xiantao wrote: >> With my previous patch, seems you still need to apply the following >> patch to xen.git. In this way, the GSI 0-15 are still setup by >> hypervisor, but it also give one chance for dom0 to re-programme its >> polarity and trigger mode. > > But the hypervisor would ignore this gsi registrations anyway.Have you applied the hypervisor patch ? Xiantao _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-15 21:15 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Mon, Mar 15, 2010 at 09:48:15PM +0800, Zhang, Xiantao wrote:> With my previous patch, seems you still need to apply the following patch to xen.git. In this way, the GSI 0-15 are still setup by hypervisor, but it also give one chance for dom0 to re-programme its polarity and trigger mode.No, this seems to break further things. I lost access to the storage. Bastian -- "We have the right to survive!" "Not by killing others." -- Deela and Kirk, "Wink of An Eye", stardate 5710.5 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Mar-16 01:31 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Mon, Mar 15, 2010 at 10:15:00PM +0100, Bastian Blank wrote:> On Mon, Mar 15, 2010 at 09:48:15PM +0800, Zhang, Xiantao wrote: > > With my previous patch, seems you still need to apply the following patch to xen.git. In this way, the GSI 0-15 are still setup by hypervisor, but it also give one chance for dom0 to re-programme its polarity and trigger mode.Yeah, that won''t do. This way there are no irq_desc set for the rest of the devices.> > No, this seems to break further things. I lost access to the storage.The mechanism this makes this work is a bit .. unwieldy. It really looks that we initially set the IOAPIC with the wrong trigger earlier on (and Zhangs patch tries to remove that so it is on demand, but it removes the rest of your GSI entries, so that is not good). 1) Can you boot your baremetal with these options: acpi.debug_level=0xffffffff acpi.debug_layer=0x2 apic=debug 2) And then later on your Xen with these (make SURE to _not_ have apic=debug on the Linux kernel command line with Xen, it will blow): xen.gz apic=debug apic_verbosity=debug console_to_ring sync_console loglvl=all guest_loglvl=all Also you could try this patch to confirm the theory that we incorrectly get the trigger/level from the MP table early on boot (not compile tested at all): diff --git a/arch/x86/xen/pci.c b/arch/x86/xen/pci.c index f5ce35f..b775452 100644 --- a/arch/x86/xen/pci.c +++ b/arch/x86/xen/pci.c @@ -88,6 +88,9 @@ void __init xen_setup_pirqs(void) if (acpi_get_override_irq(irq, &trigger, &polarity) == -1) continue; + if (irq == 14 || irq == 5) + trigger = 0; + xen_register_gsi(irq, trigger ? ACPI_LEVEL_SENSITIVE : ACPI_EDGE_SENSITIVE, polarity ? ACPI_ACTIVE_LOW : ACPI_ACTIVE_HIGH); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-16 08:18 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Mon, Mar 15, 2010 at 09:31:14PM -0400, Konrad Rzeszutek Wilk wrote:> 1) Can you boot your baremetal with these options: > acpi.debug_level=0xffffffff acpi.debug_layer=0x2 apic=debug| IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:0 Active:0) | IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:1 Active:1)> 2) And then later on your Xen with these (make SURE to _not_ have apic=debug on > the Linux kernel command line with Xen, it will blow): > xen.gz apic=debug apic_verbosity=debug console_to_ring sync_console loglvl=all guest_loglvl=all| (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:0 Active:0) | (XEN) Pin 8-14 already programmed | (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:1 Active:1) | (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:0 Active:0) | (XEN) Pin 8-5 already programmed | (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:1 Active:1) Still with my hack to allow 8-5 and 8-14 to be reprogrammed. Bastian -- The heart is not a logical organ. -- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Mar-16 15:32 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Tue, Mar 16, 2010 at 09:18:32AM +0100, Bastian Blank wrote:> On Mon, Mar 15, 2010 at 09:31:14PM -0400, Konrad Rzeszutek Wilk wrote: > > 1) Can you boot your baremetal with these options: > > acpi.debug_level=0xffffffff acpi.debug_layer=0x2 apic=debug > > | IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:0 Active:0) > | IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:1 Active:1) > > > 2) And then later on your Xen with these (make SURE to _not_ have apic=debug on > > the Linux kernel command line with Xen, it will blow): > > xen.gz apic=debug apic_verbosity=debug console_to_ring sync_console loglvl=all guest_loglvl=all > > | (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:0 Active:0) > | (XEN) Pin 8-14 already programmed > | (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:1 Active:1) > > | (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:0 Active:0) > | (XEN) Pin 8-5 already programmed > | (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:1 Active:1) > > Still with my hack to allow 8-5 and 8-14 to be reprogrammed.I wish you had included the whole serial console for Xen boot. I am curious to at what stage the pin 14 of the IOAPIC is set. Is it set by Xen hypervisor initially (don''t think so), or is there another piece of code in the pv-ops that iterates over the 0-15 IRQs and sets them to the legacy trigger/level? When you printed out the IOAPIC information, did the Xen one (in the hypervisor, when you did apic=debug during boot) have pin 14 set to the wrong mode? Or was it later when the pv-ops kernel booted that the pin 14 was set incorrectly? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-16 18:20 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Tue, Mar 16, 2010 at 11:32:16AM -0400, Konrad Rzeszutek Wilk wrote:> I wish you had included the whole serial console for Xen boot.That was the intention but I had to run. Here is it (slightly annotated).> I am > curious to at what stage the pin 14 of the IOAPIC is set. Is it set by Xen > hypervisor initially (don''t think so),No, the entries on the first IO-APIC for the devices in question are completely bogus in the initial printout. Unmasked but edge driven.> or is there another piece of code > in the pv-ops that iterates over the 0-15 IRQs and sets them to the > legacy trigger/level?Before the initialisation of the console, the kernel seem to set pins 5 to 15 on the first IO-APIC to all edge driven.> When you printed out the IOAPIC information, did the Xen one (in the > hypervisor, when you did apic=debug during boot) have pin 14 set to the > wrong mode?Yes.> Or was it later when the pv-ops kernel booted that the pin 14 was set > incorrectly?The kernel sets it to this values again. Bastian (XEN) Xen version 4.0.0-rc6 (blank@intern.jura.uni-tuebingen.de) (gcc version 4.4.3 (Debian 4.4.3-3) ) Mon Mar 15 10:53:57 UTC 2010 (XEN) Latest ChangeSet: unavailable (XEN) Console output is synchronous. (XEN) Command line: console=com1 com1=auto dom0_mem=4096M acpi=on numa=on apic=debug apic_verbosity=debug console_to_ring sync_console loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 2 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009f400 (usable) (XEN) 000000000009f400 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000cfe3e000 (usable) (XEN) 00000000cfe3e000 - 00000000cfe46000 (ACPI data) (XEN) 00000000cfe46000 - 00000000cfe47000 (usable) (XEN) 00000000cfe47000 - 00000000e0000000 (reserved) (XEN) 00000000fec00000 - 00000000fee10000 (reserved) (XEN) 00000000ffc00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000142ffff000 (usable) (XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP ) (XEN) ACPI: XSDT CFE3EEC0, 009C (r1 HP ProLiant 2 Ò 162E) (XEN) ACPI: FACP CFE3EFC0, 00F4 (r3 HP ProLiant 2 Ò 162E) (XEN) ACPI: DSDT CFE3F0C0, 380A (r1 HP DSDT 1 INTL 20030228) (XEN) ACPI: FACS CFE3E140, 0040 (XEN) ACPI: SPCR CFE3E180, 0050 (r1 HP SPCRRBSU 1 Ò 162E) (XEN) ACPI: MCFG CFE3E200, 003C (r1 HP ProLiant 1 0) (XEN) ACPI: HPET CFE3E240, 0038 (r1 HP ProLiant 2 Ò 162E) (XEN) ACPI: SPMI CFE3E280, 0040 (r5 HP ProLiant 1 Ò 162E) (XEN) ACPI: ERST CFE3E2C0, 01D0 (r1 HP ProLiant 1 Ò 162E) (XEN) ACPI: APIC CFE3E4C0, 00CA (r1 HP ProLiant 2 0) (XEN) ACPI: SRAT CFE3E6C0, 0190 (r1 AMD FAM_F_10 2 AMD 1) (XEN) ACPI: FFFF CFE3EAC0, 0176 (r1 HP ProLiant 1 Ò 162E) (XEN) ACPI: BERT CFE3EC40, 0030 (r1 HP ProLiant 1 Ò 162E) (XEN) ACPI: HEST CFE3EC80, 018C (r1 HP ProLiant 1 Ò 162E) (XEN) ACPI: FFFF CFE3EE40, 0064 (r2 HP ProLiant 2 Ò 162E) (XEN) ACPI: SSDT CFE42900, 02F7 (r3 HP pci0pcie 1 INTL 20061109) (XEN) ACPI: SSDT CFE42C00, 0125 (r3 HP CRSPCI0 2 HP 1) (XEN) ACPI: SSDT CFE42D40, 0086 (r3 HP CRSPCI1 2 HP 1) (XEN) System RAM: 81874MB (83839812kB) (XEN) SRAT: PXM 0 -> APIC 0 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 1 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 2 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 3 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 4 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 5 -> Node 0 (XEN) SRAT: PXM 1 -> APIC 8 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 9 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 10 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 11 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 12 -> Node 1 (XEN) SRAT: PXM 1 -> APIC 13 -> Node 1 (XEN) SRAT: Node 0 PXM 0 0-a0000 (XEN) SRAT: Node 0 PXM 0 100000-d0000000 (XEN) SRAT: Node 0 PXM 0 100000000-a30000000 (XEN) SRAT: Node 1 PXM 1 a30000000-1430000000 (XEN) NUMA: Allocated memnodemap from 142ffe5000 - 142fffa000 (XEN) NUMA: Using 8 for the hash shift. (XEN) Domain heap initialised DMA width 32 bits (XEN) found SMP MP-table at 000f4f80 (XEN) DMI 2.4 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x920 (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[660,0], pm1x_evt[672,900] (XEN) ACPI: wakeup_vec[cfe3e14c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x08] enabled) (XEN) Processor #8 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x09] enabled) (XEN) Processor #9 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) Processor #2 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x0a] enabled) (XEN) Processor #10 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) (XEN) Processor #3 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x0b] enabled) (XEN) Processor #11 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) (XEN) Processor #4 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0c] enabled) (XEN) Processor #12 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled) (XEN) Processor #5 0:8 APIC version 16 (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0d] enabled) (XEN) Processor #13 0:8 APIC version 16 (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) (XEN) Overriding APIC driver with bigsmp (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 17, address 0xfec00000, GSI 0-15 (XEN) ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[16]) (XEN) IOAPIC[1]: apic_id 9, version 17, address 0xfec01000, GSI 16-31 (XEN) ACPI: IOAPIC (id[0x0a] address[0xfec02000] gsi_base[32]) (XEN) IOAPIC[2]: apic_id 10, version 17, address 0xfec02000, GSI 32-47 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Phys. Using 3 I/O APICs (XEN) ACPI: HPET id: 0x1166a201 base: 0xfed00000 (XEN) PCI: MCFG configuration 0: base d0000000 segment 0 buses 0 - 255 (XEN) PCI: MCFG area at d0000000 reserved in E820 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) mapped APIC to ffff82c3ffffe000 (fee00000) (XEN) mapped IOAPIC to ffff82c3ffffd000 (fec00000) (XEN) mapped IOAPIC to ffff82c3ffffc000 (fec01000) (XEN) mapped IOAPIC to ffff82c3ffffb000 (fec02000) (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2600.162 MHz processor. (XEN) Initing memory sharing. (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 0(6) -> Core 0 (XEN) HVM: ASIDs enabled. (XEN) HVM: SVM enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) CPU0: AMD Family10h machine check reporting enabled (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) CPU0: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Getting VERSION: 80050010 (XEN) Getting VERSION: 80050010 (XEN) Getting ID: 0 (XEN) Getting LVT0: 700 (XEN) Getting LVT1: 400 (XEN) enabled ExtINT on CPU#0 (XEN) Booting processor 1/8 eip 88000 (XEN) Initializing CPU#1 (XEN) masked ExtINT on CPU#1 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 1(6) -> Core 0 (XEN) HVM: ASIDs enabled. (XEN) CPU1: AMD Family10h machine check reporting enabled (XEN) CPU1: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 2/1 eip 88000 (XEN) Initializing CPU#2 (XEN) masked ExtINT on CPU#2 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 2(6) -> Core 1 (XEN) HVM: ASIDs enabled. (XEN) CPU2: AMD Family10h machine check reporting enabled (XEN) CPU2: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 3/9 eip 88000 (XEN) Initializing CPU#3 (XEN) masked ExtINT on CPU#3 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 3(6) -> Core 1 (XEN) HVM: ASIDs enabled. (XEN) CPU3: AMD Family10h machine check reporting enabled (XEN) CPU3: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 4/2 eip 88000 (XEN) Initializing CPU#4 (XEN) masked ExtINT on CPU#4 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 4(6) -> Core 2 (XEN) HVM: ASIDs enabled. (XEN) CPU4: AMD Family10h machine check reporting enabled (XEN) CPU4: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 5/10 eip 88000 (XEN) Initializing CPU#5 (XEN) masked ExtINT on CPU#5 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 5(6) -> Core 2 (XEN) HVM: ASIDs enabled. (XEN) CPU5: AMD Family10h machine check reporting enabled (XEN) CPU5: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 6/3 eip 88000 (XEN) Initializing CPU#6 (XEN) masked ExtINT on CPU#6 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 6(6) -> Core 3 (XEN) HVM: ASIDs enabled. (XEN) CPU6: AMD Family10h machine check reporting enabled (XEN) CPU6: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 7/11 eip 88000 (XEN) Initializing CPU#7 (XEN) masked ExtINT on CPU#7 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 7(6) -> Core 3 (XEN) HVM: ASIDs enabled. (XEN) CPU7: AMD Family10h machine check reporting enabled (XEN) CPU7: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 8/4 eip 88000 (XEN) Initializing CPU#8 (XEN) masked ExtINT on CPU#8 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 8(6) -> Core 4 (XEN) HVM: ASIDs enabled. (XEN) CPU8: AMD Family10h machine check reporting enabled (XEN) CPU8: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 9/12 eip 88000 (XEN) Initializing CPU#9 (XEN) masked ExtINT on CPU#9 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 9(6) -> Core 4 (XEN) HVM: ASIDs enabled. (XEN) CPU9: AMD Family10h machine check reporting enabled (XEN) CPU9: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 10/5 eip 88000 (XEN) Initializing CPU#10 (XEN) masked ExtINT on CPU#10 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 10(6) -> Core 5 (XEN) HVM: ASIDs enabled. (XEN) CPU10: AMD Family10h machine check reporting enabled (XEN) CPU10: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Booting processor 11/13 eip 88000 (XEN) Initializing CPU#11 (XEN) masked ExtINT on CPU#11 (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 512K (64 bytes/line) (XEN) CPU 11(6) -> Core 5 (XEN) HVM: ASIDs enabled. (XEN) CPU11: AMD Family10h machine check reporting enabled (XEN) CPU11: AMD Six-Core AMD Opteron(tm) Processor 2435 stepping 00 (XEN) Total of 12 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) init IO_APIC IRQs (XEN) IO-APIC (apicid-pin) 8-0, 9-0, 9-1, 9-2, 9-3, 9-4, 9-5, 9-6, 9-7, 9-8, 9-9, 9-10, 9-11, 9-12, 9-13, 9-14, 9-15, 10-0, 10-1, 10-2, 10-3, 10-4, 10-5, 10-6, 10-7, 10-8, 10-9, 10-10, 10-11, 10-12, 10-13, 10-14, 10-15 not connected. (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #8 registers: 16. (XEN) number of IO-APIC #9 registers: 16. (XEN) number of IO-APIC #10 registers: 16. (XEN) testing the IO APIC....................... (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 0 0 0 0 0 0 0 28 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 000 00 0 0 0 0 0 0 0 38 (XEN) 06 000 00 0 0 0 0 0 0 0 40 (XEN) 07 000 00 0 0 0 0 0 0 0 48 (XEN) 08 000 00 0 0 0 0 0 0 0 50 (XEN) 09 000 00 1 1 0 1 0 0 0 58 (XEN) 0a 000 00 0 0 0 0 0 0 0 60 (XEN) 0b 000 00 0 0 0 0 0 0 0 68 (XEN) 0c 000 00 0 0 0 0 0 0 0 70 (XEN) 0d 000 00 0 0 0 0 0 0 0 78 (XEN) 0e 000 00 0 0 0 0 0 0 0 88 (XEN) 0f 000 00 0 0 0 0 0 0 0 90 (XEN) IO APIC #9...... (XEN) .... register #00: 09000000 (XEN) ....... : physical APIC id: 09 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 09000000 (XEN) ....... : arbitration: 09 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) IO APIC #10...... (XEN) .... register #00: 0A000000 (XEN) ....... : physical APIC id: 0A (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 0A000000 (XEN) ....... : arbitration: 0A (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ40 -> 0:1 (XEN) IRQ48 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ56 -> 0:5 (XEN) IRQ64 -> 0:6 (XEN) IRQ72 -> 0:7 (XEN) IRQ80 -> 0:8 (XEN) IRQ88 -> 0:9 (XEN) IRQ96 -> 0:10 (XEN) IRQ104 -> 0:11 (XEN) IRQ112 -> 0:12 (XEN) IRQ120 -> 0:13 (XEN) IRQ136 -> 0:14 (XEN) IRQ144 -> 0:15 (XEN) .................................... done. (XEN) Using local APIC timer interrupts. (XEN) calibrating APIC timer ... (XEN) ..... CPU clock speed is 2600.1423 MHz. (XEN) ..... host bus clock speed is 200.0108 MHz. (XEN) ..... bus_scale = 0x0000CCD7 (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET ÿÿ(XEN) CPU 0 APIC 0 -> Node 0 (XEN) CPU 1 APIC 8 -> Node 1 (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) CPU 2 APIC 1 -> Node 0 (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) CPU 3 APIC 9 -> Node 1 (XEN) microcode.c:73:d32767 microcode: CPU3 resumed (XEN) CPU 4 APIC 2 -> Node 0 (XEN) microcode.c:73:d32767 microcode: CPU4 resumed (XEN) CPU 5 APIC 10 -> Node 1 (XEN) microcode.c:73:d32767 microcode: CPU5 resumed (XEN) CPU 6 APIC 3 -> Node 0 (XEN) microcode.c:73:d32767 microcode: CPU6 resumed (XEN) CPU 7 APIC 11 -> Node 1 (XEN) microcode.c:73:d32767 microcode: CPU7 resumed (XEN) CPU 8 APIC 4 -> Node 0 (XEN) microcode.c:73:d32767 microcode: CPU8 resumed (XEN) CPU 9 APIC 12 -> Node 1 (XEN) microcode.c:73:d32767 microcode: CPU9 resumed (XEN) CPU 10 APIC 5 -> Node 0 (XEN) microcode.c:73:d32767 microcode: CPU10 resumed (XEN) CPU 11 APIC 13 -> Node 1 (XEN) microcode.c:73:d32767 microcode: CPU11 resumed (XEN) Brought up 12 CPUs (XEN) HPET: 3 timers in total, 0 timers will be used for broadcast (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x429000 (XEN) elf_parse_binary: phdr: paddr=0x1429000 memsz=0xaace0 (XEN) elf_parse_binary: phdr: paddr=0x14d4000 memsz=0x888 (XEN) elf_parse_binary: phdr: paddr=0x14d5000 memsz=0x15f18 (XEN) elf_parse_binary: phdr: paddr=0x14eb000 memsz=0x1bd000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x16a8000 (XEN) elf_xen_parse_note: GUEST_OS = "linux" (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 (XEN) elf_xen_parse_note: ENTRY = 0xffffffff814eb200 (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81009000 (XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" (XEN) elf_xen_parse_note: PAE_MODE = "yes" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_parse_note: unknown xen elf note (0xd) (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1 (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff816a8000 (XEN) virt_entry = 0xffffffff814eb200 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16a8000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000a24000000->0000000a28000000 (1032192 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff816a8000 (XEN) Init. ramdisk: ffffffff816a8000->ffffffff83097200 (XEN) Phys-Mach map: ffffffff83098000->ffffffff83898000 (XEN) Start info: ffffffff83898000->ffffffff838984b4 (XEN) Page tables: ffffffff83899000->ffffffff838ba000 (XEN) Boot stack: ffffffff838ba000->ffffffff838bb000 (XEN) TOTAL: ffffffff80000000->ffffffff83c00000 (XEN) ENTRY ADDRESS: ffffffff814eb200 (XEN) Dom0 has maximum 12 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81429000 (XEN) elf_load_binary: phdr 1 at 0xffffffff81429000 -> 0xffffffff814d3ce0 (XEN) elf_load_binary: phdr 2 at 0xffffffff814d4000 -> 0xffffffff814d4888 (XEN) elf_load_binary: phdr 3 at 0xffffffff814d5000 -> 0xffffffff814eaf18 (XEN) elf_load_binary: phdr 4 at 0xffffffff814eb000 -> 0xffffffff81571000 (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) ********************************************** (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) ******* This option is intended to aid debugging of Xen by ensuring (XEN) ******* that all output is synchronously delivered on the serial line. (XEN) ******* However it can introduce SIGNIFICANT latencies and affect (XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 156kB init memory. mapping kernel into physical memory Xen: setup ISA identity maps about to get started... (XEN) mm.c:859:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry 8000000000100463 for l1e_owner=0, pg_owner=32753 (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-6 -> 0x40 -> IRQ 6 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-7 -> 0x48 -> IRQ 7 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-8 -> 0x50 -> IRQ 8 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-9 -> 0x58 -> IRQ 9 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-10 -> 0x60 -> IRQ 10 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-11 -> 0x68 -> IRQ 11 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-12 -> 0x70 -> IRQ 12 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-13 -> 0x78 -> IRQ 13 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:0 Active:0) (XEN) IOAPIC[0]: Set PCI routing entry (8-15 -> 0x90 -> IRQ 15 Mode:0 Active:0) (XEN) Pin 8-9 already programmed [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.32-4-xen-amd64 (Debian 2.6.32-10~xen.1) (waldi@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Tue Mar 16 07:46:55 UTC 2010 [ 0.000000] Command line: root=/dev/mapper/dl385--64-root64 ro console=ttyS0,115200n8 console=hvc0 acpi=on [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000009f400 (usable) [ 0.000000] Xen: 000000000009f400 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 00000000cfe3e000 (usable) [ 0.000000] Xen: 00000000cfe3e000 - 00000000cfe46000 (ACPI data) [ 0.000000] Xen: 00000000cfe46000 - 00000000cfe47000 (usable) [ 0.000000] Xen: 00000000cfe47000 - 00000000e0000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fee10000 (reserved) [ 0.000000] Xen: 00000000ffc00000 - 0000000100000000 (reserved) [ 0.000000] Malformed early option ''acpi'' [ 0.000000] DMI 2.4 present. [ 0.000000] last_pfn = 0xcfe47 max_arch_pfn = 0x400000000 [ 0.000000] init_memory_mapping: 0000000000000000-00000000cfe47000 [ 0.000000] RAMDISK: 016a8000 - 03097200 [ 0.000000] ACPI: RSDP 00000000000f4f00 00024 (v02 HP ) [ 0.000000] ACPI: XSDT 00000000cfe3eec0 0009C (v01 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: FACP 00000000cfe3efc0 000F4 (v03 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: DSDT 00000000cfe3f0c0 0380A (v01 HP DSDT 00000001 INTL 20030228) [ 0.000000] ACPI: FACS 00000000cfe3e140 00040 [ 0.000000] ACPI: SPCR 00000000cfe3e180 00050 (v01 HP SPCRRBSU 00000001 Ò? 0000162E) [ 0.000000] ACPI: MCFG 00000000cfe3e200 0003C (v01 HP ProLiant 00000001 00000000) [ 0.000000] ACPI: HPET 00000000cfe3e240 00038 (v01 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: SPMI 00000000cfe3e280 00040 (v05 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: ERST 00000000cfe3e2c0 001D0 (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: APIC 00000000cfe3e4c0 000CA (v01 HP ProLiant 00000002 00000000) [ 0.000000] ACPI: SRAT 00000000cfe3e6c0 00190 (v01 AMD FAM_F_10 00000002 AMD 00000001) [ 0.000000] ACPI: FFFF 00000000cfe3eac0 00176 (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: BERT 00000000cfe3ec40 00030 (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: HEST 00000000cfe3ec80 0018C (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: FFFF 00000000cfe3ee40 00064 (v02 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: SSDT 00000000cfe42900 002F7 (v03 HP pci0pcie 00000001 INTL 20061109) [ 0.000000] ACPI: SSDT 00000000cfe42c00 00125 (v03 HP CRSPCI0 00000002 HP 00000001) [ 0.000000] ACPI: SSDT 00000000cfe42d40 00086 (v03 HP CRSPCI1 00000002 HP 00000001) [ 0.000000] SRAT: PXM 0 -> APIC 0 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 1 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 2 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 3 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 4 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 5 -> Node 0 [ 0.000000] SRAT: PXM 1 -> APIC 8 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 9 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 10 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 11 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 12 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 13 -> Node 1 [ 0.000000] SRAT: Node 0 PXM 0 0-a0000 [ 0.000000] SRAT: Node 0 PXM 0 100000-d0000000 [ 0.000000] SRAT: Node 0 PXM 0 100000000-a30000000 [ 0.000000] SRAT: Node 1 PXM 1 a30000000-1430000000 [ 0.000000] Bootmem setup node 0 0000000000000000-00000000cfe47000 [ 0.000000] NODE_DATA [0000000000030640 - 000000000003863f] [ 0.000000] bootmap [0000000000039000 - 0000000000052fcf] pages 1a [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00cfe47000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0003899000 - 00038ba000] XEN PAGETABLES ==> [0003899000 - 00038ba000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 0001687c54] TEXT DATA BSS ==> [0001000000 - 0001687c54] [ 0.000000] #4 [00016a8000 - 0003097200] RAMDISK ==> [00016a8000 - 0003097200] [ 0.000000] #5 [0003098000 - 0003899000] XEN START INFO ==> [0003098000 - 0003899000] [ 0.000000] #6 [0001688000 - 0001688114] BRK ==> [0001688000 - 0001688114] [ 0.000000] #7 [0000100000 - 0000761000] PGTABLE ==> [0000100000 - 0000761000] [ 0.000000] #8 [0000008000 - 0000030640] MEMNODEMAP ==> [0000008000 - 0000030640] [ 0.000000] found SMP MP-table at [ffff8800000f4f80] f4f80 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000000 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00100000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[3] active PFN ranges [ 0.000000] 0: 0x00000000 -> 0x0000009f [ 0.000000] 0: 0x00000100 -> 0x000cfe3e [ 0.000000] 0: 0x000cfe46 -> 0x000cfe47 [ 0.000000] ACPI: PM-Timer IO Port: 0x920 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x08] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x09] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x0a] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x0b] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0c] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0d] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0 [ 0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[16]) [ 0.000000] IOAPIC[1]: apic_id 9, version 0, address 0xfec01000, GSI 16-16 [ 0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec02000] gsi_base[32]) [ 0.000000] IOAPIC[2]: apic_id 10, version 0, address 0xfec02000, GSI 32-32 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x1166a201 base: 0xfed00000 [ 0.000000] SMP: Allowing 12 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 00000000cfe3e000 - 00000000cfe46000 [ 0.000000] Allocating PCI resources starting at e0000000 (gap: e0000000:1ec00000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.0.0-rc6 (preserve-AD) (dom0) [ 0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:12 nr_node_ids:2 [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff8800038f0000 s89880 r8192 d20712 u118784 [ 0.000000] pcpu-alloc: s89880 r8192 d20712 u118784 alloc=29*4096 [ 0.000000] pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 [ 0.000000] pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [ 0.000000] Xen: using vcpu_info placement [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 838104 [ 0.000000] Policy zone: DMA32 [ 0.000000] Kernel command line: root=/dev/mapper/dl385--64-root64 ro console=ttyS0,115200n8 console=hvc0 acpi=on [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Initializing CPU#0 [ 0.000000] DMA: Placing 64MB software IO TLB between ffff880006a54000 - ffff88000aa54000 [ 0.000000] DMA: software IO TLB at phys 0x6a54000 - 0xaa54000 [ 0.000000] xen_swiotlb_fixup: buf=ffff880006a54000 size=67108864 [ 0.000000] xen_swiotlb_fixup: buf=ffff88000aab4000 size=32768 [ 0.000000] Memory: 3243056k/3406108k available (3081k kernel code, 420k absent, 162632k reserved, 1861k data, 588k init) [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=2 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:4352 nr_irqs:3072 [ 0.000000] Already setup the GSI :0 [ 0.000000] Already setup the GSI :1 [ 0.000000] Already setup the GSI :2 [ 0.000000] Already setup the GSI :3 [ 0.000000] Already setup the GSI :4 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.000000] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=3 [ 0.000000] xen_allocate_pirq: returning irq 9 for gsi 9 [ 0.000000] Already setup the GSI :9 [ 0.000000] xen: acpi sci 9 [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [hvc0] enabled [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.32-4-xen-amd64 (Debian 2.6.32-10~xen.1) (waldi@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Tue Mar 16 07:46:55 UTC 2010 [ 0.000000] Command line: root=/dev/mapper/dl385--64-root64 ro console=ttyS0,115200n8 console=hvc0 acpi=on [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000009f400 (usable) [ 0.000000] Xen: 000000000009f400 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 00000000cfe3e000 (usable) [ 0.000000] Xen: 00000000cfe3e000 - 00000000cfe46000 (ACPI data) [ 0.000000] Xen: 00000000cfe46000 - 00000000cfe47000 (usable) [ 0.000000] Xen: 00000000cfe47000 - 00000000e0000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fee10000 (reserved) [ 0.000000] Xen: 00000000ffc00000 - 0000000100000000 (reserved) [ 0.000000] Malformed early option ''acpi'' [ 0.000000] DMI 2.4 present. [ 0.000000] last_pfn = 0xcfe47 max_arch_pfn = 0x400000000 [ 0.000000] init_memory_mapping: 0000000000000000-00000000cfe47000 [ 0.000000] RAMDISK: 016a8000 - 03097200 [ 0.000000] ACPI: RSDP 00000000000f4f00 00024 (v02 HP ) [ 0.000000] ACPI: XSDT 00000000cfe3eec0 0009C (v01 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: FACP 00000000cfe3efc0 000F4 (v03 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: DSDT 00000000cfe3f0c0 0380A (v01 HP DSDT 00000001 INTL 20030228) [ 0.000000] ACPI: FACS 00000000cfe3e140 00040 [ 0.000000] ACPI: SPCR 00000000cfe3e180 00050 (v01 HP SPCRRBSU 00000001 Ò? 0000162E) [ 0.000000] ACPI: MCFG 00000000cfe3e200 0003C (v01 HP ProLiant 00000001 00000000) [ 0.000000] ACPI: HPET 00000000cfe3e240 00038 (v01 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: SPMI 00000000cfe3e280 00040 (v05 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: ERST 00000000cfe3e2c0 001D0 (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: APIC 00000000cfe3e4c0 000CA (v01 HP ProLiant 00000002 00000000) [ 0.000000] ACPI: SRAT 00000000cfe3e6c0 00190 (v01 AMD FAM_F_10 00000002 AMD 00000001) [ 0.000000] ACPI: FFFF 00000000cfe3eac0 00176 (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: BERT 00000000cfe3ec40 00030 (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: HEST 00000000cfe3ec80 0018C (v01 HP ProLiant 00000001 Ò? 0000162E) [ 0.000000] ACPI: FFFF 00000000cfe3ee40 00064 (v02 HP ProLiant 00000002 Ò? 0000162E) [ 0.000000] ACPI: SSDT 00000000cfe42900 002F7 (v03 HP pci0pcie 00000001 INTL 20061109) [ 0.000000] ACPI: SSDT 00000000cfe42c00 00125 (v03 HP CRSPCI0 00000002 HP 00000001) [ 0.000000] ACPI: SSDT 00000000cfe42d40 00086 (v03 HP CRSPCI1 00000002 HP 00000001) [ 0.000000] SRAT: PXM 0 -> APIC 0 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 1 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 2 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 3 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 4 -> Node 0 [ 0.000000] SRAT: PXM 0 -> APIC 5 -> Node 0 [ 0.000000] SRAT: PXM 1 -> APIC 8 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 9 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 10 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 11 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 12 -> Node 1 [ 0.000000] SRAT: PXM 1 -> APIC 13 -> Node 1 [ 0.000000] SRAT: Node 0 PXM 0 0-a0000 [ 0.000000] SRAT: Node 0 PXM 0 100000-d0000000 [ 0.000000] SRAT: Node 0 PXM 0 100000000-a30000000 [ 0.000000] SRAT: Node 1 PXM 1 a30000000-1430000000 [ 0.000000] Bootmem setup node 0 0000000000000000-00000000cfe47000 [ 0.000000] NODE_DATA [0000000000030640 - 000000000003863f] [ 0.000000] bootmap [0000000000039000 - 0000000000052fcf] pages 1a [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00cfe47000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [0003899000 - 00038ba000] XEN PAGETABLES ==> [0003899000 - 00038ba000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 0001687c54] TEXT DATA BSS ==> [0001000000 - 0001687c54] [ 0.000000] #4 [00016a8000 - 0003097200] RAMDISK ==> [00016a8000 - 0003097200] [ 0.000000] #5 [0003098000 - 0003899000] XEN START INFO ==> [0003098000 - 0003899000] [ 0.000000] #6 [0001688000 - 0001688114] BRK ==> [0001688000 - 0001688114] [ 0.000000] #7 [0000100000 - 0000761000] PGTABLE ==> [0000100000 - 0000761000] [ 0.000000] #8 [0000008000 - 0000030640] MEMNODEMAP ==> [0000008000 - 0000030640] [ 0.000000] found SMP MP-table at [ffff8800000f4f80] f4f80 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000000 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00100000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[3] active PFN ranges [ 0.000000] 0: 0x00000000 -> 0x0000009f [ 0.000000] 0: 0x00000100 -> 0x000cfe3e [ 0.000000] 0: 0x000cfe46 -> 0x000cfe47 [ 0.000000] ACPI: PM-Timer IO Port: 0x920 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x08] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x09] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x0a] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x0b] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0c] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0d] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-0 [ 0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[16]) [ 0.000000] IOAPIC[1]: apic_id 9, version 0, address 0xfec01000, GSI 16-16 [ 0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec02000] gsi_base[32]) [ 0.000000] IOAPIC[2]: apic_id 10, version 0, address 0xfec02000, GSI 32-32 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x1166a201 base: 0xfed00000 [ 0.000000] SMP: Allowing 12 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 00000000cfe3e000 - 00000000cfe46000 [ 0.000000] Allocating PCI resources starting at e0000000 (gap: e0000000:1ec00000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.0.0-rc6 (preserve-AD) (dom0) [ 0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:12 nr_node_ids:2 [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff8800038f0000 s89880 r8192 d20712 u118784 [ 0.000000] pcpu-alloc: s89880 r8192 d20712 u118784 alloc=29*4096 [ 0.000000] pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 [ 0.000000] pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [ 0.000000] Xen: using vcpu_info placement [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 838104 [ 0.000000] Policy zone: DMA32 [ 0.000000] Kernel command line: root=/dev/mapper/dl385--64-root64 ro console=ttyS0,115200n8 console=hvc0 acpi=on [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Initializing CPU#0 [ 0.000000] DMA: Placing 64MB software IO TLB between ffff880006a54000 - ffff88000aa54000 [ 0.000000] DMA: software IO TLB at phys 0x6a54000 - 0xaa54000 [ 0.000000] xen_swiotlb_fixup: buf=ffff880006a54000 size=67108864 [ 0.000000] xen_swiotlb_fixup: buf=ffff88000aab4000 size=32768 [ 0.000000] Memory: 3243056k/3406108k available (3081k kernel code, 420k absent, 162632k reserved, 1861k data, 588k init) [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=2 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:4352 nr_irqs:3072 [ 0.000000] Already setup the GSI :0 [ 0.000000] Already setup the GSI :1 [ 0.000000] Already setup the GSI :2 [ 0.000000] Already setup the GSI :3 [ 0.000000] Already setup the GSI :4 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [ 0.000000] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=3 [ 0.000000] xen_allocate_pirq: returning irq 9 for gsi 9 [ 0.000000] Already setup the GSI :9 [ 0.000000] xen: acpi sci 9 [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [hvc0] enabled [ 0.000000] console [ttyS0] enabled [ 0.000000] installing Xen timer for CPU 0 (XEN) traps.c:2309:d0 Domain attempted WRMSR 00000000c0010004 from 00004031:073a4256 to 00000000:00000000. [ 0.000000] Detected 3173557.071 MHz processor. [ 0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 5200.32 BogoMIPS (lpj=10400648) [ 0.004032] Security Framework initialized [ 0.008000] SELinux: Disabled at boot. [ 0.008828] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.012411] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.016018] Mount-cache hash table entries: 256 [ 0.017838] Initializing cgroup subsys ns [ 0.020000] Initializing cgroup subsys cpuacct [ 0.020000] Initializing cgroup subsys devices [ 0.020000] Initializing cgroup subsys freezer [ 0.020000] Initializing cgroup subsys net_cls [ 0.020022] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.024004] CPU: L2 Cache: 512K (64 bytes/line) [ 0.028001] CPU 0/0x0 -> Node 0 [ 0.028012] CPU: Physical Processor ID: 0 [ 0.032001] CPU: Processor Core ID: 0 [ 0.032005] Performance Events: AMD PMU driver. [ 0.033574] ------------[ cut here ]------------ [ 0.036001] WARNING: at /home/blank/debian/kernel/dists/sid/linux-2.6/debian/build/source_amd64_xen/arch/x86/xen/enlighten.c:722 init_hw_perf_events+0x2fe/0x39e() [ 0.036001] Hardware name: ProLiant DL385 G6 [ 0.036001] Modules linked in: [ 0.036001] Pid: 0, comm: swapper Not tainted 2.6.32-4-xen-amd64 #1 [ 0.036001] Call Trace: [ 0.036001] [<ffffffff814f282d>] ? init_hw_perf_events+0x2fe/0x39e [ 0.036001] [<ffffffff814f282d>] ? init_hw_perf_events+0x2fe/0x39e [ 0.036001] [<ffffffff8104fb84>] ? warn_slowpath_common+0x77/0xa3 [ 0.036001] [<ffffffff814f282d>] ? init_hw_perf_events+0x2fe/0x39e [ 0.036001] [<ffffffff812f6e4a>] ? identify_cpu+0x2ff/0x308 [ 0.036001] [<ffffffff8100e9ef>] ? xen_restore_fl_direct_end+0x0/0x1 [ 0.036001] [<ffffffff810e7c96>] ? kmem_cache_alloc+0x8c/0xf0 [ 0.036001] [<ffffffff814f2483>] ? identify_boot_cpu+0x15/0x3e [ 0.036001] [<ffffffff814f250a>] ? check_bugs+0x9/0x2e [ 0.036001] [<ffffffff814ebcc8>] ? start_kernel+0x3c1/0x3dc [ 0.036001] [<ffffffff814edac6>] ? xen_start_kernel+0x63f/0x645 [ 0.036001] ---[ end trace a7919e7f17c0a725 ]--- [ 0.036001] ... version: 0 [ 0.036001] ... bit width: 48 [ 0.036001] ... generic registers: 4 [ 0.036001] ... value mask: 0000ffffffffffff [ 0.036001] ... max period: 00007fffffffffff [ 0.036001] ... fixed-purpose events: 0 [ 0.036001] ... event mask: 000000000000000f [ 0.036001] SMP alternatives: switching to UP code [ 0.036001] ACPI: Core revision 20090903 [ 0.044354] installing Xen timer for CPU 1 [ 0.048052] SMP alternatives: switching to SMP code [ 0.000053] Initializing CPU#1 [ 0.000200] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000209] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000216] CPU 1/0x0 -> Node 0 [ 0.000223] CPU: Physical Processor ID: 1 [ 0.000228] CPU: Processor Core ID: 0 [ 0.052408] installing Xen timer for CPU 2 [ 0.000038] Initializing CPU#2 [ 0.000158] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000167] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000174] CPU 2/0x0 -> Node 0 [ 0.000181] CPU: Physical Processor ID: 0 [ 0.000185] CPU: Processor Core ID: 1 [ 0.056457] installing Xen timer for CPU 3 [ 0.000043] Initializing CPU#3 [ 0.000164] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000173] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000180] CPU 3/0x0 -> Node 0 [ 0.000187] CPU: Physical Processor ID: 1 [ 0.000191] CPU: Processor Core ID: 1 [ 0.060400] installing Xen timer for CPU 4 [ 0.000037] Initializing CPU#4 [ 0.000152] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000161] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000167] CPU 4/0x0 -> Node 0 [ 0.000174] CPU: Physical Processor ID: 0 [ 0.000179] CPU: Processor Core ID: 2 [ 0.064432] installing Xen timer for CPU 5 [ 0.000038] Initializing CPU#5 [ 0.000158] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000167] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000173] CPU 5/0x0 -> Node 0 [ 0.000180] CPU: Physical Processor ID: 1 [ 0.000185] CPU: Processor Core ID: 2 [ 0.068392] installing Xen timer for CPU 6 [ 0.000036] Initializing CPU#6 [ 0.000150] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000158] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000165] CPU 6/0x0 -> Node 0 [ 0.000172] CPU: Physical Processor ID: 0 [ 0.000177] CPU: Processor Core ID: 3 [ 0.072451] installing Xen timer for CPU 7 [ 0.000043] Initializing CPU#7 [ 0.000162] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000171] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000178] CPU 7/0x0 -> Node 0 [ 0.000185] CPU: Physical Processor ID: 1 [ 0.000190] CPU: Processor Core ID: 3 [ 0.076410] installing Xen timer for CPU 8 [ 0.000037] Initializing CPU#8 [ 0.000150] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000159] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000166] CPU 8/0x0 -> Node 0 [ 0.000172] CPU: Physical Processor ID: 0 [ 0.000177] CPU: Processor Core ID: 4 [ 0.080439] installing Xen timer for CPU 9 [ 0.000055] Initializing CPU#9 [ 0.000175] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000184] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000191] CPU 9/0x0 -> Node 0 [ 0.000197] CPU: Physical Processor ID: 1 [ 0.000202] CPU: Processor Core ID: 4 [ 0.084430] installing Xen timer for CPU 10 [ 0.000037] Initializing CPU#10 [ 0.000150] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000159] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000166] CPU 10/0x0 -> Node 0 [ 0.000173] CPU: Physical Processor ID: 0 [ 0.000177] CPU: Processor Core ID: 5 [ 0.088455] installing Xen timer for CPU 11 [ 0.000043] Initializing CPU#11 [ 0.000162] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.000171] CPU: L2 Cache: 512K (64 bytes/line) [ 0.000178] CPU 11/0x0 -> Node 0 [ 0.000185] CPU: Physical Processor ID: 1 [ 0.000189] CPU: Processor Core ID: 5 [ 0.092355] Brought up 12 CPUs [ 0.096624] devtmpfs: initialized [ 0.103029] Grant table initialized [ 0.104001] regulator: core version 0.5 [ 0.104052] NET: Registered protocol family 16 [ 0.105673] xenbus_probe_init ok [ 0.108044] TOM: 00000000d0000000 aka 3328M [ 0.109575] TOM2: 0000001430000000 aka 82688M [ 0.112420] ACPI: bus type pci registered [ 0.116001] PCI: MCFG configuration 0: base d0000000 segment 0 buses 0 - 255 [ 0.116001] PCI: MCFG area at d0000000 reserved in E820 [ 0.161583] PCI: Using MMCONFIG at d0000000 - dfffffff [ 0.164001] PCI: Using configuration type 1 for base access [ 0.164797] bio: create slab <bio-0> at 0 [ 0.169203] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.175194] ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits) (20090903/dsopcode-596) [ 0.176001] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_._OSC] (Node ffff8800cf8376c0), AE_AML_BUFFER_LIMIT [ 0.178863] ACPI: Interpreter enabled [ 0.180001] ACPI: (supports S0 S4 S5) [ 0.180001] ACPI: Using IOAPIC for interrupt routing [ 0.190573] ACPI: No dock devices found. [ 0.192020] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 0.196297] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold [ 0.200001] pci 0000:00:04.0: PME# disabled [ 0.200149] pci 0000:00:04.2: PME# supported from D0 D3hot D3cold [ 0.204001] pci 0000:00:04.2: PME# disabled [ 0.204132] pci 0000:00:04.4: PME# supported from D0 D3hot D3cold [ 0.208001] pci 0000:00:04.4: PME# disabled [ 0.208123] pci 0000:00:04.6: PME# supported from D0 D3hot D3cold [ 0.212001] pci 0000:00:04.6: PME# disabled [ 0.212086] pci 0000:00:05.0: Enabling HT MSI Mapping [ 0.216558] pci 0000:00:07.2: PME# supported from D0 D1 D2 D3hot [ 0.219606] pci 0000:00:07.2: PME# disabled [ 0.220103] pci 0000:00:0f.0: PME# supported from D0 D3hot D3cold [ 0.224001] pci 0000:00:0f.0: PME# disabled [ 0.224076] pci 0000:00:10.0: PME# supported from D0 D3hot D3cold [ 0.228001] pci 0000:00:10.0: PME# disabled [ 0.228075] pci 0000:00:11.0: PME# supported from D0 D3hot D3cold [ 0.232001] pci 0000:00:11.0: PME# disabled [ 0.232076] pci 0000:00:12.0: PME# supported from D0 D3hot D3cold [ 0.236001] pci 0000:00:12.0: PME# disabled [ 0.236074] pci 0000:00:13.0: PME# supported from D0 D3hot D3cold [ 0.240001] pci 0000:00:13.0: PME# disabled [ 0.241287] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold [ 0.244001] pci 0000:03:00.0: PME# disabled [ 0.244154] pci 0000:03:00.1: PME# supported from D0 D3hot D3cold [ 0.246741] pci 0000:03:00.1: PME# disabled (XEN) PCI add device 00:03.0 (XEN) PCI add device 00:04.0 (XEN) PCI add device 00:04.2 (XEN) PCI add device 00:04.4 (XEN) PCI add device 00:04.6 (XEN) PCI add device 00:05.0 (XEN) PCI add device 00:06.0 (XEN) PCI add device 00:06.2 (XEN) PCI add device 00:07.0 (XEN) PCI add device 00:07.1 (XEN) PCI add device 00:07.2 (XEN) PCI add device 00:0f.0 (XEN) PCI add device 00:10.0 (XEN) PCI add device 00:11.0 (XEN) PCI add device 00:12.0 (XEN) PCI add device 00:13.0 (XEN) PCI add device 00:18.0 (XEN) PCI add device 00:18.1 (XEN) PCI add device 00:18.2 (XEN) PCI add device 00:18.3 (XEN) PCI add device 00:18.4 (XEN) PCI add device 00:19.0 (XEN) PCI add device 00:19.1 (XEN) PCI add device 00:19.2 (XEN) PCI add device 00:19.3 (XEN) PCI add device 00:19.4 (XEN) PCI add device 01:0d.0 (XEN) PCI add device 01:0e.0 (XEN) PCI add device 03:00.0 (XEN) PCI add device 03:00.1 [ 0.309146] ACPI: PCI Root Bridge [PCI1] (0000:40) [ 0.311930] pci 0000:40:0f.0: PME# supported from D0 D3hot D3cold [ 0.312001] pci 0000:40:0f.0: PME# disabled [ 0.312211] pci 0000:40:10.0: PME# supported from D0 D3hot D3cold [ 0.314606] pci 0000:40:10.0: PME# disabled [ 0.316215] pci 0000:40:11.0: PME# supported from D0 D3hot D3cold [ 0.318609] pci 0000:40:11.0: PME# disabled [ 0.320209] pci 0000:40:12.0: PME# supported from D0 D3hot D3cold [ 0.322530] pci 0000:40:12.0: PME# disabled [ 0.324214] pci 0000:40:13.0: PME# supported from D0 D3hot D3cold [ 0.326584] pci 0000:40:13.0: PME# disabled [ 0.328746] pci 0000:48:00.0: PME# supported from D0 [ 0.332001] pci 0000:48:00.0: PME# disabled [ 0.332782] pci 0000:41:00.0: PME# supported from D0 D3hot D3cold [ 0.336001] pci 0000:41:00.0: PME# disabled [ 0.336357] pci 0000:41:00.1: PME# supported from D0 D3hot D3cold [ 0.339370] pci 0000:41:00.1: PME# disabled (XEN) PCI add device 40:0f.0 (XEN) PCI add device 40:10.0 (XEN) PCI add device 40:11.0 (XEN) PCI add device 40:12.0 (XEN) PCI add device 40:13.0 (XEN) PCI add device 48:00.0 (XEN) PCI add device 41:00.0 (XEN) PCI add device 41:00.1 [ 0.363393] ACPI: PCI Interrupt Link [IUSB] (IRQs *5) [ 0.364375] ACPI: PCI Interrupt Link [ISF0] (IRQs *14) [ 0.366763] ACPI: PCI Interrupt Link [IN00] (IRQs 7 10 11) *0, disabled. [ 0.368366] ACPI: PCI Interrupt Link [IN01] (IRQs 7 10 11) *0, disabled. [ 0.372367] ACPI: PCI Interrupt Link [IN02] (IRQs 7 10 11) *0, disabled. [ 0.375255] ACPI: PCI Interrupt Link [IN03] (IRQs 7 10 11) *0, disabled. [ 0.376369] ACPI: PCI Interrupt Link [IN04] (IRQs 7 10 11) *0, disabled. [ 0.380136] ACPI: PCI Interrupt Link [IN05] (IRQs 7 10 11) *0, disabled. [ 0.384141] ACPI: PCI Interrupt Link [IN06] (IRQs 7 10 11) *0, disabled. [ 0.388137] ACPI: PCI Interrupt Link [IN07] (IRQs 7 10 11) *0, disabled. [ 0.392136] ACPI: PCI Interrupt Link [IN08] (IRQs 7 10 11) *0, disabled. [ 0.396136] ACPI: PCI Interrupt Link [IN09] (IRQs 7 10 11) *0, disabled. [ 0.400136] ACPI: PCI Interrupt Link [IN10] (IRQs 7 10 11) *0, disabled. [ 0.404136] ACPI: PCI Interrupt Link [IN11] (IRQs 7 10 11) *0, disabled. [ 0.408135] ACPI: PCI Interrupt Link [IN12] (IRQs 7 10 11) *0, disabled. [ 0.412136] ACPI: PCI Interrupt Link [IN13] (IRQs 7 10 11) *0, disabled. [ 0.416137] ACPI: PCI Interrupt Link [IN14] (IRQs 7 10 11) *0, disabled. [ 0.420146] ACPI: PCI Interrupt Link [IN15] (IRQs 7 10 11) *0, disabled. [ 0.424152] ACPI: PCI Interrupt Link [IN16] (IRQs 7 10 *11) [ 0.428140] ACPI: PCI Interrupt Link [IN17] (IRQs 7 10 *11) [ 0.432137] ACPI: PCI Interrupt Link [IN18] (IRQs 7 10 *11) [ 0.436137] ACPI: PCI Interrupt Link [IN19] (IRQs 7 10 *11) [ 0.440141] ACPI: PCI Interrupt Link [IN20] (IRQs 7 10 *11) [ 0.444136] ACPI: PCI Interrupt Link [IN21] (IRQs 7 10 11) *0, disabled. [ 0.448136] ACPI: PCI Interrupt Link [IN22] (IRQs 7 *10 11) [ 0.452138] ACPI: PCI Interrupt Link [IN23] (IRQs *7 10 11) [ 0.456136] ACPI: PCI Interrupt Link [IN24] (IRQs 7 10 *11) [ 0.460137] ACPI: PCI Interrupt Link [IN25] (IRQs 7 10 *11) [ 0.464136] ACPI: PCI Interrupt Link [IN26] (IRQs 7 10 *11) [ 0.468140] ACPI: PCI Interrupt Link [IN27] (IRQs 7 10 11) *0, disabled. [ 0.472140] ACPI: PCI Interrupt Link [IN28] (IRQs *7 10 11) [ 0.476136] ACPI: PCI Interrupt Link [IN29] (IRQs 7 10 *11) [ 0.480137] ACPI: PCI Interrupt Link [IN30] (IRQs 7 *10 11) [ 0.484137] ACPI: PCI Interrupt Link [IN31] (IRQs 7 10 11) *0, disabled. [ 0.488073] xenbus_probe_backend_init bus registered ok [ 0.489995] xenbus_probe_frontend_init bus registered ok [ 0.492001] xen_balloon: Initialising balloon driver with page order 0. [ 0.492072] vgaarb: device added: PCI:0000:00:03.0,decodes=io+mem,owns=io+mem,locks=none [ 0.496001] vgaarb: loaded [ 0.496084] PCI: Using ACPI for IRQ routing [ 0.500429] Switching to clocksource xen [ 0.506057] pnp: PnP ACPI init [ 0.513881] ACPI: bus type pnp registered [ 0.522119] xen_allocate_pirq: returning irq 1 for gsi 1 [ 0.537648] Already setup the GSI :1 [ 0.541057] xen_allocate_pirq: returning irq 12 for gsi 12 (XEN) Pin 8-12 already programmed [ 0.554843] Already setup the GSI :12 [ 0.556814] xen_allocate_pirq: returning irq 3 for gsi 3 [ 0.566619] Already setup the GSI :3 [ 0.574873] pnp: PnP ACPI: found 12 devices [ 0.588667] ACPI: ACPI bus type pnp unregistered [ 0.600537] system 00:01: ioport range 0x408-0x40f has been reserved [ 0.604529] system 00:01: ioport range 0x4d0-0x4d1 has been reserved [ 0.604529] system 00:01: ioport range 0x4d6-0x4d6 has been reserved [ 0.604529] system 00:01: ioport range 0x310-0x311 has been reserved [ 0.604529] system 00:01: ioport range 0x900-0x9fe has been reserved [ 0.604529] system 00:01: ioport range 0xc80-0xc83 has been reserved [ 0.604529] system 00:01: ioport range 0xcd4-0xcd7 has been reserved [ 0.604529] system 00:01: ioport range 0xf50-0xf58 has been reserved [ 0.604529] system 00:01: ioport range 0x520-0x520 has been reserved [ 0.604529] system 00:01: ioport range 0x580-0x59f has been reserved [ 0.604529] system 00:01: ioport range 0x700-0x703 has been reserved [ 0.604529] system 00:01: ioport range 0xc06-0xc07 has been reserved [ 0.604529] system 00:01: ioport range 0xc14-0xc14 has been reserved [ 0.604529] system 00:01: ioport range 0xc4a-0xc4a has been reserved [ 0.604529] system 00:01: ioport range 0xc50-0xc52 has been reserved [ 0.604529] system 00:01: ioport range 0xc6c-0xc6c has been reserved [ 0.604529] system 00:01: ioport range 0xc6f-0xc6f has been reserved [ 0.604529] system 00:01: ioport range 0xca0-0xca1 has been reserved [ 0.604529] system 00:01: ioport range 0xca4-0xca5 has been reserved [ 0.604529] system 00:01: ioport range 0x3f8-0x3ff has been reserved [ 0.604529] system 00:01: iomem range 0xd0000000-0xdfffffff has been reserved [ 0.825235] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 0.828007] pci 0000:01:0d.0: PCI bridge, secondary bus 0000:02 [ 0.828007] pci 0000:01:0d.0: IO window: disabled [ 0.828007] pci 0000:01:0d.0: MEM window: disabled [ 0.828007] pci 0000:01:0d.0: PREFETCH window: disabled [ 0.828007] pci 0000:00:05.0: PCI bridge, secondary bus 0000:01 [ 0.828007] pci 0000:00:05.0: IO window: 0x4000-0x4fff [ 0.828007] pci 0000:00:05.0: MEM window: 0xf3f00000-0xf3ffffff [ 0.828007] pci 0000:00:05.0: PREFETCH window: 0xe0000000-0xe00fffff [ 0.828007] pci 0000:00:0f.0: PCI bridge, secondary bus 0000:04 [ 0.828007] pci 0000:00:0f.0: IO window: disabled [ 0.828007] pci 0000:00:0f.0: MEM window: disabled [ 0.828007] pci 0000:00:0f.0: PREFETCH window: disabled [ 0.828007] pci 0000:00:10.0: PCI bridge, secondary bus 0000:07 [ 0.828007] pci 0000:00:10.0: IO window: disabled [ 0.828007] pci 0000:00:10.0: MEM window: disabled [ 0.828007] pci 0000:00:10.0: PREFETCH window: disabled [ 0.828007] pci 0000:00:11.0: PCI bridge, secondary bus 0000:0a [ 0.828007] pci 0000:00:11.0: IO window: disabled [ 0.828007] pci 0000:00:11.0: MEM window: disabled [ 0.828007] pci 0000:00:11.0: PREFETCH window: disabled [ 0.828007] pci 0000:00:12.0: PCI bridge, secondary bus 0000:03 [ 0.828007] pci 0000:00:12.0: IO window: disabled [ 0.828007] pci 0000:00:12.0: MEM window: 0xf4000000-0xf7ffffff [ 0.828007] pci 0000:00:12.0: PREFETCH window: 0xe0100000-0xe01fffff [ 0.828007] pci 0000:00:13.0: PCI bridge, secondary bus 0000:0d [ 0.828007] pci 0000:00:13.0: IO window: disabled [ 0.828007] pci 0000:00:13.0: MEM window: disabled [ 0.828007] pci 0000:00:13.0: PREFETCH window: disabled (XEN) IOAPIC[2]: Set PCI routing entry (10-10 -> 0x98 -> IRQ 42 Mode:1 Active:1) [ 0.947397] pci 0000:00:0f.0: PCI INT A -> GSI 42 (level, low) -> IRQ 42 (XEN) IOAPIC[2]: Set PCI routing entry (10-6 -> 0xa0 -> IRQ 38 Mode:1 Active:1) [ 0.953084] pci 0000:00:10.0: PCI INT A -> GSI 38 (level, low) -> IRQ 38 (XEN) IOAPIC[2]: Set PCI routing entry (10-7 -> 0xa8 -> IRQ 39 Mode:1 Active:1) [ 0.958355] pci 0000:00:11.0: PCI INT A -> GSI 39 (level, low) -> IRQ 39 (XEN) IOAPIC[2]: Set PCI routing entry (10-8 -> 0xb0 -> IRQ 40 Mode:1 Active:1) [ 0.963448] pci 0000:00:12.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40 (XEN) IOAPIC[2]: Set PCI routing entry (10-9 -> 0xb8 -> IRQ 41 Mode:1 Active:1) [ 0.968703] pci 0000:00:13.0: PCI INT A -> GSI 41 (level, low) -> IRQ 41 [ 0.971276] pci 0000:40:0f.0: PCI bridge, secondary bus 0000:42 [ 0.972692] pci 0000:40:0f.0: IO window: disabled [ 0.972692] pci 0000:40:0f.0: MEM window: disabled [ 0.972692] pci 0000:40:0f.0: PREFETCH window: disabled [ 0.972692] pci 0000:40:10.0: PCI bridge, secondary bus 0000:45 [ 0.972692] pci 0000:40:10.0: IO window: disabled [ 0.972692] pci 0000:40:10.0: MEM window: disabled [ 0.972692] pci 0000:40:10.0: PREFETCH window: disabled [ 0.972692] pci 0000:40:11.0: PCI bridge, secondary bus 0000:48 [ 0.972692] pci 0000:40:11.0: IO window: 0x5000-0x5fff [ 0.972692] pci 0000:40:11.0: MEM window: 0xfdb00000-0xfdffffff [ 0.972692] pci 0000:40:11.0: PREFETCH window: 0xfc000000-0xfc0fffff [ 0.972692] pci 0000:40:12.0: PCI bridge, secondary bus 0000:41 [ 0.972692] pci 0000:40:12.0: IO window: disabled [ 0.972692] pci 0000:40:12.0: MEM window: 0xf8000000-0xfbffffff [ 0.972692] pci 0000:40:12.0: PREFETCH window: 0xfc100000-0xfc1fffff [ 0.972692] pci 0000:40:13.0: PCI bridge, secondary bus 0000:4b [ 0.972692] pci 0000:40:13.0: IO window: disabled [ 0.972692] pci 0000:40:13.0: MEM window: disabled [ 0.972692] pci 0000:40:13.0: PREFETCH window: disabled (XEN) IOAPIC[2]: Set PCI routing entry (10-4 -> 0xc0 -> IRQ 36 Mode:1 Active:1) [ 1.073083] pci 0000:40:0f.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 (XEN) IOAPIC[2]: Set PCI routing entry (10-0 -> 0xc8 -> IRQ 32 Mode:1 Active:1) [ 1.090171] pci 0000:40:10.0: PCI INT A -> GSI 32 (level, low) -> IRQ 32 (XEN) IOAPIC[2]: Set PCI routing entry (10-1 -> 0xd0 -> IRQ 33 Mode:1 Active:1) [ 1.125489] pci 0000:40:11.0: PCI INT A -> GSI 33 (level, low) -> IRQ 33 (XEN) IOAPIC[2]: Set PCI routing entry (10-2 -> 0xd8 -> IRQ 34 Mode:1 Active:1) [ 1.158421] pci 0000:40:12.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34 (XEN) IOAPIC[2]: Set PCI routing entry (10-3 -> 0x21 -> IRQ 35 Mode:1 Active:1) [ 1.200359] pci 0000:40:13.0: PCI INT A -> GSI 35 (level, low) -> IRQ 35 [ 1.210947] NET: Registered protocol family 2 [ 1.229884] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 1.247669] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 1.265145] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 1.268985] TCP: Hash tables configured (established 524288 bind 65536) [ 1.268985] TCP reno registered [ 1.313645] NET: Registered protocol family 1 [ 1.331718] pci 0000:00:04.4: HCRESET not completed yet! [ 1.347648] pci 0000:00:06.0: disabled boot interrupts on device [1166:0205] [ 1.388208] Unpacking initramfs... [ 1.439010] Freeing initrd memory: 26556k freed [ 1.475197] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.477368] DMA: Placing 64MB software IO TLB between ffff880006a54000 - ffff88000aa54000 [ 1.477368] DMA: software IO TLB at phys 0x6a54000 - 0xaa54000 [ 1.549995] audit: initializing netlink socket (disabled) [ 1.563855] type=2000 audit(1268762593.560:1): initialized [ 1.586295] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 1.614105] VFS: Disk quotas dquot_6.5.2 [ 1.621796] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.630563] msgmni has been set to 6385 [ 1.643437] alg: No test for stdrng (krng) [ 1.661516] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 1.665460] io scheduler noop registered [ 1.665460] io scheduler anticipatory registered [ 1.665460] io scheduler deadline registered [ 1.743484] io scheduler cfq registered (default) [ 1.766466] registering netback [ 1.779997] hpet_acpi_add: no address or irqs in _CRS [ 1.793714] Linux agpgart interface v0.103 [ 1.797658] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.833695] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 1.853868] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 1.878680] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [ 1.898826] PNP: PS/2 Controller [PNP0303:KBD,PNP0f0e:PS2M] at 0x60,0x64 irq 1,12 [ 1.928251] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.948217] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.974554] mice: PS/2 mouse device common for all mice [ 2.000614] rtc_cmos 00:0a: RTC can wake from S4 [ 2.021534] rtc_cmos 00:0a: rtc core: registered rtc_cmos as rtc0 [ 2.051549] rtc0: alarms up to one month, y3k, 114 bytes nvram [ 2.071654] cpuidle: using governor ladder [ 2.075624] cpuidle: using governor menu [ 2.105498] No iBFT detected. [ 2.118747] TCP cubic registered [ 2.133568] NET: Registered protocol family 10 [ 2.143284] lo: Disabled Privacy Extensions [ 2.146683] Mobile IPv6 [ 2.146683] NET: Registered protocol family 17 [ 2.189586] registered taskstats version 1 [ 2.189773] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [ 2.244609] rtc_cmos 00:0a: setting system clock to 2010-03-16 18:03:16 UTC (1268762596) [ 2.274631] Freeing unused kernel memory: 588k freed [ 2.289677] Write protecting the kernel read-only data: 4224k [ 2.912216] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 2.918313] ACPI: Power Button [PWRF] [ 3.013365] SCSI subsystem initialized [ 3.061176] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009) [ 3.066317] xen_allocate_pirq: returning irq 40 for gsi 40 (XEN) Pin 10-8 already programmed [ 3.068925] HP CISS Driver (v 3.6.20) [ 3.069635] Already setup the GSI :40 [ 3.069650] bnx2 0000:03:00.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40 [ 3.070123] bnx2 0000:03:00.0: firmware: requesting bnx2/bnx2-mips-09-5.0.0.j3.fw [ 3.129956] xen_allocate_pirq: returning irq 33 for gsi 33 (XEN) Pin 10-1 already programmed [ 3.133379] Already setup the GSI :33 [ 3.148581] cciss 0000:48:00.0: PCI INT A -> GSI 33 (level, low) -> IRQ 33 [ 3.160196] IRQ 2997/cciss0: IRQF_DISABLED is not guaranteed on shared IRQs [ 3.164051] cciss0: <0x323a> at PCI 0000:48:00.0 IRQ 2997 using DAC [ 3.180183] cciss/c0d0: p1 p2 [ 3.191383] bnx2 0000:03:00.0: firmware: requesting bnx2/bnx2-rv2p-09-5.0.0.j3.fw [ 3.240197] eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 40, node addr 18:a9:05:68:49:fe [ 3.268347] xen_allocate_pirq: returning irq 39 for gsi 39 (XEN) Pin 10-7 already programmed [ 3.296552] Already setup the GSI :39 [ 3.301941] bnx2 0000:03:00.1: PCI INT B -> GSI 39 (level, low) -> IRQ 39 [ 3.319101] bnx2 0000:03:00.1: firmware: requesting bnx2/bnx2-mips-09-5.0.0.j3.fw [ 3.356898] bnx2 0000:03:00.1: firmware: requesting bnx2/bnx2-rv2p-09-5.0.0.j3.fw [ 3.404857] eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f4000000, IRQ 39, node addr 18:a9:05:68:4a:00 [ 3.440815] xen_allocate_pirq: returning irq 34 for gsi 34 (XEN) Pin 10-2 already programmed [ 3.461394] Already setup the GSI :34 [ 3.470507] bnx2 0000:41:00.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34 [ 3.483761] bnx2 0000:41:00.0: firmware: requesting bnx2/bnx2-mips-09-5.0.0.j3.fw [ 3.525350] bnx2 0000:41:00.0: firmware: requesting bnx2/bnx2-rv2p-09-5.0.0.j3.fw [ 3.567547] eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem fa000000, IRQ 34, node addr 18:a9:05:68:49:fa [ 3.585010] xen_allocate_pirq: returning irq 33 for gsi 33 (XEN) Pin 10-1 already programmed [ 3.610883] Already setup the GSI :33 [ 3.612294] bnx2 0000:41:00.1: PCI INT B -> GSI 33 (level, low) -> IRQ 33 [ 3.616281] bnx2 0000:41:00.1: firmware: requesting bnx2/bnx2-mips-09-5.0.0.j3.fw [ 3.668217] bnx2 0000:41:00.1: firmware: requesting bnx2/bnx2-rv2p-09-5.0.0.j3.fw [ 3.711086] eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 33, node addr 18:a9:05:68:49:fc [ 3.898839] device-mapper: uevent: version 1.0.3 [ 3.912689] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com [ 4.197225] kjournald starting. Commit interval 5 seconds [ 4.202276] EXT3-fs: mounted filesystem with ordered data mode. [ 5.304830] udev: starting version 151 (XEN) IOAPIC[2]: Set PCI routing entry (10-14 -> 0xb9 -> IRQ 46 Mode:1 Active:1) [ 5.533912] hpwdt 0000:00:04.0: PCI INT A -> GSI 46 (level, low) -> IRQ 46 [ 5.559854] hp Watchdog Timer Driver: 1.1.1, timer margin: 30 seconds (nowayout=0), allow kernel dump: OFF (default = 0/OFF), priority: LAST (default = 0/LAST). (XEN) IOAPIC[2]: Set PCI routing entry (10-13 -> 0xc1 -> IRQ 45 Mode:1 Active:1) [ 5.617275] hpilo 0000:00:04.2: PCI INT B -> GSI 45 (level, low) -> IRQ 45 [ 5.637165] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 5.653605] ipmi message handler version 39.2 [ 5.697885] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 5.711636] IPMI System Interface driver. [ 5.714228] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0 [ 5.806891] [drm] Initialized drm 1.1.0 20060810 [ 5.809860] input: PC Speaker as /devices/platform/pcspkr/input/input3 [ 5.840991] piix4_smbus 0000:00:06.0: SMBus Host Controller at 0x580, revision 0 [ 5.953576] EDAC MC: Ver: 2.1.0 Mar 16 2010 [ 5.965558] EDAC amd64_edac: Ver: 3.2.0 Mar 16 2010 [ 5.970195] EDAC amd64: ECC is enabled by BIOS. [ 5.985800] ipmi: Found new BMC (man_id: 0x00000b, prod_id: 0x0000, dev_id: 0x11) [ 5.985830] IPMI kcs interface initialized [ 5.985853] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 [ 5.985860] ipmi_si: duplicate interface [ 6.022080] EDAC amd64: ECC is enabled by BIOS. [ 6.039794] EDAC MC0: Giving out device to ''amd64_edac'' ''Family 10h'': DEV 0000:00:18.2 (XEN) Pin 10-14 already programmed [ 6.039857] xen_allocate_pirq: returning irq 46 for gsi 46 [ 6.045918] Already setup the GSI :46 [ 6.045932] ipmi_si 0000:00:04.6: PCI INT A -> GSI 46 (level, low) -> IRQ 46 [ 6.045943] ipmi_si: Trying PCI-specified kcs state machine at mem address 0xf3df0000, slave address 0x0, irq 46 [ 6.142654] EDAC MC1: Giving out device to ''amd64_edac'' ''Family 10h'': DEV 0000:00:19.2 [ 6.165195] EDAC PCI0: Giving out device to module ''amd64_edac'' controller ''EDAC PCI controller'': DEV ''0000:00:18.2'' (POLLED) [ 6.197033] logips2pp: Detected unknown logitech mouse model 2 (XEN) IOAPIC[2]: Set PCI routing entry (10-12 -> 0xd9 -> IRQ 44 Mode:1 Active:1) [ 6.208059] IRQ 46/ipmi_si: IRQF_DISABLED is not guaranteed on shared IRQs [ 6.208136] Using irq 46 [ 6.217516] [drm] radeon defaulting to userspace modesetting. [ 6.244267] pci 0000:00:03.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44 [ 6.244509] [drm] Initialized radeon 1.32.0 20080528 for 0000:00:03.0 on minor 0 [ 6.323220] Error: Driver ''pcspkr'' is already registered, aborting... [ 6.427148] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input4 [ 6.489789] ipmi: interfacing existing BMC (man_id: 0x00000b, prod_id: 0x0000, dev_id: 0x11) [ 6.493738] IPMI kcs interface initialized [ 12.127634] EXT3 FS on dm-0, internal journal [ 13.339656] kjournald starting. Commit interval 5 seconds [ 13.345018] EXT3 FS on cciss/c0d0p1, internal journal [ 13.348985] EXT3-fs: mounted filesystem with ordered data mode. [ 13.378754] kjournald starting. Commit interval 5 seconds [ 13.407292] EXT3 FS on dm-1, internal journal [ 13.411216] EXT3-fs: mounted filesystem with ordered data mode. [ 13.472093] kjournald starting. Commit interval 5 seconds [ 13.487540] EXT3 FS on dm-2, internal journal [ 13.491519] EXT3-fs: mounted filesystem with ordered data mode. [ 14.249534] Bridge firewalling registered [ 14.624675] bnx2: eth0: using MSIX [ 14.628018] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.241216] bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex, receive & transmit flow control ON [ 16.247860] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 17.442794] ip_tables: (C) 2000-2006 Netfilter Core Team [ 17.492271] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 17.496807] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 17.499666] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 17.500396] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ### Boot finished. (XEN) *** Serial input -> Xen (type ''CTRL-a'' three times to switch input to DOM0) (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #8 registers: 16. (XEN) number of IO-APIC #9 registers: 16. (XEN) number of IO-APIC #10 registers: 16. (XEN) testing the IO APIC....................... (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 009 09 0 0 0 0 0 0 0 81 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 000 00 1 0 0 0 0 0 0 38 (XEN) 06 000 00 1 0 0 0 0 0 0 40 (XEN) 07 000 00 1 0 0 0 0 0 0 48 (XEN) 08 009 09 0 0 0 0 0 0 0 89 (XEN) 09 000 00 0 0 0 0 0 0 0 58 (XEN) 0a 000 00 1 0 0 0 0 0 0 60 (XEN) 0b 000 00 1 0 0 0 0 0 0 68 (XEN) 0c 009 09 0 0 0 0 0 0 0 79 (XEN) 0d 000 00 1 0 0 0 0 0 0 78 (XEN) 0e 000 00 1 0 0 0 0 0 0 88 (XEN) 0f 000 00 1 0 0 0 0 0 0 90 (XEN) IO APIC #9...... (XEN) .... register #00: 09000000 (XEN) ....... : physical APIC id: 09 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 09000000 (XEN) ....... : arbitration: 09 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) IO APIC #10...... (XEN) .... register #00: 0A000000 (XEN) ....... : physical APIC id: 0A (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 0A000000 (XEN) ....... : arbitration: 0A (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 1 0 1 0 0 0 C8 (XEN) 01 000 00 1 1 0 1 0 0 0 D0 (XEN) 02 000 00 1 1 0 1 0 0 0 D8 (XEN) 03 000 00 1 1 0 1 0 0 0 21 (XEN) 04 000 00 1 1 0 1 0 0 0 C0 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 1 0 1 0 0 0 A0 (XEN) 07 000 00 1 1 0 1 0 0 0 A8 (XEN) 08 000 00 1 1 0 1 0 0 0 B0 (XEN) 09 000 00 1 1 0 1 0 0 0 B8 (XEN) 0a 000 00 1 1 0 1 0 0 0 98 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 1 0 1 0 0 0 D9 (XEN) 0d 005 05 0 1 0 1 0 0 0 C9 (XEN) 0e 005 05 0 1 0 1 0 0 0 D1 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ129 -> 0:1 (XEN) IRQ48 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ56 -> 0:5 (XEN) IRQ64 -> 0:6 (XEN) IRQ72 -> 0:7 (XEN) IRQ137 -> 0:8 (XEN) IRQ88 -> 0:9 (XEN) IRQ96 -> 0:10 (XEN) IRQ104 -> 0:11 (XEN) IRQ121 -> 0:12 (XEN) IRQ120 -> 0:13 (XEN) IRQ136 -> 0:14 (XEN) IRQ144 -> 0:15 (XEN) IRQ200 -> 2:0 (XEN) IRQ208 -> 2:1 (XEN) IRQ216 -> 2:2 (XEN) IRQ33 -> 2:3 (XEN) IRQ192 -> 2:4 (XEN) IRQ160 -> 2:6 (XEN) IRQ168 -> 2:7 (XEN) IRQ176 -> 2:8 (XEN) IRQ184 -> 2:9 (XEN) IRQ152 -> 2:10 (XEN) IRQ217 -> 2:12 (XEN) IRQ201 -> 2:13 (XEN) IRQ209 -> 2:14 (XEN) .................................... done. ### Load of driver which drives interrupt 14. It tries to reprogram it ### as edge driven [ 43.618936] ACPI: PCI Interrupt Link [ISF0] enabled at IRQ 14 [ 43.620022] xen_allocate_pirq: returning irq 14 for gsi 14 (XEN) Pin 8-14 already programmed (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:1 Active:1) [ 43.628705] sata_svw 0000:01:0e.0: PCI INT A -> Link[ISF0] -> GSI 14 (level, low) -> IRQ 14 [ 43.632389] scsi0 : sata_svw [ 43.633899] scsi1 : sata_svw [ 43.636719] scsi2 : sata_svw [ 43.638010] scsi3 : sata_svw [ 43.639203] ata1: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0000 irq 14 [ 43.640528] ata2: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0100 irq 14 [ 43.640528] ata3: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0200 irq 14 [ 43.640528] ata4: SATA max UDMA/133 mmio m8192@0xf3ff0000 port 0xf3ff0300 irq 14 [ 43.984136] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 44.012353] ata1.00: ATAPI: Optiarc DVD RW AD-7561S, AH52, max UDMA/100 [ 44.044371] ata1.00: configured for UDMA/100 [ 44.048675] scsi 0:0:0:0: CD-ROM Optiarc DVD RW AD-7561S AH52 PQ: 0 ANSI: 5 [ 44.376037] ata2: SATA link down (SStatus 4 SControl 300) [ 44.708037] ata3: SATA link down (SStatus 4 SControl 300) [ 45.040037] ata4: SATA link down (SStatus 4 SControl 300) [ 45.071418] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray [ 45.075361] Uniform CD-ROM driver Revision: 3.20 [ 45.108751] sr 0:0:0:0: Attached scsi generic sg0 type 5 (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #8 registers: 16. (XEN) number of IO-APIC #9 registers: 16. (XEN) number of IO-APIC #10 registers: 16. (XEN) testing the IO APIC....................... (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 009 09 0 0 0 0 0 0 0 81 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 000 00 1 0 0 0 0 0 0 38 (XEN) 06 000 00 1 0 0 0 0 0 0 40 (XEN) 07 000 00 1 0 0 0 0 0 0 48 (XEN) 08 009 09 0 0 0 0 0 0 0 89 (XEN) 09 000 00 0 0 0 0 0 0 0 58 (XEN) 0a 000 00 1 0 0 0 0 0 0 60 (XEN) 0b 000 00 1 0 0 0 0 0 0 68 (XEN) 0c 009 09 0 0 0 0 0 0 0 79 (XEN) 0d 000 00 1 0 0 0 0 0 0 78 (XEN) 0e 008 08 0 1 0 1 0 0 0 B2 (XEN) 0f 000 00 1 0 0 0 0 0 0 90 (XEN) IO APIC #9...... (XEN) .... register #00: 09000000 (XEN) ....... : physical APIC id: 09 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 09000000 (XEN) ....... : arbitration: 09 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) IO APIC #10...... (XEN) .... register #00: 0A000000 (XEN) ....... : physical APIC id: 0A (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 0A000000 (XEN) ....... : arbitration: 0A (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 1 0 1 0 0 0 C8 (XEN) 01 000 00 1 1 0 1 0 0 0 D0 (XEN) 02 000 00 1 1 0 1 0 0 0 D8 (XEN) 03 000 00 1 1 0 1 0 0 0 21 (XEN) 04 000 00 1 1 0 1 0 0 0 C0 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 1 0 1 0 0 0 A0 (XEN) 07 000 00 1 1 0 1 0 0 0 A8 (XEN) 08 000 00 1 1 0 1 0 0 0 B0 (XEN) 09 000 00 1 1 0 1 0 0 0 B8 (XEN) 0a 000 00 1 1 0 1 0 0 0 98 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 1 0 1 0 0 0 D9 (XEN) 0d 005 05 0 1 0 1 0 0 0 C9 (XEN) 0e 005 05 0 1 0 1 0 0 0 D1 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ129 -> 0:1 (XEN) IRQ48 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ56 -> 0:5 (XEN) IRQ64 -> 0:6 (XEN) IRQ72 -> 0:7 (XEN) IRQ137 -> 0:8 (XEN) IRQ88 -> 0:9 (XEN) IRQ96 -> 0:10 (XEN) IRQ104 -> 0:11 (XEN) IRQ121 -> 0:12 (XEN) IRQ120 -> 0:13 (XEN) IRQ178 -> 0:14 (XEN) IRQ144 -> 0:15 (XEN) IRQ200 -> 2:0 (XEN) IRQ208 -> 2:1 (XEN) IRQ216 -> 2:2 (XEN) IRQ33 -> 2:3 (XEN) IRQ192 -> 2:4 (XEN) IRQ160 -> 2:6 (XEN) IRQ168 -> 2:7 (XEN) IRQ176 -> 2:8 (XEN) IRQ184 -> 2:9 (XEN) IRQ152 -> 2:10 (XEN) IRQ217 -> 2:12 (XEN) IRQ201 -> 2:13 (XEN) IRQ209 -> 2:14 (XEN) .................................... done. ### Load of ehci-hcd, first driver to drive interrupt 5. Interrupt is ### properly set to edge driven and unmasked. [ 54.299957] usbcore: registered new interface driver usbfs [ 54.303639] usbcore: registered new interface driver hub [ 54.305813] usbcore: registered new device driver usb [ 54.320335] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver [ 54.325023] ACPI: PCI Interrupt Link [IUSB] enabled at IRQ 5 [ 54.328028] xen_allocate_pirq: returning irq 5 for gsi 5 (XEN) Pin 8-5 already programmed (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:1 Active:1) [ 54.341716] ehci_hcd 0000:00:07.2: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5 [ 54.344906] ehci_hcd 0000:00:07.2: EHCI Host Controller [ 54.346988] ehci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 [ 54.372157] ehci_hcd 0000:00:07.2: irq 5, io mem 0xf3dc0000 [ 54.400102] ehci_hcd 0000:00:07.2: USB 2.0 started, EHCI 1.00 [ 54.414160] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 54.416797] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 54.418096] usb usb1: Product: EHCI Host Controller [ 54.418096] usb usb1: Manufacturer: Linux 2.6.32-4-xen-amd64 ehci_hcd [ 54.418096] usb usb1: SerialNumber: 0000:00:07.2 [ 54.441124] usb usb1: configuration #1 chosen from 1 choice [ 54.459788] hub 1-0:1.0: USB hub found [ 54.462024] hub 1-0:1.0: 4 ports detected (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #8 registers: 16. (XEN) number of IO-APIC #9 registers: 16. (XEN) number of IO-APIC #10 registers: 16. (XEN) testing the IO APIC....................... (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 009 09 0 0 0 0 0 0 0 81 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 008 08 0 1 0 1 0 0 0 BA (XEN) 06 000 00 1 0 0 0 0 0 0 40 (XEN) 07 000 00 1 0 0 0 0 0 0 48 (XEN) 08 009 09 0 0 0 0 0 0 0 89 (XEN) 09 000 00 0 0 0 0 0 0 0 58 (XEN) 0a 000 00 1 0 0 0 0 0 0 60 (XEN) 0b 000 00 1 0 0 0 0 0 0 68 (XEN) 0c 009 09 0 0 0 0 0 0 0 79 (XEN) 0d 000 00 1 0 0 0 0 0 0 78 (XEN) 0e 008 08 0 1 0 1 0 0 0 B2 (XEN) 0f 000 00 1 0 0 0 0 0 0 90 (XEN) IO APIC #9...... (XEN) .... register #00: 09000000 (XEN) ....... : physical APIC id: 09 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 09000000 (XEN) ....... : arbitration: 09 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) IO APIC #10...... (XEN) .... register #00: 0A000000 (XEN) ....... : physical APIC id: 0A (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 0A000000 (XEN) ....... : arbitration: 0A (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 1 0 1 0 0 0 C8 (XEN) 01 000 00 1 1 0 1 0 0 0 D0 (XEN) 02 000 00 1 1 0 1 0 0 0 D8 (XEN) 03 000 00 1 1 0 1 0 0 0 21 (XEN) 04 000 00 1 1 0 1 0 0 0 C0 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 1 0 1 0 0 0 A0 (XEN) 07 000 00 1 1 0 1 0 0 0 A8 (XEN) 08 000 00 1 1 0 1 0 0 0 B0 (XEN) 09 000 00 1 1 0 1 0 0 0 B8 (XEN) 0a 000 00 1 1 0 1 0 0 0 98 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 1 0 1 0 0 0 D9 (XEN) 0d 005 05 0 1 0 1 0 0 0 C9 (XEN) 0e 005 05 0 1 0 1 0 0 0 D1 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ129 -> 0:1 (XEN) IRQ48 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ186 -> 0:5 (XEN) IRQ64 -> 0:6 (XEN) IRQ72 -> 0:7 (XEN) IRQ137 -> 0:8 (XEN) IRQ88 -> 0:9 (XEN) IRQ96 -> 0:10 (XEN) IRQ104 -> 0:11 (XEN) IRQ121 -> 0:12 (XEN) IRQ120 -> 0:13 (XEN) IRQ178 -> 0:14 (XEN) IRQ144 -> 0:15 (XEN) IRQ200 -> 2:0 (XEN) IRQ208 -> 2:1 (XEN) IRQ216 -> 2:2 (XEN) IRQ33 -> 2:3 (XEN) IRQ192 -> 2:4 (XEN) IRQ160 -> 2:6 (XEN) IRQ168 -> 2:7 (XEN) IRQ176 -> 2:8 (XEN) IRQ184 -> 2:9 (XEN) IRQ152 -> 2:10 (XEN) IRQ217 -> 2:12 (XEN) IRQ201 -> 2:13 (XEN) IRQ209 -> 2:14 (XEN) .................................... done. ### Load of ohci-hcd, the second driver to drive the USB hosts. ### Interrupt is again programmed and now masked! [ 62.751639] ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI) Driver [ 62.760261] xen_allocate_pirq: returning irq 5 for gsi 5 (XEN) Pin 8-5 already programmed (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0xba -> IRQ 5 Mode:1 Active:1) [ 62.765850] ohci_hcd 0000:00:07.0: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5 [ 62.769823] ohci_hcd 0000:00:07.0: OHCI Host Controller [ 62.772502] ohci_hcd 0000:00:07.0: new USB bus registered, assigned bus number 2 [ 62.777389] ohci_hcd 0000:00:07.0: irq 5, io mem 0xf3de0000 [ 62.836143] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 62.840014] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 62.840014] usb usb2: Product: OHCI Host Controller [ 62.840014] usb usb2: Manufacturer: Linux 2.6.32-4-xen-amd64 ohci_hcd [ 62.840014] usb usb2: SerialNumber: 0000:00:07.0 [ 62.858165] usb usb2: configuration #1 chosen from 1 choice [ 62.860603] hub 2-0:1.0: USB hub found [ 62.864225] hub 2-0:1.0: 2 ports detected [ 62.866323] xen_allocate_pirq: returning irq 5 for gsi 5 (XEN) Pin 8-5 already programmed (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0xba -> IRQ 5 Mode:1 Active:1) [ 62.871890] ohci_hcd 0000:00:07.1: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5 [ 62.875072] ohci_hcd 0000:00:07.1: OHCI Host Controller [ 62.894463] ohci_hcd 0000:00:07.1: new USB bus registered, assigned bus number 3 [ 62.897465] ohci_hcd 0000:00:07.1: irq 5, io mem 0xf3dd0000 [ 62.956130] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 62.960014] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 62.960014] usb usb3: Product: OHCI Host Controller [ 62.960014] usb usb3: Manufacturer: Linux 2.6.32-4-xen-amd64 ohci_hcd [ 62.960014] usb usb3: SerialNumber: 0000:00:07.1 [ 62.979124] usb usb3: configuration #1 chosen from 1 choice [ 62.983552] hub 3-0:1.0: USB hub found [ 62.985145] hub 3-0:1.0: 2 ports detected (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #8 registers: 16. (XEN) number of IO-APIC #9 registers: 16. (XEN) number of IO-APIC #10 registers: 16. (XEN) testing the IO APIC....................... (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 009 09 0 0 0 0 0 0 0 81 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 000 00 1 1 0 1 0 0 0 BA (XEN) 06 000 00 1 0 0 0 0 0 0 40 (XEN) 07 000 00 1 0 0 0 0 0 0 48 (XEN) 08 009 09 0 0 0 0 0 0 0 89 (XEN) 09 000 00 0 0 0 0 0 0 0 58 (XEN) 0a 000 00 1 0 0 0 0 0 0 60 (XEN) 0b 000 00 1 0 0 0 0 0 0 68 (XEN) 0c 009 09 0 0 0 0 0 0 0 79 (XEN) 0d 000 00 1 0 0 0 0 0 0 78 (XEN) 0e 008 08 0 1 0 1 0 0 0 B2 (XEN) 0f 000 00 1 0 0 0 0 0 0 90 (XEN) IO APIC #9...... (XEN) .... register #00: 09000000 (XEN) ....... : physical APIC id: 09 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 09000000 (XEN) ....... : arbitration: 09 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 1 0 0 0 0 0 0 00 (XEN) 02 000 00 1 0 0 0 0 0 0 00 (XEN) 03 000 00 1 0 0 0 0 0 0 00 (XEN) 04 000 00 1 0 0 0 0 0 0 00 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 0 0 0 0 0 0 00 (XEN) 07 000 00 1 0 0 0 0 0 0 00 (XEN) 08 000 00 1 0 0 0 0 0 0 00 (XEN) 09 000 00 1 0 0 0 0 0 0 00 (XEN) 0a 000 00 1 0 0 0 0 0 0 00 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 0 0 0 0 0 0 00 (XEN) 0d 000 00 1 0 0 0 0 0 0 00 (XEN) 0e 000 00 1 0 0 0 0 0 0 00 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) IO APIC #10...... (XEN) .... register #00: 0A000000 (XEN) ....... : physical APIC id: 0A (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 0A000000 (XEN) ....... : arbitration: 0A (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 1 0 1 0 0 0 C8 (XEN) 01 000 00 1 1 0 1 0 0 0 D0 (XEN) 02 000 00 1 1 0 1 0 0 0 D8 (XEN) 03 000 00 1 1 0 1 0 0 0 21 (XEN) 04 000 00 1 1 0 1 0 0 0 C0 (XEN) 05 000 00 1 0 0 0 0 0 0 00 (XEN) 06 000 00 1 1 0 1 0 0 0 A0 (XEN) 07 000 00 1 1 0 1 0 0 0 A8 (XEN) 08 000 00 1 1 0 1 0 0 0 B0 (XEN) 09 000 00 1 1 0 1 0 0 0 B8 (XEN) 0a 000 00 1 1 0 1 0 0 0 98 (XEN) 0b 000 00 1 0 0 0 0 0 0 00 (XEN) 0c 000 00 1 1 0 1 0 0 0 D9 (XEN) 0d 005 05 0 1 0 1 0 0 0 C9 (XEN) 0e 005 05 0 1 0 1 0 0 0 D1 (XEN) 0f 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ129 -> 0:1 (XEN) IRQ48 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ186 -> 0:5 (XEN) IRQ64 -> 0:6 (XEN) IRQ72 -> 0:7 (XEN) IRQ137 -> 0:8 (XEN) IRQ88 -> 0:9 (XEN) IRQ96 -> 0:10 (XEN) IRQ104 -> 0:11 (XEN) IRQ121 -> 0:12 (XEN) IRQ120 -> 0:13 (XEN) IRQ178 -> 0:14 (XEN) IRQ144 -> 0:15 (XEN) IRQ200 -> 2:0 (XEN) IRQ208 -> 2:1 (XEN) IRQ216 -> 2:2 (XEN) IRQ33 -> 2:3 (XEN) IRQ192 -> 2:4 (XEN) IRQ160 -> 2:6 (XEN) IRQ168 -> 2:7 (XEN) IRQ176 -> 2:8 (XEN) IRQ184 -> 2:9 (XEN) IRQ152 -> 2:10 (XEN) IRQ217 -> 2:12 (XEN) IRQ201 -> 2:13 (XEN) IRQ209 -> 2:14 (XEN) .................................... done. -- It would be illogical to kill without reason. -- Spock, "Journey to Babel", stardate 3842.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Mar-17 02:05 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Tue, Mar 16, 2010 at 07:20:53PM +0100, Bastian Blank wrote:> On Tue, Mar 16, 2010 at 11:32:16AM -0400, Konrad Rzeszutek Wilk wrote: > > I wish you had included the whole serial console for Xen boot. > > That was the intention but I had to run. Here is it (slightly > annotated). > > > I am > > curious to at what stage the pin 14 of the IOAPIC is set. Is it set by Xen > > hypervisor initially (don''t think so), > > No, the entries on the first IO-APIC for the devices in question are > completely bogus in the initial printout. Unmasked but edge driven.I am going to need your help here. I *think* the issue is that Xen parses the MADT table, which makes the assumption that the ISA interrupt vectors will usually be identity-mapped into the first 16 I/O APIC sources (and the INT_SRC_OVR are used to override those IO APIC pins with new entries). I think it does this: acpi_parse_madt_ioapic_entries calls mp_config_acpi_legacy_irqs: .. snip .. intsrc.mpc_irqflag = 0; /* Conforming */ Which assumes that it is edge, high. I think if you fix this line: 1089 Dprintk("Int: type %d, pol %d, trig %d, bus %d, irq %d, " to do a printk we will see that your pin 14 is programmed to edge(0), high(0). Which by itself is exactly the same thing Linux kernel in baremetal does. But that does not explain why you can''t reprogram it. There is that check you subverted which sets this: mp_ioapic_routing[ioapic].pin_programmed[idx] |= (1<<bit); but I only see that being set when you call ''mp_register_gsi''. And that is only done by the Linux kernel, not by the hypervisor. Furthermore there is a guard for that allows it to be called only for GSI above 15. Can you instrument mp_register_gsi to see when that ''pin_programmed'' is set? Or maybe your grep magic is better than mine and can you see other instances where the mp_ioapic_routing is modified and instrument that? I think once we figure out when the ''pin_programmed'' is set we can back-trace why that is set.> > or is there another piece of code > > in the pv-ops that iterates over the 0-15 IRQs and sets them to the > > legacy trigger/level? > > Before the initialisation of the console, the kernel seem to set pins 5 > to 15 on the first IO-APIC to all edge driven.Yeah, the more I look up data sheets that seems to be right way.> > > When you printed out the IOAPIC information, did the Xen one (in the > > hypervisor, when you did apic=debug during boot) have pin 14 set to the > > wrong mode? > > Yes.Which is OK, b/c when APIC turns on, then you should be able to program it. That is what Linux on baremetal does.> > > Or was it later when the pv-ops kernel booted that the pin 14 was set > > incorrectly? > > The kernel sets it to this values again.You mean it sets it to level (1), low (1) for pin 14 and 5. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhang, Xiantao
2010-Mar-19 02:55 UTC
RE: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
Maybe we need allow dom0 to re-programme the first 15 GSIs to solve this issue. And the root-cause is that the IRQ info(polarity&trigger mode) provided in MP table in some platforms is not always trusted, and system should re-programme it according to the info parsed from ACPI. If the platform provide correct info in MP table, the issue should be gone. Attached a proposed patch, could you have a try to see whether it can fix your issue. Xiantao Bastian Blank wrote:> On Mon, Mar 15, 2010 at 09:31:14PM -0400, Konrad Rzeszutek Wilk wrote: >> 1) Can you boot your baremetal with these options: >> acpi.debug_level=0xffffffff acpi.debug_layer=0x2 apic=debug > >> IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:0 Active:0) >> IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:1 Active:1) > >> 2) And then later on your Xen with these (make SURE to _not_ have >> apic=debug on >> the Linux kernel command line with Xen, it will blow): >> xen.gz apic=debug apic_verbosity=debug console_to_ring >> sync_console loglvl=all guest_loglvl=all > >> (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 >> Mode:0 Active:0) (XEN) Pin 8-14 already programmed >> (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 >> Mode:1 Active:1) > >> (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:0 >> Active:0) (XEN) Pin 8-5 already programmed >> (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:1 >> Active:1) > > Still with my hack to allow 8-5 and 8-14 to be reprogrammed. > > Bastian_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-19 11:06 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Fri, Mar 19, 2010 at 10:55:53AM +0800, Zhang, Xiantao wrote:> Maybe we need allow dom0 to re-programme the first 15 GSIs to solve this issue. And the root-cause is that the IRQ info(polarity&trigger mode) provided in MP table in some platforms is not always trusted, and system should re-programme it according to the info parsed from ACPI. If the platform provide correct info in MP table, the issue should be gone. Attached a proposed patch, could you have a try to see whether it can fix your issue.The outcome is exactly the same than <20100316182053.GA2258@wavehammer.waldi.eu.org>. However it still reports errors back to the domain. Bastian -- I''m a soldier, not a diplomat. I can only tell the truth. -- Kirk, "Errand of Mercy", stardate 3198.9 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-19 11:39 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Tue, Mar 16, 2010 at 07:20:53PM +0100, Bastian Blank wrote: Okay, lets go through the log again. Initial readout before dom0 starts. Only 0 and 9 masked.> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > (XEN) 00 000 00 1 0 0 0 0 0 0 00 > (XEN) 01 000 00 0 0 0 0 0 0 0 28 > (XEN) 02 000 00 0 0 0 0 0 0 0 F0 > (XEN) 03 000 00 0 0 0 0 0 0 0 30 > (XEN) 04 000 00 0 0 0 0 0 0 0 F1 > (XEN) 05 000 00 0 0 0 0 0 0 0 38 > (XEN) 06 000 00 0 0 0 0 0 0 0 40 > (XEN) 07 000 00 0 0 0 0 0 0 0 48 > (XEN) 08 000 00 0 0 0 0 0 0 0 50 > (XEN) 09 000 00 1 1 0 1 0 0 0 58 > (XEN) 0a 000 00 0 0 0 0 0 0 0 60 > (XEN) 0b 000 00 0 0 0 0 0 0 0 68 > (XEN) 0c 000 00 0 0 0 0 0 0 0 70 > (XEN) 0d 000 00 0 0 0 0 0 0 0 78 > (XEN) 0e 000 00 0 0 0 0 0 0 0 88 > (XEN) 0f 000 00 0 0 0 0 0 0 0 90Dom0 tries to set the first 16 IO-APIC pins to edge.> (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-6 -> 0x40 -> IRQ 6 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-7 -> 0x48 -> IRQ 7 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-8 -> 0x50 -> IRQ 8 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-9 -> 0x58 -> IRQ 9 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-10 -> 0x60 -> IRQ 10 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-11 -> 0x68 -> IRQ 11 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-12 -> 0x70 -> IRQ 12 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-13 -> 0x78 -> IRQ 13 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:0 Active:0) > (XEN) IOAPIC[0]: Set PCI routing entry (8-15 -> 0x90 -> IRQ 15 Mode:0 Active:0) > (XEN) Pin 8-9 already programmedDom0 have a console.> [ 0.000000] Linux version 2.6.32-4-xen-amd64 (Debian 2.6.32-10~xen.1) (waldi@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Tue Mar 16 07:46:55 UTC 2010ACPI only reports overrides for 2 and 9.> [ 0.000000] Already setup the GSI :0 > [ 0.000000] Already setup the GSI :1 > [ 0.000000] Already setup the GSI :2 > [ 0.000000] Already setup the GSI :3 > [ 0.000000] Already setup the GSI :4 > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) > [ 0.000000] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=3 > [ 0.000000] xen_allocate_pirq: returning irq 9 for gsi 9 > [ 0.000000] Already setup the GSI :9 > [ 0.000000] xen: acpi sci 9Readout after dom0 booted. Several other pins masked, all set to edge.> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > (XEN) 00 000 00 1 0 0 0 0 0 0 00 > (XEN) 01 009 09 0 0 0 0 0 0 0 81 > (XEN) 02 000 00 0 0 0 0 0 0 0 F0 > (XEN) 03 000 00 0 0 0 0 0 0 0 30 > (XEN) 04 000 00 0 0 0 0 0 0 0 F1 > (XEN) 05 000 00 1 0 0 0 0 0 0 38 > (XEN) 06 000 00 1 0 0 0 0 0 0 40 > (XEN) 07 000 00 1 0 0 0 0 0 0 48 > (XEN) 08 009 09 0 0 0 0 0 0 0 89 > (XEN) 09 000 00 0 0 0 0 0 0 0 58 > (XEN) 0a 000 00 1 0 0 0 0 0 0 60 > (XEN) 0b 000 00 1 0 0 0 0 0 0 68 > (XEN) 0c 009 09 0 0 0 0 0 0 0 79 > (XEN) 0d 000 00 1 0 0 0 0 0 0 78 > (XEN) 0e 000 00 1 0 0 0 0 0 0 88 > (XEN) 0f 000 00 1 0 0 0 0 0 0 90Load of driver which drives interrupt 14. It tries to reprogram it as level driven.> [ 43.620022] xen_allocate_pirq: returning irq 14 for gsi 14 > (XEN) Pin 8-14 already programmed > (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:1 Active:1)Readout after.> (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > (XEN) 00 000 00 1 0 0 0 0 0 0 00 > (XEN) 01 009 09 0 0 0 0 0 0 0 81 > (XEN) 02 000 00 0 0 0 0 0 0 0 F0 > (XEN) 03 000 00 0 0 0 0 0 0 0 30 > (XEN) 04 000 00 0 0 0 0 0 0 0 F1 > (XEN) 05 000 00 1 0 0 0 0 0 0 38 > (XEN) 06 000 00 1 0 0 0 0 0 0 40 > (XEN) 07 000 00 1 0 0 0 0 0 0 48 > (XEN) 08 009 09 0 0 0 0 0 0 0 89 > (XEN) 09 000 00 0 0 0 0 0 0 0 58 > (XEN) 0a 000 00 1 0 0 0 0 0 0 60 > (XEN) 0b 000 00 1 0 0 0 0 0 0 68 > (XEN) 0c 009 09 0 0 0 0 0 0 0 79 > (XEN) 0d 000 00 1 0 0 0 0 0 0 78 > (XEN) 0e 008 08 0 1 0 1 0 0 0 B2 > (XEN) 0f 000 00 1 0 0 0 0 0 0 90I did some digging and found similar code that disallows reprogramming of IO-APIC pins in arch/x86/kernel/apic/io_apic.c:io_apic_set_pci_routing So this behaviour is correct. So the question is: Is it wrong for the kernel to do register_gsi calls early in bootup for interrupts it does not know anything about? Bastian -- Even historians fail to learn from history -- they repeat the same mistakes. -- John Gill, "Patterns of Force", stardate 2534.7 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-19 12:13 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Fri, Mar 19, 2010 at 12:39:04PM +0100, Bastian Blank wrote:> So the question is: Is it wrong for the kernel to do register_gsi calls > early in bootup for interrupts it does not know anything about?I digged a bit further. Native Linux does the following: - Setup all interrupts into the IO-APIC but don''t fix them yet. This way it can be programmed later if the real setup is known. - During device setup the IO-APIC is written once, this value can''t be changed later. I hacked it now that it forbids access to interrupts the hypervisor wants to use and setting the pin to edge-driven does not lock it, but this is only a workaround. It is now able to drive all my USB devices. The real fix could be: - Allow the hypervisor to lock interrupts it uses. Zero would be in it by default. The interrupt for the used serial interface would be added. All other pins are free to be programmed by the kernel once. - Don''t do register_gsi calls from the initial setup in the kernel if no ACPI override is present, only setup the rest. Bastian -- It is a human characteristic to love little animals, especially if they''re attractive in some way. -- McCoy, "The Trouble with Tribbles", stardate 4525.6 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhang, Xiantao
2010-Mar-19 14:15 UTC
RE: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
Bastian Blank wrote:> > I did some digging and found similar code that disallows > reprogramming of IO-APIC pins in > arch/x86/kernel/apic/io_apic.c:io_apic_set_pci_routing > So this behaviour is correct. > So the question is: Is it wrong for the kernel to do register_gsi > calls early in bootup for interrupts it does not know anything about?I remembered you mentioned that you hacked hypervisor and allows re-programme for the special gsi and everying goes well. If you only hacked hypervisor in your case, and I think the hypervisor patch should be enough. Could you attach the full log ? Xiantao _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-19 14:36 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Fri, Mar 19, 2010 at 10:15:23PM +0800, Zhang, Xiantao wrote:> Bastian Blank wrote: > > I did some digging and found similar code that disallows > > reprogramming of IO-APIC pins in > > arch/x86/kernel/apic/io_apic.c:io_apic_set_pci_routing > > So this behaviour is correct. > > So the question is: Is it wrong for the kernel to do register_gsi > > calls early in bootup for interrupts it does not know anything about? > > I remembered you mentioned that you hacked hypervisor and allows > re-programme for the special gsi and everying goes well. If you only > hacked hypervisor in your case, and I think the hypervisor patch > should be enough.Only if we can distinguish between the two registrations, IMHO we can''t. So the kernel must not do them in the first case or we need to add something to distiguish. IMHO the first solution is easier and should work.> Could you attach the full log ?No, I have none. But there is nothing new in it over the last one anyway. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-21 21:47 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Fri, Mar 19, 2010 at 01:13:41PM +0100, Bastian Blank wrote:> The real fix could be: > - Allow the hypervisor to lock interrupts it uses. Zero would be in it by > default. The interrupt for the used serial interface would be added. > All other pins are free to be programmed by the kernel once. > - Don''t do register_gsi calls from the initial setup in the kernel if no > ACPI override is present, only setup the rest.Okay, I think I found another problem. Currently the setup looks like this: - PHYSDEVOP_setup_gsi: set trigger and polarity, unmask pin - PHYSDEVOP_map_pirq: map to pirq, set irq handler to guest If an interrupt fires between this two calles, what happens? Usually I would do the setup the other way around. This would also make it possible to use the irq table to allow the kernel to only set IO-APIC pins mapped to already properly registered interrupts. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Mar-22 06:24 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On 03/21/2010 02:47 PM, Bastian Blank wrote:> On Fri, Mar 19, 2010 at 01:13:41PM +0100, Bastian Blank wrote: > >> The real fix could be: >> - Allow the hypervisor to lock interrupts it uses. Zero would be in it by >> default. The interrupt for the used serial interface would be added. >> All other pins are free to be programmed by the kernel once. >> - Don''t do register_gsi calls from the initial setup in the kernel if no >> ACPI override is present, only setup the rest. >> > Okay, I think I found another problem. Currently the setup looks like > this: > - PHYSDEVOP_setup_gsi: set trigger and polarity, unmask pin > - PHYSDEVOP_map_pirq: map to pirq, set irq handler to guest > > If an interrupt fires between this two calles, what happens? >Doesn''t sound like a good thing to be doing. The unmask should probably be deferred until everything has been set up to receive an interrupt.> Usually I would do the setup the other way around. This would also make > it possible to use the irq table to allow the kernel to only set IO-APIC > pins mapped to already properly registered interrupts. >Sounds reasonable. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2010-Mar-23 11:37 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
>>> Bastian Blank <waldi@debian.org> 21.03.10 22:47 >>> >On Fri, Mar 19, 2010 at 01:13:41PM +0100, Bastian Blank wrote: >> The real fix could be: >> - Allow the hypervisor to lock interrupts it uses. Zero would be in it by >> default. The interrupt for the used serial interface would be added. >> All other pins are free to be programmed by the kernel once. >> - Don''t do register_gsi calls from the initial setup in the kernel if no >> ACPI override is present, only setup the rest. > >Okay, I think I found another problem. Currently the setup looks like >this: >- PHYSDEVOP_setup_gsi: set trigger and polarity, unmask pinWhere are you seeing this? Other than Linux'' (unmasking edge triggered IRQs), Xen''s io_apic_set_pci_routing() always masks the entry afaics.>- PHYSDEVOP_map_pirq: map to pirq, set irq handler to guest > >If an interrupt fires between this two calles, what happens?Since this is only for edge triggered IRQs, I believe the purpose is to not lose an edge when first enabling the interrupt. When one occurs before the handler got set up, the fact that there was one is just getting latched into desc->status, and the IRQ gets mask_ack_irq()-ed. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-23 12:37 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Tue, Mar 23, 2010 at 11:37:56AM +0000, Jan Beulich wrote:> >>> Bastian Blank <waldi@debian.org> 21.03.10 22:47 >>> > >Okay, I think I found another problem. Currently the setup looks like > >this: > >- PHYSDEVOP_setup_gsi: set trigger and polarity, unmask pin > Where are you seeing this? Other than Linux'' (unmasking edge > triggered IRQs), Xen''s io_apic_set_pci_routing() always masks the > entry afaics.In the Linux kernel, xen_register_gsi (arch/x86/xen/pci.c). The io-apic support in Xen is a copy of the Linux code and behaves similar.> >- PHYSDEVOP_map_pirq: map to pirq, set irq handler to guest > >If an interrupt fires between this two calles, what happens? > Since this is only for edge triggered IRQs, I believe the purpose is > to not lose an edge when first enabling the interrupt.No. The interrupt setup is always done before the device setup. This is core kernel functionality. Please explain why you think this is restricted to edge triggered. This is called from the PCI interrupt setup, and usualy used with level triggered interrupts. Bastian -- I have never understood the female capacity to avoid a direct answer to any question. -- Spock, "This Side of Paradise", stardate 3417.3 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2010-Mar-23 14:04 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
>>> Bastian Blank <waldi@debian.org> 23.03.10 13:37 >>> >On Tue, Mar 23, 2010 at 11:37:56AM +0000, Jan Beulich wrote: >> >>> Bastian Blank <waldi@debian.org> 21.03.10 22:47 >>> >> >Okay, I think I found another problem. Currently the setup looks like >> >this: >> >- PHYSDEVOP_setup_gsi: set trigger and polarity, unmask pin >> Where are you seeing this? Other than Linux'' (unmasking edge >> triggered IRQs), Xen''s io_apic_set_pci_routing() always masks the >> entry afaics. > >In the Linux kernel, xen_register_gsi (arch/x86/xen/pci.c). The io-apicAh, okay. The way you wrote it I read that PHYSDEVOP_setup_gsi would do the unmasking. And looking at xen_register_gsi(), I can''t really see where it would unmask the interrupt either. The only place I see it getting unmasked is in startup_pirq() (through EVTCHNOP_bind_pirq).>support in Xen is a copy of the Linux code and behaves similar.Mostly, but not in all details.>> >- PHYSDEVOP_map_pirq: map to pirq, set irq handler to guest >> >If an interrupt fires between this two calles, what happens? >> Since this is only for edge triggered IRQs, I believe the purpose is >> to not lose an edge when first enabling the interrupt. > >No. The interrupt setup is always done before the device setup. This is >core kernel functionality.Yes. But that is unrelated to the choice of keeping masked/unmasking certain interrupts.>Please explain why you think this is restricted to edge triggered. This >is called from the PCI interrupt setup, and usualy used with level >triggered interrupts.This is simply what Linux does (at the end of setup_ioapic_entry()). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bastian Blank
2010-Mar-23 15:49 UTC
Re: [Xen-devel] pvops-2.6.32 - Interrupt routing problem
On Tue, Mar 23, 2010 at 02:04:24PM +0000, Jan Beulich wrote:> >In the Linux kernel, xen_register_gsi (arch/x86/xen/pci.c). The io-apic > Ah, okay. The way you wrote it I read that PHYSDEVOP_setup_gsi > would do the unmasking. And looking at xen_register_gsi(), I can''t > really see where it would unmask the interrupt either. The only place > I see it getting unmasked is in startup_pirq() (through > EVTCHNOP_bind_pirq).Are you ignoring that we speak about the IO-APIC code in Xen? This have nothing to do with EVTCHNOP_bind_pirq.> >support in Xen is a copy of the Linux code and behaves similar. > Mostly, but not in all details.Well, this is nit-picking. The behaviour is the same.> >No. The interrupt setup is always done before the device setup. This is > >core kernel functionality. > Yes. But that is unrelated to the choice of keeping masked/unmasking > certain interrupts.No. Interrupts are unmasked before the device is configured.> >Please explain why you think this is restricted to edge triggered. This > >is called from the PCI interrupt setup, and usualy used with level > >triggered interrupts. > This is simply what Linux does (at the end of setup_ioapic_entry()).No, it is not. This function is not used while running under Xen. Native uses io_apic_set_pci_routing via mp_register_gsi to setup the GSI. In the Xen case this functionality is hidden behind PHYSDEVOP_setup_gsi. Bastian -- "Beauty is transitory." "Beauty survives." -- Spock and Kirk, "That Which Survives", stardate unknown _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel