The DP output signal of the device is lost, and it cannot be recovered by cold start

Ricardo_2007 · March 14, 2023, 9:07am

Dear experts

I have a problem with DP output and would like an answer from the DP startup process.

In the high-temperature testing environment, the DP output signal of the device is lost, and it cannot be recovered by cold start. And the HDMI signal is normal working.

What puzzles me is that this is not a hardware problem. When I reflash the firmware of the Nano, the problem can be solved.
Is there any files will be generated during DP initialization and saved to user space or ROM on the core board ？

Below is the kernel log from the issue device.
kern.log.1 (34.6 MB)
The first time the DP is worked, after the frequent plug and pull detection, and then the screen goes black. Any subsequent startup DP is unavailable.

But when I reflash the nano board, the DP works well again.

WayneWWW · March 14, 2023, 9:17am

Hi,

Could we just get a recent NG case log instead of a 34MB log?

Ricardo_2007 · March 14, 2023, 9:29am

Hi WayneWWW

This is the NG case log:
dp_issue_log.txt (226.8 KB)

thanks!

Ricardo_2007 · March 14, 2023, 9:31am

And those are the log of cold Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ Mar 10 15:26:50 gelx-desktop kernel: [ start since then:
1.053278] tegradc tegradc.0: disp0 connected to head0->/host1x/sor1
1.053373] display board info: id 0x0, fab 0x0
1.053436] generic_infoframe_type: 0x87
1.053455] tegra_cec 70015000.tegra_cec: cec_add_sysfs ret=0
1.053460] tegra_cec 70015000.tegra_cec: probed
1.053581] tegradc tegradc.0: DT parsed successfully
1.053629] tegradc tegradc.0: Display dc.ffffff800a900000 registered with id=0
1.061143] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver register 32 channels
1.065498] tegradc tegradc.0: probed
1.066261] Console: switching to colour frame buffer device 80x30
1.066297] tegradc tegradc.0: fb registered
1.066877] tegra-adma 702e2000.adma: Tegra210 ADMA driver registered 22 channels
1.067883] tegradc tegradc.1: disp1 connected to head1->/host1x/sor
1.067966] tegradc tegradc.1: No lt-data, using default setting
1.068000] tegradc tegradc.1: No hpd-gpio in DT
1.068032] tegradc tegradc.1: DT parsed successfully
1.068087] tegradc tegradc.1: Display dc.ffffff800aa80000 registered with id=1
1.068108] tegra-fuse-burn 7000f800.efuse:efuse-burn: shutdown limit check disabled
1.068217] tegra-fuse-burn 7000f800.efuse:efuse-burn: Fuse burn driver initialized
1.068872] kfuse 7000fc00.kfuse: initialized
1.069636] tegradc tegradc.1: dpd enable lookup fail:-19
1.069913] tegra-pmc-iopower pmc-iopower: Regulator supply iopower-dbg-supply not available
1.070730] tegra-pmc-iopower pmc-iopower: NO_IOPOWER setting 0x0
1.071709] tegra-dfll-pwm 70110000.pwm: DFLL_PWM regulator is available now
1.071719] vdd-cpu: 708 ↔ 1322 mV at 708 mV
1.072144] pwm-regulator pwm_regulators:pwm-regulator@0: PWM regulator registration passed
1.575412] Host read timeout at address 545c00c4
1.576122] vdd-gpu: applied init 1000000uV constraint
1.576131] vdd-gpu: 708 ↔ 1323 mV at 997 mV
1.576513] pwm-regulator pwm_regulators:pwm-regulator@1: PWM regulator registration passed
1.576727] tegradc tegradc.1: probed
1.577038] tegradc tegradc.1: fb registered
1.580426] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
1.580523] No Device Node present for smmu client: serial8250 !!
1.580531] platform serial8250: No iommus property found in DT node, got swgids from fixup(101004000)
1.580571] iommu: Adding device serial8250 to group 35
1.581255] tegradc tegradc.1: dp: irq event received, ignoring
1.582165] tegradc tegradc.1: dp: irq event received, ignoring
1.583086] 70006000.serial: ttyS0 at MMIO 0x70006000 (irq = 63, base_baud = 25500000) is a Tegra
1.583100] tegradc tegradc.1: dp: irq event received, ignoring
1.583990] 70006040.serial: ttyTHS1 at MMIO 0x70006040 (irq = 64, base_baud = 0) is a TEGRA_UART
1.584022] tegradc tegradc.1: dp: irq event received, ignoring
1.584304] serial-tegra 70006200.serial: RX in PIO mode
1.584391] 70006200.serial: ttyTHS2 at MMIO 0x70006200 (irq = 65, base_baud = 0) is a TEGRA_UART
1.584949] tegradc tegradc.1: dp: irq event received, ignoring
1.585406] [drm] Initialized
1.585876] tegradc tegradc.1: dp: irq event received, ignoring
1.586804] tegradc tegradc.1: dp: irq event received, ignoring
1.587730] tegradc tegradc.1: dp: irq event received, ignoring
1.588605] tegradc tegradc.1: dp: irq event received, ignoring
1.589820] tegradc tegradc.1: dp: irq event received, ignoring
1.590731] tegradc tegradc.1: dp: irq event received, ignoring
1.591660] tegradc tegradc.1: dp: irq event received, ignoring
1.592584] tegradc tegradc.1: dp: irq event received, ignoring
1.593509] tegradc tegradc.1: dp: irq event received, ignoring
1.594436] tegradc tegradc.1: dp: irq event received, ignoring
1.595364] tegradc tegradc.1: dp: irq event received, ignoring
1.596289] tegradc tegradc.1: dp: irq event received, ignoring
1.596442] brd: module loaded
1.597216] tegradc tegradc.1: dp: irq event received, ignoring
1.599361] tegradc tegradc.1: dp: unplug event received
1.599420] hpd: state 7 (Takeover from bootloader), hpd 0, pending_hpd_evt 1
1.599426] hpd: switching from state 7 (Takeover from bootloader) to state 0 (Reset)
1.599436] hpd: state 0 (Reset), hpd 0, pending_hpd_evt 0
1.599454] tegradc tegradc.1: blank - powerdown
1.599479] extcon-disp-state extcon:disp-state: cable 44 state 0 already set.
1.599485] Extcon DP: HPD disabled
1.599488] hpd: hpd_switch 0
1.599493] hpd: switching from state 0 (Reset) to state 1 (Check Plug)
1.599502] hpd: state 1 (Check Plug), hpd 0, pending_hpd_evt 0
1.599510] hpd: switching from state 1 (Check Plug) to state 3 (Disabled)
1.601929] loop: module loaded
1.602021] tegra_profiler: version: 1.145, samples/io: 49/28
1.602143] tegra_profiler: auth: init
1.603449] THERMAL EST: found 2 subdevs
1.603461] THERMAL EST num_resources: 0
1.603468] [THERMAL EST subdev 0]
1.603477] [THERMAL EST subdev 1]
1.603929] thermal thermal_zone5: Registering thermal zone thermal_zone5 for type thermal-fan-est
1.603933] THERMAL EST: thz register success.
1.604088] THERMAL EST: end of probe, return err: 0
1.605372] sd: No Scsi addr parsed to reserve index
1.605414] hisi_sas: driver version v1.6
1.606300] tegradc tegradc.1: nominal-pclk:148500000 parent:148500000 div:1.0 pclk:148500000 147015000~161865000
1.606390] tegradc tegradc.1: dp: HPD is not detected
1.606433] tegradc tegradc.1: dp: Failed to write DPCD data. CMD 0x600, Status 0x0
1.606459] tegradc tegradc.1: dp: HPD is not detected
1.606474] tegradc tegradc.1: dp: Failed to write DPCD data. CMD 0x600, Status 0x0
1.606498] tegradc tegradc.1: dp: HPD is not detected
1.606510] tegradc tegradc.1: dp: Failed to write DPCD data. CMD 0x600, Status 0x0
1.606532] tegradc tegradc.1: dp: HPD is not detected
1.606544] tegradc tegradc.1: dp: Failed to write DPCD data. CMD 0x600, Status 0x0
1.606558] tegradc tegradc.1: dp: failed to exit panel power save mode (0xfffffff2)
1.607026] hpd: state 3 (Disabled), hpd 0, pending_hpd_evt 1
1.607033] hpd: switching from state 3 (Disabled) to state 0 (Reset)
1.607045] hpd: state 0 (Reset), hpd 0, pending_hpd_evt 0
1.607060] tegradc tegradc.1: blank - powerdown

WayneWWW · March 14, 2023, 9:35am

Hi,

Could we confirm if this is the behavior that always happened when this error occurred?

I notice there is plug and unplug event happened at same time

Mar 9 15:36:44 gelx-desktop kernel: [ 4088.345578] tegradc tegradc.1: dp: plug event received
Mar 9 15:36:44 gelx-desktop kernel: [ 4088.492280] tegradc tegradc.1: dp: unplug event received

Is this still on NV devkit?

Ricardo_2007 · March 14, 2023, 9:42am

We didn’t actually plug in or unplug any interface, it only happened at that time, and it lasted for a while and then it stopped.
When this event occurs, DP has no signal output.

WayneWWW · March 14, 2023, 9:43am

Ok, so is this still on NV devkit or your custom board?

How to reproduce this error?

Ricardo_2007 · March 14, 2023, 9:46am

We use it on our custom board. We can’t repeat the problem.
At first we thought it was a hardware problem, so we replaced the carrier board and the problem persisted.

When I reflash the nano firmware, this problem no longer exists.

WayneWWW · March 14, 2023, 9:48am

Hi,

I think you could try to use devkit and find out how to reproduce this issue first.

Ricardo_2007 · March 14, 2023, 9:50am

What puzzles me is that this is not a hardware problem. When I reflash the firmware of the Nano, the problem can be solved.
Is there any files will be generated during DP initialization and saved to user space or ROM on the core board ？

WayneWWW · March 14, 2023, 9:50am

Nope.

system · April 5, 2023, 3:23am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.