https://bugs.freedesktop.org/show_bug.cgi?id=107784
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #25 from Dmitrii Tcvetkov ---
The fix for TSC is merged: 17f6bac2249356c795 (x86/tsc: Prevent result
truncation on 32bit)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #24 from Sylvain BERTRAND ---
Yep, it manifest also on 32 bits x86. I posted also a bug report.
Since it's critical we'll probably get a new rc very soon.
--
You are receiving this mail because:
You are the assignee for the bug.___
Yep, it manifest also on 32 bits x86. I posted also a bug report.
Since it's critical we'll probably get a new rc very soon.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #23 from Dmitrii Tcvetkov ---
> Relevant discussion about cf7a63ef4e0203f (x86/tsc: Calibrate tsc only once)
> http://lkml.iu.edu/hypermail/linux/kernel/1809.0/03226.html
And there is a patch
http://lkml.iu.edu/hypermail/linux/kerne
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #22 from Dmitrii Tcvetkov ---
(In reply to Dmitrii Tcvetkov from comment #21)
> (In reply to Sylvain BERTRAND from comment #20)
> > Roughly, if you have a cpu with a frequency above 4.2GHz (max unsigned
> > 32bits),
> > linux time su
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #21 from Dmitrii Tcvetkov ---
(In reply to Sylvain BERTRAND from comment #20)
> Roughly, if you have a cpu with a frequency above 4.2GHz (max unsigned
> 32bits),
> linux time subsystem gets broken leading to the timeouts in displaypo
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #20 from Sylvain BERTRAND ---
Found the bug, very probably.
It seems to be an upstream bug: a 32bits multiplication overflow on TSC
frequency introduced in recent TSC cleanup:
---
Found the bug, very probably.
It seems to be an upstream bug: a 32bits multiplication overflow on TSC
frequency introduced in recent TSC cleanup:
commit cf7a63ef4e0203f6f33284c69e8188d91422de83
Author: Pavel Tatashin
Breaking commit is a merge commit from upstream mainline:
commit 13e091b6dd0e78a518a7d8756607d3acb8215768
Merge: eac341194426 1088c6eef261
Author: Linus Torvalds
Date: Mon Aug 13 18:28:19 2018 -0700
Merge branch 'x86-timers-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/g
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #19 from Sylvain BERTRAND ---
Breaking commit is a merge commit from upstream mainline:
commit 13e091b6dd0e78a518a7d8756607d3acb8215768
Merge: eac341194426 1088c6eef261
Author: Linus Torvalds
Date: Mon Aug 13 18:28:19 201
Got something, sort of obvious for a human, impossible for bisect to know,
which explains why this bisection was a failure:
testing a commit in the middle of a series of commits which are to be taken as
a whole to be consistent for normal operations of the kernel, is wrong. That,
bisect cannot know
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #18 from Sylvain BERTRAND ---
Got something, sort of obvious for a human, impossible for bisect to know,
which explains why this bisection was a failure:
testing a commit in the middle of a series of commits which are to be taken as
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #17 from Sylvain BERTRAND ---
On Thu, Sep 06, 2018 at 02:22:18PM +, bugzilla-dae...@freedesktop.org
wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
>
> --- Comment #16 from Michel Dänzer ---
> "this commit" being 0
On Thu, Sep 06, 2018 at 02:22:18PM +, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
>
> --- Comment #16 from Michel Dänzer ---
> "this commit" being 019cddc88f9e4ae0de2c76802f7137210c2101aa (the I2C merge),
> which has two parents. Both of those
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #16 from Michel Dänzer ---
(In reply to Sylvain BERTRAND from comment #15)
> Not consistent? Could you be more specific?
You wrote:
(In reply to Sylvain BERTRAND from comment #6)
>- this commit is failing.
>- the co
On Thu, Sep 06, 2018 at 10:04:53AM +, bugzilla-dae...@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
>
> --- Comment #14 from Michel Dänzer ---
> That's not consistent with the merge commit you identified earlier. So I'm
> afraid it's likely that you incorrectly
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #15 from Sylvain BERTRAND ---
On Thu, Sep 06, 2018 at 10:04:53AM +, bugzilla-dae...@freedesktop.org
wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
>
> --- Comment #14 from Michel Dänzer ---
> That's not consistent
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #14 from Michel Dänzer ---
(In reply to Sylvain BERTRAND from comment #11)
> bisected: e2a9ca29b5edc89da2fddeae30e1070b272395c5
>
> This commit is one in a series related to new TSC code
That's not consistent with the merge commit
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #13 from Sylvain BERTRAND ---
Created attachment 141465
--> https://bugs.freedesktop.org/attachment.cgi?id=141465&action=edit
kernel log from a good commit
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107784
Sylvain BERTRAND changed:
What|Removed |Added
Attachment #141416|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #11 from Sylvain BERTRAND ---
bisected: e2a9ca29b5edc89da2fddeae30e1070b272395c5
This commit is one in a series related to new TSC code.
I tried to switch the clocksource to hpet early in the boot process, did not
change anything.
bisected: e2a9ca29b5edc89da2fddeae30e1070b272395c5
This commit is one in a series related to new TSC code.
I tried to switch the clocksource to hpet early in the boot process, did not
change anything.
Any ideas before I post an issue on kernel bugzilla?
__
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #10 from Felix Schwarz ---
(In reply to Sylvain BERTRAND from comment #9)
> Ok, I got it. Since my git knowledge is quite limited, this "merge" commit is
> opening a vast sea of new commits to test.
>
> I'll dive into bisection usi
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #9 from Sylvain BERTRAND ---
Ok, I got it. Since my git knowledge is quite limited, this "merge" commit is
opening a vast sea of new commits to test.
I'll dive into bisection using bisect (which actually deals with those merge
comm
Ok, I got it. Since my git knowledge is quite limited, this "merge" commit is
opening a vast sea of new commits to test.
I'll dive into bisection using bisect (which actually deals with those merge
commits). I am a bit scared of the amount of commits, may take hours/days.
Please, in the foreseab
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #8 from Felix Schwarz ---
Bugzilla: The tool which preserves all my stupid errors for eternity. :-/
Sorry, I just read the previous comments and of course you used git bisect
already... Still you should test both parents of a merge
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #7 from Felix Schwarz ---
In reply to Sylvain BERTRAND from comment #6)
> I tested several times that:
>- this commit is failing.
>- the commit right before this one was working.
>
> Then, I can reasonably say, this
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #6 from Sylvain BERTRAND ---
I tested several times that:
- this commit is failing.
- the commit right before this one was working.
Then, I can reasonably say, this commit, whatever its type, is the one breaking
di
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #5 from Michel Dänzer ---
(In reply to Sylvain BERTRAND from comment #4)
> faulty commit: 019cddc88f9e4ae0de2c76802f7137210c2101aa on
> amd-staging-drm-next
That's a pure merge commit, so it's unlikely to be the one that actually ca
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #4 from Sylvain BERTRAND ---
I did a manual bisection and got lucky:
faulty commit: 019cddc88f9e4ae0de2c76802f7137210c2101aa on amd-staging-drm-next
this commit is i2c related, right before the commit
5e8704ac1cfa9fceef94fcc457e186
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #3 from Sylvain BERTRAND ---
On Mon, Sep 03, 2018 at 09:17:30AM +, bugzilla-dae...@freedesktop.org
wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=107784
>
> --- Comment #2 from Michel Dänzer ---
> Can you bisect?
I don'
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #2 from Michel Dänzer ---
Can you bisect?
P.S. Please enable CONFIG_UNWINDER_ORC in your kernel build, to make the
backtraces in dmesg more useful.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=107784
--- Comment #1 from Sylvain BERTRAND ---
Created attachment 141416
--> https://bugs.freedesktop.org/attachment.cgi?id=141416&action=edit
kernel log
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107784
Bug ID: 107784
Summary: [AMD tahiti XT] displayport broken
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: b
35 matches
Mail list logo
