Hi,
Thomas Gleixner writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > All numbers in micro seconds! What happens if you load the system or
>> > restrict C-States?
>>
>> added intel_idle.max_cstate=0 to cmdline. Still see
Hi,
Thomas Gleixner writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > All numbers in micro seconds! What happens if you load the system or
>> > restrict C-States?
>>
>> added intel_idle.max_cstate=0 to cmdline. Still see some failures,
>> albeit a lot more
On Wed, 28 Feb 2018, Felipe Balbi wrote:
> Thomas Gleixner writes:
> > All numbers in micro seconds! What happens if you load the system or
> > restrict C-States?
>
> added intel_idle.max_cstate=0 to cmdline. Still see some failures,
> albeit a lot more rare, for example,
On Wed, 28 Feb 2018, Felipe Balbi wrote:
> Thomas Gleixner writes:
> > All numbers in micro seconds! What happens if you load the system or
> > restrict C-States?
>
> added intel_idle.max_cstate=0 to cmdline. Still see some failures,
> albeit a lot more rare, for example, caught one on iteration
Thomas Gleixner writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > Enable the hrtimer and scheduling tracepoints. That should give you a hint
>> > what's going on.
>>
>> Thanks, that does give me a lot more information. So
Thomas Gleixner writes:
> On Wed, 28 Feb 2018, Felipe Balbi wrote:
>> Thomas Gleixner writes:
>> > Enable the hrtimer and scheduling tracepoints. That should give you a hint
>> > what's going on.
>>
>> Thanks, that does give me a lot more information. So here you go:
>>
>>
On Wed, 28 Feb 2018, Felipe Balbi wrote:
> Thomas Gleixner writes:
> > Enable the hrtimer and scheduling tracepoints. That should give you a hint
> > what's going on.
>
> Thanks, that does give me a lot more information. So here you go:
>
> rtctest-1348 [003] d..2
On Wed, 28 Feb 2018, Felipe Balbi wrote:
> Thomas Gleixner writes:
> > Enable the hrtimer and scheduling tracepoints. That should give you a hint
> > what's going on.
>
> Thanks, that does give me a lot more information. So here you go:
>
> rtctest-1348 [003] d..2 313.766141:
Hi,
Thomas Gleixner writes:
> On Tue, 27 Feb 2018, Felipe Balbi wrote:
>> I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
>> final) where rtctest fails sometimes which PIE coming too late with
>> frequencies >= 1024 Hz.
>>
>> I've modified rtctest.c a
Hi,
Thomas Gleixner writes:
> On Tue, 27 Feb 2018, Felipe Balbi wrote:
>> I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
>> final) where rtctest fails sometimes which PIE coming too late with
>> frequencies >= 1024 Hz.
>>
>> I've modified rtctest.c a bit so that it
On Tue, 27 Feb 2018, Felipe Balbi wrote:
> I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
> final) where rtctest fails sometimes which PIE coming too late with
> frequencies >= 1024 Hz.
>
> I've modified rtctest.c a bit so that it continues running even after
> first failure
On Tue, 27 Feb 2018, Felipe Balbi wrote:
> I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
> final) where rtctest fails sometimes which PIE coming too late with
> frequencies >= 1024 Hz.
>
> I've modified rtctest.c a bit so that it continues running even after
> first failure
Hi folks,
I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
final) where rtctest fails sometimes which PIE coming too late with
frequencies >= 1024 Hz.
I've modified rtctest.c a bit so that it continues running even after
first failure just so I could get a glimpse of how
Hi folks,
I'm facing an odd problem with v4.16-rc2 (also reproducible on v4.15
final) where rtctest fails sometimes which PIE coming too late with
frequencies >= 1024 Hz.
I've modified rtctest.c a bit so that it continues running even after
first failure just so I could get a glimpse of how
14 matches
Mail list logo