Launchpad has imported 13 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=104778.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2018-01-24T22:47:15+00:00 Mark-a-janes wrote:

Mesa CI reports a low error rate (2/700k), however the number of
intermittent failures is consistently nonzero.  This is worse than our
historical results.

The rarity of the failures makes it difficult to pinpoint the
regression, however there are several repeating errors:

i965: Failed to submit batchbuffer: Bad address
    piglit.spec.!opengl 1_1.copypixels-draw-sync  ivb
    piglit.spec.!opengl 1_3.gl-1_3-texture-env   snb


intel_batchbuffer.c:937: submit_batch: Assertion `entry->handle == 
batch->batch.bo->gem_handle' failed.
    piglit.spec.!opengl 1_3.gl-1_3-texture-env.bdwm64
    piglit.shaders.glsl-fs-raytrace-bug27060 skl

HSW tesselation failures

deqp-gles31': corrupted double-linked list: 0x0000561e9518be50 ***
    dEQP-GLES31.functional.debug.error_filters.case_0.bdwm64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/0

------------------------------------------------------------------------
On 2018-01-31T14:59:20+00:00 Kenxeth wrote:

Do we know what kernel version is running on the machines with failures?
We do slightly different things on v4.13 and later.  Wondering if it's
only happening on machines with older kernels, or newer ones, or both.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/1

------------------------------------------------------------------------
On 2018-01-31T16:42:44+00:00 Mark-a-janes wrote:

Unfortunately I saw this recently on 4.14 and 4.11

http://otc-mesa-ci.jf.intel.com/job/Leeroy/1934476/ - ivbgt2-01 4.14
http://otc-mesa-ci.jf.intel.com/job/Leeroy/1934454/ - sklgt2-04 4.11

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/2

------------------------------------------------------------------------
On 2018-03-23T10:51:40+00:00 Lionel-g-landwerlin wrote:

Running piglit.shaders.glsl-fs-raytrace-bug27060, I found this valgrind
warning : https://patchwork.freedesktop.org/patch/212413/

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/3

------------------------------------------------------------------------
On 2018-03-23T13:42:29+00:00 Lionel-g-landwerlin wrote:

The Broadwell failure is interesting as it's clearly a memory corruption issue.
Running the dEQP-GLES31.functional.debug.* tests under valgrind, I can see a 
few errors from the CTS suite :

Test case 'dEQP-
GLES31.functional.debug.negative_coverage.callbacks.state.get_nuniformfv'..

==12081== Use of uninitialised value of size 8
==12081==    at 0x59B505E: ??? (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25)
==12081==    by 0x59B55A8: std::ostreambuf_iterator<char, 
std::char_traits<char> > std::num_put<char, std::ostreambuf_iterator<char, 
std::char_traits<char> > >::_M_insert_int<long>(std::ostreambuf_iterator<char, 
std::char_traits<char> >, std::ios_base&, char, long) const (in 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25)
==12081==    by 0x59C1178: std::ostream& std::ostream::_M_insert<long>(long) 
(in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.25)
==12081==    by 0x71CAF1: std::ostream& tcu::Format::operator<< <int 
const*>(std::ostream&, tcu::Format::Array<int const*> const&) (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0xD9F922: std::ostream& tcu::Format::operator<< 
<int>(std::ostream&, tcu::Format::ArrayPointer<int> const&) (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0xEE0160: tcu::MessageBuilder& tcu::MessageBuilder::operator<< 
<tcu::Format::ArrayPointer<int> >(tcu::Format::ArrayPointer<int> const&) (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0xE9E45F: glu::CallLogWrapper::glGetIntegerv(unsigned int, 
int*) (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0xA611D2: 
deqp::gles31::Functional::NegativeTestShared::get_nuniformfv(deqp::gles31::Functional::NegativeTestShared::NegativeTestContext&)
 (in /home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0x7230DF: deqp::gles31::Functional::(anonymous 
namespace)::TestFunctionWrapper::call(deqp::gles31::Functional::(anonymous 
namespace)::DebugMessageTestContext&) const (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0x725DA1: deqp::gles31::Functional::(anonymous 
namespace)::CallbackErrorCase::iterate() (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0x6DCAD3: 
deqp::gles31::TestCaseWrapper::iterate(tcu::TestCase*) (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)
==12081==    by 0xF9E157: 
tcu::TestSessionExecutor::iterateTestCase(tcu::TestCase*) (in 
/home/djdeath/src/mesa-src/VK-GL-CTS/build-es31/modules/gles31/deqp-gles31)


I'm not sure whether that's related, might be worth fixing though (trying to 
write some patches).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/4

------------------------------------------------------------------------
On 2018-04-15T02:12:18+00:00 Samuel-sieb wrote:

I just had my Gnome desktop crash and the only info in the log was:
i965: Failed to submit batchbuffer: Bad address

This is on Fedora 27, kernel 4.15.9, mesa 17.3.6.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/5

------------------------------------------------------------------------
On 2018-04-15T17:23:08+00:00 Mark-a-janes wrote:

It's clear to me that this bug is not simply "CI ghosts".  We have a bug
in Mesa which is hard to trigger, and we hit it very occasionally with
the exhaustive CI infrastructure.

What we need is ideas on how to narrow down the failure.  Perhaps one of
the branches that performs additional memory verification could help?  I
got nothing out of valgrind.

I'm eager to get suggestions on what to do next.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/6

------------------------------------------------------------------------
On 2018-05-03T18:33:38+00:00 Greatquux wrote:

I've also encountered some desktop crashes lately with

May 03 14:15:15 ossy /usr/lib/gdm3/gdm-x-session[5995]: i965: Failed to
submit batchbuffer: Cannot allocate memory

but it's intermittent and yeah this sounds like a tough problem to solve. 
Ubuntu 18.04; GNOME 3.28.1; Kernel 4.15.0-20-lowlatency; Intel HD Graphics 630 
with modesetting on Xorg 1.19.6  (but might try the old intel driver)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/7

------------------------------------------------------------------------
On 2018-05-23T05:36:21+00:00 Mark-a-janes wrote:

*** Bug 106621 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/8

------------------------------------------------------------------------
On 2018-10-29T15:42:48+00:00 Mark-a-janes wrote:

One of the tests that seems to reproduce this more often than others:

dEQP-
GLES31.functional.debug.negative_coverage.get_error.vertex_array.draw_arrays_instanced_incomplete_primitive

produces on stderr:
  corrupted size vs. prev_size
or
  corrupted double-linked list

Seen on bxt, bdw, bsw, ivb

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/12

------------------------------------------------------------------------
On 2018-11-01T15:12:22+00:00 Martin-peres-n wrote:

We hit this bug twice in a week, and then nothing since then (5 months
and 1 week). I wonder if newer kernels fixed this issue. What is the
most up to date kernel that has shown this issue?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/13

------------------------------------------------------------------------
On 2018-11-01T15:43:52+00:00 Mark-a-janes wrote:

4.18.  If you have a suggestion for what to run, I'll update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/14

------------------------------------------------------------------------
On 2018-11-01T16:19:17+00:00 Martin-peres-n wrote:

(In reply to Mark Janes from comment #11)
> 4.18.  If you have a suggestion for what to run, I'll update.

Our CI last saw it on Linux: 4.17.0-rc6. So I guess we are just lucky...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/comments/15


** Changed in: xserver-xorg-video-intel (Fedora)
       Status: Unknown => Incomplete

** Changed in: xserver-xorg-video-intel (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1794033

Title:
   i965: Failed to submit batchbuffer: Bad address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to