Linux

Sound imbalance

Bug #969700 reported by Bob Merhebi on 2012-03-30

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Linux	Confirmed	Medium	linux-kernel-bugs #43062
	linux (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

The sound from the builtin speakers are imbalanced to the right.

I discovered from the Sound Setting's "Test Sound" is that the left speaker is leaking sound to the right speaker causing this towards-right-imbalance!

P.S.: This occurs in Ubuntu 10.04LTS too; not sure about later versions!

lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic 3.2.0-20.33
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat Mar 31 02:19:27 2012
HibernationDevice: RESUME=UUID=ca289df0-21d9-4446-88e6-7a0e7970674c
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MachineType: Dell Inc. Studio XPS 1640
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=60fe93c2-69d8-4f58-b5ea-b65e06e7b3c8 ro quiet splash vt.handoff=7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0Y536R
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A14
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/29/2010:svnDellInc.:pnStudioXPS1640:pvrA143:rvnDellInc.:rn0Y536R:rvrA14:cvnDellInc.:ct8:cvrA14:
dmi.product.name: Studio XPS 1640
dmi.product.version: A143
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Bob Merhebi (bobmerhebi) wrote on 2012-03-30:

AcpiTables.txt Edit (159.8 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (546 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (263 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (160 bytes, text/plain; charset="utf-8")
AudioDevicesInUse.txt Edit (192 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (63.2 KiB, text/plain; charset="utf-8")
Card0.Amixer.info.txt Edit (172 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (11.0 KiB, text/plain; charset="utf-8")
Card1.Amixer.info.txt Edit (171 bytes, text/plain; charset="utf-8")
Card1.Amixer.values.txt Edit (124 bytes, text/plain; charset="utf-8")
Card1.Codecs.codec.0.txt Edit (1.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (744 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (232 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (16.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (551 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.7 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (28.0 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (138 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (194 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (141.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (330.1 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (246 bytes, text/plain; charset="utf-8")

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2012-03-30:

This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/969700

tags:

added: laptop-testing

Brad Figg (brad-figg) on 2012-03-31

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Bob Merhebi (bobmerhebi) wrote on 2012-03-31:

Bug *not* fixed in latest upstream kernel (v3.3)

$ uname -a
Linux astrobob-Studio-XPS-1640 3.3.0-030300-generic #201203182135 SMP Mon Mar 19 01:36:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-03-31: Test with newer development kernel (3.2.0-21.34)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-21.34

Bob Merhebi (bobmerhebi) on 2012-03-31

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed
tags:	added: bot-stop-nagging removed: kernel-request-3.2.0-21.34

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-04-02:

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

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
tags:	added: needs-upstream-testing
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Bob Merhebi (bobmerhebi) on 2012-04-02

tags:	added: kernel-bug-exists-upstream removed: needs-upstream-testing
Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-04-05:

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

Changed in linux (Ubuntu):
status:	Confirmed → Triaged

Bug Watch Updater (bug-watch-updater) on 2012-04-07

Changed in linux:
importance:	Unknown → Medium
status:	Unknown → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2013-11-16:

Bob Merhebi, as per http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=R301708 an update is available for your BIOS (A15). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.