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 86043] Optimus issue with libdrm 2.4.58
Date: Sun, 01 Mar 2015 23:11:43 +0000	[thread overview]
Message-ID: <bug-86043-502-9quD1Wmfh1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86043-502@http.bugs.freedesktop.org/>


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

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

Emil Velikov <emil.l.velikov@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tvrtko.ursulin@linux.intel.
                   |                            |com

--- Comment #8 from Emil Velikov <emil.l.velikov@gmail.com> ---
Adding the author to the CC list.

Vedran thanks for bisecting this :-)
I'm not sure how this patch can cause such an issue. Either something funny has
happened during bisect or there is another underlying problem.


Summary of the problem so far:

Optimus system running Intel mesa and the proprietary Nvidia drivers. Running
Steam (games) with either bumblebee, optirun or primusrun seems to cause a
crash.

Steam Log:
Game update: AppID 550 "Left 4 Dead 2", ProcID 9399, IP 0.0.0.0:0
...
malloc: unknown:0: assertion botched
free: called with unallocated block argument
last command: (null)
Aborting...Game removed: AppID 550 "Left 4 Dead 2", ProcID 9399

Bisecting libdrm shows ae8edc7544e as the offending commit.


If an Intel dev has a similar machine they can try to reproduce it locally.
Otherwise a back-trace should help at least a bit.

I while back I was able to use gdb with steam. Not sure if it still works
* Close all steam games and the steam client
* $ export GAME_DEBUGGER=gdb
* $ steam

Note I'm not looking into the issue, just trying to get some information for
the Intel devs.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

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

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

  parent reply	other threads:[~2015-03-01 23:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 20:43 [Bug 86043] Optimus issue with libdrm 2.4.58 bugzilla-daemon
2014-11-10  0:38 ` bugzilla-daemon
2014-11-12 20:34 ` bugzilla-daemon
2014-11-15 16:59 ` bugzilla-daemon
2015-01-27 11:30 ` bugzilla-daemon
2015-02-28 11:24 ` bugzilla-daemon
2015-02-28 12:59 ` bugzilla-daemon
2015-03-01 20:29 ` bugzilla-daemon
2015-03-01 23:11 ` bugzilla-daemon [this message]
2015-03-02  9:50 ` bugzilla-daemon
2015-03-02 19:39 ` bugzilla-daemon
2015-03-02 19:40 ` bugzilla-daemon
2015-03-03 10:17 ` bugzilla-daemon
2015-03-03 11:55 ` bugzilla-daemon
2015-03-03 11:59 ` bugzilla-daemon
2019-09-24 17:08 ` 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-86043-502-9quD1Wmfh1@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