lirc_dev does not work / high load

Bug #555863 reported by Benjamin Drung
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned
lirc (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I start irw and press any key on the remote control, the key is not recognized by irw. Instead, lirc_dev produces a high CPU load and the kernel log shows continuously the error message "i2c i2c-1: sendbytes: NAK bailout".

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic 2.6.32-19.28
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: privat 1303 F.... pulseaudio
 /dev/snd/controlC0: privat 1303 F.... pulseaudio
 /dev/snd/controlC2: privat 1303 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CK8S'/'NVidia CK8S with ALC850 at irq 20'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 42
   Simple ctrls : 27
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x300, irq 5'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Card2.Amixer.info:
 Card hw:2 'Bt878'/'Brooktree Bt878 at 0xeeaff000, irq 19'
   Mixer name : 'Bt87x'
   Components : ''
   Controls : 3
   Simple ctrls : 5
Card3.Amixer.info:
 Card hw:3 'U0xeb1a0x2801'/'USB Device 0xeb1a:0x2801 at usb-0000:00:02.2-1, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USBeb1a:2801'
   Controls : 2
   Simple ctrls : 1
Card3.Amixer.values:
 Simple mixer control 'Line',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 16
   Mono: Capture 0 [0%] [0.00dB] [on]
Date: Mon Apr 5 19:03:28 2010
Frequency: I don't know.
HibernationDevice: RESUME=UUID=d24a29c7-fb4c-5b88-d182-26c0e14dab9a
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100405)
MachineType: ASUSTek Computer Inc. K8N
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=74c1e79a-b62d-4465-a4b1-1cb3b3159aab ro quiet splash
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 02/16/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1011.005
dmi.board.name: 'K8N'
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1011.005:bd02/16/2006:svnASUSTekComputerInc.:pnK8N:pvrSystemVersion:rvnASUSTeKComputerINC.:rn'K8N':rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: K8N
dmi.product.version: System Version
dmi.sys.vendor: ASUSTek Computer Inc.

Revision history for this message
Benjamin Drung (bdrung) wrote :
Revision history for this message
Pim van den Berg (pommib) wrote :

I have this problem too. There are no problems when running kernel 2.6.31-20-generic.
I am using a Hauppauge WinTV PCI, bt878 chipset.

It looks like this is exactly the same problem:
https://bugzilla.redhat.com/show_bug.cgi?id=573675

When running kernel 2.6.31-20-generic:
Apr 17 10:18:57 localhost kernel: [ 32.076303] lirc_i2c: chip 0x10005 found @ 0x18 (Hauppauge IR)

When running kernel 2.6.32-21-generic:
Apr 22 19:31:01 localhost kernel: [ 26.860619] lirc_i2c: chip 0x0 found @ 0x18 (Leadtek IR)

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Benjamin,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Benjamin Drung (bdrung)
tags: removed: needs-upstream-testing
Revision history for this message
Benjamin Drung (bdrung) wrote :

The upstream kernels do not contain lirc_dev. For the upstream kernel, I have to install lirc-modules-source. The mainline kernel 2.6.32-02063212 + lirc-modules-source have the same issue.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Benjamin Drung (bdrung) wrote :

Maybe bug #550369 is related because I have this issue with a Hauppauge TV Card.

Revision history for this message
Andrew Baerg (andrew-baerg) wrote :

I can confirm this bug on upgrade to lucid from karmic.

rebooting with kernel 2.6.31 fixed the issue - although I had to edit /etc/default/grub and comment out the following 2 lines to be able to choose the kernel at boot:

#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true

after editing /etc/default/grub, I had to run:

sudo update-grub

Revision history for this message
Andrew Baerg (andrew-baerg) wrote :

forgot to say that I also have a haupage tv card

Revision history for this message
Greg (iskimj) wrote :

I have the same issue. Fails with 2.6.32 but works fine with 2.6.31. I tried the 2.6.33 kernel from the mainline, but the lirc modules fail to load. I'd have to compile the lirc modules for 2.6.33 but at this point I just want something that works and the old kernel will do until this is resolved.

Revision history for this message
Benjamin Drung (bdrung) wrote :

This bug is a duplicate of bug #550369. Please test the PPA package from there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.