System Environment BIOS:APLKRVPA.X64.0103.R13.1509280749 Kernel:4.3.0-bxt+ Tree: git://anongit.freedesktop.org/drm-intel Branch:drm-intel-nightly Commit: 6a5ee47c4451207d40bf2e816fdec37b947cee53 Bug detailed description If boot up APL with HDMI and DP cable not connected to monitor, the monitor does not display after connect the DP/HDMI cable. If boot up APL with HDMI and DP cable connected to monitor, display is OK.
Please attach dmesg with drm.debug=14 module param set. Do you have some userspace that responds to hotplug events? What does this have to do with audio, and what is "APL" in the description?
Hi, I'll on 2 days training during 9:00am~4:30pm on Thursday and Friday, please expect delayed reply. Anything emergency, please call 86-15921227373. Thanks. BR, Han Lu
Hi Jani, My platform is sent to rework. I'll add dmesg when rework is done. APL(Apollolake) is the type name of BXT-P I'm using.
Created attachment 119629 [details] dmesg with boot parameter drm.debug=14 and HDMI cable unconnected Hi Jani, Update: With latest commit on drm-nightly repo, the issue is NOT reproduced on DP, but still reproduced on HDMI. Please find dmesg log attached. My platform is BXT-P RVP2B. Reproduce steps: 1. Disconnect HDMI cable,boot up with parameter "drm.debug=14" 2. ssh to BXT 3. run "udevadm monitor --property --tag-match=HOTPLUG", output is monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent 4. Plug on HDMI cable, no output on SSH interface 5. In ssh, dmesg > dmesg.log
Please try http://patchwork.freedesktop.org/patch/msgid/1447931396-19147-1-git-send-email-tiwai@suse.de
With Takashi's patch the issue is still existing. Boot BXT-P without HDMI cable and the HDMI monitor does not display after plug on HDMI cable.
The issue still happen with the latest configuration and drm-intel-testing, we cannot get the output on HDMI unless we boot with HDMI from the beginning Bios : 119.10 KSC : 1.0 OS : Ubuntu 14.04.03 LTS x86_64 Graphic stack versions : ----------------------------------------- cairo version: 1.15.2 / commit : db8a7f1 drm version : libdrm-2.4.66 / commit : b38a4b2 intel-driver : 1.6.2 / commit: 683edee libva version : libva-1.6.2 / commit : 304bc13 mesa version : mesa-11.0.8 / commit : 261daab xf86-video-intel version : 2.99.917 / commit : baec802 xserver version :xorg-server-1.18.0 / commit :7921764 kernel drm-intel-testing: ------------------------------------------ commit 91587c722c28c4116dedbfbf08aa874377bc76f8 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Fri Dec 4 17:35:54 2015 +0100 drm-intel-nightly: 2015y-12m-04d-16h-35m-07s UTC integration manifest kernel version : 4.4.0-rc3 git url : git://anongit.freedesktop.org/drm-intel git branch : drm-intel-testing git describe : drm-intel-next-2015-11-20-rebased-13721-g91587c7
Could you attach a dmesg with a working setup, that is when you boot with the HDMI output connected?
While I chase down hardware on my side, could someone please attempt to reproduce this with a more recent kernel? In particular please verify that the following patch is in there. commit 3d8acd1f667b45c531401c8f0c2033072e32a05d Author: Gary Wang <gary.c.wang@intel.com> Date: Wed Dec 23 16:11:35 2015 +0800 drm/i915: increase the tries for HDMI hotplug live status checking
I still reproduce this issue using the following Kernel. commit 8fe9e785ae04fa7c37f7935cff12d62e38054b60 Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Thu Jan 21 11:03:06 2016 +0000 drm-intel-nightly: 2016y-01m-21d-11h-02m-42s UTC integration manifest from: git://anongit.freedesktop.org/drm-intel Verified that I do have the patch suggested by Jim Bride
Created attachment 121289 [details] dmesg log with drm.debug=14 with a working setup, HDMI connected Attaching log with HDMI connected and having a working setup as requested by Imre Deak's
(In reply to Jairo Miramontes from comment #11) > Created attachment 121289 [details] > dmesg log with drm.debug=14 with a working setup, HDMI connected > > Attaching log with HDMI connected and having a working setup as requested by > Imre Deak's Thanks. This isn't actually with drm.debug=14, could you provide one with that option?
Created attachment 121319 [details] (2)dmesg log with drm.debug=14 with a working setup, HDMI connected Excuse me, this dmesg does have the drm.debug=14 option on Regards
(In reply to Jairo Miramontes from comment #13) > Created attachment 121319 [details] > (2)dmesg log with drm.debug=14 with a working setup, HDMI connected > > Excuse me, this dmesg does have the drm.debug=14 option on > Regards Thanks. It looks like you have the following routing: Host DDI0 <- LSPCON DP-HDMI converter chip on board <- HDMI connector The driver outputs a DP signal which is converted by LSPCON to HDMI. Since we don't have a support in the driver (yet) to configure the LSPCON chip this will only work if BIOS has done so already, but it seems that BIOS will not configure the chip if there isn't any display connected. LSPCON support is being added atm, so we need to revisit this ticket when that's done. Not sure what's the proper bugzilla status until then, I'm leaving this open for now.
Bug scrub --------- Increase priority
Hi, I'm taking AL from 2/5/2016 to 2/14/2016, please expect delayed reply. Anything emergency, please call 86-15921227373. Thanks. BR, Han Lu
Hi Lu Han, could you please update to this.
The issue is still reproduced on drm-intel-testing-2016-02-14 and latest commit, FYI.
Change priority to highest. It will have an impact on Beta milestones.
The issue is fixed, but we need to wait for the patches supporting LSPCON be upstreamed.
This issue still happens on BXT-P with the following configuration: Hardware configuration ======================= Platform BXT - P (APL) Motherboard model Apollo Lake Motherboard type NOTEBOOK Hand Held Motherboard manufacturer Intel Corp. CPU family Other CPU information 06/5c GPU Card Intel Corporation Device 5a84 (rev 03) (prog-if 00 [VGA controller]) Memory ram 8 GB Software configuration ======================= --> Component : drm url : http://cgit.freedesktop.org/mesa/drm tag : libdrm-2.4.67-11-gea78c17 commit : ea78c17 author : Emil Velikov <emil.l.velikov@gmail.com> age : 20 hours ago --> Component : mesa url : http://cgit.freedesktop.org/mesa/mesa tag : mesa-11.1.2 commit : 7bcd827 author : Emil Velikov <emil.velikov@collabora.com> age : 7 weeks ago --> Component : xf86-video-intel url : http://cgit.freedesktop.org/xorg/driver/xf86-video-intel tag : 2.99.917-590-g094924f commit : 094924f author : Chris Wilson <chris@chris-wilson.co.uk> age : 4 days ago --> Component : libva url : http://cgit.freedesktop.org/libva/ tag : libva-1.7.0-1-g2339d10 commit : 2339d10 author : Xiang Haihao <haihao.xiang@intel.com> age : 13 days ago --> Component : vaapi (intel-driver) url : http://cgit.freedesktop.org/vaapi/intel-driver tag : 1.7.0-5-g759e44d commit : 759e44d author : peng.chen <peng.c.chen@intel.com> age : 13 days ago --> Component : cairo url : http://cgit.freedesktop.org/cairo tag : 1.15.2 commit : db8a7f1 author : Bryce Harrington <bryce@osg.samsung.com> age : 4 months ago --> Component : xserver url : http://cgit.freedesktop.org/xorg/xserver tag : xorg-server-1.18.0-254-g44e1c97 commit : 44e1c97 author : Olivier Fourdan <ofourdan@redhat.com> age : 8 days ago --> Component : intel-gpu-tools url : http://cgit.freedesktop.org/xorg/app/intel-gpu-tools tag : intel-gpu-tools-1.14-129-g41a26b5 commit : 41a26b5 author : Chris Wilson <chris@chris-wilson.co.uk> age : 26 hours ago kernel configuration ===================== Branch : drm-intel-nightly commit f5d413cccefa1f93d64c34f357151d42add63a84 Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Thu Mar 24 14:35:16 2016 +0000 drm-intel-nightly: 2016y-03m-24d-14h-34m-29s UTC integration manifest Kernel version : 4.5.0 Architecture : source amd64 all
Hi Maria, sorry for not state clearly. The issue is fixed when upgrade APL to B0 step, for details please refer to Bug 92805 - [BXT-P APL] [Audio] Cannot refresh ELD information on the text mode and the UI mode.
close it as this is fixed on APL B0 stepping
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.