Hello, I have some diagnostic Info for you. Tried to get xen-4.0.1 working on another node of my cluster. Only difference: Newer revision of the Hardware. Exactly same Software Stack. Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt linux-2.6.32.27 from xen/stable-2.6.32.x Nodes working: HP DL380G5 16GB (Intel X5460) Node not working: HP DL380G6 16GB (Intel X5550) Effect: Xen starts but dom0 Crashes immidiately after I see the message "Scrubbing free Ram". I attached Screenshot of the Management Processors Serial Port. I used the same dom0 kernel deb that successfully runs on other Nodes (as well on xen-4.0.1). Any ideas? I''m really stuck on this. I use XEN since 5+ years, but I never had that one.. greetings, Bastian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2011-02-09 at 10:16 +0000, Bastian Mäuser wrote:> Hello, > > I have some diagnostic Info for you. Tried to get xen-4.0.1 working on > another node of my cluster. Only difference: Newer revision of the > Hardware. Exactly same Software Stack. > > Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt > linux-2.6.32.27 from xen/stable-2.6.32.x > > Nodes working: HP DL380G5 16GB (Intel X5460) > > Node not working: HP DL380G6 16GB (Intel X5550) > > Effect: Xen starts but dom0 Crashes immidiately after I see the message > "Scrubbing free Ram". I attached Screenshot of the Management Processors > Serial Port. > > I used the same dom0 kernel deb that successfully runs on other Nodes > (as well on xen-4.0.1). > > Any ideas? I''m really stuck on this. I use XEN since 5+ years, but I > never had that one..Please can you convert the faulting RIP address to a line of code. e.g. using $ gdb vmlinux (gdb) list *0xffff..... Please see also "Are there more debugging options I could enable to troubleshoot problems with Xen and/or dom0 kernel?" http://wiki.xen.org/xenwiki/XenParavirtOps for other debug options to try. Limiting the amount of memory given to dom0 (using the dom0_mem hypervisor option) would be interesting in case this is the same issue as Debian bug #606964. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 02/09/2011 12:12 PM, Ian Campbell wrote:> On Wed, 2011-02-09 at 10:16 +0000, Bastian Mäuser wrote: >> Hello, >> >> I have some diagnostic Info for you. Tried to get xen-4.0.1 working on >> another node of my cluster. Only difference: Newer revision of the >> Hardware. Exactly same Software Stack. >> >> Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt >> linux-2.6.32.27 from xen/stable-2.6.32.x >> >> Nodes working: HP DL380G5 16GB (Intel X5460) >> >> Node not working: HP DL380G6 16GB (Intel X5550) >> >> Effect: Xen starts but dom0 Crashes immidiately after I see the message >> "Scrubbing free Ram". I attached Screenshot of the Management Processors >> Serial Port. >> >> I used the same dom0 kernel deb that successfully runs on other Nodes >> (as well on xen-4.0.1). >> >> Any ideas? I''m really stuck on this. I use XEN since 5+ years, but I >> never had that one.. > Please can you convert the faulting RIP address to a line of code. e.g. > using > $ gdb vmlinux > (gdb) list *0xffff.....I need some more Info on that. GDB''ing the Kernel Image won''t work right?> Please see also "Are there more debugging options I could enable to > troubleshoot problems with Xen and/or dom0 kernel?" > http://wiki.xen.org/xenwiki/XenParavirtOps for other debug options to > try.This is my Debugging: multiboot /boot/xen-4.0.1.gz dom0_mem=1024M dummy=dummy loglvl=all guest_loglvl=all sync_console console_to_ring com1=115200,8n1 console=com1 lapic=debug apic_verbosity=debug apic=debug iommu=off module /boot/vmlinuz-2.6.32.27 dummy=dummy root=/dev/cciss/c0d0p1 ro console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 module /boot/initrd.img-2.6.32.27> Limiting the amount of memory given to dom0 (using the dom0_mem > hypervisor option) would be interesting in case this is the same issue > as Debian bug #606964.As you can see i always allocate 1gb to dom0.. Bastian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 02/09/2011 12:40 PM, Bastian Mäuser wrote:> On 02/09/2011 12:12 PM, Ian Campbell wrote: >> On Wed, 2011-02-09 at 10:16 +0000, Bastian Mäuser wrote: >>> Hello, >>> >>> I have some diagnostic Info for you. Tried to get xen-4.0.1 working on >>> another node of my cluster. Only difference: Newer revision of the >>> Hardware. Exactly same Software Stack. >>> >>> Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt >>> linux-2.6.32.27 from xen/stable-2.6.32.x >>> >>> Nodes working: HP DL380G5 16GB (Intel X5460) >>> >>> Node not working: HP DL380G6 16GB (Intel X5550) >>> >>> Effect: Xen starts but dom0 Crashes immidiately after I see the message >>> "Scrubbing free Ram". I attached Screenshot of the Management Processors >>> Serial Port. >>> >>> I used the same dom0 kernel deb that successfully runs on other Nodes >>> (as well on xen-4.0.1). >>> >>> Any ideas? I''m really stuck on this. I use XEN since 5+ years, but I >>> never had that one.. >> Please can you convert the faulting RIP address to a line of code. e.g. >> using >> $ gdb vmlinux >> (gdb) list *0xffff..... > I need some more Info on that. GDB''ing the Kernel Image won''t work right? >> Please see also "Are there more debugging options I could enable to >> troubleshoot problems with Xen and/or dom0 kernel?" >> http://wiki.xen.org/xenwiki/XenParavirtOps for other debug options to >> try. > This is my Debugging: > > multiboot /boot/xen-4.0.1.gz dom0_mem=1024M dummy=dummy loglvl=all > guest_loglvl=all sync_console console_to_ring com1=115200,8n1 > console=com1 lapic=debug apic_verbosity=debug apic=debug iommu=off > module /boot/vmlinuz-2.6.32.27 dummy=dummy root=/dev/cciss/c0d0p1 ro > console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 > module /boot/initrd.img-2.6.32.27 >ffffffff8187da0a T xen_hvm_init_mmu_ops ffffffff8187da4f t xen_set_pte_init ffffffff8187dad4 t xen_pagetable_setup_done ffffffff8187db94 T xen_build_dynamic_phys_to_machine that''s around the RIP Address.. Bastian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, 2011-02-09 at 11:40 +0000, Bastian Mäuser wrote:> On 02/09/2011 12:12 PM, Ian Campbell wrote: > > On Wed, 2011-02-09 at 10:16 +0000, Bastian Mäuser wrote: > >> Hello, > >> > >> I have some diagnostic Info for you. Tried to get xen-4.0.1 working on > >> another node of my cluster. Only difference: Newer revision of the > >> Hardware. Exactly same Software Stack. > >> > >> Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt > >> linux-2.6.32.27 from xen/stable-2.6.32.x > >> > >> Nodes working: HP DL380G5 16GB (Intel X5460) > >> > >> Node not working: HP DL380G6 16GB (Intel X5550) > >> > >> Effect: Xen starts but dom0 Crashes immidiately after I see the message > >> "Scrubbing free Ram". I attached Screenshot of the Management Processors > >> Serial Port. > >> > >> I used the same dom0 kernel deb that successfully runs on other Nodes > >> (as well on xen-4.0.1). > >> > >> Any ideas? I''m really stuck on this. I use XEN since 5+ years, but I > >> never had that one.. > > Please can you convert the faulting RIP address to a line of code. e.g. > > using > > $ gdb vmlinux > > (gdb) list *0xffff..... > I need some more Info on that. GDB''ing the Kernel Image won''t work right?vmlinux is found at the top level of the directory where you built the kernel, it is an uncompressed, unstripped ELF file which you should be able to run gdb on. You are right that running gdb on e.g. a bzImage won''t work. Even if you were to extract the ELF file from the bzImage container it would be stripped and hence not very useful.> > Please see also "Are there more debugging options I could enable to > > troubleshoot problems with Xen and/or dom0 kernel?" > > http://wiki.xen.org/xenwiki/XenParavirtOps for other debug options to > > try. > > This is my Debugging: > > multiboot /boot/xen-4.0.1.gz dom0_mem=1024M dummy=dummy loglvl=all > guest_loglvl=all sync_console console_to_ring com1=115200,8n1 > console=com1 lapic=debug apic_verbosity=debug apic=debug iommu=off > module /boot/vmlinuz-2.6.32.27 dummy=dummy root=/dev/cciss/c0d0p1 ro > console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 > module /boot/initrd.img-2.6.32.27 > > > > Limiting the amount of memory given to dom0 (using the dom0_mem > > hypervisor option) would be interesting in case this is the same issue > > as Debian bug #606964. > As you can see i always allocate 1gb to dom0..OK, thanks.> > Bastian_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
OK,
here we go with a Full Debugging Output of the Serial Console:
16 GB
Installed
ProLiant System BIOS - P62
(08/16/2010) Copyright 1982, 2010
Hewlett-Packard Development Company,
L.P.
2 Processor(s) detected, 8 total cores enabled, Hyperthreading is enabled
Proc 1: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz Proc 2: Intel(R)
Xeon(R) CPU X5550 @ 2.67GHz QPI Speed: 6.4 GT/s
HP Power Profile Mode: Balanced Power and Performance
Power Regulator Mode: Dynamic Power Savings
Advanced Memory Protection Mode: Advanced ECC Support
Redundant ROM Detected - This system contains a valid backup system ROM.
Inlet Ambient Temperature: 16C/60F
Press any key to view Option ROM messages
SATA Option ROM ver 2.00.B12
Copyright 1982, 2008. Hewlett-Packard Development Company, L.P.
Port1: (CD-ROM) TEAC DV-W28S-VS
Broadcom NetXtreme II Ethernet Boot Agent v5.0.5
Copyright (C) 2000-2009 Broadcom Corporation
All rights reserved.
Press Ctrl-S to Configure Device (MAC Address - 18A9054D3AF2)
Integrated Lights-Out 2 Advanced iLO 2 v2.01 Aug
04 2010 10.88.0.100
Slot 0 HP Smart Array P410i Controller (512MB, v3.52) 1 Logical
Drive
\ \/ /___ _ __ | || | / _ \ / |
\ // _ \ ''_ \ | || |_| | | || |
/ \ __/ | | | |__ _| |_| || |
/_/\_\___|_| |_| |_|(_)___(_)_|
(XEN) Xen version 4.0.1 (root@) (gcc
version 4.4.3 (Ubuntu
4.4.3-4ubuntu5) ) Tue Feb 8 16:23:48 CET 2011
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Bootloader: GRUB 1.98-1ubuntu10
(XEN) Command line: dom0_mem=1024M dummy=dummy loglvl=all
guest_loglvl=all sync_console console_to_ring com2=115200,8n1
console=com2 lapic=debug apic_verbosity=debug apic=debug iommu=off
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009f400 (usable)
(XEN) 000000000009f400 - 00000000000a0000 (reserved)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000df62f000 (usable)
(XEN) 00000000df62f000 - 00000000df63c000 (ACPI data)
(XEN) 00000000df63c000 - 00000000df63d000 (usable)
(XEN) 00000000df63d000 - 00000000e4000000 (reserved)
(XEN) 00000000fec00000 - 00000000fee10000 (reserved)
(XEN) 00000000ff800000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 000000041ffff000 (usable)
(XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP )
(XEN) ACPI: XSDT DF630040, 00B4 (r1 HP ProLiant 2 � 162E)
(XEN) ACPI: FACP DF630140, 00F4 (r3 HP ProLiant 2 � 162E)
(XEN) ACPI: DSDT DF630240, 2005 (r1 HP DSDT 1 INTL 20030228)
(XEN) ACPI: FACS DF62F100, 0040
(XEN) ACPI: SPCR DF62F140, 0050 (r1 HP SPCRRBSU 1 � 162E)
(XEN) ACPI: MCFG DF62F1C0, 003C (r1 HP ProLiant 1 0)
(XEN) ACPI: HPET DF62F200, 0038 (r1 HP ProLiant 2 � 162E)
(XEN) ACPI: FFFF DF62F240, 0064 (r2 HP ProLiant 2 � 162E)
(XEN) ACPI: SPMI DF62F2C0, 0040 (r5 HP ProLiant 1 � 162E)
(XEN) ACPI: ERST DF62F300, 01D0 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: APIC DF62F500, 015E (r1 HP ProLiant 2 0)
(XEN) ACPI: SRAT DF62F680, 0570 (r1 HP Proliant 1 � 162E)
(XEN) ACPI: FFFF DF62FC00, 0176 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: BERT DF62FD80, 0030 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: HEST DF62FDC0, 00BC (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: DMAR DF62FE80, 0154 (r1 HP ProLiant 1 � 162E)
(XEN) ACPI: SSDT DF632280, 0125 (r3 HP CRSPCI0 2 HP 1)
(XEN) ACPI: SSDT DF6323C0, 0255 (r3 HP riser1a 2 INTL 20061109)
(XEN) ACPI: SSDT DF632640, 03BB (r1 HP pcc 1 INTL 20090625)
(XEN) ACPI: SSDT DF632A00, 0377 (r1 HP pmab 1 INTL 20090625)
(XEN) ACPI: SSDT DF632D80, 2B64 (r1 INTEL PPM RCM 1 INTL 20061109)
(XEN) System RAM: 16373MB (16766776kB)
(XEN) SRAT: PXM 0 -> APIC 0 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 1 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 2 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 3 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 4 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 5 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 6 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 7 -> Node 0
(XEN) SRAT: PXM 1 -> APIC 16 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 17 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 18 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 19 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 20 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 21 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 22 -> Node 1
(XEN) SRAT: PXM 1 -> APIC 23 -> Node 1
(XEN) SRAT: Node 0 PXM 0 0-e0000000
(XEN) SRAT: Node 0 PXM 0 100000000-220000000
(XEN) SRAT: Node 1 PXM 1 220000000-420000000
(XEN) NUMA: Using 17 for the hash shift.
(XEN) Reserving non-aligned node boundary @ mfn 0x220000
(XEN) Domain heap initialised DMA width 31 bits
(XEN) found SMP MP-table at 000f4f80
(XEN) DMI 2.6 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x908
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[904,0], pm1x_evt[900,0]
(XEN) ACPI: wakeup_vec[df62f10c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled)
(XEN) Processor #16 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
(XEN) Processor #4 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x24] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled)
(XEN) Processor #20 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x34] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x22] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled)
(XEN) Processor #18 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x32] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
(XEN) Processor #6 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x26] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x16] enabled)
(XEN) Processor #22 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x36] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
(XEN) Processor #1 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] enabled)
(XEN) Processor #17 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x31] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
(XEN) Processor #5 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x25] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] enabled)
(XEN) Processor #21 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x35] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
(XEN) Processor #3 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x23] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] enabled)
(XEN) Processor #19 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x33] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
(XEN) Processor #7 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x27] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] enabled)
(XEN) Processor #23 7:10 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x37] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
(XEN) Overriding APIC driver with bigsmp
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec80000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 0, version 32, address 0xfec80000, GSI 24-47
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Phys. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 63
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) mapped APIC to ffff82c3ffffe000 (fee00000)
(XEN) mapped IOAPIC to ffff82c3ffffd000 (fec00000)
(XEN) mapped IOAPIC to ffff82c3ffffc000 (fec80000)
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2666.818 MHz processor.
(XEN) Initing memory sharing.
(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) EPT supports 2MB super page.
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) Intel machine check reporting enabled
(XEN) I/O virtualisation disabled
(XEN) Getting VERSION: 60015
(XEN) Getting VERSION: 60015
(XEN) Getting ID: 0
(XEN) Getting LVT0: 700
(XEN) Getting LVT1: 400
(XEN) enabled ExtINT on CPU#0
(XEN) masked ExtINT on CPU#1
(XEN) masked ExtINT on CPU#2
(XEN) masked ExtINT on CPU#3
(XEN) masked ExtINT on CPU#4
(XEN) masked ExtINT on CPU#5
(XEN) masked ExtINT on CPU#6
(XEN) masked ExtINT on CPU#7
(XEN) masked ExtINT on CPU#8
(XEN) masked ExtINT on CPU#9
(XEN) masked ExtINT on CPU#10
(XEN) masked ExtINT on CPU#11
(XEN) masked ExtINT on CPU#12
(XEN) masked ExtINT on CPU#13
(XEN) masked ExtINT on CPU#14
(XEN) masked ExtINT on CPU#15
(XEN) Total of 16 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 8-0, 8-16, 8-17, 8-18, 8-19, 8-20, 8-21,
8-22, 8-23, 0-0, 0-1, 0-2, 0-3, 0-4, 0-5, 0-6, 0-7, 0-8, 0-9, 0-10,
0-11, 0-12, 0-13, 0-14, 0-15, 0-16, 0-17, 0-18, 0-19, 0-20, 0-21, 0-22,
0-23 not connected.
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #8 registers: 24.
(XEN) number of IO-APIC #0 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #8......
(XEN) .... register #00: 08000000
(XEN) ....... : physical APIC id: 08
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00170020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 0
(XEN) ....... : IO APIC version: 0020
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000
00 1 0 0 0 0 0 0 00
(XEN) 01 000 00 0 0 0 0 0 0 0 28
(XEN) 02 000 00 0 0 0 0 0 0 0 F0
(XEN) 03 000 00 0 0 0 0 0 0 0 F2
(XEN) 04 000 00 0 0 0 0 0 0 0 30
(XEN) 05 000 00 0 0 0 0 0 0 0 38
(XEN) 06 000 00 0 0 0 0 0 0 0 40
(XEN) 07 000 00 0 0 0 0 0 0 0 48
(XEN) 08 000 00 0 0 0 0 0 0 0 50
(XEN) 09 000 00 1 1 0 0 0 0 0 58
(XEN) 0a 000 00 0 0 0 0 0 0 0 60
(XEN) 0b 000 00 0 0 0 0 0 0 0 68
(XEN) 0c 000 00 0 0 0 0 0 0 0 70
(XEN) 0d 000 00 0 0 0 0 0 0 0 78
(XEN) 0e 000 00 0 0 0 0 0 0 0 88
(XEN) 0f 000 00 0 0 0 0 0 0 0 90
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) IO APIC #0......
(XEN) .... register #00: 00000000
(XEN) ....... : physical APIC id: 00
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00170020
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 0
(XEN) ....... : IO APIC version: 0020
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(XEN) .... register #03: 00000001
(XEN) ....... : Boot DT : 1
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000
00 1 0 0 0 0 0 0 00
(XEN) 01 000 00 1 0 0 0 0 0 0 00
(XEN) 02 000 00 1 0 0 0 0 0 0 00
(XEN) 03 000 00 1 0 0 0 0 0 0 00
(XEN) 04 000 00 1 0 0 0 0 0 0 00
(XEN) 05 000 00 1 0 0 0 0 0 0 00
(XEN) 06 000 00 1 0 0 0 0 0 0 00
(XEN) 07 000 00 1 0 0 0 0 0 0 00
(XEN) 08 000 00 1 0 0 0 0 0 0 00
(XEN) 09 000 00 1 0 0 0 0 0 0 00
(XEN) 0a 000 00 1 0 0 0 0 0 0 00
(XEN) 0b 000 00 1 0 0 0 0 0 0 00
(XEN) 0c 000 00 1 0 0 0 0 0 0 00
(XEN) 0d 000 00 1 0 0 0 0 0 0 00
(XEN) 0e 000 00 1 0 0 0 0 0 0 00
(XEN) 0f 000 00 1 0 0 0 0 0 0 00
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ40 -> 0:1
(XEN) IRQ242 -> 0:3
(XEN) IRQ48 -> 0:4
(XEN) IRQ56 -> 0:5
(XEN) IRQ64 -> 0:6
(XEN) IRQ72 -> 0:7
(XEN) IRQ80 -> 0:8
(XEN) IRQ88 -> 0:9
(XEN) IRQ96 -> 0:10
(XEN) IRQ104 -> 0:11
(XEN) IRQ112 -> 0:12
(XEN) IRQ120 -> 0:13
(XEN) IRQ136 -> 0:14
(XEN) IRQ144 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 2666.8091 MHz.
(XEN) ..... host bus clock speed is 133.3404 MHz.
(XEN) ..... bus_scale = 0x0000888D
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
��(XEN) Allocated console ring of 128 KiB.
(XEN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU9 resumed
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) microcode.c:73:d32767 microcode: CPU11 resumed
(XEN) microcode.c:73:d32767 microcode: CPU6 resumed
(XEN) microcode.c:73:d32767 microcode: CPU15 resumed
(XEN) microcode.c:73:d32767 microcode: CPU7 resumed
(XEN) microcode.c:73:d32767 microcode: CPU13 resumed
(XEN) microcode.c:73:d32767 microcode: CPU5 resumed
(XEN) microcode.c:73:d32767 microcode: CPU2 resumed
(XEN) microcode.c:73:d32767 microcode: CPU12 resumed
(XEN) microcode.c:73:d32767 microcode: CPU14 resumed
(XEN) microcode.c:73:d32767 microcode: CPU10 resumed
(XEN) microcode.c:73:d32767 microcode: CPU4 resumed
(XEN) Brought up 16 CPUs
(XEN) microcode.c:73:d32767 microcode: CPU8 resumed
(XEN) Turbo Mode detected!
(XEN) HPET: 4 timers in total, 0 timers will be used for broadcast
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1b1e000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000218000000->000000021c000000 (245760 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff81b1e000
(XEN) Init. ramdisk: ffffffff81b1e000->ffffffff832e3a00
(XEN) Phys-Mach map: ffffffff832e4000->ffffffff834e4000
(XEN) Start info: ffffffff834e4000->ffffffff834e44b4
(XEN) Page tables: ffffffff834e5000->ffffffff83504000
(XEN) Boot stack: ffffffff83504000->ffffffff83505000
(XEN) TOTAL: ffffffff80000000->ffffffff83800000
(XEN) ENTRY ADDRESS: ffffffff81879200
(XEN) Dom0 has maximum 16 VCPUs
(XEN) Scrubbing Free RAM:
......................................................................................................................................................done.
(XEN) trace.c:89:d32767 calc_tinfo_first_offset: NR_CPUs 128,
offset_in_bytes 258, t_info_first_offset 65
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen)
(XEN) Freed 176kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32.27 (root@xen1) (gcc version 4.4.3
(Ubuntu 4.4.3-4ubuntu5) ) #3 SMP Mon Jan 24 22:01:25 CET 2011
[ 0.000000] Command line: dummy=dummy root=/dev/cciss/c0d0p1 ro
console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] released 0 pages of unused memory
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] Xen: 000000000009f400 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000040000000 (usable)
[ 0.000000] Xen: 00000000df62f000 - 00000000df63c000 (ACPI data)
[ 0.000000] Xen: 00000000df63d000 - 00000000e4000000 (reserved)
[ 0.000000] Xen: 00000000fec00000 - 00000000fee10000 (reserved)
[ 0.000000] Xen: 00000000ff800000 - 0000000100000000 (reserved)
[ 0.000000] Xen: 0000000100000000 - 0000000340000000 (usable)
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] DMI 2.6 present.
[ 0.000000] last_pfn = 0x340000 max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new
0x7010600070106
[ 0.000000] last_pfn = 0x40000 max_arch_pfn = 0x400000000
[ 0.000000] e820 update range: 0000000000001000 - 0000000000006000
(usable) ==> (reserved)
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable)
[ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved)
[ 0.000000] modified: 0000000000006000 - 000000000009f400 (usable)
[ 0.000000] modified: 000000000009f400 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 0000000040000000 (usable)
[ 0.000000] modified: 00000000df62f000 - 00000000df63c000 (ACPI data)
[ 0.000000] modified: 00000000df63d000 - 00000000e4000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 00000000fee10000 (reserved)
[ 0.000000] modified: 00000000ff800000 - 0000000100000000 (reserved)
[ 0.000000] modified: 0000000100000000 - 0000000340000000 (usable)
[ 0.000000] initial memory mapped : 0 - 03fff000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000040000000
[ 0.000000] 0000000000 - 0040000000 page 4k
[ 0.000000] kernel direct mapping tables up to 40000000 @ 100000-302000
[ 0.000000] init_memory_mapping: 0000000100000000-0000000340000000
[ 0.000000] 0100000000 - 0340000000 page 4k
[ 0.000000] kernel direct mapping tables up to 340000000 @
3504000-4f12000
[ 0.000000] RAMDISK: 01b1e000 - 032e3a00
[ 0.000000] ACPI: RSDP 00000000000f4f00 00024 (v02 HP )
[ 0.000000] ACPI: XSDT 00000000df630040 000B4 (v01 HP ProLiant
00000002 �? 0000162E)
[ 0.000000] ACPI: FACP 00000000df630140 000F4 (v03 HP ProLiant
00000002 �? 0000162E)
[ 0.000000] ACPI Warning: Invalid length for Pm1aControlBlock: 32,
using default 16 (20090903/tbfadt-607)
[ 0.000000] ACPI Warning: Invalid length for Pm2ControlBlock: 32,
using default 8 (20090903/tbfadt-607)
[ 0.000000] ACPI: DSDT 00000000df630240 02005 (v01 HP DSDT
00000001 INTL 20030228)
[ 0.000000] ACPI: FACS 00000000df62f100 00040
[ 0.000000] ACPI: SPCR 00000000df62f140 00050 (v01 HP SPCRRBSU
00000001 �? 0000162E)
[ 0.000000] ACPI: MCFG 00000000df62f1c0 0003C (v01 HP ProLiant
00000001 00000000)
[ 0.000000] ACPI: HPET 00000000df62f200 00038 (v01 HP ProLiant
00000002 �? 0000162E)
[ 0.000000] ACPI: FFFF 00000000df62f240 00064 (v02 HP ProLiant
00000002 �? 0000162E)
[ 0.000000] ACPI: SPMI 00000000df62f2c0 00040 (v05 HP ProLiant
00000001 �? 0000162E)
[ 0.000000] ACPI: ERST 00000000df62f300 001D0 (v01 HP ProLiant
00000001 �? 0000162E)
[ 0.000000] ACPI: APIC 00000000df62f500 0015E (v01 HP ProLiant
00000002 00000000)
[ 0.000000] ACPI: SRAT 00000000df62f680 00570 (v01 HP Proliant
00000001 �? 0000162E)
[ 0.000000] ACPI: FFFF 00000000df62fc00 00176 (v01 HP ProLiant
00000001 �? 0000162E)
[ 0.000000] ACPI: BERT 00000000df62fd80 00030 (v01 HP ProLiant
00000001 �? 0000162E)
[ 0.000000] ACPI: HEST 00000000df62fdc0 000BC (v01 HP ProLiant
00000001 �? 0000162E)
[ 0.000000] ACPI: XMAR 00000000df62fe80 00154 (v01 HP ProLiant
00000001 �? 0000162E)
[ 0.000000] ACPI: SSDT 00000000df632280 00125 (v03 HP CRSPCI0
00000002 HP 00000001)
[ 0.000000] ACPI: SSDT 00000000df6323c0 00255 (v03 HP riser1a
00000002 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000df632640 003BB (v01 HP pcc
00000001 INTL 20090625)
[ 0.000000] ACPI: SSDT 00000000df632a00 00377 (v01 HP pmab
00000001 INTL 20090625)
[ 0.000000] ACPI: SSDT 00000000df632d80 02B64 (v01 INTEL PPM RCM
00000001 INTL 20061109)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-0000000340000000
[ 0.000000] Bootmem setup node 0 0000000000000000-0000000340000000
[ 0.000000] NODE_DATA [0000000000008000 - 000000000000cfff]
[ 0.000000] bootmap [000000000000d000 - 0000000000074fff] pages 68
[ 0.000000] (10 early reservations) ==> bootmem [0000000000 - 0340000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [00034e5000 - 0003504000] XEN PAGETABLES ==>
[00034e5000 - 0003504000]
[ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==>
[0000006000 - 0000008000]
[ 0.000000] #3 [0001000000 - 00019f33a4] TEXT DATA BSS ==>
[0001000000 - 00019f33a4]
[ 0.000000] #4 [0001b1e000 - 00032e3a00] RAMDISK ==>
[0001b1e000 - 00032e3a00]
[ 0.000000] #5 [00032e4000 - 00034e5000] XEN START INFO ==>
[00032e4000 - 00034e5000]
[ 0.000000] #6 [0100000000 - 0340000000] XEN EXTRA ==>
[0100000000 - 0340000000]
[ 0.000000] #7 [00019f4000 - 0001a00180] BRK ==>
[00019f4000 - 0001a00180]
[ 0.000000] #8 [0000100000 - 00002e0000] PGTABLE ==>
[0000100000 - 00002e0000]
[ 0.000000] #9 [0003504000 - 000470d000] PGTABLE ==>
[0003504000 - 000470d000]
[ 0.000000] found SMP MP-table at [ffff8800000f4f80] f4f80
(XEN) mm.c:860:d0 Error getting mfn 100 (pfn 5555555555555555) from L1
entry 8000000000100463 for l1e_owner=0, pg_owner=0
(XEN) mm.c:4644:d0 ptwr_emulate: could not get_page_from_l1e()
(XEN) d0:v0: unhandled page fault (ec=0003)
(XEN) Pagetable walk from ffffffff8193a008:
(XEN) L4[0x1ff] = 0000000219003067 0000000000001003
(XEN) L3[0x1fe] = 0000000219007067 0000000000001007
(XEN) L2[0x00c] = 000000021b4f4067 00000000000034f4
(XEN) L1[0x13a] = 001000021993a065 000000000000193a
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-4.0.1 x86_64 debug=n Tainted: C ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff8187dac9>]
(XEN) RFLAGS: 0000000000000246 EM: 1 CONTEXT: pv guest
(XEN) rax: 0000000000000000 rbx: ffffffff8193a008 rcx: 0000000000000040
(XEN) rdx: 0000000010000001 rsi: 8000000000100463 rdi: ffffffff8193a008
(XEN) rbp: ffffffff817bddb8 rsp: ffffffff817bdd50 r8: 0000000000007ff0
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 8000000000100463 r13: 8000000000100463 r14: 8000000000000563
(XEN) r15: 0000000000100000 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000219001000 cr2: ffffffff8193a008
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff817bdd50:
(XEN) 0000000000000040 0000000000000000 0000000000000003 ffffffff8187dac9
(XEN) 000000010000e030 0000000000010046 ffffffff817bdd98 000000000000e02b
(XEN) ffffffff8187dac9 8000000000100463 0000000000000000 00000000000ff91f
(XEN) 0000000000000001 ffffffff817bde18 ffffffff81890c3f 000000000000b080
(XEN) 0000000000000001 ffffffffff401000 000009fe00000001 00000000000f4f90
(XEN) 00000000000ff91f 000000000000b080 0000000000000001 0000000040000000
(XEN) 0000000000000000 ffffffff817bde28 ffffffff81890d23 ffffffff817bde48
(XEN) ffffffff818878ed ffff8800000f4f80 000000000000b080 ffffffff817bde78
(XEN) ffffffff81887a00 ffffffff817bde78 0000000000000001 00000000032e3a00
(XEN) 00000000017c5a00 ffffffff817bde98 ffffffff81887a79 ffffffff817bde98
(XEN) ffff8800032e3a00 ffffffff817bdf48 ffffffff8187f96d ffffffff817bdef8
(XEN) 7ffa4893da32f7d5 ffffffff8100fb28 ffffffff818b6400 0000000000000000
(XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff817bdf48
(XEN) ffffffff815594e0 0000000000000010 ffffffff817bdf58 ffffffff817bdf18
(XEN) 7ffa4893da32f7d5 ffffffff817bdf38 ffffffff818b6400 0000000000000000
(XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff817bdf88
(XEN) ffffffff81879a7c 7ffa4893da32f7d5 ffffffff818b9c20 00000000019f33a4
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff817bdfa8
(XEN) ffffffff8187933a ffffffff8186e5a0 ffffffff81001000 ffffffff817bdff8
(XEN) ffffffff8187d381 0000000000000000 0000000000000000 0000000000000000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
On 02/09/2011 12:50 PM, Ian Campbell wrote:>
> vmlinux is found at the top level of the directory where you built the
> kernel, it is an uncompressed, unstripped ELF file which you should be
> able to run gdb on.
>
> You are right that running gdb on e.g. a bzImage won''t work. Even
if you
> were to extract the ELF file from the bzImage container it would be
> stripped and hence not very useful.
>
>> Bastian
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-Feb-09 14:43 UTC
Re: [Xen-devel] reboot after "scrubbing free ram"
Thanks the useful info.
Could you please try the appended patch (just to rule out a similar
issue we found recently)?
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 947f42a..66637bd 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@ -283,6 +283,8 @@ unsigned long __init_refok init_memory_mapping(unsigned long
start,
if (!after_bootmem && !start) {
pud_t *pud;
pmd_t *pmd;
+ unsigned long addr;
+ u64 size, memblock_addr;
mmu_cr4_features = read_cr4();
@@ -291,11 +293,18 @@ unsigned long __init_refok init_memory_mapping(unsigned
long start,
* located on different 2M pages. cleanup_highmap(), however,
* can only consider _end when it runs, so destroy any
* mappings beyond _brk_end here.
+ * Respect memblock reserved regions.
*/
pud = pud_offset(pgd_offset_k(_brk_end), _brk_end);
pmd = pmd_offset(pud, _brk_end - 1);
- while (++pmd <= pmd_offset(pud, (unsigned long)_end - 1))
- pmd_clear(pmd);
+ addr = (_brk_end + PMD_SIZE - 1) & PMD_MASK;
+ while (++pmd <= pmd_offset(pud, (unsigned long)_end - 1)) {
+ memblock_addr = memblock_x86_find_in_range_size(__pa(addr),
+ &size, PMD_SIZE);
+ if (memblock_addr == (u64) __pa(addr) && size >= PMD_SIZE)
+ pmd_clear(pmd);
+ addr += PMD_SIZE;
+ }
}
#endif
__flush_tlb_all();
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Stefano Stabellini
2011-Feb-09 14:49 UTC
[SPAM] Re: [Xen-devel] reboot after "scrubbing free ram"
On Wed, 9 Feb 2011, Stefano Stabellini wrote:> Thanks the useful info. > Could you please try the appended patch (just to rule out a similar > issue we found recently)? >actually I have a better one diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c index 73ffd55..69f73c1 100644 --- a/arch/x86/mm/init.c +++ b/arch/x86/mm/init.c @@ -287,7 +287,7 @@ unsigned long __init_refok init_memory_mapping(unsigned long start, load_cr3(swapper_pg_dir); #endif -#ifdef CONFIG_X86_64 +#if 0 if (!after_bootmem && !start) { pud_t *pud; pmd_t *pmd; _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Same problem. 2.6.32.25 works fine, btw. On 02/09/2011 03:49 PM, Stefano Stabellini wrote:> On Wed, 9 Feb 2011, Stefano Stabellini wrote: > >> Thanks the useful info. >> Could you please try the appended patch (just to rule out a similar >> issue we found recently)? >> > actually I have a better one > > > > diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c > index 73ffd55..69f73c1 100644 > --- a/arch/x86/mm/init.c > +++ b/arch/x86/mm/init.c > @@ -287,7 +287,7 @@ unsigned long __init_refok init_memory_mapping(unsigned long start, > load_cr3(swapper_pg_dir); > #endif > > -#ifdef CONFIG_X86_64 > +#if 0 > if (!after_bootmem && !start) { > pud_t *pud; > pmd_t *pmd; >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel