WARNING occurs when plugin/out HDMI in OrinNX

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
, ,
1

We are working on Jetson Orin NX based custom board.

The following WARNING seems to occur frequently from Kernel when inserting or removing the HDMI cable.

[  589.716164] ------------[ cut here ]------------
[  589.716191] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[  589.725584] Modules linked in: nvidia_modeset(OE) fuse(E) lzo_rle(E) lzo_compress(E) zram(E) ramoops(E) reed_solomon(E) loop(E) snd_soc_tegra186_dspk(E) snd_soc_tegra210_ope(E) snd_soc_tegra186_asrc(E) snd_soc_tegra210_mixer(E) snd_soc_tegra186_arad(E) snd_soc_tegra210_mvc(E) snd_soc_tegra210_iqc(E) snd_soc_tegra210_afc(E) snd_soc_tegra210_i2s(E) snd_soc_tegra210_dmic(E) snd_soc_tegra210_amx(E) snd_soc_tegra210_admaif(E) snd_soc_tegra210_adx(E) snd_soc_tegra_pcm(E) snd_soc_tegra210_sfc(E) aes_ce_blk(E) crypto_simd(E) cryptd(E) aes_ce_cipher(E) ghash_ce(E) sha2_ce(E) sha256_arm64(E) sha1_ce(E) snd_soc_tegra_machine_driver(E) snd_soc_spdif_tx(E) leds_gpio(E) userspace_alert(E) snd_soc_tegra210_adsp(E) snd_soc_tegra_utils(E) snd_soc_simple_card_utils(E) snd_soc_tegra210_ahub(E) r8168(E) tegra_bpmp_thermal(E) snd_hda_codec_hdmi(E) nvadsp(E) tegra210_adma(E) snd_hda_tegra(E) r8169 snd_hda_codec(E) snd_hda_core(E) spi_tegra114(E) realtek(E) nvidia(OE) binfmt_misc(E) ina3221(E) pwm_fan(E)
[  589.725671]  nvgpu(E) nvmap(E) spidev(E) ip_tables(E) x_tables(E) [last unloaded: mtd]
[  589.725687] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           OE     5.10.104-tegra #2
[  589.725690] Hardware name: Unknown NVIDIA Orin NX based Contec Custom Board /NVIDIA Orin NX based Contec Custom Board , BIOS 2.1-32413640
[  589.725694] pstate: 20400089 (nzCv daIf +PAN -UAO -TCO BTYPE=--)
[  589.725697] pc : tegra186_gpio_irq+0x1ac/0x1f0
[  589.725699] lr : tegra186_gpio_irq+0x11c/0x1f0
[  589.725701] sp : ffff800010003ef0
[  589.725703] x29: ffff800010003ef0 x28: ffff49d8c0e58a60
[  589.725706] x27: ffffb4f4261fd578 x26: 0000000000000018
[  589.725710] x25: ffff49d8c5976080 x24: ffff49d8c59edc00
[  589.725713] x23: 000000000000000c x22: 000000000000004c
[  589.725717] x21: 00000000000000bc x20: 0000000000000000
[  589.725720] x19: ffffb4f4256ae390 x18: 0000000000000000
[  589.725723] x17: 0000000000000000 x16: 0000000000000000
[  589.725727] x15: 0000000000000000 x14: 0000000000000000
[  589.725730] x13: 0000000000000001 x12: 0000000000000500
[  589.725733] x11: 0000000000000040 x10: ffffb4f426168000
[  589.725737] x9 : ffffb4f426167ff8 x8 : ffff49d8c04b6018
[  589.725740] x7 : 0000000000000000 x6 : 0000000000000001
[  589.725743] x5 : 0000000000000000 x4 : 0000000000000000
[  589.725747] x3 : 0000000000000000 x2 : ffffb4f42457e170
[  589.725750] x1 : 000000000000004c x0 : 0000000000000000
[  589.725755] Call trace:
[  589.725758]  tegra186_gpio_irq+0x1ac/0x1f0
[  589.725766]  generic_handle_irq+0x40/0x60
[  589.725769]  __handle_domain_irq+0x70/0xd0
[  589.725773]  gic_handle_irq+0x68/0x134
[  589.725775]  el1_irq+0xd0/0x180
[  589.725782]  cpuidle_enter_state+0xb8/0x410
[  589.725785]  cpuidle_enter+0x40/0x60
[  589.725789]  call_cpuidle+0x44/0x80
[  589.725790]  do_idle+0x208/0x270
[  589.725793]  cpu_startup_entry+0x2c/0x70
[  589.725799]  rest_init+0xdc/0xe8
[  589.725805]  arch_call_rest_init+0x18/0x20
[  589.725808]  start_kernel+0x514/0x54c
[  589.725811] ---[ end trace bc4cd60b2035ae23 ]---

It’s similar to the following URL.
However, HDMI output and hot plug detect are working fine.

Could you please tell me about a workaround for this WARNING?
We have not made any specific SW changes related to HDMI.

2

Which board config is in use in this case?

3

Hi,WayneWWW.

Based on p3509-a02+p3767-0000.conf, but PINMUX_CONFIG,PMC_CONFIG is original. L4T 35.2.1.

4

Hi,

When you use Xavier NX devkit as carrier board + Orin NX, do you hit this issue?

5

Sorry, Xavier NX carrier board is not in hand at the moment.
And, I have never tried that.

6

I think xavier nx carrier board may not hit this issue. But I need double confirm on your side, so please do this test on this side as well.

7

Check whether the SDA and SCL of HDMI are connected inversely

1 Like
8

Okay, I will check when I get the Xavier NX carrier board back.

9

Hi, me_peng.
Thank you for your suggestion.
But we can see Display Name from EDID information.
So, SDA/SCI line seems fine.

a
a871×709 58.7 KB

11

I think xavier nx carrier board may not hit this issue.
But I need double confirm on your side, so please do this test on this side as well.

Hi, Xavier NX carrier board was returned to me today.
We use Xavier NX devkit as carrier board + Orin NX 8GB and confirmed that same issue occured in L4T 35.3.1.

[ 4354.081373] ------------[ cut here ]------------
[ 4354.081404] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[ 4354.090818] Modules linked in: hid_logitech_hidpp input_leds hid_logitech_dj fuse nvidia_modeset(O) loop bnep binfmt_misc snd_soc_tegra210_iqc snd_soc_tegra210_ope snd_soc_tegra186_asrc snd_soc_tegra186_dspk snd_soc_tegra186_arad snd_soc_tegra210_mvc snd_soc_tegra210_afc snd_soc_tegra210_dmic snd_soc_tegra210_adx snd_soc_tegra210_mixer snd_soc_tegra210_amx snd_soc_tegra210_i2s snd_soc_tegra210_sfc snd_soc_tegra210_admaif snd_soc_tegra_pcm aes_ce_blk crypto_simd cryptd aes_ce_cipher ghash_ce sha2_ce snd_soc_tegra_machine_driver snd_soc_spdif_tx sha256_arm64 sha1_ce rtl8822ce rtk_btusb btusb btrtl snd_soc_tegra210_adsp btbcm btintel userspace_alert snd_hda_codec_hdmi r8168 snd_soc_tegra_utils snd_soc_simple_card_utils snd_soc_tegra210_ahub snd_hda_tegra cfg80211 nvadsp tegra210_adma tegra_bpmp_thermal snd_hda_codec snd_hda_core r8169 nv_imx219 spi_tegra114 realtek nvidia(O) ina3221 pwm_fan nvgpu nvmap ip_tables x_tables
[ 4354.090983] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           O      5.10.104-tegra #1
[ 4354.090988] Hardware name: Unknown NVIDIA Orin NX Developer Kit/NVIDIA Orin NX Developer Kit, BIOS 3.1-32827747 03/19/2023
[ 4354.090994] pstate: 20400089 (nzCv daIf +PAN -UAO -TCO BTYPE=--)
[ 4354.090999] pc : tegra186_gpio_irq+0x1ac/0x1f0
[ 4354.091003] lr : tegra186_gpio_irq+0x11c/0x1f0
[ 4354.091006] sp : ffff800010003ef0
[ 4354.091009] x29: ffff800010003ef0 x28: ffff0c9d40daca60
[ 4354.091016] x27: ffffbb7aac9ccff8 x26: 0000000000000018
[ 4354.091023] x25: ffff0c9d45052880 x24: ffff0c9d450b4800
[ 4354.091029] x23: 000000000000000c x22: 000000000000004c
[ 4354.091035] x21: 00000000000000b9 x20: 0000000000000000
[ 4354.091041] x19: ffffbb7aabe7ee50 x18: 0000000000000000
[ 4354.091046] x17: 0000000000000000 x16: 0000000000000000
[ 4354.091052] x15: 0000000000000000 x14: ffffbb7aac8b2680
[ 4354.091058] x13: ffff5123fbdff000 x12: 000000003464d91d
[ 4354.091064] x11: 0000000000000040 x10: ffffbb7aac937a80
[ 4354.091070] x9 : ffffbb7aac937a78 x8 : ffff0c9d404b3930
[ 4354.091077] x7 : 0000000000000000 x6 : 0000000000000001
[ 4354.091082] x5 : 0000000000000000 x4 : 0000000000000000
[ 4354.091088] x3 : 0000000000000000 x2 : ffffbb7aaad4e170
[ 4354.091094] x1 : 000000000000004c x0 : 0000000000000000
[ 4354.091101] Call trace:
[ 4354.091106]  tegra186_gpio_irq+0x1ac/0x1f0
[ 4354.091115]  generic_handle_irq+0x40/0x60
[ 4354.091121]  __handle_domain_irq+0x70/0xd0
[ 4354.091127]  gic_handle_irq+0x68/0x134
[ 4354.091130]  el1_irq+0xd0/0x180
[ 4354.091138]  cpuidle_enter_state+0xb8/0x410
[ 4354.091142]  cpuidle_enter+0x40/0x60
[ 4354.091147]  call_cpuidle+0x44/0x80
[ 4354.091151]  do_idle+0x208/0x270
[ 4354.091154]  cpu_startup_entry+0x2c/0x70
[ 4354.091161]  rest_init+0xdc/0xe8
[ 4354.091169]  arch_call_rest_init+0x18/0x20
[ 4354.091173]  start_kernel+0x514/0x54c
[ 4354.091178] ---[ end trace 280ebbafdac94701 ]---

20230411_CPU_OrinNX8GB_Carrier_XavierNXEVK_full_dmesg.txt (79.7 KB)

12

If the system does not hang and hotplug still works fine, then this is not fatal.

13

Hi @WayneWWW
We encountered the same problem and it caused a panic loop when trying to restart.
Full log:
puttyorin.log (624.0 KB)

14

@cstdae Custom board or devkit?

15

This log file is from our custom board.
But we confirm kernel warning occurs in P3509 + P3767-0000 (16GB) case too.

16

Hi,

But the warning will not cause restart or hang on devkit. Please file a new topic for your issue.

17

@WayneWWW
@cstdae

Hi, We have also reproduced the panic loop in our CustomBoard today.
We have not made any changes to the SW or HW pin assignments from EVK about HDMI.

20230413_CustomBoard_insert_HDM_panic_loop_console_log.txt (584.8 KB)

18

We are checking this internally.

Will this cause system hang?

19

This reproduced before the first Ubuntu setup, so I could not check by command.
HPD interrupt is raised continuously and does not stop, so I think system hang. Unplugging/inserting the HDMI cable did not resolve the problem and nothing appeared on the screen.
It also continued to interrupt even after completely unplugging the HDMI cable. It is not chattering.

20

Hi,
For the record, we are having occurrences of this behaviour as well, when plugging/unplugging the HDMI cable on our carrier board. Several warnings are thrown and the number of warnings logged upon plugging/unplugging does not seem consistent. No HDMI output too, no screen detected.
We are using L4T 35.2.1.

21

[Update] After several modifications/tests, we do observe this warning when there is no device on the HDMI DDC I2C bus or more generally no device at the expected address or range of address. Still upon plugging/unplugging.
L4T version: 35.2.1.