[Bug 295788] graphics/drm-kmod: i915kms Hardware acceleration not working for Intel Braswell since >drm-510-kmod

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295788

--- Comment #54 from Roger Olofsson <[email protected]> ---
(In reply to Jean-Sébastien Pédron from comment #51)

Hi Jean- Sébastien!

Thank you for helping!

No, I haven't tried 15.1 with this asus r517sa. Before 15.1 was released I
tried releng/15.0p9 but I couldn't make drm-510 work on it. I tried to hack it
a bit (drm-510) and made it compile but it came up on boot with an upside down
green picture for a few seconds before the GPU_HANGs came ;^D

After that I went back to 14 and found the workaround where I noticed I could
build drm-510 on a releng/14.4 if I did a git switch for usr/src to 14.3 (while
on 14.4) and it works.

So far Gleb has helped me - alot - and as of now we have seen that Xorg
SIGABRTs when an assertion breaks and we think the Xorg modesetting Crocus goes
to 

intel_gem_create_hw_context which is in intel_gem.c.

C:
     64 bool
     65 intel_gem_create_context(int fd, uint32_t *context_id)
     66 {
     67    return i915_gem_create_context(fd, context_id);
     68 }

And that goes to i915/intel_gem.c

C:
     31 bool
     32 i915_gem_create_context(int fd, uint32_t *context_id)
     33 {
     34    struct drm_i915_gem_context_create create = {};
     35    if (intel_ioctl(fd, DRM_IOCTL_I915_GEM_CONTEXT_CREATE, &create))
     36       return false;
     37    *context_id = create.ctx_id;
     38    return true;
     39 }

This goes on to intel_gem.h even though there is another intel_gem.h in the
i915 subdirectory.

C:
     77 static inline int
     78 intel_ioctl(int fd, unsigned long request, void *arg)
     79 {
     80     int ret;
     81 
     82     do {
     83         ret = ioctl(fd, request, arg);
     84     } while (ret == -1 && (errno == EINTR || errno == EAGAIN));
     85     return ret;
     86 }

And there it goes to libc.so.7 on line 83 and if cont it breaks.

It would be great if you could find the time to help - anytime is fine!

Roger

-- 
You are receiving this mail because:
You are the assignee for the bug.