(In reply to Denis from comment #28)
> Hello Yoshinori Gento
>
> >I got how to reproduce.
> Does this mean that you could provide an apitrace or somekind of reproducer?
> It would be really helpful.
Hello Denis
I didn't produce an apitrace nor reproducer.
I updated kernel to 4.19.57.
Then, this
I got how to reproduce.
Cached memory grows big by reading many files and free RAM becomes empty.
In this situation (repeat release and allocate caches frequently), drawing
process faces this problem.
Does conflict of memory cause this problem?
--
You received this bug notification because
Created attachment 143768
Debug trace.
I got debug traces. Please see attached file.
PID needs to be checked is 2602.
After that this process was exited with "i965: Failed to submit batchbuffer:
Bad address".
At that time I repeated to copy and delete of files by rsync.
Note: This is occurred
I saw this problem three times from yesterday.
All of them occurred during file sync over LAN with rsync.
I think this problem might be related to load by disk i/o or network i/o.
But unfortunately I have not re-compiled kernel with CONFIG_DRM_I915_DEBUG_GEM
yet.
I will try to it next week.
--
(In reply to Mark Janes from comment #20)
> Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can
> analyze and fix it.
>
> How often does this occur in your product? If it is reproducible, then
> perhaps we can use an apitrace to investigate the root cause.
While I
I saw this once.
[Environment]
CPU: SkyLake(core i5 6500TE)
Distribution: debian(customised)
Kernel: 4.14.98
Mesa: 18.3.3
libdrm: 2.4.89
Message from stdout of drawing module was
i965: Failed to submit batchbuffer: Bad address
and back-trace were following
:
:
#5
(In reply to Yoshinori Gento from comment #18)
> I saw this once.
This occurred in our product.
--
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
7 matches
Mail list logo
