Hi Andi, Just that - nothing else. Machine is now keeping perfect time, and there are now no messages about lost ticks (at least not for the last 12 hours). Last thing when I look at the output of dmesg I get the following (see below), I am slightly worried, since I have read somewhere that the kernel needs to be patched to include a more recent version of powernow-k8. Is this error expected, or should I patch? Best wishes, jon. powernow-k8: Found 2 AMD Athlon 64 / Opteron processors (version 1.50.3) powernow-k8: 0 : fid 0xe (2200 MHz), vid 0x8 (1350 mV) powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV) cpu_init done, current fid 0xe, vid 0x8 limiting to cpu 2 failed limiting to cpu 3 failed limiting to cpu 4 failed limiting to cpu 5 failed limiting to cpu 6 failed limiting to cpu 7 failed limiting to cpu 8 failed limiting to cpu 9 failed limiting to cpu 10 failed limiting to cpu 11 failed limiting to cpu 12 failed limiting to cpu 13 failed limiting to cpu 14 failed limiting to cpu 15 failed limiting to cpu 16 failed limiting to cpu 17 failed limiting to cpu 18 failed limiting to cpu 19 failed limiting to cpu 20 failed limiting to cpu 21 failed limiting to cpu 22 failed limiting to cpu 23 failed limiting to cpu 24 failed limiting to cpu 25 failed limiting to cpu 26 failed limiting to cpu 27 failed limiting to cpu 28 failed limiting to cpu 29 failed limiting to cpu 30 failed limiting to cpu 31 failed limiting to cpu 32 failed limiting to cpu 33 failed limiting to cpu 34 failed limiting to cpu 35 failed limiting to cpu 36 failed limiting to cpu 37 failed limiting to cpu 38 failed limiting to cpu 39 failed limiting to cpu 40 failed limiting to cpu 41 failed limiting to cpu 42 failed limiting to cpu 43 failed limiting to cpu 44 failed limiting to cpu 45 failed limiting to cpu 46 failed limiting to cpu 47 failed limiting to cpu 48 failed limiting to cpu 49 failed limiting to cpu 50 failed limiting to cpu 51 failed limiting to cpu 52 failed limiting to cpu 53 failed limiting to cpu 54 failed limiting to cpu 55 failed limiting to cpu 56 failed limiting to cpu 57 failed limiting to cpu 58 failed limiting to cpu 59 failed limiting to cpu 60 failed limiting to cpu 61 failed limiting to cpu 62 failed limiting to cpu 63 failed limiting to cpu 64 failed limiting to cpu 65 failed limiting to cpu 66 failed limiting to cpu 67 failed limiting to cpu 68 failed limiting to cpu 69 failed limiting to cpu 70 failed limiting to cpu 71 failed limiting to cpu 72 failed limiting to cpu 73 failed limiting to cpu 74 failed limiting to cpu 75 failed limiting to cpu 76 failed limiting to cpu 77 failed limiting to cpu 78 failed limiting to cpu 79 failed limiting to cpu 80 failed limiting to cpu 81 failed limiting to cpu 82 failed limiting to cpu 83 failed limiting to cpu 84 failed limiting to cpu 85 failed limiting to cpu 86 failed limiting to cpu 87 failed limiting to cpu 88 failed limiting to cpu 89 failed limiting to cpu 90 failed limiting to cpu 91 failed limiting to cpu 92 failed limiting to cpu 93 failed limiting to cpu 94 failed limiting to cpu 95 failed limiting to cpu 96 failed limiting to cpu 97 failed limiting to cpu 98 failed limiting to cpu 99 failed limiting to cpu 100 failed limiting to cpu 101 failed limiting to cpu 102 failed limiting to cpu 103 failed limiting to cpu 104 failed limiting to cpu 105 failed limiting to cpu 106 failed limiting to cpu 107 failed limiting to cpu 108 failed limiting to cpu 109 failed limiting to cpu 110 failed limiting to cpu 111 failed limiting to cpu 112 failed limiting to cpu 113 failed limiting to cpu 114 failed limiting to cpu 115 failed limiting to cpu 116 failed limiting to cpu 117 failed limiting to cpu 118 failed limiting to cpu 119 failed limiting to cpu 120 failed limiting to cpu 121 failed limiting to cpu 122 failed limiting to cpu 123 failed limiting to cpu 124 failed limiting to cpu 125 failed limiting to cpu 126 failed limiting to cpu 127 failed Andi Kleen wrote:
On Friday 28 October 2005 00:29, Jonathan Brooks wrote:
You can test if notsc helps, but it's only a small chance imho.
Well something seems to have helped :)
What did you do exactly? Add these options? Anything else?
-Andi
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon