dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-102008-502-vZmaUSqZ2T@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102008-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2183 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=102008

--- 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=101774 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 only
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 84ed8b67c56b323cd834d463151e1a3c0430c53e
and f33d8af7aa354d00808f8bfd55028c396c706635
(https://cgit.freedesktop.org/mesa/mesa/log/?qt=range&q=84ed8b67c56b323cd834d463151e1a3c0430c53e..f33d8af7aa354d00808f8bfd55028c396c706635)
modesetting driver started to segfault which was fixed, but this fix probably
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.

[-- Attachment #1.2: Type: text/html, Size: 3415 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-08-02 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 21:20 [Bug 102008] DRI_PRIME causes X Error of failed request: BadAlloc (insufficient resources for operation) bugzilla-daemon
2017-08-02  1:42 ` bugzilla-daemon
2017-08-02 21:04 ` bugzilla-daemon [this message]
2017-08-03  0:25 ` bugzilla-daemon
2017-08-03  3:26 ` bugzilla-daemon
2017-08-04 13:52 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102008-502-vZmaUSqZ2T@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox