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.
Bug 1886159 - (EE) modeset(0): failed to set mode: Invalid argument with Intel GM965/GL960
Summary: (EE) modeset(0): failed to set mode: Invalid argument with Intel GM965/GL960
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-server
Version: 7.8
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-07 18:56 UTC by agents
Modified: 2022-04-14 14:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-07 07:27:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Xorg log showing the failure of setmode(0) (53.30 KB, text/plain)
2020-10-07 18:56 UTC, agents 		no flags Details
View All

Description agents 2020-10-07 18:56:23 UTC 
Created attachment 1719823 [details]
Xorg log showing the failure of setmode(0)

Description of problem:
ThinkPad laptop in docking station running CentOS 7.8 fails to initialize dual-monitor setup. Laptop works fine when not in docking station. Docking station contains a second graphics card with a Radeon RV516 chip which seemingly does not initialize correctly, specifically Xorg.0.log (attached) shows that the modeset(0) fails when setting a framebuffer.

Version-Release number of selected component (if applicable):
Latest version 19.0.1-3 as well as the previous version 18. The version before that worked fine.

How reproducible:
Every time computer boots.


Steps to Reproduce:
1. Boot computer in docking station.
2.
3.

Actual results:
The display stops at "Started Light Display Manager", the usual CentOS background is not shown. I can seemingly log in blindly and the startup apps load but since there is no graphical display it is not possible to do anything.


Expected results:
Switch to graphical display and login window.


Additional info:
lspci output showing both the ATI chip in the computer and the RV516 chip on the second graphics card in the docking station:

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series]
0d:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] (Secondary)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)
Comment 2 Michel Dänzer 2020-10-08 09:42:26 UTC 
"modeset(0)" in the log file means it's using the modesetting driver from xorg-x11-server-Xorg, not the radeon driver from xorg-x11-drv-ati. Does the problem also occur with the latter? (From the log file, it looks like the former may be explicitly selected in a xorg.conf.d/* file)
Comment 3 agents 2020-10-08 14:42:10 UTC 
How would I change this?
Comment 4 agents 2020-10-09 10:38:14 UTC 
If I understand you correctly, you believe the bug is not in the ati driver but in the xorg-x11-server-xorg driver? If I revert to an earlier version, it should work again?
Comment 5 Michel Dänzer 2020-10-09 15:43:54 UTC 
(In reply to agents from comment #4)
> If I understand you correctly, you believe the bug is not in the ati driver
> but in the xorg-x11-server-xorg driver?

Yes, and also I realized the error is about the integrated Intel GPU, not the AMD one. Reassigning accordingly.

> If I revert to an earlier version, it should work again?

In theory, yes. Mesa or the kernel might also affect it though.
Comment 6 agents 2020-10-09 18:32:37 UTC 
Now I do not follow - why do you think this is related to the integrated, primary controller? The laptop seems to work fine when not in the docking station and thus using the integrated controller. It is in the docking station with the secondary graphics controller it fails.

How can I help you find the bug?
Comment 7 Michel Dänzer 2020-10-12 09:30:30 UTC 
(In reply to agents from comment #6)
> Now I do not follow - why do you think this is related to the integrated,
> primary controller?

Because the error is from the modesetting driver, which is driving the integrated GPU.
Comment 11 RHEL Program Management 2022-04-07 07:27:27 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 12 agents 2022-04-14 14:16:18 UTC 
I reported this bug 18 months ago. I am quite underwhelmed by your response time and response which do not reflect well on Red Hat.
Note You need to log in before you can comment on or make changes to this bug.