(In reply to Mark Janes from comment #22) > Hmm...`cp` in xterm is a pretty clear indicator that this issue is random > and not triggered by a specific workload. > > Lionel suggested that it would be good to have a feedback from the kernel > about what didn't pass validation. > > There is a kernel option to generate debug traces for that but you have to > recompile your kernel with that option. Lionel, can you provide some > details? > > It would be a good data point to see if a much older kernel produces this > error (eg 4.9, 4.4). I can't deploy those kernels in Mesa i965 CI because > they lack features needed to run our Vulkan test suites.
With the kernel compiled with CONFIG_DRM_I915_DEBUG_GEM and the following command issued as root : echo 15 > /sys/module/drm/parameters/debug You should be able to get some traces about why the execbuffer failed. Unfortunately that generates a lot of traces... -- 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
