Bug 1369437 - Test case failure: Screen - Resolution after no Screen Boot
Summary: Test case failure: Screen - Resolution after no Screen Boot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-drv-nouveau
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ben Skeggs
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-23 12:21 UTC by Tomas Hudziec
Modified: 2018-08-29 16:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-29 16:22:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Tomas Hudziec 2016-08-23 12:21:45 UTC
Filed from caserun https://tcms.engineering.redhat.com/run/288296/#caserun_13122785

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.11-3.el7.x86_64

Steps to Reproduce: 
 1. reboot machine
 2. disconnect monitor while machine is shutting down
 3. wait until machine is rebooted to GDM
 4. connect display back to the machine

Actual results: 
Screen is black, only mouse cursor appears. It is possible to switch to virtual console, fbset shows resolution 1024x768 (should be 1920x1080 in my case). Restart of GDM service lead to showing up of logging screen.

Expected results:
Screen should be correctly powered on with native resolution.

Graphics card: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa]

Comment 1 Tomas Hudziec 2016-08-23 12:32:06 UTC
When powering off, screen with circle progress bar is of resolution 1024x768.

Comment 3 Tomas Hudziec 2016-08-30 09:05:41 UTC
Occurs also with NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] with xorg-x11-drv-nouveau-1.0.11-4.el7.x86_64.

Comment 5 Tomas Pelka 2017-06-19 13:17:44 UTC
I can still reproduce with 

kernel-3.10.0-681.el7.x86_64
xorg-x11-drv-nouveau-1.0.13-2.el7.x86_64
xorg-x11-server-Xorg-1.19.3-7.el7.x86_64

Comment 6 Ben Skeggs 2017-06-19 22:15:21 UTC
(In reply to Tomas Pelka from comment #5)
> I can still reproduce with 
> 
> kernel-3.10.0-681.el7.x86_64
> xorg-x11-drv-nouveau-1.0.13-2.el7.x86_64
> xorg-x11-server-Xorg-1.19.3-7.el7.x86_64

What do you see in the kernel log after attempting to reconnect the display?

The 1024x768 resolution of the console is the expected behaviour (the console fb can't be resized, on any driver, so it's determined based on connected displays at module load time), but inside gdm, it should indeed be native resolution.

Comment 7 Tomas Pelka 2017-06-20 08:52:22 UTC
nothing on kernel site (journalctl -k -f)

xorg.log on plugging:
[   135.347] (II) modeset(0): EDID vendor "ACR", prod id 314
[   135.348] (II) modeset(0): Using hsync ranges from config file
[   135.348] (II) modeset(0): Using vrefresh ranges from config file
[   135.348] (II) modeset(0): Printing DDC gathered Modelines:
[   135.348] (II) modeset(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[   135.348] (II) modeset(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   135.348] (II) modeset(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[   135.348] (II) modeset(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[   135.348] (II) modeset(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   135.348] (II) modeset(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   135.348] (II) modeset(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[   135.348] (II) modeset(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   135.348] (II) modeset(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   135.348] (II) modeset(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[   135.348] (II) modeset(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   135.348] (II) modeset(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[   135.348] (II) modeset(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[   135.348] (II) modeset(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync +vsync (44.8 kHz e)
[   135.348] (II) modeset(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)

Seems EDID tried to do something, but all I can see on monitor is blinking cursor.

Comment 8 Tomas Pelka 2017-06-20 09:42:33 UTC
also issue with 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1)

Comment 9 Tomas Pelka 2017-06-20 16:41:21 UTC
GM206 too

Comment 10 Tomas Pelka 2017-06-21 07:34:47 UTC
GM107 too

Comment 11 Tomas Hudziec 2018-08-29 16:22:43 UTC
Not reproducible any more on RHEL 7.6 with packages:
kernel-3.10.0-940.el7.x86_64
xorg-x11-drv-nouveau-1.0.15-1.el7.x86_64
xorg-x11-server-Xorg-1.20.1-1.el7.x86_64

After attaching screen the GDM is shown in correct resolution.
Tested with GM107, GM206 and NVS 510.


Note You need to log in before you can comment on or make changes to this bug.