From: Edd Barrett <edd@theunixzoo.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Gvim causes Xorg to crash in Intel driver
Date: Fri, 27 May 2016 17:33:10 +0100 [thread overview]
Message-ID: <20160527163310.GA80020@wilfred.home> (raw)
Hello everyone,
I raised a bug [1] a few days ago about a crash in the Intel driver's
SNA code on OpenBSD. I'm posting here to try to drum up some interest.
This bug is affecting a few users (including myself). It prevents us
using our text editor of choice, gvim.
I've also reported to x11@openbsd.org.
Since reporting this, I have realised that the code used in OpenBSD is a
little behind the bleeding edge [2]. It looks like the crashing
functionality has been (at least) refactored. I've browsed the git
history looking for a fix, but I haven't found one. There's a good
chance that this bug still exists in git head.
I'm going to try the latest Intel driver code over the weekend (if it
will build on OpenBSD without too many changes).
In the meantime, does this crash ring any bells to any of you? Ideally
we could find a minimal patch that could be applied to the OpenBSD tree
without updating the whole driver code (just yet).
Any help or advice is most appreciated.
Thanks!
[1] https://bugs.freedesktop.org/show_bug.cgi?id=96194
[2] http://cvsweb.openbsd.org/cgi-bin/cvsweb/xenocara/driver/xf86-video-intel/
--
Best Regards
Edd Barrett
http://www.theunixzoo.co.uk
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2016-05-27 16:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160527163310.GA80020@wilfred.home \
--to=edd@theunixzoo.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox