From: Martin Peres <martin.peres@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
"Lofstedt, Marta" <marta.lofstedt@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"pasha.tatashin@oracle.com" <pasha.tatashin@oracle.com>
Subject: Re: freedesktop bug id: 100548, bisected to sched/clock commit
Date: Wed, 12 Apr 2017 16:40:11 +0300 [thread overview]
Message-ID: <9fc50a4b-da78-5e18-8fed-3bf91a7091a7@linux.intel.com> (raw)
In-Reply-To: <20170412123134.GD5680@worktop>
On 12/04/17 15:31, Peter Zijlstra wrote:
> On Wed, Apr 12, 2017 at 12:04:00PM +0000, Lofstedt, Marta wrote:
>> Hi,
>>
>> We have this "old" Lenovo Cantiga laptop(Intel Core 2 Duo L9400), hocked up to our i915 pre-merge CI system, that has started to give unstable results after commit:
>>
>> commit 7b09cc5a9debc86c903c2eff8f8a1fdef773c649
>> Author: Pavel Tatashin <pasha.tatashin@oracle.com>
>> Date: Wed Mar 22 16:24:17 2017 -0400
>>
>> sched/clock: Fix broken stable to unstable transfer
>>
>> The issue is describe more in detail here:
>> https://bugs.freedesktop.org/show_bug.cgi?id=100548
>
> I don't click links.
>
>> We have reverted above patch and then issue is no longer reproducible.
>> Also, note that this issue has not been reproduced on any of our other machines,
>> https://intel-gfx-ci.01.org/CI/
>>
>> So, why is this only affecting the Core 2 Duo?
>
> Core2 doesn't have a usable TSC and would revert to the slow path. I'll
> have another look at that patch.
>
So, by default, it is using the hpet clock source. FYI, I tried the only
other available clock source (acpi_pm) and got the same result.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-12 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 12:04 freedesktop bug id: 100548, bisected to sched/clock commit Lofstedt, Marta
2017-04-12 12:31 ` Peter Zijlstra
2017-04-12 13:30 ` Jani Nikula
2017-04-12 14:28 ` Peter Zijlstra
2017-04-12 13:40 ` Martin Peres [this message]
2017-04-12 14:32 ` Peter Zijlstra
2017-04-12 14:49 ` Martin Peres
2017-04-12 15:50 ` Peter Zijlstra
2017-04-13 11:48 ` Peter Zijlstra
2017-04-13 12:30 ` Martin Peres
2017-04-13 13:23 ` Peter Zijlstra
2017-04-13 14:55 ` Thomas Gleixner
2017-04-18 14:10 ` Lofstedt, Marta
2017-04-18 15:53 ` Peter Zijlstra
2017-04-20 17:19 ` Peter Zijlstra
2017-04-20 19:36 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9fc50a4b-da78-5e18-8fed-3bf91a7091a7@linux.intel.com \
--to=martin.peres@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marta.lofstedt@intel.com \
--cc=pasha.tatashin@oracle.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox