https://bugzilla.kernel.org/show_bug.cgi?id=83461
Thom changed:
What|Removed |Added
CC||madeforspam at telfort.nl
--- Comment #38 from
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #37 from Alex Deucher ---
(In reply to Joerg Esser from comment #35)
> I had similar problems until I used 3.18.7.
> I couldn´t even boot beyond radeon load. The whole kernel crashed and my
> Monitor showed no usable signal. I had to
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #36 from Joerg Esser ---
Oh I forgot, In the kernel changelog it also hits bug 91861.
And it isn´t in 3.19 because there I still have those problem.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
Joerg Esser changed:
What|Removed |Added
CC||jackfritt at boh.de
--- Comment #35 from
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #34 from Alex Deucher ---
Already upstream:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=72edd83cc9e5819ed1ee771519143d7594e059f0
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=83461
tuxoholic at hotmail.de changed:
What|Removed |Added
CC||tuxoholic at hotmail.de
---
https://bugzilla.kernel.org/show_bug.cgi?id=83461
Christian König changed:
What|Removed |Added
Attachment #156211|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #31 from kb at spatium.org ---
Christian, do you have any further ideas? Can perhaps the ref_div_max be
settable via sysfs so that I can cap it on boot?
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #30 from Markus Gaugusch ---
Additional info: With the (unmodified) patch applied, I get a message
"Nonpreset Mode" displayed on my monitor when I turn it on. So I think the
patch is not 100% correct ...
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #29 from Markus Gaugusch ---
Hi,
I've also verified that commit 32167016076f714f0e35e287fbead7de0f1fb179 breaks
my system:
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880
[Radeon HD 4250] (prog-if 00
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #28 from kb at spatium.org ---
I think your patch has a typo on line 1002 should be ref_div_max not
fb_div_max.
Anyway I played with the numbers and I found a config that works for me. See
below for all the different combos. Right now
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #27 from Christian König ---
Created attachment 159331
--> https://bugzilla.kernel.org/attachment.cgi?id=159331=edit
Testing patch.
(In reply to kb from comment #26)
> (In reply to Christian König from comment #25)
> > You could
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #26 from kb at spatium.org ---
(In reply to Christian König from comment #25)
> You could try to artificially limit ref_div_max or fb_div_max until you get
> a stable signal once more. Maybe this will yield some more light on the root
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #25 from Christian König ---
(In reply to kb from comment #24)
> Any ideas on this? It's really annoying as I need to keep away from
> upgrading kernel past 3.14. :(
Unfortunately not, cause I don't have any idea what's causing
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #24 from kb at spatium.org ---
Any ideas on this? It's really annoying as I need to keep away from upgrading
kernel past 3.14. :(
Do you think change of graphics card would resolve the issue?
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #23 from kb at spatium.org ---
Created attachment 158001
--> https://bugzilla.kernel.org/attachment.cgi?id=158001=edit
dmesg #3
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #22 from kb at spatium.org ---
I've also added this line
DRM_DEBUG_KMS("in patched branch: %u\n", ref_div_max);
add the end of your patch, i.e. after
ref_div_max = min(ref_div_max, pll->reference_freq /
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #21 from Christian König ---
(In reply to kb from comment #20)
> Hi, unfortunately supplied patch does not fix the issue. Do you need some
> more debug output?
dmesg output generated with drm.debug=0xE on the kernel command line
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #20 from kb at spatium.org ---
Hi, unfortunately supplied patch does not fix the issue. Do you need some more
debug output?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
Christian König changed:
What|Removed |Added
Attachment #155721|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #18 from kb at spatium.org ---
OK, false alarm. I had a wrong kernel. Correct output attached.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #17 from kb at spatium.org ---
Created attachment 156071
--> https://bugzilla.kernel.org/attachment.cgi?id=156071=edit
dmesg round 2 with correct kernel
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #16 from kb at spatium.org ---
I applied the patch but don't see any of the extra msgs in the dmesg. Maybe
it's because i'm running it on the BAD kernel? Can you make a patch against
3.14 (this one doesn't apply cleanly on 3.14)?
--
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #15 from kb at spatium.org ---
Created attachment 156061
--> https://bugzilla.kernel.org/attachment.cgi?id=156061=edit
dmesg 2nd run
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #14 from Christian König ---
Created attachment 155721
--> https://bugzilla.kernel.org/attachment.cgi?id=155721=edit
Add more debugging output.
Please apply the attached patch and provide new dmesg created with
drm.debug=0xE
It
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #13 from Christian K?nig ---
(In reply to kb from comment #12)
> note xrandr is on good kernel, dmesg in on bad
Those outputs should work fine. Going to make a patch for this, but this might
take a while.
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #12 from kb at spatium.org ---
note xrandr is on good kernel, dmesg in on bad
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #11 from kb at spatium.org ---
Created attachment 154681
--> https://bugzilla.kernel.org/attachment.cgi?id=154681=edit
dmesg with drm.debug=0xe on BAD kernel
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #10 from kb at spatium.org ---
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x51
Timestamp: 20519
Subpixel: no subpixels
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #9 from Christian K?nig ---
Please provide the output of "xrandr --verbose" and of dmesg when booted with
"drm.debug=0xe" on the kernel command line.
Thanks,
Christian.
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #8 from kb at spatium.org ---
Also, I've noticed that when X boots, the "good" kernels give this sequence:
1) TV blanks with "No signal" message briefly
2) Desktop shows normally
And the "bad" kernels give:
1) TV blanks with "Mode not
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #7 from kb at spatium.org ---
32167016076f714f0e35e287fbead7de0f1fb179 is the first bad commit
commit 32167016076f714f0e35e287fbead7de0f1fb179
Author: Christian K?nig
Date: Fri Mar 28 18:55:10 2014 +0100
drm/radeon: rework
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #6 from kb at spatium.org ---
I'll have to setup the enviro, it'll take some time. But yeah, I'll do it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #5 from Alex Deucher ---
(In reply to kb from comment #0)
>
> Downgrading to 3.14 seems to remove the issue.
Can you bisect to find out what change caused this regression?
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #4 from kb at spatium.org ---
ok i tried it and surprisingly it does not help. I have flicker, but i don't
get the ELD messages.
Note I also use video=HDMI-A-1:640x480 for the kernel to get a usable
resolution in the text console.
--
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #3 from Alex Deucher ---
Can you try it to be sure to at least narrow down what the problem might be?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=83461
kb at spatium.org changed:
What|Removed |Added
Regression|No |Yes
--- Comment #2 from kb at
https://bugzilla.kernel.org/show_bug.cgi?id=83461
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1
38 matches
Mail list logo
