WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

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

from [Jeremy Fitzhardinge] [Permanent Link][Original]
To: Hans de Bruin <jmdebruin@xxxxxxxxx>
Subject: Re: [Xen-devel] xen 4 via nano u2300 troubles
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 20 May 2010 13:03:19 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 20 May 2010 13:04:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BF59370.9050501@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4BF59370.9050501@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4 
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] xen 4 via nano u2300 troubles, Hans de Bruin
Next by Date:  Re: [Xen-devel] [PATCH] Wait the state Connect of the frontend before connect the backend., Jeremy Fitzhardinge
Previous by Thread:  [Xen-devel] xen 4 via nano u2300 troubles, Hans de Bruin
Next by Thread:  Re: [Xen-devel] xen 4 via nano u2300 troubles, Hans de Bruin
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy