Re: [Xen-devel] [Xen-users] Re: Xen 4 TSC problems

[Mauro <mrsanna1@xxxxxxxxx>]

On 23 October 2012 16:46, Mauro <mrsanna1@xxxxxxxxx> wrote:
> On 23 October 2012 16:43, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>> On 23.10.12 at 16:07, Mauro <mrsanna1@xxxxxxxxx> wrote:
>>> On 23 October 2012 13:50, Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx> wrote:
>>>> On Tue, Oct 23, 2012 at 09:50:13AM +0100, Jan Beulich wrote:
>>>>> >>> On 23.10.12 at 10:40, Mauro <mrsanna1@xxxxxxxxx> wrote:
>>>>> > On 23 October 2012 09:58, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>> >>>>> On 23.10.12 at 09:18, Mauro <mrsanna1@xxxxxxxxx> wrote:
>>>>> >>>>  A kernel run with no Xen underneath it.
>>>>> >>>
>>>>> >>> Here is:
>>>>> >>>
>>>>> >>> uname -a
>>>>> >>> Linux xen-p02 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012
>>>>> >>> x86_64 GNU/Linux
>>>>> >>
>>>>> >> I'm sorry to say that, but 2.6.32 is nowhere close to "recent" (as
>>>>> >> I had asked for).
>>>>> >
>>>>> > Sorry I'm using squeeze in production servers and I don't have a test
>>>>> > machine on which install wheezy.
>>>>>
>>>>> And can't/don't want to install a self-built kernel?
>>>>
>>>> You could also boot one of those Live Image kernels. Like an Fedora or
>>>> Ubuntu and just capture this. That way you don't over-write anything.
>>>
>>> Ok, I'll try the live image.
>>> Today I had another clock jump so cpuidle=0 doesn't work.
>>> I'll stay using clocksource= pit and cpuidle =0 for a while to see if
>>> they together work.
>>> But...how to know what C states the kernel uses?
>>
>> If "cpuidle=0" alone doesn't work, your problem is not C-state
>> related, and you don't need to look up how much of it the native
>> kernel uses.
>
> Ok, cpuidle=0 however is to be used because also clocksource=pit alone
> doesn't work.
> Now I'll use both params and see what happens.

Sorry for the noise, I'm not sure if it has been really a clock jump.
Retry using only cpuidle=0 and then what Jan has suggested.
If you want to see the C states tell me how to do.

p.s. sorry for bad english

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel