Hi, could you please attach kern.log and/or dmesg with debug information, drm.debug=0x1e parameter on grub. Thanks.

Created attachment 137787 [details]
DRM log

I don’t see any relation with LSPCON, I analyzed the logs, I don’t even see I915 driver getting loaded properly. and looks like ACPI related error:


  [drm] Memory usable by graphics device = 4096M
  [drm] Replacing VGA console driver
  [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [drm] Driver supports precise vblank timestamp query.
  i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2
  i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/downloads/firmware], disabling runtime power management.
  i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [drm] Initialized i915 1.6.0 20170619 for 0000:00:02.0 on minor 0
  ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
  input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  ata2: SATA link down (SStatus 4 SControl 300)
  ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
  ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170531/psparse-550)
  ata1.00: ATA-8: WDC WD1600BEVT-22A23T0, 01.01A01, max UDMA/133
  ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
  ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
  ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20170531/psparse-550)

Created attachment 137792 [details]
Logs_0305_1936

Hi,
I attached the log again.
These log should have more detail when boot to Ubuntu.

Hello, could you please install dmc firmware for kbl?
https://01.org/linuxgraphics/downloads/firmware

Also, with dmc, is it this still reproducible with latest stable https://www.kernel.org?

Does it happens when you have HDMI connected before the machine is powered on, or connected while booting?

Please attach the logs as raw text, is easier to access them that way. And I don't see the debug parameter (drm.debug=0x1e) on kern.log:

Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=80203aee-c3f9-446d-a77b-7e45f9479436 ro quiet splash i915.enable_rc6=0

Thanks.

(In reply to Elizabeth from comment #5)
> Hello, could you please install dmc firmware for kbl?
> https://01.org/linuxgraphics/downloads/firmware
> 
> Also, with dmc, is it this still reproducible with latest stable
> https://www.kernel.org?
> 
> Does it happens when you have HDMI connected before the machine is powered
> on, or connected while booting?
> 
> Please attach the logs as raw text, is easier to access them that way. And I
> don't see the debug parameter (drm.debug=0x1e) on kern.log:
> 
> Command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic
> root=UUID=80203aee-c3f9-446d-a77b-7e45f9479436 ro quiet splash
> i915.enable_rc6=0
> 
> Thanks.

Hi Elizabeth,
This issue only happened on booting linux, win10 works fine.
This system has display port and HDMI port. In Display port, it can boot to Linux, but not HDMI.

And HDMI hot plug in Ubuntu also reset the system.
1. Boot to Ubuntu with Display port
2. unplug Display port, plug HDMI
3. System will reset when I unpluged HDMI

Is it related HDMI HPD function?

I will attach the log latter.

Hi Elizabeth,

Please refer to the attachment.
We installed the dmc firmware and it did not change anything except the error message related to dynamic power management disappeared. 

The debug flag has been enabled.

Thanks



Sam

Created attachment 137847 [details]
enable debug flag

Hi Elizabeth,

I found something looks not usual in the log. Check those below:


============================================================================
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID:  (err -6)
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:drm_helper_hpd_irq_event [drm_kms_helper]] [CONNECTOR:63:HDMI-A-1] status updated from unknown to disconnected
============================================================================

DP dual mode HDMI ID: err -6 and I checked the error code in the kernel and -6 means /* No such device or address */

I tried to find the root cause and found the following logs 

=============================================================================
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] /ENX for addr: 0050 w(1)
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] NAK on first message, retry
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] NAK for addr: 0050 w(1)
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent adapter i915 gmbus dpc
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] NAK for addr: 0040 w(1)
 三  05 09:31:11 supermicro-X11SSN-E kernel: [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpc] NAK on first message, retry
============================================================================

It seems like the system keeps probing the addr 0050 and 0040 but failed to get ack ( NAK received ) which causes the failure of HDMI connection in the end.

I am not sure why system failed to get ack. Please let me know if you may have any thinking.


Thanks



Sam

HDMI - Port A shouldn't exist, since we are using

Port A: LVDS (Internal Panel)
Port B: HDMI (LSPCON)
Port C: DP

I found the internal panel always be detected, but there is not panel connected.

I see you're using generic kernel. Could you try this branch https://cgit.freedesktop.org/drm-tip? It has latest fixes added for all features, so it will help to know if there is a difference between 4.13 and actual drm-tip head.

Created attachment 138013 [details]
rc4_kernel_hd620

Hi,

I've rebuild and installed the kernel on Ubuntu 16.04.

However, it did not make any difference.

Please check the log.


Thanks


Sam

Hi,

We've attached another log which enables all ACPI debug_layer and debug_level as the reference for this ticket.

I did this in the boot and run-time configuration not in the compile-time configuration. 

I assume it shouldn't have any difference.


Sam

Created attachment 138065 [details]
ACPI debug flag enabled

Hi Elizabeth,
Our HW engineer found VDD12_ON pin in PS175 will be set to low when boot to Ubuntu.
Can you help us to find why this pin set to low when booting Ubuntu?

DP dual mode HDMI ID: err -6 and I checked the error code in the kernel and -6 means /* No such device or address */ This error comes when we do a detection of dp_dual_mode_device, and it can't cause a modeset failure. For port A/C this error can be ignored. 

Now, Can I have the dmesg logs, just for following cases:
- at DP hot-unplug ?
- at following HDMI hot-plug ? 

- Shashank

Hi Shashank,
PS175 vendor pointed the reset is caused by send DPCD command address: 0x00600 Data: 02

I check the code, and Linux will set D3 power when booting.

#define DP_SET_POWER                        0x600
# define DP_SET_POWER_D0                    0x1
# define DP_SET_POWER_D3                    0x2

void intel_dp_sink_dpms(struct intel_dp *intel_dp, int mode)
{
	int ret, i;

	/* Should have a valid DPCD by this point */
	if (intel_dp->dpcd[DP_DPCD_REV] < 0x11)
		return;

	if (mode != DRM_MODE_DPMS_ON) {
		if (downstream_hpd_needs_d0(intel_dp))
			return;

		ret = drm_dp_dpcd_writeb(&intel_dp->aux, DP_SET_POWER,
					 DP_SET_POWER_D3);
	} else {

Is there any boot option we can skip DP set power d3?

First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.

Hi,
You can close this one, since this need HW change the VDD12_ON pin to fix this bug.
Thanks for your kindly support.