Bug#986124: linux-image-4.19.0-16-amd64: Version 4.19.0-16 breaks lirc and vdr

[Salvatore Bonaccorso <carnil@debian.org>]

Control: tags -1 - moreinfo

On Thu, Apr 01, 2021 at 06:27:05AM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi David,
> 
> On Tue, Mar 30, 2021 at 12:42:50AM +0200, David Ruetti wrote:
> > Package: src:linux
> > Version: 4.19.181-1
> > Severity: important
> > 
> > Upgraded to latest packages and with Kernel 4.19.0-16 lirc stopped working. It cannot find /sys/class/rc and fills every second syslog:
> > 
> > Mar 30 00:09:45 supply lircd[296]: lircd-0.10.1[296]: Error: No /sys/class/rc/ devices found
> > Mar 30 00:09:45 supply lircd-0.10.1[296]: Error: No /sys/class/rc/ devices found
> > 
> > Booting into 4.19.0-14, lirc work as expected. Breaking of lirc
> > presumably affects vdr (vdr_2.4.1-4~etobi2_amd64.deb /
> > packages.e-tobi.net vdr-experimental buster) as well. Vdr is working
> > as expected on 4.19.0-14 kernel.
> 
> Would it be possible for you to check as well directly vanilla
> upstream 4.19.181 and ideally 4.19.183 and if reproducible try to
> bisect the offending commit introducing the issue?
> 
> https://wiki.debian.org/DebianKernel/GitBisect might help here.
> 
> It might be related to
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089 and
> 896111dc4bcf ("media: rc: ensure that uevent can be read directly
> after rc device register") from 5.11-rc6 but which was backported to
> 4.19.173 and 5.10.13.
> 
> Do you have the same problem running the backports kernel?

David reported off-list to me that the problem is actually not in the
kernel itself but the card strangely behaving. 

Thus closing the bugreport accordingly.

Regards,
Salvatore