lirc_ite8709 kernel module failure on suspend/resume

Bug #631104 reported by Sébastien Guillemin
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This bug has been present in all version of Ubuntu since at least version ubuntu 9.10.

The lirc_ite8709 kernel module exhibits an incorrect behaviour on suspend/resume of a laptop. It sends lots of interruptions, which results in acpi sending even more interruptions, which also results in kernel scheduler sending even more interruptions.

All this flood of interruptions saturates ksoftirqd.

So the symptoms are simple: when using a device supported by lirc_ite8709 (i.e. an infrared receiver):
- suspend the laptop
- resume it
- observe that ksoftirqd uses 98-100% of one CPU core, unless you reboot your computer

The only work-around I've been able to find to avoid this behaviour is to disable the module by adding the following line in /etc/modprobe.d/blacklist.conf :

  blacklist lirc_ite8709

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mrlem 1404 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4600000 irq 48'
   Mixer name : 'Conexant CX20549 (Venice)'
   Components : 'HDA:14f15045,1631c104,00100100'
   Controls : 18
   Simple ctrls : 8
Date: Sun Sep 5 22:09:41 2010
HibernationDevice: RESUME=UUID=9121ba6d-0473-4aca-946f-9e1fad6be904
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
MachineType: Packard Bell BV EasyNote MB85
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=c57585d1-55e9-4617-a929-9c3d65b906be ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 08/01/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: PB2A3A07
dmi.board.name: PB2A
dmi.board.vendor: Packard Bell BV
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Packard Bell BV
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrPB2A3A07:bd08/01/2007:svnPackardBellBV:pnEasyNoteMB85:pvrPB92QW0202:rvnPackardBellBV:rnPB2A:rvrNotApplicable:cvnPackardBellBV:ct1:cvrN/A:
dmi.product.name: EasyNote MB85
dmi.product.version: PB92QW0202
dmi.sys.vendor: Packard Bell BV

Revision history for this message
Sébastien Guillemin (sebastien-guillemin) wrote :
Revision history for this message
Sébastien Guillemin (sebastien-guillemin) wrote :

The following file contains the ProcInterrupts output when the problem occurs.
Notice that lirc_ite8709 interrupts are more important one one core (and this was just a few seconds after the laptop woke-up, this gets worse as time passes), even though no use of the IR receiver is made.

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

Hi Sébastien,

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: kernel-suspend
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Sebastien DA ROCHA (seb-darocha) wrote :

Hi,

I have that problem too.

I've installed the mainline kernel as you (automaticaly) suggested and the problem happened again.
    21:20 seba@seba-EasyNote-MB87: ~/Téléchargements$ uname -a
    Linux seba-EasyNote-MB87 2.6.38-999-generic #201102140905 SMP Mon Feb 14 10:25:59 UTC 2011 i686 GNU/Linux

The problem doesn't occur when the module is blacklisted.

I have a Packard Bell Easynote MB87 (should be almost the same has Sebastien's MB85).

Changed in linux (Ubuntu):
status: Expired → New
tags: removed: needs-upstream-testing
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Sébastien Guillemin, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could 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.

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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.