search for: pmtmr

...lt;http://tinyurl.com/ycpcfv> To configure Windows Guest OS: http://tinyurl.com/yctxrr <http://tinyurl.com/yctxrr> To configure CentOS w/o X installed, you still need to install the vmware tools. Edit the vmx file for your guest, tools.syncTime="TRUE". In grub.conf, add clock=pmtmr as a kernel option. You'll need to shutdown the guest OS, reload the vmx file, then restart the system. If you have X running, then you can use the vmware tools much like windows to configure time sync with the host system. HTH Mark -------------- next part -------------- An HTML attachme...

...TSC on that platform. Action is required for these operating systems as outlined in the "Solutions" section below, but, fortunately, many of them already provide simple boot configuration options that allow the TSC to be bypassed (such as "notsc" and "clock=pmtmr") to work around this problem. C2 and C3 State Change ====================== The core-clock grid can be divided up and down when entering and exiting C2 and C3 states and the TSC is adjusted accordingly. However, the clock-grid of all cores on a processor are ramped up and...

i see this message in the dmesg , any one know this problem and the soliontion ??? Losing some ticks... checking if CPU frequency changed. thaks Jos? P?rez

The following error on a SMP x86_64 Centos 4.3 kernel 2.6.9-34 ELsmp appears at boot. and causes things to compute faster. Example, a wait(5) should wait for 5 seconds....it waits for 3 or 2. This was an open bug for that kernel. Has it been patched in the more recent kernel for Centos 2.6.9-34.0.1 ? dmseg output: Freeing unused kernel memory: 164k freed Losing some ticks... checking if CPU

...e anyone else gets bitten, I noticed that a bunch of my dual core opteron machines were losing time sync pretty fast (gaining a few days every few days...heh). I searched back on the list and found some messages about passing a clock parameter in grub.conf. The following worked for me: clock=pmtmr These are systems using the Supermicro H8SLL-i boards and Opteron 175-185 cpus and running CentOS 4.3. Cheers,

I installed CentOS 4.4 32 bit on a dual core AMD64 motherboad. Its a Tyan Tomcat K8E motherboard with socket 939. The clock keeps drifting off like 5+ minutes an hour. Run ntpupdate hourly to compensate. Any ideas why or how to fix? Matt

Hi, I'm about to setup a CentOS4 server to install VmWare Server on it. Then I'll run 2 main guest OS, Microsoft SBS 2003, and a CentOS development LAMP server. Except from the clock settings, is there any problems/comments? Regards, Ugo

Hi, I have a dual core athlon server and it is gaining 1 day every 2 days w/o time sync. Even with ntpd running, the time is not under control. I must put a very frequent cronjob of 'ntpdate' to keep the time under control. This creates big problems since winbind eventually stops working so my users can't access their data. Any ideas? -- Ugo -> Please don't send a copy of

I've got an odd situation that I need some advise on. I have two computers that I am planning to use as a cluster. I initially started with some left over Compaq Presairos with 667MHz CPUs. I loaded CentOS 4.3 and later updated to 4.4. Things ran normally, albeit slowly. I had an opportunity to upgrade to a pair of IBM Netvistas with 2.26 GHz CPUs, I did this by transferring the

...urces starting at 20000000 (gap: 1e000000:e1780000) Built 1 zonelists Kernel command line: ro root=/dev/md1 mapped APIC to ffffd000 (fee00000) Initializing CPU#0 CPU 0 irqstacks, hard=c0400000 soft=c03ff000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 2787.059 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 482360k/491200k available (2150k kernel code, 8196k reserved, 716k data, 164k init, 0k highmem) Calibrating delay...

Hi, Updated to current bk today, and my machine stopped booting ... I''ve tracked it down to the apic changes from end of last week. cset 1.1307 boots fine, 1.1308 doesn''t. Diff of the boot messages is below. Full logs are also attached. Gerd --- log-1.1307 2005-04-21 14:40:57.372885027 +0200 +++ log-1.1308 2005-04-21 14:38:52.236553392 +0200 @@ -7,7 +7,7 @@