Hi Kai-Heng,
On Thu, Aug 29, 2019 at 5:14 PM Kai-Heng Feng
wrote:
>
> Some Coffee Lake platforms have skewed HPET timer once the SoCs entered
> PC10, and marked TSC as unstable clocksource as result.
>
> Harry Pan identified it's a firmware bug [1].
>
> To prevent creating a circular dependency b
Hi Thomas,
> On Aug 30, 2019, at 03:45, Thomas Gleixner wrote:
>
> On Thu, 29 Aug 2019, Kai-Heng Feng wrote:
>> at 20:13, Thomas Gleixner wrote:
>>> On Thu, 29 Aug 2019, Kai-Heng Feng wrote:
>>>
Some Coffee Lake platforms have skewed HPET timer once the SoCs entered
PC10, and marked
On Thu, 29 Aug 2019, Kai-Heng Feng wrote:
> at 20:13, Thomas Gleixner wrote:
> > On Thu, 29 Aug 2019, Kai-Heng Feng wrote:
> >
> > > Some Coffee Lake platforms have skewed HPET timer once the SoCs entered
> > > PC10, and marked TSC as unstable clocksource as result.
> >
> > So here you talk abou
at 20:13, Thomas Gleixner wrote:
On Thu, 29 Aug 2019, Kai-Heng Feng wrote:
Some Coffee Lake platforms have skewed HPET timer once the SoCs entered
PC10, and marked TSC as unstable clocksource as result.
So here you talk about Coffee Lake and in the patch you use KABYLAKE.
Coffeelake has t
On Thu, 29 Aug 2019, Kai-Heng Feng wrote:
> Some Coffee Lake platforms have skewed HPET timer once the SoCs entered
> PC10, and marked TSC as unstable clocksource as result.
So here you talk about Coffee Lake and in the patch you use KABYLAKE.
> Harry Pan identified it's a firmware bug [1].
>
Some Coffee Lake platforms have skewed HPET timer once the SoCs entered
PC10, and marked TSC as unstable clocksource as result.
Harry Pan identified it's a firmware bug [1].
To prevent creating a circular dependency between HPET and TSC, let's
disable HPET on affected platforms.
[1]: https://lor
6 matches
Mail list logo