Bug 1320130

Summary: Test case failure: Panning with xrandr
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Hudziec <thudziec>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8CC: lyude, rclark, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:53:44 UTC Type: Bug
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
xorg log none

Description Tomas Hudziec 2016-03-22 11:35:42 UTC 
Created attachment 1138998 [details]
xorg log

Filed from caserun https://tcms.engineering.redhat.com/run/273683

Version-Release number of selected component (if applicable):
RHEL-6.8-20160215.n.0
xorg-x11-drv-ati-7.6.1-1.el6.x86_64

Steps to Reproduce: 
Get your display highest supported resolution, use xrandr for example (is is
the first resolution in the list, 1920x1080 in my case).

 1. Run xrandr and set higher resolution that you have supported

    xrandr --output DVI-1 --panning 6000x6000

Note: replace "DVI-1" with real name of your output interface.
With higher resolutions (e.g. 8000x8000) behaves similarly.

Actual results: 
Xorg freezes. Part of Xorg.0.log:
[   647.013] (II) RADEON(0): Allocate new frame buffer 6000x6000 stride 6016
[   647.035] (EE) RADEON(0): failed to set mode: Invalid argument(II) RADEON(0): VRAM usage limit set to 333244K
[   647.035] (EE) RADEON(0): failed to set mode: Invalid argument(EE) RADEON(0): failed to set mode: Invalid argumentAUDIT: Tue Mar 22 11:53:11 2016: 2704: client 34 disconnected
[   647.761] AUDIT: Tue Mar 22 11:53:11 2016: 2704: client 37 connected from local host ( uid=500 gid=500 pid=2994 )
  Auth name: MIT-MAGIC-COOKIE-1 ID: 1220
[   647.761] AUDIT: Tue Mar 22 11:53:11 2016: 2704: client 37 disconnected
[   655.687] (EE) RADEON(0): failed to set mode: Invalid argument(EE) RADEON(0): failed to set mode: Invalid argument(II) AIGLX: Suspending AIGLX clients for VT switch

Expected results:
Make sure the screen is panned. No crashes/errors at display should appear.

Graphics card:
Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] [1002:68f2]
Comment 2 Tomas Pelka 2016-03-22 12:06:01 UTC 
Not sure if this is clone of bz1318352.

In bz1318352 there was an issue in intel driver, but this is ati maybe something similar but in other driver.
Comment 3 Tomas Pelka 2016-03-22 20:37:42 UTC 
bz1318352 fix is actually in Xorg-server so it is not hw/driver dependent. If devels are right it will fix this issue too.
Comment 4 Lyude 2016-03-23 16:42:41 UTC 
(In reply to Tomas Pelka from comment #3)
> bz1318352 fix is actually in Xorg-server so it is not hw/driver dependent.
> If devels are right it will fix this issue too.

the fix for that is in xorg-x11-drv-intel, not the X server, so this is going to need a separate fix
Comment 5 Rob Clark 2016-03-23 18:01:52 UTC 
(In reply to Tomas Hudziec from comment #0)
> Steps to Reproduce: 
> Get your display highest supported resolution, use xrandr for example (is is
> the first resolution in the list, 1920x1080 in my case).
> 
>  1. Run xrandr and set higher resolution that you have supported
> 
>     xrandr --output DVI-1 --panning 6000x6000
> 

Just fyi, a 7920x7080 scanout buffer translates into nearly 215MiB, so I wouldn't really expect this to work (esp. since this particular card appears to have only 512MiB VRAM).

Probably the DDX should fail more gracefully, but I'm not sure I'd actually expect this test to work in many places.
Comment 6 Tomas Hudziec 2016-03-24 16:31:38 UTC 
(In reply to Rob Clark from comment #5)
> (In reply to Tomas Hudziec from comment #0)
> > Steps to Reproduce: 
> > Get your display highest supported resolution, use xrandr for example (is is
> > the first resolution in the list, 1920x1080 in my case).
> > 
> >  1. Run xrandr and set higher resolution that you have supported
> > 
> >     xrandr --output DVI-1 --panning 6000x6000
> > 
> 
> Just fyi, a 7920x7080 scanout buffer translates into nearly 215MiB, so I
> wouldn't really expect this to work (esp. since this particular card appears
> to have only 512MiB VRAM).
> 
> Probably the DDX should fail more gracefully, but I'm not sure I'd actually
> expect this test to work in many places.

Yes, I don't expect that high resolution to work, it was just "hard" testing. However, it shouldn't cause xorg freeze, xrandr should print error message and shutdown itself.
Comment 8 Jan Kurik 2017-12-06 10:53:44 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/