search for: i8254

...educing the sleep to 5 seconds... but as you can see the sleep ends a few seconds early and local time suddenly jumped forward 6 minutes 33 seconds... $ sysctl kern.timecounter kern.timecounter.fast_gettime: 1 kern.timecounter.tick: 1 kern.timecounter.choice: TSC-low(1000) ACPI-safe(850) HPET(950) i8254(0) dummy(-1000000) kern.timecounter.hardware: TSC-low kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 11598 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.HPET.mask: 4294967295 kern.time...

.... I just upgraded my server from 4.7-Stable to 5.0-Release by a full install. Now I hit a problem with the date.. the time goes much faster than normal.. maybe twice as normal... this morning I found the following kernel log in /var/log/messages May 26 17:23:58 jupiter kernel: Timecounter "i8254" frequency 1193182 Hz May 26 17:23:58 jupiter kernel: Timecounter "TSC" frequency 451024462 Hz May 26 17:23:58 jupiter kernel: Timecounter "ACPI-safe" frequency 3579545 Hz May 26 17:23:58 jupiter kernel: Timecounters tick every 10.000 msec that was about 17 hours ago.....

I've now seen this on two different VMs on two different ESXi servers (Xeon based hosts but different hardware otherwise and at different facilities): Everything runs fine for weeks then (seemingly) suddenly/randomly the clock STOPS. In the first case I saw a jump backwards of about 15 minutes (and then a 'freeze' of the clock). The second time just 'time standing

Hi, Did anyone else experience this? With 9.1-BETA1 the boot process freezes, among the last lines with verbose boot are acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times after this, dead. What is supposed to happen in the next stage? This laptop worked fine with 9-STABLE to at least february. //per

...t entropy this early? RDRAND/Padlock? Truerand? > Could hypervisors and simulators simply make sure these work? > If RDRAND is available, then Linux, at least, will use it. The rest are too complicated for early use. Linux on x86 plays some vaguely clever games with rdtsc and poking at the i8254 port. I think that these tricks are even less useful as a guest than they are on metal, and we can use paravirt mechanisms to make guest early boot rngs much stronger. --Andy

...t entropy this early? RDRAND/Padlock? Truerand? > Could hypervisors and simulators simply make sure these work? > If RDRAND is available, then Linux, at least, will use it. The rest are too complicated for early use. Linux on x86 plays some vaguely clever games with rdtsc and poking at the i8254 port. I think that these tricks are even less useful as a guest than they are on metal, and we can use paravirt mechanisms to make guest early boot rngs much stronger. --Andy

...ern.eventtimer.et.HPET1.flags: 3 kern.eventtimer.et.HPET1.frequency: 14318180 kern.eventtimer.et.HPET1.quality: 440 kern.eventtimer.et.HPET2.flags: 3 kern.eventtimer.et.HPET2.frequency: 14318180 kern.eventtimer.et.HPET2.quality: 440 kern.eventtimer.choice: HPET(450) HPET1(440) HPET2(440) LAPIC(400) i8254(100) RTC(0) kern.eventtimer.timer: HPET kern.timecounter.tc.HPET.mask: 4294967295 kern.timecounter.tc.HPET.counter: 749769877 kern.timecounter.tc.HPET.frequency: 14318180 kern.timecounter.tc.HPET.quality: 950 kern.timecounter.hardware: HPET kern.timecounter.choice: TSC(-1000) ACPI-fast(900) HPET(95...

Hello, kolleages! I have a problem. When I (or system) start the script 100.chksetuid in /etc/periodic/security my machine resets. The machine: Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.82-MHz 686-class CPU) System version: FreeBSD 4.10-STABLE #0: Mon Nov 8 06:50:54 PST 2004 I will glad to have help. Thank you in advance. -- Andrei Grudiy. Ukraine.

...all, even though with some warning. The other versions failed to install at all. After successful installation we noticed two problems: - After a couple of uptime hours top stopped to report CPU utilization numbers (all 0). This went away by changing the timercounter hardware from ACPI-fast to i8254 (kern.timecounter.hardware=i8254 in /etc/sysctl.conf). - The "TIMEOUT - WRITE_DMA" messages occur from time to time, always stopping the system for a few seconds (probably all processes trying to access the hard drive). So far I didn't manage to solve the latter. I upgraded to...

...opyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE #0: Mon Jul 28 19:35:09 MSD 2003 root@whale.rinet.ru:/usr/src/sys/compile/mini Calibrating clock(s) ... TSC clock: 1816175120 Hz, i8254 clock: 1193184 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 1816180228 Hz CPU: Intel(R) Celeron(R) CPU 1.80GHz (181...

...en if it only impact one domain, we prefer to use BUG_ON instead. Use [Panic/BUG_ON/ASSERT/BUG] will help different linked software modules to be aware of the HV''s consistency constraints. Below is an example we discussed with Keir which''s illustrative: I8254.c/hvm.c (c:\upstream\xen\xen\arch\x86\hvm): BUG_ON(bytes != 1); We want to make sure the handler for a single I/O port never accessed by multi-byte I/O port access. Although the illegal-access is not that fatal, it still affects HV''s consistency constraints. So...

...h. This is what this patch set does. It also converts the e500 machines and sPAPR to the new memory region model. Alex Alexander Graf (14): ac97: convert PIO to new memory api read/write virtio-pci: convert PIO to new memory api read/write es1370: convert PIO to new memory api read/write i8254: convert PIO to new memory api read/write m48t59: convert PIO to new memory api read/write mc146818rtc: convert PIO to new memory api read/write pc port92: convert PIO to new memory api read/write pckbd: convert PIO to new memory api read/write rtl8139: convert PIO to new memory api read/...

...cy 1000000000 Hz quality 950 acpi0: <Xen> on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0...

...-install of a box that was previously working fine under 4.7. The problem is that the matrox drm kernel module is failinf to initialise correctly. :from the dmesg: FreeBSD 4.8-STABLE #0: Thu May 8 11:41:26 SAST 2003 root@shagrat.prv.moria.org:/usr/src/sys/compile/SHAGRAT48 Timecounter "i8254" frequency 1193182 Hz CPU: Intel Pentium III (548.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR,SSE> real memory = 402587648 (393152K bytes) avail memo...

...at 0xcff68ebc APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled MADT: Found CPU APIC ID 4 ACPI ID 1: enabled MADT: Found CPU APIC ID 2 ACPI ID 2: enabled MADT: Found CPU APIC ID 6 ACPI ID 3: enabled ACPI APIC Table: <PTLTD APIC > Calibrating clock(s) ... i8254 clock: 1193204 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3000122064 Hz CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = "GenuineIntel" Id...

...er "HPET4" frequency 14318180 Hz quality 440 atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. Event timer "RTC" frequency 32768 Hz quality 0 attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on a...

...(c) 1992-2003 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 4.8-RELEASE-p7 #0: Sat Sep 20 17:07:38 EEST 2003 root:/space/usr/obj/space/usr/src/sys/MYKERN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199447955 Hz CPU: Pentium Pro (199.45-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV> real memory = 134217728 (13107...

Hello, With 7.1-RC2 : Dec 30 18:10:38 client1 kernel: FreeBSD 7.1-RC2 #0: Tue Dec 23 11:42:13 UTC 2008 Dec 30 18:10:38 client1 kernel: root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Dec 30 18:10:38 client1 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Dec 30 18:10:38 client1 kernel: CPU: Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (1800.01-MHz K8-class CPU) Dec 30 18:10:38 client1 kernel: Origin = "GenuineIntel" Id = 0x6f2 Stepping = 2 I have found following acpi warning and errors : Dec 30 18:10:3...

....chksetuid in /etc/periodic/security resets the mashine Reply-To: In-Reply-To: <20041112173824.GT26202@horsey.gshapiro.net> Hello, kolleages! I have a problem. When I (or system) start the script 100.chksetuid in /etc/periodic/security my machine resets. The machine: Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.82-MHz 686-class CPU) System version: FreeBSD 4.10-STABLE #0: Mon Nov 8 06:50:54 PST 2004 I will glad to have help. Thank you in advance. -- Andrei Grudiy. Ukraine.

...Padlock? Truerand? >> Could hypervisors and simulators simply make sure these work? >> > > If RDRAND is available, then Linux, at least, will use it. The rest > are too complicated for early use. Linux on x86 plays some vaguely > clever games with rdtsc and poking at the i8254 port. > > I think that these tricks are even less useful as a guest than they > are on metal, and we can use paravirt mechanisms to make guest early > boot rngs much stronger. Sorry for interrupting, as I understand the discussion tries to be generic. However, it sounds to me that at...