thr3ads.net - Xen users - [Xen-devel] xen 4 via nano u2300 troubles [May 2010]

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

Hans de Bruin

2010-May-20 19:54 UTC

[Xen-devel] xen 4 via nano u2300 troubles

I have some trouble booting xen 4 x86_64 on my jetway nf76 board. It has 
a via nano u2300 cpu and via vx8800 chipset. Xen stops with an error in 
hvm. As far as i know hvm in the nano 2000 is buggy and should be 
disabled by the bios. Never the less vme shows in cpuinfo:

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : CentaurHauls
cpu family      : 6
model           : 15
model name      : VIA Nano processor U2300@1000MHz
stepping        : 2
cpu MHz         : 533.000
cache size      : 1024 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat clflush acpi mmx fxsr sse sse2 ss tm pbe syscall nx 
fxsr_opt rdtscp lm constant_tsc up rep_good pni monitor est tm2 ssse3 
cx16 xtpr rng rng_en ace ace_en ace2 phe phe_en lahf_lm
bogomips        : 1994.83
clflush size    : 64
cache_alignment : 128
address sizes   : 36 bits physical, 48 bits virtual
power management:

Since i am not interested in hvm i changed CONFIG_HVM := y in 
config/x86_64.mk to n, but that did not make the error disapear.

The error:

  __  __            _  _    ___   _             _
  \ \/ /___ _ __   | || |  / _ \ / |   _ __ ___/ |   _ __  _ __ ___
   \  // _ \ ''_ \  | || |_| | | || |__| ''__/ __| |__|
''_ \| ''__/ _ \
   /  \  __/ | | | |__   _| |_| || |__| | | (__| |__| |_) | | |  __/
  /_/\_\___|_| |_|    |_|(_)___(_)_|  |_|  \___|_|  | .__/|_|  \___|
                                                    |_|
(XEN) Xen version 4.0.1-rc1-pre (root@system) (gcc version 4.4.3 (GCC) ) 
Tue May 18 21:29:56 CEST 2010
(XEN) Latest ChangeSet: Thu May 13 12:22:15 2010 +0100 21148:61cc8ab4d629
(XEN) Command line: com1=38400,8n1,0x3f8,4 console=com1
(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 3 MBR signatures
(XEN)  Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009f800 (usable)
(XEN)  000000000009f800 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000077de0000 (usable)
(XEN)  0000000077de0000 - 0000000077de3000 (ACPI NVS)
(XEN)  0000000077de3000 - 0000000077df0000 (ACPI data)
(XEN)  0000000077df0000 - 0000000077f00000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffff0000 - 0000000100000000 (reserved)
(XEN) System RAM: 1917MB (1963516kB)
(XEN) ACPI: RSDP 000F80F0, 0014 (r0 VX800 )
(XEN) ACPI: RSDT 77DE3000, 0038 (r1 VX800  AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: FACP 77DE3080, 0074 (r1 VX800  AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: DSDT 77DE3100, 5FE4 (r1 VX800  AWRDACPI     1000 MSFT  3000000)
(XEN) ACPI: FACS 77DE0000, 0040
(XEN) ACPI: HPET 77DE9180, 0038 (r1 VX800  AWRDACPI 42302E31 AWRD       98)
(XEN) ACPI: _WDT 77DE91C0, 0047 (r1 VX800  AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: MCFG 77DE9240, 003C (r1 VX800  AWRDACPI 42302E31 AWRD        0)
(XEN) ACPI: APIC 77DE9100, 0066 (r1 VX800  AWRDACPI 42302E31 AWRD        0)
(XEN) Domain heap initialised
(XEN) CPU: Vendor unknown, using generic init.
(XEN) CPU: Your system may be unstable.
(XEN) Processor #0 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 3, version 3, address 0xfecc0000, GSI 24-47
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 997.550 MHz processor.
(XEN) Initing memory sharing.
(XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:34
(XEN) ----[ Xen-4.0.1-rc1-pre  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82c480137644>] iommu_setup+0xd4/0x110
(XEN) RFLAGS: 0000000000010282   CONTEXT: hypervisor
(XEN) rax: 00000000000000ff   rbx: 00000000ffffffed   rcx: 0000000000000000
(XEN) rdx: 00000000000006b0   rsi: ffff82c480399ba0   rdi: ffff830076440ec0
(XEN) rbp: ffff83000007bfc0   rsp: ffff82c480367e28   r8:  0000000000000008
(XEN) r9:  ffff830076440e50   r10: 0000000000000008   r11: 0000000000000000
(XEN) r12: ffff83000007bf70   r13: 0000000000000080   r14: ffff83000007bf70
(XEN) r15: ffff82c480257030   cr0: 000000008005003b   cr4: 00000000000006b0
(XEN) cr3: 0000000077b6c000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
(XEN) Xen stack trace from rsp=ffff82c480367e28:
(XEN)    ffff82c480367f28 ffff82c480246818 0000000000000000 0000000000000000
(XEN)    0000000000000000 00007d0000000000 0000000000000000 ffff83000007bf74
(XEN)    ffffffc48036c000 000000000000000f 000000000007bf00 0000000000432440
(XEN)    ffff830077b6cff8 0000000000000000 0000000000f8b000 0000100000000000
(XEN)    ffff830077b6dff8 0000000000373000 0000000000000000 0000000000000000
(XEN)    0000000800000000 000000010000006e 0000000000000003 00000000000002f8
(XEN)    0000000000000000 0000000000000000 000000000007fe9c 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 ffff82c4801000b5
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 ffff8300778f2000
(XEN) Xen call trace:
(XEN)    [<ffff82c480137644>] iommu_setup+0xd4/0x110
(XEN)    [<ffff82c480246818>] __start_xen+0x2f28/0x3340
(XEN)    [<ffff82c4801000b5>] __high_start+0xa1/0xa3
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:34
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:19
(XEN) ----[ Xen-4.0.1-rc1-pre  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82c4801370a2>] iommu_read_apic_from_ire+0x22/0x40
(XEN) RFLAGS: 0000000000010082   CONTEXT: hypervisor
(XEN) rax: ffff82c4802285e0   rbx: ffff82c480152090   rcx: 0000000000000000
(XEN) rdx: 00000000000000ff   rsi: 0000000000000010   rdi: 0000000000000000
(XEN) rbp: 0000000000000000   rsp: ffff82c480367ae8   r8:  0000000000000002
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 3333333333333333
(XEN) r12: 0000000000000011   r13: 0000000000000010   r14: ffff82c480152020
(XEN) r15: 0000000000000046   cr0: 0000000080050033   cr4: 00000000000006b0
(XEN) cr3: 0000000077b6c000   cr2: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
(XEN) Xen stack trace from rsp=ffff82c480367ae8:
(XEN)    0000000000000046 ffff82c48015261e ffff82c48021617f ffff82c48013764e
(XEN)    0000000000000022 0000000000000000 0000000000000000 ffff82c48022ad20
(XEN)    0000000000000022 ffff82c48039eb58 ffff82c480100000 ffff82c4801526eb
(XEN)    000000000000000a 0000000000000000 ffff82c48013764e ffff82c48015317b
(XEN)    0000000000000022 000000000000000a ffff82c4801472f5 000000000000000a
(XEN)    0000000000000000 ffff82c48016b7e2 0000000000000286 ffff82c48016b370
(XEN)    ffff82c48011d247 000013880000e008 0000000000000286 0000000000000286
(XEN)    0000000000000000 ffff82c480133301 0000003000000018 ffff82c480367cc8
(XEN)    ffff82c480367bf8 ffff82c48037fda1 0000000000000000 ffff82c480212068
(XEN)    0000000000000022 0000000000000000 0000000000004000 0000000000003fff
(XEN)    ffff82c48011d247 000000000000e008 0000000000000292 ffff82c480367c50
(XEN)    0000000000000000 ffff82c48011e12a 00000000000000a3 00000000000000a1
(XEN)    ffff82c4801000b5 ffff82c480367f20 ffff82c480100000 ffff82c480172a5d
(XEN)    ffff82c480367d78 ffff82c480212068 ffff82c480367d78 ffff82c48013764e
(XEN)    ffff82c480212068 ffff82c480212068 ffff82c480367d78 ffff82c480173f55
(XEN)    0000000000000000 0000000000000000 0000000000000096 ffff82c480367cf8
(XEN)    0000000000000096 ffff82c480157f75 ffff82000daa1fbc ffff82c400000000
(XEN)    ffff82008ac20b0f ffff82c480367d38 0000000000000000 ffff82c480367f28
(XEN)    ffff830077bc00b4 0000000000000000 000000000000001a ffff8300778f2000
(XEN)    ffff83000007bfc0 ffff83000007bf70 0000000000000080 ffff83000007bf70
(XEN) Xen call trace:
(XEN)    [<ffff82c4801370a2>] iommu_read_apic_from_ire+0x22/0x40
(XEN)    [<ffff82c48015261e>] __clear_IO_APIC_pin+0x6e/0x100
(XEN)    [<ffff82c48013764e>] iommu_setup+0xde/0x110
(XEN)    [<ffff82c480100000>] _stext+0x0/0x14
(XEN)    [<ffff82c4801526eb>] clear_IO_APIC+0x3b/0x70
(XEN)    [<ffff82c48013764e>] iommu_setup+0xde/0x110
(XEN)    [<ffff82c48015317b>] disable_IO_APIC+0xb/0x1a0
(XEN)    [<ffff82c4801472f5>] disable_local_APIC+0x5/0x60
(XEN)    [<ffff82c48016b7e2>] smp_send_stop+0x52/0x60
(XEN)    [<ffff82c48016b370>] machine_restart+0x60/0x140
(XEN)    [<ffff82c48011d247>] _spin_unlock_irqrestore+0x7/0x10
(XEN)    [<ffff82c480133301>] panic+0x151/0x190
(XEN)    [<ffff82c48011d247>] _spin_unlock_irqrestore+0x7/0x10
(XEN)    [<ffff82c48011e12a>] __print_symbol+0x8a/0xc0
(XEN)    [<ffff82c4801000b5>] __high_start+0xa1/0xa3
(XEN)    [<ffff82c480100000>] _stext+0x0/0x14
(XEN)    [<ffff82c480172a5d>] show_stack+0x14d/0x1d0
(XEN)    [<ffff82c48013764e>] iommu_setup+0xde/0x110
(XEN)    [<ffff82c480173f55>] do_invalid_op+0x645/0x720
(XEN)    [<ffff82c480157f75>] do_IRQ+0x5b5/0x6b0
(XEN)    [<ffff82c4801e8615>] handle_exception_saved+0x2d/0x6b
(XEN)    [<ffff82c480137644>] iommu_setup+0xd4/0x110
(XEN)    [<ffff82c480246818>] __start_xen+0x2f28/0x3340
(XEN)    [<ffff82c4801000b5>] __high_start+0xa1/0xa3
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:19
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

( by the way how many hours take five seconds? I had to reboot manually )

-- 
Hans

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

Jeremy Fitzhardinge

2010-May-20 20:03 UTC

head link

Re: [Xen-devel] xen 4 via nano u2300 troubles

On 05/20/2010 12:54 PM, Hans de Bruin wrote:> I have some trouble booting xen 4 x86_64 on my jetway nf76 board. It
> has a via nano u2300 cpu and via vx8800 chipset. Xen stops with an
> error in hvm. As far as i know hvm in the nano 2000 is buggy and
> should be disabled by the bios. Never the less vme shows in cpuinfo:
"vme" is virtual 8086 extensions; hvm is "vt".   Xen
isn''t showing any
messages showing it has detected VT or is trying to use it.
>
> $ cat /proc/cpuinfo
> processor       : 0
> vendor_id       : CentaurHauls
> cpu family      : 6
> model           : 15
> model name      : VIA Nano processor U2300@1000MHz
> stepping        : 2
> cpu MHz         : 533.000
> cache size      : 1024 KB
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat clflush acpi mmx fxsr sse sse2 ss tm pbe syscall nx
> fxsr_opt rdtscp lm constant_tsc up rep_good pni monitor est tm2 ssse3
> cx16 xtpr rng rng_en ace ace_en ace2 phe phe_en lahf_lm
> bogomips        : 1994.83
> clflush size    : 64
> cache_alignment : 128
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> Since i am not interested in hvm i changed CONFIG_HVM := y in
> config/x86_64.mk to n, but that did not make the error disapear.
I think you''re treading into lightly tested or completely untested
territory if you disable that.
> (XEN) Initing memory sharing.
> (XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:34
> (XEN) ----[ Xen-4.0.1-rc1-pre  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff82c480137644>] iommu_setup+0xd4/0x110
Does booting with iommu=0 help?

    J
> (XEN) RFLAGS: 0000000000010282   CONTEXT: hypervisor
> (XEN) rax: 00000000000000ff   rbx: 00000000ffffffed   rcx:
> 0000000000000000
> (XEN) rdx: 00000000000006b0   rsi: ffff82c480399ba0   rdi:
> ffff830076440ec0
> (XEN) rbp: ffff83000007bfc0   rsp: ffff82c480367e28   r8: 
> 0000000000000008
> (XEN) r9:  ffff830076440e50   r10: 0000000000000008   r11:
> 0000000000000000
> (XEN) r12: ffff83000007bf70   r13: 0000000000000080   r14:
> ffff83000007bf70
> (XEN) r15: ffff82c480257030   cr0: 000000008005003b   cr4:
> 00000000000006b0
> (XEN) cr3: 0000000077b6c000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff82c480367e28:
> (XEN)    ffff82c480367f28 ffff82c480246818 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 00007d0000000000 0000000000000000
> ffff83000007bf74
> (XEN)    ffffffc48036c000 000000000000000f 000000000007bf00
> 0000000000432440
> (XEN)    ffff830077b6cff8 0000000000000000 0000000000f8b000
> 0000100000000000
> (XEN)    ffff830077b6dff8 0000000000373000 0000000000000000
> 0000000000000000
> (XEN)    0000000800000000 000000010000006e 0000000000000003
> 00000000000002f8
> (XEN)    0000000000000000 0000000000000000 000000000007fe9c
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> ffff82c4801000b5
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000
> 0000000000000000
> (XEN)    0000000000000000 0000000000000000 ffff8300778f2000
> (XEN) Xen call trace:
> (XEN)    [<ffff82c480137644>] iommu_setup+0xd4/0x110
> (XEN)    [<ffff82c480246818>] __start_xen+0x2f28/0x3340
> (XEN)    [<ffff82c4801000b5>] __high_start+0xa1/0xa3
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:34
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
> (XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:19
> (XEN) ----[ Xen-4.0.1-rc1-pre  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff82c4801370a2>]
> iommu_read_apic_from_ire+0x22/0x40
> (XEN) RFLAGS: 0000000000010082   CONTEXT: hypervisor
> (XEN) rax: ffff82c4802285e0   rbx: ffff82c480152090   rcx:
> 0000000000000000
> (XEN) rdx: 00000000000000ff   rsi: 0000000000000010   rdi:
> 0000000000000000
> (XEN) rbp: 0000000000000000   rsp: ffff82c480367ae8   r8: 
> 0000000000000002
> (XEN) r9:  0000000000000000   r10: 0000000000000000   r11:
> 3333333333333333
> (XEN) r12: 0000000000000011   r13: 0000000000000010   r14:
> ffff82c480152020
> (XEN) r15: 0000000000000046   cr0: 0000000080050033   cr4:
> 00000000000006b0
> (XEN) cr3: 0000000077b6c000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff82c480367ae8:
> (XEN)    0000000000000046 ffff82c48015261e ffff82c48021617f
> ffff82c48013764e
> (XEN)    0000000000000022 0000000000000000 0000000000000000
> ffff82c48022ad20
> (XEN)    0000000000000022 ffff82c48039eb58 ffff82c480100000
> ffff82c4801526eb
> (XEN)    000000000000000a 0000000000000000 ffff82c48013764e
> ffff82c48015317b
> (XEN)    0000000000000022 000000000000000a ffff82c4801472f5
> 000000000000000a
> (XEN)    0000000000000000 ffff82c48016b7e2 0000000000000286
> ffff82c48016b370
> (XEN)    ffff82c48011d247 000013880000e008 0000000000000286
> 0000000000000286
> (XEN)    0000000000000000 ffff82c480133301 0000003000000018
> ffff82c480367cc8
> (XEN)    ffff82c480367bf8 ffff82c48037fda1 0000000000000000
> ffff82c480212068
> (XEN)    0000000000000022 0000000000000000 0000000000004000
> 0000000000003fff
> (XEN)    ffff82c48011d247 000000000000e008 0000000000000292
> ffff82c480367c50
> (XEN)    0000000000000000 ffff82c48011e12a 00000000000000a3
> 00000000000000a1
> (XEN)    ffff82c4801000b5 ffff82c480367f20 ffff82c480100000
> ffff82c480172a5d
> (XEN)    ffff82c480367d78 ffff82c480212068 ffff82c480367d78
> ffff82c48013764e
> (XEN)    ffff82c480212068 ffff82c480212068 ffff82c480367d78
> ffff82c480173f55
> (XEN)    0000000000000000 0000000000000000 0000000000000096
> ffff82c480367cf8
> (XEN)    0000000000000096 ffff82c480157f75 ffff82000daa1fbc
> ffff82c400000000
> (XEN)    ffff82008ac20b0f ffff82c480367d38 0000000000000000
> ffff82c480367f28
> (XEN)    ffff830077bc00b4 0000000000000000 000000000000001a
> ffff8300778f2000
> (XEN)    ffff83000007bfc0 ffff83000007bf70 0000000000000080
> ffff83000007bf70
> (XEN) Xen call trace:
> (XEN)    [<ffff82c4801370a2>] iommu_read_apic_from_ire+0x22/0x40
> (XEN)    [<ffff82c48015261e>] __clear_IO_APIC_pin+0x6e/0x100
> (XEN)    [<ffff82c48013764e>] iommu_setup+0xde/0x110
> (XEN)    [<ffff82c480100000>] _stext+0x0/0x14
> (XEN)    [<ffff82c4801526eb>] clear_IO_APIC+0x3b/0x70
> (XEN)    [<ffff82c48013764e>] iommu_setup+0xde/0x110
> (XEN)    [<ffff82c48015317b>] disable_IO_APIC+0xb/0x1a0
> (XEN)    [<ffff82c4801472f5>] disable_local_APIC+0x5/0x60
> (XEN)    [<ffff82c48016b7e2>] smp_send_stop+0x52/0x60
> (XEN)    [<ffff82c48016b370>] machine_restart+0x60/0x140
> (XEN)    [<ffff82c48011d247>] _spin_unlock_irqrestore+0x7/0x10
> (XEN)    [<ffff82c480133301>] panic+0x151/0x190
> (XEN)    [<ffff82c48011d247>] _spin_unlock_irqrestore+0x7/0x10
> (XEN)    [<ffff82c48011e12a>] __print_symbol+0x8a/0xc0
> (XEN)    [<ffff82c4801000b5>] __high_start+0xa1/0xa3
> (XEN)    [<ffff82c480100000>] _stext+0x0/0x14
> (XEN)    [<ffff82c480172a5d>] show_stack+0x14d/0x1d0
> (XEN)    [<ffff82c48013764e>] iommu_setup+0xde/0x110
> (XEN)    [<ffff82c480173f55>] do_invalid_op+0x645/0x720
> (XEN)    [<ffff82c480157f75>] do_IRQ+0x5b5/0x6b0
> (XEN)    [<ffff82c4801e8615>] handle_exception_saved+0x2d/0x6b
> (XEN)    [<ffff82c480137644>] iommu_setup+0xd4/0x110
> (XEN)    [<ffff82c480246818>] __start_xen+0x2f28/0x3340
> (XEN)    [<ffff82c4801000b5>] __high_start+0xa1/0xa3
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:19
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
>
> ( by the way how many hours take five seconds? I had to reboot manually )
>

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

Keir Fraser

2010-May-20 21:29 UTC

head link

Re: [Xen-devel] xen 4 via nano u2300 troubles

On 20/05/2010 20:54, "Hans de Bruin" <jmdebruin@xmsnet.nl>
wrote:
> I have some trouble booting xen 4 x86_64 on my jetway nf76 board. It has
> a via nano u2300 cpu and via vx8800 chipset. Xen stops with an error in
> hvm. As far as i know hvm in the nano 2000 is buggy and should be
> disabled by the bios. Never the less vme shows in cpuinfo:
VIA systems are not tested or supported by us. However, the attached patch
may get you further.

 -- Keir



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

Hans de Bruin

2010-May-21 20:54 UTC

head link

Re: [Xen-devel] xen 4 via nano u2300 troubles

On 05/20/2010 10:03 PM, Jeremy Fitzhardinge wrote:> On 05/20/2010 12:54 PM, Hans de Bruin wrote:
>> I have some trouble booting xen 4 x86_64 on my jetway nf76 board. It
>> has a via nano u2300 cpu and via vx8800 chipset.

...
>>
>> Since i am not interested in hvm i changed CONFIG_HVM := y in
>> config/x86_64.mk to n, but that did not make the error disapear.
>
> I think you''re treading into lightly tested or completely untested
> territory if you disable that.
I have undone my CONFIG_HVM change.
>> (XEN) Initing memory sharing.
>> (XEN) Xen BUG at /usr/src/xen-4.0-testing.hg/xen/include/asm/hvm/io:34
>> (XEN) ----[ Xen-4.0.1-rc1-pre  x86_64  debug=n  Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) RIP:    e008:[<ffff82c480137644>] iommu_setup+0xd4/0x110
>
> Does booting with iommu=0 help?
yep. The kernel has some difficulty in finding the rootfs, but that will 
be fixed by some recompiling.

-- 
Hans

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

Hans de Bruin

2010-May-21 20:58 UTC

head link

Re: [Xen-devel] xen 4 via nano u2300 troubles

On 05/20/2010 11:29 PM, Keir Fraser wrote:> On 20/05/2010 20:54, "Hans de Bruin"<jmdebruin@xmsnet.nl> 
wrote:
>
>> I have some trouble booting xen 4 x86_64 on my jetway nf76 board. It
has
>> a via nano u2300 cpu and via vx8800 chipset. Xen stops with an error in
>> hvm. As far as i know hvm in the nano 2000 is buggy and should be
>> disabled by the bios. Never the less vme shows in cpuinfo:
>
> VIA systems are not tested or supported by us. However, the attached patch
> may get you further.
>
Has this exact the same effect as Jeremy''s iommu=0 option?

-- 
Hans


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

Hans de Bruin

2010-May-22 18:54 UTC

head link

[Xen-users] where is my root?

The pvops kernel has some trouble finding my root:

grub''2''.cfg:

menuentry "GNU/Linux, with Linux 2.6.31.13" --class gnu-linux --class 
gnu --class os {
         set gfxpayload=keep
         insmod raid
         insmod mdraid
         insmod ext2
         set root=''(md0)''
         search --no-floppy --fs-uuid --set 
5d272f28-2087-490b-8de2-c7d12beaff69
         echo    Loading Linux 2.6.31.13 ...
         linux   /vmlinuz-2.6.31.13 root=/dev/md2 ro console=tty0 
console=ttyS0,38400,8n1
}
...
menuentry "Xen 4.0.0. linux-2.6.31.13 pvops" {
         insmod raid
         insmod mdraid
         insmod ext2
         set root=''(md0)''
         search --no-floppy --fs-uuid --set 
5d272f28-2087-490b-8de2-c7d12beaff69
         echo    Loading Linux 2.6.33 ...
         multiboot /xen-4.0.1-rc1-pre.gz dom0_mem=512M  loglvl=all 
guest_loglvl=all com1=38400,8n1,0x3f8,4 console=com1 iommu=0
         module /vmlinuz-2.6.31.13 root=/dev/md2 ro console=hvc0 
earlyprintk=xen nomodeset
}


pvops kernel by itself:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.31.13 (hans@bootes) (gcc version 4.4.3 
(GCC) ) #3 SMP Sat May 22 13:46:23 CEST 2010
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.31.13 root=/dev/md2 
ro console=tty0 console=ttyS0,38400,8n1
....
[    8.177481] VFS: Mounted root (ext4 filesystem) readonly on device 9:2.
[    8.197548] Freeing unused kernel memory: 508k freed
[    8.212901] Write protecting the kernel read-only data: 8016k
[    8.283642] Warning: unable to open an initial console.
[   11.637889] scsi 2:0:0:0: Direct-Access              USB DISK 2.0 
  PMAP PQ: 0 ANSI: 0 CCS
[   11.664631] sd 2:0:0:0: Attached scsi generic sg2 type 0
[   11.681100] sd 2:0:0:0: [sdc] 15882240 512-byte logical blocks: (8.13 
GB/7.57 GiB)
[   11.705456] sd 2:0:0:0: [sdc] Write Protect is off
[   11.719981] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[   11.741948] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[   11.760338]  sdc: sdc1
[   11.770449] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[   11.788846] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[   13.131600] md: stopping all md devices.
[   13.143484] md: md1 switched to read-only mode.
[   13.157185] md: md2 switched to read-only mode.
[   13.170878] md: md0 switched to read-only mode.
[   14.675056] sd 0:0:1:0: [sdb] Synchronizing SCSI cache
[   14.690799] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   14.755088] e1000 0000:04:07.0: PCI INT A disabled
[   14.769676] e1000 0000:04:06.0: PCI INT A disabled
[   14.784256] e1000 0000:04:04.0: PCI INT A disabled
[   14.799257] Restarting system.
[   14.808522] machine restart


So there is a mounted rootfs on /dev/md2 but apparently no console.

pvops on top of xen:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.31.13 (hans@bootes) (gcc version 4.4.3 
(GCC) ) #3 SMP Sat May 22 13:46:23 CEST 2010
[    0.000000] Command line: ro console=hvc0 earlyprintk=xen nomodeset

here root=/dev/md2 has disappeared!

...
[    3.289417] md: ... autorun DONE.
[    3.289830] VFS: Cannot open root device "<NULL>" or
unknown-block(0,0)
[    3.289856] Please append a correct "root=" boot option; here are
the
available partitions:
[    3.289903] 0800       488386584 sda driver: sd
[    3.289935]   0801           72261 sda1
[    3.289962]   0802          530145 sda2
[    3.289989]   0803          530145 sda3
[    3.290021]   0804       487251450 sda4
[    3.290048] 0810       488386584 sdb driver: sd
[    3.290077]   0811           72261 sdb1
[    3.290084]   0812          530145 sdb2
[    3.290084]   0813          530145 sdb3
[    3.290084]   0814       487251450 sdb4
[    3.290084] 0900           72192 md0 (driver?)
[    3.290084] 0902          530048 md2 (driver?)
[    3.290084] 0901          530048 md1 (driver?)
[    3.290084] Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown-block(0,0)
[    3.290084] Pid: 1, comm: swapper Not tainted 2.6.31.13 #3
[    3.290084] Call Trace:
[    3.290084]  [<ffffffff81544197>] panic+0x75/0x130
[    3.290084]  [<ffffffff818daa67>] mount_block_root+0x257/0x26e
[    3.290084]  [<ffffffff818daad4>] mount_root+0x56/0x5a
[    3.290084]  [<ffffffff818dac48>] prepare_namespace+0x170/0x19d
[    3.290084]  [<ffffffff818d9f40>] kernel_init+0x1b5/0x1c5
[    3.290084]  [<ffffffff81014daa>] child_rip+0xa/0x20
[    3.290084]  [<ffffffff81013f67>] ? int_ret_from_sys_call+0x7/0x1b
[    3.290084]  [<ffffffff8101471d>] ? retint_restore_args+0x5/0x6
[    3.290084]  [<ffffffff81014da0>] ? child_rip+0x0/0x20

which ends in a disaster.

I have got to questions. In case of the pvops only boot is the an error 
in the grub.cfg file do I need to change the console?  In case of the 
xen-pvops boot where has the root=/dev/md2 gone?



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

Richie

2010-May-22 19:10 UTC

head link

Re: [Xen-users] where is my root?

Hans de Bruin wrote:> The pvops kernel has some trouble finding my root:
>
> grub''2''.cfg:
>
> menuentry "GNU/Linux, with Linux 2.6.31.13" --class gnu-linux
--class
> gnu --class os {
>         set gfxpayload=keep
>         insmod raid
>         insmod mdraid
>         insmod ext2
>         set root=''(md0)''
>         search --no-floppy --fs-uuid --set 
> 5d272f28-2087-490b-8de2-c7d12beaff69
>         echo    Loading Linux 2.6.31.13 ...
>         linux   /vmlinuz-2.6.31.13 root=/dev/md2 ro console=tty0 
> console=ttyS0,38400,8n1
> }
> ...
> menuentry "Xen 4.0.0. linux-2.6.31.13 pvops" {
>         insmod raid
>         insmod mdraid
>         insmod ext2
>         set root=''(md0)''
>         search --no-floppy --fs-uuid --set 
> 5d272f28-2087-490b-8de2-c7d12beaff69
>         echo    Loading Linux 2.6.33 ...
>         multiboot /xen-4.0.1-rc1-pre.gz dom0_mem=512M  loglvl=all 
> guest_loglvl=all com1=38400,8n1,0x3f8,4 console=com1 iommu=0
>         module /vmlinuz-2.6.31.13 root=/dev/md2 ro console=hvc0 
> earlyprintk=xen nomodeset
> }
>
>
> pvops kernel by itself:
>
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Linux version 2.6.31.13 (hans@bootes) (gcc version 
> 4.4.3 (GCC) ) #3 SMP Sat May 22 13:46:23 CEST 2010
> [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.31.13 
> root=/dev/md2 ro console=tty0 console=ttyS0,38400,8n1
> ....
> [    8.177481] VFS: Mounted root (ext4 filesystem) readonly on device 
> 9:2.
> [    8.197548] Freeing unused kernel memory: 508k freed
> [    8.212901] Write protecting the kernel read-only data: 8016k
> [    8.283642] Warning: unable to open an initial console.
> [   11.637889] scsi 2:0:0:0: Direct-Access              USB DISK 2.0 
>  PMAP PQ: 0 ANSI: 0 CCS
> [   11.664631] sd 2:0:0:0: Attached scsi generic sg2 type 0
> [   11.681100] sd 2:0:0:0: [sdc] 15882240 512-byte logical blocks: 
> (8.13 GB/7.57 GiB)
> [   11.705456] sd 2:0:0:0: [sdc] Write Protect is off
> [   11.719981] sd 2:0:0:0: [sdc] Assuming drive cache: write through
> [   11.741948] sd 2:0:0:0: [sdc] Assuming drive cache: write through
> [   11.760338]  sdc: sdc1
> [   11.770449] sd 2:0:0:0: [sdc] Assuming drive cache: write through
> [   11.788846] sd 2:0:0:0: [sdc] Attached SCSI removable disk
> [   13.131600] md: stopping all md devices.
> [   13.143484] md: md1 switched to read-only mode.
> [   13.157185] md: md2 switched to read-only mode.
> [   13.170878] md: md0 switched to read-only mode.
> [   14.675056] sd 0:0:1:0: [sdb] Synchronizing SCSI cache
> [   14.690799] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [   14.755088] e1000 0000:04:07.0: PCI INT A disabled
> [   14.769676] e1000 0000:04:06.0: PCI INT A disabled
> [   14.784256] e1000 0000:04:04.0: PCI INT A disabled
> [   14.799257] Restarting system.
> [   14.808522] machine restart
>
>
> So there is a mounted rootfs on /dev/md2 but apparently no console.
>
> pvops on top of xen:
>
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Linux version 2.6.31.13 (hans@bootes) (gcc version 
> 4.4.3 (GCC) ) #3 SMP Sat May 22 13:46:23 CEST 2010
> [    0.000000] Command line: ro console=hvc0 earlyprintk=xen nomodeset
>
> here root=/dev/md2 has disappeared!
>
> ...
> [    3.289417] md: ... autorun DONE.
> [    3.289830] VFS: Cannot open root device "<NULL>" or 
> unknown-block(0,0)
> [    3.289856] Please append a correct "root=" boot option; here
are
> the available partitions:
> [    3.289903] 0800       488386584 sda driver: sd
> [    3.289935]   0801           72261 sda1
> [    3.289962]   0802          530145 sda2
> [    3.289989]   0803          530145 sda3
> [    3.290021]   0804       487251450 sda4
> [    3.290048] 0810       488386584 sdb driver: sd
> [    3.290077]   0811           72261 sdb1
> [    3.290084]   0812          530145 sdb2
> [    3.290084]   0813          530145 sdb3
> [    3.290084]   0814       487251450 sdb4
> [    3.290084] 0900           72192 md0 (driver?)
> [    3.290084] 0902          530048 md2 (driver?)
> [    3.290084] 0901          530048 md1 (driver?)
> [    3.290084] Kernel panic - not syncing: VFS: Unable to mount root 
> fs on unknown-block(0,0)
> [    3.290084] Pid: 1, comm: swapper Not tainted 2.6.31.13 #3
> [    3.290084] Call Trace:
> [    3.290084]  [<ffffffff81544197>] panic+0x75/0x130
> [    3.290084]  [<ffffffff818daa67>] mount_block_root+0x257/0x26e
> [    3.290084]  [<ffffffff818daad4>] mount_root+0x56/0x5a
> [    3.290084]  [<ffffffff818dac48>] prepare_namespace+0x170/0x19d
> [    3.290084]  [<ffffffff818d9f40>] kernel_init+0x1b5/0x1c5
> [    3.290084]  [<ffffffff81014daa>] child_rip+0xa/0x20
> [    3.290084]  [<ffffffff81013f67>] ? int_ret_from_sys_call+0x7/0x1b
> [    3.290084]  [<ffffffff8101471d>] ? retint_restore_args+0x5/0x6
> [    3.290084]  [<ffffffff81014da0>] ? child_rip+0x0/0x20
>
> which ends in a disaster.
>
> I have got to questions. In case of the pvops only boot is the an 
> error in the grub.cfg file do I need to change the console?  In case 
> of the xen-pvops boot where has the root=/dev/md2 gone?
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-usersWhere is your dummy=dummy parameter to work around the grub2 first 
parameter bug? :)

try:
        multiboot /xen-4.0.1-rc1-pre.gz dummy=dummy dom0_mem=512M  
loglvl=all guest_loglvl=all com1=38400,8n1,0x3f8,4 console=com1 iommu=0
        module /vmlinuz-2.6.31.13 dummy=dummy root=/dev/md2 ro 
console=hvc0 earlyprintk=xen nomodeset

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

Hans de Bruin

2010-May-23 14:58 UTC

head link

Re: [Xen-users] where is my root?

On 05/22/2010 09:10 PM, Richie wrote:> Hans de Bruin wrote:
>> The pvops kernel has some trouble finding my root:...
>>
>> I have got to questions. In case of the pvops only boot is the an
>> error in the grub.cfg file do I need to change the console? In case of
>> the xen-pvops boot where has the root=/dev/md2 gone?
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
> Where is your dummy=dummy parameter to work around the grub2 first
> parameter bug? :)
>
> try:
> multiboot /xen-4.0.1-rc1-pre.gz dummy=dummy dom0_mem=512M loglvl=all
> guest_loglvl=all com1=38400,8n1,0x3f8,4 console=com1 iommu=0
> module /vmlinuz-2.6.31.13 dummy=dummy root=/dev/md2 ro console=hvc0
> earlyprintk=xen nomodeset
The grub2 first parameter bug. Great, I just switched reluctantly from 
lilo to grub to use Xen. Well, my root is back, now i have to find a 
console.

-- 
Hans


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

Xen users - May 2010 - xen 4 via nano u2300 troubles

[Xen-devel] xen 4 via nano u2300 troubles

Re: [Xen-devel] xen 4 via nano u2300 troubles

Re: [Xen-devel] xen 4 via nano u2300 troubles

Re: [Xen-devel] xen 4 via nano u2300 troubles

Re: [Xen-devel] xen 4 via nano u2300 troubles

[Xen-users] where is my root?

Re: [Xen-users] where is my root?

Re: [Xen-users] where is my root?