https://bugs.freedesktop.org/show_bug.cgi?id=85203
--- Comment #15 from emilio.more...@gmail.com ---
I'm having the same problems in ubuntu 15.04 amd64. I trigger it by playing
Dota 2.This message is the last one shown in the logs.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=90383
--- Comment #3 from Sylvain BERTRAND ---
I can't, segfault happens into a thread with a corrupted stack (gdb says)
But I get some "Mesa: User error: GL_INVALID_OPERATION in function(invalid
call)"
in log, only when asm is on.
(I suspect strongly
On Sun, May 3, 2015 at 12:18 PM, Glenn Kennard wrote:
> On Sat, 02 May 2015 22:16:31 +0200, Ilia Mirkin
> wrote:
>
>> Signed-off-by: Ilia Mirkin
>> ---
>> src/gallium/include/pipe/p_state.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/src/gallium/include/pipe/p_state.h
>> b/src
On Sun, May 3, 2015 at 12:19 PM, Glenn Kennard wrote:
> On Sat, 02 May 2015 22:16:25 +0200, Ilia Mirkin
> wrote:
>
>> Signed-off-by: Ilia Mirkin
>> ---
>> src/gallium/auxiliary/tgsi/tgsi_info.c | 4
>> src/gallium/auxiliary/tgsi/tgsi_strings.c | 4 +++-
>> src/gallium/auxiliary/tgsi/t
https://bugs.freedesktop.org/show_bug.cgi?id=90383
--- Comment #4 from Sylvain BERTRAND ---
I did excise the glapi/mapi x86 assembly code. Working and no more
"Mesa: User error: GL_INVALID_OPERATION in function(invalid call)".
This is where bad things are happening.
This bug seems to be not rela
This avoids future addition to PIPE_PRIM_ from causing regressions
on r600g.
Signed-off-by: Dave Airlie
---
src/gallium/drivers/r600/r600_state_common.c | 31 ++--
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_state_common.c
Reviewed-by: Marek Olšák
Marek
On Sun, May 10, 2015 at 10:25 PM, Dave Airlie wrote:
> This avoids future addition to PIPE_PRIM_ from causing regressions
> on r600g.
>
> Signed-off-by: Dave Airlie
> ---
> src/gallium/drivers/r600/r600_state_common.c | 31
> ++--
> 1 fi
https://bugs.freedesktop.org/show_bug.cgi?id=85203
--- Comment #16 from emilio.more...@gmail.com ---
For future reference:
I disabled vsync and lowered the game settings for Dota2. I was able to play
for 2 hours without problems. I haven't tested it more than that.
--
You are receiving this mail
On Fri, 8 May 2015, Emil Velikov wrote:
Shouldn't we authenticate with the correct gpu or master/render node ?
This implementation will auth with GPU1, and then use GPU2 which seems
a bit odd. I might be missing something ?
The original patches did do differently: when GPU1 was discovered to
Tested-by: Pierre Moreau
- Mail original -
> Commit 44673512a84 enabled support for saturating fmul. However
> experimentally this does not seem to work on the older chips.
> Restrict
> the feature to G200 (NVA0) and later.
>
> Reported-by: Pierre Moreau
> Bugzilla: https://bugs.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=90383
--- Comment #5 from Tapani Pälli ---
It looks to me you are trying to do a 32bit build (?)
what is included in $steam_i686_gnu_target variable?
You should give following flags to make sure things go ok (see
docs/autoconf.html):
"./configure CC
11 matches
Mail list logo
