You are not logged in.
Pages: 1
Hey folks,
i am having problems with my new laptop an lenovo ideapad u430p.
Actually it's working very well, except the battery isn't correctly recognized on about every 3rd boot.
I have a xfce setup and xfce4-power-manager applet running, and when it is not working it shows that the laptop is on powerline and full, even when it is on battery.
Plugging the power in or off does not change anything.
i first thougt, some modules are not loaded. but a diff on a lsmod output of a working and a not working boot gives me no difference
--- lsmod_battery_NOT_working.txt.sorted 2014-02-02 14:47:37.161903962 +0100
+++ lsmod_battery_working.txt.sorted 2014-02-02 14:47:49.488441422 +0100
@@ -1,11 +1,11 @@
ablk_helper 1980 1 aesni_intel
ac 3332 0
acpi_call 5224 0
-aesni_intel 46132 4
+aesni_intel 46132 5
aes_x86_64 7407 1 aesni_intel
ahci 23088 2
arc4 2008 2
-battery 7573 1
+battery 7573 0
bluetooth 308988 23 bnep,btusb
bnep 13317 2
btusb 18632 0
@@ -67,14 +67,14 @@
sd_mod 30821 3
serio_raw 5049 0
shpchp 25465 0
-snd 59109 21 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel,thinkpad_acpi
+snd 59109 18 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel,thinkpad_acpi
snd_hda_codec 150305 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hda_codec_hdmi 30162 1
snd_hda_codec_realtek 41295 1
-snd_hda_intel 37000 7
+snd_hda_intel 37000 5
snd_hwdep 6340 1 snd_hda_codec
snd_page_alloc 7242 2 snd_pcm,snd_hda_intel
-snd_pcm 77645 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
+snd_pcm 77645 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_timer 18726 1 snd_pcm
soundcore 5450 1 snd
sparse_keymap 3154 1 ideapad_laptop
@@ -88,6 +88,6 @@
videobuf2_memops 2343 1 videobuf2_vmalloc
videobuf2_vmalloc 3280 1 uvcvideo
videodev 111332 2 uvcvideo,videobuf2_core
-wmi 8419 1
+wmi 8419 0
x86_pkg_temp_thermal 6999 0
xhci_hcd 145281 0 i can see differences in /sys filesystem like:
/sys/devices/pci0000\:00/
but i have no clue where or how i can track that problem.
can sombody give me a hint? or does someone have similar problems?
Thanks in advanced
sepp
Offline
Can no one guide me a little bit?
I am lost ![]()
Offline
I saw this the first time you posted, but it seemed quite odd - I have no related experience, but maybe you can gather more data:
First, you say you see differences in the /sys/ entries (I find the symlinks easier to make sense of under /sys/class/power_supply myself). But what are these differences? Do you mean the entries are different when it 'works' and does not work as expected?
Have you tried other power managers, or other OSs (even a live cd/usb)? Do they work consistently, or show the same issue?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Hey Trilby, thanks for your reply.
i haven't tried any other live distribution. haven't thought about this possibility, i will definitely give it a try.
The differnce in /sys filesystem is this:
working:
ll /sys/class/power_supply
insgesamt 0
lrwxrwxrwx 1 root root 0 5. Feb 21:52 ACAD -> ../../devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ACAD
lrwxrwxrwx 1 root root 0 5. Feb 21:52 BAT1 -> ../../devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT1not working:
ll /sys/class/power_supply
insgesamt 0
lrwxrwxrwx 1 root root 0 5. Feb 22:03 ACAD -> ../../devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ACADOne thing i recognized after a dozen of reboots, when it does not work it also does not shutdown correctly.
it gives me something like this (no logs found):
...systemd-udev[221] not responding killing it.
...systemd-udev[224] not responding killing it.
...systemd-udev[232] not responding killing it.
then a few lines, i can't remember.
keeps hanging, no shutdown just by pressing power_button 4 secs.last line of journalctl when it does not work:
Feb 05 22:03:14 sepp-lappi systemd[1]: Shutting down.
Feb 05 22:03:14 sepp-lappi systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Feb 05 22:03:14 sepp-lappi systemd[1]: Set hardware watchdog to 10min.
Feb 05 22:03:14 sepp-lappi kernel: watchdog watchdog0: watchdog did not stop! <---highlighted red
Feb 05 22:03:14 sepp-lappi systemd-journal[189]: Journal stopped
-- Reboot --2 more things i found in journalctl:
Feb 05 22:07:19 sepp-lappi systemd-udevd[235]: worker [244] terminated by signal 9 (Killed)
Feb 05 22:07:19 sepp-lappi systemd-udevd[235]: worker [245] terminated by signal 9 (Killed)
Feb 05 22:07:19 sepp-lappi kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.WADR] (Node ffff8802538014d8), AE_AML_INFINITE_LOOP (20130725/p
Feb 05 22:07:19 sepp-lappi kernel: ACPI Error: Method parse/execution failed [\_SB_.BAT1.UPBI] (Node ffff880253802848), AE_AML_INFINITE_LOOP (20130725/psparse-536
Feb 05 22:07:19 sepp-lappi kernel: ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIF] (Node ffff8802538027f8), AE_AML_INFINITE_LOOP (20130725/psparse-536
Feb 05 22:07:19 sepp-lappi kernel: ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BIF (20130725/battery-444)
Feb 05 22:07:19 sepp-lappi kernel: wmi: Mapper loaded
Feb 05 22:07:40 sepp-lappi kernel: ideapad_laptop: Unknown event: 1ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \PMIO 1 (20130725/utaddress-251)
Jan 24 16:31:54 sepp-lappi kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jan 24 16:31:54 sepp-lappi kernel: ACPI Warning: 0x0000000000000830-0x000000000000083f SystemIO conflicts with Region \GPRL 1 (20130725/utaddress-251)
Jan 24 16:31:54 sepp-lappi kernel: ACPI Warning: 0x0000000000000830-0x000000000000083f SystemIO conflicts with Region \GPR_ 2 (20130725/utaddress-251)
Jan 24 16:31:54 sepp-lappi kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jan 24 16:31:54 sepp-lappi kernel: ACPI Warning: 0x0000000000000800-0x000000000000082f SystemIO conflicts with Region \GPRL 1 (20130725/utaddress-251)
Jan 24 16:31:54 sepp-lappi kernel: ACPI Warning: 0x0000000000000800-0x000000000000082f SystemIO conflicts with Region \GPR_ 2 (20130725/utaddress-251)
Jan 24 16:31:54 sepp-lappi kernel: ACPI Warning: 0x0000000000000800-0x000000000000082f SystemIO conflicts with Region \IO_D 3 (20130725/utaddress-251)
Jan 24 16:31:54 sepp-lappi kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jan 24 16:31:54 sepp-lappi kernel: lpc_ich: Resource conflict(s) found affecting gpio_ichOffline
Thanks for the info - I'm not sure where to look next, but other power management tools will almost certainly have the same proble (i.e. it's not an issue xfce's power manager). As far as I know - which really isn't far in this case - the /sys/device directory tree is a virtual space that represents hardware the kernel is detecting. So another distro/OS and/or another kernel version would be the next step if I was trouble-shooting this. Have you had different kernel version since you've been running arch on this machine? If so, was the issue present in all of them?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I am not sure if there were any kernel updates, the installation is quite new. so maybe one or two. I will look it up in the evening when i am home.
i will also give an live usb stick a try and post my findings.
Thx for your help so far.
Offline
Same problem here, this time with a Ideapad U330P (the same Haswell chipset).
Atfer some reboots (3 or 4, I'm not sure), the battery is not detected by the system (Gnome 3 in this case). Rebooting, the battery come back.
Happens with openSUSE, 13.1, too. But I think that not happens with Fedora 20, at least in my test. With this distro, battery is always detected.
Last edited by nevat (2014-02-23 21:53:55)
Offline
Pages: 1