[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #38 from Gabriele Svelto --- Yes, the emulator seems to be calling GL commands from multiple threads, or at least the traces I got seemed to have different thread identifiers for different commands. --

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #39 from Ilia Mirkin --- (In reply to Gabriele Svelto from comment #38) > Yes, the emulator seems to be calling GL commands from multiple threads, or > at least the traces I got seemed to have different thread

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #35 from Gabriele Svelto --- I've updated mesa again and running from the current master I encounter the segfault again. This time though this is the only message that pops up in the kernel log: [

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #37 from Ilia Mirkin --- (In reply to Gabriele Svelto from comment #35) > I've updated mesa again and running from the current master I encounter the > segfault again. This time though this is the only message

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #36 from Emil Velikov --- (In reply to Gabriele Svelto from comment #35) > I've updated mesa again and running from the current master I encounter the > segfault again. This time though this is the only

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #33 from Gabriele Svelto --- OK, I've just tried to reproduce the bug with the latest master build and while I haven't managed to crash the emulator yet I've found this output. This was in the kernel log:

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #32 from Gabriele Svelto --- I'll try rebuilding mesa using the mesa- packages which should get me the current master and will report back ASAP. -- You are receiving this mail because: You are the QA

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #34 from Gabriele Svelto --- I've been running the emulator for a while and it hasn't crashed yet but I've found yet more warning/error messages in my kernel log and they seem related to it: [ 3053.470749]

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #31 from Ilia Mirkin --- I've pushed out a couple of changes which might improve the situation. Please give your software a shot and see if it stops crashing. This should definitely resolve the glium issues...

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #28 from Jim Blandy --- (In reply to Jim Blandy from comment #26) > Thanks for looking into this! I still get segfaults. The entry in > extension_table for GL_ARB_direct_state_access is: > >{

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #26 from Jim Blandy --- (In reply to Ilia Mirkin from comment #24) > Hmmm... looks like rust isn't quite ready for prime-time -- there is no > 'cargo' gentoo ebuild. (Apparently cargo can't be built hermetically?)

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #27 from Ilia Mirkin --- Created attachment 119323 --> https://bugs.freedesktop.org/attachment.cgi?id=119323=edit deal with bind == 0 Oh blast, you're right. Can't disable GL_ARB_direct_state_access, since

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #30 from Ilia Mirkin --- (In reply to Jim Blandy from comment #29) > (In reply to Ilia Mirkin from comment #27) > > Created attachment 119323 [details] > > deal with bind == 0 > > > > Oh blast, you're right.

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #29 from Jim Blandy --- (In reply to Ilia Mirkin from comment #27) > Created attachment 119323 [details] > deal with bind == 0 > > Oh blast, you're right. Can't disable GL_ARB_direct_state_access, since it's >

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #23 from Ilia Mirkin --- (In reply to Jim Blandy from comment #21) > I have no idea what this code is supposed to be doing, but here's what I can > infer: > > The call to pushbuf_kref crashes because the

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #21 from Jim Blandy --- I have no idea what this code is supposed to be doing, but here's what I can infer: The call to pushbuf_kref crashes because the `struct nouveau_bo *bo` argument is NULL, and cli_push_get

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #22 from Jim Blandy --- Steps to reproduce: 1) Install Rust from www.rust-lang.org, which provides the 'cargo' command. 2) git clone g...@github.com:tomaka/glium.git 3) cd glium 4) cargo build 5) cargo build

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #20 from Jim Blandy --- I'm able to reproduce a crash with a very similar stack on Fedora 22, using the glium Rust OpenGL bindings: https://github.com/tomaka/glium Here's the stack trace I get: Program received

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #24 from Ilia Mirkin --- Hmmm... looks like rust isn't quite ready for prime-time -- there is no 'cargo' gentoo ebuild. (Apparently cargo can't be built hermetically?) So I can't repro. I'm a little worried

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #25 from Ilia Mirkin --- I believe this is now possible with ARB_direct_state_access. While I add support for this and add some asserts so that this doesn't happen in the future, would either of you mind

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #18 from Gabriele Svelto --- Quick update, I'm on mesa 11.0.4 now and the issue is still present but it manifests itself differently: when I hit the issue I can still see the error messages being dumped

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #19 from Gabriele Svelto --- Disregards my previous comment, I've just hit another segfault. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #17 from Gabriele Svelto --- Thanks for the tip. From the comments in that bug I should be able to test that patch in the 4.3+ kernels. I'm rolling my own build so I can try that out as soon as I have some

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #16 from Ilia Mirkin --- In your kernel log I see [30903.432610] nouveau E[steam[21937]] fail set_domain [30903.432614] nouveau E[steam[21937]] validating bo list [30903.432618] nouveau E[steam[21937]]

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #15 from Gabriele Svelto --- (In reply to Ilia Mirkin from comment #14) > NV94 is a tesla. Tesla is G80:MCP89 (aka nv50 family). Right, my bad, I've got confused with the actual Tesla card. > If you can

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #14 from Ilia Mirkin --- (In reply to Gabriele Svelto from comment #13) > Thanks for the info. I can reproduce this bug fairly easily so I can help > diagnosing it, would a trace of the OpenGL calls help? This

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 Gabriele Svelto changed: What|Removed |Added Version|unspecified |11.0 --

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #12 from Ilia Mirkin --- [35345.800105] nouveau E[ PFIFO][:01:00.0] DMA_PUSHER - ch 6 [emulator-x86[1371]] get 0x00200f9878 put 0x00200f98d0 ib_get 0x00ed ib_put 0x00f6 state 0x8000 (err:

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #13 from Gabriele Svelto --- Thanks for the info. I can reproduce this bug fairly easily so I can help diagnosing it, would a trace of the OpenGL calls help? This often happens after only a few seconds so

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 Gabriele Svelto changed: What|Removed |Added Attachment #118839|0 |1

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #6 from Pierre Moreau --- FYI, latest Mesa release is 11.0.3. 10.4 was branched out in December 2014 (though it did receive some additional fixes up to March 2015), so you might want to try at least 10.6.x, or

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #5 from Gabriele Svelto --- Still repros on mesa 10.4.6 and libdrm 2.4.65. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #4 from Gabriele Svelto --- I've started testing with different versions of mesa and libdrm. On my first try I could still repro with mesa 10.4.6 and libdrm 2.4.59. -- You are receiving this mail because:

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #7 from Gabriele Svelto --- After some fiddling with the various dependency I'm now testing on mesa 11.0.3. I haven't hit the bug just yet but I want to run the emulator for a while to be sure it's not just

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #11 from Gabriele Svelto --- Created attachment 118860 --> https://bugs.freedesktop.org/attachment.cgi?id=118860=edit X log -- You are receiving this mail because: You are the QA Contact for the bug.

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #9 from Gabriele Svelto --- I'm attaching a new dmesg/Xorg.0.log couple taken just after I hit the bug, they'll be probably easier to parse than the previous one. Especially the dmesg output has some

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 Gabriele Svelto changed: What|Removed |Added Attachment #118838|0 |1

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #8 from Gabriele Svelto --- I can still reproduce on mesa 11.0.3 / libdrm 2.4.65 though it takes longer to trigger the bug (a few minutes of usage). This is the backtrace when using these versions of mesa

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #1 from Gabriele Svelto --- Created attachment 118839 --> https://bugs.freedesktop.org/attachment.cgi?id=118839=edit X log -- You are receiving this mail because: You are the QA Contact for the bug. You

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #2 from Ilia Mirkin --- Does this still happen with recent mesa (and libdrm)? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.

[Nouveau] [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50

https://bugs.freedesktop.org/show_bug.cgi?id=92438 --- Comment #3 from Gabriele Svelto --- I can test it, which version of mesa and libdrm do you suggest? The portage tree seems to have all recent versions. -- You are receiving this mail because: You are the QA