does anyone have Xen running on an AMD system?

Gót András got.andras at deployis.eu
Wed Jan 12 20:34:13 UTC 2011


I've attached Colin's patch. It may work on current also.

Tobiasz Tworek wrote:
> I had tested latest curent version on my AMD Athlon II X4 Xen Server 6.5 
> and i have got panic. My output:
> 
> WARNING: loader(8) metadata is missing!
> GDB: no debug ports present
> KDB: debugger backends: ddb
> KDB: current backend: ddb
> Copyright (c) 1992-2010 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.0-CURRENT #0: Wed Jan 12 20:14:15 CET 2011
>     root at freebsdcurent:/usr/src/sys/i386/compile/XEN i386
> WARNING: WITNESS option enabled, expect reduced performance.
> Xen reported: 3013.708 MHz processor.
> Timecounter "ixen" frequency 1000000000 Hz quality 0
> CPU: AMD Athlon(tm) II X4 640 Processor (3013.71-MHz 686-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x100f53  Family = 10  Model = 5  
> Stepping = 3
>   
> Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT> 
> 
>   Features2=0x802009<SSE3,MON,CX16,POPCNT>
>   AMD 
> Features=0xee500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow!>
>   AMD 
> Features2=0x37ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT> 
> 
>   TSC: P-state invariant
> Data TLB: 48 entries, fully associative
> Instruction TLB: 32 entries, fully associative
> L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
> L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way 
> associative
> L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 8-way 
> associative
> real memory  = 536870912 (512 MB)
> Physical memory chunk(s):
> 0x000000000077d000 - 0x000000001f638fff, 518766592 bytes (126652 pages)
> avail memory = 515821568 (491 MB)
> APIC: Using the MPTable enumerator.
> SMP: Added CPU 0 (BSP)
> ULE: setup cpu 0
> [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0)
> [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1)
> Event-channel device installed.
> nfslock: pseudo-device
> mem:<memory>
> Pentium Pro MTRR support enabled
> io:<I/O>
> null:<null device, zero device>
> random:<entropy source, Software, Yarrow>
> [XEN] xen_rtc_probe: probing Hypervisor RTC clock
> rtc0:<Xen Hypervisor Clock>  on motherboard
> [XEN] xen_rtc_attach: attaching Hypervisor RTC clock
> rtc0: registered as a time-of-day clock (resolution 1000000us, 
> adjustment 0.500000000s)
> Grant table initialized
> xenbus0:<Xen Devices>  on motherboard
> xc0:<Xen Console>  on motherboard
> Device configuration finished.
> procfs registered
> Timecounters tick every 10.000 msec
> kernel trap 9 with interrupts disabled
> 
> 
> Fatal trap 9: general protection fault while in kernel mode
> cpuid = 0; apic id = 00
> instruction pointer= 0x21:0xc032b311
> stack pointer        = 0x29:0xlo0: bpf attached
> c21fec8c
> frame pointer        = 0x29:0xc21fec94
> code segment= base 0x0, limit 0xfffff, type [XEN] hypervisor wallclock 
> nudged; nudging TOD.
> 0x1b
> = DPL 1, pres 1, def32 1, gran 1
> processor eflags= resume, IOPL = 0
> current process= 11 (idle: cpu0)
> [ thread pid 11 tid 100003 ]
> Stopped at      spinlock_exit+0xa1:     hlt
> 
> 
> 
> Regards,
> Tobiasz Tworek
> 
> 
>> On 01/12/11 05:33, Gót András wrote:
>>> kernel trap 9 with interrupts disabled
>>>
>>> Fatal trap 9: general protection fault while in kernel mode
>>> cpuid = 0; apic id = 00
>>> instruction pointer    = 0x21:0xc0321241
>>> stack pointer            = 0x29:0xc21ffc8c
>>> frame pointer            = 0x29:0xc21ffc94
>>> code segment        = base 0x0, limit 0xfffff, type 0x1b
>>>              = DPL 1, pres 1, def32 1, gran 1
>>> processor eflags    = resume, IOPL = 0
>>> current process        = 11 (idle: cpu0)
>>> [thread pid 11 tid 100003 ]
>>> Stopped at      spinlock_exit+0xe1:     hlt
>> Yep, this is what I was looking for.  Can you try the attached patch 
>> (under
>> the same conditions to avoid the pmap_init panic) and let me know if this
>> problem goes away?
>>
>>
>>
>> _______________________________________________
>> freebsd-xen at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
>> To unsubscribe, send any mail to "freebsd-xen-unsubscribe at freebsd.org"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amdc1e_privileged.patch
Type: text/x-patch
Size: 682 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-xen/attachments/20110112/f4938335/amdc1e_privileged.bin


More information about the freebsd-xen mailing list