From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 102008] DRI_PRIME causes X Error of failed request: BadAlloc (insufficient resources for operation) Date: Wed, 02 Aug 2017 21:04:37 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1554205508==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CDFFE89D83 for ; Wed, 2 Aug 2017 21:04:36 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1554205508== Content-Type: multipart/alternative; boundary="15017078760.1f2B1F785.11839"; charset="UTF-8" --15017078760.1f2B1F785.11839 Date: Wed, 2 Aug 2017 21:04:36 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D102008 --- Comment #2 from bartos.petr@gmail.com --- So I have some partial results. First problem I've encoutered is that I had to use patch from https://bugs.freedesktop.org/show_bug.cgi?id=3D101774 in order to be able to build mesa between 7250cbafb90271579a1d07160498e902996cbc97 and 5ffe0c9e1be0257de1943135244419cbc86a6d84 so I hope it does not affect these results. Second problem I found is that problem is connected with using modesetting = DDX drivers, and between working and non-working commits is some problem causing segfault with modesetting drivers (X do not start). So I have tested not on= ly particular commits, but also DDX driver combinations: intel - IGPU, DRI3, SNA accel radeon - DGPU, DRI3, glamor accel modesetting - both, default settings So far I managed to find this (I have not finished bisecting yet, so these commits are ones I've found so far): f33d8af7aa354d00808f8bfd55028c396c706635 intel, radeon - OK intel, modesetting - OK modesetting, radeon - ERROR modesetting, modesetting - ERROR 81fb1547772d42c527318837d4207ecdb6899e5d intel, radeon - OK intel, modesetting - SEGFAULT modesetting, radeon - SEGFAULT modesetting, modesetting - SEGFAULT 3645268748c44825ce8d37bf03f684731eb2652a intel, radeon - OK intel, modesetting - SEGFAULT modesetting, radeon - SEGFAULT modesetting, modesetting - SEGFAULT 84ed8b67c56b323cd834d463151e1a3c0430c53e intel, radeon - OK intel, modesetting - OK modesetting, radeon - OK modesetting, modesetting - OK So it seems between somewhere between 84ed8b67c56b323cd834d463151e1a3c0430c= 53e and f33d8af7aa354d00808f8bfd55028c396c706635 (https://cgit.freedesktop.org/mesa/mesa/log/?qt=3Drange&q=3D84ed8b67c56b323= cd834d463151e1a3c0430c53e..f33d8af7aa354d00808f8bfd55028c396c706635) modesetting driver started to segfault which was fixed, but this fix probab= ly also caused problem which I have reported. It also seems there is no problem when using only intel+radeon DDX drivers. --=20 You are receiving this mail because: You are the assignee for the bug.= --15017078760.1f2B1F785.11839 Date: Wed, 2 Aug 2017 21:04:36 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 2 on bug 10200= 8 from bartos.petr&= #64;gmail.com 
So I have some partial results.

First problem I've encoutered is that I had to use patch from
https://bugs.freedesktop.org/show_bug.=
cgi?id=3D101774 in order to be able to
build mesa between 7250cbafb90271579a1d07160498e902996cbc97 and
5ffe0c9e1be0257de1943135244419cbc86a6d84 so I hope it does not affect these
results.

Second problem I found is that problem is connected with using modesetting =
DDX
drivers, and between working and non-working commits is some problem causing
segfault with modesetting drivers (X do not start). So I have tested not on=
ly
particular commits, but also DDX driver combinations:

intel - IGPU, DRI3, SNA accel
radeon - DGPU, DRI3, glamor accel
modesetting - both, default settings

So far I managed to find this (I have not finished bisecting yet, so these
commits are ones I've found so far):

f33d8af7aa354d00808f8bfd55028c396c706635
    intel, radeon - OK
    intel, modesetting - OK
    modesetting, radeon - ERROR
    modesetting, modesetting - ERROR

81fb1547772d42c527318837d4207ecdb6899e5d
    intel, radeon - OK
    intel, modesetting - SEGFAULT
    modesetting, radeon - SEGFAULT
    modesetting, modesetting - SEGFAULT

3645268748c44825ce8d37bf03f684731eb2652a
    intel, radeon - OK
    intel, modesetting - SEGFAULT
    modesetting, radeon - SEGFAULT
    modesetting, modesetting - SEGFAULT

84ed8b67c56b323cd834d463151e1a3c0430c53e
    intel, radeon - OK
    intel, modesetting - OK
    modesetting, radeon - OK
    modesetting, modesetting - OK

So it seems between somewhere between 84ed8b67c56b323cd834d463151e1a3c0430c=
53e
and f33d8af7aa354d00808f8bfd55028c396c706635
(https://cgit.freedesktop.org/mesa/mesa/log/?qt=3Drange&q=3D84e=
d8b67c56b323cd834d463151e1a3c0430c53e..f33d8af7aa354d00808f8bfd55028c396c70=
6635)
modesetting driver started to segfault which was fixed, but this fix probab=
ly
also caused problem which I have reported.

It also seems there is no problem when using only intel+radeon DDX drivers.=

You are receiving this mail because:
  • You are the assignee for the bug.
= --15017078760.1f2B1F785.11839-- --===============1554205508== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1554205508==--