2018-05-12, 14:53
@seiichiro0185 @"TheKraut" thanks, both of you, for your tests!
The thing I was interested in was the very few last dmesg log lines before the IR receiver stopped working, especially if ite_s_idle was called in the last IRQ block - which was not.
This means ite-cir was still in "normal" receive mode, expecting further data to arrive when suddenly IRQs stopped arriving.
So my guess is the ite-cir driver could probably be fine and the issue probably lies somewhere else. No idea where though, it could be anything - interrupt controller code, (management) BIOS, etc. Maybe it's some quirk in the ITE hardware that needs a workaround in the ite-cir driver, I wouldn't rule that out as well.
I'm out of clues now, but you collected some valuable info to better understand what's happening. Best do the same checks on Ubuntu/Arch and report that to the Ubuntu/Arch folks so they can pick up from there.
so long,
Hias
The thing I was interested in was the very few last dmesg log lines before the IR receiver stopped working, especially if ite_s_idle was called in the last IRQ block - which was not.
This means ite-cir was still in "normal" receive mode, expecting further data to arrive when suddenly IRQs stopped arriving.
So my guess is the ite-cir driver could probably be fine and the issue probably lies somewhere else. No idea where though, it could be anything - interrupt controller code, (management) BIOS, etc. Maybe it's some quirk in the ITE hardware that needs a workaround in the ite-cir driver, I wouldn't rule that out as well.
I'm out of clues now, but you collected some valuable info to better understand what's happening. Best do the same checks on Ubuntu/Arch and report that to the Ubuntu/Arch folks so they can pick up from there.
so long,
Hias
