Re: fpudna: fpcurthread == curthread XXXX times
Hi,
I do have the same issue on 8.4-RELEASE, 9.1-RELEASE, 9.2-RELEASE based on
XENHVM config (amd64).
The 'uname' in the guests looks like this one:
root@my:/ # uname -a
FreeBSD my.vm 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Mon Aug 19 14:08:42 EEST 2013
r...@my.vm:/usr/obj/usr/src/sys/XENHVM amd64
I could also confirm the issue doesn't affect 8.2 8.3, 9.0 versions.
The Hypervisor is CentOS release 5.9 with Xen 3.4.3, and its details are:
# cat /proc/cpuinfo
...
processor : 15
vendor_id : AuthenticAMD
cpu family : 16
model : 9
model name : AMD Opteron(tm) Processor 6128
stepping: 1
cpu MHz : 2000.140
cache size : 512 KB
physical id : 15
siblings: 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu de tsc msr pae mce cx8 apic mtrr mca cmov pat clflush mmx
fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow constant_tsc pni
cx16 popcnt lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse
bogomips: 5002.23
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc [6] [7] [8]
# xm info
host : hv.build
release: 2.6.18-308.20.1.el5.xen
version: #1 SMP Wed Dec 5 13:30:38 GMT 2012
machine: x86_64
nr_cpus: 16
nr_nodes : 1
cores_per_socket : 8
threads_per_core : 1
cpu_mhz: 2000
hw_caps:
178bf3ff:efd3fbff::0310:00802001::000837ff:
virt_caps : hvm
total_memory : 49150
free_memory: 45664
node_to_cpu: node0:0-15
node_to_memory : node0:45664
xen_major : 3
xen_minor : 4
xen_extra : .4
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params: virt_start=0x8000
xen_changeset : unavailable
cc_compiler: gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)
cc_compile_by : root
cc_compile_domain : hv.build
cc_compile_date: Wed Sep 5 18:01:10 EEST 2012
xend_config_format : 4
Could anybody please help/assist me with the issue fixing ?
Thanks
---
Yura
On Jun 2, 2011, at 10:22 PM, Sergi se...@estrafolari.com wrote:
On 01/06/11 23:36, Kostik Belousov wrote:
On Wed, Jun 01, 2011 at 03:00:51PM +0200, Sergi wrote:
On 01/06/11 11:36, Sergi wrote:
On 01/06/11 10:21, Kostik Belousov wrote:
On Wed, Jun 01, 2011 at 09:44:23AM +0200, Sergi wrote:
Hello,
I'm working with full virtual FreeBSD 8.2-RELEASE-p1 domU under debian
squeeze and xen-hypervisor-4.0-amd64.
If I cfg this hvm with cpu 4 :
vcpus= 5
these messages block the server :
fpudna: fpcurthread == curthread times
The machine is pingable but I'm unable to ssh to it.
On single user it works fine, fsck an so on ok, but when switching to
multiuser these fpudna messages start flooding.
I've googled but haven't found anything; something from 2005 about
fpudna :
http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html
and this link, but I don't have the options he mentions enabled on the
kernel :
http://forums.freebsd.org/showthread.php?t=17979
Has anyone stepped on this behaviour before?, is there any workaround?
The machine really seems to detect cpu's available and responds to
keyboard
on VNC, but it's impossible to see whats written down because of the
messages flooding the screen.
You did not specified the architecture of the domu. From the message,
I can
guess that your guest is running amd64 kernel. There are slight
differences
in the handling of the FPU in i386 and amd64 that may matter there.
The message you reported means that the FreeBSD kernel assumes that FPU
is currently loaded with the context of the current thread, but the
CR0.TS bit is set, meaning that FPU context is set for switch.
AFAIR, HVM means that you run bare-metal kernel, right ? Most likely,
it is some issue with Xen itself. I am curious whether the following
will cause any usermode-visible regression for you:
diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c
index 08e5e57..a5ee853 100644
--- a/sys/amd64/amd64/fpu.c
+++ b/sys/amd64/amd64/fpu.c
@@ -394,14 +394,8 @@ fpudna(void)
struct pcb *pcb;
critical_enter();
-if (PCPU_GET(fpcurthread) == curthread) {
-printf(fpudna: fpcurthread == curthread %d times\n,
-++err_count);
-stop_emulating();
-critical_exit();
-return;
-}
-if (PCPU_GET(fpcurthread) != NULL) {
+if (PCPU_GET(fpcurthread) != NULL
+
Re: Xen PV drivers for FreeBSD
Hi, Just let you know: everything starts work for me in 8.2-PRERELEASE (RELENG_8) Thank you for your work. I'm also highly interesting FreeBSD paravirtualized DOMU to be stable. I'll build test XEN i386 today. I'll let you know results if you want. --- Yura On Dec 3, 2010, at 3:23 PM, Justin T. Gibbs wrote: On Dec 3, 2010, at 4:12 AM, Yuriy Kohut yko...@onapp.com wrote: Hi, I would not like to disturb you, but, have you a chance to reproduce the issue ? A FreeBSD stable/8 XENHVM kernel from yesterday functions properly for me in my Xen environment. The problem is not with CDROM device, but with boot process stops. Did you remove the CDROM from the device configuration for your domain? My host systems do not have CDROM devices to pass through, so I have not tested the impact of detecting a CDROM device on the FreeBSD XENHVM device probe process. In short, I understand that you are not directly complaining a about CDROM functionality, but my hunch is that the detection of a CDROM device is exposing a bug in the block front driver which leads to a hang during boot. -- Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
FreeBSD 8.2-PRERELEASE (XEN) kernel panic at mkdir
Hi, I'm just installed the latest FreeBSD i386 Paravirtualized DomU based on the XEN kernel from RELENG_8. Kernel panics while ports installing (using sysinstall). lock order reversal: 1st 0xc0f37ab0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2636 2nd 0xc13d3e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 KDB: stack backtrace: X_db_sym_numargs(c03635ba,c0514c30,c1232870,c14116f0,636bf9e5,...) at X_db_sym_numargs+0x146 kdb_backtrace(c010e7ab,c03664cf,c10cc6d8,c10cf0b0,c80fc8a0,...) at kdb_backtrace+0x2a witness_display_spinlock(c03664cf,c13d3e00,c03814cd,c10cf0b0,c0381166,...) at witness_display_spinlock+0x75 witness_checkorder(c13d3e00,9,c0381166,11d,0,...) at witness_checkorder+0x839 _sx_xlock(c13d3e00,0,c0381166,11d,c141e32c,...) at _sx_xlock+0x85 ufsdirhash_enduseful(c0f37a50,c4214800,200,c4214810,c80fc970,...) at ufsdirhash_enduseful+0x2f5 ufsdirhash_add(c141e32c,c80fc9fc,810,c80fc95c,c80fc960,...) at ufsdirhash_add+0x13 ufs_direnter(c1411648,c14fe648,c80fc9fc,c80fcbe0,c0f452e0,...) at ufs_direnter+0x729 ufs_readdir(c80fcc08,c80fcc1c,0,c80fcbb4,c80fcb4c,...) at ufs_readdir+0x2267 VOP_MKDIR_APV(c03bd600,c80fcc08,68,0,0,...) at VOP_MKDIR_APV+0xa5 kern_mkdirat(c1232870,ff9c,2843a780,0,1ed,...) at kern_mkdirat+0x211 kern_mkdir(c1232870,2843a780,0,1ed,c80fcc8c,...) at kern_mkdir+0x2e mkdir(c1232870,c80fccfc,c80fcd38,c0364eb3,0,...) at mkdir+0x29 syscallenter(c1232870,c80fccf4,c80fccf4,2,c0332bfa,...) at syscallenter+0x246 syscall(c80fcd38) at syscall+0x34 Xint0x80_syscall() at Xint0x80_syscall+0x22 --- syscall (136, FreeBSD ELF32, mkdir), eip = 0x28331a53, esp = 0xbf7fc47c, ebp = 0xbf7fc4a8 --- panic: ufs_dirbad: /: bad dir ino 95182 at offset 0: mangled entry cpuid = 0 KDB: enter: panic [thread pid 849 tid 100032 ] Stopped at kdb_enter+0x3a: movl$0,kdb_why DomU details: kernel = /var/lib/xen/images/kernel.freebsd memory = 128 name = freebsd vcpus = 1 vif = [ 'mac=00:16:3e:fb:41:28, bridge=xenbr0, ip=68.169.47.45, vifname=freebsd ] disk = [ 'phy:/dev/iscsi_0_5,sda,w', 'phy:/dev/iscsi_0_125,sdb,w' ] extra = boot_verbose=1 extra += ,vfs.root.mountfrom=ufs:/dev/da0 extra += ,kern.hz=100 Dom0 details: CentOS release 5.4 (Final) Linux 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-94.el5_4.2 --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV drivers for FreeBSD
Hi, I would not like to disturb you, but, have you a chance to reproduce the issue ? The problem is not with CDROM device, but with boot process stops. --- Yura On Dec 1, 2010, at 10:31 PM, Justin T. Gibbs wrote: On 12/1/2010 4:52 AM, Yuriy Kohut wrote: Hi, Now your commit in place and I have built XENHVM on RELENG_8. Some things are changed for me, but the issue still exists. I will try to replicate your issues again later today. One notable difference between my configuration and yours is that I am not passing through any cdrom devices. I have no idea how well block front deals with cdroms. My testing is on OpenSuSE 11.2 with Xen 4.0.0. -- Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV drivers for FreeBSD
I'll check RELANG_8. Thank you. --- Yura On Nov 27, 2010, at 2:09 AM, Justin T. Gibbs wrote: On 11/26/2010 8:56 AM, Yuriy Kohut wrote: Hi, I have just built XENHVM from RELANG_8_1. RELENG_8_1 doesn't have the latest Xen PV code in it. stable/8 (RELENG_8 if checking out of CVS instead of SVN?) does. -- Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV drivers for FreeBSD
Hi, I have just built XENHVM from RELANG_8_1. DomU boot stop just after CDROM was detected in kernel: acd0: CDROM QEMU DVD-ROM/0.10.2 at ata1-slave WDMA2 Boot doesn't continue for a long time, Xen shows VM is blocked: # xm list freebsd-8.1 NameID Mem VCPUs State Time(s) freebsd-8.1346 1024 1 -b113.3 By the other side, GENERIC worked just fine for me. Could somebody please assist ... --- Yura On Nov 26, 2010, at 4:26 PM, Luke Marsden wrote: On Wed, 2010-11-24 at 09:24 -0800, Sean Bruno wrote: The version in -CURRENT and FreeBSD 8 that Justin is talking about is very stable. I will be updating FreeBSD 7 and 6 today. You will need to update from source to get this version as it is not on the release ISOs We are using it a lot at Yahoo. It is very stable. Just to add another positive data-point, inspired by this post (thanks Sean!) I've just got 8.1-RELEASE working well on Flexiant, a UK-based Xen HVM cloud infrastructure provider. Here are the incantations I used to get it running stably: http://lukemarsden.net/blog/2010/11/running-freebsd-8-1-as-a-xen-hvm-domu-on-flexiant/ -- Best Regards, Luke Marsden CTO, Hybrid Logic Ltd. Web: http://www.hybrid-cluster.com/ Hybrid Web Cluster - cloud web hosting Mobile: +447791750420 ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: Xen PV drivers for FreeBSD
Hi, It is for amd64 only, correct ? Do you know is it stable enough ? --- Yura On Nov 24, 2010, at 3:48 PM, Justin T. Gibbs wrote: On 11/23/2010 8:27 AM, Yuriy Kohut wrote: Hi, I'm trying HVM DomU since FreeBSD paravirtualized is not stable enough. Is there any Xen PV drivers which could be used for HVM FreeBSD DomU to not load system by full hardware virtualization ? Yes. Use the XENHVM kernel config file. -- Justin ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Xen PV drivers for FreeBSD
Hi, I'm trying HVM DomU since FreeBSD paravirtualized is not stable enough. Is there any Xen PV drivers which could be used for HVM FreeBSD DomU to not load system by full hardware virtualization ? Thanks --- Yura ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: FreeBSD 8.1-RELEASE-p1 i386 xennet_get_responses messages in console
Hi, Dom0 details: CentOS release 5.4 (Final) x86_64 kernel: 2.6.18-164.6.1.el5xen Xen 3.0.3 (package from RHEL5 build xen-3.0.3-94.el5_4.2) DomU details: FreeBSD 8.1-RELEASE-p1 i386 Build from CVS tag: RELANG_8_1 I saw the messages any ones, and they gone after I reinstalled DomU. I'll try the patch if the issue appears ones more. Thank you. --- Yura On Nov 4, 2010, at 12:11 AM, Kenneth D. Merry wrote: On Thu, Oct 28, 2010 at 15:02:41 +0300, Yuriy Kohut wrote: Hi, Does somebody know haw to deal with the following massages in the console: xennet_get_responses: too many frags 6 max 5 What are you using for your Domain 0? I haven't run into that before, so it would be nice to have a setup that would trigger this problem. It looks like there is a limit on the number of segments for LRO. I think the limit is arbitrary, but I need to look at it a bit more. Try the attached patch and let me know whether it works for you. It disables the limit on the number of receive segments. Thanks, Ken -- Kenneth Merry k...@freebsd.org netfront.c.rx_max.stable.20101103.txt ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
