Bug 58345

Summary: regression in radeon driver for HD6570
Product: xorg Reporter: Vladislav <ccvs>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: high    
Version: 7.7 (2012.06)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log
none
dmesg none

Description Vladislav 2012-12-15 19:30:20 UTC
Created attachment 71563 [details]
Xorg.0.log

in may 2012 i've posted a bug

https://bugs.freedesktop.org/show_bug.cgi?id=49792

This bug still exists in my case, but some other problems has appeared:

Now, it is impossible to normalize driver behaviour by several switching to console and back. 

Now, situation is so:

1) radeon kernel module loads
2) framebuffer console is noisy.

and there appear new problem:

3) after starting Xorg, i see noisy screen without possibility to 
switch to console. 
4) after several seconds the screen is turning off.
Comment 1 Vladislav 2012-12-15 19:31:24 UTC
Created attachment 71564 [details]
dmesg
Comment 2 Alex Deucher 2012-12-15 22:33:50 UTC
Can you bisect?
Comment 3 Vladislav 2012-12-15 23:43:16 UTC
Sorry, bisect what?
Comment 5 Alex Deucher 2012-12-16 14:52:14 UTC
*** Bug 58352 has been marked as a duplicate of this bug. ***
Comment 6 Alex Deucher 2012-12-16 14:52:52 UTC
Bisect the kernel to see what commit caused the regression.
Comment 7 Vladislav 2013-02-07 16:25:45 UTC
it looks, that 

kernel commit 95f5a3acfaf6f5672420398e01ca32220b36bb90

creates problem
Comment 8 Martin Peres 2019-11-19 07:39:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/55.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.