Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionVasiliy Sharapov
2013-11-24 10:34:15 UTC
Filed from caserun https://tcms.engineering.redhat.com/run/100139/#caserun_3856463
Version-Release number of selected component (if applicable):
Build : RHEL-7.0-20131111.1
xorg-x11-server-Xorg-1.14.99.901-5.20131101.el7.x86_64
xorg-x11-drv-ati-7.2.0-6.20131023gitf1dc677.el7.x86_64
kernel-3.10.0-48.el7.x86_64
Steps to Reproduce:
Get your display highest supported resolution, use xrandr for example (it is
the first resolution in the list, 1680x1050 in my case).
1. Run xrandr and set higher resolution that you have supported
xrandr --output LVDS --panning 1600x1200
Note: replace "LVDS" with real name of your output interface.
Actual results:
"""
[test@dhcp46-252 Desktop]$ xrandr --output default --panning 1600x1200
xrandr: Failed to get size of gamma for output default
xrandr: screen cannot be larger than 1680x1050 (desired size 1680x1200)
""" Panning didn't turn on but I tried setting it to 0 anyway: """
[test@dhcp46-252 Desktop]$ xrandr --output default --panning 0x0*0+0
xrandr: Failed to get size of gamma for output default
X Error of failed request: BadRRCrtc (invalid Crtc parameter)
Major opcode of failed request: 139 (RANDR)
Minor opcode of failed request: 29 (RRSetPanning)
Crtc id in failed request: 0x17c
Serial number of failed request: 21
Current serial number in output stream: 21
[test@dhcp46-252 Desktop]$
"""
Expected results:
Make sure the screen is panned and you can tavel in panned space. No crashes/
errors at display should appear.
This need to be retested but here i can not reproduce with :
linux-firmware-20140102-0.2.git52d77db.el7.noarch
kernel-3.10.0-89
mesa-dri-drivers-9.2.5
xorg-x11-drv-ati-7.2.0-8.20140113git3213df1
xorg-x11-glamor-0.5.1-4.20140115gitfb4d046c
Note that bonaire GPU are still likely to lockup you will have something like :
radeon 0000:01:00.0: GPU lockup
In the kernel log. When GPU lockup screen is likely to go black.