dmesg fills with "speaker allocation warnings"

Bug #1377279 reported by Artemgy
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This is an issue with the driver message log filling with warnings, and NOT an actual issue with the hardware or software functionality. Sound on this system works as expected, but dmesg becomes cluttered with log information that does not appear of significant value, considering the frequency and repetition of the warnings.

The following message appears, repeated on multiple consecutive lines: "sound hdaudioC0D0: HDMI ATI/AMD: no speaker allocation for ELD" and on some occasions is accompanied by an entry stating: "[drm:dce4_afmt_write_speaker_allocation] *ERROR* Couldn't read Speaker Allocation Data Block: 0"

The system in question is a laptop with an external monitor connected over HDMI. It has been freshly built with Lubuntu 14.10 Beta 2, and the same issue also occurs when using testing the mainline kernel 3.17.0-031700rc7.201409281835.

The occasions on which this issue (the repeated warnings) occurs under strict testing conditions include:
* Using the Monitor Preferences (LXRandR) to turn OFF and ON the external monitor (approx 10 warnings for each action)
* Putting the system into the suspend power mode and subsequently resuming (approx 30 warnings)

No warnings occur when:
* unplugging or plugging the HDMI cable
* locking and unlocking the lightdm desktop

I have observed occasions where the warnings are written many, many hundreds of times, on an almost continuous basis, but I have not been able to reproduce this behavior in controlled circumstances.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-20-generic 3.16.0-20.27
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: art 2113 F.... pulseaudio
 /dev/snd/controlC0: art 2113 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDesktop: LXDE
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
Date: Fri Oct 3 19:20:02 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-26 (7 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: Acer AO722
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=bf9f8de0-2b70-4f49-85ee-54f7d94a6508 ro
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 09/25/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE10-BZ
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.modalias: dmi:bvnAcer:bvrV1.11:bd09/25/2012:svnAcer:pnAO722:pvrV1.11:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
dmi.product.name: AO722
dmi.product.version: V1.11
dmi.sys.vendor: Acer

Revision history for this message
Artemgy (artemgy) wrote :
tags: added: kernel-bug-exists-upstream kernel-sound
Revision history for this message
Artemgy (artemgy) wrote :
Revision history for this message
Artemgy (artemgy) wrote :
Revision history for this message
Artemgy (artemgy) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Artemgy (artemgy) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 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'.

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Artemgy (artemgy) wrote :

already tested as per bug description and tagged as existing upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

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

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Also, do you happen to know if there was a prior kernel version that did not exhibit this bug?

Revision history for this message
Artemgy (artemgy) wrote :

I have now tested a new version of the upstream kernel where this issue NO LONGER occurs:

cat /proc/version
Linux version 3.19.0-031900rc2-generic (apw@tangerine) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201412290135 SMP Mon Dec 29 01:36:54 UTC 2014

Therefore I suggest there is no value to reporting this upstream. Thanks

Revision history for this message
Paul Dufresne (dufresnep) wrote :

Should be a duplicate of just now fixed upstream bug #1993217

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.