[Samsung NP530U3C-A05CZ] Incorrect battery/power status

[Ondrej Sevcik]

When 13.10 is first installed, this problem does not occur. After updating, it appears.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ondrejs 2112 F.... pulseaudio
Date: Mon Oct 28 17:16:08 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=907cf27f-f5d4-4b2d-815e-e24cfb092411
InstallationDate: Installed on 2013-04-08 (202 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=b06e6413-dac5-451b-a030-e622bec477e5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-01 (27 days ago)
dmi.bios.date: 08/21/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P01ABH
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP530U3C-A05CZ
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP01ABH:bd08/21/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A05CZ:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.12 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.12-rc7-saucy/

[Ondrej Sevcik (ondrej-sev)]

Still present in 3.12rc7 kernel.

[Ondrej Sevcik (ondrej-sev)]

Hi, that firmware is Windows 7 utility, but I dont have Windows 7 installed. (I can do it, but it take some time...). But in current state my bios is
P01ABH
08/21/2012
and LED diods in front of my notebook are working as expected.

[Ondrej Sevcik (ondrej-sev)]

So I did upgrade my BIOS to latest version + reinstalled my Ubuntu to fresh 13.10 and everything works as expected.
I couldnt tell you that problem was in BIOS or in Ubuntu (But probably in BIOS).

[Ondrej Sevcik (ondrej-sev)]

P09ABH
04/19/2013

[Ondrej Sevcik (ondrej-sev)]

Hello, the problem is back. I've installed a few applications and suddenly battery indicator stops working again.

[Ondrej Sevcik (ondrej-sev)]

Still present in 3.12rc7 kernel with P09ABH 04/19/2013 bios version.

[penalvch (penalvch)]

Ondrej Sevcik, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ ?

[Ondrej Sevcik (ondrej-sev)]

Even latest 3.12-trusty doesen't fix it.

[Ondrej Sevcik (ondrej-sev)]

But it was working on 13.10. And stops working after I do some installs and upgrades. Are you sure that I should text from pre-13.04 to 13.04?

[Ondrej Sevcik (ondrej-sev)]

I don't know. I've installed clean 13.10 ubuntu and when it starts working as expected I stop focusing on that. But then I've install some apps and upgrade system via software update and it stops working again.

[penalvch (penalvch)]

Ondrej Sevcik, so you had an issue that didn't exist in pre-13.04, occurred in 13.04, disappeared in 13.10, and reappeared in 13.10.

Hence, this bug report will only focus on the latest regression from old 13.10 to updated 13.10. So, the next step is to fully commit bisect from release 13.10 to 13.10, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Launchpad Janitor (janitor)]

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