nuvoton-cir not working after boot

[Charles]

Current setup/failing setup:
Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 4.13.0-17.20-generic 4.13.8
Ubuntu 17.10, 4.13.0-17-generic
Nuvoton w836x7hg Infrared Remote Transceiver
Zotac ID42

Working setup:
Ubuntu 17.10, 4.4.8-040408-generic

I'm not able to get the remote working after a normal reboot (using 4.13 kernel)
It does actually after a suspend and wake-up, and do a echo 'auto' to resources.

Please find snapshot of dmesg below:

[ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33
[ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0
[ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7
[ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded

<snip>
modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir
<snip>

[ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33
[ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0
[ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13
[ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded

<snip> suspend/resume

[ 105.890769] nuvoton-cir 00:0a: disabled
[ 106.651982] nuvoton-cir 00:0a: activated

<snip>
modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir
<snip>

[ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33
[ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0
[ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17
[ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded

In order to get the device working I need the following in this order:
* suspend/resume
* echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
---
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6
InstallationDate: Installed on 2014-04-01 (1317 days ago)
InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820)
MachineType: ZOTAC ZBOX-ID42-BE
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-17-generic N/A
 linux-backports-modules-4.13.0-17-generic N/A
 linux-firmware 1.169
Tags: artful
Uname: Linux 4.13.0-17-generic x86_64
UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago)
UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 05/03/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B201P010
dmi.board.asset.tag: NA
dmi.board.name: ZBOX-ID42-BE
dmi.board.vendor: ZOTAC
dmi.board.version: XX
dmi.chassis.asset.tag: NA
dmi.chassis.type: 3
dmi.chassis.vendor: NA
dmi.chassis.version: NA
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA:
dmi.product.family: NA
dmi.product.name: ZBOX-ID42-BE
dmi.product.version: XX
dmi.sys.vendor: ZOTAC

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1730958

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Charles (charles-bovy)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

[Charles (charles-bovy)]

Kernel 4.14 (latest) does NOT work correctly
Kernel 4.5.7 does work correctly
Kernel 4.6.0 does NOT work correctly

I need to do bisecting between 4.5.7 and 4.6.0 somehow. Let me figure out how to do it (or give some recommendation please).

[Joseph Salisbury (jsalisbury)]

There is a wiki on the bisect process:
https://wiki.ubuntu.com/Kernel/KernelBisection

If you need help with the bisect or building kernels, I can help you do it.

[Charles (charles-bovy)]

Thanks Joseph!
Progress is made with bisect. Only 9 steps left, but takes time with compile and testing. Hope to get there soon.

[Charles (charles-bovy)]

277edbabf6fece057b14fb6db5e3a34e00f42f42 is the first bad commit

Hope this helps.

[Charles (charles-bovy)]

not sure if it helps, but please /proc/ioports below. There is a difference between kernel 4.13 (not working) and kernel 4.5.7 (working):

kernel 4.5.7 (working):
  0220-022e : nuvoton-cir
  02e0-02ee : nuvoton-cir

kernel 4.13 before suspend and before module reload (not working):
  03e0-03ee : nuvoton-cir
  0a20-0a2e : nuvoton-cir-wake

kernel 4.13 after suspend and module reload (working):
  0220-022e : nuvoton-cir-wake
  02e0-02ee : nuvoton-cir

Maybe resource allocation is causing issues here....

[Charles (charles-bovy)]

Should I file an upstream kernel bug or is that automatically done? Any parts missing or anything I can try?
I’ve noticed it on two different systems and really strange that there are no #metoos....

[Charles (charles-bovy)]

I've just tried with more recent kernel, but issue still exists.
Kernel: linux-image-4.16.0-041600rc7-generic

[Joseph Salisbury (jsalisbury)]

Yes, it might be best to open an upstream bug since the current mainline kernel still exhibits the bug. There is some info on how to do that:

 https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Andy Whitcroft (apw)]

This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.