[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 Dexuan Cui changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 --- Comment #3 from Dexuan Cui --- The further patches on 11-CURRENT should fix the bug safely now: https://github.com/freebsd/freebsd/commit/297e2d2f528a41d9a9614e9b34049801f6935b31 https://github.com/freebsd/freebsd/commit/28d2243294e521bd34a063a402382b21ad03b262 https://github.com/freebsd/freebsd/commit/dbf747e96c50495258170a73aa5a6ab288b8b958 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 --- Comment #2 from Dexuan Cui --- The tsc-calibration fix was temporarily taken back last Friday because we found an interesting thing: with some kind of config, Xen can pretend to be Hyper-V by mimicking the hypervisor CPUID signature (this is usually to make Windows VM run better on Xen), but Xen doesn’t support Hyper-V timecounter, so the fix causes an unexpected panic when FreeBSD VM runs on Xen in this case. We're making another patch to better detect if the underlying hypervisor supports Hyper-V timecounter or not: https://lists.freebsd.org/pipermail/freebsd-current/2016-April/060519.html -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 208238] [Hyper-V] TSC frequency is not correctly detected: "calcru: runtime went backwards"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-virtualization@Free ||BSD.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: calcru runtime went backwards
Hi Kurt, So, disabling Turbo-Boost doesn't resolve the problem. Thanks for the info. I have access to a machine with similar specs to will try and repro. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: calcru runtime went backwards
On 7/8/13 11:54 PM, Peter Grehan wrote: Hi Kurt, CPU: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz (2300.13-MHz K8-class CPU) Looks like this Sandy Bridge has turbo-boost. First step is to disable that in the BIOS and see if that has any effect. How many vCPUs in the guest ? I was finally able to do this. I turned off the Turbo-Boost in the BIOS, and restarted everything. My virtual machine is configured with 4 cpus and 10240 (10GB) of memory. I got the same error today when compiling python in the virtual machine: calcru: runtime went backwards from 48142872748812902 usec to 593237864 usec for pid 73714 (make) calcru: runtime went backwards from 48142872748812902 usec to 593157552 usec for pid 73714 (make) Looking at the console log, I also found the following on the console when it was booting: calcru: runtime went backwards from 8023812124181248 usec to 979712 usec for pid 13 (geom) So, disabling Turbo-Boost doesn't resolve the problem. -Kurt ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: calcru runtime went backwards
Hi Kurt, CPU: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz (2300.13-MHz K8-class CPU) Looks like this Sandy Bridge has turbo-boost. First step is to disable that in the BIOS and see if that has any effect. How many vCPUs in the guest ? later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
calcru runtime went backwards
Greetings - I have been using bhyve for a while to host a FreeBSD stable/9 client. It works pretty well, but I often get messages similar to this, after a kick off a full 'buildworld' on the virtual host: calcru: runtime went backwards from 8023812124499416 usec to 1365567459 usec for pid 34794 (make) calcru: runtime went backwards from 8023812124499416 usec to 1365055948 usec for pid 34794 (make) I have the following in my /boot/loader.conf on the virtual host: zfs_load="YES" vfs.root.mountfrom="zfs:zroot2" virtio_load="YES" virtio_pci_load="YES" virtio_blk_load="YES" if_vtnet_load="YES" autoboot_delay="3" kern.hz="100" vfs.zfs.prefetch_disable="0" dtraceall_load="YES" (I have a small UFS partition that I mount as /bootdir, and /boot is symlinked into that. So, the virtual machine loads the kernel off of UFS, but everything else is ZFS on the machine.) Any suggestions for eliminating this warning? -Kurt (dmesg of host machine follows) Copyright (c) 1992-2013 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 10.0-CURRENT #0: Mon Jun 24 15:19:10 EDT 2013 lidl@busybox:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz (2300.13-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Features=0xbfebfbff Features2=0x1fbee3ff AMD Features=0x2c100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 32025104384 (30541 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 ioapic1 irqs 24-47 on motherboard ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of f000, 1800 (3) failed cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 cpu8: on acpi0 cpu9: on acpi0 cpu10: on acpi0 cpu11: on acpi0 atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed0-0xfed03fff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 350 Event timer "HPET1" frequency 14318180 Hz quality 340 Event timer "HPET2" frequency 14318180 Hz quality 340 Event timer "HPET3" frequency 14318180 Hz quality 340 Event timer "HPET4" frequency 14318180 Hz quality 340 Event timer "HPET5" frequency 14318180 Hz quality 340 Event timer "HPET6" frequency 14318180 Hz quality 340 Event timer "HPET7" frequency 14318180 Hz quality 340 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 1.1 on pci0 pci2: on pcib2 xhci0: mem 0xe040-0xe0401fff irq 16 at device 0.0 on pci2 usbus0: waiting for BIOS to give up control xhci0: 32 byte context size. usbus0 on xhci0 pcib3: at device 2.0 on pci0 pci3: on pcib3 vgapci0: port 0x3000-0x30ff mem 0xd000-0xdfff,0xe030-0xe031 irq 16 at device 0.0 on pci3 hdac0: mem 0xe032-0xe0323fff irq 17 at device 0.1 on pci3 pcib4: at device 3.0 on pci0 pci4: on pcib4 pci0: at device 5.0 (no driver attached) pci0: at device 5.2 (no driver attached) pcib5: at device 17.0 on pci0 pci5: on pcib5 pci0: at device 22.0 (no driver attached) em0: port 0x4040-0x405f mem 0xe050-0xe051,0xe0525000-0xe0525fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: Ethernet address: 70:54:d2:90:89:c5 ehci0: mem 0xe0601000-0xe06013ff irq 16 at device 26.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 hdac1: mem 0xe052-0xe0523fff irq 22 at device 27.0 on pci0 pcib6: at device 28.0 on p
