From: Dave Airlie <airlied@gmail.com>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Noralf Trønnes" <noralf@tronnes.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: udl hotunplug broken
Date: Fri, 15 Mar 2019 14:19:31 +1000 [thread overview]
Message-ID: <CAPM=9ty1a4LZQhJ+ykBYvV55imfAqGabfyR7OLF4bVPu4i32ew@mail.gmail.com> (raw)
Hey,
Not sure how long this has been broken, considering plugging it in was
broken, unplugging is much worse. Is there anything outside my tree
that might be fixing this?
Currently it appears if I unplug udl while userspace has the device
open, it's bad, I get the userspace fb leaked thing which isn't
surprising, but I do get a lot of backtracing and warns which differ
depending on which way the race happens between X and unload.
I'm going to see if I can find a fix, but I'm guessing it's a lot of
digging to figure this out.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-15 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 4:19 Dave Airlie [this message]
2019-03-15 14:18 ` udl hotunplug broken Noralf Trønnes
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='CAPM=9ty1a4LZQhJ+ykBYvV55imfAqGabfyR7OLF4bVPu4i32ew@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=noralf@tronnes.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;
as well as URLs for NNTP newsgroup(s).