LE11/12: CIR Stops Working after Upgrade

las1 · July 16, 2024 at 9:12 PM

I've been troubleshooting an issue for months now and have gotten nowhere. I recently hoped that building a custom image with kernel debug symbols enabled would provide some insight to my issue. Since I don't have ever see a coredump or anything I'm guessing it was a pointless effort...

Before opening an issue in git, I figured I should check if there is any additional information or things I could try to be able to include as much information in the report as possible.

I have multiple 6th generation Intel Nucs with a nuvoton consumer infrared module (built-in) that has functioned for many years on LE7/8/9/10 without any issue. After an upgrade to either LE11/12/13 (basically kernel 6.x+) I see that for whatever reason my remote stops working--randomly. The issue ususally occurs if quickly after boot I start scrolling through my PVR/TV menu. Using ir-keytable -t after I notice no input is being recognized and to look for button presses, nothing shows up.

To fix this I can simply unload and reload the kernel module (nuvoton_cir) and everything works as normal including ir-keytable populating properly. Generally after performing this it will work until it's restarted--but not always. Kodi debug logs show absolutely no issue/change when the problem occurs. dmesg output also isn't of much use:

Quote

[ 2.977534] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7
[ 2.977577] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
[ 2.977627] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
[ 3.028650] input: eventlircd as /devices/virtual/input/input10
[ 6.466788] e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 6.466879] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 6.470466] 8021q: 802.1Q VLAN Support v1.8
[ 15.065998] Bluetooth: RFCOMM TTY layer initialized
[ 15.066019] Bluetooth: RFCOMM socket layer initialized
[ 15.066023] Bluetooth: RFCOMM ver 1.11
[ 19.607148] nuvoton-cir 00:01: RX FIFO overrun detected, flushing data!
[ 20.474927] nuvoton-cir 00:01: RX FIFO overrun detected, flushing data!
[ 417.036419] nuvoton-cir 00:01: found NCT6776F or compatible: chip id: 0xc3 0x33
[ 417.036758] Registered IR keymap rc-rc6-mce
[ 417.036836] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:01/rc/rc0
[ 417.036935] rc rc0: lirc_dev: driver nuvoton-cir registered at minor = 0, raw IR receiver, no transmitter
[ 417.037041] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:01/rc/rc0/input11
[ 417.037392] nuvoton-cir 00:01: driver has been successfully loaded
[ 417.194484] input: eventlircd as /devices/virtual/input/input12

Display More

The issue did happen right at the second RX FIFO message. The next message (417.036419) is me unloading/reloading the kernel module. What's strange is if I sit and jam a bunch of input buttons I see this message, even though it doesn't freeze. Looking through source code, it looks like this is just an informative message maybe?

Lircd is not setup/configured/running and this is with a new default install of LE11/12/13.

Quote

huron:~ # ir-keytable --verbose
Found device /sys/class/rc/rc0/
Parsing uevent /sys/class/rc/rc0/lirc0/uevent
/sys/class/rc/rc0/lirc0/uevent uevent MAJOR=251
/sys/class/rc/rc0/lirc0/uevent uevent MINOR=0
/sys/class/rc/rc0/lirc0/uevent uevent DEVNAME=lirc0
Input sysfs node is /sys/class/rc/rc0/input4/
Event sysfs node is /sys/class/rc/rc0/input4/event4/
Parsing uevent /sys/class/rc/rc0/input4/event4/uevent
/sys/class/rc/rc0/input4/event4/uevent uevent MAJOR=13
/sys/class/rc/rc0/input4/event4/uevent uevent MINOR=68
/sys/class/rc/rc0/input4/event4/uevent uevent DEVNAME=input/event4
Parsing uevent /sys/class/rc/rc0/uevent
/sys/class/rc/rc0/uevent uevent NAME=rc-rc6-mce
/sys/class/rc/rc0/uevent uevent DRV_NAME=nuvoton-cir
/sys/class/rc/rc0/uevent uevent DEV_NAME=Nuvoton w836x7hg Infrared Remote Transceiver
input device is /dev/input/event4
/sys/class/rc/rc0/protocols protocol rc-5 (disabled)
/sys/class/rc/rc0/protocols protocol nec (enabled)
/sys/class/rc/rc0/protocols protocol rc-6 (enabled)
/sys/class/rc/rc0/protocols protocol jvc (disabled)
/sys/class/rc/rc0/protocols protocol sony (disabled)
/sys/class/rc/rc0/protocols protocol rc-5-sz (disabled)
/sys/class/rc/rc0/protocols protocol sanyo (disabled)
/sys/class/rc/rc0/protocols protocol sharp (disabled)
/sys/class/rc/rc0/protocols protocol mce_kbd (disabled)
/sys/class/rc/rc0/protocols protocol xmp (disabled)
/sys/class/rc/rc0/protocols protocol imon (disabled)
/sys/class/rc/rc0/protocols protocol rc-mm (disabled)
/sys/class/rc/rc0/protocols protocol lirc (enabled)
Found /sys/class/rc/rc0/ with:
Name: Nuvoton w836x7hg Infrared Remote Transceiver
Driver: nuvoton-cir
Default keymap: rc-rc6-mce
Input device: /dev/input/event4
LIRC device: /dev/lirc0
Attached BPF protocols:
Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm
Enabled kernel protocols: lirc nec rc-6
bus: 25, vendor/product: 1050:00c3, version: 0x0033
Repeat delay = 500 ms, repeat period = 125 ms
huron:~/.cache # ir-keytable -r
scancode 0x80d800 = KEY_0 (0x0b)
scancode 0x80d801 = KEY_1 (0x02)
scancode 0x80d802 = KEY_2 (0x03)
scancode 0x80d803 = KEY_3 (0x04)
scancode 0x80d804 = KEY_4 (0x05)
scancode 0x80d805 = KEY_5 (0x06)
scancode 0x80d806 = KEY_6 (0x07)
scancode 0x80d807 = KEY_7 (0x08)
scancode 0x80d808 = KEY_8 (0x09)
scancode 0x80d809 = KEY_9 (0x0a)
scancode 0x80d80e = KEY_MUTE (0x71)
scancode 0x80d810 = KEY_VOLUMEUP (0x73)
scancode 0x80d811 = KEY_VOLUMEDOWN (0x72)
scancode 0x80d812 = KEY_CHANNELUP (0x192)
scancode 0x80d813 = KEY_CHANNELDOWN (0x193)
scancode 0x80d814 = KEY_FASTFORWARD (0xd0)
scancode 0x80d815 = KEY_REWIND (0xa8)
scancode 0x80d817 = KEY_RECORD (0xa7)
scancode 0x80d819 = KEY_STOP (0x80)
scancode 0x80d81a = KEY_NEXT (0x197)
scancode 0x80d81b = KEY_PREVIOUS (0x19c)
scancode 0x80d81e = KEY_UP (0x67)
scancode 0x80d81f = KEY_DOWN (0x6c)
scancode 0x80d820 = KEY_LEFT (0x69)
scancode 0x80d821 = KEY_RIGHT (0x6a)
scancode 0x80d822 = KEY_OK (0x160)
scancode 0x80d823 = KEY_EXIT (0xae)
scancode 0x80d826 = KEY_INFO (0x166)
scancode 0x80d864 = KEY_MEDIA (0xe2)
scancode 0x80d86e = KEY_FULL_SCREEN (0x174)
scancode 0x80d86f = KEY_EPG (0x16d)
scancode 0x80d870 = KEY_PLAYPAUSE (0xa4)
scancode 0x800f0400 = KEY_NUMERIC_0 (0x200)
scancode 0x800f0401 = KEY_NUMERIC_1 (0x201)
scancode 0x800f0402 = KEY_NUMERIC_2 (0x202)
scancode 0x800f0403 = KEY_NUMERIC_3 (0x203)
scancode 0x800f0404 = KEY_NUMERIC_4 (0x204)
scancode 0x800f0405 = KEY_NUMERIC_5 (0x205)
scancode 0x800f0406 = KEY_NUMERIC_6 (0x206)
scancode 0x800f0407 = KEY_NUMERIC_7 (0x207)
scancode 0x800f0408 = KEY_NUMERIC_8 (0x208)
scancode 0x800f0409 = KEY_NUMERIC_9 (0x209)
scancode 0x800f040a = KEY_DELETE (0x6f)
scancode 0x800f040b = KEY_ENTER (0x1c)
scancode 0x800f040c = KEY_SLEEP (0x8e)
scancode 0x800f040d = KEY_MEDIA (0xe2)
scancode 0x800f040e = KEY_MUTE (0x71)
scancode 0x800f040f = KEY_INFO (0x166)
scancode 0x800f0410 = KEY_VOLUMEUP (0x73)
scancode 0x800f0411 = KEY_VOLUMEDOWN (0x72)
scancode 0x800f0412 = KEY_CHANNELUP (0x192)
scancode 0x800f0413 = KEY_CHANNELDOWN (0x193)
scancode 0x800f0414 = KEY_FASTFORWARD (0xd0)
scancode 0x800f0415 = KEY_REWIND (0xa8)
scancode 0x800f0416 = KEY_PLAY (0xcf)
scancode 0x800f0417 = KEY_RECORD (0xa7)
scancode 0x800f0418 = KEY_PAUSE (0x77)
scancode 0x800f0419 = KEY_STOP (0x80)
scancode 0x800f041a = KEY_NEXT (0x197)
scancode 0x800f041b = KEY_PREVIOUS (0x19c)
scancode 0x800f041c = KEY_NUMERIC_POUND (0x20b)
scancode 0x800f041d = KEY_NUMERIC_STAR (0x20a)
scancode 0x800f041e = KEY_UP (0x67)
scancode 0x800f041f = KEY_DOWN (0x6c)
scancode 0x800f0420 = KEY_LEFT (0x69)
scancode 0x800f0421 = KEY_RIGHT (0x6a)
scancode 0x800f0422 = KEY_OK (0x160)
scancode 0x800f0423 = KEY_EXIT (0xae)
scancode 0x800f0424 = KEY_DVD (0x185)
scancode 0x800f0425 = KEY_TUNER (0x182)
scancode 0x800f0426 = KEY_EPG (0x16d)
scancode 0x800f0427 = KEY_FULL_SCREEN (0x174)
scancode 0x800f0432 = KEY_MODE (0x175)
scancode 0x800f0433 = KEY_PRESENTATION (0x1a9)
scancode 0x800f0434 = KEY_EJECTCD (0xa1)
scancode 0x800f043a = KEY_BRIGHTNESSUP (0xe1)
scancode 0x800f0446 = KEY_TV (0x179)
scancode 0x800f0447 = KEY_AUDIO (0x188)
scancode 0x800f0448 = KEY_PVR (0x16e)
scancode 0x800f0449 = KEY_CAMERA (0xd4)
scancode 0x800f044a = KEY_VIDEO (0x189)
scancode 0x800f044c = KEY_LANGUAGE (0x170)
scancode 0x800f044d = KEY_TITLE (0x171)
scancode 0x800f044e = KEY_PRINT (0xd2)
scancode 0x800f0450 = KEY_RADIO (0x181)
scancode 0x800f045a = KEY_SUBTITLE (0x172)
scancode 0x800f045b = KEY_RED (0x18e)
scancode 0x800f045c = KEY_GREEN (0x18f)
scancode 0x800f045d = KEY_YELLOW (0x190)
scancode 0x800f045e = KEY_BLUE (0x191)
scancode 0x800f0465 = KEY_POWER2 (0x164)
scancode 0x800f0469 = KEY_MESSENGER (0x1ae)
scancode 0x800f046e = KEY_PLAYPAUSE (0xa4)
scancode 0x800f046f = KEY_PLAYER (0x183)
scancode 0x800f0480 = KEY_BRIGHTNESSDOWN (0xe0)
scancode 0x800f0481 = KEY_PLAYPAUSE (0xa4)
scancode 0x800f7400 = KEY_NUMERIC_0 (0x200)
scancode 0x800f7401 = KEY_NUMERIC_1 (0x201)
scancode 0x800f7402 = KEY_NUMERIC_2 (0x202)
scancode 0x800f7403 = KEY_NUMERIC_3 (0x203)
scancode 0x800f7404 = KEY_NUMERIC_4 (0x204)
scancode 0x800f7405 = KEY_NUMERIC_5 (0x205)
scancode 0x800f7406 = KEY_NUMERIC_6 (0x206)
scancode 0x800f7407 = KEY_NUMERIC_7 (0x207)
scancode 0x800f7408 = KEY_NUMERIC_8 (0x208)
scancode 0x800f7409 = KEY_NUMERIC_9 (0x209)
scancode 0x800f740a = KEY_DELETE (0x6f)
scancode 0x800f740b = KEY_ENTER (0x1c)
scancode 0x800f740c = KEY_SLEEP (0x8e)
scancode 0x800f740d = KEY_MEDIA (0xe2)
scancode 0x800f740e = KEY_MUTE (0x71)
scancode 0x800f740f = KEY_INFO (0x166)
scancode 0x800f7410 = KEY_VOLUMEUP (0x73)
scancode 0x800f7411 = KEY_VOLUMEDOWN (0x72)
scancode 0x800f7412 = KEY_CHANNELUP (0x192)
scancode 0x800f7413 = KEY_CHANNELDOWN (0x193)
scancode 0x800f7414 = KEY_FASTFORWARD (0xd0)
scancode 0x800f7415 = KEY_REWIND (0xa8)
scancode 0x800f7416 = KEY_PLAY (0xcf)
scancode 0x800f7417 = KEY_RECORD (0xa7)
scancode 0x800f7418 = KEY_PAUSE (0x77)
scancode 0x800f7419 = KEY_STOP (0x80)
scancode 0x800f741a = KEY_NEXT (0x197)
scancode 0x800f741b = KEY_PREVIOUS (0x19c)
scancode 0x800f741c = KEY_NUMERIC_POUND (0x20b)
scancode 0x800f741d = KEY_NUMERIC_STAR (0x20a)
scancode 0x800f741e = KEY_UP (0x67)
scancode 0x800f741f = KEY_DOWN (0x6c)
scancode 0x800f7420 = KEY_LEFT (0x69)
scancode 0x800f7421 = KEY_RIGHT (0x6a)
scancode 0x800f7422 = KEY_OK (0x160)
scancode 0x800f7423 = KEY_EXIT (0xae)
scancode 0x800f7424 = KEY_DVD (0x185)
scancode 0x800f7425 = KEY_RED (0x18e)
scancode 0x800f7426 = KEY_YELLOW (0x190)
scancode 0x800f7427 = KEY_FULL_SCREEN (0x174)
scancode 0x800f7428 = KEY_EJECTCD (0xa1)
scancode 0x800f7432 = KEY_MODE (0x175)
scancode 0x800f7433 = KEY_PRESENTATION (0x1a9)
scancode 0x800f743a = KEY_BRIGHTNESSUP (0xe1)
scancode 0x800f7446 = KEY_TV (0x179)
scancode 0x800f7447 = KEY_AUDIO (0x188)
scancode 0x800f7448 = KEY_PVR (0x16e)
scancode 0x800f7449 = KEY_CAMERA (0xd4)
scancode 0x800f744a = KEY_VIDEO (0x189)
scancode 0x800f744c = KEY_LANGUAGE (0x170)
scancode 0x800f744e = KEY_PRINT (0xd2)
scancode 0x800f744f = KEY_EPG (0x16d)
scancode 0x800f7450 = KEY_RADIO (0x181)
scancode 0x800f7451 = KEY_TITLE (0x171)
scancode 0x800f745a = KEY_SUBTITLE (0x172)
scancode 0x800f7464 = KEY_MEDIA (0xe2)
scancode 0x800f7465 = KEY_POWER2 (0x164)
scancode 0x800f7466 = KEY_GREEN (0x18f)
scancode 0x800f7468 = KEY_BLUE (0x191)
scancode 0x800f746c = KEY_CHANNELUP (0x192)
scancode 0x800f746d = KEY_CHANNELDOWN (0x193)
scancode 0x800f746e = KEY_PLAYPAUSE (0xa4)
scancode 0x800f746f = KEY_PLAYER (0x183)
scancode 0x800f7480 = KEY_BRIGHTNESSDOWN (0xe0)
scancode 0x800f7481 = KEY_PLAYPAUSE (0xa4)
Enabled kernel protocols: lirc nec rc-6
***Providing input via ir-keytable***
uron:~ # ir-keytable -t
Testing events. Please, press CTRL-C to abort.
140.603630: lirc protocol(rc6_mce): scancode = 0x800f041f
140.708048: lirc protocol(rc6_mce): scancode = 0x800f041f repeat
140.854961: lirc protocol(rc6_mce): scancode = 0x800f041f repeat

Display More

Quote

huron:~ # lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 0a)
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 09)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port (rev f1)
00:1c.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port (rev f1)
00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port (rev f1)
00:1f.0 ISA bridge: Intel Corporation HM170 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
02:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)
3c:00.0 Non-Volatile memory controller: Intel Corporation SSD 600P Series (rev 03)

Display More

This happens with both the legacy and generic image (as expected). Any ideas? It's driving me crazy.

**chewitt** · July 17, 2024 at 10:26 AM

From the problem description it's sounds like a kernel issue, so triage needs to involve building custom LE images with kernel changes that attempt to pinpoint changes to the nuvoton driver. The normal git bisect workflow (on the whole kernel) will be challenging to do as rolling back to a much earlier kernel requires more than just the kernel githash to be changed in the LE buildsystem, and you'll end up going down a rabbit hole of changes. I would instead see if there are interesting looking changes that can simply be reverted to see if anything has a positive impact.

This is the history of the driver: https://github.com/torvalds/linux…c/nuvoton-cir.c

If you are sure that problems start around the 5.x to 6.x transition we have to look back some way. Most of the changes look not related and harmless. The first one that sounds a little interesting to me is https://github.com/torvalds/linux…e6233beadc650c4 but to set expectations, I'm not a code guru.

However, to illustrate the process and test the theory I would git clone kernel sources and then revert that specific change with "git revert 4345e2e5c75895232a17e6783e6233beadc650c4" .. and if we are lucky this will revert cleanly. If it does, you can then do "git format-patch HEAD~1" to create a diff patch of the revert commit and copy the patch file to packages/linux/patches/ in the LE buildsystem. If you now respin the image, the buildsystem will detect the patch and only rebuild the kernel package with the patch applied, and then you can test the image. If the git revert fails, it's because there are other changes to the same code area since that commit, then and you need to revert the commits that touch the code in reverse sequence, and that will either be a relatively simple task with a couple more steps (and generating a few more patches to copy/respin/test) or it'll be a huge challenge. The nuvoton driver doesn't look like it had that much real-world change in recent years though, so I have a hunch specific commits will be okay to revert and test. No promises though.

The problem description shows you have a moderate level of Linux skills (enough to compile images at least) so hopefully you might have half a clue on what I'm rambling on about

las1 · July 17, 2024 at 3:22 PM

chewitt That seems to have done the trick! I was going down the right path and looking at the same nuvoton-cir.c changes but wasn't sure how I could do the revert/patch in git--network engineer, not a developer so thanks for this!

I just cloned the master Linux branch and didn't bother even checking out a branch closer to what LE11 is running. Ran the revert and patch and recompiled the image.

I'll apply this to my other PCs and test for a few days. I could attempt to do a pull request for this but it may take a few attempts..

Quote

From 01a7107571a723c47416740c87b1a8986270cfe6 Mon Sep 17 00:00:00 2001
From: x <x@eiger.home>
Date: Wed, 17 Jul 2024 09:05:27 -0500
Subject: [PATCH] Revert "media: rc: Use scnprintf() for avoiding potential
buffer overflow"
This reverts commit 4345e2e5c75895232a17e6783e6233beadc650c4.
---
drivers/media/rc/nuvoton-cir.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/rc/nuvoton-cir.c b/drivers/media/rc/nuvoton-cir.c
index 2214d41ef579..88dda9bffde5 100644
--- a/drivers/media/rc/nuvoton-cir.c
+++ b/drivers/media/rc/nuvoton-cir.c
@@ -223,10 +223,10 @@ static ssize_t wakeup_data_show(struct device *dev,
for (i = 0; i < fifo_len; i++) {
duration = nvt_cir_wake_reg_read(nvt, CIR_WAKE_RD_FIFO_ONLY);
duration = (duration & BUF_LEN_MASK) * SAMPLE_PERIOD;
- buf_len += scnprintf(buf + buf_len, PAGE_SIZE - buf_len,
+ buf_len += snprintf(buf + buf_len, PAGE_SIZE - buf_len,
"%d ", duration);
}
- buf_len += scnprintf(buf + buf_len, PAGE_SIZE - buf_len, "\n");
+ buf_len += snprintf(buf + buf_len, PAGE_SIZE - buf_len, "\n");

spin_unlock_irqrestore(&nvt->lock, flags);

--
2.39.2

Display More

Thanks!

las1 · July 17, 2024 at 6:56 PM

Eh spoke too soon, will look at going a patch or two back and re-testing

las1 · July 17, 2024 at 7:39 PM

No luck reverting to the next commit: https://github.com/torvalds/linux…a91b5d0dd6c7871 Lots of conflicts/add/removes that I'm unsure how to proceed fixing.

I'm guessing since this next commit (183e19) happened in the 4.20rc1 branch/tag and the commit you referenced (4345e2e) was the first in the 5.x branch/tag that reverting to this wouldn't make a lot of sense since it for sure happens between Linux Kernel 5.10.x and Linux Kernel 6.1.x.

Is there anything else you think I could try reverting or any additional ways to debug the nuvoton module? I just don't know enough about how this kernel module would interact with other parts of the kernel. It may look like the rc-core driver may work in conjunction with the nuvoton driver but I'm not sure...

**smp** · July 17, 2024 at 11:06 PM

The only change in that driver since kernel 5.10 (LE10) is https://github.com/torvalds/linux…440e5c8dfd02896. So I see no reason to revert other commits. The issue must be somewhere else.

las1 · July 17, 2024 at 11:33 PM

smp that's my conclusion as well and the changes seem pretty basic in that commit. My next step was to look at maybe using kgdb (after enabling in the kernel config) to try to find some additional info.

I'm an experienced Linux user (20+ years) and have been using xbmc/Kodi since the begining but this falls outside with what I know and not sure that it will be helpful. From initial research, debugging an in-tree loadable kernel module is tough to say the least..

My configs are vanilla and have been unchanged since LE7 and willing to test/try just about anything rather than refresh 5 skull canyon PCs; I'm sure someone out there is facing the same issue?

Thanks for all the helpful responses from everyone so far.

las1 · July 19, 2024 at 8:24 PM

chewitt I've been attempting to do a bisect and you're correct, it's been very challenging especially with patches and gcc versions not liking certain kernel versions. Am I able to compile the vanilla kernel outside of the LE build environment and simply install it to an existing running LE instance?

I'm having trouble determining the best workflow to complete the bisect and any guidance would be appreciated. I assume this is really the only way to fix this unless another LE developer has the same hardware and willing to test. I'm happy to do the leg work but I'm hours into the bisect screwing around with build errors.