WARNING occurs when plugin/out HDMI in OrinNX

we also found such similar issue when using p3509-a02+p3767-0000.conf on Orin NX 16G SOM, @WayneWWW do you have any update? Thanks.

Hi,

Does the warning cause system hang/ kernel panic on your side?

@WayneWWW if such happpened, in some case, such interrupts flush will result in system reboot.

@weileng could you share the monitor you are using that can reproduce this issue?

Hi Wayne

My test monitor is ThinkVision T27p-10. Thanks.

@weileng
Could you help me do beow test?

  1. Use the same monitor + devkit

  2. Run “sudo reboot” on your board for 10 times. See if you can see the gpio irq error and cause system reboot by watchdog timer. If it can,please tell me whether it is 100% happened or intermittent.

Wayne

Sorry, no devkit by hand currently. My test bed is cusomzied board + Orin NX 16G SOM. such issue doesn’t 100% happened. Directly command “sudo reboot” under system UI can’t duplicate this issue in my side. The corner case, re-flash image and the first time to re-enter system UI after system configuation, sometimes it will happen. Thanks.

> ▒▒[    5.478220] tegra-i2c 31e0000.i2c: I2C transfer timed out
> [    5.710075] nvidia: loading out-of-tree module taints kernel.
> [    5.711377] nvidia: module verification failed: signature and/or required key missing - tainting kernel
> [    5.766244] tegra-i2c 31e0000.i2c: I2C transfer timed out
> [    5.782687] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
> [    5.790355] imx219 9-0010: board setup failed
> [    5.790563] imx219: probe of 9-0010 failed with error -121
> [    5.802386] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
> [    5.807712] imx219 10-0010: board setup failed
> [    5.807910] imx219: probe of 10-0010 failed with error -121
> [    5.837264] iwlwifi 0001:03:00.0: api flags index 2 larger than supported by driver
> [    5.874228] tegra-i2c 31e0000.i2c: I2C transfer timed out
> [    6.278952] thermal thermal_zone9: failed to read out thermal zone (-61)
> [    6.746207] random: crng init done
> [    6.746325] random: 7 urandom warning(s) missed due to ratelimiting
> [    6.825378] using random self ethernet address
> [    6.825527] using random host ethernet address
> [    7.204381] using random self ethernet address
> [    7.204532] using random host ethernet address
> [    7.206837] IRQ 326: no longer affine to CPU4
> [    7.207016] CPU4: shutdown
> [    7.334815] IRQ 327: no longer affine to CPU5
> [    7.335064] CPU5: shutdown
> [    7.478837] IRQ 329: no longer affine to CPU6
> [    7.479025] CPU6: shutdown
> [    7.595868] IRQ 114: no longer affine to CPU7
> [    7.596413] IRQ 330: no longer affine to CPU7
> [    7.596762] CPU7: shutdown
> [   13.061651] Please complete system configuration setup on desktop to proceed...
> [   13.664859] ACPI: <n/a>: failed to evaluate _DSM (0x1001)
> [   13.665051] ACPI: <n/a>: failed to evaluate _DSM (0x1001)
> [  200.138220] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.138800] ---[ end trace e7b6f634cffb9927 ]---
> [  200.138973] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.139389] ---[ end trace e7b6f634cffb9928 ]---
> [  200.139531] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.139917] ---[ end trace e7b6f634cffb9929 ]---
> [  200.140063] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.140447] ---[ end trace e7b6f634cffb992a ]---
> [  200.140594] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.140981] ---[ end trace e7b6f634cffb992b ]---
> [  200.141129] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.141512] ---[ end trace e7b6f634cffb992c ]---
> [  200.141804] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.143274] ---[ end trace e7b6f634cffb992d ]---
> [  200.143835] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.152497] ---[ end trace e7b6f634cffb992e ]---
> [  200.157013] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.166320] ---[ end trace e7b6f634cffb992f ]---
> [  200.170840] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.180145] ---[ end trace e7b6f634cffb9930 ]---
> [  200.184663] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.193969] ---[ end trace e7b6f634cffb9931 ]---
> [  200.198492] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.207793] ---[ end trace e7b6f634cffb9932 ]---
> [  200.212312] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.221619] ---[ end trace e7b6f634cffb9933 ]---
> [  200.226138] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.235444] ---[ end trace e7b6f634cffb9934 ]---
> [  200.239962] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.249268] ---[ end trace e7b6f634cffb9935 ]---
> [  200.253796] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.263097] ---[ end trace e7b6f634cffb9936 ]---
> [  200.267617] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.276918] ---[ end trace e7b6f634cffb9937 ]---
> [  200.281443] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.290746] ---[ end trace e7b6f634cffb9938 ]---
> [  200.295263] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.304573] ---[ end trace e7b6f634cffb9939 ]---
> [  200.309088] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.318396] ---[ end trace e7b6f634cffb993a ]---
> [  200.322911] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.332222] ---[ end trace e7b6f634cffb993b ]---
> [  200.336738] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.346047] ---[ end trace e7b6f634cffb993c ]---
> [  200.350562] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.359869] ---[ end trace e7b6f634cffb993d ]---
> [  200.364388] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.373698] ---[ end trace e7b6f634cffb993e ]---
> [  200.378212] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.387520] ---[ end trace e7b6f634cffb993f ]---
> [  200.392038] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.401344] ---[ end trace e7b6f634cffb9940 ]---
> [  200.405862] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.415168] ---[ end trace e7b6f634cffb9941 ]---
> [  200.419687] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.428996] ---[ end trace e7b6f634cffb9942 ]---
> [  200.433513] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.442821] ---[ end trace e7b6f634cffb9943 ]---
> [  200.447337] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.456647] ---[ end trace e7b6f634cffb9944 ]---
> [  200.461162] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.470472] ---[ end trace e7b6f634cffb9945 ]---
> [  200.474988] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.484295] ---[ end trace e7b6f634cffb9946 ]---
> [  200.488813] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.498122] ---[ end trace e7b6f634cffb9947 ]---
> [  200.502637] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.511951] ---[ end trace e7b6f634cffb9948 ]---
> [  200.516522] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.525779] ---[ end trace e7b6f634cffb9949 ]---
> [  200.530301] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.539593] ---[ end trace e7b6f634cffb994a ]---
> [  200.544113] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.553420] ---[ end trace e7b6f634cffb994b ]---
> [  200.557938] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.567246] ---[ end trace e7b6f634cffb994c ]---
> [  200.571763] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.581069] ---[ end trace e7b6f634cffb994d ]---
> [  200.585586] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.594896] ---[ end trace e7b6f634cffb994e ]---
> [  200.599413] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.608721] ---[ end trace e7b6f634cffb994f ]---
> [  200.613237] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.622547] ---[ end trace e7b6f634cffb9950 ]---
> [  200.627064] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.636372] ---[ end trace e7b6f634cffb9951 ]---
> [  200.640888] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.650195] ---[ end trace e7b6f634cffb9952 ]---
> [  200.654713] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.664023] ---[ end trace e7b6f634cffb9953 ]---
> [  200.668538] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.677845] ---[ end trace e7b6f634cffb9954 ]---
> [  200.682363] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.691671] ---[ end trace e7b6f634cffb9955 ]---
> [  200.696186] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.705497] ---[ end trace e7b6f634cffb9956 ]---
> [  200.710013] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.719320] ---[ end trace e7b6f634cffb9957 ]---
> [  200.723837] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.733144] ---[ end trace e7b6f634cffb9958 ]---
> [  200.737662] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.746971] ---[ end trace e7b6f634cffb9959 ]---
> [  200.751487] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.760794] ---[ end trace e7b6f634cffb995a ]---
> [  200.765311] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.774620] ---[ end trace e7b6f634cffb995b ]---
> [  200.779138] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.788451] ---[ end trace e7b6f634cffb995c ]---
> [  200.792976] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.802275] ---[ end trace e7b6f634cffb995d ]---
> [  200.806798] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.816100] ---[ end trace e7b6f634cffb995e ]---
> [  200.820620] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.829918] ---[ end trace e7b6f634cffb995f ]---
> [  200.834444] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.843746] ---[ end trace e7b6f634cffb9960 ]---
> [  200.848267] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.857569] ---[ end trace e7b6f634cffb9961 ]---
> [  200.862092] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.871395] ---[ end trace e7b6f634cffb9962 ]---
> [  200.875919] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.885220] ---[ end trace e7b6f634cffb9963 ]---
> [  200.889745] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.899048] ---[ end trace e7b6f634cffb9964 ]---
> [  200.903574] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.912870] ---[ end trace e7b6f634cffb9965 ]---
> [  200.917392] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.926697] ---[ end trace e7b6f634cffb9966 ]---
> [  200.931217] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.940523] ---[ end trace e7b6f634cffb9967 ]---
> [  200.945045] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.954345] ---[ end trace e7b6f634cffb9968 ]---
> [  200.958867] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.968174] ---[ end trace e7b6f634cffb9969 ]---
> [  200.972692] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.981999] ---[ end trace e7b6f634cffb996a ]---
> [  200.986518] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  200.995822] ---[ end trace e7b6f634cffb996b ]---
> [  201.000342] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.009651] ---[ end trace e7b6f634cffb996c ]---
> [  201.014169] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.023471] ---[ end trace e7b6f634cffb996d ]---
> [  201.027993] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.037300] ---[ end trace e7b6f634cffb996e ]---
> [  201.041819] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.051123] ---[ end trace e7b6f634cffb996f ]---
> [  201.055643] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.064947] ---[ end trace e7b6f634cffb9970 ]---
> [  201.069475] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.078774] ---[ end trace e7b6f634cffb9971 ]---
> [  201.083292] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.092597] ---[ end trace e7b6f634cffb9972 ]---
> [  201.097118] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.106423] ---[ end trace e7b6f634cffb9973 ]---
> [  201.110943] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.120250] ---[ end trace e7b6f634cffb9974 ]---
> [  201.124767] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.134072] ---[ end trace e7b6f634cffb9975 ]---
> [  201.138593] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.147898] ---[ end trace e7b6f634cffb9976 ]---
> [  201.152418] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.161721] ---[ end trace e7b6f634cffb9977 ]---
> [  201.166243] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.175546] ---[ end trace e7b6f634cffb9978 ]---
> [  201.180067] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.189374] ---[ end trace e7b6f634cffb9979 ]---
> [  201.193895] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.203198] ---[ end trace e7b6f634cffb997a ]---
> [  201.207721] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.217026] ---[ end trace e7b6f634cffb997b ]---
> [  201.221543] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.230848] ---[ end trace e7b6f634cffb997c ]---
> [  201.235367] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.244671] ---[ end trace e7b6f634cffb997d ]---
> [  201.249192] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.258497] ---[ end trace e7b6f634cffb997e ]---
> [  201.263022] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.272321] ---[ end trace e7b6f634cffb997f ]---
> [  201.276842] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.286147] ---[ end trace e7b6f634cffb9980 ]---
> [  201.290672] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.299972] ---[ end trace e7b6f634cffb9981 ]---
> [  201.304493] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.313798] ---[ end trace e7b6f634cffb9982 ]---
> [  201.318316] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.327625] ---[ end trace e7b6f634cffb9983 ]---
> [  201.332143] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.341449] ---[ end trace e7b6f634cffb9984 ]---
> [  201.345968] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.355273] ---[ end trace e7b6f634cffb9985 ]---
> [  201.359793] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.369098] ---[ end trace e7b6f634cffb9986 ]---
> [  201.373618] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.382922] ---[ end trace e7b6f634cffb9987 ]---
> [  201.387447] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.396746] ---[ end trace e7b6f634cffb9988 ]---
> [  201.401268] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.410574] ---[ end trace e7b6f634cffb9989 ]---
> [  201.415093] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.424397] ---[ end trace e7b6f634cffb998a ]---
> [  201.428917] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.438225] ---[ end trace e7b6f634cffb998b ]---
> [  201.442744] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.452048] ---[ end trace e7b6f634cffb998c ]---
> [  201.456597] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.465879] ---[ end trace e7b6f634cffb998d ]---
> [  201.470403] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.479697] ---[ end trace e7b6f634cffb998e ]---
> [  201.484223] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.493523] ---[ end trace e7b6f634cffb998f ]---
> [  201.498043] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.507346] ---[ end trace e7b6f634cffb9990 ]---
> [  201.511869] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.521194] ---[ end trace e7b6f634cffb9991 ]---
> [  201.525703] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.535006] ---[ end trace e7b6f634cffb9992 ]---
> [  201.539523] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.548826] ---[ end trace e7b6f634cffb9993 ]---
> [  201.553346] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.562651] ---[ end trace e7b6f634cffb9994 ]---
> [  201.567168] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.576473] ---[ end trace e7b6f634cffb9995 ]---
> [  201.580997] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.581167] ---[ end trace e7b6f634cffb9996 ]---
> [  201.581182] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.581331] ---[ end trace e7b6f634cffb9997 ]---
> [  201.581345] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.581489] ---[ end trace e7b6f634cffb9998 ]---
> [  201.581504] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.581618] ---[ end trace e7b6f634cffb9999 ]---
> [  201.581636] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.581753] ---[ end trace e7b6f634cffb999a ]---
> [  201.581768] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.581882] ---[ end trace e7b6f634cffb999b ]---
> [  201.581897] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.582040] ---[ end trace e7b6f634cffb999c ]---
> [  201.582056] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.582191] ---[ end trace e7b6f634cffb999d ]---
> [  201.582206] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.582387] ---[ end trace e7b6f634cffb999e ]---
> [  201.582401] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.582520] ---[ end trace e7b6f634cffb999f ]---
> [  201.582536] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.582704] ---[ end trace e7b6f634cffb99a0 ]---
> [  201.582719] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.582870] ---[ end trace e7b6f634cffb99a1 ]---
> [  201.582885] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.583011] ---[ end trace e7b6f634cffb99a2 ]---
> [  201.583027] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.583186] ---[ end trace e7b6f634cffb99a3 ]---
> [  201.583201] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.583339] ---[ end trace e7b6f634cffb99a4 ]---
> [  201.583353] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.583469] ---[ end trace e7b6f634cffb99a5 ]---
> [  201.583486] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.583601] ---[ end trace e7b6f634cffb99a6 ]---
> [  201.583616] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.825297] ---[ end trace e7b6f634cffb99a7 ]---
> [  201.829879] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.839195] ---[ end trace e7b6f634cffb99a8 ]---
> [  201.843671] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.852977] ---[ end trace e7b6f634cffb99a9 ]---
> [  201.857493] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.866799] ---[ end trace e7b6f634cffb99aa ]---
> [  201.871319] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.880624] ---[ end trace e7b6f634cffb99ab ]---
> [  201.885144] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.894447] ---[ end trace e7b6f634cffb99ac ]---
> [  201.898969] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.908272] ---[ end trace e7b6f634cffb99ad ]---
> [  201.912793] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.922097] ---[ end trace e7b6f634cffb99ae ]---
> [  201.926622] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.935923] ---[ end trace e7b6f634cffb99af ]---
> [  201.940444] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.949752] ---[ end trace e7b6f634cffb99b0 ]---
> [  201.954285] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.963577] ---[ end trace e7b6f634cffb99b1 ]---
> [  201.968111] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.977423] ---[ end trace e7b6f634cffb99b2 ]---
> [  201.981938] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  201.991230] ---[ end trace e7b6f634cffb99b3 ]---
> [  201.995745] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.005022] ---[ end trace e7b6f634cffb99b4 ]---
> [  202.005044] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.018834] ---[ end trace e7b6f634cffb99b5 ]---
> [  202.018864] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.032664] ---[ end trace e7b6f634cffb99b6 ]---
> [  202.037196] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.046497] ---[ end trace e7b6f634cffb99b7 ]---
> [  202.046518] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.046631] ---[ end trace e7b6f634cffb99b8 ]---
> [  202.046646] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.046755] ---[ end trace e7b6f634cffb99b9 ]---
> [  202.046770] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.087937] ---[ end trace e7b6f634cffb99ba ]---
> [  202.092522] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.101833] ---[ end trace e7b6f634cffb99bb ]---
> [  202.106343] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.115651] ---[ end trace e7b6f634cffb99bc ]---
> [  202.120172] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.129478] ---[ end trace e7b6f634cffb99bd ]---
> [  202.133991] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
> [  202.143301] ---[ end trace e7b6f634cffb99be ]---
> [  202.147818] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0

Hi @weileng

Sorry that I can only discuss this issue with devkit user. I saw this issue happened on some custom boards before, but turned out this is their hardware design issue.

Thus, I need you to make sure whether devkit can reproduce this issue with same monitor.

Also, could you check if the “power save” of the monitor is related to this issue?

This is also something observed by other end users too.

For example, your issue happened after 200 second after boot up. Looks related to something triggered, maybe also the power save?

Hi @WayneWWW

Thanks for your replay. Could you please elaborate “power save” related issue?
two questions please give your comments, thanks.
#1 HDMI hotplug trigger kernel warning “tegra186_gpio_irq+0x1ac/0x1f0”, Is this state normal?
#2 What case will trigger kernel warning “tegra186_gpio_irq+0x1ac/0x1f0” on Orin NX?
The same monitor and the same motherboard with Xavier NX 8G/16G SOM has NO such issue.

Hi @weileng

  1. If the hotplug case didn’t lead to kernel panic but just 1~2 times spew, then it is not an error.

  2. So far what I can see, there are few cases.
    → One user said when the HDMI monitor enters powe save (screen goes blank due to inactive), then it would cause this error
    → Another user’s custom board will hit issue when resume from sc7 suspend mode
    → Another user said some of his/her monitors would hit this issue when keep running sudo reboot multiple times.
    Some of them said this issue could be reproduced with NV devkit (p3509 XNX devkit) but must use specific monitors. Not every monitor can reproduce this issue. That was why I cannot check this for now.

  3. There is no need to compare the XNX case with Orin. The driver structure is totally different and none of the previous jetson (TX1/TX2/Xavier) ever uses current display driver. I am not saying it has no issue. I mean the comparison does not mean anything. What we need to do here is focus on how to reproduce this issue on devkit. What setup… How to trigger.

Thank you Wayne!

If the hotplug case didn’t lead to kernel panic but just 1~2 times spew, then it is not an error.

My test bed on Orin NX 16G SOM

  1. during HDMI hotplug, it will trigger 1~2 times “tegra186_gpio_irq+0x1ac/0x1f0” kernel error warning, which won’t lead to kernel panic.
  2. System auto blank screen when Power saving( 5 minutes setting by default) will trigger 1~2 times “tegra186_gpio_irq+0x1ac/0x1f0” kernel error warning, which won’t lead to kernel panic.
  3. System reboot under UI won’t trigger “tegra186_gpio_irq+0x1ac/0x1f0” kernel error warning
  4. The corner case will trgger GPIO warning flush is that:
    Re-flash Orin NX image and the first time to re-enter system UI after system configuation, sometimes it will happen.

After I got devkit, I will retest it on Orin NX with this type 4K monitor.

1 Like

Hi ,
We have same kernel dump message on AGX Orin HDMI hot-plug.
We do modify pinmux dtis, gpio dtsi in Linux_for_Tegra/bootloader relative file, change dcb file to hdmi, and also have os_gpio_hotplug in devicetree file.
display@13800000 {
status = “okay”;
os_gpio_hotplug_a = <&tegra_main_gpio TEGRA234_MAIN_GPIO(M, 0) GPIO_ACTIVE_HIGH>;
};

Also, after system boot-up, we can not find gpio M,0 usage status in /sys/kernel/debug/gpio.
Try to export gpio M,0 to /sys/class/gpio/export , then kernel dump message disappear.

By tracing nvidia display driver, we found gpio request may not used?? (We add debug message in nvidia display driver)

Do nvidia guys any ideas?

Hi,

Which display driver are you tracing here?

Also, after you export M,0 in gpio sysfs, is your HDMI hotplug still working fine?

Hi WayneWWW,

yes, after export M,0 in gpio sysfs, HDMI hotplut still working fine.
The display driver is NVIDIA-kernel-module-source-TempVersion .

ps: to export M,0 , then unexport M,0 , kernel dump and error message disappear too. and hdmi hot-plug working fine.

Regards

@WayneWWW

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

Hi, After long investigation and aging,
We reproduced that warning cause system hang/kernel panic in OrinNX 8GB + XavierNX EVK environment.
Reproduce rate is 100%.

Step 1. Connect [OrinNX 8GB + XavierNX EVK] and Display with HDMI Cable.
Step 2. Connect [OrinNX 8GB + XavierNX EVK] and HostPC with UART Cable for console login.
Step 3  Power ON Display and [OrinNX 8GB + XavierNX EVK]
Step 3. Confirm that Ubuntu login prompt appeas on Display.
Step 4. Login from console, and stop gdm by following command.

# systemctl stop gdm

Step 5. Unplug HDMI Cable from XavierNX EVK HDMI port.

Step 6. Reproduce kernel WARNING releatedly and cause kernel panic.

[   61.878407] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[   61.888295] ---[ end trace b6b8c2c9494bf98d ]---
[   61.893129] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[   61.902842] ---[ end trace b6b8c2c9494bf98e ]---
[   61.907635] WARNING: CPU: 0 PID: 0 at drivers/gpio/gpio-tegra186.c:937 tegra186_gpio_irq+0x1ac/0x1f0
[   61.917320] ---[ end trace b6b8c2c9494bf98f ]---
...

We checked following 3 display and result is same.

・LG electronics 23M45D-B
・ViewSonic VA2719-2K-SMHD-7
・ViewSonic VX2882-4KP

Same situation is reproduced by CustomBoard only pluggig/unplugging HDMI Cable.
I think root cause is same with this problem.

This is not HW design issue.
Please reproduce and fix by internal team.

20230601_CPU_OrinNX8GB_Xavier_EVK_HDMI_warning_hang_log_LG_23M45.txt (625.2 KB)

For all who are reading this post.
I just want to share some points and explain something here.

  1. this tegra186_gpio_irq is a common warning that could be generated when the hotplug interrupt has some abnormal handle. When too many abnormal interrupt comes, it will lead to kernel panic.

  2. Based on (1), actually you cannot take everything that generated “tegra186_gpio_irq” as same issue. My point here is the root cause of “tegra186_gpio_irq” could be various. Fixing one case does not mean you will be fine in another case.

For example, we see some customer’s board indeed has hardware design problem so it will lead to tegra186_gpio_irq when enter suspend mode. The root cause of such issue is the power sequence. And this case won’t happen on devkit.

Another example here is @shinichiro.adachi tried to reproduce this issue by disabling gdm.
Honestly, I don’t think disabling gdm is a useful case here as Orin does not support framebuffer console yet. I don’t think your real usecase will be same steps as what you shared either.

Thus, back to what I want to say here. Please do not wasting your time just trying to create a scenario that can print tegra186_gpio_irq on devkit and use that to persuade me this is NV issue. If your usecase does not make sense, then it does not worth checking. Our internal team will still ignore what you want us to check.
More importantly, it may not be same issue as what you saw on your custom board.

As for how to check this issue

  1. If you can reproduce this issue on devkit with a standard usecase, please help check if this is something that could only be reproduced on specific monitors. If it is, please help probe the signal of HDMI_EN, HPD, DDC DAT and CLK signal as I don’t have the same monitor as your case.

  2. If this issue could not reproduce on devkit, and only happened on your custom board, then please again, help probe HDMI_EN, HPD, DDC DAT and CLK signal as I don’t have your board.

@shinichiro.adachi. Sorry that what you are doing here is not logical. Our internal team will not check what you told here.
If you still don’t understand what I mean, I can explain more.

I understand that tegra186_gpio_irq can be caused by many factors.
I understand that you want to separate the various issues.

This Plugin/Out issue may not be related to the irq issue that occurs when entering suspend mode.

However, I think this Plugin/Out issue is related to the irq issue with stopping gdm and unplugging the HDMI cable.

The reason is that the trigger is ultimately triggered by unplugging the HDMI cable.
Also, This problem is already reproduced in EVK, not CustomBoard.

I understand that it is difficult to check and debug each customer’s HW design individually.

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.

What we need to do here is focus on how to reproduce this issue on devkit. What setup… How to trigger.

Sorry that what you are doing here is not logical.

You said, “What we need to do here is focus on how to reproduce this issue on devkit.”

Therefore, at your own request, We purchased EVK, Spend time and money, finally found a way to reproduce it with EVK.

And if EVK finally has a problem, will they further ask the user to Debug it?
You don’t even try to see if it occurs in your Display?

If it occurs in EVK, NVIDIA should be a little more proactive and take the initiative to resolve it.

I don’t think disabling gdm is an abonormal action.

For example, if the user wanted to use EVK in clamshell mode, would disable gdm and unplug the HDMI cable.

Hi,

I am okay to check gdm case. Hope you didn’t get misunderstood.

But you just need to know.

  1. Even we resolve anything on our side, it didn’t mean your case on your board will be resolved.
    My point is, I don’t want to waste your time waiting for me to resolve some usecase that could be totally useless on your side. For example, we spend another month to resolving this issue with gdm, but turns out this totally cannot fix your issue on your board.
    We would still need you to dump hardware signal on your board then. If so, why not just dump the hardware signal from your board right now?

  2. Also, we are working on enabling framebuffer console feature for now. Thus, lots of changes will be merged at this time and this is related to your “disable gdm” case. It is pointless to check gdm issue for now. We may check it in next release, but again, your issue may not have progress here when you wait for us enabling framebuffer console.

Hope you really understand what I am talking about. I am trying to resolve an issue that really matters to your case. Not some pointless usecase.

I was able to reproduce the panic loop in EVK under the same environment as before.

The difference is using EVK, not CustomBoard.

We use Xavier NX devkit as carrier board + Orin NX 8GB.
Reproduce rate is 100%.

1. Reflash EVK+SSD Firmware from HostPC by microUSB port.

2. Boot EVK without connecting HDMI cable.

3. Insert HDMI cable when the following message appears on the serial console.

[   17.783565] Please complete system configuration setup on the serial port provided 
by Jetson's USB device mode connection. e.g. /dev/ttyACMx where x can 0, 1, 2 etc.

4. Reproduce kernel WARNING repeatedly and cause kernel panic.

This is identical situation I saw when I first posted this POST.
Therefore, we have not found any new cases of WARNING.

I wonder If HPD interrupt occurs while no GUI process such as gdm is running, a panic loop may occur.

20230607_CPU_OrinNX8GB_Xavier_EVK_HDMI_warning_hang_log_before_setup.txt (590.7 KB)