1002:6760 [Sony VAIO VPCSB2C5E] Power consumption higher after resume, probably vgaswitcheroo/radeon related

[Alessandro Pignotti]

I noticed that the power consumption, as reported in

/proc/acpi/battery/BAT1/state

gets higher when I resume my laptop from suspend to RAM. I strongly suspect that this is related to a bug in vgaswitcheroo or the radeon driver, since the power used after resume is consistent with the power used when the discrete video card is not off.

Before resume I made sure the discrete card was off by using

sudo bash -c "echo OFF > /sys/kernel/debug/vgaswitcheroo/switch"

At resume, with high power consumption, the state is reported as expected:

sudo cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:02.0
1:DIS: :Off:0000:01:00.0

Still, if I run:

sudo bash -c "echo ON > /sys/kernel/debug/vgaswitcheroo/switch"
sudo bash -c "echo OFF > /sys/kernel/debug/vgaswitcheroo/switch"

Now the power consumption goes down to the expected level.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC275 Analog [ALC275 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alex 2005 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc9400000 irq 51'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0275,104d5000,00100005 HDA:80862805,104d5000,00100000'
   Controls : 26
   Simple ctrls : 10
Date: Sun Jul 22 01:23:17 2012
HibernationDevice: RESUME=UUID=6b1034dd-b958-4939-88b4-829282357ed6
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110930)
MachineType: Sony Corporation VPCSB2C5E
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=d4bbd7c4-dc64-42f6-a165-073e9b828c86 ro pcie_aspm=force i915.i915_enable_rc6=1
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-26-generic N/A
 linux-backports-modules-3.2.0-26-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: rts_pstor mei
UpgradeStatus: Upgraded to precise on 2012-04-27 (85 days ago)
dmi.bios.date: 04/25/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R1031H4
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnINSYDE:bvrR1031H4:bd04/25/2011:svnSonyCorporation:pnVPCSB2C5E:pvrC609LHCC:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCSB2C5E
dmi.product.version: C609LHCC
dmi.sys.vendor: Sony Corporation

[penalvch (penalvch)]

Alessandro Pignotti, thank you for reporting this and helping make Ubuntu better. 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. As well, please comment on which kernel version specifically you tested.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Alessandro Pignotti (a-pignotti)]

The bug is still present in 3.4.0-030400-generic download from mainline ppa

[penalvch (penalvch)]

Alessandro Pignotti, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/ ?

[Alessandro Pignotti (a-pignotti)]

Same issue with the linked 3.5 kernel. Power consumption stays at an higher level after resume. I could not test if running

sudo bash -c "echo ON > /sys/kernel/debug/vgaswitcheroo/switch"
sudo bash -c "echo OFF > /sys/kernel/debug/vgaswitcheroo/switch"

Brings the power level down the screen locks up when the ON command is issued.

My current guess, although I'm not an ACPI expert, is that the video card at resume time is powered instead of being in D3cold state.

[penalvch (penalvch)]

Alessandro Pignotti, did this problem occur in a prior version of Ubuntu?

[Alessandro Pignotti (a-pignotti)]

It also occurred in the previous release oneiric.

[penalvch (penalvch)]

Alessandro Pignotti, the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions _VERBATIM_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about the status. Thanks in advance.

[Santiago M. Mola (smola)]

Linux Kernel Bug Tracker #45061 was marked as duplicated of #44391

[penalvch (penalvch)]

Alessandro Pignotti, as per http://www.sony.co.uk/support/en/product/VPCSB2C5E/updates an update is available for your BIOS (R2087H4). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and just 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.