An audio device is active 100.0% of the time: hwC0D0 Analog Devices AD1984

[Patty Langasek]

Powertop and powertop-1.13 report the audio device on a Lenovo X61 is active 100% of the time.

This is not caused by pulseaudio; the same is reported if the GUI is entirely shut down and powertop is run from the console.

In previous releases (maverick) this was accompanied by a persistent buzz from the internal speaker when unmuted. The buzz is gone in precise, but the power usage is still there.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-22-generic 3.2.0-22.35
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: harmoney 2948 F.... pulseaudio
Date: Sun Apr 8 17:14:05 2012
HibernationDevice: RESUME=UUID=bd0eb6d7-98ad-48de-84de-16cda961fa70
MachineType: LENOVO 7675CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-22-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-04-09 (0 days ago)
WpaSupplicantLog:

dmi.bios.date: 10/22/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NET29WW (1.10 )
dmi.board.name: 7675CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7NET29WW(1.10):bd10/22/2007:svnLENOVO:pn7675CTO:pvrThinkPadX61:rvnLENOVO:rn7675CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7675CTO
dmi.product.version: ThinkPad X61
dmi.sys.vendor: LENOVO

[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 v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

[Patty Langasek (harmoney)]

The problem is still there with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/linux-image-3.4.0-030400rc2-generic_3.4.0-030400rc2.201204072235_i386.deb

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Steve Langasek (vorlon)]

Based on upstream feedback, I'm closing this as invalid. Seems there was a rogue mixer setting causing the trouble.