Mailing List Archive

xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0
Hi Jeremy/Konrad,

I'm still trying to get the current linus tree (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) to boot as a dom0 kernel under a xen 4.1.1 hypervisor.
But still can't boot (after compiling with tracers disabled).

.config attached


Serial log:

__ __ _ _ _ _
\ \/ /___ _ __ | || | / | / |
\ // _ \ '_ \ | || |_ | | | |
/ \ __/ | | | |__ _|| |_| |
/_/\_\___|_| |_| |_|(_)_(_)_|

(XEN) Xen version 4.1.1 (root@dyndns.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) Thu Jun 16 11:28:46 CEST 2011
(XEN) Latest ChangeSet: Tue Jun 14 14:02:48 2011 +0100 23079:73a8061b01f1
(XEN) Bootloader: GRUB 1.98+20100804-14
(XEN) Command line: dom0_mem=768M loglvl=all loglvl_guest=all console_timestamps vga=gfx-1280x1024x32 cpuidle cpufreq=xe
n noreboot debug lapic=debug apic_verbosity=debug apic=debug com1=115200,8n1 console=vga,com1
(XEN) Video information:
(XEN) VGA is graphics mode 1280x1024, 32 bpp
(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 - 000000000009f000 (usable)
(XEN) 000000000009f000 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000aff90000 (usable)
(XEN) 00000000aff90000 - 00000000aff9e000 (ACPI data)
(XEN) 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
(XEN) 00000000affe0000 - 00000000b0000000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000250000000 (usable)
(XEN) ACPI: RSDP 000FB100, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT AFF90000, 0048 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: FACP AFF90200, 0084 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: DSDT AFF905E0, 9427 (r1 A7640 A7640100 100 INTL 20051117)
(XEN) ACPI: FACS AFF9E000, 0040
(XEN) ACPI: APIC AFF90390, 0088 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: MCFG AFF90420, 003C (r1 7640MS OEMMCFG 20100913 MSFT 97)
(XEN) ACPI: SLIC AFF90460, 0176 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: OEMB AFF9E040, 0072 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: SRAT AFF9A5E0, 0108 (r3 AMD FAM_F_10 2 AMD 1)
(XEN) ACPI: HPET AFF9A6F0, 0038 (r1 7640MS OEMHPET 20100913 MSFT 97)
(XEN) ACPI: IVRS AFF9A730, 0100 (r1 AMD RD890S 202031 AMD 0)
(XEN) ACPI: SSDT AFF9A830, 0DA4 (r1 A M I POWERNOW 1 AMD 1)
(XEN) System RAM: 8191MB (8387772kB)
(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: Node 0 PXM 0 0-a0000
(XEN) SRAT: Node 0 PXM 0 100000-b0000000
(XEN) SRAT: Node 0 PXM 0 100000000-250000000
(XEN) NUMA: Allocated memnodemap from 24e17b000 - 24e17e000
(XEN) NUMA: Using 8 for the hash shift.
(XEN) Domain heap initialised
(XEN) vesafb: framebuffer at 0xfb000000, mapped to 0xffff82c000000000, using 6144k, total 14336k
(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
(XEN) found SMP MP-table at 000ff780
(XEN) DMI 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[aff9e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) Processor #2 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) Processor #4 0:10 APIC version 16
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) Processor #5 0:10 APIC version 16
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-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 low 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: 0x8300 base: 0xfed00000
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
(XEN) PCI: Not using MMCONFIG.
(XEN) Table is not found!
(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 (fec20000)
(XEN) IRQ limits: 56 GSI, 1112 MSI/MSI-X
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3200.196 MHz processor.
(XEN) Initing memory sharing.
(XEN) AMD Fam10h machine check reporting enabled
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Getting VERSION: 80050010
(XEN) Getting VERSION: 80050010
(XEN) Getting ID: 0
(XEN) Getting LVT0: 700
(XEN) Getting LVT1: 400
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 0x00000004 after: 0x00000000
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 6-0, 6-16, 6-17, 6-18, 6-19, 6-20, 6-21, 6-22, 6-23, 7-0, 7-1, 7-2, 7-3, 7-4, 7-5, 7-6, 7-7,
7-8, 7-9, 7-10, 7-11, 7-12, 7-13, 7-14, 7-15, 7-16, 7-17, 7-18, 7-19, 7-20, 7-21, 7-22, 7-23, 7-24, 7-25, 7-26, 7-27, 7
-28, 7-29, 7-30, 7-31 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 #6 registers: 24.
(XEN) number of IO-APIC #7 registers: 32.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #6......
(XEN) .... register #00: 06000000
(XEN) ....... : physical APIC id: 06
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178021
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0021
(XEN) .... register #02: 06000000
(XEN) ....... : arbitration: 06
(XEN) .... register #03: 07000000
(XEN) ....... : Boot DT : 0
(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 001 01 0 0 0 0 0 1 1 30
(XEN) 02 001 01 0 0 0 0 0 1 1 F0
(XEN) 03 001 01 0 0 0 0 0 1 1 38
(XEN) 04 001 01 0 0 0 0 0 1 1 F1
(XEN) 05 001 01 0 0 0 0 0 1 1 40
(XEN) 06 001 01 0 0 0 0 0 1 1 48
(XEN) 07 001 01 0 0 0 0 0 1 1 50
(XEN) 08 001 01 0 0 0 0 0 1 1 58
(XEN) 09 001 01 1 1 0 1 0 1 1 60
(XEN) 0a 001 01 0 0 0 0 0 1 1 68
(XEN) 0b 001 01 0 0 0 0 0 1 1 70
(XEN) 0c 001 01 0 0 0 0 0 1 1 78
(XEN) 0d 001 01 0 0 0 0 0 1 1 88
(XEN) 0e 001 01 0 0 0 0 0 1 1 90
(XEN) 0f 001 01 0 0 0 0 0 1 1 98
(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 #7......
(XEN) .... register #00: 07000000
(XEN) ....... : physical APIC id: 07
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 001F8021
(XEN) ....... : max redirection entries: 001F
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0021
(XEN) .... register #02: 00000000
(XEN) ....... : arbitration: 00
(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) 18 000 00 1 0 0 0 0 0 0 00
(XEN) 19 000 00 1 0 0 0 0 0 0 00
(XEN) 1a 000 00 1 0 0 0 0 0 0 00
(XEN) 1b 000 00 1 0 0 0 0 0 0 00
(XEN) 1c 000 00 1 0 0 0 0 0 0 00
(XEN) 1d 000 00 1 0 0 0 0 0 0 00
(XEN) 1e 000 00 1 0 0 0 0 0 0 00
(XEN) 1f 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) IRQ48 -> 0:1
(XEN) IRQ56 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ64 -> 0:5
(XEN) IRQ72 -> 0:6
(XEN) IRQ80 -> 0:7
(XEN) IRQ88 -> 0:8
(XEN) IRQ96 -> 0:9
(XEN) IRQ104 -> 0:10
(XEN) IRQ112 -> 0:11
(XEN) IRQ120 -> 0:12
(XEN) IRQ136 -> 0:13
(XEN) IRQ144 -> 0:14
(XEN) IRQ152 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 3200.1301 MHz.
(XEN) ..... host bus clock speed is 200.0080 MHz.
(XEN) ..... bus_scale = 0x0000CCD7
(XEN) [2011-08-03 11:02:25] Platform timer is 14.318MHz HPET
ΓΏ(XEN) [2011-08-03 11:02:25] Allocated console ring of 64 KiB.
(XEN) [2011-08-03 11:02:25] HVM: ASIDs enabled.
(XEN) [2011-08-03 11:02:25] SVM: Supported advanced features:
(XEN) [2011-08-03 11:02:25] - Nested Page Tables (NPT)
(XEN) [2011-08-03 11:02:25] - Last Branch Record (LBR) Virtualisation
(XEN) [2011-08-03 11:02:25] - Next-RIP Saved on #VMEXIT
(XEN) [2011-08-03 11:02:25] - Pause-Intercept Filter
(XEN) [2011-08-03 11:02:25] HVM: SVM enabled
(XEN) [2011-08-03 11:02:25] HVM: Hardware Assisted Paging detected.
(XEN) [2011-08-03 11:02:24] masked ExtINT on CPU#1
(XEN) [2011-08-03 11:02:24] masked ExtINT on CPU#2
(XEN) [2011-08-03 11:02:24] masked ExtINT on CPU#3
(XEN) [2011-08-03 11:02:24] masked ExtINT on CPU#4
(XEN) [2011-08-03 11:02:24] masked ExtINT on CPU#5
(XEN) [2011-08-03 11:02:26] Brought up 6 CPUs
(XEN) [2011-08-03 11:02:26] HPET's MSI mode hasn't been supported when Interrupt Remapping is enabled.
(XEN) [2011-08-03 11:02:26] ACPI sleep modes: S3
(XEN) [2011-08-03 11:02:26] MCA: Use hw thresholding to adjust polling frequency
(XEN) [2011-08-03 11:02:26] mcheck_poll: Machine check polling timer started.
(XEN) [2011-08-03 11:02:26] Xenoprofile: Failed to setup IBS LVT offset, IBSCTL = 0xffffffff
(XEN) [2011-08-03 11:02:26] *** LOADING DOMAIN 0 ***
(XEN) [2011-08-03 11:02:26] elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa47000
(XEN) [2011-08-03 11:02:26] elf_parse_binary: phdr: paddr=0x1c00000 memsz=0x880e0
(XEN) [2011-08-03 11:02:26] elf_parse_binary: phdr: paddr=0x1c87000 memsz=0x1000
(XEN) [2011-08-03 11:02:26] elf_parse_binary: phdr: paddr=0x1c89000 memsz=0x124c0
(XEN) [2011-08-03 11:02:26] elf_parse_binary: phdr: paddr=0x1c9c000 memsz=0x2ac000
(XEN) [2011-08-03 11:02:26] elf_parse_binary: memory: 0x1000000 -> 0x1f48000
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: GUEST_OS = "linux"
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: ENTRY = 0xffffffff81c9c200
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: PAE_MODE = "yes"
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: LOADER = "generic"
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) [2011-08-03 11:02:26] elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) [2011-08-03 11:02:26] elf_xen_addr_calc_check: addresses:
(XEN) [2011-08-03 11:02:26] virt_base = 0xffffffff80000000
(XEN) [2011-08-03 11:02:26] elf_paddr_offset = 0x0
(XEN) [2011-08-03 11:02:26] virt_offset = 0xffffffff80000000
(XEN) [2011-08-03 11:02:26] virt_kstart = 0xffffffff81000000
(XEN) [2011-08-03 11:02:26] virt_kend = 0xffffffff81f48000
(XEN) [2011-08-03 11:02:26] virt_entry = 0xffffffff81c9c200
(XEN) [2011-08-03 11:02:26] p2m_base = 0xffffffffffffffff
(XEN) [2011-08-03 11:02:26] Xen kernel: 64-bit, lsb, compat32
(XEN) [2011-08-03 11:02:26] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1f48000
(XEN) [2011-08-03 11:02:26] PHYSICAL MEMORY ARRANGEMENT:
(XEN) [2011-08-03 11:02:26] Dom0 alloc.: 0000000244000000->0000000248000000 (178564 pages to be allocated)
(XEN) [2011-08-03 11:02:26] Init. ramdisk: 000000024f984000->000000024ffff400
(XEN) [2011-08-03 11:02:26] VIRTUAL MEMORY ARRANGEMENT:
(XEN) [2011-08-03 11:02:26] Loaded kernel: ffffffff81000000->ffffffff81f48000
(XEN) [2011-08-03 11:02:26] Init. ramdisk: ffffffff81f48000->ffffffff825c3400
(XEN) [2011-08-03 11:02:26] Phys-Mach map: ffffffff825c4000->ffffffff82744000
(XEN) [2011-08-03 11:02:26] Start info: ffffffff82744000->ffffffff827444b4
(XEN) [2011-08-03 11:02:26] Page tables: ffffffff82745000->ffffffff8275c000
(XEN) [2011-08-03 11:02:26] Boot stack: ffffffff8275c000->ffffffff8275d000
(XEN) [2011-08-03 11:02:26] TOTAL: ffffffff80000000->ffffffff82800000
(XEN) [2011-08-03 11:02:26] ENTRY ADDRESS: ffffffff81c9c200
(XEN) [2011-08-03 11:02:26] Dom0 has maximum 6 VCPUs
(XEN) [2011-08-03 11:02:26] elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81a47000
(XEN) [2011-08-03 11:02:26] elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81c880e0
(XEN) [2011-08-03 11:02:26] elf_load_binary: phdr 2 at 0xffffffff81c87000 -> 0xffffffff81c88000
(XEN) [2011-08-03 11:02:26] elf_load_binary: phdr 3 at 0xffffffff81c89000 -> 0xffffffff81c9b4c0
(XEN) [2011-08-03 11:02:26] elf_load_binary: phdr 4 at 0xffffffff81c9c000 -> 0xffffffff81d40000
(XEN) [2011-08-03 11:02:26] Scrubbing Free RAM: ........................................................................
.done.
(XEN) [2011-08-03 11:02:28] Xen trace buffers: disabled
(XEN) [2011-08-03 11:02:28] Std. Loglevel: All
(XEN) [2011-08-03 11:02:28] Guest Loglevel: All
(XEN) [2011-08-03 11:02:28] Xen is relinquishing VGA console.
(XEN) [2011-08-03 11:02:28] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) [2011-08-03 11:02:28] Freed 216kB 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 3.0.0nexttry-20110803+ (root@serveerstertje) (gcc version 4.4.5 (Debian 4.4.5-8) ) #7 SMP W
ed Aug 3 12:49:12 CEST 2011
[ 0.000000] Command line: root=/dev/mapper/serveerstertje-root ro console=hvc0 console=tty console=vga nomodeset vga=
794 video=vesafb earlyprintk=xen max_loop=255 loop_max_part=63
[ 0.000000] released 0 pages of unused memory
[ 0.000000] Set 327889 page(s) to 1-1 mapping.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 000000000009f000 (usable)
[ 0.000000] Xen: 000000000009f000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000030000000 (usable)
[ 0.000000] Xen: 0000000030000000 - 00000000aff90000 (unusable)
[ 0.000000] Xen: 00000000aff90000 - 00000000aff9e000 (ACPI data)
[ 0.000000] Xen: 00000000aff9e000 - 00000000affe0000 (ACPI NVS)
[ 0.000000] Xen: 00000000affe0000 - 00000000b0000000 (reserved)
[ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] Xen: 00000000fec20000 - 00000000fec21000 (reserved)
[ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] Xen: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] Xen: 0000000100000000 - 00000002b0000000 (usable)
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0x2b0000 max_arch_pfn = 0x400000000
[ 0.000000] last_pfn = 0x30000 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780
[ 0.000000] init_memory_mapping: 0000000000000000-0000000030000000
[ 0.000000] init_memory_mapping: 0000000100000000-00000002b0000000
[ 0.000000] RAMDISK: 01f48000 - 025c4000
[ 0.000000] ACPI: RSDP 00000000000fb100 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 00000000aff90000 00048 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: FACP 00000000aff90200 00084 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: DSDT 00000000aff905e0 09427 (v01 A7640 A7640100 00000100 INTL 20051117)
[ 0.000000] ACPI: FACS 00000000aff9e000 00040
[ 0.000000] ACPI: APIC 00000000aff90390 00088 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: MCFG 00000000aff90420 0003C (v01 7640MS OEMMCFG 20100913 MSFT 00000097)
[ 0.000000] ACPI: SLIC 00000000aff90460 00176 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: OEMB 00000000aff9e040 00072 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: SRAT 00000000aff9a5e0 00108 (v03 AMD FAM_F_10 00000002 AMD 00000001)
[ 0.000000] ACPI: HPET 00000000aff9a6f0 00038 (v01 7640MS OEMHPET 20100913 MSFT 00000097)
[ 0.000000] ACPI: IVRS 00000000aff9a730 00100 (v01 AMD RD890S 00202031 AMD 00000000)
[ 0.000000] ACPI: SSDT 00000000aff9a830 00DA4 (v01 A M I POWERNOW 00000001 AMD 00000001)
[ 0.000000] Scanning NUMA topology in Northbridge 24
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-00000002b0000000
[ 0.000000] Initmem setup node 0 0000000000000000-00000002b0000000
[ 0.000000] NODE_DATA [000000002fffb000 - 000000002fffffff]
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x002b0000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[3] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x00030000
[ 0.000000] 0: 0x00100000 -> 0x002b0000
(XEN) [2011-08-03 11:02:28] mm.c:907:d0 Error getting mfn 1c88 (pfn 5555555555555555) from L1 entry 8000000001c88465 for
l1e_owner=0, pg_owner=0
(XEN) [2011-08-03 11:02:28] mm.c:4967:d0 ptwr_emulate: could not get_page_from_l1e()
[ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0
[ 0.000000] PGD 0
[ 0.000000] Oops: 0003 [#1] SMP
[ 0.000000] CPU 0
[ 0.000000] Modules linked in:
[ 0.000000]
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.0.0nexttry-20110803+ #7 MSI MS-7640/890FXA-GD70 (MS-7640)
[ 0.000000] RIP: e030:[<ffffffff810074d4>] [<ffffffff810074d4>] xen_set_pte+0x24/0xe0
[ 0.000000] RSP: e02b:ffffffff81c01df8 EFLAGS: 00010097
[ 0.000000] RAX: 0000000000000000 RBX: ffff880001d43ff8 RCX: ffffffffff5ff000
[ 0.000000] RDX: 0000000010000001 RSI: 8000000001c88465 RDI: ffff880001d43ff8
[ 0.000000] RBP: ffffffff81c01e28 R08: aaaaaaaaaaaaaaaa R09: 000000002fe4c000
[ 0.000000] R10: 00000000deadbeef R11: 0000000000001000 R12: 8000000001c88465
[ 0.000000] R13: 000000000067b400 R14: 0000000030000000 R15: 0000000000000000
[ 0.000000] FS: 0000000000000000(0000) GS:ffffffff81c89000(0000) knlGS:0000000000000000
[ 0.000000] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: 0000000000000000 CR3: 0000000001c04000 CR4: 0000000000000660
[ 0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 0.000000] DR3: 0000000000000000 DR6: 0000000000000000 DR7: 0000000000000000
[ 0.000000] Process swapper (pid: 0, threadinfo ffffffff81c00000, task ffffffff81c0c020)
[ 0.000000] Stack:
[ 0.000000] ffffffffff5ff000 ffffffff81032160 ffffffffff5ff000 ffffffffff5ff000
[ 0.000000] 8000000001c88465 000000000067b400 ffffffff81c01e48 ffffffff81032393
[ 0.000000] 0000000000000800 8000000001c88465 ffffffff81c01e58 ffffffff81032400
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81032160>] ? fill_pte+0x30/0x100
[ 0.000000] [<ffffffff81032393>] set_pte_vaddr_pud+0x43/0x60
[ 0.000000] [<ffffffff81032400>] set_pte_vaddr+0x50/0x70
[ 0.000000] [<ffffffff810366d6>] __native_set_fixmap+0x26/0x30
[ 0.000000] [<ffffffff810051f1>] xen_set_fixmap+0xa1/0x160
[ 0.000000] [<ffffffff81ca3689>] map_vsyscall+0x50/0x55
[ 0.000000] [<ffffffff81ca2c9a>] setup_arch+0xa50/0xae3
[ 0.000000] [<ffffffff816d56d1>] ? printk+0x3c/0x3e
[ 0.000000] [<ffffffff81c9c999>] start_kernel+0x90/0x356
[ 0.000000] [<ffffffff81c9c346>] x86_64_start_reservations+0x131/0x135
[ 0.000000] [<ffffffff81c9ffed>] xen_start_kernel+0x5fb/0x602
[ 0.000000] Code: 1f 84 00 00 00 00 00 55 48 89 e5 48 83 ec 30 48 89 5d e8 4c 89 65 f0 48 89 fb 4c 89 6d f8 49 89 f4
e8 c1 66 02 00 83 f8 01 74 14 <4c> 89 23 48 8b 5d e8 4c 8b 65 f0 4c 8b 6d f8 c9 c3 0f 1f 00 ff
[ 0.000000] RIP [<ffffffff810074d4>] xen_set_pte+0x24/0xe0
[ 0.000000] RSP <ffffffff81c01df8>
[ 0.000000] CR2: 0000000000000000
[ 0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[ 0.000000] Pid: 0, comm: swapper Tainted: G D 3.0.0nexttry-20110803+ #7
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff816d557f>] panic+0x8c/0x1a2
[ 0.000000] [<ffffffff8104ee95>] do_exit+0x7b5/0x8d0
[ 0.000000] [<ffffffff816d7ff0>] ? _raw_spin_unlock_irqrestore+0x10/0x20
[ 0.000000] [<ffffffff8104ad35>] ? kmsg_dump+0x45/0xf0
[ 0.000000] [<ffffffff816d9375>] oops_end+0xa5/0xf0
[ 0.000000] [<ffffffff81032ac3>] no_context+0xf3/0x260
[ 0.000000] [<ffffffff81032d55>] __bad_area_nosemaphore+0x125/0x1e0
[ 0.000000] [<ffffffff8100769f>] ? __raw_callee_save_xen_restore_fl+0x11/0x1e
[ 0.000000] [<ffffffff81032e1e>] bad_area_nosemaphore+0xe/0x10
[ 0.000000] [<ffffffff816db886>] do_page_fault+0x316/0x460
[ 0.000000] [<ffffffff81cbb467>] ? memblock_find_region+0x45/0x7b
[ 0.000000] [<ffffffff81cbb467>] ? memblock_find_region+0x45/0x7b
[ 0.000000] [<ffffffff81cbba8f>] ? memblock_add_region+0x7f/0x3f1
[ 0.000000] [<ffffffff81cbb801>] ? memblock_find_base+0x9/0xab
[ 0.000000] [<ffffffff816d8735>] page_fault+0x25/0x30
[ 0.000000] [<ffffffff810074d4>] ? xen_set_pte+0x24/0xe0
[ 0.000000] [<ffffffff810074cf>] ? xen_set_pte+0x1f/0xe0
[ 0.000000] [<ffffffff81032160>] ? fill_pte+0x30/0x100
[ 0.000000] [<ffffffff81032393>] set_pte_vaddr_pud+0x43/0x60
[ 0.000000] [<ffffffff81032400>] set_pte_vaddr+0x50/0x70
[ 0.000000] [<ffffffff810366d6>] __native_set_fixmap+0x26/0x30
[ 0.000000] [<ffffffff810051f1>] xen_set_fixmap+0xa1/0x160
[ 0.000000] [<ffffffff81ca3689>] map_vsyscall+0x50/0x55
[ 0.000000] [<ffffffff81ca2c9a>] setup_arch+0xa50/0xae3
[ 0.000000] [<ffffffff816d56d1>] ? printk+0x3c/0x3e
[ 0.000000] [<ffffffff81c9c999>] start_kernel+0x90/0x356
[ 0.000000] [<ffffffff81c9c346>] x86_64_start_reservations+0x131/0x135
[ 0.000000] [<ffffffff81c9ffed>] xen_start_kernel+0x5fb/0x602
(XEN) [2011-08-03 11:02:28] Domain 0 crashed: 'noreboot' set - not rebooting.
Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0 [ In reply to ]
On Wed, Aug 03, 2011 at 01:18:24PM +0200, Sander Eikelenboom wrote:
> Hi Jeremy/Konrad,
>
> I'm still trying to get the current linus tree (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) to boot as a dom0 kernel under a xen 4.1.1 hypervisor.
> But still can't boot (after compiling with tracers disabled).

Yeah, there is a bug introduced by Andy. Here is a patchset that fixes it:

http://marc.info/?i=cover.1311736366.git.luto@mit.edu

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0 [ In reply to ]
On Wed, Aug 03, 2011 at 09:41:29AM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Aug 03, 2011 at 01:18:24PM +0200, Sander Eikelenboom wrote:
> > Hi Jeremy/Konrad,
> >
> > I'm still trying to get the current linus tree (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) to boot as a dom0 kernel under a xen 4.1.1 hypervisor.
> > But still can't boot (after compiling with tracers disabled).
>
> Yeah, there is a bug introduced by Andy. Here is a patchset that fixes it:
>
> http://marc.info/?i=cover.1311736366.git.luto@mit.edu

Oh, and a new version is http://marc.info/?i=cover.1312378163.git.luto@mit.edu
>
> _______________________________________________
> 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
Re: Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0 [ In reply to ]
Hi Konrad,

Thx, after applying those patches it boots as dom0 and xen-pciback seems to work as well from my first tests.
The compile problems reported in my earlier mail are still present (related to tracing and i think jeremy's patches).

Something that catched my eye when doing a make menuconfig:
<*> Xen virtual block device support
<*> Block-device backend driver

I think the backend description should also start with "Xen" as all xen specific drivers do ?

--
Sander


Wednesday, August 3, 2011, 3:51:52 PM, you wrote:

> On Wed, Aug 03, 2011 at 09:41:29AM -0400, Konrad Rzeszutek Wilk wrote:
>> On Wed, Aug 03, 2011 at 01:18:24PM +0200, Sander Eikelenboom wrote:
>> > Hi Jeremy/Konrad,
>> >
>> > I'm still trying to get the current linus tree (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) to boot as a dom0 kernel under a xen 4.1.1 hypervisor.
>> > But still can't boot (after compiling with tracers disabled).
>>
>> Yeah, there is a bug introduced by Andy. Here is a patchset that fixes it:
>>
>> http://marc.info/?i=cover.1311736366.git.luto@mit.edu

> Oh, and a new version is http://marc.info/?i=cover.1312378163.git.luto@mit.edu
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel



--
Best regards,
Sander mailto:linux@eikelenboom.it


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0 [ In reply to ]
On Wed, Aug 03, 2011 at 05:05:24PM +0200, Sander Eikelenboom wrote:
> Hi Konrad,
>
> Thx, after applying those patches it boots as dom0 and xen-pciback seems to work as well from my first tests.
> The compile problems reported in my earlier mail are still present (related to tracing and i think jeremy's patches).
>
> Something that catched my eye when doing a make menuconfig:
> <*> Xen virtual block device support
> <*> Block-device backend driver
>
> I think the backend description should also start with "Xen" as all xen specific drivers do ?

Yup. let me write a patch for that.
>
> --
> Sander
>
>
> Wednesday, August 3, 2011, 3:51:52 PM, you wrote:
>
> > On Wed, Aug 03, 2011 at 09:41:29AM -0400, Konrad Rzeszutek Wilk wrote:
> >> On Wed, Aug 03, 2011 at 01:18:24PM +0200, Sander Eikelenboom wrote:
> >> > Hi Jeremy/Konrad,
> >> >
> >> > I'm still trying to get the current linus tree (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) to boot as a dom0 kernel under a xen 4.1.1 hypervisor.
> >> > But still can't boot (after compiling with tracers disabled).
> >>
> >> Yeah, there is a bug introduced by Andy. Here is a patchset that fixes it:
> >>
> >> http://marc.info/?i=cover.1311736366.git.luto@mit.edu
>
> > Oh, and a new version is http://marc.info/?i=cover.1312378163.git.luto@mit.edu
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
>
>
>
> --
> Best regards,
> Sander mailto:linux@eikelenboom.it

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0 [ In reply to ]
On Wed, Aug 03, 2011 at 05:05:24PM +0200, Sander Eikelenboom wrote:
> Hi Konrad,
>
> Thx, after applying those patches it boots as dom0 and xen-pciback seems to work as well from my first tests.

Could you reply to that email thread with 'Tested-by: ' if it is not too much trouble?

> The compile problems reported in my earlier mail are still present (related to tracing and i think jeremy's patches).
>
> Something that catched my eye when doing a make menuconfig:
> <*> Xen virtual block device support
> <*> Block-device backend driver
>
> I think the backend description should also start with "Xen" as all xen specific drivers do ?

I've gotten this patch queued up (if you think of a better name or if you think
the description could use some re-wording - please do provide some ideas):

commit 4beb84ffeacbf8df21b41ca8c05d099e19c579a3
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Wed Aug 3 11:12:17 2011 -0400

xen/blkback: Make description more obvious.

With the frontend having Xen but the backend not, it just looks odd:

<*> Xen virtual block device support
<*> Block-device backend driver

Fix it to have the 'Xen' in front of it.

Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index 717d6e4..a89ebf1 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -471,7 +471,7 @@ config XEN_BLKDEV_FRONTEND
in another domain which drives the actual block device.

config XEN_BLKDEV_BACKEND
- tristate "Block-device backend driver"
+ tristate "Xen block-device backend driver"
depends on XEN_BACKEND
help
The block-device backend driver allows the kernel to export its

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Re: Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0 [ In reply to ]
Wednesday, August 3, 2011, 5:53:58 PM, you wrote:

> On Wed, Aug 03, 2011 at 05:05:24PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad,
>>
>> Thx, after applying those patches it boots as dom0 and xen-pciback seems to work as well from my first tests.

> Could you reply to that email thread with 'Tested-by: ' if it is not too much trouble?

I will :-)

>> The compile problems reported in my earlier mail are still present (related to tracing and i think jeremy's patches).
>>
>> Something that catched my eye when doing a make menuconfig:
>> <*> Xen virtual block device support
>> <*> Block-device backend driver
>>
>> I think the backend description should also start with "Xen" as all xen specific drivers do ?

> I've gotten this patch queued up (if you think of a better name or if you think
> the description could use some re-wording - please do provide some ideas):

Can't think of a better one :-)

> commit 4beb84ffeacbf8df21b41ca8c05d099e19c579a3
> Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Date: Wed Aug 3 11:12:17 2011 -0400

> xen/blkback: Make description more obvious.
>
> With the frontend having Xen but the backend not, it just looks odd:
>
> <*> Xen virtual block device support
> <*> Block-device backend driver
>
> Fix it to have the 'Xen' in front of it.
>
> Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 717d6e4..a89ebf1 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -471,7 +471,7 @@ config XEN_BLKDEV_FRONTEND
> in another domain which drives the actual block device.
>
> config XEN_BLKDEV_BACKEND
> - tristate "Block-device backend driver"
> + tristate "Xen block-device backend driver"
> depends on XEN_BACKEND
> help
> The block-device backend driver allows the kernel to export its



--
Best regards,
Sander mailto:linux@eikelenboom.it


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