From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97909] X-Plane 10 crashes with SIGSEGV on radeonsi
Date: Fri, 31 Aug 2018 05:59:14 +0000 [thread overview]
Message-ID: <bug-97909-502-Yd5odLv0Ye@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97909-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97909
Timothy Arceri <t_arceri@yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |FIXED
--- Comment #17 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to Joonas Sarajärvi from comment #16)
> Now that I tried removing the workaround again, it looks like things still
> work for me. So now at least one working combination that does not trigger
> this bug looks like this:
>
> - Fedora 28
> - kernel 4.16.14-300.fc28.x86_64
> - mesa 18.0.2
> - x-plane 11.21
>
> Compared to my earlier report, all the bits have changed their versions.
> Does anyone have any idea on if this was addressed in the driver stack or if
> it is actually X-plane behaving nicer?
It would seem its something in the driver since I doubt they are updating
X-Plane 10 any more since X-Plane 11 has been out for some time. Anyway I'm
going to close this as fixed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2808 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-08-31 5:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 23:06 [Bug 97909] X-Plane 10 crashes with SIGSEGV on radeonsi bugzilla-daemon
2016-09-23 23:07 ` bugzilla-daemon
2016-09-23 23:08 ` bugzilla-daemon
2016-09-28 13:59 ` bugzilla-daemon
2016-10-25 3:59 ` bugzilla-daemon
2016-11-04 20:20 ` bugzilla-daemon
2016-11-04 21:05 ` bugzilla-daemon
2016-11-04 21:07 ` bugzilla-daemon
2017-11-24 21:14 ` bugzilla-daemon
2017-12-29 16:31 ` bugzilla-daemon
2018-04-12 2:06 ` bugzilla-daemon
2018-04-12 6:05 ` bugzilla-daemon
2018-04-12 6:53 ` bugzilla-daemon
2018-04-12 7:45 ` bugzilla-daemon
2018-04-12 11:32 ` bugzilla-daemon
2018-04-12 16:46 ` bugzilla-daemon
2018-06-10 17:42 ` bugzilla-daemon
2018-08-31 5:59 ` bugzilla-daemon [this message]
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=bug-97909-502-Yd5odLv0Ye@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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