[Bug 108502] New: Invalid encoder after hotplug

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Oct 19 18:25:15 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=108502

            Bug ID: 108502
           Summary: Invalid encoder after hotplug
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: haupt.wolfgang at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 142105
  --> https://bugs.freedesktop.org/attachment.cgi?id=142105&action=edit
dmesg

I'm working on hotplug support for linux/gbm in kodi.
Now I hit a roadblocker which looks like a driver issue to me.

I retrieve the hotplug info through a udev monitor and then I reinitialize the
graphic system of the application.
Unfortunately I always get an encoder ID 0 and initialization of the drm/kms
code fails.

I have attached a small test application, that can easily reproduce the issue.
These are the needed steps (for ubuntu):
sudo systemctl isolate multi-user.target
DISCONNECT HDMI
cd /path/of/testapp
./a.out
CONNECT HDMI

After this steps, if you stop the app and restart it you will always get an
invalid encoder.
The kernel log also shows an issue with getting the edid infos from the i2c
controller.

This state doesn't change until you do another hotplug or reboot the box.

I've tested this with kernel 4.17.12 and kernel 4.18.3 -> same results.

Attached is the source of my sample and the dmesg log with drm.debug=14.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20181019/466cbb53/attachment.html>


More information about the intel-gfx-bugs mailing list