[Samsung NP540U3C-A01UB] Incorrect battery/power status and missing /proc/acpi/battery

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1210361

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

It's probably best to have three separate bugs for your three issues. That way they can be tracked and addressed separately.

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

The upstream kernel does not resolve these bugs. Currently I have:

Linux upc 3.11.0-031100rc4-generic #201308041735 SMP Sun Aug 4 21:36:46 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux

I believe these bugs are related, but I can open separate cases if it will
help. If you want me to do that, should I close this thread?

Thanks again for your help!

On Fri, Aug 9, 2013 at 11:27 AM, Joseph Salisbury <
<email address hidden>> wrote:

> It's probably best to have three separate bugs for your three issues.
> That way they can be tracked and addressed separately.
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.11 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.11-rc4-saucy/
>
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1210361
>
> Title:
> Incorrect battery/power status and missing /proc/acpi/battery
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Hi after the last Ubuntu upgrade, I am having these power related
> problems:
>
> 1) the initial battery/power indicator does not change when the laptop
> is plugged/unplugged. If the laptop was on battery, the indicator
> continues to show it after I plug it in, and vice versa.
>
> 2) Sleep never works when the lid is closed, however it can be invoked
> using "/etc/acpi/sleep.sh" or selecting suspend from the menu.
>
> 3) /proc/acpi/battery got disappeared
>
> I am attaching the following:
>
> - version.log
> - dmesg | grep ACPI
> - dmidecode
> - lshw
> - lscpu -vnvn
> - /proc/acpi when plugged
> - /proc/acpi when on battery
> - uname -a
>
> Ubuntu is my primary OS so I will appreciate any suggestions for
> resolving this issue. Thanks in advance!
> ---
> ApportVersion: 2.9.2-0ubuntu8.3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: memo 2111 F.... pulseaudio
> /dev/snd/pcmC0D0p: memo 2111 F...m pulseaudio
> DistroRelease: Ubuntu 13.04
> HibernationDevice: RESUME=UUID=acb42b41-ef8d-4cc3-9746-06868ce9e5d3
> InstallationDate: Installed on 2012-11-09 (272 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C
> MarkForUpload: True
> Package: linux (not installed)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTI...

MeMo, could you please provide the full computer model as noted on the sticker?

It's a Samsung NP540U3C-A01UB. Please let me know what else can I do/provide for troubleshooting. Thanks!

MeMo, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Thanks. I already tried with the upstream kernel (3.11.0-031100rc4-generic) and it did not resolve the problem. I am now downloading the Saucy distro and will try is using a live session. However, it is almost for certain that the problems will not exist in the live session, since there are no hardware compatibility between my laptop and Ubuntu. All of the versions I used so far did work without a problem. The problem happened after I updated the system and it is probably a corrupt configuration.

I will provide an update as soon as I try with the latest development release.

Thanks!

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Hello again,

Sorry that it took too long, but I finally had a chance to try with the development live distribution (3.10). To my surprise, the issues persist in this versionas well! I collected and attached apport info to the thread. So, the issues are not related to my settings and can be replicated using recent live versions.

Please let me know if you need more information. Thanks again!

Hi! Were any of the information useful? Anything else that I can provide?

I would really appreciate any suggestions for troubleshooting since this problem is significantly affecting the usability of Ubuntu. The fact that the development live distro also has this problem indicates a hardware compatibility issue with the existing/future Ubuntu releases. If this is the case, are there any packages that I can downgrade to at least get the functionality back until this bug is fixed?

Also, in case it helps, the "suspend" function does work, but closing the lid does not trigger it.

Thanks again!

MeMo, did this problem not occur in a release prior to Raring?

Hi Christopher, yes, this problem did not occur prior to Raring. My laptop had been 100% compatible with all of the Ubuntu features until the update. The problem continues to affect me in various ways. Aside from inability to suspend, I have no power management at all, so the battery lasts only for a few hours. This is very inconvenient during travel. What bothers me the most is the fact that the live development release also causes these symptoms so I am worried about the sustainability of my Ubuntu experience! I really don't want to go back to Windows.

MeMo, the next step is to bisect between Precise and Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Hello, I have the same problem with Samsung NP530. Could I do something that could help you to resovle this bug?

Mark Rein, could you please file a new report so that your hardware may be tracked via a terminal:
ubuntu-bug linux

Hi, I created new account (Mark Rein was my friend's account) and repported new bug as you suggest https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245557

Folks,

After a long period of suffering, I found that this issue was caused by a combination of hardware and software problems. Apparently my laptop had power related problems, which were resolved by a motherboard replacement. This fixed the main problem, but I was still having problems having ubuntu recognizing the lid actions (open/close). After some troubleshooting, I found that the crashplan daemon running in the background was causing it.

Here's a one-liner for checking the lid actions in case you have a similar problem:

while true; do cat /proc/acpi/button/lid/LID0/state; sleep 1; done

If you don't see "close" when you close the lid, then you might like to check for running processes, starting with crashplan.

I tried to mark this case as solved, but I can only see "fix committed/released" options. How can we properly close this case?

Thank you all from Canonical and Ubuntu community for your valuable help and feedback!

MeMo, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210361/comments/48 regarding this being fixed with a motherboard swap. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.