thr3ads.net - Xen devel - [Xen-devel] Kernel 2.6.31.6 pv

If this information is useful, please help other people find it:
Share via:

Fantu

2010-Jan-07 13:33 UTC

[Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

I have compiled kernel 2.6.31.6 pv_ops but freeze on start and the server not
have serial port, somebody can help to for solve please?
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27059994.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Jan-07 13:37 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:> 
> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and the server
not
> have serial port, somebody can help to for solve please?
>
Well you really need to figure out the error.

You can record a video of the boot process if you don''t have a serial
console (or SOL).

Have you specified correct options for the pv_ops dom0 kernel btw? 

See here: http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Jan-07 13:43 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

The entry in grub.cfg (grub2) is:

menuentry "Xen 4 hg-un, linux 2.6.31.6" {
	set root=(hd0,1)
	multiboot /boot/xen-4.gz dom0_mem=512M iommu=passthrough,pv
	module /boot/vmlinuz-2.6.31.6 root=LABEL=root-raid ro nomodeset
	module /boot/initrd.img-2.6.31.6
}

all files path and root label is correct


Pasi Kärkkäinen wrote:> 
> On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
>> 
>> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and the
server
>> not
>> have serial port, somebody can help to for solve please?
>>
> 
> Well you really need to figure out the error.
> 
> You can record a video of the boot process if you don''t have a
serial
> console (or SOL).
> 
> Have you specified correct options for the pv_ops dom0 kernel btw? 
> 
> See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
> -- Pasi
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27060108.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Jan-07 14:01 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Thu, Jan 07, 2010 at 05:43:03AM -0800, Fantu wrote:> 
> The entry in grub.cfg (grub2) is:
> 
> menuentry "Xen 4 hg-un, linux 2.6.31.6" {
> 	set root=(hd0,1)
> 	multiboot /boot/xen-4.gz dom0_mem=512M iommu=passthrough,pv
> 	module /boot/vmlinuz-2.6.31.6 root=LABEL=root-raid ro nomodeset
> 	module /boot/initrd.img-2.6.31.6
> }
> 
> all files path and root label is correct
> 
I think grub2 f*cks up the kernel parameters, and you need to specify
dummy=foo parameter before the root= parameter.

See:
http://old.nabble.com/Strange-interaction-from-grub2-and-XEN-td26464067.html

-- Pasi
> 
> Pasi Kärkkäinen wrote:
> > 
> > On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
> >> 
> >> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and the
server
> >> not
> >> have serial port, somebody can help to for solve please?
> >>
> > 
> > Well you really need to figure out the error.
> > 
> > You can record a video of the boot process if you don''t have
a serial
> > console (or SOL).
> > 
> > Have you specified correct options for the pv_ops dom0 kernel btw? 
> > 
> > See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> > -- Pasi
> > 
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27060108.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Jan-07 17:04 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

the server is Dell T610, have IPMI serial over lan, can help me to use it for
report debug please?

Pasi Kärkkäinen wrote:> 
> On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
>> 
>> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and the
server
>> not
>> have serial port, somebody can help to for solve please?
>>
> 
> Well you really need to figure out the error.
> 
> You can record a video of the boot process if you don''t have a
serial
> console (or SOL).
> 
> Have you specified correct options for the pv_ops dom0 kernel btw? 
> 
> See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
> -- Pasi
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27063167.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Jan-07 21:14 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Thu, Jan 07, 2010 at 09:04:51AM -0800, Fantu wrote:> 
> the server is Dell T610, have IPMI serial over lan, can help me to use it
for
> report debug please?
> 
First you need to figure out what IO port the IPMI SOL port is using.
lspci -vvv should help you to figure that out.

If you want to see GRUB1 prompt also on the serial console:

cat /etc/grub/grub.conf | grep -i serial

# Intel AMT serial-over-lan console
serial --port=0x3440 --speed=115200
terminal --timeout=10 console serial

0x3440 is the SOL ioport on my motherboard.


And then the actual Xen hypervisor SOL console configuration in
grub1.conf:

xen.gz com1=115200,8n1,0x3440,0 console=com1,vga

0x3440 again is the SOL device IO port. Change it to match your SOL
device IO port.

dom0_kernel should have parameters like this:

vmlinuz root=something console=hvc0 earlyprintk=xen

-- Pasi
> Pasi Kärkkäinen wrote:
> > 
> > On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
> >> 
> >> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and the
server
> >> not
> >> have serial port, somebody can help to for solve please?
> >>
> > 
> > Well you really need to figure out the error.
> > 
> > You can record a video of the boot process if you don''t have
a serial
> > console (or SOL).
> > 
> > Have you specified correct options for the pv_ops dom0 kernel btw? 
> > 
> > See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> > -- Pasi
> > 
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27063167.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Jan-08 14:16 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Thanks, i have do, this is all the i see with sol before black screen freeze
on vga:

 __  __            _  _    ___   ___              _                   
 \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _ __  _ __ ___ 
  \  // _ \ ''_ \  | || |_| | | | | | |__| ''__/ __| |__|
''_ \| ''__/ _ \
  /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__| |_) | | |  __/
 /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  | .__/|_|  \___|
                                                      |_|             
(XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version 4.3.2 (Debian
4.3.2-1.1) )0
(XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000 20756:4feec90815a0
(XEN) Command line: dom0_mem=512M iommu=passthrough,pv com2=57600,8n1
console=ca
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  0000000000100000 - 00000000cf699000 (usable)
(XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
(XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
(XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fe000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000330000000 (usable)
(XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
(XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3          1 INTL 20050624)
(XEN) ACPI: FACS CF6C6000, 0040
(XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM  80000001 INTL 20061109)
(XEN) System RAM: 12053MB (12342340kB)
(XEN) SRAT: PXM 1 -> APIC 16 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 18 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 20 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 22 -> Node 0
(XEN) SRAT: Node 0 PXM 1 0-d0000000
(XEN) SRAT: Node 0 PXM 1 100000000-330000000
(XEN) NUMA: Using 20 for the hash shift.
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.6 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI:                  wakeup_vec[cf6c600c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
(XEN) Processor #16 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
(XEN) Processor #18 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
(XEN) Processor #20 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
(XEN) Processor #22 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
(XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
(XEN) [VT-D]dmar.c:548: Host address width 40
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
(XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000 end_address
cf7dffff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000 end_address
cf7bffff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000 end_address
cf7a1fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000 end_address
cf7a3fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000 end_address
cf7a5fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000 end_address
cf7a7fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000 end_address
cf7a9fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000 end_address
cf7c0fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000 end_address
cf7c2fff
(XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
(XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
(XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec = 1  sub = 1
(XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec = 3  sub = 3
(XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec = 4  sub = 4
(XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec = 5  sub = 5
(XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec = 6  sub = 6
(XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec = 7  sub = 7
(XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec = 2  sub = 2
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 1995.045 MHz processor.
(XEN) Initing memory sharing.
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 4096K
(XEN) CPU: Physical Processor ID: 1
(XEN) CPU: Processor Core ID: 0
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled. 
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Thermal monitoring enabled (TM1)
(XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
(XEN) [VT-D]iommu.c:1063: iommu->reg = ffff82c3fff57000
(XEN) Intel VT-d Snoop Control supported.
(XEN) Intel VT-d DMA Passthrough supported.
(XEN) Intel VT-d Queued Invalidation supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests enabled
(XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
(XEN) Booting processor 1/18 eip 8c000
(XEN) Initializing CPU#1
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 4096K
(XEN) CPU: Physical Processor ID: 1
(XEN) CPU: Processor Core ID: 1
(XEN) HVM: ASIDs enabled. 
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Thermal monitoring enabled (TM1)
(XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
(XEN) Booting processor 2/20 eip 8c000
(XEN) Initializing CPU#2
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 4096K
(XEN) CPU: Physical Processor ID: 1
(XEN) CPU: Processor Core ID: 2
(XEN) HVM: ASIDs enabled. 
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Thermal monitoring enabled (TM1)
(XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
(XEN) Booting processor 3/22 eip 8c000
(XEN) Initializing CPU#3
(XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
(XEN) CPU: L2 cache: 256K
(XEN) CPU: L3 cache: 4096K
(XEN) CPU: Physical Processor ID: 1
(XEN) CPU: Processor Core ID: 3
(XEN) HVM: ASIDs enabled. 
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Thermal monitoring enabled (TM1)
(XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(


Pasi Kärkkäinen wrote:> 
> On Thu, Jan 07, 2010 at 09:04:51AM -0800, Fantu wrote:
>> 
>> the server is Dell T610, have IPMI serial over lan, can help me to use
it
>> for
>> report debug please?
>> 
> 
> First you need to figure out what IO port the IPMI SOL port is using.
> lspci -vvv should help you to figure that out.
> 
> If you want to see GRUB1 prompt also on the serial console:
> 
> cat /etc/grub/grub.conf | grep -i serial
> 
> # Intel AMT serial-over-lan console
> serial --port=0x3440 --speed=115200
> terminal --timeout=10 console serial
> 
> 0x3440 is the SOL ioport on my motherboard.
> 
> 
> And then the actual Xen hypervisor SOL console configuration in
> grub1.conf:
> 
> xen.gz com1=115200,8n1,0x3440,0 console=com1,vga
> 
> 0x3440 again is the SOL device IO port. Change it to match your SOL
> device IO port.
> 
> dom0_kernel should have parameters like this:
> 
> vmlinuz root=something console=hvc0 earlyprintk=xen
> 
> -- Pasi
> 
>> Pasi Kärkkäinen wrote:
>> > 
>> > On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
>> >> 
>> >> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and
the
>> server
>> >> not
>> >> have serial port, somebody can help to for solve please?
>> >>
>> > 
>> > Well you really need to figure out the error.
>> > 
>> > You can record a video of the boot process if you don''t
have a serial
>> > console (or SOL).
>> > 
>> > Have you specified correct options for the pv_ops dom0 kernel btw?
>> > 
>> > See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
>> > 
>> > -- Pasi
>> > 
>> > 
>> > 
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27063167.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27076636.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Jan-13 08:41 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

I have do log more complete (in attachment file)
http://old.nabble.com/file/p27141339/debug2.log debug2.log 


Pasi Kärkkäinen wrote:> 
> On Thu, Jan 07, 2010 at 09:04:51AM -0800, Fantu wrote:
>> 
>> the server is Dell T610, have IPMI serial over lan, can help me to use
it
>> for
>> report debug please?
>> 
> 
> First you need to figure out what IO port the IPMI SOL port is using.
> lspci -vvv should help you to figure that out.
> 
> If you want to see GRUB1 prompt also on the serial console:
> 
> cat /etc/grub/grub.conf | grep -i serial
> 
> # Intel AMT serial-over-lan console
> serial --port=0x3440 --speed=115200
> terminal --timeout=10 console serial
> 
> 0x3440 is the SOL ioport on my motherboard.
> 
> 
> And then the actual Xen hypervisor SOL console configuration in
> grub1.conf:
> 
> xen.gz com1=115200,8n1,0x3440,0 console=com1,vga
> 
> 0x3440 again is the SOL device IO port. Change it to match your SOL
> device IO port.
> 
> dom0_kernel should have parameters like this:
> 
> vmlinuz root=something console=hvc0 earlyprintk=xen
> 
> -- Pasi
> 
>> Pasi Kärkkäinen wrote:
>> > 
>> > On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
>> >> 
>> >> I have compiled kernel 2.6.31.6 pv_ops but freeze on start and
the
>> server
>> >> not
>> >> have serial port, somebody can help to for solve please?
>> >>
>> > 
>> > Well you really need to figure out the error.
>> > 
>> > You can record a video of the boot process if you don''t
have a serial
>> > console (or SOL).
>> > 
>> > Have you specified correct options for the pv_ops dom0 kernel btw?
>> > 
>> > See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
>> > 
>> > -- Pasi
>> > 
>> > 
>> > 
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27063167.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27141339.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Jan-13 09:12 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Wed, Jan 13, 2010 at 12:41:51AM -0800, Fantu wrote:> 
> I have do log more complete (in attachment file)
> http://old.nabble.com/file/p27141339/debug2.log debug2.log 
>
(XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.

I wonder what pv_ops dom0 kernel is trying to do..

-- Pasi

> 
> Pasi Kärkkäinen wrote:
> > 
> > On Thu, Jan 07, 2010 at 09:04:51AM -0800, Fantu wrote:
> >> 
> >> the server is Dell T610, have IPMI serial over lan, can help me to
use it
> >> for
> >> report debug please?
> >> 
> > 
> > First you need to figure out what IO port the IPMI SOL port is using.
> > lspci -vvv should help you to figure that out.
> > 
> > If you want to see GRUB1 prompt also on the serial console:
> > 
> > cat /etc/grub/grub.conf | grep -i serial
> > 
> > # Intel AMT serial-over-lan console
> > serial --port=0x3440 --speed=115200
> > terminal --timeout=10 console serial
> > 
> > 0x3440 is the SOL ioport on my motherboard.
> > 
> > 
> > And then the actual Xen hypervisor SOL console configuration in
> > grub1.conf:
> > 
> > xen.gz com1=115200,8n1,0x3440,0 console=com1,vga
> > 
> > 0x3440 again is the SOL device IO port. Change it to match your SOL
> > device IO port.
> > 
> > dom0_kernel should have parameters like this:
> > 
> > vmlinuz root=something console=hvc0 earlyprintk=xen
> > 
> > -- Pasi
> > 
> >> Pasi Kärkkäinen wrote:
> >> > 
> >> > On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
> >> >> 
> >> >> I have compiled kernel 2.6.31.6 pv_ops but freeze on
start and the
> >> server
> >> >> not
> >> >> have serial port, somebody can help to for solve please?
> >> >>
> >> > 
> >> > Well you really need to figure out the error.
> >> > 
> >> > You can record a video of the boot process if you
don''t have a serial
> >> > console (or SOL).
> >> > 
> >> > Have you specified correct options for the pv_ops dom0 kernel
btw?
> >> > 
> >> > See here: http://wiki.xensource.com/xenwiki/XenParavirtOps
> >> > 
> >> > -- Pasi
> >> > 
> >> > 
> >> > 
> >> > _______________________________________________
> >> > Xen-devel mailing list
> >> > Xen-devel@lists.xensource.com
> >> > http://lists.xensource.com/xen-devel
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context:
> >>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27063167.html
> >> Sent from the Xen - Dev mailing list archive at Nabble.com.
> >> 
> >> 
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27141339.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Jan-13 11:05 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

In attachment file output of lspci -vv do on some server (Dell T610 bios
1.3.6) with hardy with xen 3.3 from backports
http://old.nabble.com/file/p27143153/lspcivv.log lspcivv.log 

Pasi Kärkkäinen wrote:> 
> On Wed, Jan 13, 2010 at 12:41:51AM -0800, Fantu wrote:
>> 
>> I have do log more complete (in attachment file)
>> http://old.nabble.com/file/p27141339/debug2.log debug2.log 
>>
> 
> (XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with
> others.
> 
> I wonder what pv_ops dom0 kernel is trying to do..
> 
> -- Pasi
> 
> 
>> 
>> Pasi Kärkkäinen wrote:
>> > 
>> > On Thu, Jan 07, 2010 at 09:04:51AM -0800, Fantu wrote:
>> >> 
>> >> the server is Dell T610, have IPMI serial over lan, can help
me to use
>> it
>> >> for
>> >> report debug please?
>> >> 
>> > 
>> > First you need to figure out what IO port the IPMI SOL port is
using.
>> > lspci -vvv should help you to figure that out.
>> > 
>> > If you want to see GRUB1 prompt also on the serial console:
>> > 
>> > cat /etc/grub/grub.conf | grep -i serial
>> > 
>> > # Intel AMT serial-over-lan console
>> > serial --port=0x3440 --speed=115200
>> > terminal --timeout=10 console serial
>> > 
>> > 0x3440 is the SOL ioport on my motherboard.
>> > 
>> > 
>> > And then the actual Xen hypervisor SOL console configuration in
>> > grub1.conf:
>> > 
>> > xen.gz com1=115200,8n1,0x3440,0 console=com1,vga
>> > 
>> > 0x3440 again is the SOL device IO port. Change it to match your
SOL
>> > device IO port.
>> > 
>> > dom0_kernel should have parameters like this:
>> > 
>> > vmlinuz root=something console=hvc0 earlyprintk=xen
>> > 
>> > -- Pasi
>> > 
>> >> Pasi Kärkkäinen wrote:
>> >> > 
>> >> > On Thu, Jan 07, 2010 at 05:33:04AM -0800, Fantu wrote:
>> >> >> 
>> >> >> I have compiled kernel 2.6.31.6 pv_ops but freeze on
start and the
>> >> server
>> >> >> not
>> >> >> have serial port, somebody can help to for solve
please?
>> >> >>
>> >> > 
>> >> > Well you really need to figure out the error.
>> >> > 
>> >> > You can record a video of the boot process if you
don''t have a
>> serial
>> >> > console (or SOL).
>> >> > 
>> >> > Have you specified correct options for the pv_ops dom0
kernel btw?
>> >> > 
>> >> > See here:
http://wiki.xensource.com/xenwiki/XenParavirtOps
>> >> > 
>> >> > -- Pasi
>> >> > 
>> >> > 
>> >> > 
>> >> > _______________________________________________
>> >> > Xen-devel mailing list
>> >> > Xen-devel@lists.xensource.com
>> >> > http://lists.xensource.com/xen-devel
>> >> > 
>> >> > 
>> >> 
>> >> -- 
>> >> View this message in context:
>> >>
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27063167.html
>> >> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> >> 
>> >> 
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xensource.com
>> >> http://lists.xensource.com/xen-devel
>> > 
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27141339.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27143153.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad Rzeszutek Wilk

2010-Jan-13 15:39 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Wed, Jan 13, 2010 at 03:05:53AM -0800, Fantu wrote:> 
> In attachment file output of lspci -vv do on some server (Dell T610 bios
> 1.3.6) with hardy with xen 3.3 from backports
> http://old.nabble.com/file/p27143153/lspcivv.log lspcivv.log 
In your vmlinuz argument line:
root=LABEL=root-raid ro console=hvc0 console=com2,vga earlyprintk=xen

The second console=com2,vga should not be there (that syntax is only
applicable to the Xen command line).

Also add these extra arguments to the Linux command line:
initcall_debug debug loglevel=10

That should out a bit in figuring out where you are stuck.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Jan-15 07:00 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

without add also in vmlinux not show all (see precedent first post of debug)
the actual entry of grub is:
menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
	set root=(hd0,1)
	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv loglvl=all
guest_loglvl=all sync_console console_to_ring com2=56700,8n1
console=com2,vga
	module /boot/vmlinuz-2.6.31.6 root=LABEL=root-raid ro console=hvc0
console=com2,vga earlyprintk=xen
	module /boot/initrd.img-2.6.31.6
}
what i change for do correct and complete?


Konrad Rzeszutek Wilk wrote:> 
> On Wed, Jan 13, 2010 at 03:05:53AM -0800, Fantu wrote:
>> 
>> In attachment file output of lspci -vv do on some server (Dell T610
bios
>> 1.3.6) with hardy with xen 3.3 from backports
>> http://old.nabble.com/file/p27143153/lspcivv.log lspcivv.log 
> 
> In your vmlinuz argument line:
> root=LABEL=root-raid ro console=hvc0 console=com2,vga earlyprintk=xen
> 
> The second console=com2,vga should not be there (that syntax is only
> applicable to the Xen command line).
> 
> Also add these extra arguments to the Linux command line:
> initcall_debug debug loglevel=10
> 
> That should out a bit in figuring out where you are stuck.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27173149.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Jan-15 07:34 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Thu, Jan 14, 2010 at 11:00:59PM -0800, Fantu wrote:> 
> without add also in vmlinux not show all (see precedent first post of
debug)
> the actual entry of grub is:
> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> 	set root=(hd0,1)
> 	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv loglvl=all
> guest_loglvl=all sync_console console_to_ring com2=56700,8n1
> console=com2,vga
> 	module /boot/vmlinuz-2.6.31.6 root=LABEL=root-raid ro console=hvc0
> console=com2,vga earlyprintk=xen
> 	module /boot/initrd.img-2.6.31.6
> }
> what i change for do correct and complete?
>
Looks like you''re using GRUB2. It is known to remove the first 
parameter for kernel,  so you need to add a dummy option there.

ie. iun your case GRUB2 will remove the "root=" parameter, 
making your dom0 kernel fail booting.

See:
http://old.nabble.com/Strange-interaction-from-grub2-and-XEN-td26464067.html

So your GRUB2 entry should be something like this:

menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
	insmod ext2
	set root=(hd0,1)
	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv loglvl=all
guest_loglvl=all sync_console console_to_ring com2=56700,8n1 console=com2,vga
	module /boot/vmlinuz-2.6.31.6 dummy=dummy root=LABEL=root-raid ro console=hvc0
earlyprintk=xen nomodeset
	module /boot/initrd.img-2.6.31.6
}

(serial console stuff fixed aswell).
For more information see: http://wiki.xensource.com/xenwiki/XenParavirtOps

Btw is that a real physical serial port on the motherboard, 
or some virtual serial port (SOL) from a management prosessor, or a PCI serial
card?

-- Pasi

> 
> Konrad Rzeszutek Wilk wrote:
> > 
> > On Wed, Jan 13, 2010 at 03:05:53AM -0800, Fantu wrote:
> >> 
> >> In attachment file output of lspci -vv do on some server (Dell
T610 bios
> >> 1.3.6) with hardy with xen 3.3 from backports
> >> http://old.nabble.com/file/p27143153/lspcivv.log lspcivv.log 
> > 
> > In your vmlinuz argument line:
> > root=LABEL=root-raid ro console=hvc0 console=com2,vga earlyprintk=xen
> > 
> > The second console=com2,vga should not be there (that syntax is only
> > applicable to the Xen command line).
> > 
> > Also add these extra arguments to the Linux command line:
> > initcall_debug debug loglevel=10
> > 
> > That should out a bit in figuring out where you are stuck.
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27173149.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad Rzeszutek Wilk

2010-Jan-15 17:01 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Thu, Jan 14, 2010 at 11:00:59PM -0800, Fantu wrote:> 
> without add also in vmlinux not show all (see precedent first post of
debug)
Not sure what you are saying.
> the actual entry of grub is:
.. snip ..> 	module /boot/vmlinuz-2.6.31.6 root=LABEL=root-raid ro console=hvc0
> console=com2,vga earlyprintk=xen
Get rid off ''console=com2,vga''. Add in
''initcall_debug debug
loglevel=10''

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Jeremy Fitzhardinge

2010-Jan-21 22:04 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On 01/08/2010 06:16 AM, Fantu wrote:> Thanks, i have do, this is all the i see with sol before black screen
freeze
> on vga:
>
>   __  __            _  _    ___   ___              _
>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _ __  _ __ ___
>    \  // _ \ ''_ \  | || |_| | | | | | |__| ''__/ __| |__|
''_ \| ''__/ _ \
>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__| |_) | | |  __/
>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  | .__/|_|  \___|
>                                                        |_|
> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version 4.3.2 (Debian
> 4.3.2-1.1) )0
> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000 20756:4feec90815a0
> (XEN) Command line: dom0_mem=512M iommu=passthrough,pv com2=57600,8n1
> console=ca
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> (XEN) Disc information:
> (XEN)  Found 2 MBR signatures
> (XEN)  Found 2 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 00000000000a0000 (usable)
> (XEN)  0000000000100000 - 00000000cf699000 (usable)
> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000330000000 (usable)
> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3          1 INTL 20050624)
> (XEN) ACPI: FACS CF6C6000, 0040
> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3          1 DELL        1)
> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM  80000001 INTL 20061109)
> (XEN) System RAM: 12053MB (12342340kB)
> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
> (XEN) SRAT: Node 0 PXM 1 0-d0000000
> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
> (XEN) NUMA: Using 20 for the hash shift.
> (XEN) Domain heap initialised
> (XEN) found SMP MP-table at 000fe710
> (XEN) DMI 2.6 present.
> (XEN) Using APIC driver default
> (XEN) ACPI: PM-Timer IO Port: 0x808
> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
> (XEN) ACPI:                  wakeup_vec[cf6c600c], vec_size[20]
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
> (XEN) Processor #16 7:10 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
> (XEN) Processor #18 7:10 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
> (XEN) Processor #20 7:10 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
> (XEN) Processor #22 7:10 APIC version 21
> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
> (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> (XEN) ACPI: IRQ0 used by override.
> (XEN) ACPI: IRQ2 used by override.
> (XEN) ACPI: IRQ9 used by override.
> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
> (XEN) [VT-D]dmar.c:548: Host address width 40
> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
> (XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000 end_address
> cf7dffff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000 end_address
> cf7bffff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000 end_address
> cf7a1fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000 end_address
> cf7a3fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000 end_address
> cf7a5fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000 end_address
> cf7a7fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000 end_address
> cf7a9fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000 end_address
> cf7c0fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000 end_address
> cf7c2fff
> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec = 1  sub = 1
> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec = 3  sub = 3
> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec = 4  sub = 4
> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec = 5  sub = 5
> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec = 6  sub = 6
> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec = 7  sub = 7
> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec = 2  sub = 2
> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> (XEN) PCI: MCFG area at e0000000 reserved in E820
> (XEN) Using ACPI (MADT) for SMP configuration information
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Initializing CPU#0
> (XEN) Detected 1995.045 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 256K
> (XEN) CPU: L3 cache: 4096K
> (XEN) CPU: Physical Processor ID: 1
> (XEN) CPU: Processor Core ID: 0
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging detected.
> (XEN) Intel machine check reporting enabled on CPU#0.
> (XEN) CPU0: Thermal monitoring enabled (TM1)
> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
> (XEN) [VT-D]iommu.c:1063: iommu->reg = ffff82c3fff57000
> (XEN) Intel VT-d Snoop Control supported.
> (XEN) Intel VT-d DMA Passthrough supported.
> (XEN) Intel VT-d Queued Invalidation supported.
> (XEN) Intel VT-d Interrupt Remapping not supported.
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests enabled
> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
> (XEN) Booting processor 1/18 eip 8c000
> (XEN) Initializing CPU#1
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 256K
> (XEN) CPU: L3 cache: 4096K
> (XEN) CPU: Physical Processor ID: 1
> (XEN) CPU: Processor Core ID: 1
> (XEN) HVM: ASIDs enabled.
> (XEN) Intel machine check reporting enabled on CPU#1.
> (XEN) CPU1: Thermal monitoring enabled (TM1)
> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
> (XEN) Booting processor 2/20 eip 8c000
> (XEN) Initializing CPU#2
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 256K
> (XEN) CPU: L3 cache: 4096K
> (XEN) CPU: Physical Processor ID: 1
> (XEN) CPU: Processor Core ID: 2
> (XEN) HVM: ASIDs enabled.
> (XEN) Intel machine check reporting enabled on CPU#2.
> (XEN) CPU2: Thermal monitoring enabled (TM1)
> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
> (XEN) Booting processor 3/22 eip 8c000
> (XEN) Initializing CPU#3
> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> (XEN) CPU: L2 cache: 256K
> (XEN) CPU: L3 cache: 4096K
> (XEN) CPU: Physical Processor ID: 1
> (XEN) CPU: Processor Core ID: 3
> (XEN) HVM: ASIDs enabled.
> (XEN) Intel machine check reporting enabled on CPU#3.
> (XEN) CPU3: Thermal monitoring enabled (TM1)
> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
> (XEN) Total of 4 processors activated.
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  ->  Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> (XEN) checking TSC synchronization across 4 CPUs: passed.
> (XEN) Platform timer is 14.318MHz HPET
> (
>    
Ah, I saw the same when using a IPMI SOL implementation; this is the 
point when the serial port becomes interrupt-driven, and there''s 
something wrong with interrupts.  The fix is this patch from Konrad:

diff -r 8f304c003af4 -r 7863747c5061 xen/drivers/char/ns16550.c
--- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009 +0000
+++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009 -0800
@@ -39,6 +39,7 @@
      /* UART with no IRQ line: periodically-polled I/O. */
      struct timer timer;
      unsigned int timeout_ms;
+    int probing, intr_works;
  } ns16550_com[2] = { { 0 } };

  /* Register offsets */
@@ -127,6 +128,13 @@
      struct serial_port *port = dev_id;
      struct ns16550 *uart = port->uart;

+    if (uart->intr_works == 0)
+    {
+        uart->probing = 0;
+        uart->intr_works = 1;
+        stop_timer(&uart->timer);
+    }
+
      while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
      {
          char lsr = ns_read_reg(uart, LSR);
@@ -143,6 +151,15 @@
      struct ns16550 *uart = port->uart;
      struct cpu_user_regs *regs = guest_cpu_user_regs();

+    if ( uart->intr_works )
+        return;     /* Interrupts work - no more polling */
+
+    if ( uart->probing ) {
+        uart->probing = 0;
+        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff )
+            return;     /* All bits set - probably no UART present */
+    }
+
      while ( ns_read_reg(uart, LSR)&  LSR_DR )
          serial_rx_interrupt(port, regs);

@@ -230,15 +247,14 @@

      serial_async_transmit(port);

+    init_timer(&uart->timer, ns16550_poll, port, 0);
+    /* Calculate time to fill RX FIFO and/or empty TX FIFO for polling. */
+    bits = uart->data_bits + uart->stop_bits + !!uart->parity;
+    uart->timeout_ms = max_t(
+        unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
uart->baud);
+
      if ( uart->irq == 0 )
-    {
-        /* Polled mode. Calculate time to fill RX FIFO and/or empty TX FIFO. */
-        bits = uart->data_bits + uart->stop_bits + !!uart->parity;
-        uart->timeout_ms = max_t(
-            unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
uart->baud);
-        init_timer(&uart->timer, ns16550_poll, port, 0);
          set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
-    }
      else
      {
          uart->irqaction.handler = ns16550_interrupt;
@@ -252,6 +268,12 @@

          /* Enable receive and transmit interrupts. */
          ns_write_reg(uart, IER, IER_ERDAI | IER_ETHREI);
+
+        /* Do a timed write to make sure we are getting interrupts. */
+        uart->probing = 1;
+        uart->intr_works = 0;
+        ns_write_reg(uart, THR, 0xff);
+        set_timer(&uart->timer, NOW() + MILLISECS(uart->timeout_ms));
      }
  }


	J


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Feb-16 13:56 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

I have download update xen from unstable, kernel from git and i try to apply
patch but it seems already present
I have try to start and log with SOL, this is the full output: 
http://old.nabble.com/file/p27608625/logsol.txt logsol.txt 
The entry in grub for debug:
menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
	set root=(hd0,1)
	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv loglvl=all
guest_loglvl=all sync_console console_to_ring com2=56700,8n1
console=com2,vga
	module /boot/vmlinuz-2.6.31.6-xen root=LABEL=root-raid ro console=hvc0
initcall_debug debug loglevel=10 earlyprintk=xen
	module /boot/initrd.img-2.6.31.6-xen
}

Jeremy Fitzhardinge wrote:> 
> On 01/08/2010 06:16 AM, Fantu wrote:
>> Thanks, i have do, this is all the i see with sol before black screen
>> freeze
>> on vga:
>>
>>   __  __            _  _    ___   ___              _
>>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _ __  _ __ ___
>>    \  // _ \ ''_ \  | || |_| | | | | | |__| ''__/ __|
|__| ''_ \| ''__/ _ \
>>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__| |_) | | |  __/
>>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  | .__/|_|  \___|
>>                                                        |_|
>> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version 4.3.2 (Debian
>> 4.3.2-1.1) )0
>> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000
20756:4feec90815a0
>> (XEN) Command line: dom0_mem=512M iommu=passthrough,pv com2=57600,8n1
>> console=ca
>> (XEN) Video information:
>> (XEN)  VGA is text mode 80x25, font 8x16
>> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
>> (XEN) Disc information:
>> (XEN)  Found 2 MBR signatures
>> (XEN)  Found 2 EDD information structures
>> (XEN) Xen-e820 RAM map:
>> (XEN)  0000000000000000 - 00000000000a0000 (usable)
>> (XEN)  0000000000100000 - 00000000cf699000 (usable)
>> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
>> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
>> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
>> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
>> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
>> (XEN)  0000000100000000 - 0000000330000000 (usable)
>> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
>> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3          1 INTL
>> 20050624)
>> (XEN) ACPI: FACS CF6C6000, 0040
>> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3          1 DELL
>> 1)
>> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM  80000001 INTL
>> 20061109)
>> (XEN) System RAM: 12053MB (12342340kB)
>> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
>> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
>> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
>> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
>> (XEN) SRAT: Node 0 PXM 1 0-d0000000
>> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
>> (XEN) NUMA: Using 20 for the hash shift.
>> (XEN) Domain heap initialised
>> (XEN) found SMP MP-table at 000fe710
>> (XEN) DMI 2.6 present.
>> (XEN) Using APIC driver default
>> (XEN) ACPI: PM-Timer IO Port: 0x808
>> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
>> (XEN) ACPI:                  wakeup_vec[cf6c600c], vec_size[20]
>> (XEN) ACPI: Local APIC address 0xfee00000
>> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
>> (XEN) Processor #16 7:10 APIC version 21
>> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
>> (XEN) Processor #18 7:10 APIC version 21
>> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
>> (XEN) Processor #20 7:10 APIC version 21
>> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
>> (XEN) Processor #22 7:10 APIC version 21
>> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
>> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
>> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
>> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
>> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
>> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
>> (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI 32-55
>> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
>> (XEN) ACPI: IRQ0 used by override.
>> (XEN) ACPI: IRQ2 used by override.
>> (XEN) ACPI: IRQ9 used by override.
>> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
>> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
>> (XEN) [VT-D]dmar.c:548: Host address width 40
>> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
>> (XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
>> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000 end_address
>> cf7dffff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000 end_address
>> cf7bffff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000 end_address
>> cf7a1fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000 end_address
>> cf7a3fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000 end_address
>> cf7a5fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000 end_address
>> cf7a7fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000 end_address
>> cf7a9fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000 end_address
>> cf7c0fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
>> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000 end_address
>> cf7c2fff
>> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
>> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
>> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec = 1  sub = 1
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec = 3  sub = 3
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec = 4  sub = 4
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec = 5  sub = 5
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec = 6  sub = 6
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec = 7  sub = 7
>> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec = 2  sub = 2
>> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
>> (XEN) PCI: MCFG area at e0000000 reserved in E820
>> (XEN) Using ACPI (MADT) for SMP configuration information
>> (XEN) Using scheduler: SMP Credit Scheduler (credit)
>> (XEN) Initializing CPU#0
>> (XEN) Detected 1995.045 MHz processor.
>> (XEN) Initing memory sharing.
>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> (XEN) CPU: L2 cache: 256K
>> (XEN) CPU: L3 cache: 4096K
>> (XEN) CPU: Physical Processor ID: 1
>> (XEN) CPU: Processor Core ID: 0
>> (XEN) VMX: Supported advanced features:
>> (XEN)  - APIC MMIO access virtualisation
>> (XEN)  - APIC TPR shadow
>> (XEN)  - Extended Page Tables (EPT)
>> (XEN)  - Virtual-Processor Identifiers (VPID)
>> (XEN)  - Virtual NMI
>> (XEN)  - MSR direct-access bitmap
>> (XEN) HVM: ASIDs enabled.
>> (XEN) HVM: VMX enabled
>> (XEN) HVM: Hardware Assisted Paging detected.
>> (XEN) Intel machine check reporting enabled on CPU#0.
>> (XEN) CPU0: Thermal monitoring enabled (TM1)
>> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
>> (XEN) [VT-D]iommu.c:1063: iommu->reg = ffff82c3fff57000
>> (XEN) Intel VT-d Snoop Control supported.
>> (XEN) Intel VT-d DMA Passthrough supported.
>> (XEN) Intel VT-d Queued Invalidation supported.
>> (XEN) Intel VT-d Interrupt Remapping not supported.
>> (XEN) I/O virtualisation enabled
>> (XEN) I/O virtualisation for PV guests enabled
>> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
>> (XEN) Booting processor 1/18 eip 8c000
>> (XEN) Initializing CPU#1
>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> (XEN) CPU: L2 cache: 256K
>> (XEN) CPU: L3 cache: 4096K
>> (XEN) CPU: Physical Processor ID: 1
>> (XEN) CPU: Processor Core ID: 1
>> (XEN) HVM: ASIDs enabled.
>> (XEN) Intel machine check reporting enabled on CPU#1.
>> (XEN) CPU1: Thermal monitoring enabled (TM1)
>> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
>> (XEN) Booting processor 2/20 eip 8c000
>> (XEN) Initializing CPU#2
>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> (XEN) CPU: L2 cache: 256K
>> (XEN) CPU: L3 cache: 4096K
>> (XEN) CPU: Physical Processor ID: 1
>> (XEN) CPU: Processor Core ID: 2
>> (XEN) HVM: ASIDs enabled.
>> (XEN) Intel machine check reporting enabled on CPU#2.
>> (XEN) CPU2: Thermal monitoring enabled (TM1)
>> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
>> (XEN) Booting processor 3/22 eip 8c000
>> (XEN) Initializing CPU#3
>> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> (XEN) CPU: L2 cache: 256K
>> (XEN) CPU: L3 cache: 4096K
>> (XEN) CPU: Physical Processor ID: 1
>> (XEN) CPU: Processor Core ID: 3
>> (XEN) HVM: ASIDs enabled.
>> (XEN) Intel machine check reporting enabled on CPU#3.
>> (XEN) CPU3: Thermal monitoring enabled (TM1)
>> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz stepping 05
>> (XEN) Total of 4 processors activated.
>> (XEN) ENABLING IO-APIC IRQs
>> (XEN)  ->  Using new ACK method
>> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
>> (XEN) checking TSC synchronization across 4 CPUs: passed.
>> (XEN) Platform timer is 14.318MHz HPET
>> (
>>    
> 
> Ah, I saw the same when using a IPMI SOL implementation; this is the 
> point when the serial port becomes interrupt-driven, and there''s 
> something wrong with interrupts.  The fix is this patch from Konrad:
> 
> diff -r 8f304c003af4 -r 7863747c5061 xen/drivers/char/ns16550.c
> --- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009 +0000
> +++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009 -0800
> @@ -39,6 +39,7 @@
>       /* UART with no IRQ line: periodically-polled I/O. */
>       struct timer timer;
>       unsigned int timeout_ms;
> +    int probing, intr_works;
>   } ns16550_com[2] = { { 0 } };
> 
>   /* Register offsets */
> @@ -127,6 +128,13 @@
>       struct serial_port *port = dev_id;
>       struct ns16550 *uart = port->uart;
> 
> +    if (uart->intr_works == 0)
> +    {
> +        uart->probing = 0;
> +        uart->intr_works = 1;
> +        stop_timer(&uart->timer);
> +    }
> +
>       while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
>       {
>           char lsr = ns_read_reg(uart, LSR);
> @@ -143,6 +151,15 @@
>       struct ns16550 *uart = port->uart;
>       struct cpu_user_regs *regs = guest_cpu_user_regs();
> 
> +    if ( uart->intr_works )
> +        return;     /* Interrupts work - no more polling */
> +
> +    if ( uart->probing ) {
> +        uart->probing = 0;
> +        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff )
> +            return;     /* All bits set - probably no UART present */
> +    }
> +
>       while ( ns_read_reg(uart, LSR)&  LSR_DR )
>           serial_rx_interrupt(port, regs);
> 
> @@ -230,15 +247,14 @@
> 
>       serial_async_transmit(port);
> 
> +    init_timer(&uart->timer, ns16550_poll, port, 0);
> +    /* Calculate time to fill RX FIFO and/or empty TX FIFO for polling.
> */
> +    bits = uart->data_bits + uart->stop_bits + !!uart->parity;
> +    uart->timeout_ms = max_t(
> +        unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
> uart->baud);
> +
>       if ( uart->irq == 0 )
> -    {
> -        /* Polled mode. Calculate time to fill RX FIFO and/or empty TX
> FIFO. */
> -        bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> -        uart->timeout_ms = max_t(
> -            unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
> uart->baud);
> -        init_timer(&uart->timer, ns16550_poll, port, 0);
>           set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
> -    }
>       else
>       {
>           uart->irqaction.handler = ns16550_interrupt;
> @@ -252,6 +268,12 @@
> 
>           /* Enable receive and transmit interrupts. */
>           ns_write_reg(uart, IER, IER_ERDAI | IER_ETHREI);
> +
> +        /* Do a timed write to make sure we are getting interrupts. */
> +        uart->probing = 1;
> +        uart->intr_works = 0;
> +        ns_write_reg(uart, THR, 0xff);
> +        set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
>       }
>   }
> 
> 
> 	J
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27608625.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Feb-16 14:27 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Tue, Feb 16, 2010 at 05:56:35AM -0800, Fantu wrote:> 
> I have download update xen from unstable, kernel from git and i try to
apply
> patch but it seems already present
> I have try to start and log with SOL, this is the full output: 
> http://old.nabble.com/file/p27608625/logsol.txt logsol.txt 
> The entry in grub for debug:
> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> 	set root=(hd0,1)
> 	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv loglvl=all
> guest_loglvl=all sync_console console_to_ring com2=56700,8n1
> console=com2,vga
> 	module /boot/vmlinuz-2.6.31.6-xen root=LABEL=root-raid ro console=hvc0
> initcall_debug debug loglevel=10 earlyprintk=xen
> 	module /boot/initrd.img-2.6.31.6-xen
> }
So you''re using GRUB2..

Please check this wiki page:
http://wiki.xensource.com/xenwiki/XenCommonProblems

There''s a chapter called "Booting Xen with GRUB2 fails?".

-- Pasi
> 
> Jeremy Fitzhardinge wrote:
> > 
> > On 01/08/2010 06:16 AM, Fantu wrote:
> >> Thanks, i have do, this is all the i see with sol before black
screen
> >> freeze
> >> on vga:
> >>
> >>   __  __            _  _    ___   ___              _
> >>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _ __  _ __
___
> >>    \  // _ \ ''_ \  | || |_| | | | | | |__| ''__/
__| |__| ''_ \| ''__/ _ \
> >>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__| |_) | | |
__/
> >>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  | .__/|_| 
\___|
> >>                                                        |_|
> >> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version 4.3.2 (Debian
> >> 4.3.2-1.1) )0
> >> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000
20756:4feec90815a0
> >> (XEN) Command line: dom0_mem=512M iommu=passthrough,pv
com2=57600,8n1
> >> console=ca
> >> (XEN) Video information:
> >> (XEN)  VGA is text mode 80x25, font 8x16
> >> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> >> (XEN) Disc information:
> >> (XEN)  Found 2 MBR signatures
> >> (XEN)  Found 2 EDD information structures
> >> (XEN) Xen-e820 RAM map:
> >> (XEN)  0000000000000000 - 00000000000a0000 (usable)
> >> (XEN)  0000000000100000 - 00000000cf699000 (usable)
> >> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
> >> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
> >> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
> >> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> >> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
> >> (XEN)  0000000100000000 - 0000000330000000 (usable)
> >> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
> >> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3          1 INTL
> >> 20050624)
> >> (XEN) ACPI: FACS CF6C6000, 0040
> >> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3          1 DELL
> >> 1)
> >> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM  80000001 INTL
> >> 20061109)
> >> (XEN) System RAM: 12053MB (12342340kB)
> >> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
> >> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
> >> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
> >> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
> >> (XEN) SRAT: Node 0 PXM 1 0-d0000000
> >> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
> >> (XEN) NUMA: Using 20 for the hash shift.
> >> (XEN) Domain heap initialised
> >> (XEN) found SMP MP-table at 000fe710
> >> (XEN) DMI 2.6 present.
> >> (XEN) Using APIC driver default
> >> (XEN) ACPI: PM-Timer IO Port: 0x808
> >> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
> >> (XEN) ACPI:                  wakeup_vec[cf6c600c], vec_size[20]
> >> (XEN) ACPI: Local APIC address 0xfee00000
> >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
> >> (XEN) Processor #16 7:10 APIC version 21
> >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
> >> (XEN) Processor #18 7:10 APIC version 21
> >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
> >> (XEN) Processor #20 7:10 APIC version 21
> >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
> >> (XEN) Processor #22 7:10 APIC version 21
> >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
> >> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> >> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
> >> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI
0-23
> >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
> >> (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000, GSI
32-55
> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> >> (XEN) ACPI: IRQ0 used by override.
> >> (XEN) ACPI: IRQ2 used by override.
> >> (XEN) ACPI: IRQ9 used by override.
> >> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
> >> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
> >> (XEN) [VT-D]dmar.c:548: Host address width 40
> >> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
> >> (XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
> >> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000
end_address
> >> cf7dffff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000
end_address
> >> cf7bffff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000
end_address
> >> cf7a1fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000
end_address
> >> cf7a3fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000
end_address
> >> cf7a5fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000
end_address
> >> cf7a7fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000
end_address
> >> cf7a9fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000
end_address
> >> cf7c0fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000
end_address
> >> cf7c2fff
> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> >> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
> >> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec = 1  sub =
1
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec = 3  sub =
3
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec = 4  sub =
4
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec = 5  sub =
5
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec = 6  sub =
6
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec = 7  sub =
7
> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec = 2  sub =
2
> >> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 -
255
> >> (XEN) PCI: MCFG area at e0000000 reserved in E820
> >> (XEN) Using ACPI (MADT) for SMP configuration information
> >> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> >> (XEN) Initializing CPU#0
> >> (XEN) Detected 1995.045 MHz processor.
> >> (XEN) Initing memory sharing.
> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> (XEN) CPU: L2 cache: 256K
> >> (XEN) CPU: L3 cache: 4096K
> >> (XEN) CPU: Physical Processor ID: 1
> >> (XEN) CPU: Processor Core ID: 0
> >> (XEN) VMX: Supported advanced features:
> >> (XEN)  - APIC MMIO access virtualisation
> >> (XEN)  - APIC TPR shadow
> >> (XEN)  - Extended Page Tables (EPT)
> >> (XEN)  - Virtual-Processor Identifiers (VPID)
> >> (XEN)  - Virtual NMI
> >> (XEN)  - MSR direct-access bitmap
> >> (XEN) HVM: ASIDs enabled.
> >> (XEN) HVM: VMX enabled
> >> (XEN) HVM: Hardware Assisted Paging detected.
> >> (XEN) Intel machine check reporting enabled on CPU#0.
> >> (XEN) CPU0: Thermal monitoring enabled (TM1)
> >> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
> >> (XEN) [VT-D]iommu.c:1063: iommu->reg = ffff82c3fff57000
> >> (XEN) Intel VT-d Snoop Control supported.
> >> (XEN) Intel VT-d DMA Passthrough supported.
> >> (XEN) Intel VT-d Queued Invalidation supported.
> >> (XEN) Intel VT-d Interrupt Remapping not supported.
> >> (XEN) I/O virtualisation enabled
> >> (XEN) I/O virtualisation for PV guests enabled
> >> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping 05
> >> (XEN) Booting processor 1/18 eip 8c000
> >> (XEN) Initializing CPU#1
> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> (XEN) CPU: L2 cache: 256K
> >> (XEN) CPU: L3 cache: 4096K
> >> (XEN) CPU: Physical Processor ID: 1
> >> (XEN) CPU: Processor Core ID: 1
> >> (XEN) HVM: ASIDs enabled.
> >> (XEN) Intel machine check reporting enabled on CPU#1.
> >> (XEN) CPU1: Thermal monitoring enabled (TM1)
> >> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping 05
> >> (XEN) Booting processor 2/20 eip 8c000
> >> (XEN) Initializing CPU#2
> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> (XEN) CPU: L2 cache: 256K
> >> (XEN) CPU: L3 cache: 4096K
> >> (XEN) CPU: Physical Processor ID: 1
> >> (XEN) CPU: Processor Core ID: 2
> >> (XEN) HVM: ASIDs enabled.
> >> (XEN) Intel machine check reporting enabled on CPU#2.
> >> (XEN) CPU2: Thermal monitoring enabled (TM1)
> >> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping 05
> >> (XEN) Booting processor 3/22 eip 8c000
> >> (XEN) Initializing CPU#3
> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> (XEN) CPU: L2 cache: 256K
> >> (XEN) CPU: L3 cache: 4096K
> >> (XEN) CPU: Physical Processor ID: 1
> >> (XEN) CPU: Processor Core ID: 3
> >> (XEN) HVM: ASIDs enabled.
> >> (XEN) Intel machine check reporting enabled on CPU#3.
> >> (XEN) CPU3: Thermal monitoring enabled (TM1)
> >> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping 05
> >> (XEN) Total of 4 processors activated.
> >> (XEN) ENABLING IO-APIC IRQs
> >> (XEN)  ->  Using new ACK method
> >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
> >> (XEN) checking TSC synchronization across 4 CPUs: passed.
> >> (XEN) Platform timer is 14.318MHz HPET
> >> (
> >>    
> > 
> > Ah, I saw the same when using a IPMI SOL implementation; this is the 
> > point when the serial port becomes interrupt-driven, and
there''s
> > something wrong with interrupts.  The fix is this patch from Konrad:
> > 
> > diff -r 8f304c003af4 -r 7863747c5061 xen/drivers/char/ns16550.c
> > --- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009 +0000
> > +++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009 -0800
> > @@ -39,6 +39,7 @@
> >       /* UART with no IRQ line: periodically-polled I/O. */
> >       struct timer timer;
> >       unsigned int timeout_ms;
> > +    int probing, intr_works;
> >   } ns16550_com[2] = { { 0 } };
> > 
> >   /* Register offsets */
> > @@ -127,6 +128,13 @@
> >       struct serial_port *port = dev_id;
> >       struct ns16550 *uart = port->uart;
> > 
> > +    if (uart->intr_works == 0)
> > +    {
> > +        uart->probing = 0;
> > +        uart->intr_works = 1;
> > +        stop_timer(&uart->timer);
> > +    }
> > +
> >       while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
> >       {
> >           char lsr = ns_read_reg(uart, LSR);
> > @@ -143,6 +151,15 @@
> >       struct ns16550 *uart = port->uart;
> >       struct cpu_user_regs *regs = guest_cpu_user_regs();
> > 
> > +    if ( uart->intr_works )
> > +        return;     /* Interrupts work - no more polling */
> > +
> > +    if ( uart->probing ) {
> > +        uart->probing = 0;
> > +        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff )
> > +            return;     /* All bits set - probably no UART present */
> > +    }
> > +
> >       while ( ns_read_reg(uart, LSR)&  LSR_DR )
> >           serial_rx_interrupt(port, regs);
> > 
> > @@ -230,15 +247,14 @@
> > 
> >       serial_async_transmit(port);
> > 
> > +    init_timer(&uart->timer, ns16550_poll, port, 0);
> > +    /* Calculate time to fill RX FIFO and/or empty TX FIFO for
polling.
> > */
> > +    bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> > +    uart->timeout_ms = max_t(
> > +        unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
> > uart->baud);
> > +
> >       if ( uart->irq == 0 )
> > -    {
> > -        /* Polled mode. Calculate time to fill RX FIFO and/or empty
TX
> > FIFO. */
> > -        bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> > -        uart->timeout_ms = max_t(
> > -            unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
> > uart->baud);
> > -        init_timer(&uart->timer, ns16550_poll, port, 0);
> >           set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
> > -    }
> >       else
> >       {
> >           uart->irqaction.handler = ns16550_interrupt;
> > @@ -252,6 +268,12 @@
> > 
> >           /* Enable receive and transmit interrupts. */
> >           ns_write_reg(uart, IER, IER_ERDAI | IER_ETHREI);
> > +
> > +        /* Do a timed write to make sure we are getting interrupts.
*/
> > +        uart->probing = 1;
> > +        uart->intr_works = 0;
> > +        ns_write_reg(uart, THR, 0xff);
> > +        set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
> >       }
> >   }
> > 
> > 
> > 	J
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27608625.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Feb-16 17:49 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

also with this not boot:
menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
 	set root=(hd0,1)
 	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M iommu=passthrough,pv
loglvl=all guest_loglvl=all sync_console console_to_ring com2=56700,8n1
console=com2,vga
 	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy root=LABEL=root-raid ro
console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
 	module /boot/initrd.img-2.6.31.6-xen
 }

Pasi Kärkkäinen wrote:> 
> On Tue, Feb 16, 2010 at 05:56:35AM -0800, Fantu wrote:
>> 
>> I have download update xen from unstable, kernel from git and i try to
>> apply
>> patch but it seems already present
>> I have try to start and log with SOL, this is the full output: 
>> http://old.nabble.com/file/p27608625/logsol.txt logsol.txt 
>> The entry in grub for debug:
>> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>> 	set root=(hd0,1)
>> 	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv
loglvl=all
>> guest_loglvl=all sync_console console_to_ring com2=56700,8n1
>> console=com2,vga
>> 	module /boot/vmlinuz-2.6.31.6-xen root=LABEL=root-raid ro console=hvc0
>> initcall_debug debug loglevel=10 earlyprintk=xen
>> 	module /boot/initrd.img-2.6.31.6-xen
>> }
> 
> So you''re using GRUB2..
> 
> Please check this wiki page:
> http://wiki.xensource.com/xenwiki/XenCommonProblems
> 
> There''s a chapter called "Booting Xen with GRUB2
fails?".
> 
> -- Pasi
> 
>> 
>> Jeremy Fitzhardinge wrote:
>> > 
>> > On 01/08/2010 06:16 AM, Fantu wrote:
>> >> Thanks, i have do, this is all the i see with sol before black
screen
>> >> freeze
>> >> on vga:
>> >>
>> >>   __  __            _  _    ___   ___              _
>> >>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _ __ 
_ __ ___
>> >>    \  // _ \ ''_ \  | || |_| | | | | | |__|
''__/ __| |__| ''_ \| ''__/ _
>> \
>> >>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__| |_) |
| |
>> __/
>> >>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  |
.__/|_|
>> \___|
>> >>                                                        |_|
>> >> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version 4.3.2
(Debian
>> >> 4.3.2-1.1) )0
>> >> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000
>> 20756:4feec90815a0
>> >> (XEN) Command line: dom0_mem=512M iommu=passthrough,pv
com2=57600,8n1
>> >> console=ca
>> >> (XEN) Video information:
>> >> (XEN)  VGA is text mode 80x25, font 8x16
>> >> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
>> >> (XEN) Disc information:
>> >> (XEN)  Found 2 MBR signatures
>> >> (XEN)  Found 2 EDD information structures
>> >> (XEN) Xen-e820 RAM map:
>> >> (XEN)  0000000000000000 - 00000000000a0000 (usable)
>> >> (XEN)  0000000000100000 - 00000000cf699000 (usable)
>> >> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
>> >> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
>> >> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
>> >> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
>> >> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
>> >> (XEN)  0000000100000000 - 0000000330000000 (usable)
>> >> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
>> >> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3          1
INTL
>> >> 20050624)
>> >> (XEN) ACPI: FACS CF6C6000, 0040
>> >> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3          1
DELL
>> >> 1)
>> >> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM  80000001
INTL
>> >> 20061109)
>> >> (XEN) System RAM: 12053MB (12342340kB)
>> >> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
>> >> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
>> >> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
>> >> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
>> >> (XEN) SRAT: Node 0 PXM 1 0-d0000000
>> >> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
>> >> (XEN) NUMA: Using 20 for the hash shift.
>> >> (XEN) Domain heap initialised
>> >> (XEN) found SMP MP-table at 000fe710
>> >> (XEN) DMI 2.6 present.
>> >> (XEN) Using APIC driver default
>> >> (XEN) ACPI: PM-Timer IO Port: 0x808
>> >> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
>> >> (XEN) ACPI:                  wakeup_vec[cf6c600c],
vec_size[20]
>> >> (XEN) ACPI: Local APIC address 0xfee00000
>> >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
>> >> (XEN) Processor #16 7:10 APIC version 21
>> >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
>> >> (XEN) Processor #18 7:10 APIC version 21
>> >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
>> >> (XEN) Processor #20 7:10 APIC version 21
>> >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
>> >> (XEN) Processor #22 7:10 APIC version 21
>> >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
>> >> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
>> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
>> >> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
>> >> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000,
GSI 0-23
>> >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000] gsi_base[32])
>> >> (XEN) IOAPIC[1]: apic_id 1, version 32, address 0xfec80000,
GSI 32-55
>> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
level)
>> >> (XEN) ACPI: IRQ0 used by override.
>> >> (XEN) ACPI: IRQ2 used by override.
>> >> (XEN) ACPI: IRQ9 used by override.
>> >> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
>> >> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
>> >> (XEN) [VT-D]dmar.c:548: Host address width 40
>> >> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
>> >> (XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
>> >> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000
end_address
>> >> cf7dffff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000
end_address
>> >> cf7bffff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000
end_address
>> >> cf7a1fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000
end_address
>> >> cf7a3fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000
end_address
>> >> cf7a5fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000
end_address
>> >> cf7a7fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000
end_address
>> >> cf7a9fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000
end_address
>> >> cf7c0fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000
end_address
>> >> cf7c2fff
>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
>> >> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
>> >> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec = 1 
sub = 1
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec = 3 
sub = 3
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec = 4 
sub = 4
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec = 5 
sub = 5
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec = 6 
sub = 6
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec = 7 
sub = 7
>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec = 2 
sub = 2
>> >> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
>> >> (XEN) PCI: MCFG area at e0000000 reserved in E820
>> >> (XEN) Using ACPI (MADT) for SMP configuration information
>> >> (XEN) Using scheduler: SMP Credit Scheduler (credit)
>> >> (XEN) Initializing CPU#0
>> >> (XEN) Detected 1995.045 MHz processor.
>> >> (XEN) Initing memory sharing.
>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> >> (XEN) CPU: L2 cache: 256K
>> >> (XEN) CPU: L3 cache: 4096K
>> >> (XEN) CPU: Physical Processor ID: 1
>> >> (XEN) CPU: Processor Core ID: 0
>> >> (XEN) VMX: Supported advanced features:
>> >> (XEN)  - APIC MMIO access virtualisation
>> >> (XEN)  - APIC TPR shadow
>> >> (XEN)  - Extended Page Tables (EPT)
>> >> (XEN)  - Virtual-Processor Identifiers (VPID)
>> >> (XEN)  - Virtual NMI
>> >> (XEN)  - MSR direct-access bitmap
>> >> (XEN) HVM: ASIDs enabled.
>> >> (XEN) HVM: VMX enabled
>> >> (XEN) HVM: Hardware Assisted Paging detected.
>> >> (XEN) Intel machine check reporting enabled on CPU#0.
>> >> (XEN) CPU0: Thermal monitoring enabled (TM1)
>> >> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
>> >> (XEN) [VT-D]iommu.c:1063: iommu->reg = ffff82c3fff57000
>> >> (XEN) Intel VT-d Snoop Control supported.
>> >> (XEN) Intel VT-d DMA Passthrough supported.
>> >> (XEN) Intel VT-d Queued Invalidation supported.
>> >> (XEN) Intel VT-d Interrupt Remapping not supported.
>> >> (XEN) I/O virtualisation enabled
>> >> (XEN) I/O virtualisation for PV guests enabled
>> >> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping
>> 05
>> >> (XEN) Booting processor 1/18 eip 8c000
>> >> (XEN) Initializing CPU#1
>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> >> (XEN) CPU: L2 cache: 256K
>> >> (XEN) CPU: L3 cache: 4096K
>> >> (XEN) CPU: Physical Processor ID: 1
>> >> (XEN) CPU: Processor Core ID: 1
>> >> (XEN) HVM: ASIDs enabled.
>> >> (XEN) Intel machine check reporting enabled on CPU#1.
>> >> (XEN) CPU1: Thermal monitoring enabled (TM1)
>> >> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping
>> 05
>> >> (XEN) Booting processor 2/20 eip 8c000
>> >> (XEN) Initializing CPU#2
>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> >> (XEN) CPU: L2 cache: 256K
>> >> (XEN) CPU: L3 cache: 4096K
>> >> (XEN) CPU: Physical Processor ID: 1
>> >> (XEN) CPU: Processor Core ID: 2
>> >> (XEN) HVM: ASIDs enabled.
>> >> (XEN) Intel machine check reporting enabled on CPU#2.
>> >> (XEN) CPU2: Thermal monitoring enabled (TM1)
>> >> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping
>> 05
>> >> (XEN) Booting processor 3/22 eip 8c000
>> >> (XEN) Initializing CPU#3
>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>> >> (XEN) CPU: L2 cache: 256K
>> >> (XEN) CPU: L3 cache: 4096K
>> >> (XEN) CPU: Physical Processor ID: 1
>> >> (XEN) CPU: Processor Core ID: 3
>> >> (XEN) HVM: ASIDs enabled.
>> >> (XEN) Intel machine check reporting enabled on CPU#3.
>> >> (XEN) CPU3: Thermal monitoring enabled (TM1)
>> >> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz
stepping
>> 05
>> >> (XEN) Total of 4 processors activated.
>> >> (XEN) ENABLING IO-APIC IRQs
>> >> (XEN)  ->  Using new ACK method
>> >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
>> >> (XEN) checking TSC synchronization across 4 CPUs: passed.
>> >> (XEN) Platform timer is 14.318MHz HPET
>> >> (
>> >>    
>> > 
>> > Ah, I saw the same when using a IPMI SOL implementation; this is
the
>> > point when the serial port becomes interrupt-driven, and
there''s
>> > something wrong with interrupts.  The fix is this patch from
Konrad:
>> > 
>> > diff -r 8f304c003af4 -r 7863747c5061 xen/drivers/char/ns16550.c
>> > --- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009 +0000
>> > +++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009 -0800
>> > @@ -39,6 +39,7 @@
>> >       /* UART with no IRQ line: periodically-polled I/O. */
>> >       struct timer timer;
>> >       unsigned int timeout_ms;
>> > +    int probing, intr_works;
>> >   } ns16550_com[2] = { { 0 } };
>> > 
>> >   /* Register offsets */
>> > @@ -127,6 +128,13 @@
>> >       struct serial_port *port = dev_id;
>> >       struct ns16550 *uart = port->uart;
>> > 
>> > +    if (uart->intr_works == 0)
>> > +    {
>> > +        uart->probing = 0;
>> > +        uart->intr_works = 1;
>> > +        stop_timer(&uart->timer);
>> > +    }
>> > +
>> >       while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
>> >       {
>> >           char lsr = ns_read_reg(uart, LSR);
>> > @@ -143,6 +151,15 @@
>> >       struct ns16550 *uart = port->uart;
>> >       struct cpu_user_regs *regs = guest_cpu_user_regs();
>> > 
>> > +    if ( uart->intr_works )
>> > +        return;     /* Interrupts work - no more polling */
>> > +
>> > +    if ( uart->probing ) {
>> > +        uart->probing = 0;
>> > +        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff )
>> > +            return;     /* All bits set - probably no UART
present */
>> > +    }
>> > +
>> >       while ( ns_read_reg(uart, LSR)&  LSR_DR )
>> >           serial_rx_interrupt(port, regs);
>> > 
>> > @@ -230,15 +247,14 @@
>> > 
>> >       serial_async_transmit(port);
>> > 
>> > +    init_timer(&uart->timer, ns16550_poll, port, 0);
>> > +    /* Calculate time to fill RX FIFO and/or empty TX FIFO for
>> polling.
>> > */
>> > +    bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
>> > +    uart->timeout_ms = max_t(
>> > +        unsigned int, 1, (bits * port->tx_fifo_size * 1000) /
>> > uart->baud);
>> > +
>> >       if ( uart->irq == 0 )
>> > -    {
>> > -        /* Polled mode. Calculate time to fill RX FIFO and/or
empty TX
>> > FIFO. */
>> > -        bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
>> > -        uart->timeout_ms = max_t(
>> > -            unsigned int, 1, (bits * port->tx_fifo_size *
1000) /
>> > uart->baud);
>> > -        init_timer(&uart->timer, ns16550_poll, port, 0);
>> >           set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
>> > -    }
>> >       else
>> >       {
>> >           uart->irqaction.handler = ns16550_interrupt;
>> > @@ -252,6 +268,12 @@
>> > 
>> >           /* Enable receive and transmit interrupts. */
>> >           ns_write_reg(uart, IER, IER_ERDAI | IER_ETHREI);
>> > +
>> > +        /* Do a timed write to make sure we are getting
interrupts. */
>> > +        uart->probing = 1;
>> > +        uart->intr_works = 0;
>> > +        ns_write_reg(uart, THR, 0xff);
>> > +        set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
>> >       }
>> >   }
>> > 
>> > 
>> > 	J
>> > 
>> > 
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel
>> > 
>> > 
>> 
>> -- 
>> View this message in context:
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27608625.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27612307.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Feb-16 18:31 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Tue, Feb 16, 2010 at 09:49:42AM -0800, Fantu wrote:> 
> also with this not boot:
> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>  	set root=(hd0,1)
>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M iommu=passthrough,pv
> loglvl=all guest_loglvl=all sync_console console_to_ring com2=56700,8n1
> console=com2,vga
>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy root=LABEL=root-raid ro
> console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
>  	module /boot/initrd.img-2.6.31.6-xen
>  }
>
What''s the full serial console output when using the grub config above?

-- Pasi
> 
> Pasi Kärkkäinen wrote:
> > 
> > On Tue, Feb 16, 2010 at 05:56:35AM -0800, Fantu wrote:
> >> 
> >> I have download update xen from unstable, kernel from git and i
try to
> >> apply
> >> patch but it seems already present
> >> I have try to start and log with SOL, this is the full output: 
> >> http://old.nabble.com/file/p27608625/logsol.txt logsol.txt 
> >> The entry in grub for debug:
> >> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> >> 	set root=(hd0,1)
> >> 	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv
loglvl=all
> >> guest_loglvl=all sync_console console_to_ring com2=56700,8n1
> >> console=com2,vga
> >> 	module /boot/vmlinuz-2.6.31.6-xen root=LABEL=root-raid ro
console=hvc0
> >> initcall_debug debug loglevel=10 earlyprintk=xen
> >> 	module /boot/initrd.img-2.6.31.6-xen
> >> }
> > 
> > So you''re using GRUB2..
> > 
> > Please check this wiki page:
> > http://wiki.xensource.com/xenwiki/XenCommonProblems
> > 
> > There''s a chapter called "Booting Xen with GRUB2
fails?".
> > 
> > -- Pasi
> > 
> >> 
> >> Jeremy Fitzhardinge wrote:
> >> > 
> >> > On 01/08/2010 06:16 AM, Fantu wrote:
> >> >> Thanks, i have do, this is all the i see with sol before
black screen
> >> >> freeze
> >> >> on vga:
> >> >>
> >> >>   __  __            _  _    ___   ___              _
> >> >>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _
__  _ __ ___
> >> >>    \  // _ \ ''_ \  | || |_| | | | | | |__|
''__/ __| |__| ''_ \| ''__/ _
> >> \
> >> >>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__|
|_) | | |
> >> __/
> >> >>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  |
.__/|_|
> >> \___|
> >> >>                                                       
|_|
> >> >> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version
4.3.2 (Debian
> >> >> 4.3.2-1.1) )0
> >> >> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000
> >> 20756:4feec90815a0
> >> >> (XEN) Command line: dom0_mem=512M iommu=passthrough,pv
com2=57600,8n1
> >> >> console=ca
> >> >> (XEN) Video information:
> >> >> (XEN)  VGA is text mode 80x25, font 8x16
> >> >> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
> >> >> (XEN) Disc information:
> >> >> (XEN)  Found 2 MBR signatures
> >> >> (XEN)  Found 2 EDD information structures
> >> >> (XEN) Xen-e820 RAM map:
> >> >> (XEN)  0000000000000000 - 00000000000a0000 (usable)
> >> >> (XEN)  0000000000100000 - 00000000cf699000 (usable)
> >> >> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
> >> >> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
> >> >> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
> >> >> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> >> >> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
> >> >> (XEN)  0000000100000000 - 0000000330000000 (usable)
> >> >> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
> >> >> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3        
1 INTL
> >> >> 20050624)
> >> >> (XEN) ACPI: FACS CF6C6000, 0040
> >> >> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3        
1 DELL
> >> >> 1)
> >> >> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM 
80000001 INTL
> >> >> 20061109)
> >> >> (XEN) System RAM: 12053MB (12342340kB)
> >> >> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
> >> >> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
> >> >> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
> >> >> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
> >> >> (XEN) SRAT: Node 0 PXM 1 0-d0000000
> >> >> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
> >> >> (XEN) NUMA: Using 20 for the hash shift.
> >> >> (XEN) Domain heap initialised
> >> >> (XEN) found SMP MP-table at 000fe710
> >> >> (XEN) DMI 2.6 present.
> >> >> (XEN) Using APIC driver default
> >> >> (XEN) ACPI: PM-Timer IO Port: 0x808
> >> >> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0],
pm1x_evt[800,0]
> >> >> (XEN) ACPI:                  wakeup_vec[cf6c600c],
vec_size[20]
> >> >> (XEN) ACPI: Local APIC address 0xfee00000
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
> >> >> (XEN) Processor #16 7:10 APIC version 21
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
> >> >> (XEN) Processor #18 7:10 APIC version 21
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
> >> >> (XEN) Processor #20 7:10 APIC version 21
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
> >> >> (XEN) Processor #22 7:10 APIC version 21
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
> >> >> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
> >> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
> >> >> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000]
gsi_base[0])
> >> >> (XEN) IOAPIC[0]: apic_id 0, version 32, address
0xfec00000, GSI 0-23
> >> >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000]
gsi_base[32])
> >> >> (XEN) IOAPIC[1]: apic_id 1, version 32, address
0xfec80000, GSI 32-55
> >> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl
dfl)
> >> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9
high level)
> >> >> (XEN) ACPI: IRQ0 used by override.
> >> >> (XEN) ACPI: IRQ2 used by override.
> >> >> (XEN) ACPI: IRQ9 used by override.
> >> >> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
> >> >> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
> >> >> (XEN) [VT-D]dmar.c:548: Host address width 40
> >> >> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
> >> >> (XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
> >> >> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000
end_address
> >> >> cf7dffff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000
end_address
> >> >> cf7bffff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000
end_address
> >> >> cf7a1fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000
end_address
> >> >> cf7a3fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000
end_address
> >> >> cf7a5fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000
end_address
> >> >> cf7a7fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000
end_address
> >> >> cf7a9fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000
end_address
> >> >> cf7c0fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> >> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000
end_address
> >> >> cf7c2fff
> >> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> >> >> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
> >> >> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec =
1  sub = 1
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec =
3  sub = 3
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec =
4  sub = 4
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec =
5  sub = 5
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec =
6  sub = 6
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec =
7  sub = 7
> >> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec =
2  sub = 2
> >> >> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0
buses 0 - 255
> >> >> (XEN) PCI: MCFG area at e0000000 reserved in E820
> >> >> (XEN) Using ACPI (MADT) for SMP configuration information
> >> >> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> >> >> (XEN) Initializing CPU#0
> >> >> (XEN) Detected 1995.045 MHz processor.
> >> >> (XEN) Initing memory sharing.
> >> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> >> (XEN) CPU: L2 cache: 256K
> >> >> (XEN) CPU: L3 cache: 4096K
> >> >> (XEN) CPU: Physical Processor ID: 1
> >> >> (XEN) CPU: Processor Core ID: 0
> >> >> (XEN) VMX: Supported advanced features:
> >> >> (XEN)  - APIC MMIO access virtualisation
> >> >> (XEN)  - APIC TPR shadow
> >> >> (XEN)  - Extended Page Tables (EPT)
> >> >> (XEN)  - Virtual-Processor Identifiers (VPID)
> >> >> (XEN)  - Virtual NMI
> >> >> (XEN)  - MSR direct-access bitmap
> >> >> (XEN) HVM: ASIDs enabled.
> >> >> (XEN) HVM: VMX enabled
> >> >> (XEN) HVM: Hardware Assisted Paging detected.
> >> >> (XEN) Intel machine check reporting enabled on CPU#0.
> >> >> (XEN) CPU0: Thermal monitoring enabled (TM1)
> >> >> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
> >> >> (XEN) [VT-D]iommu.c:1063: iommu->reg =
ffff82c3fff57000
> >> >> (XEN) Intel VT-d Snoop Control supported.
> >> >> (XEN) Intel VT-d DMA Passthrough supported.
> >> >> (XEN) Intel VT-d Queued Invalidation supported.
> >> >> (XEN) Intel VT-d Interrupt Remapping not supported.
> >> >> (XEN) I/O virtualisation enabled
> >> >> (XEN) I/O virtualisation for PV guests enabled
> >> >> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >> 05
> >> >> (XEN) Booting processor 1/18 eip 8c000
> >> >> (XEN) Initializing CPU#1
> >> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> >> (XEN) CPU: L2 cache: 256K
> >> >> (XEN) CPU: L3 cache: 4096K
> >> >> (XEN) CPU: Physical Processor ID: 1
> >> >> (XEN) CPU: Processor Core ID: 1
> >> >> (XEN) HVM: ASIDs enabled.
> >> >> (XEN) Intel machine check reporting enabled on CPU#1.
> >> >> (XEN) CPU1: Thermal monitoring enabled (TM1)
> >> >> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >> 05
> >> >> (XEN) Booting processor 2/20 eip 8c000
> >> >> (XEN) Initializing CPU#2
> >> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> >> (XEN) CPU: L2 cache: 256K
> >> >> (XEN) CPU: L3 cache: 4096K
> >> >> (XEN) CPU: Physical Processor ID: 1
> >> >> (XEN) CPU: Processor Core ID: 2
> >> >> (XEN) HVM: ASIDs enabled.
> >> >> (XEN) Intel machine check reporting enabled on CPU#2.
> >> >> (XEN) CPU2: Thermal monitoring enabled (TM1)
> >> >> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >> 05
> >> >> (XEN) Booting processor 3/22 eip 8c000
> >> >> (XEN) Initializing CPU#3
> >> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >> >> (XEN) CPU: L2 cache: 256K
> >> >> (XEN) CPU: L3 cache: 4096K
> >> >> (XEN) CPU: Physical Processor ID: 1
> >> >> (XEN) CPU: Processor Core ID: 3
> >> >> (XEN) HVM: ASIDs enabled.
> >> >> (XEN) Intel machine check reporting enabled on CPU#3.
> >> >> (XEN) CPU3: Thermal monitoring enabled (TM1)
> >> >> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >> 05
> >> >> (XEN) Total of 4 processors activated.
> >> >> (XEN) ENABLING IO-APIC IRQs
> >> >> (XEN)  ->  Using new ACK method
> >> >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1
pin2=-1
> >> >> (XEN) checking TSC synchronization across 4 CPUs: passed.
> >> >> (XEN) Platform timer is 14.318MHz HPET
> >> >> (
> >> >>    
> >> > 
> >> > Ah, I saw the same when using a IPMI SOL implementation; this
is the
> >> > point when the serial port becomes interrupt-driven, and
there''s
> >> > something wrong with interrupts.  The fix is this patch from
Konrad:
> >> > 
> >> > diff -r 8f304c003af4 -r 7863747c5061
xen/drivers/char/ns16550.c
> >> > --- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009
+0000
> >> > +++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009
-0800
> >> > @@ -39,6 +39,7 @@
> >> >       /* UART with no IRQ line: periodically-polled I/O. */
> >> >       struct timer timer;
> >> >       unsigned int timeout_ms;
> >> > +    int probing, intr_works;
> >> >   } ns16550_com[2] = { { 0 } };
> >> > 
> >> >   /* Register offsets */
> >> > @@ -127,6 +128,13 @@
> >> >       struct serial_port *port = dev_id;
> >> >       struct ns16550 *uart = port->uart;
> >> > 
> >> > +    if (uart->intr_works == 0)
> >> > +    {
> >> > +        uart->probing = 0;
> >> > +        uart->intr_works = 1;
> >> > +        stop_timer(&uart->timer);
> >> > +    }
> >> > +
> >> >       while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
> >> >       {
> >> >           char lsr = ns_read_reg(uart, LSR);
> >> > @@ -143,6 +151,15 @@
> >> >       struct ns16550 *uart = port->uart;
> >> >       struct cpu_user_regs *regs = guest_cpu_user_regs();
> >> > 
> >> > +    if ( uart->intr_works )
> >> > +        return;     /* Interrupts work - no more polling */
> >> > +
> >> > +    if ( uart->probing ) {
> >> > +        uart->probing = 0;
> >> > +        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff )
> >> > +            return;     /* All bits set - probably no UART
present */
> >> > +    }
> >> > +
> >> >       while ( ns_read_reg(uart, LSR)&  LSR_DR )
> >> >           serial_rx_interrupt(port, regs);
> >> > 
> >> > @@ -230,15 +247,14 @@
> >> > 
> >> >       serial_async_transmit(port);
> >> > 
> >> > +    init_timer(&uart->timer, ns16550_poll, port, 0);
> >> > +    /* Calculate time to fill RX FIFO and/or empty TX FIFO
for
> >> polling.
> >> > */
> >> > +    bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> >> > +    uart->timeout_ms = max_t(
> >> > +        unsigned int, 1, (bits * port->tx_fifo_size *
1000) /
> >> > uart->baud);
> >> > +
> >> >       if ( uart->irq == 0 )
> >> > -    {
> >> > -        /* Polled mode. Calculate time to fill RX FIFO
and/or empty TX
> >> > FIFO. */
> >> > -        bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> >> > -        uart->timeout_ms = max_t(
> >> > -            unsigned int, 1, (bits * port->tx_fifo_size *
1000) /
> >> > uart->baud);
> >> > -        init_timer(&uart->timer, ns16550_poll, port,
0);
> >> >           set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
> >> > -    }
> >> >       else
> >> >       {
> >> >           uart->irqaction.handler = ns16550_interrupt;
> >> > @@ -252,6 +268,12 @@
> >> > 
> >> >           /* Enable receive and transmit interrupts. */
> >> >           ns_write_reg(uart, IER, IER_ERDAI | IER_ETHREI);
> >> > +
> >> > +        /* Do a timed write to make sure we are getting
interrupts. */
> >> > +        uart->probing = 1;
> >> > +        uart->intr_works = 0;
> >> > +        ns_write_reg(uart, THR, 0xff);
> >> > +        set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
> >> >       }
> >> >   }
> >> > 
> >> > 
> >> > 	J
> >> > 
> >> > 
> >> > _______________________________________________
> >> > Xen-devel mailing list
> >> > Xen-devel@lists.xensource.com
> >> > http://lists.xensource.com/xen-devel
> >> > 
> >> > 
> >> 
> >> -- 
> >> View this message in context:
> >>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27608625.html
> >> Sent from the Xen - Dev mailing list archive at Nabble.com.
> >> 
> >> 
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27612307.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Feb-24 08:39 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

I have reupdate xen and kernel and redo debug with also dummy=dummy and this
is the sol log:  http://old.nabble.com/file/p27714129/sol2.txt sol2.txt 

Fantu wrote:> 
> also with this not boot:
> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>  	set root=(hd0,1)
>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M iommu=passthrough,pv
> loglvl=all guest_loglvl=all sync_console console_to_ring com2=56700,8n1
> console=com2,vga
>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy root=LABEL=root-raid ro
> console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
>  	module /boot/initrd.img-2.6.31.6-xen
>  }
> 
> Pasi Kärkkäinen wrote:
>> 
>> On Tue, Feb 16, 2010 at 05:56:35AM -0800, Fantu wrote:
>>> 
>>> I have download update xen from unstable, kernel from git and i try
to
>>> apply
>>> patch but it seems already present
>>> I have try to start and log with SOL, this is the full output: 
>>> http://old.nabble.com/file/p27608625/logsol.txt logsol.txt 
>>> The entry in grub for debug:
>>> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>>> 	set root=(hd0,1)
>>> 	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv
loglvl=all
>>> guest_loglvl=all sync_console console_to_ring com2=56700,8n1
>>> console=com2,vga
>>> 	module /boot/vmlinuz-2.6.31.6-xen root=LABEL=root-raid ro
console=hvc0
>>> initcall_debug debug loglevel=10 earlyprintk=xen
>>> 	module /boot/initrd.img-2.6.31.6-xen
>>> }
>> 
>> So you''re using GRUB2..
>> 
>> Please check this wiki page:
>> http://wiki.xensource.com/xenwiki/XenCommonProblems
>> 
>> There''s a chapter called "Booting Xen with GRUB2
fails?".
>> 
>> -- Pasi
>> 
>>> 
>>> Jeremy Fitzhardinge wrote:
>>> > 
>>> > On 01/08/2010 06:16 AM, Fantu wrote:
>>> >> Thanks, i have do, this is all the i see with sol before
black screen
>>> >> freeze
>>> >> on vga:
>>> >>
>>> >>   __  __            _  _    ___   ___              _
>>> >>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |   _
__  _ __
>>> ___
>>> >>    \  // _ \ ''_ \  | || |_| | | | | | |__|
''__/ __| |__| ''_ \| ''__/ _
>>> \
>>> >>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__| |__|
|_) | | |
>>> __/
>>> >>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|  |
.__/|_|
>>> \___|
>>> >>                                                        |_|
>>> >> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version 4.3.2
(Debian
>>> >> 4.3.2-1.1) )0
>>> >> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010 +0000
>>> 20756:4feec90815a0
>>> >> (XEN) Command line: dom0_mem=512M iommu=passthrough,pv
com2=57600,8n1
>>> >> console=ca
>>> >> (XEN) Video information:
>>> >> (XEN)  VGA is text mode 80x25, font 8x16
>>> >> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
>>> >> (XEN) Disc information:
>>> >> (XEN)  Found 2 MBR signatures
>>> >> (XEN)  Found 2 EDD information structures
>>> >> (XEN) Xen-e820 RAM map:
>>> >> (XEN)  0000000000000000 - 00000000000a0000 (usable)
>>> >> (XEN)  0000000000100000 - 00000000cf699000 (usable)
>>> >> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
>>> >> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI data)
>>> >> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
>>> >> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
>>> >> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
>>> >> (XEN)  0000000100000000 - 0000000330000000 (usable)
>>> >> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
>>> >> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3         
1 INTL
>>> >> 20050624)
>>> >> (XEN) ACPI: FACS CF6C6000, 0040
>>> >> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3         
1 DELL
>>> >> 1)
>>> >> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM 
80000001 INTL
>>> >> 20061109)
>>> >> (XEN) System RAM: 12053MB (12342340kB)
>>> >> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
>>> >> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
>>> >> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
>>> >> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
>>> >> (XEN) SRAT: Node 0 PXM 1 0-d0000000
>>> >> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
>>> >> (XEN) NUMA: Using 20 for the hash shift.
>>> >> (XEN) Domain heap initialised
>>> >> (XEN) found SMP MP-table at 000fe710
>>> >> (XEN) DMI 2.6 present.
>>> >> (XEN) Using APIC driver default
>>> >> (XEN) ACPI: PM-Timer IO Port: 0x808
>>> >> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0],
pm1x_evt[800,0]
>>> >> (XEN) ACPI:                  wakeup_vec[cf6c600c],
vec_size[20]
>>> >> (XEN) ACPI: Local APIC address 0xfee00000
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
>>> >> (XEN) Processor #16 7:10 APIC version 21
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
>>> >> (XEN) Processor #18 7:10 APIC version 21
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14] enabled)
>>> >> (XEN) Processor #20 7:10 APIC version 21
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16] enabled)
>>> >> (XEN) Processor #22 7:10 APIC version 21
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
>>> >> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
>>> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
>>> >> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000]
gsi_base[0])
>>> >> (XEN) IOAPIC[0]: apic_id 0, version 32, address
0xfec00000, GSI 0-23
>>> >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000]
gsi_base[32])
>>> >> (XEN) IOAPIC[1]: apic_id 1, version 32, address
0xfec80000, GSI 32-55
>>> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl
dfl)
>>> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
level)
>>> >> (XEN) ACPI: IRQ0 used by override.
>>> >> (XEN) ACPI: IRQ2 used by override.
>>> >> (XEN) ACPI: IRQ9 used by override.
>>> >> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
>>> >> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
>>> >> (XEN) [VT-D]dmar.c:548: Host address width 40
>>> >> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
>>> >> (XEN) [VT-D]dmar.c:374:   dmaru->address = fed90000
>>> >> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c8000
end_address
>>> >> cf7dffff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7b1000
end_address
>>> >> cf7bffff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a1000
end_address
>>> >> cf7a1fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a3000
end_address
>>> >> cf7a3fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a5000
end_address
>>> >> cf7a5fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a7000
end_address
>>> >> cf7a7fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7a9000
end_address
>>> >> cf7a9fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c0000
end_address
>>> >> cf7c0fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
>>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
>>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr cf7c2000
end_address
>>> >> cf7c2fff
>>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
>>> >> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
>>> >> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0 sec = 1
sub = 1
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0 sec = 3
sub = 3
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0 sec = 4
sub = 4
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0 sec = 5
sub = 5
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0 sec = 6
sub = 6
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0 sec = 7
sub = 7
>>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0 sec = 2
sub = 2
>>> >> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0
buses 0 -
>>> 255
>>> >> (XEN) PCI: MCFG area at e0000000 reserved in E820
>>> >> (XEN) Using ACPI (MADT) for SMP configuration information
>>> >> (XEN) Using scheduler: SMP Credit Scheduler (credit)
>>> >> (XEN) Initializing CPU#0
>>> >> (XEN) Detected 1995.045 MHz processor.
>>> >> (XEN) Initing memory sharing.
>>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>> >> (XEN) CPU: L2 cache: 256K
>>> >> (XEN) CPU: L3 cache: 4096K
>>> >> (XEN) CPU: Physical Processor ID: 1
>>> >> (XEN) CPU: Processor Core ID: 0
>>> >> (XEN) VMX: Supported advanced features:
>>> >> (XEN)  - APIC MMIO access virtualisation
>>> >> (XEN)  - APIC TPR shadow
>>> >> (XEN)  - Extended Page Tables (EPT)
>>> >> (XEN)  - Virtual-Processor Identifiers (VPID)
>>> >> (XEN)  - Virtual NMI
>>> >> (XEN)  - MSR direct-access bitmap
>>> >> (XEN) HVM: ASIDs enabled.
>>> >> (XEN) HVM: VMX enabled
>>> >> (XEN) HVM: Hardware Assisted Paging detected.
>>> >> (XEN) Intel machine check reporting enabled on CPU#0.
>>> >> (XEN) CPU0: Thermal monitoring enabled (TM1)
>>> >> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
>>> >> (XEN) [VT-D]iommu.c:1063: iommu->reg = ffff82c3fff57000
>>> >> (XEN) Intel VT-d Snoop Control supported.
>>> >> (XEN) Intel VT-d DMA Passthrough supported.
>>> >> (XEN) Intel VT-d Queued Invalidation supported.
>>> >> (XEN) Intel VT-d Interrupt Remapping not supported.
>>> >> (XEN) I/O virtualisation enabled
>>> >> (XEN) I/O virtualisation for PV guests enabled
>>> >> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
>>> 05
>>> >> (XEN) Booting processor 1/18 eip 8c000
>>> >> (XEN) Initializing CPU#1
>>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>> >> (XEN) CPU: L2 cache: 256K
>>> >> (XEN) CPU: L3 cache: 4096K
>>> >> (XEN) CPU: Physical Processor ID: 1
>>> >> (XEN) CPU: Processor Core ID: 1
>>> >> (XEN) HVM: ASIDs enabled.
>>> >> (XEN) Intel machine check reporting enabled on CPU#1.
>>> >> (XEN) CPU1: Thermal monitoring enabled (TM1)
>>> >> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
>>> 05
>>> >> (XEN) Booting processor 2/20 eip 8c000
>>> >> (XEN) Initializing CPU#2
>>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>> >> (XEN) CPU: L2 cache: 256K
>>> >> (XEN) CPU: L3 cache: 4096K
>>> >> (XEN) CPU: Physical Processor ID: 1
>>> >> (XEN) CPU: Processor Core ID: 2
>>> >> (XEN) HVM: ASIDs enabled.
>>> >> (XEN) Intel machine check reporting enabled on CPU#2.
>>> >> (XEN) CPU2: Thermal monitoring enabled (TM1)
>>> >> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
>>> 05
>>> >> (XEN) Booting processor 3/22 eip 8c000
>>> >> (XEN) Initializing CPU#3
>>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
>>> >> (XEN) CPU: L2 cache: 256K
>>> >> (XEN) CPU: L3 cache: 4096K
>>> >> (XEN) CPU: Physical Processor ID: 1
>>> >> (XEN) CPU: Processor Core ID: 3
>>> >> (XEN) HVM: ASIDs enabled.
>>> >> (XEN) Intel machine check reporting enabled on CPU#3.
>>> >> (XEN) CPU3: Thermal monitoring enabled (TM1)
>>> >> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
>>> 05
>>> >> (XEN) Total of 4 processors activated.
>>> >> (XEN) ENABLING IO-APIC IRQs
>>> >> (XEN)  ->  Using new ACK method
>>> >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
>>> >> (XEN) checking TSC synchronization across 4 CPUs: passed.
>>> >> (XEN) Platform timer is 14.318MHz HPET
>>> >> (
>>> >>    
>>> > 
>>> > Ah, I saw the same when using a IPMI SOL implementation; this
is the
>>> > point when the serial port becomes interrupt-driven, and
there''s
>>> > something wrong with interrupts.  The fix is this patch from
Konrad:
>>> > 
>>> > diff -r 8f304c003af4 -r 7863747c5061
xen/drivers/char/ns16550.c
>>> > --- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009
+0000
>>> > +++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009
-0800
>>> > @@ -39,6 +39,7 @@
>>> >       /* UART with no IRQ line: periodically-polled I/O. */
>>> >       struct timer timer;
>>> >       unsigned int timeout_ms;
>>> > +    int probing, intr_works;
>>> >   } ns16550_com[2] = { { 0 } };
>>> > 
>>> >   /* Register offsets */
>>> > @@ -127,6 +128,13 @@
>>> >       struct serial_port *port = dev_id;
>>> >       struct ns16550 *uart = port->uart;
>>> > 
>>> > +    if (uart->intr_works == 0)
>>> > +    {
>>> > +        uart->probing = 0;
>>> > +        uart->intr_works = 1;
>>> > +        stop_timer(&uart->timer);
>>> > +    }
>>> > +
>>> >       while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
>>> >       {
>>> >           char lsr = ns_read_reg(uart, LSR);
>>> > @@ -143,6 +151,15 @@
>>> >       struct ns16550 *uart = port->uart;
>>> >       struct cpu_user_regs *regs = guest_cpu_user_regs();
>>> > 
>>> > +    if ( uart->intr_works )
>>> > +        return;     /* Interrupts work - no more polling */
>>> > +
>>> > +    if ( uart->probing ) {
>>> > +        uart->probing = 0;
>>> > +        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff )
>>> > +            return;     /* All bits set - probably no UART
present */
>>> > +    }
>>> > +
>>> >       while ( ns_read_reg(uart, LSR)&  LSR_DR )
>>> >           serial_rx_interrupt(port, regs);
>>> > 
>>> > @@ -230,15 +247,14 @@
>>> > 
>>> >       serial_async_transmit(port);
>>> > 
>>> > +    init_timer(&uart->timer, ns16550_poll, port, 0);
>>> > +    /* Calculate time to fill RX FIFO and/or empty TX FIFO
for
>>> polling.
>>> > */
>>> > +    bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
>>> > +    uart->timeout_ms = max_t(
>>> > +        unsigned int, 1, (bits * port->tx_fifo_size *
1000) /
>>> > uart->baud);
>>> > +
>>> >       if ( uart->irq == 0 )
>>> > -    {
>>> > -        /* Polled mode. Calculate time to fill RX FIFO and/or
empty
>>> TX
>>> > FIFO. */
>>> > -        bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
>>> > -        uart->timeout_ms = max_t(
>>> > -            unsigned int, 1, (bits * port->tx_fifo_size *
1000) /
>>> > uart->baud);
>>> > -        init_timer(&uart->timer, ns16550_poll, port,
0);
>>> >           set_timer(&uart->timer, NOW() +
>>> MILLISECS(uart->timeout_ms));
>>> > -    }
>>> >       else
>>> >       {
>>> >           uart->irqaction.handler = ns16550_interrupt;
>>> > @@ -252,6 +268,12 @@
>>> > 
>>> >           /* Enable receive and transmit interrupts. */
>>> >           ns_write_reg(uart, IER, IER_ERDAI | IER_ETHREI);
>>> > +
>>> > +        /* Do a timed write to make sure we are getting
interrupts.
>>> */
>>> > +        uart->probing = 1;
>>> > +        uart->intr_works = 0;
>>> > +        ns_write_reg(uart, THR, 0xff);
>>> > +        set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
>>> >       }
>>> >   }
>>> > 
>>> > 
>>> > 	J
>>> > 
>>> > 
>>> > _______________________________________________
>>> > Xen-devel mailing list
>>> > Xen-devel@lists.xensource.com
>>> > http://lists.xensource.com/xen-devel
>>> > 
>>> > 
>>> 
>>> -- 
>>> View this message in context:
>>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27608625.html
>>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>> 
>> 
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27714129.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Feb-24 08:59 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Wed, Feb 24, 2010 at 12:39:28AM -0800, Fantu wrote:> 
> I have reupdate xen and kernel and redo debug with also dummy=dummy and
this
> is the sol log:  http://old.nabble.com/file/p27714129/sol2.txt sol2.txt 
> 
(XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.

Does that ring any bells? IRQ 0 is the system timer..

-- Pasi
> Fantu wrote:
> > 
> > also with this not boot:
> > menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> >  	set root=(hd0,1)
> >  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M
iommu=passthrough,pv
> > loglvl=all guest_loglvl=all sync_console console_to_ring
com2=56700,8n1
> > console=com2,vga
> >  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy root=LABEL=root-raid
ro
> > console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
> >  	module /boot/initrd.img-2.6.31.6-xen
> >  }
> > 
> > Pasi Kärkkäinen wrote:
> >> 
> >> On Tue, Feb 16, 2010 at 05:56:35AM -0800, Fantu wrote:
> >>> 
> >>> I have download update xen from unstable, kernel from git and
i try to
> >>> apply
> >>> patch but it seems already present
> >>> I have try to start and log with SOL, this is the full output:
> >>> http://old.nabble.com/file/p27608625/logsol.txt logsol.txt 
> >>> The entry in grub for debug:
> >>> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> >>> 	set root=(hd0,1)
> >>> 	multiboot /boot/xen-4.gz dom0_mem=1024M iommu=passthrough,pv
loglvl=all
> >>> guest_loglvl=all sync_console console_to_ring com2=56700,8n1
> >>> console=com2,vga
> >>> 	module /boot/vmlinuz-2.6.31.6-xen root=LABEL=root-raid ro
console=hvc0
> >>> initcall_debug debug loglevel=10 earlyprintk=xen
> >>> 	module /boot/initrd.img-2.6.31.6-xen
> >>> }
> >> 
> >> So you''re using GRUB2..
> >> 
> >> Please check this wiki page:
> >> http://wiki.xensource.com/xenwiki/XenCommonProblems
> >> 
> >> There''s a chapter called "Booting Xen with GRUB2
fails?".
> >> 
> >> -- Pasi
> >> 
> >>> 
> >>> Jeremy Fitzhardinge wrote:
> >>> > 
> >>> > On 01/08/2010 06:16 AM, Fantu wrote:
> >>> >> Thanks, i have do, this is all the i see with sol
before black screen
> >>> >> freeze
> >>> >> on vga:
> >>> >>
> >>> >>   __  __            _  _    ___   ___              _
> >>> >>   \ \/ /___ _ __   | || |  / _ \ / _ \    _ __ ___/ |
_ __  _ __
> >>> ___
> >>> >>    \  // _ \ ''_ \  | || |_| | | | | | |__|
''__/ __| |__| ''_ \| ''__/ _
> >>> \
> >>> >>    /  \  __/ | | | |__   _| |_| | |_| |__| | | (__|
|__| |_) | | |
> >>> __/
> >>> >>   /_/\_\___|_| |_|    |_|(_)___(_)___/   |_|  \___|_|
| .__/|_|
> >>> \___|
> >>> >>                                                      
|_|
> >>> >> (XEN) Xen version 4.0.0-rc1-pre (root@) (gcc version
4.3.2 (Debian
> >>> >> 4.3.2-1.1) )0
> >>> >> (XEN) Latest ChangeSet: Tue Jan 05 08:40:18 2010
+0000
> >>> 20756:4feec90815a0
> >>> >> (XEN) Command line: dom0_mem=512M
iommu=passthrough,pv com2=57600,8n1
> >>> >> console=ca
> >>> >> (XEN) Video information:
> >>> >> (XEN)  VGA is text mode 80x25, font 8x16
> >>> >> (XEN)  VBE/DDC methods: V2; EDID transfer time: 1
seconds
> >>> >> (XEN) Disc information:
> >>> >> (XEN)  Found 2 MBR signatures
> >>> >> (XEN)  Found 2 EDD information structures
> >>> >> (XEN) Xen-e820 RAM map:
> >>> >> (XEN)  0000000000000000 - 00000000000a0000 (usable)
> >>> >> (XEN)  0000000000100000 - 00000000cf699000 (usable)
> >>> >> (XEN)  00000000cf699000 - 00000000cf6af000 (reserved)
> >>> >> (XEN)  00000000cf6af000 - 00000000cf6ce000 (ACPI
data)
> >>> >> (XEN)  00000000cf6ce000 - 00000000d0000000 (reserved)
> >>> >> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> >>> >> (XEN)  00000000fe000000 - 0000000100000000 (reserved)
> >>> >> (XEN)  0000000100000000 - 0000000330000000 (usable)
> >>> >> (XEN) ACPI: RSDP 000F0EC0, 0024 (r2 DELL  )
> >>> >> (XEN) ACPI: XSDT 000F0FC4, 009C (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: FACP CF6C3F9C, 00F4 (r3 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: DSDT CF6AF000, 3CF2 (r1 DELL   PE_SC3    
1 INTL
> >>> >> 20050624)
> >>> >> (XEN) ACPI: FACS CF6C6000, 0040
> >>> >> (XEN) ACPI: APIC CF6C3478, 015E (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: SPCR CF6C35D8, 0050 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: HPET CF6C362C, 0038 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: DMAR CF6C3668, 01D0 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: MCFG CF6C38C4, 003C (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: WD__ CF6C3904, 0134 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: SLIC CF6C3A3C, 0024 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: ERST CF6B2E74, 0270 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: HEST CF6B30E4, 03A8 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: BERT CF6B2CF4, 0030 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: EINJ CF6B2D24, 0150 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: SRAT CF6C3BC0, 0370 (r1 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: TCPA CF6C3F34, 0064 (r2 DELL   PE_SC3    
1 DELL
> >>> >> 1)
> >>> >> (XEN) ACPI: SSDT CF6C7000, 0F08 (r1  INTEL PPM RCM 
80000001 INTL
> >>> >> 20061109)
> >>> >> (XEN) System RAM: 12053MB (12342340kB)
> >>> >> (XEN) SRAT: PXM 1 ->  APIC 16 ->  Node 0
> >>> >> (XEN) SRAT: PXM 1 ->  APIC 18 ->  Node 0
> >>> >> (XEN) SRAT: PXM 1 ->  APIC 20 ->  Node 0
> >>> >> (XEN) SRAT: PXM 1 ->  APIC 22 ->  Node 0
> >>> >> (XEN) SRAT: Node 0 PXM 1 0-d0000000
> >>> >> (XEN) SRAT: Node 0 PXM 1 100000000-330000000
> >>> >> (XEN) NUMA: Using 20 for the hash shift.
> >>> >> (XEN) Domain heap initialised
> >>> >> (XEN) found SMP MP-table at 000fe710
> >>> >> (XEN) DMI 2.6 present.
> >>> >> (XEN) Using APIC driver default
> >>> >> (XEN) ACPI: PM-Timer IO Port: 0x808
> >>> >> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[804,0],
pm1x_evt[800,0]
> >>> >> (XEN) ACPI:                  wakeup_vec[cf6c600c],
vec_size[20]
> >>> >> (XEN) ACPI: Local APIC address 0xfee00000
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10]
enabled)
> >>> >> (XEN) Processor #16 7:10 APIC version 21
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12]
enabled)
> >>> >> (XEN) Processor #18 7:10 APIC version 21
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x14]
enabled)
> >>> >> (XEN) Processor #20 7:10 APIC version 21
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x16]
enabled)
> >>> >> (XEN) Processor #22 7:10 APIC version 21
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x24]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x25]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x26]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x27]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e]
disabled)
> >>> >> (XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f]
disabled)
> >>> >> (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge
lint[0x1])
> >>> >> (XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000]
gsi_base[0])
> >>> >> (XEN) IOAPIC[0]: apic_id 0, version 32, address
0xfec00000, GSI 0-23
> >>> >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec80000]
gsi_base[32])
> >>> >> (XEN) IOAPIC[1]: apic_id 1, version 32, address
0xfec80000, GSI 32-55
> >>> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2
dfl dfl)
> >>> >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9
high level)
> >>> >> (XEN) ACPI: IRQ0 used by override.
> >>> >> (XEN) ACPI: IRQ2 used by override.
> >>> >> (XEN) ACPI: IRQ9 used by override.
> >>> >> (XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
> >>> >> (XEN) ACPI: HPET id: 0x8086a301 base: 0xfed00000
> >>> >> (XEN) [VT-D]dmar.c:548: Host address width 40
> >>> >> (XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
> >>> >> (XEN) [VT-D]dmar.c:374:   dmaru->address =
fed90000
> >>> >> (XEN) [VT-D]dmar.c:386:   flags: INCLUDE_ALL
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7c8000 end_address
> >>> >> cf7dffff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7b1000 end_address
> >>> >> cf7bffff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.2
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7a1000 end_address
> >>> >> cf7a1fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.0
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7a3000 end_address
> >>> >> cf7a3fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.1
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7a5000 end_address
> >>> >> cf7a5fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.0
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7a7000 end_address
> >>> >> cf7a7fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.1
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7a9000 end_address
> >>> >> cf7a9fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.2
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7c0000 end_address
> >>> >> cf7c0fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1a.7
> >>> >> (XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
> >>> >> (XEN) [VT-D]dmar.c:446:   RMRR region: base_addr
cf7c2000 end_address
> >>> >> cf7c2fff
> >>> >> (XEN) [VT-D]dmar.c:326:   endpoint: 0:1d.7
> >>> >> (XEN) [VT-D]dmar.c:565: found ACPI_DMAR_ATSR:
> >>> >> (XEN) [VT-D]dmar.c:476:   atsru->all_ports: 0
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:1.0  start = 0
sec = 1  sub = 1
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:3.0  start = 0
sec = 3  sub = 3
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:4.0  start = 0
sec = 4  sub = 4
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:5.0  start = 0
sec = 5  sub = 5
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:7.0  start = 0
sec = 6  sub = 6
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:9.0  start = 0
sec = 7  sub = 7
> >>> >> (XEN) [VT-D]dmar.c:314:   bridge: 0:a.0  start = 0
sec = 2  sub = 2
> >>> >> (XEN) PCI: MCFG configuration 0: base e0000000
segment 0 buses 0 -
> >>> 255
> >>> >> (XEN) PCI: MCFG area at e0000000 reserved in E820
> >>> >> (XEN) Using ACPI (MADT) for SMP configuration
information
> >>> >> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> >>> >> (XEN) Initializing CPU#0
> >>> >> (XEN) Detected 1995.045 MHz processor.
> >>> >> (XEN) Initing memory sharing.
> >>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>> >> (XEN) CPU: L2 cache: 256K
> >>> >> (XEN) CPU: L3 cache: 4096K
> >>> >> (XEN) CPU: Physical Processor ID: 1
> >>> >> (XEN) CPU: Processor Core ID: 0
> >>> >> (XEN) VMX: Supported advanced features:
> >>> >> (XEN)  - APIC MMIO access virtualisation
> >>> >> (XEN)  - APIC TPR shadow
> >>> >> (XEN)  - Extended Page Tables (EPT)
> >>> >> (XEN)  - Virtual-Processor Identifiers (VPID)
> >>> >> (XEN)  - Virtual NMI
> >>> >> (XEN)  - MSR direct-access bitmap
> >>> >> (XEN) HVM: ASIDs enabled.
> >>> >> (XEN) HVM: VMX enabled
> >>> >> (XEN) HVM: Hardware Assisted Paging detected.
> >>> >> (XEN) Intel machine check reporting enabled on CPU#0.
> >>> >> (XEN) CPU0: Thermal monitoring enabled (TM1)
> >>> >> (XEN) [VT-D]iommu.c:1062: drhd->address = fed90000
> >>> >> (XEN) [VT-D]iommu.c:1063: iommu->reg =
ffff82c3fff57000
> >>> >> (XEN) Intel VT-d Snoop Control supported.
> >>> >> (XEN) Intel VT-d DMA Passthrough supported.
> >>> >> (XEN) Intel VT-d Queued Invalidation supported.
> >>> >> (XEN) Intel VT-d Interrupt Remapping not supported.
> >>> >> (XEN) I/O virtualisation enabled
> >>> >> (XEN) I/O virtualisation for PV guests enabled
> >>> >> (XEN) CPU0: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >>> 05
> >>> >> (XEN) Booting processor 1/18 eip 8c000
> >>> >> (XEN) Initializing CPU#1
> >>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>> >> (XEN) CPU: L2 cache: 256K
> >>> >> (XEN) CPU: L3 cache: 4096K
> >>> >> (XEN) CPU: Physical Processor ID: 1
> >>> >> (XEN) CPU: Processor Core ID: 1
> >>> >> (XEN) HVM: ASIDs enabled.
> >>> >> (XEN) Intel machine check reporting enabled on CPU#1.
> >>> >> (XEN) CPU1: Thermal monitoring enabled (TM1)
> >>> >> (XEN) CPU1: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >>> 05
> >>> >> (XEN) Booting processor 2/20 eip 8c000
> >>> >> (XEN) Initializing CPU#2
> >>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>> >> (XEN) CPU: L2 cache: 256K
> >>> >> (XEN) CPU: L3 cache: 4096K
> >>> >> (XEN) CPU: Physical Processor ID: 1
> >>> >> (XEN) CPU: Processor Core ID: 2
> >>> >> (XEN) HVM: ASIDs enabled.
> >>> >> (XEN) Intel machine check reporting enabled on CPU#2.
> >>> >> (XEN) CPU2: Thermal monitoring enabled (TM1)
> >>> >> (XEN) CPU2: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >>> 05
> >>> >> (XEN) Booting processor 3/22 eip 8c000
> >>> >> (XEN) Initializing CPU#3
> >>> >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K
> >>> >> (XEN) CPU: L2 cache: 256K
> >>> >> (XEN) CPU: L3 cache: 4096K
> >>> >> (XEN) CPU: Physical Processor ID: 1
> >>> >> (XEN) CPU: Processor Core ID: 3
> >>> >> (XEN) HVM: ASIDs enabled.
> >>> >> (XEN) Intel machine check reporting enabled on CPU#3.
> >>> >> (XEN) CPU3: Thermal monitoring enabled (TM1)
> >>> >> (XEN) CPU3: Intel(R) Xeon(R) CPU           E5504  @
2.00GHz stepping
> >>> 05
> >>> >> (XEN) Total of 4 processors activated.
> >>> >> (XEN) ENABLING IO-APIC IRQs
> >>> >> (XEN)  ->  Using new ACK method
> >>> >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1
pin2=-1
> >>> >> (XEN) checking TSC synchronization across 4 CPUs:
passed.
> >>> >> (XEN) Platform timer is 14.318MHz HPET
> >>> >> (
> >>> >>    
> >>> > 
> >>> > Ah, I saw the same when using a IPMI SOL implementation;
this is the
> >>> > point when the serial port becomes interrupt-driven, and
there''s
> >>> > something wrong with interrupts.  The fix is this patch
from Konrad:
> >>> > 
> >>> > diff -r 8f304c003af4 -r 7863747c5061
xen/drivers/char/ns16550.c
> >>> > --- a/xen/drivers/char/ns16550.c	Wed Dec 09 10:59:31 2009
+0000
> >>> > +++ b/xen/drivers/char/ns16550.c	Thu Dec 10 11:03:25 2009
-0800
> >>> > @@ -39,6 +39,7 @@
> >>> >       /* UART with no IRQ line: periodically-polled I/O.
*/
> >>> >       struct timer timer;
> >>> >       unsigned int timeout_ms;
> >>> > +    int probing, intr_works;
> >>> >   } ns16550_com[2] = { { 0 } };
> >>> > 
> >>> >   /* Register offsets */
> >>> > @@ -127,6 +128,13 @@
> >>> >       struct serial_port *port = dev_id;
> >>> >       struct ns16550 *uart = port->uart;
> >>> > 
> >>> > +    if (uart->intr_works == 0)
> >>> > +    {
> >>> > +        uart->probing = 0;
> >>> > +        uart->intr_works = 1;
> >>> > +        stop_timer(&uart->timer);
> >>> > +    }
> >>> > +
> >>> >       while ( !(ns_read_reg(uart, IIR)&  IIR_NOINT) )
> >>> >       {
> >>> >           char lsr = ns_read_reg(uart, LSR);
> >>> > @@ -143,6 +151,15 @@
> >>> >       struct ns16550 *uart = port->uart;
> >>> >       struct cpu_user_regs *regs = guest_cpu_user_regs();
> >>> > 
> >>> > +    if ( uart->intr_works )
> >>> > +        return;     /* Interrupts work - no more polling
*/
> >>> > +
> >>> > +    if ( uart->probing ) {
> >>> > +        uart->probing = 0;
> >>> > +        if ( (ns_read_reg(uart, LSR)&  0xff) == 0xff
)
> >>> > +            return;     /* All bits set - probably no
UART present */
> >>> > +    }
> >>> > +
> >>> >       while ( ns_read_reg(uart, LSR)&  LSR_DR )
> >>> >           serial_rx_interrupt(port, regs);
> >>> > 
> >>> > @@ -230,15 +247,14 @@
> >>> > 
> >>> >       serial_async_transmit(port);
> >>> > 
> >>> > +    init_timer(&uart->timer, ns16550_poll, port,
0);
> >>> > +    /* Calculate time to fill RX FIFO and/or empty TX
FIFO for
> >>> polling.
> >>> > */
> >>> > +    bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> >>> > +    uart->timeout_ms = max_t(
> >>> > +        unsigned int, 1, (bits * port->tx_fifo_size *
1000) /
> >>> > uart->baud);
> >>> > +
> >>> >       if ( uart->irq == 0 )
> >>> > -    {
> >>> > -        /* Polled mode. Calculate time to fill RX FIFO
and/or empty
> >>> TX
> >>> > FIFO. */
> >>> > -        bits = uart->data_bits + uart->stop_bits +
!!uart->parity;
> >>> > -        uart->timeout_ms = max_t(
> >>> > -            unsigned int, 1, (bits *
port->tx_fifo_size * 1000) /
> >>> > uart->baud);
> >>> > -        init_timer(&uart->timer, ns16550_poll,
port, 0);
> >>> >           set_timer(&uart->timer, NOW() +
> >>> MILLISECS(uart->timeout_ms));
> >>> > -    }
> >>> >       else
> >>> >       {
> >>> >           uart->irqaction.handler = ns16550_interrupt;
> >>> > @@ -252,6 +268,12 @@
> >>> > 
> >>> >           /* Enable receive and transmit interrupts. */
> >>> >           ns_write_reg(uart, IER, IER_ERDAI |
IER_ETHREI);
> >>> > +
> >>> > +        /* Do a timed write to make sure we are getting
interrupts.
> >>> */
> >>> > +        uart->probing = 1;
> >>> > +        uart->intr_works = 0;
> >>> > +        ns_write_reg(uart, THR, 0xff);
> >>> > +        set_timer(&uart->timer, NOW() +
MILLISECS(uart->timeout_ms));
> >>> >       }
> >>> >   }
> >>> > 
> >>> > 
> >>> > 	J
> >>> > 
> >>> > 
> >>> > _______________________________________________
> >>> > Xen-devel mailing list
> >>> > Xen-devel@lists.xensource.com
> >>> > http://lists.xensource.com/xen-devel
> >>> > 
> >>> > 
> >>> 
> >>> -- 
> >>> View this message in context:
> >>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27608625.html
> >>> Sent from the Xen - Dev mailing list archive at Nabble.com.
> >>> 
> >>> 
> >>> _______________________________________________
> >>> Xen-devel mailing list
> >>> Xen-devel@lists.xensource.com
> >>> http://lists.xensource.com/xen-devel
> >> 
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> >> 
> >> 
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27714129.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fabio Fantoni

2010-Feb-24 13:23 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

What i must check in bios about this problem?


Il 24/02/2010 09:59, Pasi Kärkkäinen ha scritto:> On Wed, Feb 24, 2010 at 12:39:28AM -0800, Fantu wrote:
>    
>> I have reupdate xen and kernel and redo debug with also dummy=dummy and
this
>> is the sol log:  http://old.nabble.com/file/p27714129/sol2.txt sol2.txt
>>
>>      
> (XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.
>
> Does that ring any bells? IRQ 0 is the system timer..
>
> -- Pasi
>
>    

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Feb-26 13:32 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

With xen/master always not start, now i try also xen/stable with pasi config
on wiki page and start but without xen, the dmesg with detail: 
http://old.nabble.com/file/p27718305/dmesg dmesg 


Fantu wrote:> 
> I have reupdate xen and kernel and redo debug with also dummy=dummy and
> this is the sol log:  http://old.nabble.com/file/p27714129/sol2.txt
> sol2.txt 
> 
> Fantu wrote:
>> 
>> also with this not boot:
>> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>>  	set root=(hd0,1)
>>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M
>> iommu=passthrough,pv loglvl=all guest_loglvl=all sync_console
>> console_to_ring com2=56700,8n1 console=com2,vga
>>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy root=LABEL=root-raid ro
>> console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
>>  	module /boot/initrd.img-2.6.31.6-xen
>>  }
>> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27718305.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Feb-26 14:42 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

On Fri, Feb 26, 2010 at 05:32:34AM -0800, Fantu wrote:> 
> With xen/master always not start, now i try also xen/stable with pasi
config
> on wiki page and start but without xen, the dmesg with detail: 
> http://old.nabble.com/file/p27718305/dmesg dmesg 
> 
So this dmesg is from a working non-xen (baremetal) boot? 
Can you provide log of the failing boot as xen dom0? 

You can capture the messages using a serial console:
http://wiki.xensource.com/xenwiki/XenSerialConsole

-- Pasi
> 
> Fantu wrote:
> > 
> > I have reupdate xen and kernel and redo debug with also dummy=dummy
and
> > this is the sol log:  http://old.nabble.com/file/p27714129/sol2.txt
> > sol2.txt 
> > 
> > Fantu wrote:
> >> 
> >> also with this not boot:
> >> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> >>  	set root=(hd0,1)
> >>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M
> >> iommu=passthrough,pv loglvl=all guest_loglvl=all sync_console
> >> console_to_ring com2=56700,8n1 console=com2,vga
> >>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy
root=LABEL=root-raid ro
> >> console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
> >>  	module /boot/initrd.img-2.6.31.6-xen
> >>  }
> >> 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27718305.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Feb-26 15:58 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

sol2.txt is complete sol from xen master update and grub with dummy=dummy ecc
dmesg is from xen stable boot with xen but with problem, read it can help to
understand, sorry if you not understand for my bad english^^''''


Pasi Kärkkäinen wrote:> 
> On Fri, Feb 26, 2010 at 05:32:34AM -0800, Fantu wrote:
>> 
>> With xen/master always not start, now i try also xen/stable with pasi
>> config
>> on wiki page and start but without xen, the dmesg with detail: 
>> http://old.nabble.com/file/p27718305/dmesg dmesg 
>> 
> 
> So this dmesg is from a working non-xen (baremetal) boot? 
> Can you provide log of the failing boot as xen dom0? 
> 
> You can capture the messages using a serial console:
> http://wiki.xensource.com/xenwiki/XenSerialConsole
> 
> -- Pasi
> 
>> 
>> Fantu wrote:
>> > 
>> > I have reupdate xen and kernel and redo debug with also
dummy=dummy and
>> > this is the sol log: 
http://old.nabble.com/file/p27714129/sol2.txt
>> > sol2.txt 
>> > 
>> > Fantu wrote:
>> >> 
>> >> also with this not boot:
>> >> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>> >>  	set root=(hd0,1)
>> >>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M
>> >> iommu=passthrough,pv loglvl=all guest_loglvl=all sync_console
>> >> console_to_ring com2=56700,8n1 console=com2,vga
>> >>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy
root=LABEL=root-raid
>> ro
>> >> console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
>> >>  	module /boot/initrd.img-2.6.31.6-xen
>> >>  }
>> >> 
>> > 
>> 
>> -- 
>> View this message in context:
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27718305.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27719983.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Mar-01 09:54 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Now i have redo kernel from xen/master, view kernel panic and calltrace on
screen, the screenshot: 
http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
2.6.31.6_pv_ops_not_start.jpg 

Pasi Kärkkäinen wrote:> 
> On Fri, Feb 26, 2010 at 05:32:34AM -0800, Fantu wrote:
>> 
>> With xen/master always not start, now i try also xen/stable with pasi
>> config
>> on wiki page and start but without xen, the dmesg with detail: 
>> http://old.nabble.com/file/p27718305/dmesg dmesg 
>> 
> 
> So this dmesg is from a working non-xen (baremetal) boot? 
> Can you provide log of the failing boot as xen dom0? 
> 
> You can capture the messages using a serial console:
> http://wiki.xensource.com/xenwiki/XenSerialConsole
> 
> -- Pasi
> 
>> 
>> Fantu wrote:
>> > 
>> > I have reupdate xen and kernel and redo debug with also
dummy=dummy and
>> > this is the sol log: 
http://old.nabble.com/file/p27714129/sol2.txt
>> > sol2.txt 
>> > 
>> > Fantu wrote:
>> >> 
>> >> also with this not boot:
>> >> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
>> >>  	set root=(hd0,1)
>> >>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M
>> >> iommu=passthrough,pv loglvl=all guest_loglvl=all sync_console
>> >> console_to_ring com2=56700,8n1 console=com2,vga
>> >>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy
root=LABEL=root-raid
>> ro
>> >> console=hvc0 initcall_debug debug loglevel=10 earlyprintk=xen
>> >>  	module /boot/initrd.img-2.6.31.6-xen
>> >>  }
>> >> 
>> > 
>> 
>> -- 
>> View this message in context:
>>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27718305.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27741588.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Pasi Kärkkäinen

2010-Mar-01 10:21 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

On Mon, Mar 01, 2010 at 01:54:46AM -0800, Fantu wrote:> 
> Now i have redo kernel from xen/master, view kernel panic and calltrace on
> screen, the screenshot: 
> http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
> 2.6.31.6_pv_ops_not_start.jpg 
>
Ok.. maybe Jeremy has some ideas about this one. It seems to crash pretty early.

-- Pasi
 > Pasi Kärkkäinen wrote:
> > 
> > On Fri, Feb 26, 2010 at 05:32:34AM -0800, Fantu wrote:
> >> 
> >> With xen/master always not start, now i try also xen/stable with
pasi
> >> config
> >> on wiki page and start but without xen, the dmesg with detail: 
> >> http://old.nabble.com/file/p27718305/dmesg dmesg 
> >> 
> > 
> > So this dmesg is from a working non-xen (baremetal) boot? 
> > Can you provide log of the failing boot as xen dom0? 
> > 
> > You can capture the messages using a serial console:
> > http://wiki.xensource.com/xenwiki/XenSerialConsole
> > 
> > -- Pasi
> > 
> >> 
> >> Fantu wrote:
> >> > 
> >> > I have reupdate xen and kernel and redo debug with also
dummy=dummy and
> >> > this is the sol log: 
http://old.nabble.com/file/p27714129/sol2.txt
> >> > sol2.txt 
> >> > 
> >> > Fantu wrote:
> >> >> 
> >> >> also with this not boot:
> >> >> menuentry "Xen 4 hg-un DEBUG, linux 2.6.31.6" {
> >> >>  	set root=(hd0,1)
> >> >>  	multiboot /boot/xen-4.gz dummy=dummy dom0_mem=1024M
> >> >> iommu=passthrough,pv loglvl=all guest_loglvl=all
sync_console
> >> >> console_to_ring com2=56700,8n1 console=com2,vga
> >> >>  	module /boot/vmlinuz-2.6.31.6-xen dummy=dummy
root=LABEL=root-raid
> >> ro
> >> >> console=hvc0 initcall_debug debug loglevel=10
earlyprintk=xen
> >> >>  	module /boot/initrd.img-2.6.31.6-xen
> >> >>  }
> >> >> 
> >> > 
> >> 
> >> -- 
> >> View this message in context:
> >>
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27718305.html
> >> Sent from the Xen - Dev mailing list archive at Nabble.com.
> >> 
> >> 
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 
> -- 
> View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27741588.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Campbell

2010-Mar-01 10:27 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

On Mon, 2010-03-01 at 10:21 +0000, Pasi Kärkkäinen
wrote:> On Mon, Mar 01, 2010 at 01:54:46AM -0800, Fantu wrote:
> > 
> > Now i have redo kernel from xen/master, view kernel panic and
calltrace on
> > screen, the screenshot: 
> > http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
> > 2.6.31.6_pv_ops_not_start.jpg 
> >
> 
> Ok.. maybe Jeremy has some ideas about this one. It seems to crash pretty
early.
This issue is also being discussed in the thread "CONFIG_SPARSE_IRQ
breaks single VCPU domain 0 between xen/master and xen/next" started
last week. Although it looks like it might not necessarily be tied to
CONFIG_SPARSE_IRQ at this point.

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Campbell

2010-Mar-01 10:32 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

On Mon, 2010-03-01 at 10:27 +0000, Ian Campbell wrote:> On Mon, 2010-03-01 at 10:21 +0000, Pasi Kärkkäinen wrote:
> > On Mon, Mar 01, 2010 at 01:54:46AM -0800, Fantu wrote:
> > > 
> > > Now i have redo kernel from xen/master, view kernel panic and
calltrace on
> > > screen, the screenshot: 
> > >
http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
> > > 2.6.31.6_pv_ops_not_start.jpg 
> > >
> > 
> > Ok.. maybe Jeremy has some ideas about this one. It seems to crash
pretty early.
> 
> This issue is also being discussed in the thread "CONFIG_SPARSE_IRQ
> breaks single VCPU domain 0 between xen/master and xen/next" started
> last week. Although it looks like it might not necessarily be tied to
> CONFIG_SPARSE_IRQ at this point.
It''s also possible (likely!) that my change "fix off-by-one error
in
find_unbound_irq" is what is causing this issue in xen/master rather
than the sparse IRQ thing.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Mar-01 10:45 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

i have problem more before...
CONFIG_SPARSE_IRQ=y on all .config i have used, i can change to n and try or
must set to y?

Ian Campbell-10 wrote:> 
> On Mon, 2010-03-01 at 10:27 +0000, Ian Campbell wrote:
>> On Mon, 2010-03-01 at 10:21 +0000, Pasi Kärkkäinen wrote:
>> > On Mon, Mar 01, 2010 at 01:54:46AM -0800, Fantu wrote:
>> > > 
>> > > Now i have redo kernel from xen/master, view kernel panic and
>> calltrace on
>> > > screen, the screenshot: 
>> > >
http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
>> > > 2.6.31.6_pv_ops_not_start.jpg 
>> > >
>> > 
>> > Ok.. maybe Jeremy has some ideas about this one. It seems to crash
>> pretty early.
>> 
>> This issue is also being discussed in the thread
"CONFIG_SPARSE_IRQ
>> breaks single VCPU domain 0 between xen/master and xen/next"
started
>> last week. Although it looks like it might not necessarily be tied to
>> CONFIG_SPARSE_IRQ at this point.
> 
> It''s also possible (likely!) that my change "fix off-by-one
error in
> find_unbound_irq" is what is causing this issue in xen/master rather
> than the sparse IRQ thing.
> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27742020.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ian Campbell

2010-Mar-01 11:05 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

On Mon, 2010-03-01 at 10:45 +0000, Fantu wrote:> i have problem more before...
> CONFIG_SPARSE_IRQ=y on all .config i have used, i can change to n and try
or
> must set to y?
Try reverting this first:

commit 68458a366412dbbfa726dbdd403e94be5ac10a69
Author: Ian Campbell <ian.campbell@citrix.com>
Date:   Fri Feb 26 10:59:35 2010 +0000

    xen: fix off-by-one error in find_unbound_irq
    
    e459de95 "Find an unbound irq number in reverse order (high to
low)" introduced
    an off by one error which would cause repeated allocations of the
nr_irq''th IRQ
    if there are no spare interrupts (i.e. get_nr_hw_irqs() == nr_irqs).
    
    Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
    Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
    Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

If that doesn''t help then try setting CONFIG_SPARSE_IRQ to n.

Ian.
> 
> 
> Ian Campbell-10 wrote:
> > 
> > On Mon, 2010-03-01 at 10:27 +0000, Ian Campbell wrote:
> >> On Mon, 2010-03-01 at 10:21 +0000, Pasi Kärkkäinen wrote:
> >> > On Mon, Mar 01, 2010 at 01:54:46AM -0800, Fantu wrote:
> >> > > 
> >> > > Now i have redo kernel from xen/master, view kernel
panic and
> >> calltrace on
> >> > > screen, the screenshot: 
> >> > >
http://old.nabble.com/file/p27741588/2.6.31.6_pv_ops_not_start.jpg
> >> > > 2.6.31.6_pv_ops_not_start.jpg 
> >> > >
> >> > 
> >> > Ok.. maybe Jeremy has some ideas about this one. It seems to
crash
> >> pretty early.
> >> 
> >> This issue is also being discussed in the thread
"CONFIG_SPARSE_IRQ
> >> breaks single VCPU domain 0 between xen/master and xen/next"
started
> >> last week. Although it looks like it might not necessarily be tied
to
> >> CONFIG_SPARSE_IRQ at this point.
> > 
> > It''s also possible (likely!) that my change "fix
off-by-one error in
> > find_unbound_irq" is what is causing this issue in xen/master
rather
> > than the sparse IRQ thing.
> > 
> > Ian.
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> > 
> > 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Mar-01 15:34 UTC

head link

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

I have try xen/master with CONFIG_SPARSE_IRQ=n and reverse of your patch but
nothing, after i try xen/stable with CONFIG_SPARSE_IRQ=n and apply patch
0001-x86-ioapic-Remove-the-hack-for-calculating-nr_irq_ from another post
and work... finally xen 4 with kernel pv_ops work on  Dell T610 :jumping:

Ian Campbell-10 wrote:> 
> On Mon, 2010-03-01 at 10:45 +0000, Fantu wrote:
>> i have problem more before...
>> CONFIG_SPARSE_IRQ=y on all .config i have used, i can change to n and
try
>> or
>> must set to y?
> 
> Try reverting this first:
> 
> commit 68458a366412dbbfa726dbdd403e94be5ac10a69
> Author: Ian Campbell <ian.campbell@citrix.com>
> Date:   Fri Feb 26 10:59:35 2010 +0000
> 
>     xen: fix off-by-one error in find_unbound_irq
>     
>     e459de95 "Find an unbound irq number in reverse order (high to
low)"
> introduced
>     an off by one error which would cause repeated allocations of the
> nr_irq''th IRQ
>     if there are no spare interrupts (i.e. get_nr_hw_irqs() == nr_irqs).
>     
>     Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>     Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>     Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>     Signed-off-by: Jeremy Fitzhardinge
<jeremy.fitzhardinge@citrix.com>
> 
> If that doesn''t help then try setting CONFIG_SPARSE_IRQ to n.
> 
> Ian.
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27745067.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Zhang, Xiantao

2010-Mar-02 07:09 UTC

head link

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Fantu wrote:> I have try xen/master with CONFIG_SPARSE_IRQ=n and reverse of your
> patch but nothing, after i try xen/stable with CONFIG_SPARSE_IRQ=n
> and apply patch
> 0001-x86-ioapic-Remove-the-hack-for-calculating-nr_irq_ from another
> post and work... finally xen 4 with kernel pv_ops work on  Dell T610
> :jumping:  
Have you tried CONFIG_SPARSE_IRQ=y with this patch ?  I think it should work as
well.
Xiantao 

> Ian Campbell-10 wrote:
>> 
>> On Mon, 2010-03-01 at 10:45 +0000, Fantu wrote:
>>> i have problem more before...
>>> CONFIG_SPARSE_IRQ=y on all .config i have used, i can change to n
>>> and try or must set to y?
>> 
>> Try reverting this first:
>> 
>> commit 68458a366412dbbfa726dbdd403e94be5ac10a69
>> Author: Ian Campbell <ian.campbell@citrix.com>
>> Date:   Fri Feb 26 10:59:35 2010 +0000
>> 
>>     xen: fix off-by-one error in find_unbound_irq
>> 
>>     e459de95 "Find an unbound irq number in reverse order (high to
>>     low)" introduced an off by one error which would cause
repeated
>>     allocations of the nr_irq''th IRQ if there are no spare
>> interrupts (i.e. get_nr_hw_irqs() == nr_irqs). 
>> 
>>     Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>>     Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>     Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>>     Signed-off-by: Jeremy Fitzhardinge
>> <jeremy.fitzhardinge@citrix.com> 
>> 
>> If that doesn''t help then try setting CONFIG_SPARSE_IRQ to n.
>> 
>> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Mar-05 10:30 UTC

head link

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

i have recompile on xen/master updated (necessary for gfx test) but not work
now i try with CONFIG_SPARSE_IRQ=n
the config use is:  http://old.nabble.com/file/p27792293/.config .config 

Zhang, Xiantao wrote:> 
> Fantu wrote:
>> I have try xen/master with CONFIG_SPARSE_IRQ=n and reverse of your
>> patch but nothing, after i try xen/stable with CONFIG_SPARSE_IRQ=n
>> and apply patch
>> 0001-x86-ioapic-Remove-the-hack-for-calculating-nr_irq_ from another
>> post and work... finally xen 4 with kernel pv_ops work on  Dell T610
>> :jumping:  
> 
> Have you tried CONFIG_SPARSE_IRQ=y with this patch ?  I think it should
> work as well. 
> Xiantao 
> 
> 
>> Ian Campbell-10 wrote:
>>> 
>>> On Mon, 2010-03-01 at 10:45 +0000, Fantu wrote:
>>>> i have problem more before...
>>>> CONFIG_SPARSE_IRQ=y on all .config i have used, i can change to
n
>>>> and try or must set to y?
>>> 
>>> Try reverting this first:
>>> 
>>> commit 68458a366412dbbfa726dbdd403e94be5ac10a69
>>> Author: Ian Campbell <ian.campbell@citrix.com>
>>> Date:   Fri Feb 26 10:59:35 2010 +0000
>>> 
>>>     xen: fix off-by-one error in find_unbound_irq
>>> 
>>>     e459de95 "Find an unbound irq number in reverse order
(high to
>>>     low)" introduced an off by one error which would cause
repeated
>>>     allocations of the nr_irq''th IRQ if there are no spare
>>> interrupts (i.e. get_nr_hw_irqs() == nr_irqs). 
>>> 
>>>     Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>>>     Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>>     Cc: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>>>     Signed-off-by: Jeremy Fitzhardinge
>>> <jeremy.fitzhardinge@citrix.com> 
>>> 
>>> If that doesn''t help then try setting CONFIG_SPARSE_IRQ to
n.
>>> 
>>> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27792293.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Mar-05 15:41 UTC

head link

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

now work also with CONFIG_SPARSE_IRQ=n and also with
0001-x86-ioapic-Remove-the-hack-for-calculating-nr_irq_ :-(

Fantu wrote:> 
> i have recompile on xen/master updated (necessary for gfx test) but not
> work now i try with CONFIG_SPARSE_IRQ=n
> the config use is:  http://old.nabble.com/file/p27792293/.config .config 
> 
> Zhang, Xiantao wrote:
>> 
>> Fantu wrote:
>>> I have try xen/master with CONFIG_SPARSE_IRQ=n and reverse of your
>>> patch but nothing, after i try xen/stable with CONFIG_SPARSE_IRQ=n
>>> and apply patch
>>> 0001-x86-ioapic-Remove-the-hack-for-calculating-nr_irq_ from
another
>>> post and work... finally xen 4 with kernel pv_ops work on  Dell
T610
>>> :jumping:  
>> 
>> Have you tried CONFIG_SPARSE_IRQ=y with this patch ?  I think it should
>> work as well. 
>> Xiantao 
>> 
>> 
>>> Ian Campbell-10 wrote:
>>>> 
>>>> On Mon, 2010-03-01 at 10:45 +0000, Fantu wrote:
>>>>> i have problem more before...
>>>>> CONFIG_SPARSE_IRQ=y on all .config i have used, i can
change to n
>>>>> and try or must set to y?
>>>> 
>>>> Try reverting this first:
>>>> 
>>>> commit 68458a366412dbbfa726dbdd403e94be5ac10a69
>>>> Author: Ian Campbell <ian.campbell@citrix.com>
>>>> Date:   Fri Feb 26 10:59:35 2010 +0000
>>>> 
>>>>     xen: fix off-by-one error in find_unbound_irq
>>>> 
>>>>     e459de95 "Find an unbound irq number in reverse order
(high to
>>>>     low)" introduced an off by one error which would cause
repeated
>>>>     allocations of the nr_irq''th IRQ if there are no
spare
>>>> interrupts (i.e. get_nr_hw_irqs() == nr_irqs). 
>>>> 
>>>>     Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>>>>     Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>>>     Cc: Jeremy Fitzhardinge
<jeremy.fitzhardinge@citrix.com>
>>>>     Signed-off-by: Jeremy Fitzhardinge
>>>> <jeremy.fitzhardinge@citrix.com> 
>>>> 
>>>> If that doesn''t help then try setting
CONFIG_SPARSE_IRQ to n.
>>>> 
>>>> Ian.
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>> 
>> 
> 
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p27795487.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Apr-14 11:46 UTC

head link

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

I have the same boot problem also with 2.6.32 after update of last commit
with also merging of .11, now with .31 and .32 kernel from pv_ops not boot
and stop at the same point with last 2 line drm and serial
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p28241561.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Fantu

2010-Apr-19 09:25 UTC

head link

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

The screenshot where boot stop on Dell t610 with last bios (also with old),
with xen 4 from hg-testing and kernel 2.6.32.11 pv_ops
http://old.nabble.com/file/p28287631/2.6.32.11_pv_ops_not_boot.jpg
2.6.32.11_pv_ops_not_boot.jpg 

Fantu wrote:> 
> I have the same boot problem also with 2.6.32 after update of last commit
> with also merging of .11, now with .31 and .32 kernel from pv_ops not boot
> and stop at the same point with last 2 line drm and serial
> 
-- 
View this message in context:
http://old.nabble.com/Kernel-2.6.31.6-pv_ops-freeze-on-start-tp27059994p28287631.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Konrad Rzeszutek Wilk

2010-Apr-19 13:52 UTC

head link

[Xen-devel] Boot hands - need sync serial console to help.

On Mon, Apr 19, 2010 at 02:25:38AM -0700, Fantu wrote:> 
> The screenshot where boot stop on Dell t610 with last bios (also with old),
> with xen 4 from hg-testing and kernel 2.6.32.11 pv_ops
> http://old.nabble.com/file/p28287631/2.6.32.11_pv_ops_not_boot.jpg
> 2.6.32.11_pv_ops_not_boot.jpg 
First, the subject refers to something entirely different than what you
see.

Secondly, take a look at this Wiki and follow
http://wiki.xensource.com/xenwiki/XenParavirtOps
the steps outlined in the ''Are there more debugging options I could
enable to troubleshoot booting problems?'' section.

Please carefully follow the steps and make sure you have a working
serial console so that we can help you and Fantu with this issue.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Xen devel - Jan 2010 - Kernel 2.6.31.6 pv_ops freeze on start

[Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Re: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

RE: [Xen-devel] Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

[Xen-devel] Boot hands - need sync serial console to help.