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 1803811 - Mesa driver exits the application when trying to launch 2nd screen with 'i965: Failed to submit batchbuffer: Invalid argument' [rhel-7.9.z]
Summary: Mesa driver exits the application when trying to launch 2nd screen with 'i965...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mesa
Version: 7.7
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: 7.9
Assignee: Michel Dänzer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1835682 1843381
TreeView+ depends on / blocked
 
Reported: 2020-02-17 13:53 UTC by Vikramsingh Patil
Modified: 2023-10-06 19:13 UTC (History)
11 users (show)

Fixed In Version: mesa-18.3.4-12.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1835682 (view as bug list)
Environment:
Last Closed: 2020-11-10 13:16:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Working scenario (954.13 KB, image/png)
2020-02-17 13:56 UTC, Vikramsingh Patil 		no flags Details
Actual Result (934.42 KB, image/png)
2020-02-17 13:58 UTC, Vikramsingh Patil 		no flags Details
strace from both client and server (202.43 KB, application/gzip)
2020-02-17 14:01 UTC, Vikramsingh Patil 		no flags Details
Issue without applying the patch (757.49 KB, image/png)
2020-03-11 10:19 UTC, Vikramsingh Patil 		no flags Details
Issue after applying the patch (815.75 KB, image/png)
2020-03-11 10:20 UTC, Vikramsingh Patil 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:5046 0 None None None 2020-11-10 13:16:27 UTC
freedesktop.org Gitlab mesa/mesa/issues/1373 0 None None None 2020-03-03 10:49:55 UTC

Internal Links: 1843381

Description Vikramsingh Patil 2020-02-17 13:53:40 UTC 
Description of problem:

When trying to launch application having 2 screen, The application exits with error 'i965: Failed to submit batchbuffer: Invalid argument'

Version-Release number of selected component (if applicable):

xorg-x11-drv-intel-2.99.917-28.el7.x86_64
mesa-dri-drivers-18.0.5-3.el7.x86_64

How reproducible:

Hardwre 
- hardware: i965 GPU chipset
- software: RHEL 7.7 + mesa-dri-drivers + mesa-demo

1) Install the mesa-demos.x86_64 (comes from RHEL optional repository)

2) Run '/usr/lib64/mesa/manywin 2'

Steps to Reproduce:
1. Install the mesa-demos.x86_64 (comes from RHEL optional repository)
2. Run '/usr/lib64/mesa/manywin 2'
3.

Actual results:

It should launch 2 screen

Expected results:

Gives error 'i965: Failed to submit batchbuffer: Invalid argument'

Additional info:
Comment 2 Vikramsingh Patil 2020-02-17 13:56:38 UTC 
Created attachment 1663521 [details]
Working scenario

Above image shows the working scenario for the bug
Comment 3 Vikramsingh Patil 2020-02-17 13:58:15 UTC 
Created attachment 1663522 [details]
Actual Result

It is the Actual Result customer is getting
Comment 4 Vikramsingh Patil 2020-02-17 14:01:11 UTC 
Created attachment 1663525 [details]
strace from both client and server
Comment 5 Adam Jackson 2020-02-19 18:57:22 UTC 
This appears to have been already reported (though neglected) upstream:

https://gitlab.freedesktop.org/mesa/mesa/issues/1373

I can reproduce this locally on Fedora 31 but do not yet have an estimate
for time to fix.
Comment 7 Michel Dänzer 2020-03-03 10:49:56 UTC 
Reassigning to mesa per the linked upstream issue.
Comment 11 Adam Jackson 2020-03-09 15:13:49 UTC 
I've backported a few stable / pending fixes from upstream that should
address this issue here:

https://people.redhat.com/ajackson/1803811/

Please test and report any issues you encounter.
Comment 13 Vikramsingh Patil 2020-03-11 10:19:08 UTC 
Created attachment 1669221 [details]
Issue without applying the patch
Comment 14 Vikramsingh Patil 2020-03-11 10:20:28 UTC 
Created attachment 1669222 [details]
Issue after applying the patch
Comment 15 Adam Jackson 2020-03-12 15:50:37 UTC 
Well that's unexpected. I can reproduce this failure locally, will post another test
build when I have a fix.
Comment 17 Adam Jackson 2020-03-13 19:39:39 UTC 
I've posted a new test build to:

https://people.redhat.com/ajackson/1803811

The issue (which the upstream merge request looks like it fixes) has to do with
sharing resources between different connections to the same display. There are
some subtle resource lifetime issues that can arise from that and I haven't been
able to exhaustively test them, so while the packages above fix the manywin demo
for me, that demo is quite simplistic in its shared resource usage. If you find
additional issues with the real application with this build, please let me know.
Comment 42 errata-xmlrpc 2020-11-10 13:16:19 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (mesa bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5046
Comment 43 Red Hat Bugzilla 2023-09-14 05:52:45 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.