Bug 703460

Summary: [rv250_kms] boot time LVDS corruption
Product: [Fedora] Fedora Reporter: Robert de Rooy <rderooy>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: jglisse, mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: [cat:modesetting]
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 14:56:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg output on T41 with debug
none
Xorg log none

Description Robert de Rooy 2011-05-10 11:56:26 UTC 
Description of problem:
ThinkPad T41 with Radeon rv250

Booting F15 Beta with all updates applied causes plymouth graphical boot to get corrupted. First the LVDS display slowly turns white, then it gives a picture where plymouth is horizontally shifted.
When X starts everything is sorted out and the display corruption is gone.

If an external display is attached during boot, the external display switches off and comes back on later when X is started.

I am wondering if this has anything to do with the following;

A few fedora release or two ago there was a change made such that this ThinkPad no longer booted using plymouth graphical mode, but rather plymouth high-res text mode. The reason for this had to do with the limited amount of graphical memory (32MB). Although this change was never consistent, because while it did this when booting with only the LVDS attached, booting with both LVDS and an external display caused plymouth to again boot in graphical mode.

Regardless of the above, with F14 I did not experience this boot-time LVDS corruption either when booting with LVDS only or booting with LVDS and an external display (VGA or DVI).

Version-Release number of selected component (if applicable):
kernel-2.6.38.5-24.fc15.i686
xorg-x11-drv-ati-6.14.1

How reproducible:
Every boot

Steps to Reproduce:
1. Boot F15 Beta on rv250 equipped machine
2.
3.
  
Actual results:
Corrupted display during boot

Expected results:
no display corruption

Additional info:
Comment 1 Adam Jackson 2011-05-10 15:12:43 UTC 
Not really sure why you filed a Radeon bug against the Intel driver...
Comment 2 Matěj Cepl 2011-05-10 20:50:38 UTC 
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 3 Robert de Rooy 2011-05-12 07:46:18 UTC 
Created attachment 498456 [details]
dmesg output on T41 with debug
Comment 4 Robert de Rooy 2011-05-12 07:46:47 UTC 
Created attachment 498457 [details]
Xorg log
Comment 5 Robert de Rooy 2011-05-12 07:51:31 UTC 
No xorg.conf exists. In addition it seems that since an update on May 9th that syslog is no longer updating /var/log/messages. Not sure what is going on there.

I am booting with radeon.agpmode=1 to work around a resume problem (bug 531825), but booting without that and letting it go to the default AGP 4X makes no difference to the corruption at boot.
Comment 6 Robert de Rooy 2011-11-23 17:48:28 UTC 
Still the same with F16 kernel-3.1.1-2.fc16. Regression from F14.
Comment 7 Fedora End Of Life 2013-01-16 13:59:56 UTC 
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 8 Fedora End Of Life 2013-02-13 14:56:56 UTC 
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.