All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56788] [nv96] Dota2 (wine) consistently crashes with "WARNING: out of code space, evicting all shaders"
Date: Mon, 05 Nov 2012 22:53:46 +0000	[thread overview]
Message-ID: <bug-56788-502-R0y6ifIQQP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56788-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Emil Velikov <emil.l.velikov@gmail.com> ---
Created attachment 69590
  --> https://bugs.freedesktop.org/attachment.cgi?id=69590&action=edit
Wine backtrace

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

[-- Attachment #1.2: Type: text/html, Size: 1314 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

  reply	other threads:[~2012-11-05 22:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 22:50 [Bug 56788] New: [nv96] Dota2 (wine) consistently crashes with "WARNING: out of code space, evicting all shaders" bugzilla-daemon
2012-11-05 22:53 ` bugzilla-daemon [this message]
2012-11-05 22:54 ` [Bug 56788] " bugzilla-daemon
     [not found] <bug-56788-8800@http.bugs.freedesktop.org/>
     [not found] ` <bug-56788-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-11-05 22:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-05 23:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-10 14:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-10 21:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-16 15:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-56788-502-R0y6ifIQQP@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.