https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #19 from mrj at advancedcontrols.com.au ---
Alex, I've created Bug 99326.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=95206
Alex Deucher changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #18 from Alex Deucher ---
(In reply to mrj from comment #15)
> Sorry Alex, I wasn't clear.
>
> It's the fixed version that (I've now verified) is causing the Radeon HD6320
> problem as described here
>
> https://bugzilla.redhat.com/
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #17 from mrj at advancedcontrols.com.au ---
The good and bad kernels give identical xrandr outputs:
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
XWAYLAND0 connected 1360x768+0+0 520mm x 320mm
1360x768 5
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #16 from mrj at advancedcontrols.com.au ---
The (native) display resolution exhibiting the problem on the Radeon HD6320
(AMD G-series T56N) is 1366x768.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=95206
mrj at advancedcontrols.com.au changed:
What|Removed |Added
Resolution|FIXED |---
Status|R
https://bugs.freedesktop.org/show_bug.cgi?id=95206
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #13 from mrj at advancedcontrols.com.au ---
May be causing https://bugzilla.redhat.com/show_bug.cgi?id=1402293
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #12 from Christian L. ---
Your fix works like a charm. Thanks alot!
Applied the fix to 4.5.0 mainline and the problem is gone.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part -
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #11 from Alex Deucher ---
Created attachment 123629
--> https://bugs.freedesktop.org/attachment.cgi?id=123629&action=edit
possible fix
This patch should fix it.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #10 from Christian L. ---
Created attachment 123618
--> https://bugs.freedesktop.org/attachment.cgi?id=123618&action=edit
dmesg with debugging patch
attached dmesg output of mainline kernel 4.5.0 with your debugging patch
applied
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #9 from Alex Deucher ---
Created attachment 123611
--> https://bugs.freedesktop.org/attachment.cgi?id=123611&action=edit
add debugging output
Can you attach the dmesg output with the attached debugging patch applied?
--
You are r
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #8 from Christian L. ---
Hi,
I've bisected the problem down to the following commit to the mainline kernel
(see below). Can I help with some further information?
092c96a8ab9d1bd60ada2ed385cc364ce084180e is the first bad commit
commi
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #7 from barneyman at gmx.de ---
Ok, understood. Didn't know that feature. I'll give it a try in the next days.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #6 from Felix Schwarz ---
"bisecting" is a way to find out which commit caused a specific regression.
This involves compiling the linux kernel from git and testing the compiled
versions. If you can find out which commit is the culprit
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #5 from barneyman at gmx.de ---
Attachments added...
What do you mean with bisect?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #4 from barneyman at gmx.de ---
Created attachment 123352
--> https://bugs.freedesktop.org/attachment.cgi?id=123352&action=edit
xrandr output kernel 4.5.2
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #3 from barneyman at gmx.de ---
Created attachment 123351
--> https://bugs.freedesktop.org/attachment.cgi?id=123351&action=edit
Xorg.0.log kernel 4.5.2
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #2 from barneyman at gmx.de ---
Created attachment 123350
--> https://bugs.freedesktop.org/attachment.cgi?id=123350&action=edit
dmesg kernel 4.5.2
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #1 from Alex Deucher ---
Please attach your xorg log and dmesg output. Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbe
https://bugs.freedesktop.org/show_bug.cgi?id=95206
Bug ID: 95206
Summary: Display port bandwidth regression
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity:
21 matches
Mail list logo